Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

Hey! Is there a way I can access my microSD card (To update ReiNX) with RCM over USB, without booting into the Switch OFW? I have AutoRCM, and I just wanna update ReiNX.

Sorry if this is dumb, I'm just desperate, and I refuse to believe no one has encountered this and left it alone, yet my research sees otherwise.

Thank you for any help, I'm just a bored person on the internet trying to use my Switch.

Either update the file on a computer or update via the app store.

 

[hdhani]

• If you update online now, you will burn fuses which will make it impossible for you to downgrade in case better exploits are released on lower firmware versions such as an untethered coldboot hack. While it is advised to update with the homebrew application ChoiDujourNX, you can still dump your NAND with an exFAT formatted SD card without updating your console to support exFAT
• As explained in the previous bullet point, you do not need exFAT support on your console to dump your NAND with an exFAT formatted SD card. This is because Hekate, the main way to dump the NAND, is loaded outside of the console's operating system and as such does not require exFAT support from your console
• If you dump the NAND with a FAT32 SD card with Hekate, you will get a NAND dump split into 15 parts
• Here is where the dilemma comes into play. There are no reliable ways of updating without burning fuses that do not involve homebrew and thus risk a ban. But if you update while burning fuses, you lock yourself into using Fusee Gelee which is the RCM exploit for nearly the entire lifespan of the Switch. If you are fine with that, you can just go ahead and update while burning fuses to redeem your download code before using CFW. But if you want to preserve your fuses, either update your firmware with ChoiDujourNX or enable AutoRCM then perform a system update while running Atmosphere/ReiNX. Both of these can bring you to firmware 8.1 without burning fuses. You can then redeem your download code before using any other features of CFW. The chances of a ban in this scenario is relatively low
• One thing you should also be aware of is that since your console came with firmware 3.0, your gamecart slot has not been updated. There is an update for it on firmware versions 4.0 and above that prevent it from being used on firmware versions below 4.0. This only matters when you update without burning fuses as this is the only situation where you would return to a firmware version of 4.0 or less. To prevent this update from occurring, modern CFW break the cartridge slot on firmware versions 4.0 or higher. This means you cannot play cartridges on firmware versions 4.0 or higher if you updated without burning fuses from a firmware below 4.0. Now this isn't that big of a deal since all of the free CFW support games in .NSP format which is the digital version of Switch games. But this is something to be mindful about if you decide to update without burning fuses

Wow thanks for the detailed response. So from what I can understand the only benefit of not burning fuses is to be able to downgrade and use a potential untethered exploit? But dont most games now require higher firmware versions so what is the point of that?

If the cartridge slot becomes disabled too if I dont burn a fuse then that sounds like a disadvantage to me.

I don't plan to play online with this, but only for homebrew / cfw / nsps etc.

Would you advise me to nand backup before or after I update the firmware? I'm not sure which method I should use to update the system yet :/

 

[Hipeopeo]

Either update the file on a computer or update via the app store.

Did you... read my post? Was I not clear enough? I cannot currently modify files, and my Switch is off right now. I cannot use the app store right now, and I cannot use a microSD adapter.

I am trying to use a USB-A to USB-C cable to edit files using only RCM, or get an FTP Client, over RCM.

In example: A payload that brings you to an FTP client, WITHOUT modifying the microSD card.

 

[Hayato213]

Did you... read my post? Was I not clear enough? I cannot currently modify files, and my Switch is off right now. I cannot use the app store right now, and I cannot use a microSD adapter.

I am trying to use a USB-A to USB-C cable to edit files using only RCM, or get an FTP Client, over RCM.

In example: A payload that brings you to an FTP client, WITHOUT modifying the microSD card.

Not possible through rcm mode

 

[alex2196]

Either update the file on a computer

What did you do to get it into this state in the first place?

Highly unlikely. By the time such tools come out, the console will be at End Of Life meaning Nintendo will stop banning people as they will have shifted focus to their next device.

i solve my problem, i get in the recovery mode and than restore ALL switch things. Now i clear all the file on the sd and i'm on ofw 7.0.1 (i think it s clear since i have get back all at original status) could you give a full guide to install the best cfw (and easier) to install and play games on switch? thankssss

 

[Hipeopeo]

Not possible through rcm mode

Okay.

Next question would be if I could boot a CFW without a microSD, put a microSd in, and update ReiNX?

 

[Hayato213]

Okay.

Next question would be if I could boot a CFW without a microSD, put a microSd in, and update ReiNX?

You wouldn't be able to , as the CFW files is stored on a micro SD, not on the system.

 

[Draxzelex]

i solve my problem, i get in the recovery mode and than restore ALL switch things. Now i clear all the file on the sd and i'm on ofw 7.0.1 (i think it s clear since i have get back all at original status) could you give a full guide to install the best cfw (and easier) to install and play games on switch? thankssss

Easiest is probably ReiNX as it not only is free but bundles everything you need into one package.

Wow thanks for the detailed response. So from what I can understand the only benefit of not burning fuses is to be able to downgrade and use a potential untethered exploit? But dont most games now require higher firmware versions so what is the point of that?

If the cartridge slot becomes disabled too if I dont burn a fuse then that sounds like a disadvantage to me.

I don't plan to play online with this, but only for homebrew / cfw / nsps etc.

Would you advise me to nand backup before or after I update the firmware? I'm not sure which method I should use to update the system yet :/

In that case, you would use EmuNAND to run the latest firmware without breaking the firmware compatibility on SysNAND for untethered coldboot. And EmuNAND is now available for free CFW via Atmosphere albeit unstable and limited to hidden partition.

As for when you should dump your NAND, do it as soon as possible. While your chance of bricking is next to impossible while setting up CFW, you never know when you will run into issues.

Also I personally update without burning fuses all the time. What I do is download the system update in Hekate's stock mode (Hekate is another payload that also doubles as a bootloader aka tool for booting CFW), delete my Internet settings, make sure AutoRCM is enabled, then install the system update offline while running CFW. Normally AutoRCM is removed during a system update but if you are running the latest CFW, they prevent AutoRCM from being removed. I should also mention AutoRCM is the key to avoid burning fuses. The way fuses are burnt is that the console's bootloader checks the firmware with the fuse count. If they match, your console is allowed passage. If there are too few fuses burnt compared to the firmware, it will burn fuses so that they match then allow the Switch to boot. If too many fuses are burnt compared to the firmware, your console will not boot and the screen stays black which is a "soft brick" (soft because if you perform a manual shutdown, which is holding the Power button for 12 seconds, you can exit out of the brick). For reference, the list of fuses and their respective firmware versions can be found here. Anyway I have been doing that method of updating without burning fuses for several months now and I have not been banned yet.

 

[alex2196]

Easiest is probably ReiNX as it not only is free but bundles everything you need into one package.


In that case, you would use EmuNAND to run the latest firmware without breaking the firmware compatibility on SysNAND for untethered coldboot. And EmuNAND is now available for free CFW via Atmosphere albeit unstable and limited to hidden partition.

As for when you should dump your NAND, do it as soon as possible. While your chance of bricking is next to impossible while setting up CFW, you never know when you will run into issues.

Also I personally update without burning fuses all the time. What I do is download the system update in Hekate's stock mode (Hekate is another payload that also doubles as a bootloader aka tool for booting CFW), delete my Internet settings, make sure AutoRCM is enabled, then install the system update offline while running CFW. Normally AutoRCM is removed during a system update but if you are running the latest CFW, they prevent AutoRCM from being removed. I should also mention AutoRCM is the key to avoid burning fuses. The way fuses are burnt is that the console's bootloader checks the firmware with the fuse count. If they match, your console is allowed passage. If there are too few fuses burnt compared to the firmware, it will burn fuses so that they match then allow the Switch to boot. If too many fuses are burnt compared to the firmware, your console will not boot and the screen stays black which is a "soft brick" (soft because if you perform a manual shutdown, which is holding the Power button for 12 seconds, you can exit out of the brick). For reference, the list of fuses and their respective firmware versions can be found here. Anyway I have been doing that method of updating without burning fuses for several months now and I have not been banned yet.

okay thanks one more thing, I saw using the heckake menu that my switch (with is on 7.0.1) has 7 fusee burnt, is this ok? I don't know what they are. After the restore of the system for sure I'm on the ofw right? so it should be ok if I'll follow the ReiNX installation guide.Sorry If I disturb you with noobs questions, but I don't want to make big mistakes and buy another switch! thanks so much

 

[Draxzelex]

okay thanks one more thing, I saw using the heckake menu that my switch (with is on 7.0.1) has 7 fusee burnt, is this ok? I don't know what they are. After the restore of the system for sure I'm on the ofw right? so it should be ok if I'll follow the ReiNX installation guide.Sorry If I disturb you with noobs questions, but I don't want to make big mistakes and buy another switch! thanks so much

Fuses are designed to prevent downgrading. A fuse count of 7 indications you can only normally boot a firmware of 6.0-6.1. For reference, a full list can be found here. However this doesn't matter so much when using the current exploit, Fusee Gelee. All bootloaders (e.g. the payloads that boot CFW) bypass the fuse check so technically you can run any firmware version you want.

 

[Hipeopeo]

You wouldn't be able to , as the CFW files is stored on a micro SD, not on the system.

Okay, so I managed to pull off the impossible task. Here's a guide as detailed as I can go.: (Windows Only, will look for other options for macOS and Linux :{ )

Warning: GBATemp, the developers of TegraRcmGUI, and myself (Hipeopeo) are not responsible for bricked Switches. Proceed at your own risk.

Note: Your microSD will not need any files to be put on it, but it will still need to be in the Switch to be modified.

1. Download the latest TegraRcmGUI, and either install it, for extract it.

2. Open TegraRcmGUI, go to settings, and click "Install Driver", and go through with the installer that pops up.

3. In TegraRcmGUI, go to tools (The buttons should be greyed out. If they're not, skip step 4). Make sure "Memloader v3 / UMS Tool" is set to "MMC - SD Card" in the option thing after "Mount". Warning: Do not select any other option. Those are unsafe for inexperienced users.

4. Make sure your Switch is plugged in to your computer, and boot into RCM.

5. The buttons should become available (ignore this if they already were). Click on the button with the USB drive on it, next to "Memloader v3 / UMS Tool". Your Switch should flash a bit, maybe some text, then stay on a glowing screen. You should now be able to access your Switch's microSD from File Explorer.

Note: To end the connection, hold the power button on your Switch until it turns off.

 

[hdhani]

In that case, you would use EmuNAND to run the latest firmware without breaking the firmware compatibility on SysNAND for untethered coldboot. And EmuNAND is now available for free CFW via Atmosphere albeit unstable and limited to hidden partition.

As for when you should dump your NAND, do it as soon as possible. While your chance of bricking is next to impossible while setting up CFW, you never know when you will run into issues.

Also I personally update without burning fuses all the time. What I do is download the system update in Hekate's stock mode (Hekate is another payload that also doubles as a bootloader aka tool for booting CFW), delete my Internet settings, make sure AutoRCM is enabled, then install the system update offline while running CFW. Normally AutoRCM is removed during a system update but if you are running the latest CFW, they prevent AutoRCM from being removed. I should also mention AutoRCM is the key to avoid burning fuses. The way fuses are burnt is that the console's bootloader checks the firmware with the fuse count. If they match, your console is allowed passage. If there are too few fuses burnt compared to the firmware, it will burn fuses so that they match then allow the Switch to boot. If too many fuses are burnt compared to the firmware, your console will not boot and the screen stays black which is a "soft brick" (soft because if you perform a manual shutdown, which is holding the Power button for 12 seconds, you can exit out of the brick). For reference, the list of fuses and their respective firmware versions can be found..Anyway I have been doing that method of updating without burning fuses for several months now and I have not been banned yet.

Seems like a lot of work required just to prevent burnt fuses! I'm assuming if i jump from 3.0 to 8.1 without burning a fuse, dont enable autorcm the next time my switch boots into ofw it will burn fuses to match version 8.1 ? So I'd have to leave autorcm enabled all the time to prevent any burning of fuses?

Also if I create a nand now on 3.0 and upgrade while burning a fuse to 8.1 (through a normal system update), and then try to restore the nand it wont restore properly because the fuse count doesn't match?

Maybe I should update the normal way and then create a nand backup after if I dont care about burnt fuses? Assuming cfw works on 8.1.0? Do game cartridges and legit downloaded games work on cfw or I'll need to reboot into ofw to play those?

 

[Zantezuke]

I hacked my Switch recently and went to restore a NAND backup, but I may have (and probably did) update to 8.1.0 from my 8.0.0 backup.

Right after I restored the backup, my switch powered down and won't turn on.

I've tried to get back into RCM using a paperclip (which I've gotten pretty good at doing), but I've had no luck. Am I screwed?

 

[Draxzelex]

Seems like a lot of work required just to prevent burnt fuses! I'm assuming if i jump from 3.0 to 8.1 without burning a fuse, dont enable autorcm the next time my switch boots into ofw it will burn fuses to match version 8.1 ? So I'd have to leave autorcm enabled all the time to prevent any burning of fuses?

Also if I create a nand now on 3.0 and upgrade while burning a fuse to 8.1 (through a normal system update), and then try to restore the nand it wont restore properly because the fuse count doesn't match?

Maybe I should update the normal way and then create a nand backup after if I dont care about burnt fuses? Assuming cfw works on 8.1.0? Do game cartridges and legit downloaded games work on cfw or I'll need to reboot into ofw to play those?

Well that is the method I use. The other much simpler method involves using the homebrew application ChoiDujourNX. However it involves a homebrew application which means it carries an inherent ban risk. I personally see it as riskier than my method because in mine, I only boot CFW but with ChoiDujourNX, you boot CFW and a homebrew application so the risk might be greater. And in either scenario, you will need AutoRCM enabled at all times to prevent fuses from being burnt (ChoiDujourNX enables it by default). However AutoRCM is incredibly useful as it eliminates the need for a jig and plenty of people use it for that purpose instead of having to avoid burning fuses.

In the case of restoring a NAND backup of a firmware lower than the fuse count, you will not be able to boot the console up normally but you can still boot it up through RCM by using a bootloader that bypasses the fuse check which all modern bootloaders do by default.

At the end of the day, it is up to you if you want to burn fuses or not. I just thought I would let you know of the possibilities you have.

I hacked my Switch recently and went to restore a NAND backup, but I may have (and probably did) update to 8.1.0 from my 8.0.0 backup.

Right after I restored the backup, my switch powered down and won't turn on.

I've tried to get back into RCM using a paperclip (which I've gotten pretty good at doing), but I've had no luck. Am I screwed?

Just keep trying or maybe use something else like aluminum foil.

 

[Hayato213]

Okay, so I managed to pull off the impossible task. Here's a guide as detailed as I can go.: (Windows Only, will look for other options for macOS and Linux :{ )

Warning: GBATemp, the developers of TegraRcmGUI, and myself (Hipeopeo) are not responsible for bricked Switches. Proceed at your own risk.

Note: Your microSD will not need any files to be put on it, but it will still need to be in the Switch to be modified.

1. Download the latest TegraRcmGUI, and either install it, for extract it.

2. Open TegraRcmGUI, go to settings, and click "Install Driver", and go through with the installer that pops up.

3. In TegraRcmGUI, go to tools (The buttons should be greyed out. If they're not, skip step 4). Make sure "Memloader v3 / UMS Tool" is set to "MMC - SD Card" in the option thing after "Mount". Warning: Do not select any other option. Those are unsafe for inexperienced users.

4. Make sure your Switch is plugged in to your computer, and boot into RCM.

5. The buttons should become available (ignore this if they already were). Click on the button with the USB drive on it, next to "Memloader v3 / UMS Tool". Your Switch should flash a bit, maybe some text, then stay on a glowing screen. You should now be able to access your Switch's microSD from File Explorer.

Note: To end the connection, hold the power button on your Switch until it turns off.

I don't get it , why wouldn't you just don't do it the old fashion way, just by taking it out to update it, beside your post has nothing to boot with booting cfw.

 

[NANASHI89]

Is FAT32 recommended for Linux on Switch?

 

[G_T_C]

Hi all

Apologies for the following dumb questions,

This is my first portable console and I would like to have cfw mostlyto run backups

i just got a nintendo that it was offered to me, i can see that the serial is under the orange serial sign, which probably means that it is pacthed

Additoanlly the switch is currently on firmware 7.0.1 and untill I have the release of cfw i do not want to update to firmware higher than this )as already advised if i get over 8.0.0 probably i will never be able to get cfw)

If i am not mistaken this should hacked on a forseable future trough deja vu process righ ? ( I think that yesterday it was released the update for consoles patched up untill firmware 4.0.1)

one last question and this is the one that led me to bother you all with this...

While i wait for the new release in order to have cfw on software 7.0.1, can I buy marvel black order that comes out next month ? Would i need to update the switch in order to play such game ? ( or this would be required only if I wanted to update game version ?)

Many thanks in advance
Kind regards
G

 

[Draxzelex]

Is FAT32 recommended for Linux on Switch?

Its not just recommended, its mandatory.

Hi all

Apologies for the following dumb questions,

This is my first portable console and I would like to have cfw mostlyto run backups

i just got a nintendo that it was offered to me, i can see that the serial is under the orange serial sign, which probably means that it is pacthed

Additoanlly the switch is currently on firmware 7.0.1 and untill I have the release of cfw i do not want to update to firmware higher than this )as already advised if i get over 8.0.0 probably i will never be able to get cfw)

If i am not mistaken this should hacked on a forseable future trough deja vu process righ ? ( I think that yesterday it was released the update for consoles patched up untill firmware 4.0.1)

one last question and this is the one that led me to bother you all with this...

While i wait for the new release in order to have cfw on software 7.0.1, can I buy marvel black order that comes out next month ? Would i need to update the switch in order to play such game ? ( or this would be required only if I wanted to update game version ?)

Many thanks in advance
Kind regards
G

You should at least test to see if it is indeed patched because if its not, none of the following will matter. You can use this tutorial to test it out. Anyways, its impossible to say what firmware version an unreleased game will require because its unreleased. Its highly unlikely for it to require a firmware version higher than 7.1 but you should wait until someone confirms the required firmware of the game after you confirm your Switch is patched. If its not patched, firmware is no longer an issue.

 

[Blaze Uchiha]

I need some help with something. I'm new to Switch hacking. I've been studying how it's done for a couple months now and I know I have a Switch that's vulnerable to fusee gelee ( I bought it February of last year brand new, it was stocked with FW 4.1.0). I thought I would give it a shot and the first thing I wanted to do was make a nand backup, so I tried to push the latest Hekate payload using TegraRCMSmash. It didn't work and now I just get a black screen and it doesn't look like my Switch even turns on. How do I fix this? Any help is greatly appreciated.

 

[AuRiM]

Which allocation is better for SD 256gb exfat, 32kb or 64kb ??