I was able to unbrick my console by entering the ReSwitched discord, sesrching in the switch-hacking-meta for a ncm save fix .kip, putting that kip in a newly created "kips" folder on the 16.0 Atmosphere folder, and then booting fusee.bin with emummc disabled
Here is the kip i mentioned, you need to boot atmosphere on sysnand for it to apply and unbrick the system
Not sure if maybe this will work for me. Maybe you can help. Where I currently sit: I had a 16.1.0 FW backup. After applying this, I can now boot into cfw atmosphere 16.1.0/s. My switch ofw sysnand is still 100% bricked (not even a Nintendo logo or even charge indicator when plugging it in). When booting without a jig, I have to hard reset still to turn it off. Just curious if what you posted here will work for me. I can boot into hekate and atmosphere 16.1.0. Currently just leaving my console not attached to any internet.
I will do everything possible to describe what I did to make it work both on ofw and cfw. It was janky, so be warned
downloaded the new releases of atmosphere, hekate, and 17.0.0 firmware. all of those can be found in the respective github pages. Followed switchbrew's latest update video, but applying the steps for the new atmosphere 1.6.0-prerelease, hekate 6.0.7 and the 17.0.0 update files. After all that, my cfw booted, but showing nonsigchk error, with press power button to continue. My ofw though, did not boot, and it switched my console off right after showing the nintendo logo. Tried a couple more times, with no success. Then I found Alan11780 and using the file and his guide, my ofw booted, but on system it was showing 17.0.0|AMS 1.6.0|E. Afraid of a ban, if my wifi connects, I intended to reboot, enable emummc, delete the kip file + folder, but before doing that, the switch crashed, showing some errors I could not see fast enough. After doing the above mentioned things: enabling emummc again, deleting the kip file + folder, my ofw FINALLY booted successfully, on the preinstalled 17.0.0, which I updated to accidently, hence my problems in the first place, and the cfw boots successfully on 17.0.0|AMS 1.6.0|E, but not without showing the nonsigchk error still. I suspect this is due to the lack of up-to-date sigpatches, as suggested by some old threads I've read regarding this error. So I rebooted 2-3 more times, both stock and cfw, and everything works now, but the process was indeed janky. Hope I helped somebody, and hope we get them sigpatches soon! Good luck to everyone.
I feel you bro! Read on another site people with no cfw, no homebrew unpatched switches having the same problem. Read only one comment saying they had no problem installing update 17 on theirs.
Got any links to that? It's serious if untouched Switches crashes
i couldnt fix my bricked switch with this. I copied the file in Atmosphere/kips/ncm_savefix.kip and try to boot atmosphere on sysnand. It shows nintendo logo and then black screen. If i select in "Launch" emunand it runs fine, so the switch it's fine, but the sysnand is bricked.
What I could understand after researching for a while looking for a way to unbrick my switch is that there is a new issue when updating to 17.0, apparently when you reset a switch trying to clean the NAND not everything gets erased, a single ncm save file with number 120 or whatever gets stored in the sysnand and that breaks the system when updating, what the .kip file that I sent does is erase that save file and it lets the system finally boot, for it to delete the file you must boot to Atmosphere in sysnand, it seems you keep booting to your emummc, that means the .kip file cleans your emummc but the sysnand stays the same, you need to disable the Emummc temporarily, launch fusee.bin into your sysnand with the .kip file inside a newly created "kips" folder in the atmosphere folder, then when you boot turn the console off fast if you are worried of a ban and delete the .kip file from the folder
If you havent try disabling emummc in Hekate and then launching the fusee.bin directly
Hi! I followed the MMC Rebuild section of the guide and was able to boot on Atmosphere and OFW. Lockpick RCM was not available so I used Picklock RCM instead. After confirming everything worked I went back to Hekate and switched AutoRCM to OFF then chose reboot OFW. linuxares is correct, if you follow the guide you won't lose your saves. Thank you so much!
