Hacking HELP! After restore NAND...I got blue screen of death, any idea how to fix it?

[darrenhuang22]

I tried to restore NAND based on my backup, it went smoothly till the end, then power off, click power button, then unfortunately blue screen...
Any idea how to fix it?

 

[darrenhuang22]

Digging around, here is more info on my case, could boot cfw, and burnt fuse number is 7 (upgraded the system to 6.1.0 before restoring but the NAND is based on 4.1.0) and unfortunately, I did not back up BOOT 0/1...

Is there still a way to save this?

 

[rksora]

i think you burn your fuses, i think there is no way to restore for now, i read from other post "dont listen grepoman"

 

[Taorn]

You can only boot your backup with a custom bootloader that ignores your fuses. You're probably trying to boot into OFW with the normal Nintendo bootloader.

So to fix your problem, you need to update back to 6.1.0. Alternatively you could always boot your Switch with a payload.

 

[aerios169]

you can updapte via choi to the actual version or just use hekate to launch cfw

 

[AndyGJorgensen]

With fuse count 7

You can only boot your backup with a custom bootloader that ignores your fuses. You're probably trying to boot into OFW with the normal Nintendo bootloader.

So to fix your problem, you need to update back to 6.1.0. Alternatively you could always boot your Switch with a payload.

This would be true if you had a nand backup with matching boot 0/1 to restore with it

 

[darrenhuang22]

With fuse count 7



This would be true if you had a nand backup with matching boot 0/1 to restore with it

hmmm, so no boot 0/1 backup here means no choice left?

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

you can updapte via choi to the actual version or just use hekate to launch cfw

If I do not have boot 0/1, can I still update it? and btw, when I try launch cfw, actually it got stuck...

 

[Kubas_inko]

-snip-

@darrenhuang22 I have no idea how to repair this, but you can always recreate your NAND using only prodinfo. But I have no idea how.

 

[chippy]

-snip-
The issue is that he burnt fuses to 6.10 but loaded a nand from 4.1 without boot 0/1 as well which are firmware version specific
His os try's to boot (4.1) but sees that fuses butt is 7 and is too high so it panics and locks up. Its Nintendo's way to stop downgrading.
If you use a bootloader (payload) that ignores this check it will boot but official firmware will not.
You can upgrade back to 6.1 and everything will be how it was and working

This is NOTHING to do with using sx os or not....

 

[Kubas_inko]

The issue is that he burnt fuses to 6.10 but loaded a nand from 4.1 without boot 0/1 as well which are firmware version specific
His os try's to boot (4.1) but sees that fuses butt is 7 and is too high so it panics and locks up. Its Nintendo's way to stop downgrading.
If you use a bootloader (payload) that ignores this check it will boot but official firmware will not.
You can upgrade back to 6.1 and everything will be how it was and working

This is NOTHING to do with using sx os or not....

Any payload nowadays bypasses the fuse count. Yet, he can't boot, so the problem is not that he is booting lower FW than his fuse count, but that, probably, he restored bad boot1/0 or he didn't restore those 2 at all or something just got messed up.

 

[Hexalform]

Can we please get back to helping this person <___<

I'm kind of interested to see if anyone finds a solution.

 

[mrdude]

-snip-

As for the OP - if you had a nand backup - restore from that, there's people on here who can help you recover in other ways, and there's already posts on how to fix your problem, try using the search button and reading through some older posts.

 

[a9lh-1user]

-snip-
@darrenhuang22 there are a member who know your problem and helped many people with it it's @rajkosto
maybe he knows a way to solve it.
If he is not answering in that thread try to PM him.

I think it would be possible to "ractivate" your switch ..... but i'am not sure

 

[chippy]

The op hasn't said if the issue is booting throu custom or official bootloader with this issue.

@op let us know if this happens when trying to boot cfw or just ofw

 

[Kubas_inko]

The op hasn't said if the issue is booting throu custom or official bootloader with this issue.

@op let us know if this happens when trying to boot cfw or just ofw

In both cases apparently, As he once said that he can't boot to CFW either.

and btw, when I try launch cfw, actually it got stuck...

 

[KHEOPS]

Shit!!! It sucks serious
I restored 6 times my nand with hekate without any problems, and now I see that...
I'm waiting for news from the op to find out more... I know that the backup nand reinx is not reliable, but I don't know what the op used for its backup..

 

[darrenhuang22]

The op hasn't said if the issue is booting throu custom or official bootloader with this issue.

@op let us know if this happens when trying to boot cfw or just ofw

So when I tried to boot the OFW, I got blue screen of death

Now if I load hekate and do launch CFW, it got stuck and the message reads as

"
Initializing...
Identified package1<`20180802162753`>
keyblob version 5

loaded package1 and keyblob
Decrypted and unpacked package1
Loaded wrmboot.bin and secmon
Read package2
"

 

[grepoman]

Try to reformat your sd card

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

Or try another sd card

 

[Kubas_inko]

So when I tried to boot the OFW, I got blue screen of death

Now if I load hekate and do launch CFW, it got stuck and the message reads as

"
Initializing...
Identified package1<`20180802162753`>
keyblob version 5

loaded package1 and keyblob
Decrypted and unpacked package1
Loaded wrmboot.bin and secmon
Read package2
"

Try redownloading SD files and use different fat32 (just to be sure) SD card.

 

[darrenhuang22]

Try redownloading SD files and use different fat32 (just to be sure) SD card.

Tried another SD card using fat32, booting CFW, same message, it seems this package2 is corrupted or broken?