Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,111,671
  • Replies Replies 47,954
  • Likes Likes 66
I updated my firmware, Hekate and Atmosphere but when I try going into sysmmc I get "Failed to identify Kernal! Failed to launch HOS!" and it takes me back to hekate load screen. Not sure what I'm missing.
 
Where we see instructions to update prod.keys? I think I did it once but don't remember!

1667772427601.png


According to this, when it load, it says grabbing keys from prod.keys
 
Now I'm getting "No main boot entries found...""Check that bootloader/ini has at least one file." Where do you think my ini file went? And how do I create/get it back?
 
Now I'm getting "No main boot entries found...""Check that bootloader/ini has at least one file." Where do you think my ini file went? And how do I create/get it back?

If you don't have one create one, name it hekate-ipl.ini

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


{------- Launch -------}
[Atmosphere]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/sysnand.bmp

{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

[Horizon]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
{}
 
  • Like
Reactions: FoureyeSamurai
Alright, I started over and updated atmosphere and hekate from the beginning, updated fusee and the hekate_ipl.ini config. Now when I launch emummc, atmosphere launches, I see the icon and then it crashes to black screen. I'm able to get back to stock and hekate launch menu but this will happen everytime now. Any ideas anybody?
 
Last edited by FoureyeSamurai,
Alright, I started over and updated atmosphere and hekate from the beginning, updated fusee and the hekate_ipl.ini config. Now when I launch emummc, atmosphere launches, I see the icon and then it crashes to black screen. I'm able to get back to stock and hekate launch menu but this will happen everytime now. Any ideas anybody?
you do have an emunand?
 
Decided to just use a different SD card for my modded/EmuNAND shenanigans. Doesn't bother me about switching it either, I'll probably be in CFW much more often anyway.
 
Hello everybody.
I have installed Atmosphere on my Switch, is it ok if I turn wifi on emuNAND so that I can upgrade the firmware, bootloaders and Atmosphere from ALL-In-One Switch Updater or will I get banned?

Kind regards
 
Hello everybody.
I have installed Atmosphere on my Switch, is it ok if I turn wifi on emuNAND so that I can upgrade the firmware, bootloaders and Atmosphere from ALL-In-One Switch Updater or will I get banned?

Kind regards
I wouldn't recommend using the AIO Updater at all. Its notorious for giving users issues so I'm certain you'll be back here asking for help if you use it. Its always better to update your stuff manually rather than using an app.
 
Hello everybody.
I have installed Atmosphere on my Switch, is it ok if I turn wifi on emuNAND so that I can upgrade the firmware, bootloaders and Atmosphere from ALL-In-One Switch Updater or will I get banned?

Kind regards

Recommend updating the Hekate/Atmosphere files manually, you can use hekate usb mounting feature to replace the old file, and grab firmware update files from Darthsternie and update via daybreak.
 
Only issue with constant SD card switching is that you can damaged that slot.
Don't worry. It won't be constant. I have an OLED that is used much more frequently for legitimate purchases and stuff. It'll be in SysNAND incredibly rarely.
 
Don't worry. It won't be constant. I have an OLED that is used much more frequently for legitimate purchases and stuff. It'll be in SysNAND incredibly rarely.

You can use one SD card if it large enough, that would at least save some hassle with dealing with broken SD card connector. As long you partition your NAND correctly you would be fine.
 
I have a couple questions that perplex me a bit, I just want to make sure I haven't made a horrific mistake.

I've done the backups of NAND, Keys, all fine.
I've created an Emunand, made sure Exosphere is installed, all that good stuff - Serials say zeroes and I can't connect to nintendo servers.

Is it normal for all of my save data and installed games to also be on the emunand? Is it fine to conclude that it literally copies everything, and doesn't just make a blank?

Also, I've made sure it's actually booted into emunand, it says AMS 1.4.0|E.
 

Site & Scene News

Popular threads in this forum