I need some advice what to prepare to avoid BAN when update my OFW version for online.
My goal is able to play online in SysNAND OFW, while keeping backup on emuNAND CFW.
I want to make sure I am clean (at least do whatever I could) before I attempt to go online and do a official OFW update,
but there are so many guide out there, like should I clean my error log? should i do a factory reset?
I tried to list out what i have done so far, hope people can give me some tips what should I do in my situation before i attempt to go online.
since June 2018
- Begin using SXOS, OFW was 5.1.0
- Wifi profile deleted, disabled send report
- so far Never go online on sysNAND OFW/CFW since I use SXOS
- didn't make pure SysNAND backup before I start using SXOS
- did use autoRCM for a while to boot to systemNAND CFW, later on removed autoRCM as there was some distrust to that
- been using XCI and NSP in SysNAND CFW for switch gaming, sometimes install NSP DLC for XCI games
- did experience several errors and getting reboot message in history, while installing NSP using sxInstaller.
- Never bother any theme mod, emulator, homebrew. I dont even know what is LayeredFS
Dec 2018
- created the first SysNAND backup (probably is dirty?)
- created emuNAND from OFW 5.1.0.
- from Dec 2018 only play games on emuNAND.
- did install some DLC / nsp games on emuNAND
- updated emuNAND to 6.2 around Late Dec 2018 by using ChoiDujourNX
Now
- SysNAND 5.1.0 EmuNAND 6.2, fuse burnt count is 6
My goal is able to play online in SysNAND OFW, while keeping backup on emuNAND CFW.
I want to make sure I am clean (at least do whatever I could) before I attempt to go online and do a official OFW update,
but there are so many guide out there, like should I clean my error log? should i do a factory reset?
I tried to list out what i have done so far, hope people can give me some tips what should I do in my situation before i attempt to go online.
since June 2018
- Begin using SXOS, OFW was 5.1.0
- Wifi profile deleted, disabled send report
- so far Never go online on sysNAND OFW/CFW since I use SXOS
- didn't make pure SysNAND backup before I start using SXOS
- did use autoRCM for a while to boot to systemNAND CFW, later on removed autoRCM as there was some distrust to that
- been using XCI and NSP in SysNAND CFW for switch gaming, sometimes install NSP DLC for XCI games
- did experience several errors and getting reboot message in history, while installing NSP using sxInstaller.
- Never bother any theme mod, emulator, homebrew. I dont even know what is LayeredFS
Dec 2018
- created the first SysNAND backup (probably is dirty?)
- created emuNAND from OFW 5.1.0.
- from Dec 2018 only play games on emuNAND.
- did install some DLC / nsp games on emuNAND
- updated emuNAND to 6.2 around Late Dec 2018 by using ChoiDujourNX
Now
- SysNAND 5.1.0 EmuNAND 6.2, fuse burnt count is 6
Last edited by paymok,
So I tried setting up ldm_mitm and made a new copy of my connection to use for LAN play. After a few tests, now the regular connection fails the connection test because "connection to server was lost". The web applet also immediately crashes the system when I try to launch it. Tried deleting the LAN play connection and disabling ldn_mitm, but the problem still isn't solved. Does anyone know what's wrong and how do I fix it?
I updated my switch to 8.1 and reinx 2.4 now when my switch enters sleep mode longer then 10 minutes it gets hot and then crashes wtf is going on? Did the 8.1 update turn my switch into a nuke?
Check your Switch serial number if it’s patched or not. Then use one of the cfw guides to hack. Atmosphere, ReiNX, or SXOS.
If your Switch is patched and on 8.1 you are out of luck for now.
https://gbatemp.net/threads/switch-...he-first-post-before-asking-questions.481215/
Last edited by Zuzuooloo,
Thanks! Mine's refurbished so it's most likely patched. The thread links to another process to see if it's actually patched or not but it involves the whole joy-con pin method which seems really convoluted. I'd try it if it definately worked but for probably a negative I'm ok I guess.
Oh well.
So I somehow lost my bis keys and accidentally updated to 8.1.0 (where the TSEC FW is different). I'm impatient and didn't wait for a new biskeydump version or properly downgrade to 8.0.1, so I flashed my old 8.0.1 boot0/1 files, which got my bis keys back - but I can't boot back up (or at least I think so). I have AutoRCM on, TegraRcmGUI doesn't recognize when I try booting into RCM mode (and my computer doesn't say a new USB device connected). Any suggestions, or is my switch toast?
Probably a dumb question but, I am trying to run Kosmos/Atmosphere for the first time. I have AMS 9.1 and am on FW 8.1.0, Everything seems fine but it stops me at Sept saying the keys are invalid. I thought I read something about this but can't seem to find the answer again. The only key dump I have done was with LockpickRCM.
What am I missing to boot atmosphere?
What am I missing to boot atmosphere?
Unfortunately you cannot tell if your BOOT0 was dumped before or after enabling AutoRCM without restoring it then checking the AutoRCM status with something like Hekate. But there are no tools that can check when CFW was run with respect to the NAND dump.
Without a clean NAND backup, you cannot safely go online with SysNAND or EmuNAND. And there is no way to regenerate one with either.
This is the first I'm hearing of this but this is generally why its not recommended to update to the latest firmware since there is no use for it apart from online play which is not a good idea with a hacked console anyways.
Well if you buy the SX Pro, it will give you everything you need from a jig to enter RCM with to a dongle that will send the payload via USB. If you get SX OS which is cheaper, you will need to acquire a jig or something else to enter RCM with as well as a way to send payloads via USB like a USB cable and a phone or computer.
No
Restore either an eMMC SYS or eMMC raw GPP that matches your 8.0.1 BOOT0/BOOT1 files.
Just use the latest Atmosphere and send Fusee instead of Hekate.
You shouldn't need to dump or provide any keys to boot Atmosphere. Delete any keys you may have on your SD card and try again. It may also be worth starting over by deleting any old Atmosphere files/folders and putting the new ones on the SD card. If you don't know which files and folders are for Atmosphere, simply delete everything except the Nintendo and potentially the Switch folders.
I'm planning on doing that after I can get back into RCM, right now I can't for some reason. Any suggestions on how? (I've heard of draining/charging the battery, I tried charging to 100% earlier but that didn't work so right now I'm seeing if draining makes a difference)
So this means even though Atmosphere has been updated, we have to wait for Hekate, then.
RCM is dependent on one and only one thing; shorting pin 10. The problem is there is no way of verifying that pin 10 is being shorted apart from successfully entering RCM meaning if you aren't entering RCM, then you aren't shorting pin 10. This step is completely user-dependent so there is not much I can do except tell you to use other items to enter RCM such as aluminum foil, a paperclip, sim card remover, etc. You can find a list of some user-submitted suggestions for entering RCM here.
If you want to launch Atmosphere, you can do it now by launching Fusee instead of Hekate. Otherwise, yes.
can I assume doing all these cleaning doesn't make a differences, so I can take my chances try to do a factory setting then just go online and see what happen? To me self-ban more or least equal to Ban
Last edited by paymok,
I'm using AutoRCM (I know you go through quite a bit of posts and may have missed that in my first post), and just can't get it to be recognized by PC (both in TegraRcmGUI and Device Manager). I'm not even quite sure what the problem is; I've used multiple USB-C cables and it still doesn't show up.
But did the BOOT0 have AutoRCM enabled? Meaning did you dump it while AutoRCM was enabled? Or are you saying you enabled AutoRCM after restoring your BOOT0?
