After compressing the nand backup its now around 3GB which lets me store it on a free GDrive account since they only give you 15Gigs. sweeet ill do the same to my wiiu backup since it's also 32GB
Have you tried holding power for 12 seconds then turning it on again?It was around 60%.
I recommend updating your firmware without burning fuses using the homebrew application ChoiDujourNX. Newer games, updates, and DLC require higher firmware so if you want to keep playing the latest content, you will have to update sooner or later.Should I update my firmware? Currently running on 4.1.0 with sx os.
Have you tried holding power for 12 seconds then turning it on again?
Thanks! One more question. I noticed that sx os has ftp option but I've read that its very slow; and it gets very inconvenient to take out microsd card to transfer games.Have you tried holding power for 12 seconds then turning it on again?
I recommend updating your firmware without burning fuses using the homebrew application ChoiDujourNX. Newer games, updates, and DLC require higher firmware so if you want to keep playing the latest content, you will have to update sooner or later.
When you plug the Switch into your computer, what does it show up as?
For .NSP files, you can install them with various homebrew applications like Goldleaf or Tinfoil (the original one, not the one on the appstore). For all types of files, there is a WIP homebrew that can transfer via USB known as nxmtp.Thanks! One more question. I noticed that sx os has ftp option but I've read that its very slow; and it gets very inconvenient to take out microsd card to transfer games.
Is there a faster way of transferring game files(.cxi, .nsp) from pc to switch? I've read that we can use usb flash drives, but I don't have large ones.
When you plug the Switch into your computer, what does it show up as?
have you ever used Linux?It doesn't show anything
EDIT: Nevermind!! I just plugged the switch to electricity with the official charger and it's booting again! I don't know what just happened, maybe it was a battery desync or something? Really weird... my heart rate is back to normal
Why is that? Is the Switch unhackable permanently or do the ones doing the CFW not care to do one? Leaving in sleep mode is no good option because then you need to babysit the battery. The tethering is a serious PITA too. I also don't care about online so that isn't an issue.by the time now, i think there is no method to have a permanent cfw in the console. What i use to avoid jig is autoRCM but if i turn off the switch i need to inject a payload or it will be in black screen (RCM)
Should be, yes. You can test it yourself. The instructions are in the thread.Is 90DNS working right now?
Fuses prevent downgrades. Once burnt, they cannot be undone without performing micro soldering (these pins are smaller than bacteria) or replacing the motherboard of the Switch.Okay so I was on OFW 1.0.0 only showing 1 fuse blown.. perfectly fine.
Installed SXOS 2.5.2 but every time I booted to CFW.. it would make it to the dashboard and crash with an error 2254-0006. So i only assumed some issue with 1.0.0 and SXOS 2.5.2 must be amuck. So rebooted back into SXOS Config and made me a emuNAND and enabled it.. was still unable to boot without crashing to error..
Went and found an older version of SXOS 2.2 that allowed me to boot..( keep in mind I enabled emuNAND on 2.5.2) so I booted up on SXOS 2.2 on OFW sysnand.. great! So I ran through choiDujourNX to update to 6.20.. enabled AutoRCM.. rebooted and could not get back into the OS. Come to find out I choiDujourNX updated my OFW to 6.20.. because when I loaded up 2.2 instead of 2.5.2 the emuNAND did not stay in effect..(didn't notice)... so started messing around and probably turned off AutoRCM booted OFW 6.20 burning all 8 fuses!
That being said.. everything works fine like that.. and I can actually choiDujourNX update my FW from 1.0.0 all the way up to 6.20 and back down as I choose.. Though I thought burning fuses means I cant downgrade? Please explain this situation I have got myself into lol.
Also before i did anything I made a complete Hekate nand backup including BIS keys.. the works.. I got everything clean.. Just curious what options I still have to retaining 1.0.0 CFW in the event coldboot comes about.
Did you try the 883e Tinfoil build from Lavatech?
Got it, you're defintely right. But can you please explain why one needs to update twice to have exfat support?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).
Hi everyone!
I just got a hackable Switch unit on fw version 4.1.0 and I am just wondering whether or not to update it to 6.2.0. I have already ordered my payload injector dongle and am waiting for it to arrive.
I want to use it to play my back-ups, but I also want to buy some digital-only games and play other official games online.
Should I update normally or should I use something like ChoiDujourNX, because as far I heard using that updates the console without burning fuses, thus gives the ability for a downgrade, right?
What are my advantages on 4.1.0 as compared to 6.2.0?
I don't mind waiting for the dongle, but if the only way to play online is on the latest firmware what is the reason for staying on 4.1.0?
Can ChoiDujourNX update my firmware to 6.2.0 (and give me access to the e-shop and online play) without burning fuses?
oh okay just wonder because a person i follow on YT had battery de-syncing issues after using linux, thats when your switch randomly shuts off even with a full charged battery. he fixed it by unplugging the switch battery and holding down the power button for 15sec.Nope
If it says software update, that is a game update. If it says system update, the only possible scenario I can envision is that there was a pending system update for your SysNAND before you created EmuNAND which got carried over. Yes, you can get pending system updates if you are already on 6.2 if you updated offline but connected the console online at any point before updating.This worked great, thank you.
When i start a game im getting a message saying the system needs to update even though my emunand is on fw 6.2?
Is this solved by finding a game update and installing it via tinfoil also?
Since Nintendo doesn't provide exFAT support in their console, it has to be downloaded separately. And you can only trigger this download if your firmware doesn't currently support exFAT. Furthermore, if your firmware already supports exFAT, you can only update officially to the non-exFAT version of the latest firmware. An example will help illustrate.Got it, you're defintely right. But can you please explain why one needs to update twice to have exfat support?
Nope.Hey guys I hope you can help me
I did a clean backup of my 5.1.0 switch and then updated to 6.2.0 with choidujournx.
When moving files on my Computer I accidentally deleted my backup.
Is there any safe (I know nothing is 100% safe) method to downgrade and do a clean Backup again?
There were no exfat drivers installed since there hasn't been a sdcard in my switch before I started hacking it.
Also I didn't install any games yet, but I've been using homebrew (choidujournx, Lockpick).
Thanks in advance and hello gbatemp community (this is my first post )
Sure I guess. Not sure why you don't just send Hekate as a payload instead of SX OS unless you don't have a USB-C cable. Even with only the SX Pro, you can just download the boot.dat for SX Gear and rename Hekate to payload.bin so the SX Pro loads automatically into Hekate."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)."
So how do i proceed to restore my Nand using SXOS ?
Do i have to erase everything on my SD card and just simply put the latest version of SXOS and use Hektake in RCM mode to restore my Clean NAND ?
Then, i'll create an SDEmunand and then put my previous files back on my microSD card correct ?