Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,146,143
  • Replies Replies 47,990
  • Likes Likes 66
So I am currently running Version 8.0.1 (AMS 0.8.10) on my switch. What I want to do is update that to a newer version of ams or fw? I've looked but I cant find a video on how to do this most of the videos I find are starting from scratch and require formatting my 400gb sd card which is full... I'd like to try and avoid doing so if possible. My question is this even possible? Reason why is I'd like to update is do to newer games not wanting to install asking for higher fw requirements on gold leaf and tinfoil. When I try to convert them from xci to nsp using 4xci it gives me an error aswell. I'm thinking because keys are outta date? It works with older xci files.
(Method of installing:I use kosmos toolbox to boot into hekate Pull sd card out Transfer xci or nsp Put sd card back Load payload = hekate_ctcaer_4.10.1.bin Use gold leaf or tinfoil to install)
Always worked but with these newer games I cant seem to get any of it to work and it gives higher fw required error. Any help would truly be appreciated I've looked and commented on older forums but with no luck.
 
HI GUYS! so I got my hand on an unpatched switch, does the update version it's on (idk if I would call this the firmware sorry I'm stoopid:P) matter when it comes to hacking it? And by this I mean Homebrewong it with atmosphere custom firmware.:whip:
 
So I am currently running Version 8.0.1 (AMS 0.8.10) on my switch. What I want to do is update that to a newer version of ams or fw? I've looked but I cant find a video on how to do this most of the videos I find are starting from scratch and require formatting my 400gb sd card which is full... I'd like to try and avoid doing so if possible. My question is this even possible? Reason why is I'd like to update is do to newer games not wanting to install asking for higher fw requirements on gold leaf and tinfoil. When I try to convert them from xci to nsp using 4xci it gives me an error aswell. I'm thinking because keys are outta date? It works with older xci files.
(Method of installing:I use kosmos toolbox to boot into hekate Pull sd card out Transfer xci or nsp Put sd card back Load payload = hekate_ctcaer_4.10.1.bin Use gold leaf or tinfoil to install)
Always worked but with these newer games I cant seem to get any of it to work and it gives higher fw required error. Any help would truly be appreciated I've looked and commented on older forums but with no luck.
Delete the “atmosphere”, “sept”, and “bootloader” folders on your SD card
Download the latest atmosphere and hekate release (https://github.com/Atmosphere-NX/Atmosphere/releases & https://github.com/CTCaer/hekate/releases)
Extract both to your SD card.
Delete the sd:/atmosphere/reboot_payload.bin file and throw a copy of hekate_ctcaer_5.1.1.bin file from the latest hekate release in sd:/atmosphere and rename it to reboot_payload.bin
Throw another copy of hekate_ctcaer_5.1.1.bin on whatever device you use for injecting payloads, and inject it.
Then the rest is as normal except hekate will have better looking UI and more features.

EDIT: then for updating the system you can use ChoiNX or the regular system updater.

You may also need sigpatches for certain things, you can find them on this forum somewhere.
 
Last edited by ZachyCatGames,
  • Like
Reactions: TechFumaMota
Delete the “atmosphere”, “sept”, and “bootloader” folders on your SD card
Download the latest atmosphere and hekate )
Extract both to your SD card.
Delete the sd:/atmosphere/reboot_payload.bin file and throw a copy of hekate_ctcaer_5.1.1.bin file from the latest hekate release in sd:/atmosphere and rename it to reboot_payload.bin
Throw another copy of hekate_ctcaer_5.1.1.bin on whatever device you use for injecting payloads, and inject it.
Then the rest is as normal except hekate will have better looking UI and more features.

EDIT: then for updating the system you can use ChoiNX or the regular system updater.

You may also need sigpatches for certain things, you can find them on this forum somewhere.

So I followed instructions it seems to have updated hekate like you said ui looks nicer theres nothing in launch or more configs?
When I load the payload bin or rcmloader just takes me back to hekate? Any ideas how to boot into switch?
 
APX driver not installed. I bought 2 rcm jigs, I have tried putting switch into RCM and using tegra however nothing happens and when I click on install drivers it keeps saying APX driver is missing so I click install and I get a message saying nintendo switch ready to use but tegra still showing NO RCM. I have also tried using Zadig to install APX that way but still no luck. If anyone can please help me I will be forever grateful. I am unsure if switch is even entering RCM but I assume it is as just black screen and wont turn on unless I keep power button pressed in for a while and then take finger off then press power button again
 
Delete the “atmosphere”, “sept”, and “bootloader” folders on your SD card
Download the latest atmosphere and hekate
Extract both to your SD card.
Delete the sd:/atmosphere/reboot_payload.bin file and throw a copy of hekate_ctcaer_5.1.1.bin file from the latest hekate release in sd:/atmosphere and rename it to reboot_payload.bin
Throw another copy of hekate_ctcaer_5.1.1.bin on whatever device you use for injecting payloads, and inject it.
Then the rest is as normal except hekate will have better looking UI and more features.

EDIT: then for updating the system you can use ChoiNX or the regular system updater.

You may also need sigpatches for certain things, you can find them on this forum somewhere.
Got it running just needed latest sigpatches thank you sir you are a genius now to update it using Choinx thanks a billion!!

Edit: so everything works fine except HBmenu
It wont go into where screen shot icon was I gotta hold L and start app to acsess.
And kosmos tool box no longer works or kosmos udater.? Not that I need em but just curious
 
Last edited by TechFumaMota,
OMG please ignore my post....I have done it. I didn't realise I was using the power cable and I have switched cables and now working fine :-)
 
Hi guys, I saw some ppl giving advices that you should use vanilla atmosphere instead of kosmos/hekate combo. Can someone pls explain to me why ?
I've been using kosmos for quite some time now and havent found out any big troubles yet (although small troubles occured : homebrew buttons no longer works after 9.0 update even if I deleted everything and downloaded all the new files from sdsetup site)
 
Hi guys, I saw some ppl giving advices that you should use vanilla atmosphere instead of kosmos/hekate combo. Can someone pls explain to me why ?
I've been using kosmos for quite some time now and havent found out any big troubles yet (although small troubles occured : homebrew buttons no longer works after 9.0 update even if I deleted everything and downloaded all the new files from sdsetup site)
There’s people that recommend fusee over hekate? Lol
Hekate + Atmosphere is factually superior to vanilla Atmosphere in literally every way.
Only reason to ever use fusee is if you’re making a bug report on the Atmosphere github.
 
  • Like
Reactions: Lumona
Hi all,

Because 9.1 update the gc, I wanted to dump some of my gc to install them directly on my switch.

I downgraded with Choidujour to 8.1 to be able to read gc.
Then I tried to dump gc to NSP using NXdumptool.
Then I tried to install it back using Goldleaf but I got an "invalid NCA" error (2002-4518 (0x234C02) is the error code).

Anyone know what it can be ?

I tried this without sucess :
  • Dumping gc again
  • Updating to 9.1 before installing NSP
  • Getting the gc off my switch before installing
  • Removing the game before installing it
Try installing it with Gamecard Installer NX as Goldleaf is buggy

HI GUYS! so I got my hand on an unpatched switch, does the update version it's on (idk if I would call this the firmware sorry I'm stoopid:P) matter when it comes to hacking it? And by this I mean Homebrewong it with atmosphere custom firmware.:whip:
Unpatched consoles refer to the hardware not being patched as the exploit relies on the hardware and not the software aka the firmware.

Hey man, thank you for your reply. How about kosmos ? Is it that bad / crap as they said ?
Kosmos uses Hekate and Hekate is better than Fusee so...
 
Noticed a couple of games I can't get to work are NSPs converted from XCIs. Is there something specific I have to do to get these to work?
 
Hello, I've read the past few dozen pages of this thread and feel like I have a good grasp of what I am going to do.

I'm planning on keeping my sysMMC on the OFW for official online features, and running cfw on an emuMMC for offline fun stuff. I'm on an unpatched switch running 9.1, and planning on making my right joy con release button an RCM switch so I can decide when to boot to RCM. I'll be using an RCMLoader One to inject the payload. I do not care about burning fuses since I'm on 9.1 already anyway.

1. If I want to boot into my OFW in sysMMC, will I have to go through RCM and choose the stock boot in sysMMC to play online, or can I just bypass RCM completely and let it boot normally?
2. Do people go through RCM to boot an OFW just to bypass the fuse burning, or is there a ban risk by not doing so? (I can't imagine there is any more of a risk, since I won't have any CFW or homebrew on my sysMMC.
3. Is never connecting to a WiFi network sufficient for my CFW instance, or should I install 90DNS/Incognito_RCM for safety? If so, which is preferred? Do they use the same database of hostnames/IPs to block or is one more up to date than the other?
4. In my setup, ALL modded content will be on the SD card, correct? For instance, removing my joy con mod and formatting my SD card will essentially make all changes reversed and (so long as no online contact has been made in CFW) for all intent and purposes back to a vanilla device?

Thanks so much in advance, and for all of the support you guys are giving here. You rock!
 
Noticed a couple of games I can't get to work are NSPs converted from XCIs. Is there something specific I have to do to get these to work?
What CFW are you using?

Hello, I've read the past few dozen pages of this thread and feel like I have a good grasp of what I am going to do.

I'm planning on keeping my sysMMC on the OFW for official online features, and running cfw on an emuMMC for offline fun stuff. I'm on an unpatched switch running 9.1, and planning on making my right joy con release button an RCM switch so I can decide when to boot to RCM. I'll be using an RCMLoader One to inject the payload. I do not care about burning fuses since I'm on 9.1 already anyway.

1. If I want to boot into my OFW in sysMMC, will I have to go through RCM and choose the stock boot in sysMMC to play online, or can I just bypass RCM completely and let it boot normally?
2. Do people go through RCM to boot an OFW just to bypass the fuse burning, or is there a ban risk by not doing so? (I can't imagine there is any more of a risk, since I won't have any CFW or homebrew on my sysMMC.
3. Is never connecting to a WiFi network sufficient for my CFW instance, or should I install 90DNS/Incognito_RCM for safety? If so, which is preferred? Do they use the same database of hostnames/IPs to block or is one more up to date than the other?
4. In my setup, ALL modded content will be on the SD card, correct? For instance, removing my joy con mod and formatting my SD card will essentially make all changes reversed and (so long as no online contact has been made in CFW) for all intent and purposes back to a vanilla device?

Thanks so much in advance, and for all of the support you guys are giving here. You rock!
  1. The only reason to boot Stock mode is to bypass the fuse check and prevent fuses from being burnt. If you don't care about burnt fuses and thus downgrading for the sake of better future exploits, then you can boot OFW normally.
  2. There is a ban risk however no one has been banned yet for only having a mismatched fuse count
  3. The only reason to use utilities such as 90DNS or Incognito is to continue using Wi-Fi without fear of getting banned. Using them or having no Wi-Fi settings just simulate a ban
  4. Nintendo does not scan for files on the SD card and even if they did, its extremely unreliable and potentially illegal. There is also no evidence Nintendo tracks how people enter RCM especially since RCM is a part of the console and not a hack
 
What CFW are you using?


  1. The only reason to boot Stock mode is to bypass the fuse check and prevent fuses from being burnt. If you don't care about burnt fuses and thus downgrading for the sake of better future exploits, then you can boot OFW normally.
  2. There is a ban risk however no one has been banned yet for only having a mismatched fuse count
  3. The only reason to use utilities such as 90DNS or Incognito is to continue using Wi-Fi without fear of getting banned. Using them or having no Wi-Fi settings just simulate a ban
  4. Nintendo does not scan for files on the SD card and even if they did, its extremely unreliable and potentially illegal. There is also no evidence Nintendo tracks how people enter RCM especially since RCM is a part of the console and not a hack

For 2. in my case my fuse count would be the expected value, right? If I keep my OFW updated normally and boot without going into RCM it will essentially be a stock setup, therefore retaining the fuse count Nintendo would expect at all times?
 
Awesome, thanks for all of your guidance! One more quick question, if I follow the guide at switch.homebrew.guide sequentially, should I create my emuMMC before booting CFW? It doesn't specify where Atmosphere will run from when it says to launch into it before the emuMMC setup portion of the guide.
 
Hi everyone I solved my last post by moving everything to the desktop and running MakeEmu.exe from there. Unfortunately I have another problem though. The touch screen on my switch doesn’t work so I’m required to delete nyx.bin and use text Hekate, so I have to set up the emummc manually and was following the guide on such meme,many skills dumping ground for manual emummc setup. But I can’t seem to get atmosphere to boot into emu. If I select boot cfw emummc in Hekate it says unknown pkg1 version, if I inject fusee primary directly or select the payload in Hekate it boots to sysnand. My emummc.ini looks like this

[emummc]
emummc_enabled = 1
emummc_sector = 0x12D75800

In MakeEmu.exe it gave me a starting offset and a emummc sector so I put the emummc sector. When I inject fusee primary it says the system version is 9.1.0|AMS 0.10.2|S. I’m expecting it to end with an E if I’m booting to emummc right? It’s definitely booting into sysnand though because I tried changing the color scheme and it always stays the same. Any help would be much appreciated.
 
Hi guys, I'm planning to hack my unpatched switch on 9.1. I want to use emuMMC/emuNAND for offline dirty stuff and sysNAND for online legit playing. Are there any differences as far as security is concerned between sxOS and Atmosphere emuNAND solutions? Is one of them more ban prone than the other? Are there any other major differences between them or is spending 30 bucks for sxOS quite useless now? Thanks a lot in advance for your help.
 

Site & Scene News

Popular threads in this forum