Whoops forgot to respond to this. You're going to be risking a ban either way so just get it out of the way now. Who knows, you may end up lucky and never get banned.
Sorry that's the extent of my knowledge. While you tried other USB-C cables, you can also try other devices like an Android phone or another computer if you have one. Other than that, it might be worth making a thread for your issue.
OK so i just did following things
- did a factory reset on my SysNAND OFW 5.1
- then updated my SDCard EMUnand to 8.1.0 using ChoiDujourNX and disabled AutoRCM
- unplugged my SD card, updated SysNAND to 8.1.0 through internet
- with new SysNAND 8.1.0 OFW, created a new account, about to link the new account to device
- I cannot check eshop as it ask me for nintendo online code, don't want to pay for that unless i am sure i am safe.
So I wonder is that mean my device is not banned (yet)?
Did Nintendo ever ban anyone on switch not instantly but by a ban wave? I understand I might be flagged even i may safe at the moment
Hi,
I have a problem. I just update a switch to 8.0.1. When I power off and then on its freezes and don't want to boot. I'm using a ns-atmosphere. I just see a ns-atmosphere logo and then write Welcome to Atmosphere and switch turns black and nothing happened. Can you help me?
I have a problem. I just update a switch to 8.0.1. When I power off and then on its freezes and don't want to boot. I'm using a ns-atmosphere. I just see a ns-atmosphere logo and then write Welcome to Atmosphere and switch turns black and nothing happened. Can you help me?
Total newbie here so a couple of quick questions
1) I’ve got a clean unpatched Switch with zero mods which is running OFW 6.0 is there really any advantage staying in this old firmware or am I good to update to 8.1 ?
My final goal is to run the switch in two modes, first mode completely legit using eShop and playing online and second mode running an Emunand on hidden partition completely offline with nsp games
As a rough plan so far I have booted into RCM, backed up my totally virgin and current NAND and Boot 0/1 files to SD and copied these too several locations..just so I have a totally virgin NAND backup. I was thinking next step would be to update to 8.1 OFM via Nintendo, boot back onto RCM and backup the NAND again with both BOOT 0/1 files ...again back these up to several locations..this should give me a fully legit online account and a nice legit 8.1 NAND to role back too if needed.
Then boot back into RCM and create an emuNAND with 8.1 fresh ..this is where I’m not sure where to head, are there alternatives to emunand SX OS such as Atmosphere emunand or is the TX CFW the best for NAND emulation ?
1) I’ve got a clean unpatched Switch with zero mods which is running OFW 6.0 is there really any advantage staying in this old firmware or am I good to update to 8.1 ?
My final goal is to run the switch in two modes, first mode completely legit using eShop and playing online and second mode running an Emunand on hidden partition completely offline with nsp games
As a rough plan so far I have booted into RCM, backed up my totally virgin and current NAND and Boot 0/1 files to SD and copied these too several locations..just so I have a totally virgin NAND backup. I was thinking next step would be to update to 8.1 OFM via Nintendo, boot back onto RCM and backup the NAND again with both BOOT 0/1 files ...again back these up to several locations..this should give me a fully legit online account and a nice legit 8.1 NAND to role back too if needed.
Then boot back into RCM and create an emuNAND with 8.1 fresh ..this is where I’m not sure where to head, are there alternatives to emunand SX OS such as Atmosphere emunand or is the TX CFW the best for NAND emulation ?
how is actual update procedure ?
I'm on CFW 6.2.0 atmosphere (old) OFW 5.x.x (no fuses burned during update). now me question, how can I update to a newer firmware (8.0.0? or 8.0.1 or 8.1.0)? Update atmosphere, then download firmware, and then download newest ChoiDujourNX? then start cfw and update through ChoiDujourNX enable "prevent fuse burning AutoRCM" is this right?
do I need to update the "boadloader" (hekate) on my sd card / on my external device as well?!
which fw is recommendedat the moment?!
edit: what do I read here? ... you can do a emunand now? run 2 different nands? one with OFW and one stealth? ... does this really works? Or shall I be on the old one wait till I don't need a external device to boot my switch up (do have ns- atmosphere) ... or is this fixed now as well?!
I'm on CFW 6.2.0 atmosphere (old) OFW 5.x.x (no fuses burned during update). now me question, how can I update to a newer firmware (8.0.0? or 8.0.1 or 8.1.0)? Update atmosphere, then download firmware, and then download newest ChoiDujourNX? then start cfw and update through ChoiDujourNX enable "prevent fuse burning AutoRCM" is this right?
do I need to update the "boadloader" (hekate) on my sd card / on my external device as well?!
which fw is recommendedat the moment?!
edit: what do I read here? ... you can do a emunand now? run 2 different nands? one with OFW and one stealth? ... does this really works? Or shall I be on the old one wait till I don't need a external device to boot my switch up (do have ns- atmosphere) ... or is this fixed now as well?!
Last edited by dagarui,
Trying to put my Switch into Recovery mode but it will not do it. After removing the right joy-con and putting the Jig in place and holding vol+ and pushing power the screen will not come on. If I remove the jig and insert the joy-con back in place the switch will power up. So does that mean I have a patched console and unable to mod?
If you do not see a banned error code, you are not banned. But Nintendo typically bans in waves which we have no idea when they occur. Nintendo never instantly bans anyone.
What is your SD card formatted as?
There may be an advantage in keeping firmware 6.0 but there is also a way to retain the ability to downgrade to 6.0 as well as update to firmware 8.1. This is done by updating without burning fuses. There are several ways of doing this such as with the homebrew application ChoiDujourNX, having a jig inserted and holding volume + when the system reboots after finishing installing a system update so it manually reboots into RCM as detailed here, or updating online and running Atmosphere/ReiNX while AutoRCM is enabled. In terms of which one is safest from a banning perspective, the second option is the least detectable but it is also the riskiest because if your jig fails to work, then you will not reboot into RCM and thus burn fuses. The other 2 methods of updating without burning fuses are equally detectable I would say although I can personally vouch for the third method as I have been using it to update without burning fuses and I haven't been banned yet. Also be aware that regardless of which method you choose, AutoRCM must be enabled in order to prevent fuses from being burnt.
The reason for updating without burning fuses is because lower firmware versions may have better exploits than the current one which requires a jig and USB device to boot CFW. When this exploit will come out is anyone's guess but having access to more options is objectively better than having access to less options. If you are fine with booting CFW with a jig and USB device, then you can simply ignore my top paragraph, update normally, and irreversibly burn fuses. But if you want to have the option in the future to boot CFW without a jig and USB device, then update your SysNAND firmware without burning fuses.
As for which CFW you should go with, Atmosphere's implementation of EmuNAND will eventually be better than TX's but not at the current moment. Atmosphere's current implementation is still experimental and only supports the hidden partition method of EmuNAND. It is also free unlike SX OS. So I recommend waiting until Atmosphere stabilizes their implementation which is what I'm doing as well.
You pretty much answered your own question. As for which firmware you should update to, either 8.0 or 8.0.1 is fine as Hekate does not support firmware 8.1 yet.
And while emuEMMC is out for Atmosphere, it is considered experimental and only supports the hidden partition method. It is also currently not very user-friendly.
--------------------- MERGED ---------------------------
All units, patched or not, can enter RCM. What is patched is the ability to send payloads in RCM.
any way of transferring dlc updates or whole games i installes under sxos to the sd card? its wasted 32gb of emunand space on the sd card if i dont put anything in there. i installed all to sd though and dont find any way to transfer to (emu)nand.
also is it safe now to update emunand to latest firmware? i read that some games wont run higher than 7.1? did they fix that on sxos? id very much like to get the new game sorting feature of fw8
also is it safe now to update emunand to latest firmware? i read that some games wont run higher than 7.1? did they fix that on sxos? id very much like to get the new game sorting feature of fw8
Did you use the latest files? 190513-v1.7? If yes, how did you add the new files to your SD card?
- No one is chatting at the moment.
-
-
-
@
BakerMan:
Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.+2 -
-
-
@
BakerMan:
Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
