Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,127,460
  • Replies Replies 47,985
  • Likes Likes 66
I just installed my first game with ZeroTwoXci and it works perfect! I only have a question, how can I update the games?
Either update the game officially by downloading the updates from your console or install them offline by downloading the updates elsewhere, such as from the same place where you acquired the .XCI and possibly prod.keys from
 
Either update the game officially by downloading the updates from your console or install them offline by downloading the updates elsewhere, such as from the same place where you acquired the .XCI and possibly prod.keys from

Is there any useful tool to do that? Only have to install it as a game?
 
Is there any useful tool to do that? Only have to install it as a game?
Update files come in .NSP format much like games and DLC so you would install an update file the same way you would with any other .NSP file. In fact, its much easier than installing a .XCI file.
 
Quick Question: I have a brand new in box (hackable lower than XAW10078XX) and have all the right tools (SX PRO) to get the ball rolling. Switch came with original FW4.1 stocked. Should I update my "virgin" Switch to the latest FW6.0 (officially via nintendo) then use it with SX PRO & SX OS 2.0 to move forward? I know some people are having issues with certain games not booting up. Any suggestions on how I should tackle this? Much thanks in advance!
 
Quick Question: I have a brand new in box (hackable lower than XAW10078XX) and have all the right tools (SX PRO) to get the ball rolling. Switch came with original FW4.1 stocked. Should I update my "virgin" Switch to the latest FW6.0 (officially via nintendo) then use it with SX PRO & SX OS 2.0 to move forward? I know some people are having issues with certain games not booting up. Any suggestions on how I should tackle this? Much thanks in advance!
I would recommend using ChoiDujourNX to update to 5.1 since it is the best firmware for CFW currently as well as the fact that no game, update, or DLC actually requires firmware 6.0. If you must install a game, update, or DLC that is asking for firmware 6.0, use the bypass firmware requirement in Tinfoil when installing the .NSP file
 
I went to buy a used Switch today. The owner said she had it for 5 months. It was on firmware 6.0. I put my SX PRO into it. When I tried to boot into RCM the screen would flicker but it wouldn't start the OS X boot up menu. It would just start booting like normal.
Whay gives?
 
I went to buy a used Switch today. The owner said she had it for 5 months. It was on firmware 6.0. I put my SX PRO into it. When I tried to boot into RCM the screen would flicker but it wouldn't start the OS X boot up menu. It would just start booting like normal.
Whay gives?
If the screen is flickering, you've likely not actually entered RCM. You will know you entered RCM if the screen stays black when you turn it on.
 
If the screen is flickering, you've likely not actually entered RCM. You will know you entered RCM if the screen stays black when you turn it on.

So does that mean it was an updated model that doesn't go into RCM? (despite the owner claiming to have had it for 5 months)
 
So does that mean it was an updated model that didn't go into RCM? (despite the owner claiming to have had it for 5 months)
You misunderstood, RCM cannot be patched out. It is a feature of both unpatched and ipatched units. Without RCM, we wouldn't be able to test if a unit is patched or not. Enter RCM then you will be able to determine if it is patched or not.
 
You misunderstood, RCM cannot be patched out. It is a feature of both unpatched and ipatched units. Without RCM, we wouldn't be able to test if a unit is patched or not. Enter RCM then you will be able to determine if it is patched or not.

Ok, thanks. I tried few times and I think the screen stayed off once or twice... If it was a patched unit, would the screen just have stayed off with SX PRO plugged in? And that would indicate that it is a patched unit?
Alternatively, if it just never got into RCM, why might that be with that unit? I already have 4 switches and they all work perfectly with the SX PRO. (Tested them when I got home to make sure my jig and dongle were working)
 
Ok, thanks. I tried few times and I think the screen stayed off once or twice... If it was a patched unit, would the screen just have stayed off with SX PRO plugged in? And that would indicate that it is a patched unit?
Alternatively, if it just never got into RCM, why might that be with that unit? I already have 4 switches and they all work perfectly with the SX PRO. (Tested them when I got home to make sure my jig and dongle were working)
If you enter RCM and insert the dongle but the screen stays black, its patched. As for your other point, maybe something is wrong with the pins in the used Switch? Although you can't fix that without replacing the entire rail.
 
If you enter RCM and insert the dongle but the screen stays black, its patched. As for your other point, maybe something is wrong with the pins in the used Switch? Although you can't fix that without replacing the entire rail.

Sounds like it was a dud either way. Thanks!
I was worried it wasnt working because I had to update the SX PRO for 6.0. (I haven't updated my other switches tp 6.0 yet)
 
All bans are superbans now. Once your banned you can't update games/system, play online, access the eShop, etc. You can install updates to your games and system with homebrew tho
Well, damn. Not like I'll be playing multiplayer games since Nintendo Switch Online launched.

At least I can't accidentally update my system now..


What sucks is that now I'll have to browse DU for updates since CDNSP is dead now.
 
Hi I have a question regarding auto-rcm usage with sx os. I believe I read somewhere that auto-rcm is not entirely safe, that there are issues with fully powering down the device in which you need to boot hek to properly shutdown and a chance of brick if switch goes into negative battery. Is this true? What are the dangers of auto rcm mode in usage with sx os in particular?
 
Last edited by mesakagi,
Hi I have a question regarding auto-rcm usage with sx os. I believe I read somewhere that auto-rcm is not entirely safe, that there are issues with fully powering down the device in which you need to boot hek to properly shutdown and a chance of brick if switch goes into negative battery. Is this true? What are the dangers of auto rcm mode in usage with sx os in particular?

  • Firstly, let’s explain exactly what AutoRCM is. In order to get CFW working on your Switch, you must enter RCM and push a payload, which can be quite a pain in the ass depending on what method you are using to bridge the pins on the right Joycon rail. AutoRCM alleviates this by having your Switch boot directly into RCM. This can be healthier for the Switch as you won’t be tinkering with the Joycon rail on each boot. However, you will be unable to boot your Switch unless you send a payload to it on each boot. If you turn your Switch off periodically and occasionally would like to boot into OFW (Original Firmware), it’s probably best that you leave AutoRCM behind. However, if you are just interested in running only CFW and do not want to tinker with your Joycon rail on each boot, AutoRCM is for you!
If you have autorcm on and you don't charge your switch and it goes flat then you need to leave it plugged into the AC charger for a while* (from what I've seen about 60minutes) before you can reboot the console and re-enter RCM before charging normally...

AFAIK Hekate is the only way to properly shutdown with AutoRCM.
 
  • Like
Reactions: mesakagi

Site & Scene News

Popular threads in this forum