team-neptune / deepsea Goto Github PK

I noticed that since the 2.0.0 release, you no longer include the fusee-primary and Lockpick_RCM payloads in the /bootloader/payloads/ folder...Would you reconsider including those in future releases, since I find them to be rather useful and I am pretty sure there are many others who would as well? Thanks!

To me it seems that ndeadly/MissionControl is a more complete and actively maintained repo. Maybe these sys-modules can be used concurrently? I haven't tested. MissionControl specifically handles third party controllers connecting wirelessly via the Switch's built-in controllers menu, and doesn't support wired connections. Just a suggestion. Thanks for reviving Kosmos, it looks like DeepSea has almost all of the packages that I typically install!

Hi, a couple of days ago I was running previous release of deepsea with firmware 11.0.1 everything was fine but then I left the wireless enabled then the console was updated to 12.0.0 I waited until the firmware 12.0.0 was supported now I upgrade as soon start the console, run hetake go to atmosphere I can see the boot logo of deepsea then the purple logo of atmosphere then a black/white and finally I see the original nintendo logo (not the modified logo from deepsea) any help you cloud provide to be able to run again the homebrew version?

deepsea1.3.0-patch package still has issue in sysnand cfw
thanks TN release aio deepsea package. i found a little issue when i use it.
if you want to hack sysnand, some of nsp can't run in cfw-sysnand, i assume maybe the problem is patch.ini, fs patch doesn't working in cfw. but it's so weired that's nothing happened in cfw-emummc . so i add a line in hekate_ipl.ini to fix it as follows :
1, i DL loader.kip from haruko's github page and copy to sdpath atmosphere/kips/.
2, i add a line as "kip1=atmosphere/kips/loader.kip" below "kip1=nosigchk" in [cfw(sysnand)].
ok, fs patch take effect afterward.
the loader.kip needn't add in cfw(emummc)

i confirmed that the same issue is also with kosmos 16.1 package.

https://github.com/ITotalJustice/patches

enjoy！！！

I tried posting this issue in NSAInstaller repo, but there was no issue tab. The USB installation is not working on 11.0.0.

sorry, i can not install xci when i update to latest version

On Release v2.0.2 emuiibo "cant access" message. Didn't have this issue on Release v2.0.1

v3.3.2 支持 OLED 硬破機嗎？

Just want to say if you put edizonSe insted of edizon it will be better since edizon wont get any new update's
but edizonSe always got new update's

I have a chip cracked switch, 10.2 firmware with sxos 3.05 boot.dat.，the emunand system is 10.2 too.
When I use deepsea to enter a emunand system or a nand system, pkg1 errors will appear. I didn't have this problem using m17.1 atmosphere before, If I change 3.05 boot.dat to sx-gear 1.1 boot.dat, it's OK .
Is the guide mode of the atmosphere system or something changed？How to use deepsea with 3.05boot not sx-gear boot.dat???

Hi,

I've just installed the latest release of DeepSea, did everything in commonproblemresolver with success, I then launch CFW (SYSNAND) from Hekate and it boots OK, but I cannot open Tesla, nothing happens nor HBMenu.

When running deepsea with HOS 13 + Atmosphere 1.1.1 and booting from hekate in to emuMMC i am unable to install some NSP files as i get an invalid NCA error.

The same NSP's will not run and show as corrupt

However if i boot using fusee.bin i am able to install/run without error

Please can you advise?

I was updating the Deepsea into 3.2, then I update the latest sigpatch that supports HOS 13.00. After that I update FW 13.00 via AIO updater and Daybreak,

I boot into CFW - sysMMC via hekate, Deepsea boots up, but after got into Home menu, the Switch just hangs there, I cannot do anything, press anything, no errors popped up. I don't know what to do.

But when I tried to boot up into Stock - sysMMC, I can operate my Switch normally, no hangs or anything.

Please help.

Ok so my switch is a v1 launch unit now i am using the latest version package advanced and i know my 13.1 firmware is supported well i keep getting these crashes.It will work fine for a bit then randomly it will crash without warning.Now the only thing i have done to my switch was format the system and use a brand new fresh 512gb sandisk switch branded sd card.I copied all the files over and everything and made sure to eject the sd card before taking it out.I also do not use a emu nand and dont install any nsp files or anything so this should not be happing.Hope someone can help.

I know it has only just been released but do you plan to add support for HOS 13 and atmosphere 1.1.0 in the near future?

Thanks for the brilliant project

Hi, using 2.2.2 release of Deepsea I can’t activate Tesla from DeepSea Toolbox. When I turn it ON and go back to the homesreen, Tesla goes back to OFF.

Cannot use missioncontrol. If I delete the contents title id folder, it boots fine, but if I reinstall, it crashes on the splash screen, no atmosphere crash screen either. Hope this is where to post this issue...

Installed with aio-updater, then homebrew store.

When I update DeepSea from the updater homebrew app atmosphere crashes and I have to restart. I will put my FW version, DeepSea Version, Atmosphere Version, and DeepSea Updater Version in the morning when I have access to my pc. I am willing to help fix the issue and if I find a fix I will send a pull request. (This has probably been fixed but I never saw an issue created so I decide to create one myself)

I'm on official firmware 9.0. I am using Deep Sea's latest release for all other files. I can send the payload with a dongle, open hekate. No matter whether I choose sysnand or emunand, the deep sea logo loads, and then the screen goes black. The device is fully charged.

https://github.com/tallbl0nde/NX-Activity-Log/releases

Rationale:

• It's neat
• No seriously it's a pretty cool app

I'm confused at the need of the minimum package.. isn't this just atmosphere+Hekate with a custom bootlogo and no patches? If it has patches I 100% get it but it's not exactly clear what it's for is all.. all the best :)

I love you guys!

As the title says when I try to open HB menù with R trigger pressed I get an error that says "Unable to start the software, try again from the home". I'm on official firmware 12.0.1 and DeepSea normal 2.2.5. Any way to fix this? Thank you

Enabling Tesla on DeepSea 3.2 with firmware 12.1.0 causes the following error and prevents booting.

.

Enabling ldn_mitm is causing unexpected behavior on my switch. It seems as through for FW 12.0 a new release was published 4 days ago though DeepSea was published 5 days ago. Perhaps it's worth pinning commit shas, or tags so we know if a package is truly out of date?

Tesla is enabled in the DeepSea toolbox, however when holding down L + Down D Pad + Down Joystick nothing happens at all.

¤ Fixed support for latest Atmosphere versions (0.19.x) and for 12.x system updates. Note that this emuiibo version (and next ones) won't work on older Atmosphere versions.

https://github.com/XorTroll/emuiibo/releases/tag/0.6.3

Is there any way to bypass？

how to fix Panic while running Atmosphere Title ID: 010000000000002B
i had tried to format sd card and fix archive bit still can not run ds-cfw sysnand

I'm trying to put "Tegra Rcm GUI 2.6" and "deepsea-normal_v2.1.0.zip" into "switch 11.0.1".
However, even if I write the settings in "bootloader / hekate_ipl.ini", the contents disappear.
I don't know the cause. Please let me know.

--- The contents are as follows

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1

{--- DeepSea ---}
{DeepSea}
{Github: https://github.com/orgs/Team-Neptune/}


{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}

SciresM released atmosphere0.19.2 a pre build hash of -e8ba6326 on 2021/04/30 , The updated zip is a build hash of "-14ed4e40" released on 2021/05/02, but Deepsea 2.2.3 still used the previous one. so it cause black screen when launched cfw-sysnand/emummc, because of the old stratosphere component.

Hi. Whenever I try to open ACNH on either sysNAND CFW or emummc, I get the 2155-8007 error. I've tried almost everything, and nothing works.

The hekate_ipl.ini lacks of extra configuration: kip1patch=nosigchk

This gives sigpatches problem and can't start the game, such as "error 2155-8007", "corrupted data",...

More discussion here: https://www.reddit.com/r/SwitchPirates/comments/q2kxvd/fix_sigpatches_problem_when_booting_with_hekate

Hello there :)

Each time I launch the updater I get this error:

Any idea from where that could come from ?

Hello I am trying to download the new deep sea update but it keeps coming up with an error code of 2349-008 picture attached as well thanks

Hello Team-Neptune!
Do you know how I can uninstall DeepSea?

Hello, yesterday I updated the deepsea package and aftee booting up the sysnand or emunand I get that error, and I cant find any fix, what should I do? please help :(

when i updated deepsea, my sig patches broke but i haven't updated my switch firmware. Do you have a fix?

switch firmware : 10.0.4
i used hekate.

simply when I activate it, it crashes a few seconds after turning on and entering the HOME screen

Error Code: 2144-0001 (0x290)
Program: 0100000000001000
Firmware: 13.1.0 (Atmosphère 1.2.4-master-e256261b8)

I decided to update since AIO Updater doesn't work on Atmosphère 1.2.2, it says that the downloaded files are not zip files.
After updating, when I try to open hbmenu, it crashes with the error code shown above.
Also I'm having problems with the micro SD card, it says it was used in another Nintendo Switch, then delete the data, the NS reboots and the error is not shown, but if I reboot again the error is still there.

I got this error when start Atmosphere CFW
Error Code: 2168-0002 (0x4a8)
Program: 42000....07E51A
Firmware: 12.0.2 (Atmosphere M 0.19.4-master-2ab01ad3)

An error has occurred.

What should I do? Thanks.

I used Ksomos before, now I use DeepSea, but system_settings.ini uses the default atmosphere, which causes a lot of troubles, such as cheating all turned on by default, which makes the experience unfriendly.

In addition, there is a small BUG I want to give feedback, which existed during the Kosmos period. In cfw-sysnand, fs/loader can not be effective, resulting in cfw-sysnand unable to run tinfoil, the solution is to add loader.kip, but these will not happen in emuMMC.

You must have cfw-sysnand and emuMMC, if you only have one cfw-sysnand, this BUG will not trigger!

Thank you for your timely presence, and thank you for your work!

I am using mac Finder to connect my switch via ftp://ip:5000
Listing and opening files are fine, but when I edit and save a fie (config.ini file), I got error message say no write access.

Is it possible to enable the write permission for ftpd? I've went through the sys-ftpd/config.ini file, but find no option for this. If it's not supported by now, will it be supported in coming versions? Thanks !

I couldn't load hekate. it sends a error message. Panic Occurred.... What's the problem?

Emuiibo requires a significant update on which XorTroll was working on but as of yet is not out and/or working yet.
Using it will result into forever loading screens or crashes.

Suggestion is to remove it from the packs until updated.