Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,097,922
  • Replies Replies 47,953
  • Likes Likes 66
If you create EmuNAND and update EmuNAND, SysNAND will stay on 6.0.1. Normaly people use EmuNAND for offline CFW and clean SysNAND for online.

You have the latest SX OS release on your micro sd?

Right on player- forgot SX had taken a while to support 7.x so I'm up and running again.
 
if i have a title that wont install is that due to a bad dump of it
im on 7.1 lastest goldleaf but get the error code that indicates i need a new firmware, tried to ignore needed firmware for both nand and sd card and use needed firmware to no provail its a nsp by the way a newish game
thank you
 
Using RCM for first time.. what are the risks?

Sleep mode issues in SX? or was this resolved a while ago?

Battery issues? drains, overheating? Problems recharging or rebooting if battery is run down during either idleness or play?

I really don't mind taking an extra 4 seconds using the jig to avoid any potential issues. If I could just disable through SX menu I will. But that leads me to this:

I can no longer boot into OFW due to fuse check? Via either the SX options menu or just from powering on with no SD? Currently on 7.0 from 6.0.1 via choidujoir. Does having RCM enabled help with this fuse issue in some way?

And not really related, but

What about the emunand feature in SX? A few months ago folks here convinced me that the feature (on release) did not perform as advertised. But I think it may have been addressed by TX a while ago. Is it worth adding the hidden partition and using emunand? Now that my systems on 7.0 via choudijour what would I do at this point? Keep sysnand on 7.0 and update (eventually!) emunand to 8.0? I never backed up my 6.0.1 nand since it was pretty 'dirty' but my pre CFW nand backup (5.1) is intact. So if I have this, anything I mess up in the future can likely be fixed via a nand restore? Within reason of course :)

Thanks all! Been saving up some questions over here lol
 
Using RCM for first time.. what are the risks?

Sleep mode issues in SX? or was this resolved a while ago?

Battery issues? drains, overheating? Problems recharging or rebooting if battery is run down during either idleness or play?

I really don't mind taking an extra 4 seconds using the jig to avoid any potential issues. If I could just disable through SX menu I will. But that leads me to this:

I can no longer boot into OFW due to fuse check? Via either the SX options menu or just from powering on with no SD? Currently on 7.0 from 6.0.1 via choidujoir. Does having RCM enabled help with this fuse issue in some way?

And not really related, but

What about the emunand feature in SX? A few months ago folks here convinced me that the feature (on release) did not perform as advertised. But I think it may have been addressed by TX a while ago. Is it worth adding the hidden partition and using emunand? Now that my systems on 7.0 via choudijour what would I do at this point? Keep sysnand on 7.0 and update (eventually!) emunand to 8.0? I never backed up my 6.0.1 nand since it was pretty 'dirty' but my pre CFW nand backup (5.1) is intact. So if I have this, anything I mess up in the future can likely be fixed via a nand restore? Within reason of course :)

Thanks all! Been saving up some questions over here lol
1) Just make sure to power the console off from sx os menu when you have enabled autoRCM.
2) If you have enabled autoRCM you can't simply boot in OFW because as soon as you boot your console, it directly enters RCM. You have to boot to OFW from the sx os menu. AutoRCM prevents that you boot to OFW with Nintendo boot loader in order to prevent fuses burning.
3) EmuNAND allows you to keep SysNAND clean and play online while you run CFW in offline EmuNAND. Also you don't have to mess with SysNAND anymore. If EmuNAND bricks, just create a new one. But if you don't have created a backup of your clean SysNAND you should NOT use it for online.
 
I'm having issues with nxtheme installer as its saying cant find cfw folder and I'm running sx os on 7.0.1 as I downloaded a theme off of the homebrew app store what do I do

Update found out my problem no sxos folder
 
Last edited by Saintseiya911,
I updated from 4.0.1 to 7.0.1 choidujournx (latest vr) and everything install OK but everything went sideways after the reboot which activated auto rcm after that it wasn't loading past the Nintendo logo use hetake to deactivate auto rcm which now it let's me boot ofw but now it doesn't let me load any cfw I have try every latest one and none latest, any idea what is wrong with it?
(forgot to mention when I try to use cfw it loads ofw normal and album doesn't load hbl)
 
Last edited by gogi4349,
Fatal error NXBoot... I have a hackable switch and I managed to downgrade my Switch but I can't run atomosphere anymore. I restrored my NAND to downgrade so what is wrong and what do I have to do to run CFW again?
 
Hello everyone, I'm having a problem with Kosmos.
I'm using SX OS to inject henkate. I've dump my keys, but when I choose the option "CFW" in the henkate menu i keep getting this error

"Failed to get TSEC keys, please try again
Failed to launch firmware"
 
Last edited by er3eroMKII,
My brother accidentally downgraded from 7.0.1 to 4.0.1 for some reason it wont load past nintendo logo. Did i brick my console? Or is there hopefully a fix for this? I had 9 fuses burned.
 
if i have a title that wont install is that due to a bad dump of it
im on 7.1 lastest goldleaf but get the error code that indicates i need a new firmware, tried to ignore needed firmware for both nand and sd card and use needed firmware to no provail its a nsp by the way a newish game
thank you
Goldleaf is too buggy for my tastes. My personal recommendation is using USB install with Tinfoil and Aluminum Foil as the Windows client. That link also has a build of Tinfoil for you to download in case you don't have a working one already.

I updated from 4.0.1 to 7.0.1 choidujournx (latest vr) and everything install OK but everything went sideways after the reboot which activated auto rcm after that it wasn't loading past the Nintendo logo use hetake to deactivate auto rcm which now it let's me boot ofw but now it doesn't let me load any cfw I have try every latest one and none latest, any idea what is wrong with it?
(forgot to mention when I try to use cfw it loads ofw normal and album doesn't load hbl)
Reformat your SD card to FAT32.

Fatal error NXBoot... I have a hackable switch and I managed to downgrade my Switch but I can't run atomosphere anymore. I restrored my NAND to downgrade so what is wrong and what do I have to do to run CFW again?
When you say you restored your NAND, what exactly did you restore? What is your console's fuse count? You can check this by booting Hekate -> Tools -> Fuse Info. And what firmware was your NAND backup?

Hello everyone, I'm having a problem with Kosmos.
I'm using SX OS to inject henkate. I've dump my keys, but when I choose the option "CFW" in the henkate menu i keep getting this error

"Failed to get TSEC keys, please try again
Failed to launch firmware"
You have to load Hekate directly to dump those keys.

My brother accidentally downgraded from 7.0.1 to 4.0.1 for some reason it wont load past nintendo logo. Did i brick my console? Or is there hopefully a fix for this? I had 9 fuses burned.
How did he downgrade? And did he perform a system initialization when downgrading? If not, try holding both volume + and - after sending a payload that boots CFW/OFW
 
Goldleaf is too buggy for my tastes. My personal recommendation is using USB install with Tinfoil and Aluminum Foil as the Windows client. That link also has a build of Tinfoil for you to download in case you don't have a working one already.

Reformat your SD card to FAT32.

When you say you restored your NAND, what exactly did you restore? What is your console's fuse count? You can check this by booting Hekate -> Tools -> Fuse Info. And what firmware was your NAND backup?

You have to load Hekate directly to dump those keys.

How did he downgrade? And did he perform a system initialization when downgrading? If not, try holding both volume + and - after sending a payload that boots CFW/OFW
He used choiurdejour to downgrade.
 
Would restoring my nand fix my issue hopefully?
Restoring your NAND should work. Make sure you restore boot0/boot1 as well as the raw eMMC GPP. If the firmware of your NAND is lower than 7.0, you will have to enable AutoRCM afterwards since any firmware lower than 7.0 expects a fuse count of less than 9 which you do not have.
 
Restoring your NAND should work. Make sure you restore boot0/boot1 as well as the raw eMMC GPP. If the firmware of your NAND is lower than 7.0, you will have to enable AutoRCM afterwards since any firmware lower than 7.0 expects a fuse count of less than 9 which you do not have.
Ok ty ill try holding + and - hopefully that works
 
Reformat your SD card to FAT32.

When you say you restored your NAND, what exactly did you restore? What is your console's fuse count? You can check this by booting Hekate -> Tools -> Fuse Info. And what firmware was your NAND backup?

You have to load Hekate directly to dump those keys.

I loaded hekate and went to tools but there's no fuse info... I did a generic restore like advised and it gave me BOOT0,BOOT1, and rawnand. Is there a folder I can download that has everything I need to get back into CWF?
 
I loaded hekate and went to tools but there's no fuse info... I did a generic restore like advised and it gave me BOOT0,BOOT1, and rawnand. Is there a folder I can download that has everything I need to get back into CWF?
My bad, I meant Console Info not Tools. And do you remember what firmware your NAND backup was on?
 
Goldleaf is too buggy for my tastes. My personal recommendation is using USB install with Tinfoil and Aluminum Foil as the Windows client. That link also has a build of Tinfoil for you to download in case you don't have a working one already.

Reformat your SD card to FAT32.

When you say you restored your NAND, what exactly did you restore? What is your console's fuse count? You can check this by booting Hekate -> Tools -> Fuse Info. And what firmware was your NAND backup?

You have to load Hekate directly to dump those keys.

How did he downgrade? And did he perform a system initialization when downgrading? If not, try holding both volume + and - after sending a payload that boots CFW/OFW

My FW was 7.01 I believe and I found a fuse count that said I have 9/64 burnt fuses?
 

Site & Scene News

Popular threads in this forum