Hacking SWITCH NOOB PARADISE - Ask questions here

[rustb0y]

Again, AutoRCM is only needed if you are running a higher firmware than your fuses on SysNAND; EmuNAND is irrelevant in this case.

As for EmuNAND, only SX OS V2.4 supports it. If you are using an earlier version, the highest firmware it can go up to is 6.1
Are you sending the new ReiNX.bin as the payload or is it on your SD card? Because the one for 6.2 has to be on the SD card, not sent as a payload.

I am using the 6.2 as payload and on my SD card. so i should pop the 6.2 on the SD card and payload with the previous version .bin ?

 

[Draxzelex]

I am using the 6.2 as payload and on my SD card. so i should pop the 6.2 on the SD card and payload with the previous version .bin ?

Yes I don't think the 6.2 build supports being sent as the primary payload which would explain why you aren't even seeing the splash screen.

 

[Zap2000]

Again, AutoRCM is only needed if you are running a higher firmware than your fuses on SysNAND; EmuNAND is irrelevant in this case.

As for EmuNAND, only SX OS V2.4 supports it. If you are using an earlier version, the highest firmware it can go up to is 6.1
Are you sending the new ReiNX.bin as the payload or is it on your SD card? Because the one for 6.2 has to be on the SD card, not sent as a payload.

Will the sleep work on this one 6.2? Is there any loss of functions on 6.2?
How long till 2.4 becomes stable release? Is there many known bugs?
What setup do u think would be best from scratch?

 

[Draxzelex]

Will the sleep work on this one 6.2?
How long till 2.4 becomes stable release?
What setup do u think would be best?

Sleep mode works when you have a fuse count that is less than or equal to the firmware that is currently running, regardless if its SysNAND or EmuNAND.

Given that TX is now following the naming tactics of Gateway in that they are labeling all of their new releases as "betas" to sweep any issues under the rug, probably never.

Games, updates, and DLC are eventually going to require 6.2 and higher firmwares so better update EmuNAND to 6.2 and use SX OS V2.4 now rather than later. Firmware of SysNAND is going to depend on whether you want to play online, what firmware your retail cartridges/digital games require, etc.

 

[Zap2000]

Sleep mode works when you have a fuse count that is less than or equal to the firmware that is currently running, regardless if its SysNAND or EmuNAND.

Given that TX is now following the naming tactics of Gateway in that they are labeling all of their new releases as "betas" to sweep any issues under the rug, probably never.

Games, updates, and DLC are eventually going to require 6.2 and higher firmwares so better update EmuNAND to 6.2 and use SX OS V2.4 now rather than later. Firmware of SysNAND is going to depend on whether you want to play online, what firmware your retail cartridges/digital games require, etc.

If I’m just using pirated games on emuNAND. is it still is useful to keep sysnand on low firmware?

 

[Draxzelex]

If I’m just using pirated games on emuNAND. is it still is useful to keep sysnand on low firmware?

If you want to keep your options open for future exploits such as the coveted untethered coldboot, yes. If you don't care about future exploits and are content with the current one, then no.

 

[Troll1011]

I upgraded to 6.2.0 with choidujournx and i know it turns on autorcm. Is there a way to boot into OFW without using another device?
i can't boot into OFW
when i use the fusee payload through hekate i hold the volume buttons but i can't seem to get into recovery mode on atmosphere why?
when i updated to 6.2.0 on system settings it says something like version 6.2.0 ( in the brackets it said something but i dont know because it downloaded another system version but it was like AMT)
why is it like that?

 

[Zap2000]

If you want to keep your options open for future exploits such as the coveted untethered coldboot, yes. If you don't care about future exploits and are content with the current one, then no.

Thx for all the help so far do If I use options open for future exploits way above would u recommend me use autoCRM or not?

Also I found this on sx os site
OFW 4.1 and lower support: These older firmwares require special care for backwards compatibility, and in this specific release if you use SX OS, your switch will boot to a black screen.
If you update your sysNAND this will be resolved for you. If you don't want to do that (day dreaming about the sloooowwwww booting dejavu exploit that will probably never be released) then you will have to wait for the next edition of SX OS for this to be fixed.

Does this mean the method we chatted about sysnand stay low and running lastest emuNAND fw won’t work?

 

[Zap2000]

Thx for all the help so far do If I use options open for future exploits way above would u recommend me use autoCRM or not?

Also will homebrew apps work as good on latest higher firmware?
Team executer recommend innthey maual to use exfat but I read here about problems with corruptions. Should I use exfat or fat32 with the above method?

 

[Steve2000]

Hi...total noob question here so be gentle

So my daughter accidentally updated the switch to 6.2 while it was running cfw (im using sx pro), i'm trying to get the switch back to boot for the last 2 days and i'm completely lost with this.... i redownloaded the latest 2.4 cfw from sx team, but no luck so far. I'm even struggling to load the sx pro menu to choose custom or original firmware, it doesnt load all the time, and when it loads and i click on csf or ofw the switch just goes black....

Is there anything i can do or is my switch bricked ?

ive read a lot on the forums but couldnt find an answer to this, i also do not understand what "emunand" or "fuses" are, so a very simple explanation would be great

thanks a lot to help a fellow noob out !

 

[icevenom]

Hekate is the best tool for backing up the NAND. Make sure you dump boot0/boot1 and eMMC raw GPP as these comprise your full NAND backup. If you want to save some space and don't mind losing save data as well as installed content, you can dump eMMC SYS instead of the raw GPP.

FAT32 is objectively better than exFAT since we have ways of bypassing the 4 GB limit on FAT32 but more importantly, exFAT has the chance to corrupt your SD card unlike FAT32. The only purpose of exFAT is when you are restoring the eMMC raw GPP or rawnand since it is larger than 4 GB and cannot be split when restoring.

Both Atmosphere and ReiNX come with the default homebrew applications to install backups in .NSP format. Certain packages of Atmosphere come with more useful homebrew applications such as NX-Shell (file manager).

It is possible to update games in CFW but you risk getting the console banned in doing so. Its safer to acquire the game updates in .NSP format and install them.

Thank you for taking the time to reply and help out. There is just so much to try and get your head around. How would I make a back-up of the NAND etc if I use FAT32, are there tools to get around it, would you be able to tell me which ones? and how about if i wanted to load .nsp's? would i need some sort of a splitter if the files are larger than 4GB?

I have read a lot about AutoRCM - if i have switch which is OFW 6.2 and i am installing CFW for 6.2, do i need to enable autoRCM?

I have also read about SigPatches? What do these do and do I need these if i plan to download .nsp games? do these sipatches come included in Atmosphere or ReinX?

Are there any advantages to paying and buying SX OS? - I know there is a lot po politic behind this whole thing from what i have reas, but for the average user is this a good platform, or is Atmosphere enough?

Thank you again.

 

[rustb0y]

Yes I don't think the 6.2 build supports being sent as the primary payload which would explain why you aren't even seeing the splash screen.

i have tried and it comes up with a error? package 2 magic error with using the previous version as a payload

 

[turtlejay]

I just powered on a brand new switch with a 128gb sd card in it. Its on firmware 4.0.1. I backed up NAND via Hekate based on the tutorial here: https://guide.sdsetup.com/ . I am contemplating purchasing SX OS solely because of EmuNAND. I do not have a windows pc and im injecting payload from my Android, which works wonderfully. Im trying to figure out the next step. I havent found a clear and concise tutorial in which they discuss how to create the EmuNAND. Also if anyone is familiar with MAC OS, is the MS-DOS FAT option in Disk Utility the same as FAT32? if so i have a 128gb FAT32 Sd card empty atm.

 

[Draxzelex]

I upgraded to 6.2.0 with choidujournx and i know it turns on autorcm. Is there a way to boot into OFW without using another device?
i can't boot into OFW
when i use the fusee payload through hekate i hold the volume buttons but i can't seem to get into recovery mode on atmosphere why?
when i updated to 6.2.0 on system settings it says something like version 6.2.0 ( in the brackets it said something but i dont know because it downloaded another system version but it was like AMT)
why is it like that?

To boot into OFW, you can use the Stock Launch Configuration of Hekate.

Thx for all the help so far do If I use options open for future exploits way above would u recommend me use autoCRM or not?

I'd only recommend AutoRCM if you care about burning fuses and you either use Sleep Mode a lot or know how to properly turn off a console with AutoRCM. To properly turn it off, you must turn it off from RCM not Horizon (name of Switch's OS)

Also will homebrew apps work as good on latest higher firmware?
Team executer recommend innthey maual to use exfat but I read here about problems with corruptions. Should I use exfat or fat32 with the above method?

FAT32 is superior over exFAT especially when it comes to homebrew. SX OS recommends exFAT because they don't bother providing the community alternatives to splitters or tools that can install files larger than 4 GB without paying heed to possible corruption issues.

Hi...total noob question here so be gentle

So my daughter accidentally updated the switch to 6.2 while it was running cfw (im using sx pro), i'm trying to get the switch back to boot for the last 2 days and i'm completely lost with this.... i redownloaded the latest 2.4 cfw from sx team, but no luck so far. I'm even struggling to load the sx pro menu to choose custom or original firmware, it doesnt load all the time, and when it loads and i click on csf or ofw the switch just goes black....

Is there anything i can do or is my switch bricked ?

ive read a lot on the forums but couldnt find an answer to this, i also do not understand what "emunand" or "fuses" are, so a very simple explanation would be great

thanks a lot to help a fellow noob out !

If your SD card is formatted as exFAT, this will cause it to not boot because you are on firmware 6.2 without exFAT support. Format the SD card to FAT32. If it is bigger than 32 GB, you will have to use a third-party program such as GUIFormat. FAT32 is better than exFAT anyway since there are a plethora of ways to bypass the 4 GB limit on FAT32 plus you have no chance at corruption with FAT32 unlike exFAT.

Thank you for taking the time to reply and help out. There is just so much to try and get your head around. How would I make a back-up of the NAND etc if I use FAT32, are there tools to get around it, would you be able to tell me which ones? and how about if i wanted to load .nsp's? would i need some sort of a splitter if the files are larger than 4GB?

I have read a lot about AutoRCM - if i have switch which is OFW 6.2 and i am installing CFW for 6.2, do i need to enable autoRCM?

I have also read about SigPatches? What do these do and do I need these if i plan to download .nsp games? do these sipatches come included in Atmosphere or ReinX?

Are there any advantages to paying and buying SX OS? - I know there is a lot po politic behind this whole thing from what i have reas, but for the average user is this a good platform, or is Atmosphere enough?

Thank you again.

Hekate, which is the main tool to dump the NAND, dumps it in parts which you can join together afterwards. Alternatively you can temporarily use exFAT to dump the NAND in one part as Hekate is separate from Horizon (name of the Switch's OS) so its irrelevant if your system supports exFAT or not. For installing .NSP files, USB installation is highly preferred as it not only works on both FAT32 and exFAT but is faster than the regular installation.

AutoRCM is primarily meant to remove the need for a jig (because it AUTOmatically boots the console into RCM).

SX OS is the only CFW that supports .XCI loading (all other CFW support .XCI conversions and installation), HDDs, EmuNAND, and their own cheat engine. Everything else can be done in Atmosphere and then some. For example, there is a program that lets you play games that support LAN over the Internet known as Switch Lan Play. Think of it like Xlinkai for the Switch (which is also coming soon). The problem was that this tool only supported games that had LAN and not all games support LAN. There is now a kip that converts games that only have local wireless into LAN meaning all games with local multiplayer can be played "online" which SX OS does not support. Atmosphere also allows you further customization of the CFW itself as well as boot0 protection when updating officially. Meaning that if you have AutoRCM enabled and you update online, AutoRCM won't be removed (it is normally removed upon system updates).

i have tried and it comes up with a error? package 2 magic error with using the previous version as a payload

I believe someone compiled the latest ReiNX commits into a build. You can give it a try: https://cdn.discordapp.com/attachments/470724990296391711/523608206090567690/reinx_dec15.zip

I just powered on a brand new switch with a 128gb sd card in it. Its on firmware 4.0.1. I backed up NAND via Hekate based on the tutorial here: https://guide.sdsetup.com/ . I am contemplating purchasing SX OS solely because of EmuNAND. I do not have a windows pc and im injecting payload from my Android, which works wonderfully. Im trying to figure out the next step. I havent found a clear and concise tutorial in which they discuss how to create the EmuNAND. Also if anyone is familiar with MAC OS, is the MS-DOS FAT option in Disk Utility the same as FAT32? if so i have a 128gb FAT32 Sd card empty atm.

This is the only tutorial I have found with setting up EmuNAND.

 

[Zap2000]

To boot into OFW, you can use the Stock Launch Configuration of Hekate.
I'd only recommend AutoRCM if you care about burning fuses and you either use Sleep Mode a lot or know how to properly turn off a console with AutoRCM. To properly turn it off, you must turn it off from RCM not Horizon (name of Switch's OS)
FAT32 is superior over exFAT especially when it comes to homebrew. SX OS recommends exFAT because they don't bother providing the community alternatives to splitters or tools that can install files larger than 4 GB without paying heed to possible corruption issues.
If your SD card is formatted as exFAT, this will cause it to not boot because you are on firmware 6.2 without exFAT support. Format the SD card to FAT32. If it is bigger than 32 GB, you will have to use a third-party program such as GUIFormat. FAT32 is better than exFAT anyway since there are a plethora of ways to bypass the 4 GB limit on FAT32 plus you have no chance at corruption with FAT32 unlike exFAT.
Hekate, which is the main tool to dump the NAND, dumps it in parts which you can join together afterwards. Alternatively you can temporarily use exFAT to dump the NAND in one part as Hekate is separate from Horizon (name of the Switch's OS) so its irrelevant if your system supports exFAT or not. For installing .NSP files, USB installation is highly preferred as it not only works on both FAT32 and exFAT but is faster than the regular installation.

AutoRCM is primarily meant to remove the need for a jig (because it AUTOmatically boots the console into RCM).

SX OS is the only CFW that supports .XCI loading (all other CFW support .XCI conversions and installation), HDDs, EmuNAND, and their own cheat engine. Everything else can be done in Atmosphere and then some. For example, there is a program that lets you play games that support LAN over the Internet known as Switch Lan Play. Think of it like Xlinkai for the Switch (which is also coming soon). The problem was that this tool only supported games that had LAN and not all games support LAN. There is now a kip that converts games that only have local wireless into LAN meaning all games with local multiplayer can be played "online" which SX OS does not support. Atmosphere also allows you further customization of the CFW itself as well as boot0 protection when updating officially. Meaning that if you have AutoRCM enabled and you update online, AutoRCM won't be removed (it is normally removed upon system updates).

I believe someone compiled the latest ReiNX commits into a build. You can give it a try: https://cdn.discordapp.com/attachments/470724990296391711/523608206090567690/reinx_dec15.zip
This is the only tutorial I have found with setting up EmuNAND.

I thought I couldn’t burn fuses on lower fw sysnand 4.1.0 and 6.2 emuNAND do I still need AutoRCM to prevent fuses burning?

Sry u sure it’s ok to keep sysnand at 4.1.0 and make emuNAND 6.2 coz I found this in the bug page of 2.4?

SX OS 2.4 BETA Confirmed bugs
Hello again loyal SX OS users

Recently Team Xecuter dropped the 2.4 BETA for SX OS that brought support for those who have updated their switch to OFW 6.2.
- OFW 4.1 and lower support: These older firmwares require special care for backwards compatibility, and in this specific release if you use SX OS, your switch will boot to a black screen.
If you update your sysNAND this will be resolved for you. If you don't want to do that (day dreaming about the sloooowwwww booting dejavu exploit that will probably never be released) then you will have to wait for the next edition of SX OS for this to be fixed.

 

[Troll1011]

To boot into OFW, you can use the Stock Launch Configuration of Hekate.
I'd only recommend AutoRCM if you care about burning fuses and you either use Sleep Mode a lot or know how to properly turn off a console with AutoRCM. To properly turn it off, you must turn it off from RCM not Horizon (name of Switch's OS)
FAT32 is superior over exFAT especially when it comes to homebrew. SX OS recommends exFAT because they don't bother providing the community alternatives to splitters or tools that can install files larger than 4 GB without paying heed to possible corruption issues.
If your SD card is formatted as exFAT, this will cause it to not boot because you are on firmware 6.2 without exFAT support. Format the SD card to FAT32. If it is bigger than 32 GB, you will have to use a third-party program such as GUIFormat. FAT32 is better than exFAT anyway since there are a plethora of ways to bypass the 4 GB limit on FAT32 plus you have no chance at corruption with FAT32 unlike exFAT.
Hekate, which is the main tool to dump the NAND, dumps it in parts which you can join together afterwards. Alternatively you can temporarily use exFAT to dump the NAND in one part as Hekate is separate from Horizon (name of the Switch's OS) so its irrelevant if your system supports exFAT or not. For installing .NSP files, USB installation is highly preferred as it not only works on both FAT32 and exFAT but is faster than the regular installation.

AutoRCM is primarily meant to remove the need for a jig (because it AUTOmatically boots the console into RCM).

SX OS is the only CFW that supports .XCI loading (all other CFW support .XCI conversions and installation), HDDs, EmuNAND, and their own cheat engine. Everything else can be done in Atmosphere and then some. For example, there is a program that lets you play games that support LAN over the Internet known as Switch Lan Play. Think of it like Xlinkai for the Switch (which is also coming soon). The problem was that this tool only supported games that had LAN and not all games support LAN. There is now a kip that converts games that only have local wireless into LAN meaning all games with local multiplayer can be played "online" which SX OS does not support. Atmosphere also allows you further customization of the CFW itself as well as boot0 protection when updating officially. Meaning that if you have AutoRCM enabled and you update online, AutoRCM won't be removed (it is normally removed upon system updates).

I believe someone compiled the latest ReiNX commits into a build. You can give it a try: https://cdn.discordapp.com/attachments/470724990296391711/523608206090567690/reinx_dec15.zip
This is the only tutorial I have found with setting up EmuNAND.

My question was can i boot without any devices and also why cant i go to recovery mode

 

[rustb0y]

To boot into OFW, you can use the Stock Launch Configuration of Hekate.
I'd only recommend AutoRCM if you care about burning fuses and you either use Sleep Mode a lot or know how to properly turn off a console with AutoRCM. To properly turn it off, you must turn it off from RCM not Horizon (name of Switch's OS)
FAT32 is superior over exFAT especially when it comes to homebrew. SX OS recommends exFAT because they don't bother providing the community alternatives to splitters or tools that can install files larger than 4 GB without paying heed to possible corruption issues.
If your SD card is formatted as exFAT, this will cause it to not boot because you are on firmware 6.2 without exFAT support. Format the SD card to FAT32. If it is bigger than 32 GB, you will have to use a third-party program such as GUIFormat. FAT32 is better than exFAT anyway since there are a plethora of ways to bypass the 4 GB limit on FAT32 plus you have no chance at corruption with FAT32 unlike exFAT.
Hekate, which is the main tool to dump the NAND, dumps it in parts which you can join together afterwards. Alternatively you can temporarily use exFAT to dump the NAND in one part as Hekate is separate from Horizon (name of the Switch's OS) so its irrelevant if your system supports exFAT or not. For installing .NSP files, USB installation is highly preferred as it not only works on both FAT32 and exFAT but is faster than the regular installation.

AutoRCM is primarily meant to remove the need for a jig (because it AUTOmatically boots the console into RCM).

SX OS is the only CFW that supports .XCI loading (all other CFW support .XCI conversions and installation), HDDs, EmuNAND, and their own cheat engine. Everything else can be done in Atmosphere and then some. For example, there is a program that lets you play games that support LAN over the Internet known as Switch Lan Play. Think of it like Xlinkai for the Switch (which is also coming soon). The problem was that this tool only supported games that had LAN and not all games support LAN. There is now a kip that converts games that only have local wireless into LAN meaning all games with local multiplayer can be played "online" which SX OS does not support. Atmosphere also allows you further customization of the CFW itself as well as boot0 protection when updating officially. Meaning that if you have AutoRCM enabled and you update online, AutoRCM won't be removed (it is normally removed upon system updates).

I believe someone compiled the latest ReiNX commits into a build. You can give it a try: https://cdn.discordapp.com/attachments/470724990296391711/523608206090567690/reinx_dec15.zip
This is the only tutorial I have found with setting up EmuNAND.

I have tried that as well , still got nothing , this is one that i think i might just leave as i have tried everything. I have looked at SX OS but you have to pay for that.

I have seen that Atmosphere is another one and tried that but got a error about the fusee secondary not being found, but it was there.

my serial is XAJ7003 and on the list its hackable .

 

[Draxzelex]

I thought I couldn’t burn fuses on lower fw sysnand 4.1.0 and 6.2 emuNAND do I still need AutoRCM to prevent fuses burning?

Sry u sure it’s ok to keep sysnand at 4.1.0 and make emuNAND 6.2 coz I found this in the bug page of 2.4?

SX OS 2.4 BETA Confirmed bugs
Hello again loyal SX OS users

Recently Team Xecuter dropped the 2.4 BETA for SX OS that brought support for those who have updated their switch to OFW 6.2.
- OFW 4.1 and lower support: These older firmwares require special care for backwards compatibility, and in this specific release if you use SX OS, your switch will boot to a black screen.
If you update your sysNAND this will be resolved for you. If you don't want to do that (day dreaming about the sloooowwwww booting dejavu exploit that will probably never be released) then you will have to wait for the next edition of SX OS for this to be fixed.

Please read through what I'm saying as you're now forcing me to repeat myself. EmuNAND has no bearing on fuses since it cannot be booted into normally but with SX Loader which disables the fuse check. AutoRCM is only needed when SysNAND is running a firmware higher than the fuse count.

Also I was not aware of that issue (SX OS is really unstable). However this is a non-issue if you are not using AutoRCM since you do not need SX OS to boot OFW in that case.

My question was can i boot without any devices and also why cant i go to recovery mode

If it has AutoRCM, then no. And you should be able to boot into recovery mode by holding volume + and - when using a payload that launches CFW/OFW. At the very least, I have confirmed its possible with ReiNX and ReiNX is the easiest to do this with since it autoboots into CFW.

I have tried that as well , still got nothing , this is one that i think i might just leave as i have tried everything. I have looked at SX OS but you have to pay for that.

I have seen that Atmosphere is another one and tried that but got a error about the fusee secondary not being found, but it was there.

my serial is XAJ7003 and on the list its hackable .

Have you tried using another SD card?

 

[rustb0y]

Please read through what I'm saying as you're now forcing me to repeat myself. EmuNAND has no bearing on fuses since it cannot be booted into normally but with SX Loader which disables the fuse check. AutoRCM is only needed when SysNAND is running a firmware higher than the fuse count.

Also I was not aware of that issue (SX OS is really unstable). However this is a non-issue if you are not using AutoRCM since you do not need SX OS to boot OFW in that case.
If it has AutoRCM, then no. And you should be able to boot into recovery mode by holding volume + and - when using a payload that launches CFW/OFW. At the very least, I have confirmed its possible with ReiNX and ReiNX is the easiest to do this with since it autoboots into CFW.
Have you tried using another SD card?

Yea ive tried three different ones, scan disk normal black one 32gb , scan disk ultra 32gb and another ultra but 64gb. I have tried doing a setup through SDsetup and selected reinx that way and does same. I did atmosphere but i keep getting the fusee secondary error.

 

[nando]

Check for archive bits also with atmosphere make sure you have the sigpatches

with reinx make sure you have the homebrew redirection (100D folder in titles or hbl.nsp in reinx)

So i checked my folders and it has 100d etc. But none of the nro show up. I can navigate out of the folder and the hbl nro shows up but none of the other homebrew apps. Ive reformatted my sd card too and i nothing changes.