Hacking Restored old NAND before downgrading firmware need help

[wither3211]

So i made a mistake restored nand through Hekate 3.2 before having downgraded back to original firmware. The NAND was from 4.1.0 and i was in 5.1.0. I don't have any other Nand backup than the 4.1.0. I still have Auto-RCM (updated thru ChoidujourNX) and can still boot into Hekate.bin or SX OS loader, etc, but i do get a blue screen when trying to enter CFW proper. Is there anyway i can repair the damage i've done?

Reading some other threads i've managed to dump my biskeys into a keys.txt, but launching Choidujour has been tricky (it keeps closing on me, despite having downloaded the c++ visual studio, and HacDiskMount tells me "Integrity engine error" and missing MSCVP140.dll, so that won't run either).

 

[DarthItachiX]

So i made a mistake restored nand through Hekate 3.2 before having downgraded to the backus original firmware. The NAND was from 4.1.0 and i was in 5.1.0. I don't have any other Nand backup than the 4.1.0. I still have Auto-RCM and can still boot into Hekate.bin or SX OS loader, etc, but i do get a blue screen when trying to enter CFW. Is there anyway i can repair the damage i've done?

Reading some other threads i've managed to dump my biskeys into a keys.txt, but launching Choidujour has been tricky (it keeps closing on me, despite having downloaded the c++ visual studio, and HacDiskMount tells me "Integrity engine error" and missing MSCVP140.dll, so that won't run either).

If you updated to 5.1.0 without using ChoiDujourNX you burned fuses so your 4.1.0 backup will no longer work and to get your keys use kezplez .. https://github.com/shchmue/kezplez-nx/releases

 

[wither3211]

If you updated to 5.1.0 without using ChoiDujourNX you burned fuses so your 4.1.0 backup will no longer work and to get your keys use kezplez ..

thanks a bunch for responding! I updated to 5.1.0 with ChoiDujourNX, so auto-rcm is enabled. I just checked and my fuse burn count is 5. my problem is that while i can boot into sx os or hekate via dongle, i can't get into the cfw without a blue screen of death happening.

 

[DarthItachiX]

thanks a bunch for responding! I updated to 5.1.0 with ChoiDujourNX, so auto-rcm is enabled. I just checked and my fuse burn count is 5. my problem is that while i can boot into sx os or hekate via dongle, i can't get into the cfw without a blue screen of death happening.

Does your console boots to OFW ??? If so restore to factory default and try again.

 

[wither3211]

Does your console boots to OFW ??? If so restore to factory default and try again.

I could try, since i didn't want to burn my fuses i've only ever logged into ReiNX and SXOS since updating to 5.1.0. I haven't logged into Horizon since then. Would that be the best option? I mean,even if i end up burning fuses 5.1.0 is way better than having to buy a new Switch.

 

[DarthItachiX]

I could try, since i didn't want to burn my fuses i've only ever logged into ReiNX and SXOS since updating to 5.1.0. I haven't logged into Horizon since then. Would that be the best option? I mean,even if i end up burning fuses 5.1.0 is way better than having to buy a new Switch.

You wont burn fuses as long as you dont update thru normal update. Restoring just will clear your console and will stay at your current firmware.

 

[wither3211]

You wont burn fuses as long as you dont update thru normal update. Restoring just will clear your console and will stay at your current firmware.

Okay, so trying to boot into OF via sx os dongle also results in a blue screen.

To recap what i've managed to do so far. A) booting into SX OS Loader and B) from there going into hekate, and dumping my keys thru Biskeydump.bin. I can't boot into ReiNX, SX OS, or Original Firmware from there. All result in a blue screen.

 

[DarthItachiX]

Okay, so trying to boot into OF via sx os dongle also results in a blue screen.

To recap what i've managed to do so far. A) booting into SX OS Loader and B) from there going into hekate, and dumping my keys thru Biskeydump.bin. I can't boot into ReiNX, SX OS, or Original Firmware from there. All result in a blue screen.

You don't need the dongle to boot into OFW. Just turn off AutoRCM with Hekate and use it to restore your backup once again. Once you boot with AutoRCM off and with you backup restored you should boot straight into OFW.

 

[nero99]

dont Forget you need the boot0 and boot1 files for 4.1 in order to “boot” into HOS.

 

[wither3211]

You don't need the dongle to boot into OFW. Just turn off AutoRCM with Hekate and use it to restore your backup once again. Once you boot with AutoRCM off and with you backup restored you should boot straight into OFW.

okay,i'm going to try this. Thanks for sticking with me, man! Okay so i did it. Result was light teal/green screen.

dont Forget you need the boot0 and boot1 files for 4.1 in order to “boot” into HOS.

Okay i have the boot0 and boot1 files for 4.1, since that was the only nand backup i had, do i restore the rawbin as well or just those (when i tried to downgrade is think i restored eMMC RAM GPP (exfat only) as well? i tried with just the boot0 and boot1 and was welcomed with a light teal/green screen.

 

[Bst22322]

So do you have to downgrade before restoring nand backup?

 

[DarthItachiX]

okay,i'm going to try this. Thanks for sticking with me, man! Okay so i did it. Result was light teal/green screen.


Okay i have the boot0 and boot1 files for 4.1, since that was the only nand backup i had, do i restore the rawbin as well or just those (when i tried to downgrade is think i restored eMMC RAM GPP (exfat only) as well? i tried with just the boot0 and boot1 and was welcomed with a light teal/green screen.

You have to restore to full rawbin file that its around 29GB.

 

[wither3211]

You have to restore to full rawbin file that its around 29GB.

my rawnand.bin is split into 14 parts. I'm assuming i have to join them right? Not sure how to go about that. Man, the more this goes on the less self confident i'm becoming. I've been following directions to the letter though, so hopefully this resolves itself soon. Thanks again!

 

[DarthItachiX]

my rawnand.bin is split into 14 parts. I'm assuming i have to join them right? Not sure how to go about that. Man, the more this goes on the less self confident i'm becoming. I've been following directions to the letter though, so hopefully this resolves itself soon. Thanks again!

Check this thread it might help you with your rawnand.bin been splitted ... also format your microsd to exfat to be able to put the 29gb rawnand.bin file without splitting ... https://gbatemp.net/threads/joiner-...share_tid=515435&share_fid=27398&share_type=t

Sent from my SM-T810 using Tapatalk

 

[wither3211]

Check this thread it might help you with your rawnand.bin been splitted ... also format your microsd to exfat to be able to put the 29gb rawnand.bin file without splitting ... https://gbatemp.net/threads/joiner-...share_tid=515435&share_fid=27398&share_type=t

Sent from my SM-T810 using Tapatalk

It worked! Man, you're a fucking god. You didn't need to hang in there and help me so much but ya did. Much appreciated. Thanks.

 

[paulzheng]

Does your console boots to OFW ??? If so restore to factory default and try again.

autorcm is not allow get into ofw system. the console only boot into cfw from microsd card

 

[XaneTenshi]

autorcm is not allow get into ofw system. the console only boot into cfw from microsd card

Not true. The "stock" setting in Hekate is pretty much Official Firmware. The only thing it does is skip the fuse count and that happens before the Switch boots the firmware, so...It's still Official Firmware.