Question Help, I bricked my switch with a FW update

City Hunter Sep 19, 2019.

  1. City Hunter
    OP

    City Hunter Member

    Newcomer
    1
    Aug 16, 2012
    I think the title says it all, but I will write the long story now, since I really don‘t understand what I did wrong and how I can fix the problem.


    I wanted to install a new NSP release, but tinfoil just crashed with some error, which was not readable and using goldleaf, I was able to use the remote PC function (had access to my PC drives), but when I wanted to install the NSP, I got an error about an invalid NCA and that it is probably caused by a low firmware or missing sigpatches.


    So actually it might sound stupid, but I always thought the CFW (atmosphere in my case) replaces the complete FW of the switch, so I thought I have the newest FW when I update atmosphere. So I downloaded atmosphere 0.9.4 (newest release), also downloaded the newest version of kosmos 14.1 and also downloaded the newest sigpatches which I could found. I overwrite with the new files the existing on my SD card, so Atmosphere and Kosmos were on the newest version. However I got the same error when trying to install the NSP and when I checked my FW system at the boot and in the settings and it showed 7.0.0, it hit me and I realized that the CFW apparently is only an addon and I am still on a very old FW version and that this is probably the reason I can’t install the NSP file. So I knew what I had to do and followed the guide one switch.homebrew.guide to install a new firmware via ChoiDujourNX. I downloaded Firmware 8.1 from team-xecuter and started the install process via ChoiDujourNX. I was also careful that autoRCM remains activated and that it blocks to reset to factory settings as explained in the guide. The install process worked without any error or problem and it finished exactly as described in the guide and followed the last step to shutdown the console. After that the problem started.


    Since I was still in RCM, I injected the fusee-primary payload (also newest version 0.9.3 which I was also using before the FW update. It started with the kosmos and atmosphere boot screens, but then after the white atmosphere symbol, it went to a black screen and nothing happened anymore. I pressed the power button and realized that it didn’t went back to RCM, so I was already scared at that point. Since the battery was kind of low during the firmware update (although it was plugged in the PC), I thought perhaps the battery died after the FW update and restating the system and since it was late in the night and I had to work the next morning, I decided to put it to the charger overnight. I tried this morning again before work and still nothing happened, PC also didn’t show RCM and I couldn’t inject a payload. Since I quickly searched the internet and found out that I have to press the power button more than 10 seconds to shut the console completely off, which I did then and pressed the power button again to turn it on and I was relived when I saw that RCM has been detected and I could insert a payload again. So I injected fusee-primary again and the same thing happened, after the atmosphere logo the switch freezes on a black screen.


    Now, I don’t know what I did wrong and more importantly, what I can do to fix the problem. I wonder if it has to do with the fact that I bought my console in Japan and perhaps the English FW I downloaded is not compatible, but I thought it should be the same FW, since CFW also worked until now and the switch is region-free.


    The biggest concern of mine is that I don’t have any backups. I did a backup when I first installed a CFW, but I lost that backup. I wouldn’t mind to loose all save games or other stuff one my switch if there is no other way, I just want to bring it to life again and hopefully on a CFW. I saw something about injecting another payload, but I am not sure which one and what to do afterwards (fixing the problem).


    Can someone please explain to me my options (I hope I have some), and if possible what would be the easiest way to bring it back to a CFW, hopefully running on switch FW 8.1 or 9.0.


    Thank you so much for all your help.
     
    melat likes this.
  2. maddenmike95

    maddenmike95 Advanced Member

    Newcomer
    4
    Mar 26, 2009
    United States
    This same problem happened to me a while back and I found out it was a really easy fix. When I updated with ChoiDujourNX I had a exfat micro sd card but accidently chose the wrong option for my micro sd card. So to fix it I backed up the micro sd card to my computer and then reformatted it to fat32 and recopied everything back over to it and tried to boot again. This fixed the black screen problem. To get exfat support back I had to update again with ChoiDujourNX and pick the exfat option this time. After the update it booted to a black screen again so I had to reformat my micro sd card back to exfat and copy everything back over to it, then it booted fine and I was now back on a exfat micro sd card. So I suggest that you check your micro sd card on your computer and see if it fat32 or exfat. Whichever format it is just back it up and reformat it to the opposite, this should fix the problem. I hope this makes since to you. Try this out and report back.
     
    Last edited by maddenmike95, Sep 19, 2019
  3. City Hunter
    OP

    City Hunter Member

    Newcomer
    1
    Aug 16, 2012
    Thanks, that makes absolutely sense to me and would explain everything since I cannot imagine what else caused the problem. I will surely try that out tonight after I return home, that would be surely a super easy fix. One small question, when reformatting back to exfat, could you choose to update to the exactly same fw version? Also should I stay now on 8.1 or is it absolutely safe and has no negative effect to go already to 9.0?
     
  4. maddenmike95

    maddenmike95 Advanced Member

    Newcomer
    4
    Mar 26, 2009
    United States
    Yes, when reformatting back to exfat you can choose the exact same firmware version and yes 8.1 0r 9.0 will be totally fine. Just remember to choose the correct option for your micro sd card.

    [​IMG]

    The option on the left is fat32 and the right is exfat, just ignore the 6.0.0 in the picture, as it was the only picture I could find quickly to show. Also make sure you leave auto RCM on.
     
    Last edited by maddenmike95, Sep 19, 2019
  5. City Hunter
    OP

    City Hunter Member

    Newcomer
    1
    Aug 16, 2012
    I think I used the left option, which means FAT32, but since I have a 32GB stick I think that is already by default formatted to exfat... so I guess you are right.

    Do i need a Special Software to Format to fat32? If so do you have a recommendation? By the way is it recommended to return to exfat afterwards? What are the advantages/disadvantages?
     
  6. pLaYeR^^

    pLaYeR^^ Doctor Switch

    Member
    9
    GBAtemp Patron
    pLaYeR^^ is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Sep 18, 2014
    Austria
    Austria
    You can use guiformat to format the stick to FAT32. Don't use exFAT since it causes many issues on the switch. It's simply not necessary to use exFAT on your switch.
     
  7. maddenmike95

    maddenmike95 Advanced Member

    Newcomer
    4
    Mar 26, 2009
    United States
    I use exfat with no problems, it makes it easier when coping backup nsp's that are 4gb plus. You can not copy backup nsp's that are 4gb or more unless they are split to fat32 and this is why I use exfat. I have a lot of backups and I do not use network install, so exfat is much easier for my situation. I have separate micro sd cards that I use for lakka, Linux for tegra and android os when I need to use those. For all those you need a fat 32 micro sd.
     
    Last edited by maddenmike95, Sep 19, 2019
  8. pLaYeR^^

    pLaYeR^^ Doctor Switch

    Member
    9
    GBAtemp Patron
    pLaYeR^^ is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Sep 18, 2014
    Austria
    Austria
    You don't need network for goldtree...
     
  9. City Hunter
    OP

    City Hunter Member

    Newcomer
    1
    Aug 16, 2012
    Thanks again man. Just to let you know it was indeed the SD card formatting, now it works again as it should be on FW 8.1. only problem is that i still get a crash when trying to install the NSP via USB with Fluffy/Tinfoil and using Quark/Goldleaf I still get the error about invalid NCA, so either too low FW or missing sigpatches. But it can be neither of these. Well perhaps the NSP file is corrupted and I should get a new one...
     
  10. maddenmike95

    maddenmike95 Advanced Member

    Newcomer
    4
    Mar 26, 2009
    United States
    It could very well be the sig patches, I use devmenu to install all my nsp's and never have run into any problems.
     
Quick Reply
Draft saved Draft deleted
Loading...