Is your console on the same firmware as the backup you made or did you update your console ??? Another thing .. is your backup splitted or is a full rawnand.bin of 29GB ..
Did you backup your boot0/boot1 after installing autoRCM? This looks to be your problem. Send the hekate.bin file again, and under tools, disable autorcm and your Switch will start booting just fine.
It honestly sounds to me like your "problem" isn't really an actual problem. Do you have AutoRCM installed? Because if so, your Switch will only boot to "black screen" as it is in RCM mode, in which case you HAVE to use hekate to boot it, that's intended behavior. Also, the "stock" setting in Hekate IS ofw. The only thing it does is skip the fuse check, which happens before the firmware is even booted, so it's still ofw.
If you didn't install AutoRCM, then you might have a problem, but otherwise, things are working as they should.
I don't have AutoRCM installed. I did backup the Boot0/1 and the NAND at the same time. I updated to the latest version of 6.0.1. I think the NAND might have been an older OFW version. Only way to get system working is to fiddle with the volume up/down and power button with RCM jig in place. I boot Hekate then use stock or payloader to get Switch working. When I turn off Switch and press power button to turn on doesn't work.
Check the fuse count with either Hekate and briccmii then check the firmware under System Settings.
I think 7 burned fuses corresponds to a 6.x firmware version, in which case you cannot boot a lower firmware version without using Hekate because you have burned too many fuses. Which version is the Nand backup that you did?
Actually I just saw that you said you upgraded to 6.0.1, so your fuse count checks out that way.
According to switchbrew the expected number of burnt fuses (retail OFW) for 6.0.1 is 7 (https://switchbrew.org/wiki/Fuses). It appears that your nand backup is for a lower FW and you somehow updated your NSW using the 6.0.1 OFW & this has burnt your fuses preventing you to downgrade. Maybe you need to be on the correct FW as your nand backup for the restore to happen. No one has mentioned this as far as I can see.
Last edited by proffk,
The NAND backup was 5.0.1. Same goes for the Boot0/1. When I did the restore, I noticed I couldn't turn on the system. So I played with the power/volume buttons. I put my payloader in and was able to get Hekate working. I ended up normally updated to 6.0.1 OFW via internet. Still running into turning the system power on as normal.
Edit: Briccmiiv2 showing all keys : PUBKEY CORRECT (NORMAL)! With updating to 6.0.1 did that update the Boot0/1?
Edit: Briccmiiv2 showing all keys : PUBKEY CORRECT (NORMAL)! With updating to 6.0.1 did that update the Boot0/1?
Last edited by brian007,
Did you ever figure this out? Im in the same boat. My switch is HAVING the same problem and I restored to backup before as well and my fuse count is 7
@Emeraldman94 he solved by updating offically but i recomand to Use ChoiDujourNX https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/
to update to 6.10 firmware and untick autorcm, after that make new backup for boot0,1 and nand.
to update to 6.10 firmware and untick autorcm, after that make new backup for boot0,1 and nand.
Last edited by Modificatorul,
Similar threads
-
Psionic Roshambo
-
K3Nv2
-
BigOnYa
-
Xdqwerty
what are you looking at?
-
-
-
@
Psionic Roshambo:
Technically for a month there I had Frontier FIOS 500Mbps and Spectrum 1Gbps (they got me on Spectrum because it was a little cheaper for double the speed)
-
-
@
BigOnYa:
I mean what would you really need that fast for tho, 500mb streams 4k fine. 1gb should be fine for 8k eventually. That's what I just switched to Spermrum.
-
-
-
-
@
Psionic Roshambo:
Might have only been like 7 bucks but thats like 84 dollars at the end of the year lol
-
-
-
-
-
-
-
-
@
BigOnYa:
Good, maybe she will leave me the f alone, now I can drink, smoke, and play my games in peace!+1
-
-
-
@
Psionic Roshambo:
As a reminder crack pipes left in the lobby will be thrown away, the DMV is not responsible for lost crack pipes!
-
-
-
-
-
