Hacking SWITCH NOOB PARADISE - Ask questions here

[Draxzelex]

Thank you for your reply. Apologies as I meant I have since upgraded the emuMMC's firmware to 12.0.1 with Daybreak whereas the sysMMC is currently on 12.0.2. I'm still a noob especially with Atmosphere so hope that makes sense. I'm using the latest Atmosphere ver 0.19.3 (when I switched over from SXOS I believe I got 0.19.2 and my firmware was 11.x on both CFW & OFW and I was still on these versions when I started getting the error).

Unfortunately I can't really pin where I went wrong as the installation appeared to work fine when I switched over a few days. I was on CFW without the error, then rebooted into OFW for a couple of days, shut down the console and dropped Tinfoil onto the sd card then when I went to boot Atmosphere I got that error. I have since updated everything to latest (apart from emuMMC not being 12.0.2) but no luck. I haven't attempted to downgrade but I do have an eMMC backup. Do you think if I get the emuMMC updated to 12.0.2 it might help, or might I be looking at possibly doing a restore? Thank you!

Well that error is typically caused by a mismatched fuse count. While your sysMMC is on 12.0.2, the console expects a fuse count of 15. Your emuMMC however is on firmware 12.0.1 which expects a fuse count of 14 so this might be the issue. Since there is not much to lose by upgrading your emuMMC to 12.0.2, I would recommend doing that first so the firmware matches the fuse count at least. If the issue is still not resolved by then, the next step would be to restore your eMMC backup.

 

[Ed12]

Well that error is typically caused by a mismatched fuse count. While your sysMMC is on 12.0.2, the console expects a fuse count of 15. Your emuMMC however is on firmware 12.0.1 which expects a fuse count of 14 so this might be the issue. Since there is not much to lose by upgrading your emuMMC to 12.0.2, I would recommend doing that first so the firmware matches the fuse count at least. If the issue is still not resolved by then, the next step would be to restore your eMMC backup.

Thank you, I will give that a try. I assume we are not allowed to discuss sources here but I can only see 12.0.1 on the site I use, would TegraExplorer be the best option if I want to make my own backup?

 

[Draxzelex]

Thank you, I will give that a try. I assume we are not allowed to discuss sources here but I can only see 12.0.1 on the site I use, would TegraExplorer be the best option if I want to make my own backup?

By backup, do you mean eMMC backup or something else?

 

[Ed12]

By backup, do you mean eMMC backup or something else?

In this guide I am reading it says to use TegraExplorer to dump the sysMMC firmware and then use that to update the emuMMC, would that be the best/correct way to go about that to your knowledge? Before when I updated my emuMMC FW to 12.0.1 I had used publicly available FW files so I hadn't gone through this step.

 

[Draxzelex]

In this guide I am reading it says to use TegraExplorer to dump the sysMMC firmware and then use that to update the emuMMC, would that be the best/correct way to go about that to your knowledge? Before when I updated my emuMMC FW to 12.0.1 I had used publicly available FW files so I hadn't gone through this step.

I understand now. In lieu of a public dump, you wish to make a dump of the firmware yourself. That being said, there are more user-friendly tools available to dump Switch firmware files. For example, take this newly updated Firmware Updater tool. This should be much easier to use than TegraExplorer for your needs.

 

[Zetareta]

I am not familiar with that guide so I do not have an opinion on it. I have been recommending this guide since its from the forum to help people transition from SX OS to Atmosphere.

Thank you.

 

[linkref]

Hi,

Switch lite with sx lite here

I was using sx os emunand without any problem but i decided to migrate to Atmosphere.
I wanted a fresh start so I cleaned up SD & Switch, create emunand with hekate and run the fusee payload through hekate.

Everything works fine but... I have to wait 4 minutes until atmosphere boots up...
I have emunand on files, sd is sandisk official, 20mo/s write.

Any ideas.. ?

 

[Draxzelex]

Hi,

Switch lite with sx lite here

I was using sx os emunand without any problem but i decided to migrate to Atmosphere.
I wanted a fresh start so I cleaned up SD & Switch, create emunand with hekate and run the fusee payload through hekate.

Everything works fine but... I have to wait 4 minutes until atmosphere boots up...
I have emunand on files, sd is sandisk official, 20mo/s write.

Any ideas.. ?

Fusee takes longer to load Atmosphere than Hekate. Instead of running fusee through Hekate, have Hekate directly boot Atmosphere. You will need a hekate_ipl.ini with the proper configuration in order to do that which you can find on SDSetup.

 

[linkref]

I think i have a big issue with my installation...
I can't install any nsp or launch any homebrew i have the 2168-0001 error code, what do you advise me to do.. ?

 

[Draxzelex]

I think i have a big issue with my installation...
I can't install any nsp or launch any homebrew i have the 2168-0001 error code, what do you advise me to do.. ?

Well you need patches to install .NSP files which you can find in the pinned thread on this forum. As for the error code, there should be a program ID attached to it. Usually, you can fix it by deleting that program ID from your /atmosphere/contents folder. It also helps if you launch the homebrew menu by holding R over a game rather than launching it from the Album so you do not enter Applet Mode.

 

[linkref]

I have the patches... I can"t even install tinfoil through his nsp installer

 

[Draxzelex]

I have the patches... I can"t even install tinfoil through his nsp installer

Are you sure you have the patches? Unfortunately there are many different places where you can download patches but not all of them are updated or give you the right set. And seeing as you cannot install a .NSP file, then the issue is more likely due to patches since you need those to install and launch any .NSP file.

 

[shurillu]

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

 

[Draxzelex]

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

I think you are a bit confused. There is no such thing as a CFW 11.0.1. 11.0.1 can only refer to Nintendo Switch firmware version. CFW follows a different numbering scheme depending on the CFW you use. Since you are using Atmosphere, the latest version is 0.19.3. Ensure you are using that version instead of whatever version you are using.

 

[linkref]

Are you sure you have the patches? Unfortunately there are many different places where you can download patches but not all of them are updated or give you the right set. And seeing as you cannot install a .NSP file, then the issue is more likely due to patches since you need those to install and launch any .NSP file.

Ok thanks you ! My problem was i was in applet mode ! I run a game and press R, then I managed to install a xci.
Thanks you for your help !

I wanted to ask you, since i am launching the fusee-primary.bin by renaming it on the SD cart the sx lite boot to atmosphere.
Do you know any way to reboot to sysNand to play online etc ?

Thanks

 

[Bravestarr]

I am on 10.0.4 AMS but AiO Switch Updater v2.4.9 gives only black screen I think I need to update my cfw. So I started AIO Switch updater v2.4.9 but it only shows a black screen. How can I update my cfw and

 

[Draxzelex]

Ok thanks you ! My problem was i was in applet mode ! I run a game and press R, then I managed to install a xci.
Thanks you for your help !

I wanted to ask you, since i am launching the fusee-primary.bin by renaming it on the SD cart the sx lite boot to atmosphere.
Do you know any way to reboot to sysNand to play online etc ?

Thanks

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.

--------------------- MERGED ---------------------------

I am on 10.0.4 AMS but AiO Switch Updater v2.4.9 gives only black screen I think I need to update my cfw. So I started AIO Switch updater v2.4.9 but it only shows a black screen. How can I update my cfw and

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.

 

[shurillu]

I think you are a bit confused. There is no such thing as a CFW 11.0.1. 11.0.1 can only refer to Nintendo Switch firmware version. CFW follows a different numbering scheme depending on the CFW you use. Since you are using Atmosphere, the latest version is 0.19.3. Ensure you are using that version instead of whatever version you are using.

Ok, sorry, but what I mean is: the EmuNAND firmware version is 11.0.1 and now I can't boot it (with Atmosphere 0.19.3).

 

[Draxzelex]

Ok, sorry, buw what I mean is: the EmuNAND firmware version is 11.0.1 and now I can't boot it (with Atmosphere 0.19.3).

Did you boot your 12.0.2 firmware with Atmosphere 0.19.3?

 

[.Darky]

I'm having maybe similar errors as the user above "Failed to match warmboot with fuses, if you continue sleep won't work". If I override the error it boots and runs backups fine, but going into sleep locks the unit until restarted. I recently switched from SXOS to Atmosphere on my Mariko SX Core unit. Had no sleep issues on first boot into Atmosphere, but after rebooting to attempt to add tinfoil I am now getting this error. I have updated Atmosphere/sigpatches/hekate & also updated system to 12.0.2 & CFW to 12.0.1 (might they need to be exactly matching?). Did I mess up something?

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.

Did you ever downgrade your firmware?

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.