Toggle sidebar

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,423
  • Replies Replies 44
  • Likes Likes 18
silien3 said:
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.
Click to expand...
Can confirm this worked for me! Thank you very mucho my friend
 
rodrigues14 said:
I made a tegrexplorer script to automatize the process.

Have you prod.keys dump in switch folder, extract this script file on you sd, run script using TegraExplorer payload, done.

The script ask you want to run on Sysmmc or Emummc.

EDIT: uploaded correct script
Click to expand...
How long should this script take to run? Im stuck for quite a while on mounting system partition. I do use a 1.5tb microSD will a larger SD cause it to be slower?
 
Last edited by SegAgeS,
Hello im having the exact same problem, but when I go into tegraexplorer and try to do the things you did, an error pops up. It says "Desc: NO FAT"
 
silien3 said:
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.
Click to expand...
You hero!! That 8000000000073 was definitely the culprit after downgrading from useless 21.0.0+ back down to stable 20.5.0 trusted you that much i didn't bother making a backup 😅
 
silien3 said:
J'ai réussi à récupérer mes données emuNAND. Je ne sais pas si la solution fonctionnera pour tout le monde après la rétrogradation de la version 21.0 à la version 20.5. Le problème est le suivant : 2162-0002 1000000000025.
Vous devrez lancer tegraexplorer.bin via Hekate.

Tutoriel : Attention : utilisez toujours eMUMMC pour l'emuNAND via Tegra Explorer.
N'y touchez pas, c'est votre sysNAND. Ceux qui rencontrent le même problème et qui n'ont pas d'emuNAND devront effectuer le test à leurs risques et périls.

Je ne sais pas si le problème est le même pour tout le monde, y compris le nom du fichier ; j’ai mis beaucoup de temps à le trouver, mais un seul fichier pose problème.

- Ensuite, avec TegraExplorer lancé par Hekate, accédez à l'emuNAND, puis à emummc,
- pour le chemin emunand = emuMMc--systeme --save ​
- pour le chemin sysnand = eMMc--systeme --save (à vos risques et périls, car cela implique la mémoire sysNAND).​

- Faites une sauvegarde au cas où

- Lorsque vous avez des valeurs 800000 et 00000, cliquez sur « Options du dossier actuel », puis sur « Copier dans le presse-papiers ».

- Retournez à l'écran de sélection avec « Parcourir la carte SD » et sélectionnez « Parcourir la carte SD ». Choisissez l'emplacement où enregistrer votre sauvegarde et copiez le contenu du presse-papiers situé juste au-dessus de l'option « Dossier actuel ».

- Vous disposez maintenant d'une sauvegarde du dossier de sauvegarde sur la carte SD ; prévoyez 1 ou 2 Go d'espace libre.

- Maintenant, la correction dans emuMMc--systeme --save localise les noms à partir de cette sauvegarde pour moi, c'était [8000000000000073]

Sélectionnez le fichier et cliquez sur « Supprimer le fichier ».

Pour moi, il a simplement suffi de supprimer ce fichier et tout a fonctionné comme avant.

Voilà, vous pouvez désormais profiter à nouveau de votre Switch en version 20.5 sans tout réinitialiser et conserver vos jeux précédemment installés sans avoir à tout recommencer.


Ça a fonctionné pour moi. J'ignore les conséquences futures, mais pour l'instant, tout redémarre. Je ne sais pas si le nom du fichier est le même pour tout le monde.


Excusez mon anglais, j'utilise Google Traduction.
Click to expand...
Merci mec, tu à littéralement sauvé ma switch après un downgrade du firmware 21, je pense que Nintendo à délibérément ajouté un fichier qui corrompe le démarrage de la console après un downgrade.
Post automatically merged:

Merci mec, tu à littéralement sauvé ma switch après un downgrade du firmware 21, je pense que Nintendo à délibérément ajouté un fichier qui corrompe le démarrage de la console après un downgrade.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Hacking Emulation  Switch Prod Keys downloading from sites okay?

Is it fixable