Homebrew Question Cant restore backup

[jajamundo]

Ok! I try everything to restore my backup of 5.1.0 Nintendo Switch

I have a boot0.bin, boot1.bin and a rawnand.bin that I made with reinx

Now I want to restore it so I already try using SX OS and heatake 4.2. My switch is on 6.0.0

So someone could help me with this!! Thanks

What I'm doing wrong??

Edit: Yes my fuses count is 5 (it Means 4.0.0 and I really want 5.1).

 

[Draxzelex]

Did you put the boot0/boot1 and rawnand.bin files in the proper folder? Hekate auto-generates them when you run it; they need to be placed in the /restore/"eMMC serial number" folder

 

[Canna]

If you did not use the no burn fuse guide/method/ then you cannot downgrade from 6.0 so your 5.1.0 restore will not work. but if your using a fuse bypass check method then its fine

But then again you say your fuse count is 5, im guessing you checked that with bricc mii right ??

Your post is a Little confusing to which system you are or were on..

if you do have a fuse count of 5 then im guessing you made a backup of your nand, when you was using no burnfuse method on 5.1.0 system.. as u say u have a 5.1.0 backup and a fuse count of 5

Then if you still have the correct backup folder on your sd card ,

then you need to place boot 0,1 and rawnand.bin into the restore folder.

Backup/your emmc id/restore <<< place those files in restore folder..

if the boot0/1 was backed up when using the no burn fuse boot files/choidujour then it should still have auto rcm installed...


Please give us a little more information... what is the problem your having the error code ? what does it say on screen ? can you post a pic ...

ALSO Hekate only restores the rawnand.bin if the sd card is formatted to EXFAT

i dont think hekate restores boot0/1 if the filename has .bin in it i am not talking about the file extension..


rename to boot0 and boot1 instead of boot0.bin boot1.bin

But unless your wanting something thats on the 5.1.0 nand backup i would just use choidujourNX
And go back to 5.1.0 that way

 

[Draxzelex]

If you did not use the no burn fuse guide/method then you cannot downgrade from 6.0 so your 5.1.0 restore will not work.

It will work as long as he bypasses the fuse check with a bootloader that does so. However we don't have a way of patching the warmboot fuse check so he'll lose out on sleep mode.

 

[Canna]

It will work as long as he bypasses the fuse check with a bootloader that does so. However we don't have a way of patching the warmboot fuse check so he'll lose out on sleep mode.

Dude i know this ...i said if he hasnt used the no burn fuse method it will not work.
Meaning the fuse check bypass

 

[jajamundo]

Dude i know this ...i said if he hasnt used the no burn fuse method it will not work.
Meaning the fuse check bypass

Thanks for your help. I skipp the fuse method when I enter to RCM mode after upgrading my console. Just using a Jig and pressing the vol button. I checked with briccmii already and thats why I know that. The reason I want 5.0.1 instead of 4.0.0 os because I think my 4.0.0 is corrupted (is 28GB instead of 29GB). I'm going to burn fuses to 6 because I just want a clean 5.0.1 switch.

ALSO Hekate only restores the rawnand.bin if the sd card is formatted to EXFAT

i dont think hekate restores boot0/1 if the filename has .bin in it i am not talking about the file extension..


rename to boot0 and boot1 instead of boot0.bin boot1.bin

View attachment 146093

I think I'm gonna try this! I just gonna rename the boot0 and the boot1 to a non extansion file. I'm gonna give this a try when I get home.

Did you put the boot0/boot1 and rawnand.bin files in the proper folder? Hekate auto-generates them when you run it; they need to be placed in the /restore/"eMMC serial number" folder

Yes! I run hetake first in order to generate those folders and then paste my boot0.bin, boot1.bin and rawnand.bin. I think the problem is @Canna said about to rename the boot1 and boot0 to a non extension file.

 

[jajamundo]

I know I cant double post, but I Just wanna thanks you guys @Canna and @Draxzelex

Just downgrade my console. Rename the boot0 and boot1 and already burn fuses. So I'm on 5.1.0

Create my emuNand and just updated it to 6.0.0. Is time to figure out how to unlink sysnand and emunand. hanks you very much

 

[DocBo]

Hi, is it possible restore my nand backup with ChoiDujourNX?!
Because ChoiDujourNX accept only *.nca files right?!

 

[Canna]

Hi, is it possible restore my nand backup with ChoiDujourNX?!
Because ChoiDujourNX accept only *.nca files right?!

Choidujournx is not a backup or restore program...
Its basically a program that automates choidujour and lets you swap between system versions with ease..and or install exfat

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

I know I cant double post, but I Just wanna thanks you guys @Canna and @Draxzelex

Just downgrade my console. Rename the boot0 and boot1 and already burn fuses. So I'm on 5.1.0

Create my emuNand and just updated it to 6.0.0. Is time to figure out how to unlink sysnand and emunand. hanks you very much

Your welcome
Make a new backup of 5.1.0 but this time with hekate.

 

[jajamundo]

Your welcome
Make a new backup of 5.1.0 but this time with hekate.

Thanks! I already did with hetake and with SX OS menu before creating my emuNAND. Then made another Nand backup with the emuNand installed

 

[DocBo]

Choidujournx is not a backup or restore program...
Its basically a program that automates choidujour and lets you swap between system versions with ease..and or install exfat

I have tried to switch to a lower fw with Choidujournx on emuNAND but after the joycon logo blackscreen.

 

[Canna]

I have tried to switch to a lower fw with Choidujournx on emuNAND but after the joycon logo blackscreen.

black screen after choirdujour nx ,,, that is auto rcm... run your payload or hekate and launch cfw..

I do not mess with that messy emu nand so i dont think i can be much help

 

[DocBo]

black screen after choirdujour nx ,,, that is auto rcm... run your payload or hekate and launch cfw..

I do not mess with that messy emu nand so i dont think i can be much help

It boots up, nintendo splash, joycon splash, black screen.
But another question, what happens if i mess up the sysNAND and not able to boot up?!
Is it a unbrickable state?!
Or can i use hekate to restore my backup sysNAND?!