Hacking Need Help - Blue Screen when using Hekate/TegraRcmGUI

  • Thread starter Thread starter shano
  • Start date Start date
  • Views Views 2,152
  • Replies Replies 2

shano

Well-Known Member
Member
Joined
Aug 27, 2012
Messages
272
Reaction score
183
Trophies
1
XP
2,458
Country
Australia
I went to restore my 1.0.0 split Nand backup from 6.1.0 i restored the BOOT0 & BOOT1 then went to restore NAND but had it in wrong folder so i turned off the Switch and moved it to correct folder and upon trying to go back to Hekate i get the Blue screen. =(

What can i do to fix this mess?

Edit: I was on 6.1.0 with no fuse burns.
Edit 2: Nevermind, had to use my Jig again lol.
 
Last edited by shano,
Restoring my 1.0.0 NAND now from 6.1.0. After thats done i assume it's ok to turn the Switch on normally without RCM/AutoRCM and it should be booting to 1.0.0 with no fuses getting burned on boot? Just wanna make sure everything goes fine.

I plan to setup Nebra & the EmuNAND stuff.
 
Restoring my 1.0.0 NAND now from 6.1.0. After thats done i assume it's ok to turn the Switch on normally without RCM/AutoRCM and it should be booting to 1.0.0 with no fuses getting burned on boot? Just wanna make sure everything goes fine.

I plan to setup Nebra & the EmuNAND stuff.
Yes once you've fully restored to 1.0.0 it will be safe to boot without autoRCM since you should only have 1 fuse burned. (The number it expects)

It will only ever burn fuses if you boot into a higher firmware without a custom bootloader that disables fuse r/w.
 
  • Like
Reactions: shano

Site & Scene News

Popular threads in this forum