Hacking Question Help recover switch without BOOT0/BOOT1 backups

  • Thread starter Thread starter simon66
  • Start date Start date
  • Views Views 26,065
  • Replies Replies 31
I need feedback as to if it is working for people, or how I can streamline the process.

Tried to re-build 6.2 FW, it didn't work for me, I've never been able to get 6.2 working. At the boot Fusee.primary step I got NXBOOT Error: Failed to derive keys.
When I tried to run biskeydump my keyblobs were corrupted. I restored the proper boot 0 and 1 not the key_killer versions.
I had already dumped my biskeys from 5.1 so I used those to mount with hackdisk prior FYI

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

Tried to re-build 6.2 FW, it didn't work for me, I've never been able to get 6.2 working. At the boot Fusee.primary step I got NXBOOT Error: Failed to derive keys.
When I tried to run biskeydump my keyblobs were corrupted. I restored the proper boot 0 and 1 not the key_killer versions.
I had already dumped my biskeys from 5.1 so I used those to mount with hackdisk prior FYI

*Edit* I actually flashed the key_killer versions when I was on 7.X but I got OFW booting, and ReiNX 2.2.1 / Atmosphere 0.8.9 would not boot. ReiNX will only load NSPS with masterkey rev 2-3 or lower, all other games just hang on the first load splash with nintendo switch in bottom right, its very odd...

I decided to choidujourNX back to 6.2 everything went fine, but no CFW would boot or OFW, thus I tried your boot_repair package again.
 
Last edited by Philliyxx,
Tried to re-build 6.2 FW, it didn't work for me, I've never been able to get 6.2 working. At the boot Fusee.primary step I got NXBOOT Error: Failed to derive keys.
When I tried to run biskeydump my keyblobs were corrupted. I restored the proper boot 0 and 1 not the key_killer versions.
I had already dumped my biskeys from 5.1 so I used those to mount with hackdisk prior FYI

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



*Edit* I actually flashed the key_killer versions when I was on 7.X but I got OFW booting, and ReiNX 2.2.1 / Atmosphere 0.8.9 would not boot. ReiNX will only load NSPS with masterkey rev 2-3 or lower, all other games just hang on the first load splash with nintendo switch in bottom right, its very odd...

I decided to choidujourNX back to 6.2 everything went fine, but no CFW would boot or OFW, thus I tried your boot_repair package again.

Did you have a BOOT0/BOOT1 backup already? I tried flashing the blank BOOT0/BOOT1 (for FW 6.2) and my switch still wont get passed the reswitched logo.
I don't know if this is possible or not, but is there a way to rebuild my NAND? I tried following this tutorial here (https://guide.sdsetup.com/usingcfw/manualchoiupgrade) to install both 5.1 and 4.1 and I still get a black screen.
 
Thanks for the help :)
I have the file but looks like the lowest firmware it was is 6.2.0 (which is not supported by ChoiDujoir). Going to look around and see how I can manually get this to work on 6.2.0

Im slowly making progress. Looks like this unit might not be a gonner after all.
I got the similar situation like you, I've been followed the scene quite sometime now especially with anythings relate to "mattytrog" comments for a while after I brick my switch and try to rebuild the firmware. I can't pm him for the password of the filed ( BOOT_REPAIR_PACKAGE_iha2 ). my account haven't reach that PM feature yet. TT
 
Can somebody pm or mail the psw for opening those files? completely stuck and my son offcourse wants to play his switch in the vacation. Thanks in advance!
 
Last edited by BGabriels,
I bought a used bricked switch without any backup, so I'm trying to fix it.
 
@mattytrog
could you pm me the password as well? had a corrupted emmc that bootloop to switch logo with no rcm mode available, got new emmc chip but lost my boot files. but now i can get into rcm
thanx in advance
 
my problem is that I do not know what firmware other than hekate and atmosphere is on my switch. i bought it used, supposedly bricked but was stuck in autorcm. Hekate loads fine, version 5.1.1, if I remember correctly. Atmosphere is version 0.8.9 i think. The OFW, I haven't a clue where to find that information. It could be the whole reason it is bricked. I tried Nevercholt Tech's Remove Custom Firmware tutorial on the Tube, but it didn't work. @mattytrog would your rebuild help me in this situation?
 
my problem is that I do not know what firmware other than hekate and atmosphere is on my switch. i bought it used, supposedly bricked but was stuck in autorcm. Hekate loads fine, version 5.1.1, if I remember correctly. Atmosphere is version 0.8.9 i think. The OFW, I haven't a clue where to find that information. It could be the whole reason it is bricked. I tried Nevercholt Tech's Remove Custom Firmware tutorial on the Tube, but it didn't work. @mattytrog would your rebuild help me in this situation?

You can find your FW version from these tools. Could be as simple as updating atmosphere if the official firmware is 9 or higher, I think 0.8.9 doesn't support 9+

https://github.com/eliboa/NxNandManager
https://gbatemp.net/threads/firmware-version-inspector-get-fw-version-from-nand-dump.515308/
 
Last edited by Philliyxx,

Site & Scene News

Popular threads in this forum