Hacking SWITCH NOOB PARADISE - Ask questions here

[binkinator]

just updated every file and booted into hekate 5.8.0 but i am missing my emummc, probably because i changed the hekate config file. is there a solution to get it back or should i start with a fresh emummc? 1 other question will i lose my custom theme in atmosphere and my save files now that i have updated the files?

(It’s starting to look like you might have a corrupt SDCard but let’s keep going and if it keeps behaving oddly we’ll address it.)

That would not have changed via the upgrade. The pointer to your emunand is stored in /emummc/emummc.ini. Please paste the contents of that file here.

E: themes and save files are not overwritten by an upgrade either.

 

[Rens02]

(It’s starting to look like you might have a corrupt SDCard but let’s keep going and if it keeps behaving oddly we’ll address it.)

That would not have changed via the upgrade. The pointer to your emunand is stored in /emummc/emummc.ini. Please paste the contents of that file here.

E: themes and save files are not overwritten by an upgrade either.

This is stored in my emummc.ini:

[emummc]
enabled=1
sector=0x380b8000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

maybe this help but this is stored in my hekate_ipl.ini file:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp


also thank you very much for taking the time to help me out!

 

[binkinator]

This is stored in my emummc.ini:

[emummc]
enabled=1
sector=0x380b8000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

maybe this help but this is stored in my hekate_ipl.ini file:

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp


also thank you very much for taking the time to help me out!

(No worries.)

Appreciate the details. Everything looks good, except for the fact that we can’t see your actual emunand.

Are you on a Mac or PC? We can try a quick and dirty fix by running fix archive bit inside Hekate and see if that helps (slim chance but costs us nothing to try.)

We can also try to take a look at your emunand on your PC using NXNandManager. It will make sure we have the correct sector in the emummc.ini file and tell us if it’s even readable on your SDCard.

 

[Rens02]

(No worries.)

Appreciate the details. Everything looks good, except for the fact that we can’t see your actual emunand.

Are you on a Mac or PC? We can try a quick and dirty fix by running fix archive bit inside Hekate and see if that helps (slim chance but costs us nothing to try.)

We can also try to take a look at your emunand on your PC using . It will make sure we have the correct sector in the emummc.ini file and tell us if it’s even readable on your SDCard.

I am currently using a laptop with windows 10 pro, do you happen to know how i run a fix archive inside hekate? i have also downloaded the NXNandManager from github but cant find an .exe file inside the folder.

 

[binkinator]

I am currently using a laptop with windows 10 pro, do you happen to know how i run a fix archive inside hekate?

great…then it’s probably not an archive bit issue but here’s how to run it in Hekate just for the heck of it:
‘Tools > Archive Bit - AutoRCM > Unset archive bit’

i have also downloaded the NXNandManager from github but cant find an .exe file inside the folder.

Download the zip file from the Releases page (on the lower right of the front page)

 

[Rens02]

great…then it’s probably not an archive issue but here’s how to run it in Hekate:
‘Tools > Archive Bit - AutoRCM > Unset archive bit’

Download the zip file from the Releases page (on the lower right of the front page)

awesome i got my NxNandManager working. in the Hekate tools section i can only see misc: fix archive bit and calibrate touchscreen on the left side and on the right side it says under Others: AutoRcm off and a button for Dump Package 1/2.

should i click on fix archive bit in Hekate?

 

[binkinator]

awesome i got my NxNandManager working. in the Hekate tools section i can only see misc: fix archive bit and calibrate touchscreen on the left side and on the right side it says under Others: AutoRcm off and a button for Dump Package 1/2.

should i click on fix archive bit in Hekate?

Yes. It should come back with “0 files fixed”

for NXNandManager, put your SDCard in your pc and try to open the emunand on it.

 

[Rens02]

Yes. It should come back with “0 files fixed”

for NXNandManager, put your SDCard in your pc and try to open the emunand on it.

awesome, just did the fix archive bit and it said 1 unset and 0 set.

in my NXNandManager i see this:

my sd card for the switch is on my D drive. when i select my D drive it says input file/drive is not a valid NX storage. however i can select the E drive which is 29.16GB it shows me this:

 

[IceFairy11]

Hello, so I haven't used my switch(RCMable switch) in a bit. It's currently sitting on 6.2.0 with whatever version of atmosphere or what not. I'd like to get some new game carts so I'd like to upgrade. I'm not sure to what version would be required so I guess the newest version which seems to be 14.1.2 . If I were to upgrade a cfw way I wouldn't be burning fuses but I'd also be disabling my game card reader with nogc. Is there any draw back from just burning the fuses to allow my game card reader to work on the newer version? I've done a little research on the topic and most of the things I've found are pretty old but mention that if you're past version 4 that you should just update to the newest version. Is this still the truth? Obviously I wouldn't be able to downgrade with using a cfw to bypass the fuse check and the game card reader wouldn't work due to having fuses burnt from a newer firmware.

Obviously this might be a subjective answer to what you really lose from losing downgrading. But I guess more so just in a general scheme of things. Only real thing I could maybe see is some form of a cold boot. Though I feel if it did exist it'd be at some lower level like RCM. Or maybe that is just me coping.

 

[binkinator]

awesome, just did the fix archive bit and it said 1 unset and 0 set.

in my NXNandManager i see this:
View attachment 322534
my sd card for the switch is on my D drive. when i select my D drive it says input file/drive is not a valid NX storage. however i can select the E drive which is 29.16GB it shows me this:
View attachment 322535

That’s actually good news on both counts.

1) It corrected “something” so there’s a slight chance it fixed things for you. very slight but still. If it works we can stop everything here and you can enjoy your switch. If not…let’s keep going…
2) you have emunand data that we can back up to your PC.

A few things first:

Put your SDCard back in your switch
Download lockpick_RCM and inject it in RCM mode instead of Hekate or fusee.
Dump your keys and take note of where it says it stored prod.keys on the SDCard.
Eject your SDCard and put it in your PC and copy the keys to somewhere safe on your PC.
Restart NXNandManager and go to the tabs at the top and enter the location of your keys file so it can unencrypt things.
Now us NXNandManager to take a backup of your emunand.
You can backup you SDCard itself while we’re at it.
Now that you have secure backups you can format your SDCard to FAT32 w/ 32k block size using rufus
Next follow this guide to get everything back up and running: https://rentry.co/SwitchHackingIsEasy

once you’re back up you can restore things from your backup as needed. let’s get you back up and then see what’s missing that we need to recover.

 

[binkinator]

Hello, so I haven't used my switch(RCMable switch) in a bit. It's currently sitting on 6.2.0 with whatever version of atmosphere or what not. I'd like to get some new game carts so I'd like to upgrade. I'm not sure to what version would be required so I guess the newest version which seems to be 14.1.2 . If I were to upgrade a cfw way I wouldn't be burning fuses but I'd also be disabling my game card reader with nogc. Is there any draw back from just burning the fuses to allow my game card reader to work on the newer version? I've done a little research on the topic and most of the things I've found are pretty old but mention that if you're past version 4 that you should just update to the newest version. Is this still the truth? Obviously I wouldn't be able to downgrade with using a cfw to bypass the fuse check and the game card reader wouldn't work due to having fuses burnt from a newer firmware.

Obviously this might be a subjective answer to what you really lose from losing downgrading. But I guess more so just in a general scheme of things. Only real thing I could maybe see is some form of a cold boot. Though I feel if it did exist it'd be at some lower level like RCM. Or maybe that is just me coping.

Go latest and greatest. Leave your GC blocked. Any GC you have can be downloaded as an XCI and installed without it so why bother. You won’t burn any fuses as long as you use Hekate to bypass the anti-downgrade measures.

Here’s a guide to get you started: https://rentry.co/SwitchHackingIsEasy

If you do everything on emunand you can leave your Sysnand on 6.x in the unlikely even a future soft hack ever come out.

 

[HalfScoper]

if you're past version 4 that you should just update to the newest version. Is this still the truth?

Yes.
Either do what binkinator said, avoid using the sysNAND and use an emuNAND instead, or just update. I mean you stated your Switch is exploitable anyway, so in my opinion you should just update.
Nevertheless, even if you do update, I'd still recommend using an emuNAND anyway.
To play legit cartridges on CFW, you'd have to do this: https://rentry.org/DisableNOGC

 

[Rens02]

That’s actually good news on both counts.

1) It corrected “something” so there’s a slight chance it fixed things for you. very slight but still. If it works we can stop everything here and you can enjoy your switch. If not…let’s keep going…
2) you have emunand data that we can back up to your PC.

A few things first:

Put your SDCard back in your switch
Download lockpick_RCM and inject it in RCM mode instead of Hekate or fusee.
Dump your keys and take note of where it says it stored prod.keys on the SDCard.
Eject your SDCard and put it in your PC and copy the keys to somewhere safe on your PC.
Restart NXNandManager and go to the tabs at the top and enter the location of your keys file so it can unencrypt things.
Now us NXNandManager to take a backup of your emunand.
You can backup you SDCard itself while we’re at it.
Now that you have secure backups you can format your SDCard to FAT32 w/ 32k block size using rufus
Next follow this guide to get everything back up and running: https://rentry.co/SwitchHackingIsEasy

once you’re back up you can restore things from your backup as needed. let’s get you back up and then see what’s missing that we need to recover.

i succesfully dumped my keys onto my sd card with lockpick_rcm. Just to make sure, in NXNandManager do i need to go to the options tab and click on configure keyset then select from file and then select my prod keys? after i have done this i need to select the 29.16 gb drive which is i think my emunand. After selecting this i need to create a full dump and format my sd card using rufus. after all this i need to follow a guide and at last i need to restore my backup. is this correct?

 

[binkinator]

i succesfully dumped my keys onto my sd card with lockpick_rcm. Just to make sure, in NXNandManager do i need to go to the options tab and click on configure keyset then select from file and then select my prod keys? after i have done this i need to select the 29.16 gb drive which is i think my emunand. After selecting this i need to create a full dump and format my sd card using rufus. after all this i need to follow a guide and at last i need to restore my backup. is this correct?

You have good instincts. All correct.

E: we could go through all the rubble and try to find that one thing or do the reverse…just clean house and the cherry pick the few things we want to get back from backups. And yes, e: (the one windows always wants you to format) is your hidden emunand.

 

[Rens02]

You have good instincts. All correct.

awesome! thank you so much bro im going to do it right away! ill keep you updated about the progress

 

[vampier206]

hey yall. was tryan to update sig patches to play new xeno now im getting a "nosigchk" launching from hekate.
did sigpatches change or somthing os a i miss something for newer firm games

 

[vampier206]

ok fixed the "nosigchk" with this threads help.
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/

 

[vampier206]

new sigpatvches still can not install xeno 2nd download froma dif site and still the same error.

 

[Draxzelex]

thanks for the info - reason for asking was i was trying to use tinfoil to pc usb but was running in to issues
ended using AWOO To pc usb thats running fine ... so recap the tinfoil 13.0 -isnt the real 1 ?
so what about the 1 on the tinfoil web site ? 14.0 ?

No, the only place to find the real Tinfoil is the GitHub page where I linked which is why I linked specifically that page. All other sources are fakes or knockoffs.

I have the RCMloader ONE. I bought it on aliexpress a while back. I can see the files on the device when I connect it to my pc but when I use the firmware upgrade tool it just says no device detected. Ive tried about 5 other cables & all have the same result.....strange.

Do you have another computer or device you can try connecting the RCM Loader to via USB?

I have another question. I am trying to install pirated games on my emummc. I use Awoo Installer because tinfoil didnt work somehow. If I click on a game that I Installed with a NSP file, i get an error because it wants to check on the Eshop if thats my game but I blocked it with 90DNS. After some research I found out that I have to use sigpatches. So I downloaded a Sigpatch file and installed it with awoo installer. It told me to restart the switch so I did that. Then when I try to open emummc with hekate, I get an error :

(

Error while loading fss0:

atmosphere/fusee-secondary.bin

Wrong in cfg or missing/corrupt files

Failed to launch HOS/

)

Then I replaced the Hekate_ipl.ini file from the sigpatch pack with the one I got from Hekate. Now I am able to open emummc again but of course the Sigpatches are not installed. I use Atmosphere 1.3.2 and Firmware 14.1.2.
I tried both of these sigpatches:

https://hackintendo.com/download/sigpatches-atmosphere-esfsloader/

https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/


Please help me I tried it for over 2 hours...

The patches from the second thread you linked are foolproof. Either you put the patches in the wrong places or there are some bad leftover patches from what you downloaded with Awoo. I recommend deleting the /atmosphere folder and downloading a new one from the GitHub page then redownloading the patches from the second thread you linked. Also next time, please do not open a thread if your post isn't answered immediately. At the very least, I can guarantee I check this thread 3 times a day and nobody likes helping a multi-poster.

new sigpatvches still can not install xeno 2nd download froma dif site and still the same error.

You just said in the previous post that you fixed an earlier error and now it came back? Which is it?

 

[vampier206]

No, the only place to find the real Tinfoil is the GitHub page where I linked which is why I linked specifically that page. All other sources are fakes or knockoffs.


The patches from the second thread you linked are foolproof. Either you put the patches in the wrong places or there are some bad leftover patches from what you downloaded with Awoo. I recommend deleting the /atmosphere folder and downloading a new one from the GitHub page then redownloading the patches from the second thread you linked. Also next time, please do not open a thread if your post isn't answered immediately. At the very least, I can guarantee I check this thread 3 times a day and nobody likes helping a multi-poster.

You just said in the previous post that you fixed an earlier error and now it came back? Which is it?

Sorry, I fixed the bootloader sigpatch at launch issues. Now I'm running into issue when installing over nusbloader and tinwoo. Are my sigpatches wrong?