As for when it is getting released, all I can say is soon because I haven't heard much since that post
As for when it is getting released, all I can say is soon because I haven't heard much since that post
Hi
I recently did roughly the same. What you should do is:
1. Update Sxos to 2.5.
2. Make sure there is at least 32gb space free on your sd card.
3. Create emunand (takes just over an hour).
4. Boot into cfw and update fw via choidujournx to 6.2 (making sure to select the 'ex-fat' option if you are using ex fat.)
5. Power off. Remove sd card and connect to pc. If you have saves/games you want to use on emunand delete the 'Emutendo' folder and rename the 'Nintendo' folder to 'Emutendo'.
6. Boot up and make sure emunand is enabled on the sxos splash screen (it should be already).
7. Boot into cfw!
thanks @Adran_Marit switching to fat32 worked. it still boots up pretty slow compared to the videos ive seen on YT but no big deal i guess. so just be clear now that i have autorcm installed if i shut it off i need the dongle to boot into cfw again and if i dont put in the dongle its stays in black screen rcm to prevent fuse burn?
Quick question. I have a switch with emunand. If for some reason I forget and turn it on normally without entering rcm/cfw would all my games be wiped from the sd card? This happened before I created an emunand. Appreciate any advice!
Other day another issue i cant seem to figure out lol.
So my sd is formatted to fat32, i am using emunand.
I quickly learnt that i was unable to drop any nsp files over 4gb on the sd card so have been looking at using some USB installer. (I dont want to connect the switch to the net)
I have tried tinfoil and goldleaf/tree and briefly looked at SX installer but havent been successful.
Tinfoil crashed when i try to launch the .nro from within sxos
Gold leaf ive had a little bit more success, i have managed to install gold leaf which does communicate with gold tree (I have installed the correct driver) but anytime i try to send anything over 4GB it hangs up in "starting installation.." on the switch and "gold leaf is ready for installation prepping everything.." showing on goldtree.
Any clue why a, tinfoil crashes SXOS and b, has gold leaf crashed or is it just super slow at starting the installation?
Also ive no idea how to set up SX installer correctly to see my files, there isnt much information about it.
Any ideas?
So my sd is formatted to fat32, i am using emunand.
I quickly learnt that i was unable to drop any nsp files over 4gb on the sd card so have been looking at using some USB installer. (I dont want to connect the switch to the net)
I have tried tinfoil and goldleaf/tree and briefly looked at SX installer but havent been successful.
Tinfoil crashed when i try to launch the .nro from within sxos
Gold leaf ive had a little bit more success, i have managed to install gold leaf which does communicate with gold tree (I have installed the correct driver) but anytime i try to send anything over 4GB it hangs up in "starting installation.." on the switch and "gold leaf is ready for installation prepping everything.." showing on goldtree.
Any clue why a, tinfoil crashes SXOS and b, has gold leaf crashed or is it just super slow at starting the installation?
Also ive no idea how to set up SX installer correctly to see my files, there isnt much information about it.
Any ideas?
Hey ! Thanks for your answer !
Is it safe to create an emunand based on a nand that has already been hacked ?
Don't you think that Nintendo will spot my CFW and ban me if i use my console in OFW to play Fortnite for instance while i use Emunand for playing cracked games with a dirty Nand ?
Hope i made myself clear with that example
Sorry, can't help you with that i'm afraid... I suppose you can't go online with emunand anyway (I don't think?) so it doesn't matter if it's a copy of a nand that has been been banned? Maybe someone else can give some definite advice?Hey ! Thanks for your answer !
Is it safe to create an emunand based on a nand that has already been hacked ?
Don't you think that Nintendo will spot my CFW and ban me if i use my console in OFW to play Fortnite for instance while i use Emunand for playing cracked games with a dirty Nand ?
Hope i made myself clear with that example
Is it really needed to update without burning fuses? I mean, since it seems not needed downgrading, does still worth it to updating preserving fuses?
Now SX OS creates an Emutendo folder for EmuNAND so SysNAND and EmuNAND don't overlap due to originally sharing the Nintendo folder.
Did you try the 883e Tinfoil build from Lavatech?
That's a subjective question; there is no right answer. There may be an exploit on lower firmwares, there may not be, the exploit on lower firmwares may be worse than the current one, it may be better, etc. There's way too many possibilities and unknowns to know if its worth preserving fuses or not. However what I can say is that firmware is temporary but fuses are permanent; once they are burnt, they're gone. And if an untethered coldboot exploit is revealed tomorrow but only works on firmwares 4.1 and below, I wouldn't want to kick myself because I thought fuses were irrelevant or AutoRCM wasn't worth it.
I see.. but i am on firmware 6.1 so the chances that a definitive exploit will work on this such as young fw are low. With that in mind, i am not upgrading to 6.2 for sure, but also i do not care of my fuse count. Do you agree?
Firmware or fuses? Firmware is irrelevant with the Switch. You can be on firmware 6.1 with one burnt fuse or seven burnt fuses. While in the past, hacking was firmware dependent, that is no longer the case with the Switch as the fuses determine what firmware you can or can't run.
Assuming you are referring to a fuse count of 7 which corresponds to firmwares of 6.0-6.1, Deja Vu is the one exploit not capable of being launched past firmware 6.1 so if you burn your eighth fuse, you already lose out on one confirmed exploit. Also there's no point in discussing the chances of an exploit being dropped on a specific firmware. There is about an equal chance of an exploit being dropped for firmwares 3.0 and below as there is one for firmwares 6.1 and below; anything can happen and no one knows what the future may bring. The only way we can prepare ourselves is by preserving our fuses.
Personally I prefer updating without burning fuses more than normally updating because it not only lets me retain AutoRCM, which I would be using normally anyways, as well as retain exFAT support. If you update officially, you have to update twice to be on a firmware that supports exFAT and AutoRCM is removed during system updates (unless you're running Atmosphere).
Hello!
I'm running Atmosphere on my switch and suddenly it turned off and I can't turn it on again (I'm not on autoRCM). It happened randomly :/ it's been working very fine until now, so... I hope it's not a brick. Any idea?
I'm running Atmosphere on my switch and suddenly it turned off and I can't turn it on again (I'm not on autoRCM). It happened randomly :/ it's been working very fine until now, so... I hope it's not a brick. Any idea?
I should make myself more clear
To eventually use my OFW for playing legitimate games online. Should i back up my "clean" NAND before doing an EMUNAND ?
To eventually use my OFW for playing legitimate games online. Should i back up my "clean" NAND before doing an EMUNAND ?
i dont get why using autorcm prevent burning fuses. I mean.. I got a 5.1 swtich. I updgraded it trought the console to 6.2 and in that version i did my nand backup so i guess i burned the fuses needed to be in that version. Now, i'm using autorcm not because of ChoiDujourNX, because i never used it, but to prevent using a jig. Now what will happen when the 6.3 cames out and i need to update my console because of new games? If i want to stay out of being banned, do i must use ChoiDujourNX? And after using it make a new nand backup? or it is safe to keep using my 6.2 nand backup since ChoiDujourNX dont burn fuses and i can downgrade without being worried about the fuses count match?
I still do not completely get it. Is the Switch afterwards in a state where it can run any homebrew without having the dongle available, so is the dongle a one-time-only device?
Or is the switch, when the dongle and the jig(?) are removed, in the same state as before, i.e. unmodified?
P.S.: I'm asking because I want to play scummvm (if that's already available) but my son does not want the switch to be hacked because of Nintendo Online he wants to use and he fears getting banned.
Last edited by Skeeve,
Did it run out of battery?
If your SysNAND is currently not clean but you do have a clean SysNAND, you should restore that prior to going online. When you do that should be before you setup EmuNAND because EmuNAND writes to boot1 which is a part of your NAND backup meaning you should also be restoring that (unless your current firmware matches the firmware of your NAND backup).I should make myself more clear
To eventually use my OFW for playing legitimate games online. Should i back up my "clean" NAND before doing an EMUNAND ?
AutoRCM isn't directly preventing the fuses from being burnt. Its completely possible to burn fuses with AutoRCM and I'm not just referring to system updates that remove it. What actually burns fuses is the stock bootloader of the console. If you normally turn on the console, you're using the stock bootloader. AutoRCM prevents you from using the stock bootloader. Instead, you have to supplement your own which all CFW happen to come with. These substitute bootloaders now have to bypass the fuse check and prevent fuses from being burnt. All builds of ReiNX, Fusee, and Hekate do this but early version of SX OS (V1.1 and V1.0) did not. Meaning you can still burn your fuses if you use an early enough copy of SX OS but the chances of that happening are non-existent.
As for your other questions, nothing is going to require the new firmware immediately because that game would need to have been developed after the firmware is already out. You don't need to make a new NAND backup if you don't burn fuses; its completely optional.
CFW doesn't persist after the console is shut down or rebooted. The payload needs to be sent in order to use CFW. If you want to avoid having to send payloads, you can keep the console in sleep mode or install an internal trinket that will send payloads for you. And in order to send a payload, your console has to be in RCM which you must always do with a jig or AutoRCM.
Also if he doesn't want the console to be banned, you shouldn't hack it. Nintendo has stepped up their security with this console and have banned people for pretty much everything.
ok so after i installed a XCI game how do i uninstall it ? do i need their sx installer tool ?
update: nvm i think i found it from data manager right
update: nvm i think i found it from data manager right
Last edited by GATWYAY3.2,
- No one is chatting at the moment.
