My current firmware version is 3.0.0
1) Is it safe to install firmware updates by using NSP files using Tinfoil?
2) Is it worth to use more complicated versions of updating in order to not burn any efuses?
- You can't install firmware updates as .NSP files
- Although they aren't really that complicated, they are definitely worth using
I have recently got an unpatched switch for homebrew/backups but it's still in the box (XAW1004600xxxx). This version should be 4.0.1, or perhaps 3.0.1/3.0.2, correct? I've read a few places that there's merit to having a switch lower than 3.0.1 for an untethered coldboot exploit in the future. Is it worth to see if I can get a lower version? Has there been any progress on that exploit?
There has been no progress on any other exploits.
There was a thread created informing people that Atmosphere could run on 6.2.0 if you provided the required keys. Does anyone know why it got removed? All notifications regarding the thread also vanished from my notifications page.
Most likely because they were distributing the keys necessary to launch Atmosphere which is against the rules of GBATemp.
i was just about to ask which firmware i should put on my emuNAND and then I saw it mentioned above that 5.1 is the current best for CFW. I'll definitely go with 5.1 then as you are supremely well informed and a hero of this forum. but just so I can learn, may I ask why 5.1 is considered the best? I know it can run Devmenu which is useful if you want to delete game updates without deleting the whole game. i was thinking of using 5.1 for this feature alone, unless there is some other way to do this on 6.1
also while doing some reading I saw a post where they said that loading into sysNAND after running emuNAND caused their sdcard to be completely wiped. I'm assuming this no longer happens cause of something about there being an emutendo folder, but i just want to check first as in a perfect world I'd like to be switching back between my emuNAND and sysNAND.
DevMenu is the only tool that can do that hence why 5.1 is considered the best firmware for CFW.
Yes, the sole purpose of the Emutendo folder is to allow safe swapping between EmuNAND and SysNAND.
If I'm using Kosmos, I notice it comes with exefs patches. Is that all that I need or do I also need the kip patches from The-4n? Secondly, what are the kip patches and why would I need them versus not? Thanks! (I know they are kernel patches, but what are they patching?)
The patches the 4-n compiles are for using Fusee as the bootloader. Kosmos' patches are for using Hekate as the bootloader. In both cases, the CFW is still Atmosphere but depending on the bootloader you use, it will require different patches.
The kip patches have a plethora of functions such as enable backup launching (of titles you don't own), enable the nogc patch, and disable signature checks on unsigned .NSP files such as homebrew.
How big is SX EmuNAND suppose to be? Could the size not be the same for different users?
Mine is about 30 gb with lots of 3-4 small parts (like part 1, 2, 3, etc). I thought it was about 15 gb or so.
When EmuNAND was ran from the NAND, it was 15 GB because obviously you can't fit the entire NAND within the NAND. Now that EmuNAND runs from the SD card, it can achieve full size which is around 30 GB.
So 6.2.0 was hyped as armageddon for Switch homebrew/piracy, but now it sounds like 6.2.0 CFW isn't too far off. I just ran across a video on youtube acting like 5.0.0 was going to kill homebrew/piracy at the time but we know better now. Is this normal? Were there more firmware that were supposed to be uncrackable at the time?
Well 6.2 still has not been publicly cracked so I wouldn't count your chickens before they hatch.
So, I upgraded to 6.2.0 and just successfully downgraded to 6.1.0. When I am ready to upgrade again (On December 6th at 11pm
), if I just restore my full NAND backup and all that jazz, will I boot back up into 6.2.0 and I'll be able to pick up where I left off? I removed Network Connections and put it into Airplane Mode (trying to not get banned).
If you made the NAND backup when you were on firmware 6.2, then yes. Make sure you also restore boot0/boot1 as well as the rawnand as all 3 files are needed to complete your NAND.