Hacking RELEASE Team Neptune presents DeepSea. A new AiO CFW package, that continues where Kosmos left off.

FFTfanatic · Jul 8, 2021

@Slluxx Hi, first let me say thanks for all your hard work, I tried for the first time today.

Second, I'd like to make a suggestion:

- If hekate.ipl.ini is to be bundled in therefore overwriting a user's previous one when they install Deepsea (something briefly alluded to by Lordelan a few comments above), perhaps it would then be better to re-order the launch options so that [CFW (EMUMMC)] is the *first* option (and thus presents as the first / left-most option in Hekate / Nyx's launch tab) instead of [CFW (SYSNAND)].
This would reduce the likelihood of users accidentally launching sysMMC out of pure habit from always selecting the first / left-most option (because their previous hekate.ipl.ini was configured to present that way).

-----------------------------------------------------------------------------------------------------------------------------

Context / Rationale:

I decided to update OFW today, and, using DeepSea for the first time, Hekate and Atmosphere.

Previously, all my CFW activities had been on emuMMC, using exosphere.ini to stay under the radar online; just graphics mods, overclocking and emulation, no NSPs or anything like that. All my 'official' activities such as buying / downloading / updating games and playing online were done on OFW sysMMC.

After I installed Deepsea, I launched into Atmosphere and immediately sensed something was off. The background theme was white (which is what I use for sysMMC) rather than my usual black which is what I use for emuMMC. I quickly activated airplane mode (panicked placebo, if nothing else) and checked the firmware in the system info. My heart dropped - I was in Atmosphere, on *sysMMC*, and had, until seconds prior, been connected online.

I immediately turned off the Switch, booted into Hekate and checked the launch tab. As I feared, the first / left-most option which I had always used to launch CFW on *emuMMC* was now instead the option to launch CFW on *sysMMC*.
Prior to my installing Deepsea, CFW on sysMMC had always been the last / right-most option so there was little chance of me choosing it by accident. I did a google to work out what had happened, and then checked the Deepsea hekate.ipl.ini to confirm.

I should have been more careful; I now fear that there's a ban headed my way sooner rather than later.

----------------------------------------------------------------------------------------------------------------------------

If my suggestion of re-ordering the launch options is undesirable for some reason, another idea might be for Deepsea to be bundled with more conspicuous icons to visually differentiate the launch options in Hekate/Nyx? The wireframe green designs of the existing symbols are cool - but rather muted - and thus easier to overlook out of habit if you've always been pressing the first / left-most option.

If that's no good then just a mention in the read-me of the order of the launch options and an explanation of how to re-order them by editing the hekate.ipl.ini could still be wothwhile (given that scene-newbies are one of the major intended beneficiaries of the project).

Anyway, thank you for your time and keep up the good work.

Slluxx · Jul 8, 2021

FFTfanatic said:
@Slluxx Hi, first let me say thanks for all your hard work, I tried for the first time today.

Second, I'd like to make a suggestion:

- If hekate.ipl.ini is to be bundled in therefore overwriting a user's previous one when they install Deepsea (something briefly alluded to by Lordelan a few comments above), perhaps it would then be better to re-order the launch options so that [CFW (EMUMMC)] is the *first* option (and thus presents as the first / left-most option in Hekate / Nyx's launch tab) instead of [CFW (SYSNAND)].
This would reduce the likelihood of users accidentally launching sysMMC out of pure habit from always selecting the first / left-most option (because their previous hekate.ipl.ini was configured to present that way).

-----------------------------------------------------------------------------------------------------------------------------

Context / Rationale:

I decided to update OFW today, and, using DeepSea for the first time, Hekate and Atmosphere.

Previously, all my CFW activities had been on emuMMC, using exosphere.ini to stay under the radar online; just graphics mods, overclocking and emulation, no NSPs or anything like that. All my 'official' activities such as buying / downloading / updating games and playing online were done on OFW sysMMC.

After I installed Deepsea, I launched into Atmosphere and immediately sensed something was off. The background theme was white (which is what I use for sysMMC) rather than my usual black which is what I use for emuMMC. I quickly activated airplane mode (panicked placebo, if nothing else) and checked the firmware in the system info. My heart dropped - I was in Atmosphere, on *sysMMC*, and had, until seconds prior, been connected online.

I immediately turned off the Switch, booted into Hekate and checked the launch tab. As I feared, the first / left-most option which I had always used to launch CFW on *emuMMC* was now instead the option to launch CFW on *sysMMC*.
Prior to my installing Deepsea, CFW on sysMMC had always been the last / right-most option so there was little chance of me choosing it by accident. I did a google to work out what had happened, and then checked the Deepsea hekate.ipl.ini to confirm.

I should have been more careful; I now fear that there's a ban headed my way sooner rather than later.

----------------------------------------------------------------------------------------------------------------------------

If my suggestion of re-ordering the launch options is undesirable for some reason, another idea might be for Deepsea to be bundled with more conspicuous icons to visually differentiate the launch options in Hekate/Nyx? The wireframe green designs of the existing symbols are cool - but rather muted - and thus easier to overlook out of habit if you've always been pressing the first / left-most option.

If that's no good then just a mention in the read-me of the order of the launch options and an explanation of how to re-order them by editing the hekate.ipl.ini could still be wothwhile (given that scene-newbies are one of the major intended beneficiaries of the project).

Anyway, thank you for your time and keep up the good work.

Hey, thanks for this post. its always nice to see someone wanting to improve something instead of saying nothing or even bashing on it. Im sorry for what happened.

Changing the order of the boot icons is probably not what we want to do, because with 2000+ people on our discord and almost 100.000 downloads on github (not to mention all the aio updater requests) there will probably a few hundret people like you that expected it to be in the order that it was and now it suddenly changed. Changing the icons on the otherhand to make it more apparent which option is "good" and which is "bad" is a good idea. we had it that way for a long time but people called it bloat and unnecessary, thus it got removed by us.

Due to your request, we will most likely add it back in the near future!

FFTfanatic · Jul 8, 2021

Slluxx said:
Hey, thanks for this post. its always nice to see someone wanting to improve something instead of saying nothing or even bashing on it. Im sorry for what happened.

Changing the order of the boot icons is probably not what we want to do, because with 2000+ people on our discord and almost 100.000 downloads on github (not to mention all the aio updater requests) there will probably a few hundret people like you that expected it to be in the order that it was and now it suddenly changed. Changing the icons on the otherhand to make it more apparent which option is "good" and which is "bad" is a good idea. we had it that way for a long time but people called it bloat and unnecessary, thus it got removed by us.

Due to your request, we will most likely add it back in the near future!

Fair enough and thanks so much for the quick response and kind words!

Maybe I'm missing something here, but if I understand correctly, accidentally booting into Atmosphere on emuMMC instead of sysMMC would be a relatively trivial inconvenience because there are no potentially permanent consequences by comparison.

Presumably, the users for whom re-ordering the launch options might be an unwelcome change worthy of complaint, would be those who main CFW on sysMMC. But if that's their predominant use case, then they're either already banned (in which case they have nothing to worry about), or else they are not banned (yet) but are going online with CFW on sysMMC for official Nintendo services and willingly accept the increased risk.

For everyone else, i.e. those Deepsea users who try to confine CFW to emuMMC, such a change would almost certainly be most welcome as it would save them from having to edit the order of the launch options in the ipl.ini themselves after each new Deepsea installation. If they're not doing that already then it will only be because they don't know how to do it / don't know that it's possible to do so, in which case, still the same result, a welcome change as it removes the worry / risk of accidentally booting sysMMC.

Accordingly, I would suggest that the key point of consideration becomes the potential ramifications/consequences of an accidental launch. Launching into emuMMC by accident can be remedied with a reboot and reconfiguration of the ipl.ini which takes no time at all and has no effect on the likelihood of a ban by comparison. On the other hand, launching into sysMMC by accident is dangerous as it significantly increases the risk of a ban.

For these reasons, if you were to change the order, it's easily explained and defensible. If anyone had a problem with it that would say everything about them and nothing about you guys. Of course, you guys know better than anyone that you are *always* gonna get unreasonable complaints, whatever you do, but for those reasons, I'd wager that you'd actually get *less* complaints about changing the order of the launch options than you would about "unnecessary bloat" if you were to change the icons (and apparently *did* get in the past, you say), especially given how anal some people can get when it comes to aesthetics ("But where's mah gween wire fwame?!").

I dunno, maybe there's something I haven't taken into account. Anyway, I've said my piece.

Thanks again!

lordelan · Jul 8, 2021

Slluxx said:
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.

I see. Maybe what you're doing could become the better sdsetup.com

Slluxx said:
Use sys-cw. Its clingwrap but as sysmodule developed by me. With this, your problems of messing up the bootloader folder are gone

Valid point although one could argue to avoid having too many sysmodules active. I'd imagine that sys-cw would literally use almost zero memory though so yeah, really valid point.

Slluxx said:
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.

lol really? First time I'm hearing this. Oo
So any hekate***.bin on sd root that is newer than the one sent will be detected and used instead? That indeed would be pretty interesting.

FFTfanatic said:
Maybe I'm missing something here, but if I understand correctly, accidentally booting into emuMMC instead of sysMMC would be a relatively trivial inconvenience because there are no potentially permanent consequences by comparison.

If you really just boot into it without doing anything (aka you instantly detected where you are and rebooted), nothing happens.

Slluxx · Jul 8, 2021

lordelan said:
I see. Maybe what you're doing could become the better sdsetup.com

Our intention never was to compete with sdsetup. We just wanted to let our community chose the packages we prepared and deemed "worthy" to be in this AiO pack.
sdsetup is doing a great job and i dont think that what i have created will render it obsolete.

lordelan said:
Valid point although one could argue to avoid having too many sysmodules active. I'd imagine that sys-cw would literally use almost zero memory though so yeah, really valid point.

i actually dont know what the memory footprint is and i dont know how i would check that. i used sys-clk as base, stripped their code and used my own to detect if tinfoil launches so .. i really dont know.

lordelan said:
So any hekate***.bin on sd root that is newer than the one sent will be detected and used instead?

yes, thats correct

lordelan · Jul 8, 2021

Slluxx said:
Our intention never was to compete with sdsetup. We just wanted to let our community chose the packages we prepared and deemed "worthy" to be in this AiO pack.
sdsetup is doing a great job and i dont think that what i have created will render it obsolete.

Don't worry that's not what I meant. I second that. sdsetup is doing fine. However it doesn't cover my use case (a few of the suggestions I wrote earlier here) but your site has the potential to do so.

Slluxx said:
i actually dont know what the memory footprint is and i dont know how i would check that. i used sys-clk as base, stripped their code and used my own to detect if tinfoil launches so .. i really dont know.

I thought so. Saw your thread.

Nice sysmodule anyway.

Slluxx said:
yes, thats correct

Never heard of that tbh but thanks for the info. That indeed prevents me from using Argon NX.

FFTfanatic · Jul 8, 2021

lordelan said:
If you really just boot into it without doing anything (aka you instantly detected where you are and rebooted), nothing happens.

But I thought that booting Atmosphere on *sys*MMC connected to wifi with no masking countermeasures significantly increases the ban risk?

Slluxx · Jul 8, 2021

FFTfanatic said:
But I thought that booting Atmosphere on *sys*MMC connected to wifi with no masking countermeasures significantly increases the ban risk?

only if you are doing shady stuff. No one is 100% sure what exactly is bannable and what not because nintendo didnt hand us some guidlines.
The general accepted take on this that if you are only doing cfw, themes and homebrews, you probably will not get banned.

lordelan · Jul 9, 2021

FFTfanatic said:
But I thought that booting Atmosphere on *sys*MMC connected to wifi with no masking countermeasures significantly increases the ban risk?

Assuming you didn't install any NSPs or used any homebrews in your sysNAND anyway, booting into it with Atmosphère is no problem.

IgnotusP · Aug 3, 2021

Hi I installed vía all in one installer but I have one problem how do I uninstall the theme, when I turn on the payload it came with a theme on the load screen call Nintendo deepsea… how do I uninstalled it??

Slluxx · Aug 4, 2021

IgnotusP said:
Hi I installed vía all in one installer but I have one problem how do I uninstall the theme, when I turn on the payload it came with a theme on the load screen call Nintendo deepsea… how do I uninstalled it??

delete `/atmosphere/exefs_patches/bootlogo/`

TheFivePack · Aug 6, 2021

New Deepsea user after years with Sxos and just Atmosphere on my own. I'm used to moving my saves with Tinfoil. Since I can't find a way to install it with DS, is there a guide somewhere on how to use JKSV or similar? I tried restoring my save .ZIP for a few games in JKSV but they don't seem to work. Thank you!

Slluxx · Aug 6, 2021

tinfoil removed its restrictions against hekate users so you can continue to use it. probably need to install sigpatches and add the nosigchk patch to hekate.
using jksv is usually extremly simple. but i dont know how tinfoil exports the saves. usually you want to use jks to export a save to the sd, then edit or replace files in it and then in jksv import it back to the game. i dont know a guide for jksv because its extremly simple.

IgnotusP · Aug 11, 2021

Slluxx said:
delete `/atmosphere/exefs_patches/bootlogo/`

Thanks!!!

Reploid · Aug 17, 2021

Thanks for the deep sea. I had to abandon SX, altho it worked well, and on atmosphere I had problem with certain titles (Ys9, MHstories 2). I couldn't apply some DLCs or updates, because games would crush before main menu (workaround would be to install everything from patched repacked XCIs found online).
I've double-checked CFW and sigpatches, but found no solution. Furthermore, I've decided to give Deep sea a try, even tho I was sure I can install everything myself. Dunno what was the case, but this problem seems to be gone. Problematic games are working again with any additions and from any source.

PS I found strange behavior. If in hekate I'll choose to boot to 'sysnand cfw' I'll boot to Atmosphere alright, but all apps would give error momentarily after launch. But if I'll try to choose to manually load 'fusee primary' everything works fine.

spotanjo3 · Aug 17, 2021

Wow, I am so behind, lol! Anyway, It is great for newbies. If someone in my family or my friends that are newbies then I would be sure to let them know about this. The reason is that I always do it for them without them learning something. It is great for them so they can study it and learn themselves. Maybe not but at least they can do it themselves.

viper3344 · Sep 27, 2021

Slluxx said:
patches will not be included. But we are very sure that there will be people that make it easy to include them, if you really want them

Hey Slluxx! Just migrated from SXos to atmo then did an emunand to the latest fw13 and your deepsea worked great! Had to add my own sigpatches but everything is working great and I LOVE the custom boot logo as well. Your work is very appreciated and I love your all in one package!

Slluxx · Sep 27, 2021

viper3344 said:
Hey Slluxx! Just migrated from SXos to atmo then did an emunand to the latest fw13 and your deepsea worked great! Had to add my own sigpatches but everything is working great and I LOVE the custom boot logo as well. Your work is very appreciated and I love your all in one package!

Thanks! Ill share the compliment with the team!
Hope you have a great time with you switch

Purple_Heart · Sep 28, 2021

After I put the deepsea files on my sd... I always grt an sd card data damaged error (I was using ams and hekate (downloaded em seperately) I just copied the newest deepsea advanced package over

Purple_Heart · Sep 28, 2021

Sora Takihawa said:
After I put the deepsea files on my sd... I always get an sd card data damaged error when I launch a game installed on sd (I was using ams and hekate (downloaded em seperately) I just copied the newest deepsea advanced package over

Hacking RELEASE Team Neptune presents DeepSea. A new AiO CFW package, that continues where Kosmos left off.

Active Member

GBATemp Mayor

Active Member

Well-Known Member

GBATemp Mayor

Well-Known Member

Active Member

GBATemp Mayor

Well-Known Member

Well-Known Member

Attachments

GBATemp Mayor

New Member

GBATemp Mayor

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

GBATemp Mayor

GBATemp´s weirdest Individual

GBATemp´s weirdest Individual

Similar threads

Popular threads in this forum