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.
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.
