Hardware DSi nand hash mismatch

[1m4b0t]

I was looking to update unlaunch to have twilight menu's patches so i can have sound on the dsi menu and i noticed that both nand backups I have, one from 2 years ago before installing unlaunch and another from 2 months ago, don't match the hash contained on the .sha1 file, sooo, how fucked am i?

ps: i can open both nand backups with ninfs

 

[4d1xlaan]

could be the hash is without nocash footer or something

why would you restore a backup just for that though? or even care if those backups were bad? you can just rerun the unlaunch installer in twilight menu, and if you think those backups might be bad you can just make a new one

 

[1m4b0t]

could be the hash is without nocash footer or something

why would you restore a backup just for that though? or even care if those backups were bad? you can just rerun the unlaunch installer in twilight menu, and if you think those backups might be bad you can just make a new one

thank you so much, i didn't know that fwtool added the nocash footer but calculated the hash without it, removed it with hiyacfw helper as i saw on dsi cfw guide and now the hashes match

also i like to have at least the first dump before unlaunch so i can restore the dsi to how it was without unlaunch

 

[4d1xlaan]

i didn't know that fwtool added the nocash footer but calculated the hash without it

you also dont need to restore a nand dump to uninstall unlaunch

 

[RocketRobz]

you also dont need to restore a nand dump to uninstall unlaunch

Restoring a pre-Unlaunch NAND backup is the safest way to uninstall Unlaunch. The built-in uninstaller has a high chance of bricking.

 

[1m4b0t]

Restoring a pre-Unlaunch NAND backup is the safest way to uninstall Unlaunch. The built-in uninstaller has a high chance of bricking.

i read something like that on your safe nand manager post so i wanted to know if my pre unlaunch dump was usable and now i know that it is a good one

 

[4d1xlaan]

The built-in uninstaller has a high chance of bricking.

High how? I've used it plenty of times with no issues. and what would cause the brick?

from edo in 2018 it was said uninstall brick chance is the same as installing, but then again that was 6 years ago

i read something like that on your safe nand manager post so i wanted to know if my pre unlaunch dump was usable and now i know that it is a good one

https://dsi.cfw.guide/uninstalling-unlaunch.html

"If you are not able to use no$gba or get an error after uninstalling Unlaunch in no$gba it is also possible to flash a NAND backup made prior to installing Unlaunch if you still have one, however it is recommended to try using a NAND backup that previously had Unlaunch first. This will make recovery significantly easier in the case of a brick requiring a hardmod as Unlaunch leaves the no$gba footer embedded in the NAND even when uninstalled."

but also "Brick requiring a hardmod" is simply not a thing anymore lol

 

[RocketRobz]

High how? I've used it plenty of times with no issues. and what would cause the brick?

from edo in 2018 it was said uninstall brick chance is the same as installing, but then again that was 6 years ago

The Unlaunch uninstaller has a weird bug where it clears Launcher's .tmd file (before the Unlaunch area), causing the console to not boot (without ntrboot, at least).
Plenty of users on our Discord server have reported bricks after using the uninstaller, which as I recall, last happened earlier this year.

 

[4d1xlaan]

The Unlaunch uninstaller has a weird bug where it clears Launcher's .tmd file (before the Unlaunch area), causing the console to not boot (without ntrboot, at least).
Plenty of users on our Discord server have reported bricks after using the uninstaller, which as I recall, last happened earlier this year.

that's actually hilarious tbh, I mean not the fact that people can brick from that, but just the fact that is can do this

are you in touch with the ones working on safe unlaunch installer? it sounds like it should probably be suggested to use that instead of running official unlaunch.dsi, but because they never made any builds directly available, I guess it's not totally ready yet?

I mean, to be fair, I guess I would know, I'm how we found out it would brick when opening data management last month. there could be other critical bugs like this and they probably want to wait until we're sure everything is good before actually making it available

 

[rvtr]

there could be other critical bugs like this and they probably want to wait until we're sure everything is good before actually making it available

Yeah. Nothing like releasing a tool to fix an existing bug and creating more.