Hi all, yet another one here who's at a bit of a loss after trying to get into CFW...
I got a second-hand Switch a few days ago and it was on 7.0.0. Proceeded to upgrade to 8.1.0 to be able to register an account.
I've been following the "Switch Homebrew Guide" and everything was super smooth - working 3d printed jig; confirmed fusee vuln.; RCM OK and can flash Hekate.
I also went the emuMMC route just in case - seemed to work fine, got a backup before anything and then went on to create the partitions/enable emuMMC.
However when I went to "Launch" CFW (either emuNAND or sysNAND) I get the splash screens until the Atmosphere logo and then I get an all black screen...
The console isn't bricked or anything, it just seems to be stuck somehow. This is because I can power it down and get back into RCM or boot normally into OFW.
After doing a bit of research I figured it could be related to the SD card's partition being in exFAT - changed to FAT32 but still the same result.
Thanks in advance!
I got a second-hand Switch a few days ago and it was on 7.0.0. Proceeded to upgrade to 8.1.0 to be able to register an account.
I've been following the "Switch Homebrew Guide" and everything was super smooth - working 3d printed jig; confirmed fusee vuln.; RCM OK and can flash Hekate.
I also went the emuMMC route just in case - seemed to work fine, got a backup before anything and then went on to create the partitions/enable emuMMC.
However when I went to "Launch" CFW (either emuNAND or sysNAND) I get the splash screens until the Atmosphere logo and then I get an all black screen...
The console isn't bricked or anything, it just seems to be stuck somehow. This is because I can power it down and get back into RCM or boot normally into OFW.
After doing a bit of research I figured it could be related to the SD card's partition being in exFAT - changed to FAT32 but still the same result.
Thanks in advance!
Hi
I currently have clean (should be clean) SysNand of 6.20. I want to register my Switch with Nintendo (it has been online once with clean NAND, so logged with Nintendo on that firmware), Draxzelex in my earlier question said that as soon as i try and register with Nintendo my firmware will need to go to 8.1.
My plan is to go online, get registered, than create a backup of NAND and then create a EmuNAND, but ideally keep the option to go back down to 6.20 incase of exploits in the future.
Hope that makes sense.
Last edited by Epps,
Well you could restore the clean SysNAND, update SysNAND without burning fuses, register, go offline and create EmuNAND. Then you don't need to connect with dirty 8.1.0 NAND.
Please clarify this bit for me: update SysNAND without burning fuses - is that through official means i.e. by going online or by using an alternative method?
Also, is it possible to use EmuNAND to go online if i am only using retail games?
Yes, official update. But you need to enter RCM right after the update is finished or your console will burn fuses up to 8.1.0.
People use emuMMC (Atmosphere) online with legit games and weren't banned. It depends on what you want to do in emuMMC online.
Honestly that is a really weird issue. Try booting another CFW to see if the issue persists such as ReiNXHi all, yet another one here who's at a bit of a loss after trying to get into CFW...
I got a second-hand Switch a few days ago and it was on 7.0.0. Proceeded to upgrade to 8.1.0 to be able to register an account.
I've been following the "Switch Homebrew Guide" and everything was super smooth - working 3d printed jig; confirmed fusee vuln.; RCM OK and can flash Hekate.
I also went the emuMMC route just in case - seemed to work fine, got a backup before anything and then went on to create the partitions/enable emuMMC.
However when I went to "Launch" CFW (either emuNAND or sysNAND) I get the splash screens until the Atmosphere logo and then I get an all black screen...
The console isn't bricked or anything, it just seems to be stuck somehow. This is because I can power it down and get back into RCM or boot normally into OFW.
After doing a bit of research I figured it could be related to the SD card's partition being in exFAT - changed to FAT32 but still the same result.
Thanks in advance!
Thanks pLaYeR for giving up your time to answer these.
I have found this thread https://gbatemp.net/threads/an-easy...ch-firmware-without-burning-any-fuses.511847/ to help me update the way you have mentioned.
--------------------- MERGED ---------------------------
Quick browse in that thread my understanding is that once updated via this method i need to keep console in AutoRCM to avoid burning fuses and get AutoRCM to boot into sysNAND.
2002-4153 error playing wolfenstein younblood custom xci (base game + update + dlc)
SX OS v2.8 beta, rcm enabled, emunand located on internal storage/OFW both 8.1 firmware, microsd 128 sandisk class 10 U1 A1.
i have to mention i played other titles in the same conditions and they run pefectly.
Can anyone helpme? thanks
SX OS v2.8 beta, rcm enabled, emunand located on internal storage/OFW both 8.1 firmware, microsd 128 sandisk class 10 U1 A1.
i have to mention i played other titles in the same conditions and they run pefectly.
Can anyone helpme? thanks
This error code seems to indicate that the game is corrupted. Redownload/reinstall the game.2002-4153 error playing wolfenstein younblood custom xci (base game + update + dlc)
SX OS v2.8 beta, rcm enabled, emunand located on internal storage/OFW both 8.1 firmware, microsd 128 sandisk class 10 U1 A1.
i have to mention i played other titles in the same conditions and they run pefectly.
Can anyone helpme? thanks
@Draxzelex
Thanks a lot for the tip! I was about to go with ReiNX but decided to give atmo another go.
Stupid as this may seem, the SD card I was using probably had issues, despite there being no indication of it.
Swapped it for a new one, dumped the NAND again and re-setup the emuMMC and now it seems to be working - I can boot into CFW under emuNAND.
However (not sure if this is a me problem or a general issue) I can't install anything via the Homebrew App Store - always get an error regardless of whether its a theme, game or whatever.
Is it just me?
Thanks a lot for the tip! I was about to go with ReiNX but decided to give atmo another go.
Stupid as this may seem, the SD card I was using probably had issues, despite there being no indication of it.
Swapped it for a new one, dumped the NAND again and re-setup the emuMMC and now it seems to be working - I can boot into CFW under emuNAND.
However (not sure if this is a me problem or a general issue) I can't install anything via the Homebrew App Store - always get an error regardless of whether its a theme, game or whatever.
Is it just me?
The Homebrew appstore has be to loaded from the homebrew menu via title override and not the Album. What this means is that you have to enter the homebrew menu by holding R on a game or any other installed title so that the appstore has enough RAM to download and install homebrew applications.
The console's bootloader checks the number of fuses burnt with the firmware you are booting. If they match, then the console boots up. If they do not, the next action depends on whether there are more or less fuses burnt than the expected number for that firmware. If there are less fuses burnt than the number expected for that firmware, then the bootloader burns fuses so that they end up matching. If there are more fuses burnt than the number expected for that firmware, then the bootloader does not boot up the console and the screen will stay black which may look like a brick but it is actually not. Performing a manual shutdown in this state will turn the console back off. All of this is designed to prevent downgrading as lower firmware versions are always more exploitable than higher firmware versions. There is always the possibility that newer exploits are discovered on lower firmware versions that may be better than current exploits such as a hypothetical untethered coldboot hack. For reference, a list of firmware versions and their expected fuse counts can be found here.
it's like my first switch, now it's sold cheap2002-4153 error playing wolfenstein younblood custom xci (base game + update + dlc)
SX OS v2.8 beta, rcm enabled, emunand located on internal storage/OFW both 8.1 firmware, microsd 128 sandisk class 10 U1 A1.
i have to mention i played other titles in the same conditions and they run pefectly.
Can anyone helpme? thanks
Last edited by Lactobacillus,
How do I restore a save backup with checkpoint? I used it to backup all my save games then I used Kefir and it deleted my accounts that was on the Switch and added 1 but I can't restore the saves since it's a new account. I backed up but how do I restore with a different account. I want my saves and progress I tried to restore but it didn't work. Can I please get help.
I have a Nintendo refurbished switch with serial # XAW941xxx.
Would just attempting to run fusee gelee on it brick it?
I ask because there isn't much info on ZAW9 serial numbers
Would just attempting to run fusee gelee on it brick it?
I ask because there isn't much info on ZAW9 serial numbers
-
The Real Jdbye
*is birb* -
Veho
-
-
-
-
-
-
-
-
-
-
-
-
@
realtimesave:
Nintendo needs to release a new console, switch is getting such shitty little games lately lol it's pathetic -
-
-
-
@
The Real Jdbye:
well actually
a new console won't do anything right now, because the games are still in development, that's why there are few games being released -
-
-
-
-
-
-
-
-
