Hacking SWITCH NOOB PARADISE - Ask questions here

[binkinator]

Didnt work

Interesting. You didn’t upgrade Firmware yet, did you?

Still thinking what this could be…in the mean time go ahead and make a backup of your emunand using Hekate (there is a button to do emunand instead of Sysnand)

E: while you are in there, run the Fix Archive Bit button in Hekate (under the Tools Menu) and note if any errors are reported.

 

[waz]

Interesting. You didn’t upgrade Firmware yet, did you?

Still thinking what this could be…in the mean time go ahead and make a backup of your emunand using Hekate (there is a button to do emunand instead of Sysnand)

E: while you are in there, run the Fix Archive Bit button in Hekate (under the Tools Menu) and note if any errors are reported.

Correct. Emummc firmware is on 14.1.2 (unsure which rebootless update as I used AIO when I did it)
Sysnand is on 9.1.0
No errors reported from Fix Archive Bit

 

[Draxzelex]

Correct. Emummc firmware is on 14.1.2 (unsure which rebootless update as I used AIO when I did it)
Sysnand is on 9.1.0
No errors reported from Fix Archive Bit

Well I think we found the source of your problem at least. Never ever use the AIO Updater. It is highly notorious for causing more issues than it fixes. Its going to be better to start fresh because there is no telling what stupid files it may or may not have installed. For starters, delete the /atmosphere folder and download the newest from the official GitHub page.

 

[binkinator]

Correct. Emummc firmware is on 14.1.2 (unsure which rebootless update as I used AIO when I did it)
Sysnand is on 9.1.0
No errors reported from Fix Archive Bit

Well heck. There’s only one more directory to look at so we might as well finish the job…

Let’s temporarily move /bootloader to /bootloader.bk and unzip the latest hekate.x.x.x.zip. Then copy your /bootloader.bk/hekate_ipl.ini file to the /bootloader/ directory and let’s try again.

E: Also, what @Draxzelex said.

 

[waz]

Well I think we found the source of your problem at least. Never ever use the AIO Updater. It is highly notorious for causing more issues than it fixes. Its going to be better to start fresh because there is no telling what stupid files it may or may not have installed. For starters, delete the /atmosphere folder and download the newest from the official GitHub page.

Was mistaken, I actually used daybreak. Think I attempted to use AIO before but like you said its garbo. Anyways, for this problem specifically though I had successfully updated and everything was going fine, but I let the battery die and had to charge from AutoRCM for a bit.. then boom this issue.
Had been following suchmememanyskill's mmc rebuild guide up until I couldn't get EmmcHaccGen to work. There a different guide you recommend for rebuilding?

Well heck. There’s only one more directory to look at so we might as well finish the job…

Let’s temporarily move /bootloader to /bootloader.bk and unzip the latest hekate.x.x.x.zip. Then copy you /bootloader.bk/hekate_ipl.ini file to the /bootloader/ directory and let’s try again.

No dice

 

[binkinator]

Was mistaken, I actually used daybreak. Think I attempted to use AIO before but like you said its garbo. Anyways, for this problem specifically though I had successfully updated and everything was going fine, but I let the battery die and had to charge from AutoRCM for a bit.. then boom this issue.
Had been following suchmememanyskill's mmc rebuild guide up until I couldn't get EmmcHaccGen to work. There a different guide you recommend for rebuilding?


No dice

Soooo, you’ve updated /atmosphere, Sigpatches and now /bootloader. You already updated /bootloader/payloads/fusee.bin. Your hekate_ipl.ini file is good and there are no archive bit issues. That’s almost the entire shootin match at this point. We might have to consider backing up your Emunand and formatting. How is that going btw? If Hekate isn’t your speed you can backup your emunand using EmuTool.

Let’s double check the SDCard using h2testw.

 

[waz]

Soooo, you’ve updated /atmosphere, Sigpatches and now /bootloader. You already updated /bootloader/payloads/fusee.bin. Your hekate_ipl.ini file is good and there are no archive bit issues. That’s almost the entire shootin match at this point. We might have to consider backing up your Emunand and formatting. How is that going btw? If Hekate isn’t your speed you can backup your emunand using EmuTool.

Let’s double check the SDCard using h2testw.

Had already backed up with hekate last night trying to solve this issue using this guide. Couldnt get EmmcHaccGen to create NX-(fw version)_exFAT so I came here.

Should be no issues with the sd card it reads and writes perfectly, but ill let you know if the program finds any errors

 

[binkinator]

Had already backed up with hekate last night trying to solve this issue using this guide. Couldnt get EmmcHaccGen to create NX-(fw version)_exFAT so I came here.

Should be no issues with the sd card it reads and writes perfectly, but ill let you know if the program finds any errors

Once you have a backup, use NXNandManager to see if you can recover your :USER/saves directory on from your emunand. If you can do this then it’s safe to simply format your SDCard and start from scratch. You will be able to manually recover your saves using JKSV like so:

https://gbatemp.net/threads/recovering-games-saves-from-nand-using-nxnandmanager-and-jksv.620758/

 

[Livebythecoin]

installed a new copy of files to SD card using the Fusee-gelee SD Setup process in the guide, recommended settings. also installed Hekate latest version (6.0.1). my switch takes me to the main hekate screen where i can launch, but when trying to launch CFW (sysMMC) I am getting the following error message:

Error while loading fss0:
atmosphere/package3
wrong ini cfg or missing/corrupt files!

failed to launch HOS!

any ideas what I need to change? I've tried the other launch options and all show different error messages, but following the set up guide it says the one i'm booting is the correct one.

 

[binkinator]

installed a new copy of files to SD card using the Fusee-gelee SD Setup process in the guide, recommended settings. also installed Hekate latest version (6.0.1). my switch takes me to the main hekate screen where i can launch, but when trying to launch CFW (sysMMC) I am getting the following error message:

Error while loading fss0:
atmosphere/package3
wrong ini cfg or missing/corrupt files!

failed to launch HOS!

any ideas what I need to change? I've tried the other launch options and all show different error messages, but following the set up guide it says the one i'm booting is the correct one.

What does your /bootloader/hekate_ipl.ini look like and do you have a file called /atmosphere/package3? If not you need to grab the latest atmosphere and unzip atmosphere.x.x.x.zip at the top level of your SDCard.

E: which guide are you following? Ideally you want to launch CFW/EmuMMC but your guide may have other directions.

 

[waz]

Once you have a backup, use NXNandManager to see if you can recover your :USER/saves directory on from your emunand. If you can do this then it’s safe to simply format your SDCard and start from scratch. You will be able to manually recover your saves using JKSV like so:

https://gbatemp.net/threads/recovering-games-saves-from-nand-using-nxnandmanager-and-jksv.620758/

Figured haha. Appreciate you taking the time to help!

 

[binkinator]

Figured haha. Appreciate you taking the time to help!

Yeah, sorry man. Once we’ve run through all that you’ve been through already, there’s not much else to look at. When you format, make sure you stick w/ FAT32. I use rufus to do so and set it as non-bootable and 32k block size.

If you need a guide to help rip through the steps: https://rentry.org/SwitchHackingIsEasy

 

[Livebythecoin]

What does your /bootloader/hekate_ipl.ini look like and do you have a file called /atmosphere/package3? If not you need to grab the latest atmosphere and unzip atmosphere.x.x.x.zip at the top level of your SDCard.

E: which guide are you following? Ideally you want to launch CFW/EmuMMC but your guide may have other directions.

I used the switch.homebrewguide one, and installed the recommended settings it prompted from sdsetup atmosphere was within those settings, could it be an outdated version tho? do you have a link to the most recent version? and it would be a case of removing the atmosphere folder and putting the other version in?

CFW/EmuMMC displays the same error message, but I can boot that one in future, it may have just been a case of me misreading.

the bootloader/hekate_ipl.ini is as follows:

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

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

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

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

 

[binkinator]

I used the switch.homebrewguide one, and installed the recommended settings it prompted from sdsetup atmosphere was within those settings, could it be an outdated version tho? do you have a link to the most recent version? and it would be a case of removing the atmosphere folder and putting the other version in?

No worries. This one is fine: https://switch.homebrew.guide/

CFW/EmuMMC displays the same error message, but I can boot that one in future, it may have just been a case of me misreading.

Just a matter of preference. I like to use an emunand in case anything happens to it I always have a clean Sysnand to go back to.

the bootloader/hekate_ipl.ini is as follows:

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

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

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

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

This looks good. Do you have a /atmosphere/package3? If not, simply delete /atmosphere/ and unzip a new copy directly from the source and unzip at the top level of your SDCard to create a new /atmosphere directory.

 

[waz]

Yeah, sorry man. Once we’ve run through all that you’ve been through already, there’s not much else to look at. When you format, make sure you stick w/ FAT32. I use rufus to do so and set it as non-bootable and 32k block size.

If you need a guide to help rip through the steps: https://rentry.org/SwitchHackingIsEasy

Sweet. While we're both here.. is there a way to make my sysnand 'clean' for the purposes of avoiding a ban? Believe I tampered with it when those early beta versions of atmosphere came out and emmummc wasnt available yet.

 

[binkinator]

Sweet. While we're both here.. is there a way to make my sysnand 'clean' for the purposes of avoiding a ban? Believe I tampered with it when those early beta versions of atmosphere came out and emmummc wasnt available yet.

Many have had success with Haku33. There is discussion that using it to wipe log files might attract unwanted Ninty Ninja attention but if your are self-banning anyway (i.e. not going online for fear of filth) you don’t have much to lose.

 

[Livebythecoin]

No worries. This one is fine:

Just a matter of preference. I like to use an emunand in case anything happens to it I always have a clean Sysnand to go back to.


This looks good. simply delete /atmosphere/ and unzip a new copy directly from the source and unzip at the top level of your SDCard to create a new /atmosphere directory.

i removed the atmosphere that was the default one in the sdsetup package, and reinstalled the latest one from source at the top level of the sd card. the error message i'm now getting is:

emuMMC is forced but not enabled!

failed to launch HOS!

any ideas?

 

[binkinator]

i removed the atmosphere that was the default one in the sdsetup package, and reinstalled the latest one from source at the top level of the sd card. the error message i'm now getting is:

emuMMC is forced but not enabled!

failed to launch HOS!

any ideas?

Go into Hekate and see if you have an emunand (big emuMMC tile on the right of main page)created and enabled. If it says disabled then you missed a step somewhere.

 

[Livebythecoin]

Go into Hekate and see if you have an emunand (big emuMMC tile on the right of main page)created and enabled. If it says disabled then you missed a step somewhere.

perfect, it says disabled. do i just create one through the button on the right? also, what type do i need, SD file or SD Partition? is there a guide for creating one? i feel i'm so close, thanks so much for all your help

 

[binkinator]

perfect, it says disabled. do i just create one through the button on the right? also, what type do i need, SD file or SD Partition? is there a guide for creating one? i feel i'm so close, thanks so much for all your help

Great!

Here is that section in the guide you are using:
https://switch.homebrew.guide/emummc/emummc.html

I prefer a hidden partition which will require Hekate to format your SDCard. If you have games installed on your SDCard it will likely be too large to temporarily backup to memory (how Hekate does it on the fly) so you will need to make a backup by copy-paste on your PC.