Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,179,494
  • Replies Replies 48,015
  • Likes Likes 66
Maybe partition my sd card to have XS on one partion and Atmos on the other, and just install the games that need modern firmware on the atmos partition?
You could give this guide a try. It's not the easiest one to follow and most of us will suggest switching to Atmosphere instead.

thats disappointing... installing each game makes file management a nightmare.
You could get yourself a MIG Switch flashcart but going through games on it can be a hassle, especially if you have more than e.g. 10 games on it.
 
I meed to do some updating to the switch. I see atmosphere supports 20.3 now. But hekate doesnt?
What about 1.5.6 sys-patch. It just says 20.0+ so I am not entirely sure.

Am I able to update those to 20.3 without issues?
 
Hi all,

Went to play my modded switch for the fist time in ages and it looks like it wasn't set in the dock properly and the battery is now drained :cry:

If I connect the Switch to my PC and run TegraRcmGUI, the app sees the RCM and lets me inject the payload.bin file. I then see the Atmostphere splash screen and the white logo; TegraRcmGUI then show a "red" switch icon and the Switch is just showing the battery charging symbol.

Do I just need to wait for the Switch to slowly charge via the PC's USB socket or is it not actually charging at all?

TIA for any help
 
But hekate doesnt?
Hekate doesn't require an update yet.

What about 1.5.6 sys-patch. It just says 20.0+ so I am not entirely sure.
Works perfectly fine on my end.

Am I able to update those to 20.3 without issues?
As long as you don't use a homebrew app that hasn't been updated in a while, you shouldn't run into issues.

Do I just need to wait for the Switch to slowly charge via the PC's USB socket or is it not actually charging at all?
Just let it charge for a while and see if it works after that.
 
Hekate doesn't require an update yet.


Works perfectly fine on my end.


As long as you don't use a homebrew app that hasn't been updated in a while, you shouldn't run into issues.


Just let it charge for a while and see if it works after that.
Thank you. The only homebrew I really use is Jksv and DBI. Oh and tinfoil.
So I am good to go I guess
 
The problem is not that I can't install the file with DBI (installing it at all costs isn't the goal), but that I can no longer trust in the integrity of any XCI or NSP file if problems are reported despite a valid signature and hash. This is the basis for how I check if an XCI or NSP file is OK:
invalid hash = corrupt crap that shouldn't be touched with a 10m pole
invalid signature = I rather avoid this for base games and patches, but tolerable as far as I know when there's no alternative (often the case for DLC, somehow...)

That's why I need to understand what's going on with this game.
for what it's worth invalid hash doesnt necessarily mean corrupt. a lot of converters that convert xci to nsp (and some installers that install xci to console) don't bother rewriting the cnmt with the modified hashes when it modifies them into installable digital games, so the programs that check nsp will say the hash is invalid, because it verifies the hash by comparing each file with the hash in the cnmt

the switch does the same thing in data management if you check for corrupted data, it just compares the hash of the file with the hash in the cnmt. so it will report corrupted data if the cnmt wasnt rewritten, but it doesnt mean the files are necessarily bad or corrupted (the console doesnt care about hashes and will run everything even if the hashes don't match, unless you use the "signature" patch that ignores invalid hashes)

i probably recommend ignoring files with invalid hash still though, because there is no reason to use them when you can get the xci directly and install that instead. a nsp with invalid signature could in theory be anything. nx game info will tell you if the file has dangerous permissions but I dont know how well it can be trusted. but still there's no reason for anyone to ever use converted nsp when xci are right there

hello. Just bough an OLED Switch and going to mod it. How do I play on LAN Worlds in Minecraft (joining other worlds in my LAN, for example on Windows PC).
I assume I would have "emulate" that I have Nintendo Switch Online membership and an Nintendo Account - how tho? Is there a software that does it?
there is this but I dont know if it helps for lan (or if it's even needed for lan multiplayer, I dont play minecraft on switch)

 
  • Like
Reactions: Nynrah and Blythe93
Thank you. The only homebrew I really use is Jksv and DBI. Oh and tinfoil.
So I am good to go I guess
Not sure about Tinfoil, but I guess it does work on latest firmware.

It's now stuck on the "nintendo switch" logo :cry:
Make a backups of your atmosphere and bootloader folders and, after that, get fresh latest Atmosphere and Hekate builds from their repositories. Hopefully, it'll work this time around.
 
there is this but I dont know if it helps for lan (or if it's even needed for lan multiplayer, I dont play minecraft on switch)
on banned though? does it connect to servers that can get my console banned? even though i blocked Nintendo servers?
 
on banned though? does it connect to servers that can get my console banned? even though i blocked Nintendo servers?
I dont know how it works, but it bypasses the nintendo servers to connect to the game's servers without it. blocking nintendo servers intentionally is functionally the same as being banned though

it might be worth asking about how it works and what it does, it might not necessarily be safe to use if you're not banned and want to be able to unblock nintendo later. I guess it's possible that the servers for the game can see you're skipping the nintendo servers and could communicate back to nintendo about this
 
  • Like
Reactions: Blythe93
Hello, is there an easy way or a program on windows to tell if my .xci files are bad or corrupted?
I need to check some of my xci
 
  • Like
Reactions: Blythe93
Hello, is there an easy way or a program on windows to tell if my .xci files are bad or corrupted?
Most of the time, I use NxFileViewer. Just make sure that you have the latest prod.keys.

NSC Builder and NSFW (Nintendo Switch File Wizard) apparently can do that as well, but I'm yet to give them a try.
 
Okay, I need soome advice. Two things. Quick Backstory. I modded my v1 Nintendo Switch over a year ago. I haven't updated it since because I havne't needed to but at this point, I haven't used it in over like 6 months. Do I need to update it if I want to play newer games? And if so, how do I update it?

Also, I currently have a crappy 120gb microsd in it right now but can onnly use like 80gb of it. I have a spare 500gb micro sd laying around. What do I need to do in order to just use that one? Can I just pop it in the Switch?
 
So just to confirm—if I’m using a first-gen Nintendo Switch (from 2017 or early 2018), do I still need to go through the RCM + payload injection process every time I fully power off the console? There’s no permanent software/hardware-only way to boot directly into custom firmware without doing that, right?
 
So just to confirm—if I’m using a first-gen Nintendo Switch (from 2017 or early 2018), do I still need to go through the RCM + payload injection process every time I fully power off the console? There’s no permanent software/hardware-only way to boot directly into custom firmware without doing that, right?
Assuming it is an unpatched V1 console:
  • There is an option (named AutoRCM in Hekate) that, if enabled, makes the console boot always in RCM, so you do not need to use the jig every time.
  • Note that updating OFW normally will disable AutoRCM and you will then need the jig again, to boot Hekate and re-enable it.
  • In any case, you still need to inject a payload via USB anyway, so you need another device that can do that. I prefer an Android device with the Rekado app and an USB OTG cable, but others use a PC, or a dedicated payload injector dongle.
If you are willing to mod the hardware:
  • You can install a RCM x86 / SAMD21-based modchip to automate the RCM boot and payload injection.
  • Or, you could install a HWfly (old, expensive, very hard to find) or RP2040-based Picofly (common, cheap, plentiful). These work for patched V1, V2, Lite and OLED consoles too. They force a glitch during boot to make the console boot straight to a payload.
IMHO, It's a bit of a shame to mod the hardware on a soft-moddable V1, but they are becoming older, and will soon need repair anyway (battery, thermal paste, fan...). So I would look into a SAMD21 when that time comes.
 
Assuming it is an unpatched V1 console:
  • There is an option (named AutoRCM in Hekate) that, if enabled, makes the console boot always in RCM, so you do not need to use the jig every time.
  • Note that updating OFW normally will disable AutoRCM and you will then need the jig again, to boot Hekate and re-enable it.
  • In any case, you still need to inject a payload via USB anyway, so you need another device that can do that. I prefer an Android device with the Rekado app and an USB OTG cable, but others use a PC, or a dedicated payload injector dongle.
If you are willing to mod the hardware:
  • You can install a RCM x86 / SAMD21-based modchip to automate the RCM boot and payload injection.
  • Or, you could install a HWfly (old, expensive, very hard to find) or RP2040-based Picofly (common, cheap, plentiful). These work for patched V1, V2, Lite and OLED consoles too. They force a glitch during boot to make the console boot straight to a payload.
IMHO, It's a bit of a shame to mod the hardware on a soft-moddable V1, but they are becoming older, and will soon need repair anyway (battery, thermal paste, fan...). So I would look into a SAMD21 when that time comes.

Thank you , I found this adapter on Ebay https://www.ebay.com/itm/396317424771
And we still need to inject the payload via USB anyways correct?
 
  • Like
Reactions: Nephiel
for what it's worth, autorcm is only removed if you update sys mmc without cfw. so just boot sys cfw and update from system settings (dont sideload it with daybreak, nintendo can probably tell that you're suddenly on a higher firmware version despite not downloading and installing it from their servers)

but you want to be careful if you have anything like tinfoil self installer on your homebrew, or if you have custom modules that might change the way the console or the os behaves. if you only need to update then it's safer to rename your atmosphere folder on the sd card and extract a fresh version in its place to ensure you run sys cfw without any extra modules or mods or anything that could behave differently and be detected

it's totally safe btw, just ask scires how many consoles he's had banned since 2018 (spoilers: it's 0)
 
  • Like
Reactions: Blythe93
If you got firmware 20.1.1 installed with Atmosphere 1.9.1, would you be able to run a game whose latest update claims to require firmware 20.3.0? Strictly I'd guess not, but the difference looks small enough to double check.
 

Site & Scene News

Popular threads in this forum