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

[hax4dayz]

PRESENTS

The only All-in-One package you will ever need.​

What is DeepSea?

DeepSea is an All-in-One custom firmware package for your Switch. It includes the latest version of Atmosphere and Hekate, aswell as very useful homebrew applications to get you started. All you need to do is to extract the zip you think suits you best to the root of your sd-card and push the included hekate payload. If you dont know how to hack your switch yet, head over to switch.homebrew.guide and hack your Switch first.


Why should i use DeepSea?

The Homebrews we provide are not just packed together in a zip. We modified configs, replaced files, created new ones and much more to create a flawless and well tested experience. If you know your stuff and want more freedom, this package might not be for you. But if you are new to the scene and have no idea where to start, we definitely provide the tools you need. We are working hard to create or own homebrews aswell as working with other developers to integrate our work into other systems. Join our Discord-server to get help with any problem you have (using DeepSea or not) and any homebrew.


What are DeepSeas features?

• Background FTP server for filetransfers
• Install NSP, NSZ, XCI & XCZ files from Harddrive, Google Drive, WLAN or wired through PC, Smartphone, etc
• Over & Underclocking
• Update OFW & CFW through homebrew
• Find new homebrew through the Appstore
• Savegame management
• Cheating in games (please dont cheat online)
• Emulate Amiibos
• Use all kinds of 3rd party controllers
• Lan play (like Hamachi for your Switch)
• Tesla overlay to controll all those features (press L1+DpadDown+RightStick)

For a complete list on the included homebrews, please check our Github page.


Get our latest release: here
Join our Discord-server: here

 

[ShadowOne333]

So far this looks neat!
I'll for sure give it a try.

Just a question, are you guys going to leave sigpatches out of the package?
Or are you planning on including them too?

 

[Lightyose]

Interesting. Let's see how this goes.

 

[Slluxx]

Just a question, are you guys going to leave sigpatches out of the package?
Or are you planning on including them too?

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

 

[izy]

so first void nx now this whats the difference

 

[jester_]

but why?

 

[hax4dayz]

but why?

Why

We decided to to DeepSea because Kosmos was not just a good AiO package but also a great place for developers to be and for all kinds of switch users to get help, talk about technical stuff, joke around and maybe even learn how to code themselves. It was something that we are missing right now and want to continue, despite the hate we may get. We want to help people just as much and we will continue the legacy.

 

[pimpinpsp]

but why?

Why not?

Congrats on release. Glad I was in the discord during indev

 

[Slluxx]

so first void nx now this whats the difference

the difference is that we have an automated build process, just like kosmos did (infact, we modified kosmos tools) and void "just" manually packs his releases. We also have a working updater and so on.

we actually talked to him and are trying to work together to get the best out of this situation. from here on it looks like he will use us as base and support patches but nothing is written in stone. More talk needs to be done.

 

[jester_]

blawar said he would remove patches.ini restrictions if this bundled fusee-secondary trash wasn't being actively distributed

this ""team"" is now blocking tinfoil for all of you who wanted to use secondary/patches.ini yourselves. round of applause for keeping the most useful homebrew closed off to an entire userbase. congratulations.

 

[Hayato213]

so first void nx now this whats the difference

Just a bunch of different CFW bundle packs, Kosmos was the only one that really got famous with all the other people attemptted sharing.

 

[ShadowOne333]

blawar said he would remove patches.ini restrictions if this bundled fusee-secondary trash wasn't being actively distributed

this ""team"" is now blocking tinfoil for all of you who wanted to use secondary/patches.ini yourselves. round of applause for keeping the most useful homebrew closed off to an entire userbase. congratulations.

What?
How is usage of fusee secondary wrong?
Also, re-read your first sentence:

blawar said he would remove patches.ini restrictions if this bundled fusee-secondary trash wasn't being actively distributed

How is this in any way "blocking" Tinfoil when the developer has clearly stated that he is the one making restrictions for his own purposes?

Have some logic, kid.

 

[8BitWonder]

blawar said he would remove patches.ini restrictions if this bundled fusee-secondary trash wasn't being actively distributed

this ""team"" is now blocking tinfoil for all of you who wanted to use secondary/patches.ini yourselves.

Yeah, no.
Like you mentioned in the first part of your comment blawar implemented those restrictions, and can remove them whenever.
It's their closed-source project so they do whatever they want with it.

This project won't force blawar's hand though by existing.
That's assinine. StormSilver (Fixed that for you <3)

 

[jester_]

How is this in any way "blocking" Tinfoil when the developer has clearly stated that he is the one making restrictions for his own purposes?

Have some logic, kid.

blocking the ability for old kosmos users/savvy users who want to use that boot method, by actively distributing it to people who don't know anything despite the developers wishes.

calling old men kids on a forum when you're in the wrong isn't edgy. bundle this with fusee-primary instead, and suddenly everyone can use Tinfoil again. neat, some vocal people here dislike piracy. Tinfoil is still the best installer, and continuing to actively push fusee-secondary and patches.ini to noobs means none of them can use the app. actively keeping the block in place via ignoring clearly posted messages = blocking

That's assinine.

that's not how you spell asinine.

blawar can and does block whatever he wants, but the specific action of continued distribution means that now nobody can use this with the best installer. do all the mental gymnastics you want, guys. he said it, and now with this pack, it's blocking all of those users.

 

[yikkyon]

41 minutes in and there's already some heat. Be nice guys. Hate will only ruin this entire scene.

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

Good for trying to consolidate. This is good.

 

[8BitWonder]

he said it, and now with this pack, it's blocking all of those users.

This scene doesn't cater to a single homebrew application, as surprising as that may come to you.

You can jump through however many hoops you want to try and blame this project, but we both know that at the end of the day blawar has full control over his application.

 

[jester_]

at the end of the day that blawar has full control over his application.

and i never said otherwise. i said he posted a clear message about the conditions which he would allow this style of patching/booting. ignoring it is preventing an entire userbase from using it

i don't care about catering to a single homebrew app. i think its dumb to copy kosmos (without even removing references to the name) just to selfishly claim clout at the expense of other people. i have no dog in the race, im making simple observations. i use the superior way of booting ams anyway, so I can use what i want. observations are not a crime, and this group chasing the attention is not a crime either. it's just shortsighted and quite sad

 

[Slluxx]

We are well aware of the fusee-secondary argument thats going on and its fine if you dont like that but i want to make one thing clear:

We dont care about piracy and blawar. If thats the only reason you (and others) are here for, thats fine. But dont excpect us to care about your (and others) desire to play illegal games.

We are simply doing this to get new people started, have a place to help and develop new homebrew, just as kosmos did. You cant get that type of help over at HBG for example. And we rather stay away from the toxicity that place creates.

That said, i will try to stop arguing with people that are just here for the same reson.

 

[ShadowOne333]

and i never said otherwise. i said he posted a clear message about the conditions which he would allow this style of patching/booting. ignoring it is preventing an entire userbase from using it

Nothing's stopping the "prevented userbase" from jumping to the supported (or should I say, forced) method that Tinfoil uses.
They can switch at any point, whenever they want.

Something existing doesn't make it bad, it's only made bad when someone tries to force it to be.
That's what homebrew is about, having options and deciding what to use on our own console.

Besides, trying to force their own service and option down everyone's throat, who does someone thinks to be with that?
Nintendo? LOL

 

[iriez]

Since this does seem to be a project with serious individuals committed to development I will add to xbins for auto-monitoring/posting.

I wish everyone could just play nicely though. Frankly I don't really understand the tinfoil situation enough to speculate. If I were to guess, its because some of the 3rd party bootloaders are well documented to cause issues with game installs and installers. blawar is merely trying to increase compatibility for the majority of the scene members.

I know its difficult, but try to have perspective from both sides. When you are developing for and supporting the most popular title installer application the support end can get beyond miserable if configurations are being distributed by default that cause incompatibilities.

The better way to handle this would be for blawar to take a more direct and active approach to this new team and to communicate his needs and desires and to try to convince them to distribute their bundles so that it creates the most-compatible scenario.

If not, it would be trivial to fork the releases and to make the modifications necessary to remove the secondary bootloaders ....but....it does feel like a bit of a timewaster to "fix" other peoples problems of their own making.

I can say this - I have personally had many issues with hekate. It breaks stuff. Most importantly, it causes incompatiblity issues with retroarch and tinfoil, 2 of the most popular applications on the switch. For that reason alone, I will give blawar a little extra rope here for his cause. Whether he communicates efficiently does not distract from the reality that these bootloaders do in fact cause issues that I can personally confirm.

I would encourage hax4days to take this into consideration and to make modifications to the release to account for these issues. If the developers don't understand the depth, i would encourage them to reach out to blawar and the retroarch guys to get a better understanding of the issues. The best case scenario here would be to resolve the issues from a code perspective, but if that is not possible to at the least modify the releases so that they have better compatibility.