Yes, the web site was down. However, you can just replace the 2.5.3 boot.dat file on your SD card, with the newer boot.dat file that you download from their web site.
Hello everyone. I'm currently a sx os user, but I was trying to make Kosmos work but I have a problem. I've followed the set-up guide, prepared my SD and used the sx os to inject the henkate payload, no problem there, the problem is in henkate itself.
When I enter henkate and choose the option cfw it loads then freezes when "loaded pkg1 & key blob" appears.
When I enter henkate and choose the option cfw it loads then freezes when "loaded pkg1 & key blob" appears.
Do you think I'm okay to go online with sysNand et run xci on emuNand ?
Brand new switch 7.0.1
1 - Factory reset of sysnand and backup raw + boot0/1 withn Henk
2 - Creating emunand on SD with SX OS
3 - Booting into emunand (airplain mode) and run XCI
4 - Disabling AutoRCM
Brand new switch 7.0.1
1 - Factory reset of sysnand and backup raw + boot0/1 withn Henk
2 - Creating emunand on SD with SX OS
3 - Booting into emunand (airplain mode) and run XCI
4 - Disabling AutoRCM
Hey, guys been gone for a minute lol had sold my switch about 6-7months ago and was missing some of the games that I used to play and bought another hackable variant. My question now is I had started that switch with ReiNX and ended up switching to SX OS and was the last CFW I ran I just don't feel like spending $32 dollars on another license if anyone can give me a quick update on what I've missed and what CFW is worth getting into. Another question is it worth updating to 7.0.1 or just stay in whatever firmware the switch is on I mostly want to be able to add themes like I used to with gold leaf and install games Idk if cheats are possible either or if is an SX OS only thing.
You won't be immediately banned for going online with a hacked Switch. You should have enough time to go online, update to the latest firmware, and link a Nintendo Accout.
There is no way to install Atmosphere or any CFW on the Switch. And you don't really need to use bricmii regularly. Just use it once to enable AutoRCM then switch back to fusee_primary.bin. You will only ever need bricmmii again if you want to enable or disable AutoRCM which should be almost never.
That sounds like a good plan. You shouldn't be banned as long as you perform all CFW and homebrew in EmuNAND as well as keep it 100% offline.
Any of the free CFW are fine. You can even just keep more than one CFW on your SD card so you swap between them at a moment's notice.
Also 7.X is still a little buggy especially with certain homebrew applications. Tinfoil for example cannot install .NSP files from the SD card on 7.X. However USB and network install still work even on 7.X. Other title installers such as Lithium and Goldleaf work as long as you are using the latest versions. Otherwise, 6.2 is still the best firmware to be on as long as you don't play online.
I stopped following the scene around the time SXOS released their first version of emunand which wasn't real emunand so I'm not up to date on the latest. I have a switch with FW 6.2 (or w/e the latest is necessary for Let's Go) that has the fusee-gelee vulnerability and has never been modded. My questions are:
- If I update to the latest FW and decided to use the fusee-gelee exploit am I losing out anything by not using it on my current FW (6.2)?
- Is the SXOS emunand legit this time?
- Are there any ban risks by using SXOS emunand?
- Atmosphere was said to be developing an emunand that's safer than the one SXOS developed, is this still true and in works?
Thanks in advance.
- If I update to the latest FW and decided to use the fusee-gelee exploit am I losing out anything by not using it on my current FW (6.2)?
- Is the SXOS emunand legit this time?
- Are there any ban risks by using SXOS emunand?
- Atmosphere was said to be developing an emunand that's safer than the one SXOS developed, is this still true and in works?
Thanks in advance.
Well hot off the press is firmware 8.0 so definitely don't update to the latest firmware. Even if you just update SysNAND, it can cause issues like it did when 7.0 was released. Other than that, EmuNAND is pretty legit as no one has been banned for using it. And Atmosphere is now actively working on EmuNAND if you check their GitHub page. Whether its safer than the one TX made may either just be hot air or anti-TX sentiment. Either way, its too soon to tell.
Before SX OS V2.5.3 was released, EmuNAND wouldn't boot if SysNAND was on 7.0. Of course the issue was addressed and subsequently fixed however I wouldn't be surprised if this issue returned in firmware 8.0 and I am not willing to test that theory out.
Since SciresM made a post about not updating past 7.0.1 if you want to use Deja Vu in the future, can someone ELI5 what would make Deja Vu better than using the current RCM exploit for an unpatched unit?
warmboot
--------------------- MERGED ---------------------------
DO NOT UPDATE TO 8.0
If you do however and you have an unpatched switch, it is possible to restore/manually downgrade your console
OK but I'm 5YO. Does that mean something like what Enso is for Vita where the exploit to use CFW is just applied automatically on boot so as to be completely transparent to the user? Or is Enso a coldboot? I haven't even considered going to 7.0.1 yet (still on AMS 0.8.1 on firmware 6.2.0) so not eager at all to upgrade to 8.0.0. Switch is always on airplane mode
Last edited by nutsack,
How Deja Vu will work is you launch PegaSwitch and then from there you will run a script that launches Deja Vu. This is why its considered "warmboot" because it is applied while the console is already running. Its extremely similar to CFW on the PS4 and the Wii U via Mocha aka without CBHC.
I formated it to fat32... did the back up... and when I go to Launch I still dont see anything?? it just says
Payloads
More Configs
No Main Config found.
I did everything on the text based guide
( When I launch the payloads on tegra this is the message I see)
ploading payload
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
The files on my Sd card are: hbmenu.nro,atmosphere,bootloader,edizon,nintendo and switch
Payloads
More Configs
No Main Config found.
I did everything on the text based guide
( When I launch the payloads on tegra this is the message I see)
ploading payload
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
The files on my Sd card are: hbmenu.nro,atmosphere,bootloader,edizon,nintendo and switch
I have bought a (secondhand) unpatched switch. I was checking the settings and clicked on tv output (in handheld mode) and it only shows 480p, while my patched switch 480 p 720 and 1080p. I only play handheld mode so i assume its not a big deal, but i am curious to why this unpatched switch is just showing 480p
It runs on FW 7.1, no CFW of any sorts yet.
I did attemp a factory reset.
It runs on FW 7.1, no CFW of any sorts yet.
I did attemp a factory reset.
Is it possible to restore a sysNand backup from an older firmware (let's say 6.0) to a newer firmware (let's say 7.0.1) ?
If it's not possible we have to do a sysNand backup at every firmware ?
Thanks
If it's not possible we have to do a sysNand backup at every firmware ?
Thanks
I believe so long as you made the backup yourself and it's your switch, it ought to work.
Meanwhile, I ended up upgrading to 8.0.0 in an attempt to get FF10 for Switch having already pre-purchased it, it made me download the update and now my console won't go into RCM mode no matter what I do (tinfoil, or jig) the jig looks like this:
And as you can see the pins are significantly smaller than other jigs. Any way to get this jig to work?
Meanwhile, I ended up upgrading to 8.0.0 in an attempt to get FF10 for Switch having already pre-purchased it, it made me download the update and now my console won't go into RCM mode no matter what I do (tinfoil, or jig) the jig looks like this:
And as you can see the pins are significantly smaller than other jigs. Any way to get this jig to work?
Hopefully someone can answer this for me before I start playing around with my switch.
I currently have a switch which uses sxos. I'm able to install games fine on to it no problem. Are these games installed on the system no matter what cfw I booted in to? If I was to install atmosphere as well on my sd card and boot to that, will the games all show as working still and saves be in tact or is everything different for different cfw?
I currently have a switch which uses sxos. I'm able to install games fine on to it no problem. Are these games installed on the system no matter what cfw I booted in to? If I was to install atmosphere as well on my sd card and boot to that, will the games all show as working still and saves be in tact or is everything different for different cfw?
