Hacking Need help to put my switch back to usable state

[mosse]

Hi people !
Like the title said, I need help to put my switch back to a usable state. After doing some (hazardous?) manipulations, it cannot boot any more.

The steps I had to arrive at the situation :

My switch is an old model.
I first played officially with it for some time. It was on 6.0.0 I think when I decided to buy the sx pro.
The hack went with no problem at all. I did not forget to first backup my NAND (using sxos) until some days ago when I decided to update the console firmware.
I updated to last sx os, then used choidujournx homebrew to update the switch.
The update seemed to go normally, until it rebooted, and never booted sx os CFW ever (could go to sxos startup menu, then only black screen).
After some unsecussful manipulations and researches, I decided to restore my NAND.
The restoration went well, and I was able to boot to OFW without any problem.
In OFW I connected to internet and (maybe the biggest error, don't judge!) updated the console officially to latest firmare (I believe 8.1.0, or at leas the latest 2 weeks ago).
I then retried booting sxos without more success.
After that I decided to try other hacks than sxos, and went to follow some tutorial ("the ultimate noob guide for hacking your nintendo switch) to install hekate/atmosphere/kosmos. Not really sure which terms stands for what, but I setup everything using sdsetup website to retrieve a complete package named "Kosmos Defaults".
So I started by putting back my NAND backup, and following the tutorial. Everything went as expected, until I try to boot the CFW and it does not work (details follow). Ultimately, I tried formatting my 64Gb SD card to FAT32 instead of exFAT with some found software, because Windows 10 won't allow this. This did not have any effect.

Here is the current status of the switch:

It's loaded with a 64Gb SD card, formated to FAT32, containing SD Setup stuff.
Without jig, it shows absolutely no life signs.
With jig, vol+ / power, it goes into rcm, and allows to inject payload using tegrarcmgui (windows). I inject hekate 4.10.1.
See a beautiful splashscreen, then arrive in the hekate menu.
choose "launch"
choose "CFW". => Found pkg1, found FSS Atmosphere 0.8.10..., ..., Loaded pkg1 & keyblob, Loaded warmboot and secmon, Failed to launch firmware.

Go back and try to activate (or desactivate?) autorcm :
choose "Tools"
choose "AutoRCM" => Failed to init eMMC.

Now I'm stuck and not sure what to try.
By the way I could backup my BIS keys using "biskeybump" which gave me a HWI string and a SBK string.

I'm looking forward for your help and will try anything, give any supplementary information to help unblock the situation.
I thank you all in advance for your help !
And, also, have a very nice day !

See you soon.

 

[mosse]

As far as I understand, maybe more concise steps would help :
- I backed up NAND originally when I was in 6.0.0
- Played with sxos for some months
- Went 6.0.0 -> 8.1.0 using choidujournx
- Could not boot CFW
- Restored NAND to 6.0.0
- Boot OFW and updated to 8.1.0 officially (and doing such, I assume, burning fuse, but how important is that?)
- Did not backup NAND at this point
- Was still not able to boot CFW, so went back to 6.0.0 with my NAND backup
- Was still not able to boot so tried to setup stuff using SD SETUP
- Still stuck in bootloader menu, not knowing what to do
Thanks.

 

[Hayato213]

As far as I understand, maybe more concise steps would help :
- I backed up NAND originally when I was in 6.0.0
- Played with sxos for some months
- Went 6.0.0 -> 8.1.0 using choidujournx
- Could not boot CFW
- Restored NAND to 6.0.0
- Boot OFW and updated to 8.1.0 officially (and doing such, I assume, burning fuse, but how important is that?)
- Did not backup NAND at this point
- Was still not able to boot CFW, so went back to 6.0.0 with my NAND backup
- Was still not able to boot so tried to setup stuff using SD SETUP
- Still stuck in bootloader menu, not knowing what to do
Thanks.

You should be able to boot CFW when you updated to 8.1.0, by using SX OS 2.8, as it support 8.1.0, reason it won't boot 6.0.0 while your fuse count is 10, you burnt too many fuse probably. You can try the latest Kosmos file.

 

[Lacius]

As far as I understand, maybe more concise steps would help :
- I backed up NAND originally when I was in 6.0.0
- Played with sxos for some months
- Went 6.0.0 -> 8.1.0 using choidujournx
- Could not boot CFW
- Restored NAND to 6.0.0
- Boot OFW and updated to 8.1.0 officially (and doing such, I assume, burning fuse, but how important is that?)
- Did not backup NAND at this point
- Was still not able to boot CFW, so went back to 6.0.0 with my NAND backup
- Was still not able to boot so tried to setup stuff using SD SETUP
- Still stuck in bootloader menu, not knowing what to do
Thanks.

Do the following steps in order:

1. Remove all traces of Atmosphere from your SD card.
2. Download the latest Atmosphere (atmosphere-0.9.2-master-6f85b11f, as of this post) and put the contents onto your SD card.
3. Download the latest fusee-primary (next to Atmosphere).
4. Boot your Switch using fusee-primary.

What happens?

 

[mosse]

1. Wiped SD card
2. The latest is actually 0.9.2 b0a66a6. I downloaded the zip and extracted to SD
3. Downloaded fusee-primary in 0.9.2 release to my PC
4. Put back the SD and feed switch fusee-primary with tegrarcmgui
5. got atmosphere blue splashscreen, then atmosphere B&W splashscreen then... hey hey the actual switch menu nice.

This says console is 6.0.0 (AMS 0.9.2).
Does this mean something was fixed in atmosphere super recently ?

Now I'm not quite sure how to go on with that. Is it time to follow a tutorial on how to update to 8.1.0 using choidujournx ?

Thank you for pointing what's next to do

 

[Lacius]

1. Wiped SD card
2. The latest is actually 0.9.2 b0a66a6. I downloaded the zip and extracted to SD
3. Downloaded fusee-primary in 0.9.2 release to my PC
4. Put back the SD and feed switch fusee-primary with tegrarcmgui
5. got atmosphere blue splashscreen, then atmosphere B&W splashscreen then... hey hey the actual switch menu nice.

This says console is 6.0.0 (AMS 0.9.2).
Does this mean something was fixed in atmosphere super recently ?

Now I'm not quite sure how to go on with that. Is it time to follow a tutorial on how to update to 8.1.0 using choidujournx ?

Thank you for pointing what's next to do

Your problem was caused by two things: Your fuses were too high, and you were using outdated versions of Atmosphere, etc. You can use ChoiDujourNX to update to 8.1.0 now.

Please make sure your Switch is kept offline (or you have 90DNS and/or Incognito installed) if you don't want to get banned.

 

[mosse]

Thank you. I'll try that and, hopefully, will get back with success feedback ! Got to go now see you later.

 

[mosse]

I was able to update to 8.1.0 using choidujournx. Also I installed kosmos from latest release of sdsetup, and this was a success (is it a good way instead of plain atmosphere ?)
Now I have a little problem because when trying to transfer nsp using goldleaf, it was veeeeeery slow (like 0.2M/s, so that I did not let it finish).
When cold booting, also, the payload might take ages to be pushed to switch...
Maybe suddenly my usb cable has a problem, or maybe the problem cause is because of the Zadig stuff... will take a look more carefully this evening.
Thx !

 

[mosse]

Juste tried with another cable this evening.
Working like a charm
Thanks all for your help !