Hacking Question I need help.

[Psychoticgamer92]

So long story short. I made a nand backup of 6.1.0. My girl updated the system to 6.2.0. So I went in to restore my old nand and boot 0/1 and when I tried to restore the raw nand gpp and I got the error the size is different than the sd card. But the boot 0/1 worked and now my switch wont boot at all. Any fix to this? I can still access rcm.

 

[M7L7NK7]

Everyone's girlfriends are doing this a lot lately

 

[Psychoticgamer92]

Everyone's girlfriends are doing this a lot lately

Lmao that's a damn shame because after she did it I just went out and bought her her own switch lmao

 

[AmandaRose]

Everyone's girlfriends are doing this a lot lately

Yep as I have said in other threads nobody ever admits they fucked up its much easier to blame the girlfriend or a little brother.

 

[sansnumen]

So long story short. I made a nand backup of 6.1.0. My girl updated the system to 6.2.0. So I went in to restore my old nand and boot 0/1 and when I tried to restore the raw nand gpp and I got the error the size is different than the sd card. But the boot 0/1 worked and now my switch wont boot at all. Any fix to this? I can still access rcm.

Uh I think you just bricked. FW 6.2 requires 8 burnt fuses, while FW 6.1 requires 7 burnt fuses. You restored FW 6.1. Your switch expected 7 burnt fuses, but saw 8 instead, so it panicked. Can you boot the recovery menu by any chance?

 

[Psychoticgamer92]

Yep as I have said in other threads nobody ever admits they fucked up its much easier to blame the girlfriend or a little brother.

I have no problem admitting if I fuck up. Clearly I fucked up resoring boot 0/1

 

[comput3rus3r]

"my girflriend/brother/dog/friend/evil twin/insert anybody else but me here updated to 6.2..."

somebody did predict this the day 6.2 released. I forgot who though.

 

[Psychoticgamer92]

Uh I think you just bricked. FW 6.2 requires 8 burnt fuses, while FW 6.1 requires 7 burnt fuses. You restored FW 6.1. Your switch expected 7 burnt fuses, but saw 8 instead, so it panicked. Can you boot the recovery menu by any chance?

Unfortunately not. I've tried a few times now.

 

[sansnumen]

Unfortunately not. I've tried a few times now.

You can still boot your system using Hekate bootloader found here https://github.com/CTCaer/hekate.

You can use Hekate to boot into a CFW. See if you can get that to work.

 

[Psychoticgamer92]

You can still boot your system using Hekate bootloader found here https://github.com/CTCaer/hekate.

You can use Hekate to boot into a CFW. See if you can get that to work.

I tried booting into reinx and I get some package error.

 

[sansnumen]

I tried booting into reinx and I get some package error.

Does Atmosphere boot?

 

[stephrk398]

Everyone's girlfriends are doing this a lot lately

And a new meme was born. So long to all the uncles working at nintendo.

 

[Psychoticgamer92]

Does Atmosphere boot?

Nope I get failed to decrypt the package2 header (master ke"y revision 5)"

 

[sansnumen]

Nope I get failed to decrypt the package2 header (master ke"y revision 5)"

Are you sure you are using Atmosphere v0.8.1? There was a person with the same issue on the github bug page for Atmosphere, and it seems the issue was fixed for that person.

 

[Psychoticgamer92]

Are you sure you are using Atmosphere v0.8.1? There was a person with the same issue on the github bug page for Atmosphere, and it seems the issue was fixed for that person.

I am using 0.8.1. I used brisket to get my keys on the sd card too

 

[sansnumen]

I am using 0.8.1. I used brisket to get my keys on the sd card too

The only other things I can think of is that either your boot0/boot1 restore did not work, or your backup of boot/boot1 are themselves corrupted.

 

[Psychoticgamer92]

The only other things I can think of is that either your boot0/boot1 restore did not work, or your backup of boot/boot1 are themselves corrupted.

The console only fucked up after I hit restore boot0/boot1 so I assume that's what messed up the console.

 

[bodefuceta]

Did you make a backup before restoring? Should be easier to just revert to that and use atmosphere which does support 6.2. If not I think you'll have to go through this guide to get your your firmware back in tact, but you might want to wait someone more knowledgeable to answer.

 

[sansnumen]

The console only fucked up after I hit restore boot0/boot1 so I assume that's what messed up the console.

You can try restoring boot0/boot1 again and see if Atmosphere boots. If not, I think that means your boot0/boot1 backup files are corrupted. I don't know what else to tell you.

 

[bodefuceta]

So you have 6.2 nand but ealier boot0/1, if they're incompatible it's what stopped your console from booting. Since you can't restore the previous nand, you should backup the current one and keep it safe too, maybe you'll need to recover from that.