Hacking Switch FOREVER stuck on 5.1- Need experts/devs to fix

[Philliyxx]

As a preface, I have read nearly every guide am active on discord and the forum I am not new to hacking my switch I know what I am doing. This is not a simple mistake of burnt fuses, sd card not formatted, custom theme, clear archive bits etc. Something is seriously wrong. with my switch. ALL OFW files have been downloaded from multiple reputable sites XBINS/thatdiscord/darth, etc.

I try to update every time a new OFW or CFW is released. I try fat32 and exfat. I try every combination of FW and CFW this is just getting tedious and beyond frustrating.

What I have

• Windows 10
• 256GB Sandisk
• 128 GB Sandisk
• 128 GB Samsung
• 9 Burnt Fuses (updated officially to 8.0.1 thinking it would solve problems)

• 4.1 clean NAND boot0/1 prodinfo -possibly corrupted I have tried to restore and can not get it to boot, even booting from Hekate and AMS bypassing fuse check since my fuses are burnt. OFW or CFW will not boo
  
• 5.1 nand boot 0/1 prodinfo
  

What works

• 5.1 NAND ReiNX 2.2.1 and Atmosphere 0.8.6-0.8.9 EVERYTHING JUST WORKS
  
• 7.1 ReiNX 2.2.1 GAMES UNDER SDK 2 AND MASTER KEY 1 ONLY WORK ANY HIGHER DO NOT AND FREEZE ON STARTUP, the switch logo bounces infinitely in the bottom right corner (all nsps work and are verified they work on 5.1 they are not corrupt) --No one in the discord could explain or believe why the patches wouldn't work right.

• 8.0.1 OFW at one point this booted when I updated officially, but no CFW would work that was supposed too.

What does not work

• 4.1 Choidujour
• 6.0 Choidujour
• 6.1 Choidujour
• 6.2 Choidujour/ChoidujourNX (0.8.7 / 2.2.1 - 2.4)
  
• 6.2 Mattytrog boot repair files
• 7.1 AMS 0.8.7 - 0.9.2
• 8.0.1 AMS 0.8.9 Atmosphere gets to Nintendo switch logo then fades to black right before booting but never does.
• 8.1 Newsest AMS and ReiNX

Desperate attempts

• Mattytrog repair package
• Nintendo system initializing before AND after using choidujour
• burning all my damn fuses updating officially to avoid choidujourNX
• ChoidujourNX system initializing every other time updating OFW
• formating SYS partition fat32 16k cluster via hackdiskmount
• deleting all but 000000120 system partition via hackdiskmount

 

[Mythical]

Did you replace signature patches after updating atmosphere also redumping keys for higher firmware (with lockpick iirrc)?
https://gbatemp.net/threads/i-heard-that-you-guys-need-some-sweet-patches-for-atmosphere.521164/
https://gbatemp.net/threads/lockpick-switch-key-derivation-homebrew.525575/

 

[Philliyxx]

All sig patches and keys.txt are up to date.

 

[Hayato213]

So does the 5.1.0 boot with the latest Kosmos build?

 

[marine5422]

I'm not sure that this is same, but I had very similar case on 3DS era.

https://gbatemp.net/threads/stuck-on-2-1-0-after-ctrtransfer-a9lh-weirdo-brick.460351/

In my case mostly due to NAND fat partition corruption or fragmentation. So I suspect this.
In order to fix it, Extracted the NAND, Manually decrypt the nand, Extract the all file manually.
Reformat the partition (and you may need to manually fix or backup/restore the partition header with hex editor, In my case I do.)
and inject all file manually again, then re-encrypt and inject NAND.
I know that it's different console, but It's could be same reason. At least it worth to try it.

Maybe this will be help to you.

 

[Hayato213]

I'm not sure that this is same, but I had very similar case on 3DS era.

https://gbatemp.net/threads/stuck-on-2-1-0-after-ctrtransfer-a9lh-weirdo-brick.460351/

In my case mostly due to NAND fat partition corruption or fragmentation.
In order to fix it. Manually decrypt the nand, extract the file.
Reformat the partition, and inject file manually again, then encrypt.

Maybe this will be help to you.

This is about switch not 3ds.

 

[marine5422]

This is about switch not 3ds.

I know. But it doesn't matter it is switch or 3ds, if NAND corrupted or fragramented. That's why I replied.
If you really carefully read my old article situation that I wrote before, you maybe notice that could be similar situation with OP's case.
(Can't update manually or had weird behavior or error on each FW system). At least it's not bad idea for OP.


And to OP: Check the inside every partition(Boot/Prodinfo/BCPkg/User whatever) if its any infinite loop folder or any cracked file system available. Maybe that's the key. (I guess...)

 

[Philliyxx]

So does the 5.1.0 boot with the latest Kosmos build?

5.1 does not. It only boots on atmosphere up to 0.8.9 the latest kosmos hangs on the switch logo

 

[Hayato213]

5.1 does not. It only boots on atmosphere up to 0.8.9 the latest kosmos hangs on the switch logo

Did you use Fusee-primary to boot instead of hekate?

 

[Philliyxx]

I tried fusee primary via tegragui and ruen hekate5.0 cfw and ofw boot options. I did not try to chainload fusee primary through hekate this go around as in the past it has not worked and I was already tired.

 

[Zonark]

Could you share a video of you attempting to boot into cfw?
You also have a boot0/1 backup correct?
I try a new emmc module as well personally like the 3ds guy said that you ever so kindly blew off it really sounds like the chip went out.

Also not all cfw work with all firmware you may need to get older versions of Hekate

 

[Philliyxx]

Could you share a video of you attempting to boot into cfw?
You also have a boot0/1 backup correct?
I try a new emmc module as well personally like the 3ds guy said that you ever so kindly blew off it really sounds like the chip went out.

Also not all cfw work with all firmware you may need to get older versions of Hekate

I didnt blow him off but i have yet to attempt his suggestion. I can get a video sure. what do you mean by chip went out?

Are not all the newest cfw supposed to work with every fw?

 

[Hayato213]

So what error you get when running the latest Kosmos?

 

[Philliyxx]

Latest kosmos gets stuck on the switch logo . O.8.9 will boot past it

 

[Hayato213]

Latest kosmos gets stuck on the switch logo . O.8.9 will boot past it

Latest should be able to boot if you push from fusee primary, set autoboot to fusee primary.

 

[Philliyxx]

Latest should be able to boot if you push from fusee primary, set autoboot to fusee primary.

I pushed fusee primary from tegragui and chainloaded it from hekate same result. it gets hung in the nintendo switch logo