got it. thanksYes because DLC use personalized tickets unlike the common tickets for updates although I've never tried rebuilding a DLC without the ticket and seeing what would happen.
got it. thanksYes because DLC use personalized tickets unlike the common tickets for updates although I've never tried rebuilding a DLC without the ticket and seeing what would happen.
It's real, I tried another SD-card, I tried a 16 GB SD card, but that one didn't work too.Did you check if it was fake? If you did not, use a tool like FakeFlashTest.
Nope because traces of CFW persist in the NAND even after you reboot or turn the console off. Only way to remove such traces is to restore a clean NAND backup made before hacking the console.Hello everyone,
Once i use my Nintendo Switch under CFW with SX OS can i just put my Nintendo Switch off and then booting back up in OFW without risking having a ban if i want to play Splatoon 2 online or once you just put SX OS dongle on your Nintendo Switch it's over ?
Firmware doesn't matter as the exploit is reliant on the hardware of the console, not the firmware. As long as the serial number isn't one of the patched ones, the console should be vulnerable. Although given it was bought last year, the serial number is most likely unpatched.Alright thanks.
My Switch bought on launch last year is on latest firmware, is this a problem to start using SX Loader ?
I would do #3 before #4 unless you plan on chainloading Hekate from the SX OS menu.OK awesome !
So correct me if i'm wrong but this is what i'm planning to do step by step to hack my Switch :
1 - Forget WIFIs on my Nintendo Switch
2 - Put my Switch on airplane mode
3 - Launch the procedure to start using SX SX OS (RCM launch...)
4 - Dump my clean NAND using Hexate
5 - Start using my .xci and enjoy SX OS
Does it sound good ?
And what can i do once for example the lastest Pokemon game and Smash Bros Ultimate use a new firmware ? Should i use ChoixduJour NX software i keep hearing about in this forum ?
Thanks again for your patience and your answer to my questions for the past few days.
Regards,
What I'm saying is you should backup the NAND with Hekate before using SX OS unless you were plan on launching Hekate from the SX OS menu which is fine since its in RCM.You said "I would do #3 before #4" not sure what you meant here ? but yes i was planning on putting Hekate on my micro SD at the same time as putting the files for SX OS so i can do it right away. Is that a bad thing ?
I saw somewhere that "AutoRCM" is a bad thing that can hurt the Switch ? Is this true ?
If you really don't want to keep your options open for exploits on lower firmwares and don't mind burning fuses, you can disable AutoRCM when installing firmwares with ChoiDujourNX.OK
So to prevent any harm for my console. Can i just disabled AutoRCM while i'm not needing a update using ChoidujourNX and just put it back on when doing a firmware update using the homebrew ?
Quite lost using this ^^ Also what's Horizon ?
If you really don't want to keep your options open for exploits on lower firmwares and don't mind burning fuses, you can disable AutoRCM when installing firmwares with ChoiDujourNX.
Also Horizon is the name of the OS of the Switch.
Fuses will be burnt regardless if you use CFW or OFW without AutoRCM.Ok so it's ok as long as i keep using my console in CFW ? right ?
Maybe shoud i wait for the release of Pokemon Let's Go & Ultimate Smash Bros prior to using SX OS ? In case there's an update firmware released after the launch of those two titles maybe it'll be better since i heard that people on this forum already have issues with SX OS once they updated their console to 6.1 firmware ?
Fuses will be burnt regardless if you use CFW or OFW without AutoRCM.
Also I don't know of any issues with firmware 6.1 with SX OS. I've only heard of one issue and thats with the "sig patches" Atmosphere uses.
The only way to check if you're banned is by risking a ban and the fastest way is by connecting to the eShop.So i have a specific problem, i used my atmosphere jig yesterday and oversaw the fact that - brings up the backup menu, so it booted the Switch to the Homemenu, ofc my Switch was still in Airplane mode, i then shut it off and made copies of everything (NAND etc), i only used one homebrew tool from hekate to get the keys (still in airplane mode), but i forgot to change the internet settings beforehand, so when i was in ofw mode to do that, my Switch then proceeded to download the update, which i got rid of via recovery.
The question is, is there any way to check if my unit is not banned/superbanned?
Because not knowing it kinda bugs me.
AutoRCM means you don't have to use a jig to enter RCM anymore meaning it can save some wear and tear on your pins so it has benefits outside of protecting the fuses.Ok i'll use AutoRCM then, you likely to say that it's better for the console right ? ^^
What your thought about what i said earlier regarding waiting for the release of Pokemon & Smash Bros before hacking due to potential firmware update ?
The only way to check if you're banned is by risking a ban and the fastest way is by connecting to the eShop.
If you try connecting to the eShop on a lower firmware and it tells you to update, you're not banned. It would give you the ban error code if you were actually banned.Tbh im not that daring to try this direct approach.
I mean, i already used Hekate which surely left at least once trace, couldnt i just reflash my nand with the backup i have and then see if my Switch still downloads the system update?
I cant connect to the E-Shop anyway since im still on 5.0.1 and it always asked me to update which i didnt do.
More stability?So I'm in the process of getting ready for sx os on a totally clean switch that has never been tinkered with. Nice and slowly. It's on 6.01 right now and I am preparing the nand dump. What's the harm in updating to 6.1 before I continue?