Hacking Problem with restoring Nand

  • Thread starter Thread starter Madsmaten
  • Start date Start date
  • Views Views 3,875
  • Replies Replies 25

Madsmaten

Member
Newcomer
Joined
May 31, 2015
Messages
23
Reaction score
3
Trophies
0
Age
34
XP
239
Country
Hi guys!

I am helping a friend out with a Switch. However we have a little bit of difficulties restoring it's Nand.

I am trying to restore the Switch into a clean 5.1.0 Nand backup.

It has been running SX OS - Autorcm, with a ChoixDuJourNX installed firmware of: 8.0.1
No fuses are burned over 5.1.0 (just checked).

Here is the deal, I have the rawnand.bin file, I also have keys and a few other files such as "SYSTEM", "SAFE", "PRODINFO" and "PRODINFOF".
However I don't have the boot0 and boot1 files.

Is there anything I can do to restore the Switch back to it's original state?
 
Last edited by Madsmaten,
Hi guys!

I am helping a friend out with a Switch. However we have a little bit of difficulties restoring it's Nand.

I am trying to restore the Switch into a clean 5.1.0 Nand backup.

It has been running SX OS - Autorcm, with a ChoixDuJourNX installed firmware of: 8.0.1
No fuses are burned over 5.1.0 (just checked).

Here is the deal, I have the rawnand.bin file, I also have keys and a few other files such as "SYSTEM", "SAFE", "PRODINFO" and "PRODINFOF".
However I don't have the boot0 and boot1 files.

Is there anything I can do to restore the Switch back to it's original state?
May I ask why a clean 5.1.0?

As soon as you connect, it will update.

I`d go back to 8.0.1 and choiNX down to 5.1.0 ticking the system initialise - full factory reset option.

This will give you a clean emmc.
 
  • Like
Reactions: NoNAND
I believe you would need the BOOT 0/1 of the original NAND backup in order to achieve a proper system restore.
There ought to be blank boot 0/1 sample files somewhere in the homebrew section.
If you're sure that your current number of fuses aren't burnt and are eligible for booting a 5.1.0 OFW you should consider rebuilding your NAND with ChoiPC and upgrade to 6.0 if you can't get your backup to restore in the end.
 
  • Like
Reactions: Deleted User
May I ask why a clean 5.1.0?

As soon as you connect, it will update.

I`d go back to 8.0.1 and choiNX down to 5.1.0 ticking the system initialise - full factory reset option.

This will give you a clean emmc.

This Switch is going to be restored and used without CFW.
It would not stay on 5.1.0 for long.

So I should downgrade it to 5.1.0, factory reset it, and the backup the boot files?
Afterwards uninstall autorcm and then restore the rawnand, and boot0 + boot1?
 
This Switch is going to be restored and used without CFW.
It would not stay on 5.1.0 for long.

So I should downgrade it to 5.1.0, factory reset it, and the backup the boot files?
Afterwards uninstall autorcm and then restore the rawnand, and boot0 + boot1?

Just grab 8.1.0 firmware from the site that cant be mentioned(hint - umbrella) and choiNX to that firmware.

You cannot restore same version with choiNX. Thats why I say 8.1.0.
 
Just grab 8.1.0 firmware from the site that cant be mentioned(hint - umbrella) and choiNX to that firmware.

You cannot restore same version with choiNX. Thats why I say 8.1.0.

I apologise, but I don't understand :D

Why would upgrading to 8.1.0 with choiNX help me restore my boot files?

--------------------- MERGED ---------------------------

I believe you would need the BOOT 0/1 of the original NAND backup in order to achieve a proper system restore.
There ought to be blank boot 0/1 sample files somewhere in the homebrew section.
If you're sure that your current number of fuses aren't burnt and are eligible for booting a 5.1.0 OFW you should consider rebuilding your NAND with ChoiPC and upgrade to 6.0 if you can't get your backup to restore in the end.

Fuses burnt: 6 = either a 5.0.2 or 5.1.0 firmware.
 
  • Like
Reactions: NoNAND
Alrighty then, if your fuse count matches your current CFW there's no need to update, simply fix your NAND with Choi.
Not sure I know how to do this?
I thought that the only sure way to get back online, would be a "clean" nand restore.
 
I apologise, but I don't understand :D

Why would upgrading to 8.1.0 with choiNX help me restore my boot files?

--------------------- MERGED ---------------------------



Fuses burnt: 6 = either a 5.0.2 or 5.1.0 firmware.
because you already have 8.0.1 on there. you havent restored yet have you?

Hidden on my git, there are blank files.
 
because you already have 8.0.1 on there. you haven't restored yet have you?

Hidden on my git, there are blank files.
No nothing has been restored.

I realized that I did not have the boot files, I would not go through with it without consulting you guys.

Does it matter whether it was 5.0.2 or 5.1.0 the backup was taken on?

So I will install 8.1.0 with ChoiNX.
And then restore boot files with the one from your Git?
+ the original rawnand?
 
Last edited by Madsmaten,
Alrighty then, if your fuse count matches your current CFW there's no need to update, simply fix your NAND with Choi.
Can you guide me in how to do that?
Or point me in a direction of a guide/video on it? :D

Also: Thank you guys for helping me out.
 
  • Like
Reactions: NoNAND
I guess I could get away with just restoring my boot0 & boot1 as it says on step 5 and 6.

And then reflashing my original rawnand, right?
If you have a "blank" BOOT0/BOOT1 for 5.1.0 from mattytrog and then restore a 5.1.0 NAND backup, it should work.
 
  • Like
Reactions: Madsmaten
As far as I can tell they only goes from 6.20 and up.

Would this work: Uninstall autorcm, flash blank 8.0.1 boot files, restore original 5.0.2 nand? :)

Or do I need blank boot files for 5.0.2?
If you're on 5.1.0, you can just generate the BOOT files on your PC with ChoiDujour. Sorry, I wasn't paying close attention.
 
If you're on 5.1.0, you can just generate the BOOT files on your PC with ChoiDujour. Sorry, I wasn't paying close attention.
I have tried for two days to generate my 5.0.2 boot files :D
And I seriously don't get it. Have been following every guide I could fine, but I always hit a stop somewhere.
 

Site & Scene News

Popular threads in this forum