Hacking Restore rawnand after updating

[raphzthename]

Quick question rawnand restore.

I followed these steps:
1. Used hekate to backup rawnand and boot0/boot1.
2. Updated from 4.0 to 5.1

I cannot actually remember if I updated before or after backing up my nand. Other than burnt fuses, is there anything else to look out for? Will I hit any issues going from 5.1 to 4.0 if my nand was backed up before updating?

For the restore process with sxos:
1. Move rawnand and boot0/boot1 to root of sd card.
2. Restore from sxos

Are the above steps correct?

 

[Draxzelex]

If the fuse count doesn't match the firmware, your console won't be able boot up normally. You can mitigate this by booting it into RCM and sending a payload/bootloader that bypasses the fuse check but once you do, your console will be unable to awaken from sleep mode.

Although I've never used SX OS to dump/restore the NAND (and I would sooner trust Hekate over SX OS when it comes to the NAND), those steps seem logical to me.

 

[raphzthename]

I would sooner trust Hekate over SX OS when it comes to the NAND

Thanks, I think I'm going the Hekate route. I've moved boot0/boot1 and my rawnand files to the sd card.

The restore options show:

• restore emmc boot0/1
• restore emmc raw gpp (exfat only)

Do I need to do both or will one of the options do a full restore?

 

[Draxzelex]

You need to restore both since boot0/boot1 are firmware-specific

 

[raphzthename]

You need to restore both since boot0/boot1 are firmware-specific

Thanks again. When I originally backed up my rawnand, it looks like it split it into multiple files. Hekate 4.2 seems to expect it in a single bin file. Is there any way for it to process the split files or what tool would you recommend to combine the files?

Edit: nm, looks like hekate includes a joiner script for just that purpose: https://github.com/CTCaer/hekate/releases