Hacking Switch possible Bricked. Doesnt work after NAND restore.

[kamakazi]

Ive done that. FLashing using Balena Etcher using the BOOT choi provides me. No luck. I try REINX Hekate atmosphere. No luck. Then I turn off ato RCM and retry all. Then try maintainence mode on all. No luck. Tried repairing GPT. no luck

How’d you manage to get into maintanance mode? I’m still having trouble getting to that point.

 

[Canna]

Ok start fresh

What system version was the backup.?

What was or is to your knowledge the system version you system is or was updated to now..?

I think you should restore your original rawnand backup and boot 0/1 to your switch
(if your backup is a lower system version then what you currently have on your system. then you have burnt more fuses then your backup and you will need to use hekate to bypass the fuse check to launch into ofw )

Once you reach the hekate main menu after restore .. You should launch into cfw
(making sure to have the required cfw files on your sd card)
Once into cfw You should run the ChoidujourNX and update the system to the current or same fuse count aka the system version that matches ya fuse count or the system version your switch is currently updated to...

You may use a payload called briccmii to check ya fuse count and check here for the system version your switch supports normally.

Good luck sir hope this helps you

 

[Emeraldman94]

Ok start fresh

What system version was the backup.?

What was or is to your knowledge the system version you system is or was updated to now..?

I think you should restore your original rawnand backup and boot 0/1 to your switch
(if your backup is a lower system version then what you currently have on your system. then you have burnt more fuses then your backup and you will need to use hekate to bypass the fuse check to launch into ofw )

Once you reach the hekate main menu after restore .. You should launch into cfw
(making sure to have the required cfw files on your sd card)
Once into cfw You should run the ChoidujourNX and update the system to the current or same fuse count aka the system version that matches ya fuse count or the system version your switch is currently updated to...

You may use a payload called briccmii to check ya fuse count and check here for the system version your switch supports normally.
View attachment 151813

Good luck sir hope this helps you

Thank you. The backup is 4.1 But my fuse count tells me Im at 6.1. I updated after my backup did some stuff. Week later the problem happened.

I tried to restore my original rawnand backu and BOOT0/1. Then I used hekate to bypass the fuse check and still get hung on switch logo. Loading REINX, ATmosphere is all no dice.

Ive even tried using choi computer to rewrite a BOOT0/1 and make some patches adn then flash it over to move to 6.1 or 4.1 again but that doesnt help

 

[Trunkz]

Thank you. The backup is 4.1 But my fuse count tells me Im at 6.1. I updated after my backup did some stuff. Week later the problem happened.

I tried to restore my original rawnand backu and BOOT0/1. Then I used hekate to bypass the fuse check and still get hung on switch logo. Loading REINX, ATmosphere is all no dice.

Ive even tried using choi computer to rewrite a BOOT0/1 and make some patches adn then flash it over to move to 6.1 or 4.1 again but that doesnt help

1. Copy off any data you would like to keep from your SD card if you havent already.
2. Delete all files off your SD card.
3. Copy over the latest Hekate release.
4. Copy over the latest Kosmos release.
5. Copy over the latest Choujodour release.
6. Copy over your NAND backup.
7. Copy over the firmware files for 6.1
8. Boot into Hekate; restore BOOT0/BOOT1. Then restore RAW GPP.
9. Still in Hekate; install AutoRCM.
10. Boot into Atmosphere now.
11. Using Choujodour; update to 6.1 ensuring you select exFAT when asked.
12. Profit!

 

[Canna]

1. Copy off any data you would like to keep from your SD card if you havent already.
2. Delete all files off your SD card.
3. Copy over the latest Hekate release.
4. Copy over the latest Kosmos release.
5. Copy over the latest Choujodour release.
6. Copy over your NAND backup.
7. Copy over the firmware files for 6.1
8. Boot into Hekate; restore BOOT0/BOOT1. Then restore RAW GPP.
9. Still in Hekate; install AutoRCM.
10. Boot into Atmosphere now.
11. Using Choujodour; update to 6.1 ensuring you select exFAT when asked.
12. Profit!

He has a 4.1 backup so would not be restoring 6.1

 

[Canna]

Thank you. The backup is 4.1 But my fuse count tells me Im at 6.1. I updated after my backup did some stuff. Week later the problem happened.

I tried to restore my original rawnand backu and BOOT0/1. Then I used hekate to bypass the fuse check and still get hung on switch logo. Loading REINX, ATmosphere is all no dice.

Ive even tried using choi computer to rewrite a BOOT0/1 and make some patches adn then flash it over to move to 6.1 or 4.1 again but that doesnt help

Suggest you make a duplicate of your 4,1 nand backup and your boot 0/1 for 4.1
Store the original some were safe..
Now with the copy of your rawnand and your boot 0/1,
I suggest you rebuild your nand to match your fuse count this can be done manually with hacdiskmount and your biskeys and fw of your choice in your case 6.1

There is a guide here that basically does this but with a different method.. if you follow the guide below
Loading your backup into hacdiskmount first then copy over the 6.1 files that you extract from nca into the hacdiskmount add your biskeys were you are told to do so... and use the newly generated boot0/1 files you get when extracting the fw...

Alot is explained in the guid im sure your figure it out . but please make a backup or a copy of your original 4.1 nand and boot0/1 you have now ..

Heres the guide good luck

>Rebuild with this guide click me<


also i would like to add that what was the original problem you faced...
If your unable to boot past the bootlogo/nintendo logo... After fixing nand/system files.
the other cause could be the power ic chip/battery ic...
Meaning that if you been unplugging/replugging the usbc mutiple times, or using a 3rd party dock, when the IC breaks it freezes you at the nintendo logo.. But if your charging ok chances are its just corrupt files...
\
Anyway... just throwing options and thoughts out there.. Suggest you rebuild.. take care