eMMC backup/restore doesn't work + Nintendo Logo stuck

[forgerer]

Device Information:

• V1 Unpatched Switch
• Atmosphere 1.8.0 (no theme)
• Hekate 6.2.2
• made backups when I first modded the switch, and I still have the backup folder stored on my PC

I used to just dock my NS all the time for charging purposes (I have the auto-RCM enabled, so I never wanted the battery to be drained), and I recently noticed an error message popped up that I did not read carefully (I don't remember what the error was about). I thought the issue will go away if I just reboot my Switch, so I did that and I had no problems booting into Hekate. But then when I tried to boot into emuMMC, I got stuck at the Nintendo Switch logo permanently. Despite searching about this issue for hours, I could not seem to find a proper solution other than just backing up the NAND and remaking the MMC, but then I also realized that my NS won't let me backup eMMC with the following error messages:

00: BOOT0...
Error (5) while creating
backup/dd99ee67/BOOT0
Failed!
01: BOOT1...
Error (5) while creating
backup/dd99ee67/BOOT1
Failed!

Even the backup I made when I first set up the homebrew can't be restored with the following error message:

00: BOOT0...
Error (5) while opening file. Continuing...
01: BOOT1...
Error (5) while opening file. Continuing...

I don't want to start modifying my switch without having the assurance that my backups are working, so I don't know what to do. When I plug in my Switch to my PC via the USB tools > eMMC BOOT0/BOOT1/RAW GPP, it prompts me to format the disk or otherwise I can't do anything with the partitions, so I have no fucking clue if I could just format it and not brick my console. Any guidance on what I should do or if I can start fucking around?

 

[Hayato213]

Do you have the boot0/boot1 and the rawnand gpp?

 

[forgerer]

This is the file tree of backup files I have it on my PC:

• backup
  • dd99ee67
    • restore
      • emummc (empty)
      • partitions (empty)
    • BOOT0
    • BOOT1
    • rawnand.bin.00
    • rawnand.bin.01
    • rawnand.bin.02
    • rawnand.bin.03
    • rawnand.bin.04
    • rawnand.bin.05
    • rawnand.bin.06
    • rawnand.bin.07
    • rawnand.bin.08
    • rawnand.bin.09
    • rawnand.bin.10
    • rawnand.bin.11
    • rawnand.bin.12
    • rawnand.bin.13
    • rawnand.bin.14

BOOT0 and BOOT1 both occupy around 4 MB of storage, and each rawnand file occupies 2097152 KB exactly, except the rawnand.bin.14 one, which occupies 1175552 KB for some reason.

 

[Hayato213]

Sound like problem is your NAND backup if they are from the same dump, you can't mix boot0/boot1 and rawnand from one firmware with another firmware. It must be a set.

 

[forgerer]

Sound like problem is your NAND backup if they are from the same dump, you can't mix boot0/boot1 and rawnand from one firmware with another firmware. It must be a set.

Wait, I don't quite understand. Is the problem that BOOT0/BOOT1/rawnand files are separate, instead of a combined file? I recall that I literally followed what the Making Essential Backups page of the NH Switch Guide told me to do.

Also, sure, let's say my backups are fucked. What do I do now? My whole goal is to be able to boot into emuMMC CFW somehow.

 

[Hayato213]

Wait, I don't quite understand. Is the problem that BOOT0/BOOT1/rawnand files are separate, instead of a combined file? I recall that I literally followed what the Making Essential Backups page of the NH Switch Guide told me to do.

Also, sure, let's say my backups are fucked. What do I do now? My whole goal is to be able to boot into emuMMC CFW somehow.

That is not what I meant what I meant is that the boot0/boot1 has to match with rawnand gpp that the firmware it was dump from, like boot0/boot1 of 18.1.0 and a rawnand of 19.0.0 won't work together. Probably your NAND backup is fucked if you restore them and it won't boot.

 

[forgerer]

That is not what I meant what I meant is that the boot0/boot1 has to match with rawnand gpp that the firmware it was dump from, like boot0/boot1 of 18.1.0 and a rawnand of 19.0.0 won't work together. Probably your NAND backup is fucked if you restore them and it won't boot.

I mean that might explain why I couldn't restore them, but why would I get an error for creating new eMMC backups then? How do fix my system to create a set eMMC backups?

 

[Hayato213]

I mean that might explain why I couldn't restore them, but why would I get an error for creating new eMMC backups then? How do fix my system to create a set eMMC backups?

Well if you don't have a working sysnand/ofw then creating an emunand would not work, if it is the sysannd/ofw backup you are making but the sysnand has a problem then it is no point of making one.

 

[jkyoho]

More like a fked SD card to me. Try another card with fresh Hekate and AMS then make a backup on new SD

 

[forgerer]

That is not what I meant what I meant is that the boot0/boot1 has to match with rawnand gpp that the firmware it was dump from, like boot0/boot1 of 18.1.0 and a rawnand of 19.0.0 won't work together. Probably your NAND backup is fucked if you restore them and it won't boot.

What prompted you to think that my boot0/boot1 and the rawnand have different firmware versions?

Post automatically merged: Mar 24, 2025

Okay, I just confirmed that my eMMC is not dead just yet because I was able to boot into stock, albeit both sysMMC boot and emuMMC boot are not working. Especially for sysMMC, it just becomes a black screen and stays there. So, perhaps something with Atmosphere is broken or the SD card itself?

 

[Hayato213]

What prompted you to think that my boot0/boot1 and the rawnand have different firmware versions?

Post automatically merged: Mar 24, 2025

Okay, I just confirmed that my eMMC is not dead just yet because I was able to boot into stock, albeit both sysMMC boot and emuMMC boot are not working. Especially for sysMMC, it just becomes a black screen and stays there. So, perhaps something with Atmosphere is broken or the SD card itself?

Im not saying that your boot0/boot1 and rawnand are different firmware version but if they were then they won't work, since your is the same firmware it was dumped out problem is probably your backup. If it won't finish booting then it is problem with your NAND.

 

[l7777]

What prompted you to think that my boot0/boot1 and the rawnand have different firmware versions?

Post automatically merged: Mar 24, 2025

Okay, I just confirmed that my eMMC is not dead just yet because I was able to boot into stock, albeit both sysMMC boot and emuMMC boot are not working. Especially for sysMMC, it just becomes a black screen and stays there. So, perhaps something with Atmosphere is broken or the SD card itself?

If OFW works and AMS on sys or emunand don't then it's an AMS and/or SD Card corruption problem not a NAND problem. Try a new SD Card with fresh Hekate/AMS. If that works you can try updating/refreshing Hekate & AMS on your old SD Card but know it likely has some corruption things happening.