Hacking Switch won't turn on after doing a NAND restore

balbalbilbil · Nov 21, 2018

Hi,

Can someone please help me. Switch won't turn on anymore after doing a restore via hekate. Please see details below for reference:

1.) Created full backup of BOOT 0/1 and RawNAND while on FW 5.1.0
2.) Accidentally updated OFW to 6.2.0
3.) Tried to restore to FW 5.1.0 via hekate using the 5.1.0 backup
4.) After restore was finished, turned off the power using "Power Off" option in hekate.
5.) Switch won't turn on anymore.

-tried connecting to PC to see if its in RCM mode but no luck, didn't enable AutoRCM either
-tried long pressing power button, no luck
-tried to enter maintenance mode, no luck

Help is very much appreciated. I think i just bricked my nswitch

TIA!

bananapi761 · Nov 21, 2018

Either the backup became corrupted, or the fuses no longer match due to the 2 different firmwares, causing it to stop booting. I'm unsure if there's a fix, not likely since you can't boot into ChoiDujourNX.

ExploitJunkie · Nov 21, 2018

Downgrading is only possible if you didn't burn fuses. Since you did it accidentally it's more than likely you burnt fuses. Go and look at your fuse count Hekate if you have 8 burnt fuses ...your hit.

jakkal · Nov 21, 2018

sorry you bricked your system man. but you definitely ignored everyone when they said do not restore nand if you blew your fuses
every day a thread gets created regarding this

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

ExploitJunkie said:
Downgrading is only possible if you didn't burn fuses. Since you did it accidentally it's more than likely you burnt fuses. Go and look at your fuse count Hekate if you have 8 burnt fuses ...your hit.

i wouldnt even recommend checking his burnt fuse

im 100% sure he burnt them all with the 6.2 update

RIP

Abespada · Nov 21, 2018

Downgrading is possible with burnt fuse, but you have to bypass fuses check using CFW. I'm pretty sure that your switch is not bricked at all. Even if you completely fucked your NAND, you can still boot payloads like hekate bootloader or SX bootloader. Just do that (with the joy con jig and a dongle/ USB C cable with your favorite payload injector) and boot in CFW (try Atmosphere/ReiNX or SX OS if you bought it) and I think you should be fine. If not, that means your NAND backup was corrupted and you're probably fucked.
After your switch booted in CFW, use ChoidujourNX to update or Nintendo servers (but I think that you'll probably be banned whatever)

balbalbilbil · Nov 22, 2018

UPDATE: Managed to boot into RCM

Yes I did burnt all of the demn 8 fuses as I've checked via Hekate.

Tried booting to Atmosphere CFW, got a black screen then after a minute it gave me an error: an error has occurred please contact Nintendo support

paulzheng · Nov 22, 2018

switch contain a function to prevent downgrade by efuse，
backup emmc boot0/1 and emmc sys is absolutely enough.

Creatable · Nov 22, 2018

Efuses don't match and you're on 6.2.0 which will basically kill your Switch. Most you can do is restore and try to update with the restored backup by going into CFW which ignores fuses

balbalbilbil · Nov 22, 2018

UPDATE: I've managed to boot and launch the switch via Stock and current version is on 5.1.0; tried launching to CFW and managed to boot in the system but I cannot access the homebrew application in the album as I'm getting the microsd system update pop up (can'tt access homebrew to go to Choidujour)

hatredg0d · Nov 22, 2018

balbalbilbil said:
UPDATE: I've managed to boot and launch the switch via Stock and current version is on 5.1.0; tried launching to CFW and managed to boot in the system but I cannot access the homebrew application in the album as I'm getting the microsd system update pop up (can'tt access homebrew to go to Choidujour)

use another sd card formatted to fat32 to run choidujour

balbalbilbil · Nov 22, 2018

hatredg0d said:
use another sd card formatted to fat32 to run choidujour

Thanks for that idea! I've managed to run choidujour and i can now boot in the system using exfat microsd. The only problem that I have now is that everytime I put the switch in sleepmode it crashes. Is it because of the burnt fuses? THanks for the help!

vastrolorde · Nov 22, 2018

balbalbilbil said:
Thanks for that idea! I've managed to run choidujour and i can now boot in the system using exfat microsd. The only problem that I have now is that everytime I put the switch in sleepmode it crashes. Is it because of the burnt fuses? THanks for the help!

Same thing just happened to me bacause i was trying the switch lan-play or something, though i have 90dns input on my dns settings, the switch updated the firmware. i thought that 90 dns prevents the system to connect on nintendo servers?, anyway my bad.. But how di you managed to boot it up on cfw again? i have 6.1 NAND backup. i dont know where to start. im afraid ill just brick my switch in the process if i restore my 6.1 nand backup..

balbalbilbil · Nov 22, 2018

vastrolorde said:
Same thing just happened to me bacause i was trying the switch lan-play or something, though i have 90dns input on my dns settings, the switch updated the firmware. i thought that 90 dns prevents the system to connect on nintendo servers?, anyway my bad.. But how di you managed to boot it up on cfw again? i have 6.1 NAND backup. i dont know where to start. im afraid ill just brick my switch in the process if i restore my 6.1 nand backup..

Hi Vastrolorde,
Out of desperation I guess haha. Basically what I did was:

1.) Boot into RCM (the most difficult part for me as I do not have a proper jig)
2.) Did another restore from my clean 5.1.0 backup (BOOT0/1 and rawnand)
3.) Formatted my microSD to FAT32 and added Choidujour (As Im being prompted for an update)
4.) Launched CFW via Hekate (I'm using Atmosphere)
5.) Added Exfat support by installingg 5.1.0 NCAs using Choudjour (I also updated to 6.1.0 since I'm already in there)
6.) Reboot to RCM
7.) Formatted the microSD back to exfat, re-extracted the sdfiles again
8.) Launch CFW then I've managed to bring my switch back alive again and currently running FW 6.1.0

Although I've already burnt out all of my fuses and there still the sleep mode crash issue due to fuses, switch is still operable and I'm currently playing my games right now

vastrolorde · Nov 22, 2018

balbalbilbil said:
Hi Vastrolorde,
Out of desperation I guess haha. Basically what I did was:

1.) Boot into RCM (the most difficult part for me as I do not have a proper jig)
2.) Did another restore from my clean 5.1.0 backup (BOOT0/1 and rawnand)
3.) Formatted my microSD to FAT32 and added Choidujour (As Im being prompted for an update)
4.) Launched CFW via Hekate (I'm using Atmosphere)
5.) Added Exfat support by installingg 5.1.0 NCAs using Choudjour (I also updated to 6.1.0 since I'm already in there)
6.) Reboot to RCM
7.) Formatted the microSD back to exfat, re-extracted the sdfiles again
8.) Launch CFW then I've managed to bring my switch back alive again and currently running FW 6.1.0

Although I've already burnt out all of my fuses and there still the sleep mode crash issue due to fuses, switch is still operable and I'm currently playing my games right now

what cfw are you using right now? have you updated your hekate sd files to the latest?
i fixed my sleep crash issues by updating the hekate files. 10.1 i believe. your lucky men.. your switch booted up even though all fuses were burnt? and technically downgrading. didnt know it was possible.

balbalbilbil · Nov 22, 2018

vastrolorde said:
what cfw are you using right now? have you updated your hekate sd files to the latest?
i fixed my sleep crash issues by updating the hekate files. 10.1 i believe. your lucky men.. your switch booted up even though all fuses were burnt? and technically downgrading. didnt know it was possible.

Currently I'm using the latest CFW Atmosphere that came in by default in the KOSMOS package and yes sadly I'm already on hekate 4.2 but still no luck with regards to the sleeping crash.

I was surprised myself. I already lost hope last night but still tried this morning and Im glad I did try.

I guess desperate measures at desperate times

tikanot · Nov 22, 2018

hi have same mistake but before power off i start cfw and switch work. but after power off impossible To power on and impossible to launch rcm pc not reconized it. how do you do To rcm work again. i have downgrade 6.2 To 6.0 with boot0/1 and partition

Creatable · Nov 22, 2018

tikanot said:
hi have same mistake but before power off i start cfw and switch work. but acter power off impossible To power on and impossible to launch rcm pc not reconized it. how do you do To rcm work again. i have downgrade 6.2 To 6.0 with boot0/1 and partition

I have no idea as to what you're talking about, but downgrading soft bricks you

tikanot · Nov 22, 2018

balbalbilbil do same thing and his switch work. i dont have read that rcm is impossible after downgrade. but yes ofw nit work because of burn fuse

tnnuy · Nov 22, 2018

the console can only start in rcm, it will always remain in black screen

tikanot · Nov 22, 2018

i try rcm but computer dont see the switch

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

switch work again in rcm. i have wait one hour. how To delete update in waiting? and block update. it s my children do update 6.2

tnnuy · Nov 22, 2018

I had this problem, I was not able to put it in rcm mod, after the console fell asleep, try to make sure that everything goes well to enter the rcm mod, try to power 12 or 30 seconds

Hacking Switch won't turn on after doing a NAND restore

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Similar threads

Popular threads in this forum