Hacking How do I update emuNAND OFW?

ignudi · Jun 30, 2020

hi. i also have the same problem with Error 2011-0301 every time i launch homebrew menu. either by holding R and double-tapping the Album icon, or by launching Puyo Puyo Tetris (game card), then holding R while choosing my user icon.

my switch is unpatched. bought it december 2017 (before nintendo patched the tegra bug). it came with 4.1.0 OFW. never connected it to the internet. only used it for game cartridges (no online games). i do not wish to connect this switch to download games nor have any plans to update the 4.1.0 firmware (NSPs/XCIs or game cartridges would be enough for my needs and i can always install CFW on emuMMC and update that instead).

i downloaded the latest hekate (0.5.30) and atmosphere (0.13.0), and followed the instructions by @scandal_uk above to format my 64GB microSD using FAT32 (previously checked for bad blocks, none found). i have created the hidden partition and set up emuMMC on it. i even edited the hekate_ipl.ini file as instructed. i can inject hekate using NS-Atmosphere payload dongle (the white one).

i can successfully load atmosphere (switch shows 4.1.0|AMS 0.13.0|E in Settings). but when i try to access the homebrew menu, the switch crashes and Error 2011-0301 appears. therefore i cannot load choidujournx in homebrew menu to update my emuMMC CFW to 8.1.0 (my desired firmware version).

i tried fiddling with the latest version of SX OS (just for test purposes, no intention to purchase a license). followed the instructions, and strangely enough, i was able to access the homebrew menu. so i presume the problem is not with my switch, but with the atmosphere-nx/hekate configuration.

i've been tearing my hair these past few days looking for a solution to this problem. any help would be appreciated. thank you.

fvig2001 · Jun 30, 2020

Worst case, try using an older version of atmosphere like 0.12 then update to 0.13 after the update is completed. I did this via Hekate from 3.0 and I didn't have issues but I did use 0.13 for that.

ignudi · Jun 30, 2020

fvig2001 said:
Worst case, try using an older version of atmosphere like 0.12 then update to 0.13 after the update is completed. I did this via Hekate from 3.0 and I didn't have issues but I did use 0.13 for that.

hi. thank you for the input.

what do you mean by did this via Hekate from 3.0 ? you're referring to your switch's OFW (3.0.0)? and did you use atmosphere 0.13.0? what hekate version did you use for payload? and what CFW version did you update to? Thanks again.

fvig2001 · Jun 30, 2020

Yes NAND 3.0. I used the latest hekate + patches + latest atmosphere

ignudi · Jun 30, 2020

fvig2001 said:
Yes NAND 3.0. I used the latest hekate + patches + latest atmosphere

please clarify what you mean with latest patches. are these the sig_patches? where do i save them on the sd card? and exactly how do these patches work?

in both switch homebrew guides (.io and .guide), the instructions do not require downloading the patches (i.e. optional). thank you.

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

fvig2001 said:
Yes NAND 3.0. I used the latest hekate + patches + latest atmosphere

if the latest hekate and atmosphere releases worked for your 3.0.0 switch OFW as you say, then why don't they work for my 4.1.0 switch?

scandal_uk · Jun 30, 2020

ignudi said:
please clarify what you mean with latest patches. are these the sig_patches? where do i save them on the sd card? and exactly how do these patches work?

in both switch homebrew guides (.io and .guide), the instructions do not require downloading the patches (i.e. optional). thank you.

Check this: https://gbatemp.net/threads/sigpatches-for-atmosphere-0-13-0.567542/

ignudi · Jun 30, 2020

scandal_uk said:
Check this:

hi. thank you for the suggestion.

i was about to try it when, as a final attempt, i downloaded atmosphere-nx 0.12.0 and used this with hekate 5.3.0 as suggested by @fvig2001. i created the hekate_ipl.ini entries as you described in your previous post, then injected hekate. next i created emuMMC on the sd card, then launched atmosphere. i was finally able to access the homebrew menu!

i have a few more questions, if you don't mind:

after i update my emuMMC CFW to 8.1.0, what do you suggest i do next? should i update atmosphere to 0.13.0? and how about the sigpatches you mentioned? should i copy them over to the sd card, or would it be ok to skip copying the files over?
will the stock 4.1.0 OFW of my switch get updated when i update the emuMMC CFW to 8.1.0 using ChoiDuJourNX? or will the update only apply to the emuMMC version (i.e. the stock firmware remains at 4.1.0)?
if the stock OFW won't be affected by the CFW update, should i worry about fuses burning? i mean, if i turn off the switch completely and boot normally (no payload), the switch boot process should still see the expected number of burnt fuses for the 4.1.0 OFW. is this correct?
will updating the emuMMC CFW to 8.1.0 burn a game cartridge fuse? i believe the 9.0.0 does this, but i'm not really certain.

as i mentioned earlier, i do not play games online nor download games from the e-shop (i don't have a nintendo account), and i am content playing with game cards and homebrew games. hence forgive my dogged insistence that the 4.1.0 OFW of the switch remains untouched

. i have made backups of the sysNAND, BOOT0/BOOT1 and prod keys following the .io and .guide homebrew guides.

thank you for providing helpful insights in this forum. your efforts are very much appreciated. :bow:

fvig2001 · Jun 30, 2020

1. Delete all the atmosphere files and hekate files and extract the latest versions of each and their corresponding sig patches if needed (Atmosphere usually needs old files removed to ensure no blackscreens on start up)
2. Update to 10.4 via choudujour nx on emunand
Your actual nand should be untouched if you do everything in emuMMC (make sure you are in the correct nand when doing so.

Fuse burning only happens if the actual NAND on the switch is higher than 4.1 and is booted without atmosphere. Game cart will not be updated normally when you update your firmware. You will not be able to read newer game cartridges until you upgrade the firmware of the game cartridge. Safest way to retain your fuse count is to enable auto-rcm when you update via choudujour nx since you can only boot to horizon via RCM

scandal_uk · Jun 30, 2020

The whole point of emuMMC is so that you can update CFW without burning fuses - of course you must use ChoirDujourNX to update CFW but it won’t affect OFW.

ignudi · Jun 30, 2020

fvig2001 said:
1. Delete all the atmosphere files and hekate files and extract the latest versions of each and their corresponding sig patches if needed (Atmosphere usually needs old files removed to ensure no blackscreens on start up)
2. Update to 10.4 via choudujour nx on emunand
Your actual nand should be untouched if you do everything in emuMMC (make sure you are in the correct nand when doing so.

Fuse burning only happens if the actual NAND on the switch is higher than 4.1 and is booted without atmosphere. Game cart will not be updated normally when you update your firmware. You will not be able to read newer game cartridges until you upgrade the firmware of the game cartridge. Safest way to retain your fuse count is to enable auto-rcm when you update via choudujour nx since you can only boot to horizon via RCM

hi. i followed your instructions in a previous post to use atmosphere 0.12.0, and i was able to access the homebrew menu. thanks! :bow:

i am quite confused with item 1 above. if i start with a clean sd card and copy over the latest atmosphere and hekate files, where does the line delete all the atmosphere files and hekate files apply? did you assume that my sd card had existing hekate and atmosphere files, hence the instruction?
if i were to download atmosphere 0.13.0 and hekate 5.3.0 (as i previously did the past few days), but this time copying over the sigpatches files, would this now allow me to access the homebrew menu?

i am aware that newer game cards won't be read by the switch if i don't upgrade to at least 9.0.0. but if i do so, i will lose game cartridge capability once i decide to boot to stock 4.1.0 FW, hence my hesitation. unless there is an exploit similar to hekate that bypasses game cartridge fuse checking?

thank you so much for being patient and informative.

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

scandal_uk said:
The whole point of emuMMC is so that you can update CFW without burning fuses - of course you must use ChoirDujourNX to update CFW but it won’t affect OFW.

thank you so much for the clarification.

scandal_uk · Jun 30, 2020

And don’t try to launch the homebrew menu from the album, hold R and select a game instead, keep R pressed until it actually launches

ignudi · Jul 1, 2020

scandal_uk said:
And don’t try to launch the homebrew menu from the album, hold R and select a game instead, keep R pressed until it actually launches

hi. i tried using atmosphere 0.13.0 with hekate 5.3.0 and copied the sigpatches from the link you gave. but the switch still crashes with error 2011-0301 when trying to access the homebrew menu.

if i use atmosphere 0.12.0 with hekate 5.3.0 instead, i can access the menu.

what could be the problem with atmosphere 0.13.0 that it crashes the switch when i access the menu
the homebrew menu in atmosphere 0.12.0 says it's in 'applet' mode. is this correct? if my homebrew menu is in 'applet mode', will i be able to use ChoiDujourNX to update my emuMMC CFW to 8.1.0?

by the way, holding R continuously (whether opening a game or the album) doesn't launch the menu.

thanks!

Sparkss · Jul 10, 2020

ignudi said:
hi. i tried using atmosphere 0.13.0 with hekate 5.3.0 and copied the sigpatches from the link you gave. but the switch still crashes with error 2011-0301 when trying to access the homebrew menu.

I have the exact same issue with a newly setup Switch. I don't much care about HBL outside of being able to update the emunand and installing NSPs. For the latter I can install an NSP of the Awoo installer, then only need to deal with upgrading. I am using my SX Pro dongle to boot directly into Atmos. Time for more reading.

scandal_uk · Jul 10, 2020

Sparkss said:
I have the exact same issue with a newly setup Switch. I don't much care about HBL outside of being able to update the emunand and installing NSPs. For the latter I can install an NSP of the Awoo installer, then only need to deal with upgrading. I am using my SX Pro dongle to boot directly into Atmos. Time for more reading.

have you tried booting with the TegraRcmGUI?

Sparkss · Jul 10, 2020

scandal_uk said:
have you tried booting with the TegraRcmGUI?

Yes, used TegraRcmGUI and injected the fusee_primary that came with Atmos 13. Unfortunately the same result.

I think that something got borked on my EMU(NAND) since I tried Atmos 12 (deleted all Atmos 13 files/folders) and installed Atmos 12 files (+ patches), now it won't boot at all, just goes to black screen after Atmos logo (no Sept logo). So I deleted all of the Atmos 12 files/folders, copied back over the Atmos 13 ones I had saved off, and now that won't boot either (same behavior). the only thing consistent is the Emu (well, and the SD Card, which worked before. It is a PNY 256 GB card). I also tried booting it a couple of ways, via dongle, TergraRCM and chainloaded through Hekate. All with the same results. I did mage sure that each method was using the correct, matched fusee_primary.bin for the version of Atmos I was trying to load. It is a bit frustrating as I had .13 running, just had the homebrew menu issue.

The only persistent files are a couple of homebrew NROs and the EMU ini file, which were all there before. I will try wiping the card and starting over, just hate to go through that if I don't need to

. The next time through I will go with Atmos 12 to start. I have to get some actual work done today, so this will be a "tonight" project.

scandal_uk · Jul 10, 2020

You clearly seem to know a bit and have picked up some knowledge along the way, which is refreshing!

When I want to use an SD card fresh - I remove all partitions using Windows Disk Manager, then allocate one with all the space (doesn’t matter about it being exFAT).

Then follow my directions on the previous page using Hekate (the SD space will be FAT32 afterwards).

Sparkss · Jul 10, 2020

scandal_uk said:
You clearly seem to know a bit and have picked up some knowledge along the way, which is refreshing!

When I want to use an SD card fresh - I remove all partitions using Windows Disk Manager, then allocate one with all the space (doesn’t matter about it being exFAT).

Then follow my directions on the previous page using Hekate (the SD space will be FAT32 afterwards).

Thanks, your feedback is appreciated.

I forgot to mention that I kept it FAT32 (not exFAT), so the FS was not the issue

. I use Partition Wizard Free Edition for most of my partition activities, it is also what I used to format the SD card to FAT32 initially.

If I had never gotten it to boot Atmos I would be taking a different approach, but as it did boot (a couple of times, trying different ways to get the HBMenu to launch), I know the end to end chain is (was) good. I do suspect Atmos 13 of doing something to the EMU, because nothing else persisted across my tests and also because others reported some previously installed apps not working after downgrading from Atmos 13 back to 12. That points to something potentially being altered on the user part of the EMU.

I originally set up the EMU using SX OS, but will go the Hekate route this time. I do have all of the tools, as I used those to backup the NAND and pull the keys before I started

. I am thinking of trying a few things first, just to see if I can get it to boot, but wholly expect to be wiping the SD card and starting over before I reach the end of this "journey". I am just one of those that doesn't like to admit defeat, and wiping the card is a sort of mini-defeat

. After I do get the card setup again I intend to take a backup image of the SD card, to make "resetting" easier, if it comes to that again.

EDIT: I also don't recall if I mentioned that OFW is still at 3.0.0, which I suspect is playing a role in the HBM not launching. But as I can't get to Choi. to upgrade, it is a bit of a chicken and an egg thing

.

Sparkss · Jul 10, 2020

No joy. Wiped SD card, setup Hekate on SD, pushed bin via tegrarcm, setup EMU, installed Atmos 12 files (+ sigs). Booted into Hekate again (via tegrarcm) and it booted Atmos. Confirmed on the System settings that I was running Atmos. Tried to launch HBM (using Album, as it is a clean system and I have installed apps or carts). I get a different error this time. Diff Error Code and app ID, but I am on Atmos 12 versus previously on 13. I tried booting a couple of different ways, but same result with HBM.

Error Code: 2347-0003 (0x75b)
Program: 010000000000100D
Firmware: 3.0.0 (Atmosphere 0.12.0-master-7bc0250c)

I just have to wonder if it is because the EMU is on 3.0. Any other way to upgrade it w/o upgrading the sysNAND and/or risking a ban? Outside of buying a cartridge and running it while in EMU (letting it update the EMU), however I am not sure how well that would even work as I do have nogc set to 1 to avoid updating the GC slot, but at this point I may not have a choice?

Are there any additional patches, sigs or files needed to use Hekate (5.3.0) as the bootloader for Atmos?

Thanks!

Sparkss · Jul 11, 2020

I did some searching and found this with regards to my most recent error:

I'm getting error 2347-0003?

This means the nro file wasn't found. Make sure your sdcard is inserted, and that it has hbmenu.nro on its root.

I checked and sure enough the .nro was not there, so I copied it over and now am able to boot and launch HBM.IT was in my Atmos 13 backuped folders, but somehow I left it off when I reverted to Atmos 12. I am running through the upgrade using Choi. now.

scandal_uk · Jul 11, 2020

Sparkss said:
I did some searching and found this with regards to my most recent error:

I'm getting error 2347-0003?

This means the nro file wasn't found. Make sure your sdcard is inserted, and that it has hbmenu.nro on its root.

I checked and sure enough the .nro was not there, so I copied it over and now am able to boot and launch HBM.IT was in my Atmos 13 backuped folders, but somehow I left it off when I reverted to Atmos 12. I am running through the upgrade using Choi. now.

Easily done, tricky to diagnose too!

Hacking How do I update emuNAND OFW?

Member

Well-Known Member

Member

Well-Known Member

Member

Not Really There

Member

Well-Known Member

Not Really There

Member

Not Really There

Member

Well-Known Member

Not Really There

Well-Known Member

Not Really There

Well-Known Member

Well-Known Member

Well-Known Member

Not Really There

Similar threads

Popular threads in this forum