Hacking Switch won't boot after NAND restore

  • Thread starter Thread starter Ragone
  • Start date Start date
  • Views Views 3,754
  • Replies Replies 4

Ragone

Well-Known Member
Newcomer
Joined
Mar 25, 2006
Messages
66
Reaction score
0
Trophies
1
Website
Visit site
XP
178
Country
United States
So, my switch was on 6.2, and I installed a game not knowing it was 7.0, it flagged all my games as requiring an update before installing. I checked my settings, still 6.2

-Restored my NAND backup, which I later found out was 4.1 stupidly, now the system does not power on. Attempting to connect to system via USB, via usb to payloader, no lights or anything. Can't seem to get into Hekate. Is this thing done now?
 
So, my switch was on 6.2, and I installed a game not knowing it was 7.0, it flagged all my games as requiring an update before installing. I checked my settings, still 6.2

-Restored my NAND backup, which I later found out was 4.1 stupidly, now the system does not power on. Attempting to connect to system via USB, via usb to payloader, no lights or anything. Can't seem to get into Hekate. Is this thing done now?

i suppose that you should replace a old kosmos version named sdfiles on to SD card, also inject a old hekate.bin to active cfw working which are all compatible with official 4.1 firmware

actually the console is power on but efuse is incorrect. cause black screen. so you have to use jig let it get into RCM.

hold on power button around 12 seconds. then make it into RCM
 
Last edited by paulzheng,
So, I was able to get it booted with the jig and dongle, my NAND backup is 4.1.

However, per hekate my burnt fuses indicate 6.2. Is there a way of booting Hekate to bypass and update via the official method and grab 6.2 to create a new NAND? Or is it screwed?
 
Last edited by Ragone,
Real question is why did you restore your nand? This seems like a problem that can easily be solved without doing that.
 
So, I was able to get it booted with the jig and dongle, my NAND backup is 4.1.

However, per hekate my burnt fuses indicate 6.2. Is there a way of booting Hekate to bypass and update via the official method and grab 6.2 to create a new NAND? Or is it screwed?
You don’t need to update official. Boot over hekate to 4.1, update with ChoiDujourNX to 6.2 and enjoy. And now keep your fuses with AutoRCM. Backup of 4.1 is nice but useless if you don’t keep your fuses count to 4.1...
 

Site & Scene News

Popular threads in this forum