Hacking SWITCH NOOB PARADISE - Ask questions here

[Zuzuooloo]

So question, is it worth it to staying on 3.0.0 firmware anymore?

I see everyone mentioning 4.1 or something as their firmware. Should I be updating my ofw to that? And would that be through a game cart update or that choidujournx thing?

 

[Itsuki235]

So question, is it worth it to staying on 3.0.0 firmware anymore?

If your switch is patched, keep it on 3.0.0.

For unpatched units, there is no point in being on a low firmware version since it breaks compatibility with some titles. Use Hekate to create a full sysNAND back and also backup boot 0/1. Then enable autoRCM, and launch CFW. Update to the latest OFW using ChoiDujourNX. Team Altax has a guide on it. If a coldboot exploit ever happens for an early firmware version, you could use that nand backup to go back to that 3.0 OFW without burning any fuses in the mean time.

 

[zzoltan]

Hello,
I'm a noob with an unpatched switch bought in December 2017 and never updated. I don't remember which is the firmware of my switch but I would ask if updating now to las firmware would prevent from hacking it in the future. I've read about blown fuses but I did not understand...
Thank you very much

 

[1alien1]

hey guys, got a brand new virgin switch with fw 4.0.1. i have the sx pro, with the dongle and the clip and getting into the sx menu works.

could anybody be so kind as to talk me through the further steps? i need to update the firmware so i can use my 400gb micro sd card. but i dont want to burn fuses so i need to use the other updater. are there tutorials? first i update and then install sx os with emunand? and which nand should i update to max firmware?

also is it safe now to play online in the clean system with the cardridge and use the emunand for sx stuff?

i would really appreciate a small tutorial on how to proceed. i can do the sx part, but i want to make sure i dont screw anything up before, like the updating, the getting a backup of the nand and so forth...

appreciated!

 

[LapCheong]

hey guys, got a brand new virgin switch with fw 4.0.1. i have the sx pro, with the dongle and the clip and getting into the sx menu works.

could anybody be so kind as to talk me through the further steps? i need to update the firmware so i can use my 400gb micro sd card. but i dont want to burn fuses so i need to use the other updater. are there tutorials? first i update and then install sx os with emunand? and which nand should i update to max firmware?

also is it safe now to play online in the clean system with the cardridge and use the emunand for sx stuff?

i would really appreciate a small tutorial on how to proceed. i can do the sx part, but i want to make sure i dont screw anything up before, like the updating, the getting a backup of the nand and so forth...

appreciated!

1. Do a back up of your clean nand (4.0.1) using hekate plenty of guides out there

2. If want to keep your sysnand clean, you have to update the official way through OTA, this will burn the fuses. You can either make a clone of 4.0.1 for emunand then update sysnand. Don't see a problem either way. The latest firmware is not a problem for homebrew. Although i will suggest 7.0.1
There is no way to keep your fuses and keep your sysnand clean for online uses. Since you have to update the firmware for sysnand and doing it the unofficial will require to run homebrew

3. Use choidujournx for emunand to update, it is pretty straightforward just get the firmware files (google can get it easily) then put in on your sd card then follow on screen instruction.

 

[Draxzelex]

Hello,
I'm a noob with an unpatched switch bought in December 2017 and never updated. I don't remember which is the firmware of my switch but I would ask if updating now to las firmware would prevent from hacking it in the future. I've read about blown fuses but I did not understand...
Thank you very much

The exploit we are using right now is hardware-based not software. In English, this means the exploit works regardless of your firmware because it takes advantage of a physical part of your device, one that cannot change with a firmware update. That being said, if you update your firmware online, you will burn fuses. The relevance of burning fuses is that you will not be able to downgrade to lower firmware versions. The reason why you would want to downgrade is because there may be a better exploit such as a hypothetical untethered coldboot hack. However if you burn fuses, you will most likely not be able to take advantage of that exploit if and when it is released. Plus updating without burning fuses is really easy since we have tools such as ChoiDujourNX. Bear in mind that it will enable AutoRCM to prevent fuses from being burnt.

 

[1alien1]

1. Do a back up of your clean nand (4.0.1) using hekate plenty of guides out there

2. If want to keep your sysnand clean, you have to update the official way through OTA, this will burn the fuses. You can either make a clone of 4.0.1 for emunand then update sysnand. Don't see a problem either way. The latest firmware is not a problem for homebrew. Although i will suggest 7.0.1
There is no way to keep your fuses and keep your sysnand clean for online uses. Since you have to update the firmware for sysnand and doing it the unofficial will require to run homebrew

3. Use choidujournx for emunand to update, it is pretty straightforward just get the firmware files (google can get it easily) then put in on your sd card then follow on screen instruction.

thx for the info. so if i want to play online i have to burn the fuses for sure? or are there no bans reportet related to that question in particular? also i should not use autorcm feature right? or are no known bans from this?

 

[Ivellios]

Hello, i have not followed the scene for a while now, i just want to ask a quick question:

Which is the safest firmware i can update to in order to play NSPs and use homebrew? Mine is 6.xx i think

I read somewhere a long time ago that SciresM said its not safe to update to 8.0.1, is this still true?

Thanks!

 

[LapCheong]

thx for the info. so if i want to play online i have to burn the fuses for sure? or are there no bans reportet related to that question in particular? also i should not use autorcm feature right? or are no known bans from this?

Yup, I lost you at the ban you meant that burning fuses will result in ban? If so, burning the fuses is ninty way of preventing users from downgrading so to use a exploit of some kind

Autorcm is automatically toggle to prevent burning of fuses when you use choidujournx. Of course, yours will be burned anyway since you want to play online and it needs latest update. But thats not the point, by enabling autorcm it corrupts the boot partition and forces your switch into RCM mode.This is convenient if you want to avoid using a jig, but for sysnand usage you want to remove autoRCM and let it burn the fuses and boot.

Take note when your system boots it check for the correct fuses and burn more if it is needed to match the firmware. But if for reason, you decided to downgrade your sysnand to lower a firmware than what your fuses have already burnt. Your switch will be put into a soft-brick, this can be avoided by using the higher firmware and hence matching the fuses burnt or bypass using a payload like hekate.bin

--------------------- MERGED ---------------------------

Hello, i have not followed the scene for a while now, i just want to ask a quick question:

Which is the safest firmware i can update to in order to play NSPs and use homebrew? Mine is 6.xx i think

I read somewhere a long time ago that SciresM said its not safe to update to 8.0.1, is this still true?

Thanks!

Safest firmware with most games compatibility (latest update) if i not wrong is 7.0.1
Updating tp 8.0.1 is not advisable as some users reported that some homebrew nsp not running correctly, might be fixed though. I am not sure about this

 

[zzoltan]

The exploit we are using right now is hardware-based not software. In English, this means the exploit works regardless of your firmware because it takes advantage of a physical part of your device, one that cannot change with a firmware update. That being said, if you update your firmware online, you will burn fuses. The relevance of burning fuses is that you will not be able to downgrade to lower firmware versions. The reason why you would want to downgrade is because there may be a better exploit such as a hypothetical untethered coldboot hack. However if you burn fuses, you will most likely not be able to take advantage of that exploit if and when it is released. Plus updating without burning fuses is really easy since we have tools such as ChoiDujourNX. Bear in mind that it will enable AutoRCM to prevent fuses from being burnt.

Thank you very much for the information.
I don't know what untethered coldboot hack means, but I understood that burning fuses while updating is made by Nintendo in order to prevent firmware downgrades and so to run exploits.
I didn't catch your warning about enabling AutoRCM, would it cause issues?
Anyway for now I will not update firmware unless some titles require it.

 

[Draxzelex]

Thank you very much for the information.
I don't know what untethered coldboot hack means, but I understood that burning fuses while updating is made by Nintendo in order to prevent firmware downgrades and so to run exploits.
I didn't catch your warning about enabling AutoRCM, would it cause issues?
Anyway for now I will not update firmware unless some titles require it.

AutoRCM is a reversible modification that is made to your Switch. It changes the way your console behaves. For one thing, as the name implies, it automatically boots your console into RCM. This can be good or bad depending on how you look at it because while it removes the need for a jig, you will not be able to use the console without sending a payload. Secondly, a console running AutoRCM would reboot back into RCM if you tried turning it off however non-SX OS CFW now support proper shutdowns with AutoRCM. I warned you about AutoRCM as it is pretty mandatory for updating without burning fuses. If you do not like AutoRCM, then you can update and burn fuses but bear in mind you will not be able to downgrade in case better exploits are released for lower firmware versions. In other words, you may be stuck using the current exploit for the rest of the Switch's lifespan which is sending a payload via USB in RCM.

 

[zzoltan]

AutoRCM is a reversible modification that is made to your Switch. It changes the way your console behaves. For one thing, as the name implies, it automatically boots your console into RCM. This can be good or bad depending on how you look at it because while it removes the need for a jig, you will not be able to use the console without sending a payload. Secondly, a console running AutoRCM would reboot back into RCM if you tried turning it off however non-SX OS CFW now support proper shutdowns with AutoRCM. I warned you about AutoRCM as it is pretty mandatory for updating without burning fuses. If you do not like AutoRCM, then you can update and burn fuses but bear in mind you will not be able to downgrade in case better exploits are released for lower firmware versions. In other words, you may be stuck using the current exploit for the rest of the Switch's lifespan which is sending a payload via USB in RCM.

Thank you again.
I have no need to update al the moment and from what you're saying it's better not to update now if there is no need. When that need comes, I will come back here again to check available exploits.

 

[alexj9626]

So... just saw the EmuNAND from Atmos post. Is that really it? We have SXOS like EmuNAND for FREE? It works the same and it works for every CFW?

I know we should probably wait for 0.9.1, but this is fucking great, just want to be sure its actually a real EmuNAND like SXOS.

 

[Draxzelex]

So... just saw the EmuNAND from Atmos post. Is that really it? We have SXOS like EmuNAND for FREE? It works the same and it works for every CFW?

I know we should probably wait for 0.9.1, but this is fucking great, just want to be sure its actually a real EmuNAND like SXOS.

Basically although it won't work for every CFW. Atmosphere's EmuNAND will only work with Atmosphere meaning it will not work with ReiNX and certainly not SX OS.

 

[alexj9626]

Basically although it won't work for every CFW. Atmosphere's EmuNAND will only work with Atmosphere meaning it will not work with ReiNX and certainly not SX OS.

Shit, i didnt mean to ask for every CFW, it was for every FW/firmware, like 7.x, 8.x etc.

 

[Andiukas223]

Hello, i am a noob. I have a non-patched switch with 8.0.1 running atmosphere with 90DNS, when i install .nsp game (tried with gold-leaf and tinfoil via USB ) and try to start it up i get an error 2155-8007 and when i turn on flight mode and try to run the game i get asked "please turn flight mode off". Maybe some of you good people know the answers to my prayers

 

[Draxzelex]

Shit, i didnt mean to ask for every CFW, it was for every FW/firmware, like 7.x, 8.x etc.

It'll be supported by whatever firmware the CFW supports which in this case is Atmosphere. Which means if Nintendo releases a new firmware update, expect EmuNAND to not work until the CFW is updated. So just think of EmuNAND as CFW when it comes to compatibility.

 

[Cacx101]

Ok, so I'm just starting to hack my switch. I haven't installed any software or games to my switch (only have homebrew on microSD), but can I still perform a NAND backup? Also, when I try to restore BOOT0 and BOOT1, Hakate doesn't read it, even though the folders are in the right place. So, even when disabling autoRCM, am a able to go online without risking getting banned? And if I can't, what can I do to fix my restoring problem? (sorry for all the questions, I just don't want to run the risks)

EDIT: Scratch that, I installed and uninstalled a theme, but that's it.

 

[Draxzelex]

Ok, so I'm just starting to hack my switch. I haven't installed any software or games to my switch (only have homebrew on microSD), but can I still perform a NAND backup? Also, when I try to restore BOOT0 and BOOT1, Hakate doesn't read it, even though the folders are in the right place. So, even when disabling autoRCM, am a able to go online without risking getting banned? And if I can't, what can I do to fix my restoring problem? (sorry for all the questions, I just don't want to run the risks)

EDIT: Scratch that, I installed and uninstalled a theme, but that's it.

Unless your console has no battery, you can always perform a NAND backup. And its recommended to perform one as soon as possible because you never know when a brick will strike.

How did you dump your BOOT0/BOOT1?

AutoRCM is a minor, if non-existent, ban risk. However you always run the risk of getting banned when using a hacked console. The only way to ever be risk-free is to have a clean NAND dump made before running CFW/homebrew. Without that, you will never be able to go online without risking a ban.

 

[Cacx101]

How did you dump your BOOT0/BOOT1?

I used the one in Hakete. It creates it in the folder, and it reads the BOOT0 and BOOT1 files when it is going to overwrite them, but not when trying to restore them.