@yukimuravn & @burhansalih
"Program: 42000....07E51A" is a Tesla error. you can just delete the "boot2.flag" file located under "atmosphere/contents/420000000007E51A/flags".
There is hardly ever a need to delete the entire atmosphere folder.
@YBI & @hausa51
You can get the patches from aio-switch-updater which is included with DeepSea. No need to manually download them.
We modify Atmopshere's settings slighly and deliver a preconfigred hekate+atmosphere setup, bundled with always up-to-date homebrews. Its aimed at people that are new to the scene or people that just dont want any hassle taken care of. There are some slight changes to the booting process as we dont use fusee-primary at all but completly rely on hekate to manage the bootprocess (known as FSS0 instead of Fusee-Primary). This hekate has more features, newer code and boots slightly faster.
"Program: 42000....07E51A" is a Tesla error. you can just delete the "boot2.flag" file located under "atmosphere/contents/420000000007E51A/flags".
There is hardly ever a need to delete the entire atmosphere folder.
@YBI & @hausa51
You can get the patches from aio-switch-updater which is included with DeepSea. No need to manually download them.
We modify Atmopshere's settings slighly and deliver a preconfigred hekate+atmosphere setup, bundled with always up-to-date homebrews. Its aimed at people that are new to the scene or people that just dont want any hassle taken care of. There are some slight changes to the booting process as we dont use fusee-primary at all but completly rely on hekate to manage the bootprocess (known as FSS0 instead of Fusee-Primary). This hekate has more features, newer code and boots slightly faster.
Last edited by Slluxx,
This is a fss0 build, different than loading from Fusee Primary. If you use deepsea you need hekate/fss0 patches, and tinfoil doesn't work with hekate/fss0 build, blame Blawar.
I know fella but always better to start from scratch I guess right or at least clean.
this is also not entirely true. you can still use tinfoil with hekate/fss0 if you know how. But its a "hack" and since the biggest freeshops are a thing of the past, thankfully there is no need to use it anymore. Goldleaf, Awoo, Tinwoo, DBI, doesnt matter .. use anything other than tinfoil pls
This in itself also isn't entirely true. Tinfoil is still the best installer due to the vast amount of features it has, and even though I really dislike Blawar, I cannot deny the fact that he did a great job with Tinfoil. There's also still many freeshops around, even if some like HBG and JITS are down, there's still plenty, so that fact is also evidently wrong. I can understand the argument, but I ended up going with Atmosphere + Hekate + EmuNAND (and I use the Atmosphere Updater Tool by the JITS gang, really great to update Hekate + Patches and make Hekate work with Atmosphere and EmuNAND and have all the right options and configs), works all totally fine.
Do you really want to nitpick?
this is absolutly subjective. also quantity is not quality.
i said "since the biggest freeshops are a thing of the past". Of course there are still others and i have never said HBG and JITS are the only shops around. if you are referring to "thankfully there is no need to use it anymore." this is still true. the existing shops are quite small and as soon as they become bigger because the top shops are gone, they hit googles quota limit easily. Either tinfoil/the backend thats used figures out how to circumvent that "new" obstacle or tinfoil changes to a different hoster, which it didnt do yet, effectively rendering it useless for growing freeshops.
Considering that most of these installers also crash often in one way or another, Tinfoil has both quality and quantity, but that aside, to answer your other statement, it doesn't just use Google, some shops use private hosted servers, which I won't mention here though.
DeepSea was updated to 3.0.0
The biggest news right away: We have worked together with @Homlet to bring a custom package builder into your browser and on your switch!
From now on, you can create your own custom package and use that instead of our predefined ones. You can easily update your package
whenever you want (the homebrews on our server are updated every hour)!
You will even find the Sigpatches there
Check out the browser version here: https://builder.teamneptune.net/
Don't miss out on our payload CommonProblemResolver (CPR).
It will help you fix the most common issues with your switch right from within Hekate, so you hopefully never need a pc to fix your switch anymore.
Some examples that our payload covers are: Updating while having themes installed, Cling-Wrap was still active upon reboot,
it removes extra files added by mac (._* files) and much more!
We also added a new "advanced" package.
This package is what the normal package was but with a few extras, while the normal package got a little less heavy. Check our readme for a list of included homebrews.
Support for HOS 12.1.0 was added by updating Atmosphere and Hekate.
Of course all available homebrews got updated too.
https://github.com/Team-Neptune/DeepSea/releases/latest
PS: We tested everything with a few people but if you experience bugs or have ideas how to improve things even further, please let us know (Barbeitet)
The biggest news right away: We have worked together with @Homlet to bring a custom package builder into your browser and on your switch!
From now on, you can create your own custom package and use that instead of our predefined ones. You can easily update your package
whenever you want (the homebrews on our server are updated every hour)!
You will even find the Sigpatches there
Check out the browser version here: https://builder.teamneptune.net/
Don't miss out on our payload CommonProblemResolver (CPR).
It will help you fix the most common issues with your switch right from within Hekate, so you hopefully never need a pc to fix your switch anymore.
Some examples that our payload covers are: Updating while having themes installed, Cling-Wrap was still active upon reboot,
it removes extra files added by mac (._* files) and much more!
We also added a new "advanced" package.
This package is what the normal package was but with a few extras, while the normal package got a little less heavy. Check our readme for a list of included homebrews.
Support for HOS 12.1.0 was added by updating Atmosphere and Hekate.
Of course all available homebrews got updated too.
https://github.com/Team-Neptune/DeepSea/releases/latest
PS: We tested everything with a few people but if you experience bugs or have ideas how to improve things even further, please let us know (Barbeitet)
FYI, I updated using the new package. Copied and replaced all files, and now I have corrupt games everywhere. Going to do a complete wipe of all items, except my games, and see how it goes. Also I think it removed my hekate INI which had kip1patch=nosigchk removed.
You did not install the patches. And yeah, the hekate file will not have the kip1patch, we will do something about that soon
Nice so far.
I won't use a package like DeepSea personally since I know what I'm doing (I'm using AiO updater though since it leaves my hekate_ipl.ini as it is which is amazing) but nevertheless I tried your link to see what I would have wanted because I often set up consoles for friends and I like the lazy less time consuming way (aka use CFW packages) so whats missing imho is:
- MissionControl (especially since you included the USB-only sys-con)
- Checkpoint
- DBI (although I understand that you most likely won't do that since it's not open source)
- HekateBrew (since you're always bundle hekate anyway, it's the best "reboot to payload" homebrew imho)
- Lockpick_RCM payload
aaand very nice would be an optional step (for advanced users) that let's you configure the content of the hekate_ipl.ini ...
Something like in a CMS ... "add item" -> "add payload path" + "add custom bootscreen" + "edit icon image".
Also I really hope that you automatically put the most recent fusee-primary.bin in sd:/bootloader/payloads/ and the most recent hekate.bin as sd:/atmosphere/reboot_payload.bin so I could use that CMS feature to create myself a fusee-primary AMS entry in hekate's launch section and remove the fss0 one if I like to do so.
That would make it very nice and easy for me to quickly configure a CFW package for a friend.
Very nice work anyway. Site looks good and feels good. Well done.
I thought I had selected it. Maybe not, I was also going to mention the selection is not super clear when selecting and deselecting. Great product though.
Btw: Really like this one!
https://github.com/Team-Neptune/CommonProblemResolver
All three features are fantastic.
If anyone's interested, this is my setup:
I have hekate payload here: sd:/argon/payload.bin
Then I use my RCMloader One to always send the Argon payload which autoboots hekate.
However if I messed things up I can hold VOL- in Argon to get to a payload selection and use CommonProblemResolver.
Then I use AiO Switch Updater to keep hekate, Atmosphère and sigpatches up to date.
https://github.com/Team-Neptune/CommonProblemResolver
All three features are fantastic.
If anyone's interested, this is my setup:
I have hekate payload here: sd:/argon/payload.bin
Then I use my RCMloader One to always send the Argon payload which autoboots hekate.
However if I messed things up I can hold VOL- in Argon to get to a payload selection and use CommonProblemResolver.
Then I use AiO Switch Updater to keep hekate, Atmosphère and sigpatches up to date.
Nice so far.
I won't use a package like DeepSea personally since I know what I'm doing (I'm using AiO updater though since it leaves my hekate_ipl.ini as it is which is amazing) but nevertheless I tried your link to see what I would have wanted because I often set up consoles for friends and I like the lazy less time consuming way (aka use CFW packages) so whats missing imho is:
- MissionControl (especially since you included the USB-only sys-con)
- Checkpoint
- DBI (although I understand that you most likely won't do that since it's not open source)
- HekateBrew (since you're always bundle hekate anyway, it's the best "reboot to payload" homebrew imho)
- Lockpick_RCM payload
aaand very nice would be an optional step (for advanced users) that let's you configure the content of the hekate_ipl.ini ...
Something like in a CMS ... "add item" -> "add payload path" + "add custom bootscreen" + "edit icon image".
Also I really hope that you automatically put the most recent fusee-primary.bin in sd:/bootloader/payloads/ and the most recent hekate.bin as sd:/atmosphere/reboot_payload.bin so I could use that CMS feature to create myself a fusee-primary AMS entry in hekate's launch section and remove the fss0 one if I like to do so.
That would make it very nice and easy for me to quickly configure a CFW package for a friend.
Very nice work anyway. Site looks good and feels good. Well done.
Thank you for your that message!
- MissionControl is currently disabled because it has problems with the latest versions of atmosphere (i have to admit that i have not checked back at it in quite some time now though).
- We didnt include Checkpoint because JKSV is already included, but i guess with the custom builder, we can go a little more broad on the options. I think ill rewrite the website to cover more options and do something for advanced users too. This will take me some time though.
- DBI is closed source, yeah. not quite what we like.
- (HekateBrew) Is that something people really need? A reboot with deepsea will always boot you into hekate and from there you can choose all the payloads you want. Sure its faster to cut out the extra step but we are trying to balance easyness, the confusion that something can create (eg an overlay expects the user to know what tesla is) and the files/filesizes. Everything is wheighted differently and on a "per app" basis. I need to look into HekateBrew and evaluate this with the team.
- probably will add lockpick soon
- Hekate payload is already set to "sd:/atmosphere/reboot_payload.bin". probably add the fp.bin file to payloads too soon.
Regarding your setup: why use argon? Whats the benefit?
Hekate can boot all payloads and if your argon autoboots hekate, i see no reason for the man in the middle
Since you seem to have that website of yours collect and pack automatically all latest homebrew versions (directly from github I guess?) it's a good chance to bundle more optional stuff like HekateBrew even if you personally don't see the big use case for it. Just hide it behind a checkbox like "more apps" or "advanced user" that will unfold more of those app tiles to pick from.
Same goes here. Add a warning or disclaimer that this is closed source software and thus it's not recommended to use it or that there's no warranty or whatever, the same way many Linux distributions do it when they bundle media codec packages and so on.
However I still absolutely understand if you and you're team don't want to do this in the first place so take it as nothing but a suggestion from me with no real intention behind it.
For two reasons.
1. Those who use Cling Wrap may mess up their bootloader folder so they can't use hekate unless they used your nice CRP payload to fix that and: You can just boot that directly from Argon NX so in your next reboot cycle you can let it chainload hekate again.
2. Especially for those with a payload injector dongle like RCMloader One it's pretty nice to use Argon NX. You set up your dongle to use Argon NX just once, then never touch it again.
Now you just have to update sd:/argon/payload.bin on your SD card when you update hekate.
Because if you directly put hekate on the dongle and don't touch it for a while, your Switch firmware might be too new for that (meanwhile) old hekate version to boot and you have to update it on the dongle as well.
Last edited by lordelan,
Almost. The website is just the frontend to a custom backend i wrote. It does more than just downloading things from github but yeah, the general idea is about the same. Its not quite as easily doable because everything is integrated and connected with AiO updater. Ill work on it but i need some time to get some things right.
1. Those who use Cling Wrap may mess up their bootloader folder so they can't use hekate unless they used your nice CRP payload to fix that and: You can just boot that directly from Argon NX so in your next reboot cycle you can let it chainload hekate again.
Use sys-cw. Its clingwrap but as sysmodule developed by me. With this, your problems of messing up the bootloader folder are gone
This is impossible since we store a copy of hekate of the sdcard. If an old hekate payload is pushed, hekate will detect itself on the sd and use the new version instead.
-
-
-
-
-
-
-
@
Xdqwerty:
@Purple_Heart, then I will be actually older than him for a bit (ik thats not how ages work btw) -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
