Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,102,851
  • Replies Replies 47,953
  • Likes Likes 66
Giving botw another go. Obtained 2 nsps for UPD 1.5 and DLC and installed to SD card with SX OS installer (the regular installer in the album). I'm using the actual game cart and still have the 1.5 update installed in system storage from before I added CFW.

DLC is not showing up- do I need to delete the legit update from system storage so the system recognizes the UPD nsp I installed with the DLC nsp (i.e. do these 2 nsps work together?)

Or do I need to grab an XCI/NSP of the game itself? This my first time even trying a cart while running CFW..

Anyone have any ideas?
 
Hello! I'm late , I know. But I'd like to buy a switch in these weeks. I was wondering how can I check if I go into a physical store if the switch is hackable. Can I understand it from the serial on the box?

My goal is to hack the switch and use the sysnand for online and emunand for the rest.
 
Last edited by codeluca,
Guys I hacked my switch and now I can't use youtube.

Is there anyway to use YouTube or access Internet in hacked switch?
 
Is EmuNand a thing now with SXOS? Can I play offline with emunand while using a clean SysNand to play online with legit bought games? Should I use 2 SD cards or is this not needed with XCI dumps? I see that EmuNand is planned for Atmosphere, any news when it's coming?
 
Can i inject hekate payload using android telefon, did someone try? Laptop is broken, i need to make nand backup.
 
Last edited by Zdobuzdo,
Can anyone help me with EmuNAND.
I set it up on hidden partition then i copied back all my files to my SD card.
YES BOOT.DAT AND LICENSE ARE IN THE ROOT OF THE SD CARD.
YES MY SD CARD IS REAL WITH NO ERRORS AND A 1 YEAR WARRANTY.
BUT i KEEP getting the same thing. BOOT.DAT ERROR when booting up sx os payload.
LIKE wtf. I did this for 5-6 times already. I've reformatted using GUIFORMAT to fat32.
I used EMUNAND on SD files as well BUT get a black screen when booting it up.
SO Any help will be nice and NO ISSUE WITH SD CARD.
 
Have Switch 6.2 Switch with SXOS installed (2.5.2 I think with no emunand enabled in it) and AutoRCM installed.

What happens to my switch if it goes to absolute zero battery? I remember reading in some of the guides (sorry, don't remember which in particular) that I should never load the normal official firmware. Is it fine loading it? Am I even able to do it?

Thanks in advance!
 
Have Switch 6.2 Switch with SXOS installed (2.5.2 I think with no emunand enabled in it) and AutoRCM installed.

What happens to my switch if it goes to absolute zero battery? I remember reading in some of the guides (sorry, don't remember which in particular) that I should never load the normal official firmware. Is it fine loading it? Am I even able to do it?

Thanks in advance!
Your console will always charge, with or without AutoRCM. The only thing AutoRCM changes when it comes to charging is the charge rate in RCM which is reduced and is something you will experience if your console runs out of battery with AutoRCM enabled. Also with AutoRCM, you can't load the normal official firmware unless you perform a system update.
 
  • Like
Reactions: ReDEyeDz
Your console will always charge, with or without AutoRCM. The only thing AutoRCM changes when it comes to charging is the charge rate in RCM which is reduced and is something you will experience if your console runs out of battery with AutoRCM enabled. Also with AutoRCM, you can't load the normal official firmware unless you perform a system update.
So theoretically I can bring it back to the official one, right? By system update you mean updating to the new version like 7.0? What if I'm on the latest already?
 
So theoretically I can bring it back to the official one, right? By system update you mean updating to the new version like 7.0? What if I'm on the latest already?
If you're on the latest, then there is no risk in removing AutoRCM accidentally. The only other ways of disabling AutoRCM include manually removing it with the tool used to enable it or restoring a boot0 that wasn't dumped with AutoRCM enabled aka a stock boot0.
 
  • Like
Reactions: ReDEyeDz
If you're on the latest, then there is no risk in removing AutoRCM accidentally. The only other ways of disabling AutoRCM include manually removing it with the tool used to enable it or restoring a boot0 that wasn't dumped with AutoRCM enabled aka a stock boot0.
I'm not going to do anything like that, I'm just genuinely curious about what can I possibly do wrong to screw something up to avoid it.
 

Site & Scene News

Popular threads in this forum