Hacking Blue screen :(

  • Thread starter Thread starter 3ds player
  • Start date Start date
  • Views Views 1,583
  • Replies Replies 4

3ds player

Active Member
Newcomer
Joined
Jan 22, 2014
Messages
31
Reaction score
3
Trophies
1
Age
56
XP
169
Country
United States
Ok, i shouldn't have attempt to restore my sysnand now.

I did the restore for eMMC BOOT0 & BOOT1 successfully, but failed at eMMC RAW GPP. The error was about the wrong file size. I power off the switch, and now it is blue screen, i can't send payload now.

Background - first backup using Reinx; second backup using Atom. The second backup is backup when the switch was already on CFW.

Henceforth, i decide to use first backup to restore the sysnand.

Any advice? thank you!
 
I had something similar happend to me.

The only thing that worked for me was:
Power the switch completly off, hold the power button for 15 seconds.
Put your Jig in.
Run Tegra and connect the Switch with your PC.
Turn the Switch on.

This way I could boot into RCM.

But unfortunately I can't really help you about your Nand backup erorr :(
 
I had something similar happend to me.

The only thing that worked for me was:
Power the switch completly off, hold the power button for 15 seconds.
Put your Jig in.
Run Tegra and connect the Switch with your PC.
Turn the Switch on.

This way I could boot into RCM.

But unfortunately I can't really help you about your Nand backup erorr :(

yes you are right. The auto rcm was broken. I have to use the jig to put console back to rcm, inject payload and active auto rcm again.

if I remembered correctly my console ofw was 4.1 and I have manually updated to 5.1 without burning fuse. The console would have never been able to switch on anyway.

And I only figured this out after successfully rebuilt the nand using ChoiDujourNX.

Biggest take out is I have grasped what and how the keys should be to rebuilt the nand if I ever need it.
 
yes you are right. The auto rcm was broken. I have to use the jig to put console back to rcm, inject payload and active auto rcm again.

if I remembered correctly my console ofw was 4.1 and I have manually updated to 5.1 without burning fuse. The console would have never been able to switch on anyway.

And I only figured this out after successfully rebuilt the nand using ChoiDujourNX.

Biggest take out is I have grasped what and how the keys should be to rebuilt the nand if I ever need it.
So you got it working again?
 

Site & Scene News

Popular threads in this forum