Homebrew RELEASE dOPUS becomes n1dus

[lordelan]

Critics.

Who did critisize him apart from the name and github confusion(s)?

 

[Localhorst86]

Who did critisize him apart from the name and github confusion(s)?

people attacked him for forking tinfoil and releasing a "competing installer" based on the source instead of contributing to the tinfoil project by issuing a pull request.

 

[lordelan]

people attacked him for forking tinfoil and releasing a "competing installer" based on the source instead of contributing to the tinfoil project by issuing a pull request.

Okay I missed that. Since he added some things (GUI, filebrowser) and removed some things (network install, install all) it became something different. But nonetheless a pull request would've been the nicer way.
However since it's open source as well it could be added to tinfoil (or the new tinfoil features could be added to n1dus).

 

[Muxi]

The tool is first class, as it automatically ignores the firmware requirement. It would make it perfect if there was a possibility of installation via the dock's USB port.

 

[Localhorst86]

The tool is first class, as it automatically ignores the firmware requirement. It would make it perfect if there was a possibility of installation via the dock's USB port.

The software has obviously been abandonded by the author. Anything on your wishlist will remain there.

 

[Muxi]

that is regrettable. Is there no one who continues development of this tool or an alternative?

 

[peteruk]

Was 0.7 the final release of n1dus ?

 

[0000ff]

Was 0.7 the final release of n1dus ?

yes

 

[peteruk]

yes

Thanks

found it !

 

[metal921]

How would one implement usb install to this? I would do it but I don’t know jack sh**

Anyways it’s sad the author abandoned this great program.

 

[peteruk]

How would one implement usb install to this? I would do it but I don’t know jack sh**

Anyways it’s sad the author abandoned this great program.

It is a real shame, I've only just started experimenting with different app's and this one is pretty great, hopefully someone will decide to take up production but it's not looking likely

 

[subcon959]

Anyone who wants to know why we didn't get to see how good this could've been can read the old thread.

You probably won't be surprised by the people responsible.

 

[peteruk]

Anyone who wants to know why we didn't get to see how good this could've been can read the old thread.

You probably won't be surprised by the people responsible.

No surprises there, just no need ffs

 

[subcon959]

No surprises there, just no need ffs

Turns out that karma really is a bitch though

 

[peteruk]

Turns out that karma really is a bitch though

true

 

[markmcrobie]

How come n1dus won't install Super Smash Bros 1.1 update? I'm on SX OS 2.3 beta and firmware 6.1

 

[duckbill007]

You need to update to firmware 6.2
Update is signed by newest master key.

 

[bad361]

How come n1dus won't install Super Smash Bros 1.1 update? I'm on SX OS 2.3 beta and firmware 6.1

there are also patched updates out there if you dont want to update like me

 

[pr0dukt]

The 1.1 Update and the DLC patcher for Smash Ultimate, unfortunately, requires 6.2.0 ofw to verify NCA signature with master key 6, which is non-existent in 6.1.0. Which is why some may have noticed if using tinfoil on 6.1.0, a booterror for missing key.
I use SX OS too consistently to forsake it to bump up to 6.2.0, plus i currently have most of my data consolidated to SX's Emunand, and still am unsure whether just renaming the Emutendo folder to Nintendo, and removing the original nintendo folder, will preserve all my emunand save and content data if persay I was to run Atmosphere primarily on sysnand instead... I likely will eventually make the full commit to Atmosphere though, as SX is far too slow behind the curve on firmware updates. CTCaer and Rei even put them to shame and they've been almost dark about eta the past couple weeks... le sigh.

In any case, Smash on. I do eventually want to crack into that DLC content..

 

[Localhorst86]

unsure whether just renaming the Enutendo folder to Nintendo, and removing the orginal nintendo folder, will perserve all my emunand save and content data if running Atmosphere on sysnand instead.

Your saves and contents are stored in the USER partition of whatever NAND you're running, that's the entire point of using TXs Emunand solution. If you're using emunand, your content database and your saves are stored in your emunand container file.

Switching back over to sysnand will basically return your switch (including your content and savegames) to the state they were in when you created your Emunand.

You might (Note: MIGHT!) be able to use hacDiskMount (https://switchtools.sshnuke.net/) to access the content of your Emunand file, extract whatever content you want from your user partition and put it on your sysnand but that depends entirely on wether or not HDM can even access the Emunand dump from SX OS. Also, you'd be doing this at your own risk, I am unable to assess wether or not this could potentially brick your system.