Hacking Switch won't boot - pkg1 Loaded pkg1 & keyblob

[PabloZaiden]

I managed to get a 2nd switch with a completely nuked NAND and no backups.
Tried several potential solutions, but couldn't make any of those work. Best outcome I get are, either Nintendo logo and then black screen, or after flashing everything from an older firmware, first boot never actually boots.

Any ideas? So far it's a great Android / Linux tablet

 

[urherenow]

quick question: Have any of you tried actually using the safe mode to try updating/fixing firmware? I guess you wouldn't want to on an ipatched system, but otherwise, I still see trying to save fuses as pointless. CFW ignores fuses anyway, and you can do what you want with emummc. Also, a lot of the "black screen" problems people are getting on HOS 10+ are specifically because of using nogc patch.

 

[PabloZaiden]

quick question: Have any of you tried actually using the safe mode to try updating/fixing firmware? I guess you wouldn't want to on an ipatched system, but otherwise, I still see trying to save fuses as pointless. CFW ignores fuses anyway, and you can do what you want with emummc. Also, a lot of the "black screen" problems people are getting on HOS 10+ are specifically because of using nogc patch.

the unit isn’t patched. Can’t access safe mode. Don’t care about fuses.
What do you mean when you say that the black screen issues are because of the nogc patch?

 

[urherenow]

the unit isn’t patched. Can’t access safe mode. Don’t care about fuses.
What do you mean when you say that the black screen issues are because of the nogc patch?

if you're sure you can't get into safe mode, then nogc patch obviously isn't the issue.

But a lot of people have had issues with not booting (screen stays black after the logos) and they simply needed to turn off nogc in the config files. whether it be hekate_ipl.ini or the config for atmosphere. There was 1 other black-screen issue caused by installing certain nsp files, then not having proper patches for HOS 10. That should be a thing of the past now with sdsetup doing most of the work for people.

 

[PabloZaiden]

Also tried turning off the nogc patch. Same outcome: black screen.

 

[Canna]

I managed to get a 2nd switch with a completely nuked NAND and no backups.
Tried several potential solutions, but couldn't make any of those work. Best outcome I get are, either Nintendo logo and then black screen, or after flashing everything from an older firmware, first boot never actually boots.

Any ideas? So far it's a great Android / Linux tablet

You need prodinfo/prodinfoF, and biskeys To Recover this. Without those its brick for cfw or ofw switch .

Did you at least backup the switch in the state it was before you tried to fix it ? if not I feel you may have made the chance of recovery worse..

 

[PabloZaiden]

I have that backed up, but the original owner told me he had already messed that up anyway.
Ok then, it will be an amazing Android/Linux tablet until someone figures out how to boot horizon from a completely nuked emmc

 

[Canna]

I have that backed up, but the original owner told me he had already messed that up anyway.
Ok then, it will be an amazing Android/Linux tablet until someone figures out how to boot horizon from a completely nuked emmc

If only the original Owner made a backup before he or she fcked it up. Any old backup that worked will recover that switch, maybe you could contact them and see if such a thing exists.

 

[PabloZaiden]

He actually sold it because he didn’t have a backup

 

[SadSamurai]

I had the same issue. The fix was:
I used ChoiDejuour to convert Firmware 8.1.0 files to HacDismount file type with my prod.keys what I dumped with lockpick. Now It is working with atmosphere no stucking and no black screen after injecting the payload. The signature fail was only when I used other prod.keys file (from the internet). I had to use my own key file (from lockpick). After that every signature was OK.

 

[PabloZaiden]

Few questions:
- how did you use Choi on pc for 8.1.0? It support up to 6.1.0 afaik.
- did you also have an invalid prodinfo?

 

[PabloZaiden]

You should be able to get them from your console with lockpick_rcm

 

[Nex9]

Ok i followed the instructions and when I load the hekate and launch the FW i just get a message

"Initializing....

Identified package1 ('20170921172629')
Keyblob version 3

Loaded package1 and keyblob"

and it's stuck there....

 

[_bibi]

Hi,

I'm following the tutorial HelpRafi wrote but I always got a CMAC Signature (FAIL) when running bin\hactoolnet.exe -t save -k prod.keys NX-5.1.0_exfat\SYSTEM\save\8000000000000120...
Probably comes from the prod.keys I'm using (found them with google...) Is there any way somebody can provide me a working list of those keys? (like FXDX did previously)

Thanks so much!

 

[FXDX]

Hi,

I'm following the tutorial HelpRafi wrote but I always got a CMAC Signature (FAIL) when running bin\hactoolnet.exe -t save -k prod.keys NX-5.1.0_exfat\SYSTEM\save\8000000000000120...
Probably comes from the prod.keys I'm using (found them with google...) Is there any way somebody can provide me a working list of those keys? (like FXDX did previously)

Thanks so much!

you have PM

 

[Thundermofocat]

so.... i'm having a trouble, i have created a FW with my keys but the point is i can't open the "SYSTEM" and "USER" partitions because my biskeys doesn't match.

edit: my serial in prodinfo match , but my keys not

edit2: i have a blank nand (unbrick_pack (MATTYTROG)) but i no have any idea how i can insert my keys on nand with hacdiskmount if everytime says: FAIL entropy

 

[NEMAKARA168]

Hi,
I got the same issue, i follow everything carefully and repeatedly: bin\hactoolnet.exe -t save -k prod.keys NX-5.1.0_exfat\SYSTEM\save\8000000000000120... i still got CMAC Signature (fail). i use lockpick RCM to dump the prod.keys from my NS. I think something may be wrong. Anyway, what is FXDX Keys? Could you PM me?

Your helps is much appreciated.

Plz help, thanks you so much!

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

Hi,
I got the same issue, i follow everything carefully and repeatedly: bin\hactoolnet.exe -t save -k prod.keys NX-5.1.0_exfat\SYSTEM\save\8000000000000120... i still got CMAC Signature (fail). i use lockpick RCM to dump the prod.keys from my NS. I think something may be wrong. Anyway, what is FXDX Keys? Could you PM me?

Your helps is much appreciated.

Plz help, thanks you so much!

 

[FXDX]

Hi,
I got the same issue, i follow everything carefully and repeatedly: bin\hactoolnet.exe -t save -k prod.keys NX-5.1.0_exfat\SYSTEM\save\8000000000000120... i still got CMAC Signature (fail). i use lockpick RCM to dump the prod.keys from my NS. I think something may be wrong. Anyway, what is FXDX Keys? Could you PM me?

Your helps is much appreciated.

Plz help, thanks you so much!

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

you have PM