Hacking SWITCH NOOB PARADISE - Ask questions here

[shurillu]

Did you boot your 12.0.2 firmware with Atmosphere 0.19.3?

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!

 

[Draxzelex]

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.

Did you ever boot Atmosphere on firmware 12.0.2?

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!

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.

 

[.Darky]

Did you ever boot Atmosphere on firmware 12.0.2?

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.

 

[shurillu]

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.

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!

 

[Draxzelex]

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.

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.

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!

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.

 

[linkref]

As I suggested earlier, not only is launching Atmosphere with Hekate faster but it is more flexible than fusee_primary. You can boot a semi-Stock mode with Hekate which you cannot do with fusee_primary. If you download the hekate_ipl.ini file from the website I mentioned earlier, it will give you all of the launch options you need.

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

 

[Draxzelex]

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?

 

[.Darky]

Hello,
I've upgraded my original firmware to 12.0.2 but I forgot to upgrade my CFW (11.0.1).
Now when I try to boot the CFW I get this message:

Fatal error: [NXBOOT] Failed to determine mariko warmboot firmware

Some infos:

• OFW: 12.0.2
• CFW: 11.0.1
• Atmosphere + hekate version: latest (clean install)
• Switch version: Mariko

There is any chance to boot this CFW version?
If don't, is there any chance to retrieve my savegames from the CFW?

Thanks a lot

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.

 

[Dotmore]

I'm thinking of buying a Switch, but i want to mod it. While i doubt I can go online on pirated games on EmuNAND, how about playing legit games on SysNAND?
Will that still get me banned?

 

[linkref]

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?

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?

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

 

[Draxzelex]

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.

 

[shurillu]

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.

Nope, no luck. I have to find another way.

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 tried both: first booting with hekate payload and then fusee-primary.bin (no way); second fusee-primary.bin directly (nope, same error).

 

[Draxzelex]

Nope, no luck. I have to find another way.

Do you have a warmboot_mariko folder on your SD card? If you do, try deleting it then try to launch emuMMC again.

 

[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've already checked but none, the folder doesn't exist.

Thank you again Draxzelex

 

[Draxzelex]

I've already checked but none, the folder doesn't exist.

Thank you again Draxzelex

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.

 

[Bravestarr]

You can update your CFW by simply deleting the old files and folders from your SD card then placing the new ones on the SD card. Specifically, you should be deleting the /atmosphere and /sept folders. If you have any game mods that you wish to keep, back them up from the /atmosphere/contents folder before deleting the /atmosphere folder.

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?

 

[Draxzelex]

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.

 

[coscino]

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).

1. What is HOS?
   
   
2. 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.
   

 

[Draxzelex]

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).

1. What is HOS?
   
   
2. 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.

1. HOS is short for Horizon Operating System. Horizon is the name of the OS of the Switch similar to how Windows is an OS for most computers
2. Well even if you only plan to use Atmosphere on your emuMMC, the files for Atmosphere itself still have to go somewhere on your SD card and they cannot be placed onto any of the partitions. That is the reason you will need a separate partition for that. There is also room for any legally purchased games that you plan to play on sysMMC which need to be allocated on this separate partition. So basically, there is no way around this separate HOS FAT32 partition

 

[coscino]

1. HOS is short for Horizon Operating System. Horizon is the name of the OS of the Switch similar to how Windows is an OS for most computers
2. Well even if you only plan to use Atmosphere on your emuMMC, the files for Atmosphere itself still have to go somewhere on your SD card and they cannot be placed onto any of the partitions. That is the reason you will need a separate partition for that. There is also room for any legally purchased games that you plan to play on sysMMC which need to be allocated on this separate partition. So basically, there is no way around this separate HOS FAT32 partition

Ah ok now it is clear, thank a lot.
Last question , idk if is allowed on this forum to speak about piracy, in this case i will eliminate my comment immediatly.
In which partition should I put nsp roms of these 4? Because I have now understood there are 4: ubuntu, android, atmosphere and legally purchased partition.