Hello, i did the same mistake yesterday. I was on the newest FM, but my Switch did't accept my exFat SD-Card.
Now my Switch didn't boot anymore. I can boot to RCM but when i try to boot the Nintendo FM, my Switch Display turn black.
I don't have any NAND backup. What can I do now to fix my problem?
It's currently not possible to restore a bricked Switch without a proper NAND backup from your own. The NAND has console-specific keys to get it working and restoring from another user's NAND backup isn't gonna help you either.
If you followed the OP's tutorial and/or messed with system files leading to this one black screen, your Switch will be bricked until a recover solution is made available (if it is going to).
Good luck with that one.
So you mean i destroyed my switch and it isn't possible to rescue it?
--------------------- MERGED ---------------------------
The only file i have safed before i did the tutorial is this one: BCPKG2-1-Normal-Main.bin
It's not possible to recover it only with this file, I'm afraid.
Your best bet is try to boot into CFW at least. Check your console version through RCM and try booting again into CFW compatible with your system (Atmosphere/ReiNX or SX OS) using a FAT32 formated SD.
If the screen keeps turing black after this process, it means your NAND is corrupted and the console is bricked.
*trumpvoice* WRONG!
no firmware comes with exfat as is.
nintendo has to pay royalties to microsoft for the exfat functionality. to save that money, they only ask you to install exfat once you put in a card that would usually require exfat format (anything over 32gb)
the guide he used wasn't outdated 3 months ago when he followed it either.
--------------------- MERGED ---------------------------
what are you trying to do and what guid are you following? maybe there's something more recent that works better.
otherwise, from thelockpick thread:
- ChoiDujour will complain about extra keys and fail. for this just provide a key file edited to contain only the following:
- master_key_00 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- master_key_01 = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- [... all master_keys through the latest one required by the firmware you're trying to install]
- header_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- aes_kek_generation_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- aes_key_generation_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- key_area_key_application_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXX
- key_area_key_ocean_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
- key_area_key_system_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXX
- package2_key_source = XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Did you make the BCPKG2-1-Normal-Main.bin backup before you did the exfat update if so i think you may need to restore it to fix your switch.So you mean i destroyed my switch and it isn't possible to rescue it?
--------------------- MERGED ---------------------------
The only file i have safed before i did the tutorial is this one: BCPKG2-1-Normal-Main.bin
Yes, the 32 GB is optional since it's still possible to format 32+ GB cards using FAT32 using third-party programs and the console will not ask you to install exfat.The 32GB is optional right ?
16GB also can trigger the exfat update pop-up as long as it's formatted as exfat.
Yes, i safed this file on my computer before I did the exfat update with HacDiskMountDid you make the BCPKG2-1-Normal-Main.bin backup before you did the exfat update if so i think you may need to restore it to fix your switch.
Good i think thats the file you need to restore with hacdiskmount to fix it but you should wait until someone can confirm it because its always risky messing with the nand.Yes, i safed this file on my computer before I did the exfat update with HacDiskMount
There is still hope just restore BCPKG2-1-Normal-Main.bin with hacdiskmount the tutorial you followed probably had you make the BCPKG2-1-Normal-Main.bin backup in case this happened.I am a little bit hopeless. I buyed a SX OS yesterday and it worked well. My SD Card was a fat32 and the games don't fit on it. So i tried to make exFat run and after that nothing worked. I am really affraid that I destroyed the console without even beeing able to play for one time
Always ensure you test your backup before saying you have a backup.
hekate does verification by default at the time the backup is made, this can be skipped or disabled though and you can't verify a given backup this way ever again after you've booted the switch again as there's nand info that changes on every bootAny way to test backup without actually restoring it ?
thanks
Actually, you can recover from pretty much any brick without a nand backup as long as you have a copy of your console unique keys and PRODINFO .It's currently not possible to restore a bricked Switch without a proper NAND backup from your own. The NAND has console-specific keys to get it working and restoring from another user's NAND backup isn't gonna help you either.
If you followed the OP's tutorial and/or messed with system files leading to this one black screen, your Switch will be bricked until a recover solution is made available (if it is going to).
Good luck with that one.
any softbrick* and you can always get the console unique keys if it's not hardbricked so all you really need is PRODINFO and hopefully boot0 as regenerating keyblobs is tedious, but they're only needed for firmwares below 6.2.0Actually, you can recover from pretty much any brick without a nand backup as long as you have a copy of your console unique keys and PRODINFO .