Hacking Question Blue Screen as soon as I press power button after downgrading firmware

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States
So I was having issues with 8.1 and booting any games, so I still had my nand backup of 6.2 and decided to downgrade using hekate. It was working OK, I turned the console off, took out my memory card to add some files to it, put it back in, pushed a payload to the console again, booted into CFW. It seemed ok, screen was dark so I figured it went to sleep, pressed power button and the Home screen came up, went into the dashboard and then the console went off and the blue screen came up. Is my console completely screwed now? I'm unable to send any payloads to it. As soon as I turn the console on(regular and dev way) it just goes directly to blue screen.

For the short period I had the console on with 6.2, my problem with launching games went away.

Is there any way I can fix this or did I brick my console?

thanks
 

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States


well I guess the fuses are off now, but I did use MY nand backup and not one I found online. Is my console bricked for good, or is there a way I can somehow upgrade back to my 8.1 nand backup?
 

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States
Nah. You just need to boot hekate. Get a fuse count and let us know what it is. Then we'll be able to better help you.

Also when you restored you nand did you also restore boot0 and boot1?
im having trouble getting into RCM though unfortunately, so im not certain i can get into hekate. i found another post on here where a user said to have the console plugged in, then turn it off and then turn it back on and he was able to send a payload. this isnt working for me though.

i did restore boot0 and boot1 with my nand.

thanks for your reply, any help or other ideas are greatly appreciated
 

Qubarf

Well-Known Member
Member
Joined
Dec 14, 2018
Messages
239
Trophies
0
Age
33
XP
967
Country
Pakistan
Interesting, boot0 and boot1 files are firmware specific, this is very contradictory to my experience!
I downgraded once and got this blue screen but luckily i had boot0 and boot1 files i was just able to flash them, boot via hekate to cfw and upgrade back?
Also didn't know there was a purple screen of death?!?!?!?
New stuff here folk. :)
 

Philliyxx

Well-Known Member
Member
Joined
Sep 21, 2018
Messages
304
Trophies
0
Age
36
XP
943
Country
United States
Was your 6.2 backup autorcm'd ever?

How are you trying to get into rcm? Maybe your jig pins have been bent over time and you need a new one.
 

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States
Was your 6.2 backup autorcm'd ever?

How are you trying to get into rcm? Maybe your jig pins have been bent over time and you need a new one.

my 6.2 firmware was not autorcm'd and i was thinking maybe my pins did bend, so i bought a new one last night and hoping that is the answer. i keep turning the switch on with the blue screen, it keeps coming on and shutting off relatively quick now as opposed to staying on constantly so i think im finally getting it to die.

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

Maybe your Switch is dead. Plug it in for about an hour or two. Then try it out.
i was at about 60 percent battery when it went blue, so i think its ok
 

smf

Well-Known Member
Member
Joined
Feb 23, 2009
Messages
6,640
Trophies
2
XP
5,854
Country
United Kingdom
my 6.2 firmware was not autorcm'd and i was thinking maybe my pins did bend, so i bought a new one last night and hoping that is the answer.

You bought a new what? Rails or JIG? Were you using autorcm on 8.1? If so then are you sure you're remembering how to get into RCM properly?
 

DuveltjeDG

Well-Known Member
Member
Joined
Apr 5, 2019
Messages
132
Trophies
0
Age
40
XP
844
Country
Netherlands
After downgrading whit choidujour it is put in autoRCM automatically I think. That could be the reason why you can't boot. If you left your switch alone for sometime the battery could be drained. Put your switch on the charger and wait minimum 2 hours. Then try to start your Switch with hekate as payload.
 
  • Like
Reactions: Philliyxx

Philliyxx

Well-Known Member
Member
Joined
Sep 21, 2018
Messages
304
Trophies
0
Age
36
XP
943
Country
United States
After downgrading whit choidujour it is put in autoRCM automatically I think. That could be the reason why you can't boot. If you left your switch alone for sometime the battery could be drained. Put your switch on the charger and wait minimum 2 hours. Then try to start your Switch with hekate as payload.

He said downgrade to 6.2 with hekate, so did not use choidujour. Should have said "restore"
 

eyeliner

Has an itch needing to be scratched.
Member
Joined
Feb 17, 2006
Messages
2,887
Trophies
2
Age
44
XP
5,522
Country
Portugal
What files did you restore?
RAWNAND.BIN? What about BOOT0.BIN and BOOT1.BIN?
Try to rebuild an 8.1 NAND. There's a guide for it somewhere around this forum.
 
  • Like
Reactions: Notnagel

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States
https://switchbrew.org/wiki/Panic_codes (This could possibly lead us in some direction)


Are we sure that BOOT0/BOOT1 did belong to the backup OP flashed? Since they DO relate to the FW Version, it could be som kind of Version mismatch oder Error while flashing them. Now, we have to wait for OP and if he manage to go into RCM.

100% sure, it was my original backup

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

What files did you restore?
RAWNAND.BIN? What about BOOT0.BIN and BOOT1.BIN?
Try to rebuild an 8.1 NAND. There's a guide for it somewhere around this forum.


Yes to all three BINs. I have a 8.1 nand build but like i said, i can't send a payload with tegra.

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

https://switchbrew.org/wiki/Panic_codes (This could possibly lead us in some direction)


Are we sure that BOOT0/BOOT1 did belong to the backup OP flashed? Since they DO relate to the FW Version, it could be som kind of Version mismatch oder Error while flashing them. Now, we have to wait for OP and if he manage to go into RCM.


I'm getting this color - 0x0000FF
 

CoolestGuy1234

Member
OP
Newcomer
Joined
Jul 14, 2019
Messages
11
Trophies
0
Age
36
XP
82
Country
United States
alright, i got a new jig and was able to get into rcm and was able to restore to my 8.1 nand. im able to launch into normal firmware but i cant seem to launch into cfw. i get t o the hekate menu and boot into atmosphere, the hekate logo comes back up and then the screen just goes dark. any ideas?
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://youtu.be/D9fLxKY8UQs?si=OFjLmB-QcLZLxjdM