Hacking ROM Hack [Tuto] For those experiencing bug 2162-0002 010000000025 following a downgrade from 21.0 to 20.5, recover the emuNAND without data loss and therefore

  • Thread starter Thread starter silien3
  • Start date Start date
  • Views Views 13,843
  • Replies Replies 44
  • Likes Likes 18
i upgraded to 21.0 and now i cannot boot hekate at all. my switch gets opened like there is no hekate. could anyone help me with that
 
Thank, you,
step by step (hours to backup the save folder) was ok !

I recovered access to EmuMMC system !! love you !

Still all games "corrupted".

(not all in fact, so I will try to reinstall the ones corrupted)

Any idea ?
 
Last edited by holister,
Du bist mein Superheld dieses Jahr ❣️
Post automatically merged:

Danke schön,
Schritt für Schritt (Stunden für die Sicherung des Speicherordners) war in Ordnung!

Ich habe wieder Zugriff auf das EmuMMC-System!! Ich liebe dich!

Immer noch sind alle Spiele "beschädigt".

(Tatsächlich nicht alle, daher werde ich versuchen, die beschädigten neu zu installieren.)

Irgendeine Idee?
Welche Firmware-Version ist installiert? Und welche Version von Atmosphere?
Ich hatte auch mit den meisten Spielen Probleme. Jetzt habe ich Atmosphere 1.9.5 und Firmware 20.0.0 installiert, und alles funktioniert wieder einwandfrei.
 
Last edited by sir-tobi88,
Okay, I managed to recover my emuNAND data. I don't know if it will work for everyone after downgrading from 21.0 to 20.5. The bug is 2162-0002 1000000000025.
You will need to launch tegraexplorer.bin via Hekate.

Tuto: Warning: always use eMUMMC for the emuNAND via Tegra Explorer.
Don't touch that one, it's your sysNAND. Those with the same problem who don't have emuNAND will have to test it there at their own risk.


I don't know if the bug is the same for everyone, including the filename, it took me a long time to locate it, but only one is problemati

- Then, with TegraExplorer launched by Hekate, go to the emuNAND, then emummc,
- for path emunand = emuMMc--systeme --save
- for path sysnand = eMMc--systeme --save (at your own risk, as this involves the sysNAND.)

- make a backup just in case

- Where you have 800000 and 00000 values, click on "Current Folder Options" and then on "Copy to Clipboard".

- Return to the selection screen with "Browse SD" and select "Browse SD". Choose where to place your backup and copy the clipboard directly above the "Current Folder option.

- Now you have a backup of the save folder on the SD card; allow 1 or 2 GB of free space.

- Now the fix in emuMMc--systeme --save locate the names from this backup for me for me it was [8000000000000073]

- Select the file and click on delete file

- For me, it was simply a matter of deleting that file and everything worked as before.

There you go, you can now enjoy your Switch on version 20.5 again without resetting everything and keep your previously installed games without having to start all over again.


It worked for me, I don't know the future impact, but for now, everything is starting up again for me. I don't know if the file name is the same for everyone


Sorry for the English, I'm using Google Translate.
save my life ! everything come back! worked proper
 
And if you downgrade the sysnand you're just... fucked? I have legit 6.2 backup but I've always just updated through the servers so my fuses are burnt and thus I'm fucked?
 
Okay, I managed to recover my emuNAND data. I don't know if it will work for everyone after downgrading from 21.0 to 20.5. The bug is 2162-0002 1000000000025.
You will need to launch tegraexplorer.bin via Hekate.

Tuto: Warning: always use eMUMMC for the emuNAND via Tegra Explorer.
Don't touch that one, it's your sysNAND. Those with the same problem who don't have emuNAND will have to test it there at their own risk.


I don't know if the bug is the same for everyone, including the filename, it took me a long time to locate it, but only one is problemati

- Then, with TegraExplorer launched by Hekate, go to the emuNAND, then emummc,
- for path emunand = emuMMc--systeme --save
- for path sysnand = eMMc--systeme --save (at your own risk, as this involves the sysNAND.)

- make a backup just in case

- Where you have 800000 and 00000 values, click on "Current Folder Options" and then on "Copy to Clipboard".

- Return to the selection screen with "Browse SD" and select "Browse SD". Choose where to place your backup and copy the clipboard directly above the "Current Folder option.

- Now you have a backup of the save folder on the SD card; allow 1 or 2 GB of free space.

- Now the fix in emuMMc--systeme --save locate the names from this backup for me for me it was [8000000000000073]

- Select the file and click on delete file

- For me, it was simply a matter of deleting that file and everything worked as before.

There you go, you can now enjoy your Switch on version 20.5 again without resetting everything and keep your previously installed games without having to start all over again.


It worked for me, I don't know the future impact, but for now, everything is starting up again for me. I don't know if the file name is the same for everyone


Sorry for the English, I'm using Google Translate.
Chiming in for the people facing this issue but with sysnand instead of emunand: doing this method worked for me on sysnand. I downgraded from 21.0.1 to 20.5.0 and ran into the 2162-0002 error. I couldn't boot into stock or atmosphere on sysnand, the screen would show nothing at all, not even a charging indicator with it plugged in when the system was shut off and I originally thought I had a brick until I realized I could still get into rcm.

After deleting just the 8000000000000073 file in Tegra, I'm now able to boot into stock or atmosphere on sys but with one lingering problem: I for some reason cannot boot into stock normally with the power button while my switch is powered off. I can only get it to turn on through hekate. I'll be investigating this further at some point but for now I'm just happy I can use it.

Obviously take your precautions with a backup and all that but it indeed worked (mostly)! A million thank yous for your solution :)
 
Last edited by koltron,
I was on 20.0.0 and accedently downgraded to 19.0.0 (wanted to update to 21.0.0 but wrong folder)
Tried to deleate the Folder 800...0073 and didnt work.

IF anyone can fix this please msg me but i guess ill reset my Emummc and build it new.
Saved all my saves so ty for that.
 
I was on 20.0.0 and accedently downgraded to 19.0.0 (wanted to update to 21.0.0 but wrong folder)
Tried to deleate the Folder 800...0073 and didnt work.

IF anyone can fix this please msg me but i guess ill reset my Emummc and build it new.
Saved all my saves so ty for that.

Did you try the recovery mode?. (Press + and - at the same time while booting the console). You'll lose the games installed but saves are ok.
 
Cheers for this. I was on Sysnand and updated to 21.0.0, downgraded to 20.1.0 after. Was having this issue but it's fixed now and all my games + saves still seem to be working fine.
 
Hi so for me, I downgraded from 21.1 to 20.5 and now Atmosphere give me the error screen with the same code:
Result: 0x4A2 (2162-0002)

Program ID: 0100000000000025
My switch's lcd is wearing out (lines) so I can't see very well, so I navigated on my pc instead. Did I do the right thing by going to "H:\emuMMC\RAW1\Nintendo\save\8000000000000124"? I don't have 80...073, I just have this 80...0124 instead. I tried deleting that but still getting the same error :(

I have downgraded atmosphere to 1.9.5 as well as fusee.bin, am I missing something here? Please help
 
Hi so for me, I downgraded from 21.1 to 20.5 and now Atmosphere give me the error screen with the same code:
Result: 0x4A2 (2162-0002)

Program ID: 0100000000000025
My switch's lcd is wearing out (lines) so I can't see very well, so I navigated on my pc instead. Did I do the right thing by going to "H:\emuMMC\RAW1\Nintendo\save\8000000000000124"? I don't have 80...073, I just have this 80...0124 instead. I tried deleting that but still getting the same error :(

I have downgraded atmosphere to 1.9.5 as well as fusee.bin, am I missing something here? Please help
No you can't solve it like that. The file you need to delete is on the hidden partition containing your RAW EmuMMC. So you need to use Tegra Explorer or a similar tool. Maybe you can use Hekate to mount your EmuMMC on your computer and then delete the file from there.
 
Ty so much for this...i misclicked on update instead of game start and had to do so much research for a fix, this helped me go back to atmo 1.9.5 , firm 20.5 :cry:
 

Site & Scene News

Popular threads in this forum