Glad I'm not alone. I migrated from SXOS back in december too. Please let me know if you manage to solve your problem after updating emuNAND to 12.0.2. Seems to be the same issue I have.
Nope, never.
Seems it was related to burnt fuses as I said in previous posts. Sadly I don't have an eMMC backup, hope updating emuNAND solves this.
Last edited by .Darky,
I updated my original firmware to the 12.0.2 version then I noticed that I can't boot anymore the EmuNAND (which is 11.0.1 version) with the error posted in the previous post.
So I tried with a fresh installation of Atmosphere and Hekate to the last versions but without success (same error).
Finally I took a new uSD and I made a new EmuNAND dump from the original firmware (12.0.2) and with latest version of Hekate and Atmosphere it boot without an issue.
So my question is: there is any chance to boot the old EmuNAND? I need to recover the savegames stored in that EmuNAND.
Thanks!
Did you ever boot Atmosphere on firmware 12.0.2?
According to SciresM, that error is due to you not booting on the higher firmware version before the lower firmware version. Once you boot Atmosphere on firmware 12.0.2, it should work on your 11.0.1 emuMMC.
Well, yes. The error message gives the option to press the power button to boot Atmosphere / emuNAND anyway. Like I said it boots fine and all games work, but I can't put the system on sleep mode since it will freeze.
Mmmm... So if I made a brand new uSD with the latest Atmosphere and Hekate with a new EmuNAND from the 12.0.2 firmware and I boot my switch from that; THEN I delete ONLY the EmuNAND replacing that with the old one (the 11.0.1) this could be fix my booting problems?
I'll give a try..
Thanks!
Alright I can only think of one other thing to try before updating your emuMMC. If you have it, try deleting any /warmboot_mariko folder you may have on your SD card.
If you really do not wish to boot Atmosphere on sysMMC, this is a valid option. I patiently await your findings and wish you luck.
I tried thoses solutions with hekate_ipl.ini, but when i boot atmosphere that way i have a error message boot0 : couldn't parse boot0:success!
The only way i manage to do it is booting fusee-primary directly by renaming it payload.bin
Let me see the hekate_ipl.ini file. And while you're at it, can you also tell me whether or not you are using the latest version of Hekate?
Are you using fusee_primary as a payload or Hekate? Seems you have a similar problem to mine and @Ed12. Probably something that only affects Mariko since we ported from SX OS initially.
I double check everything now all is okay, thanks to you !!!
I have a question : is it possible on hekate to hide all option except launch ? It's for kids.
Or use an alternative to hekate which can do the same thing as the "Launch" function of hekate, this is to prevent kids to mess up everything.. and be more user frindly
While Hekate can be customized, there is a limit to the customization. You cannot modify the Hekate home menu options probably because some of those options are very crucial to Hekate's utility. Still there is room for improvement. You can remove some of the launch profiles after selecting Launch by deleting them from the hekate_ipl.ini file. If you just want to use Hekate to boot Stock or another mode without navigating the menu, you can setup autoboot which will automatically boot one of the launch profiles when you use Hekate. While autoboot is enabled, you can hold volume (-) to prevent that launch profile from being automatically booted in order to enter the regular Hekate menu.
Nope, no luck. I have to find another way.
I tried both: first booting with hekate payload and then fusee-primary.bin (no way); second fusee-primary.bin directly (nope, same error).
Last edited by shurillu,
Do you have a warmboot_mariko folder on your SD card? If you do, try deleting it then try to launch emuMMC again.
I think you should try my original advice and boot Atmosphere one time on your 12.0.2 sysMMC. From what I have heard, it is not as unsafe as you may think it is because some people only boot Atmosphere and are not banned yet.
Okay but why does the app that should do this job not start? It would be easier if I could just start the process from within the app. And if this can not be repaired: Where do I get the correct files?
I don't know the specifics of why the app is not working but issues like these are primarily why I NEVER recommend updater applications to anybody. They are always known to be buggy or have problems but most importantly, they are always inferior to manually updating files. Rant aside, you can grab Atmosphere from its official GitHub repo, patches from the pinned thread on this forum, and if you use Hekate, you can download that from its GitHub page as well. Anything else you would need would just be specific homebrew applications that you personally use and can be found via looking up their specific GitHubs.
Hello, please tell me if this is the wrong method to ask help in this forum
I am following mr Rabbit youtube tutorial for quad booting the switch but I didn't understand completely because I am a newby. (I don't even have a switch, i have bought an unpatched switch on ebay just today and I am reading now tutorial on how to hack it).
I am following mr Rabbit youtube tutorial for quad booting the switch but I didn't understand completely because I am a newby. (I don't even have a switch, i have bought an unpatched switch on ebay just today and I am reading now tutorial on how to hack it).
- What is HOS?
- I understand we have to do a partition for android and one for linux but why a partition of emuMCC of just 29gb and a separate partition(HOS FAT32). For what I am guessing HOS FAT 32 is the space for the pirated/personally dumped switch games. Because if it was for me I would create an android partition, a linux partition and an Atmosphere partition with Atmosphere OS and all the switch roms.
