Hacking EMUMMC Unknow pkg1, SYSMMC HOS loads black screen

Tuto

Member
Newcomer
Joined
Aug 23, 2026
Messages
5
Reaction score
0
Trophies
0
Age
27
XP
8
Country
Honduras
I have spended like 8 hours trying to solve this issue and i don't know what do right now i am so desperate

I tryed
Updating Atmosphere and Hekate to last version
Use Hat Packs
Creating EMUMMC more than 2 times
Launching Recovery Mode using + and -
Format SD card to FAT 32 in hekate and Linux laptop
using the Fix Raw and Archive bit function

i have 23 burnt fuses fw 22.0.0+
i don't know what more to i feel i already tryed to do everything but the issue is always the same
also some months ago i was able to launch HOS OFW perfectly fine and i updated the firmware from the OFW
the reason why i say OFW is kinda launching is because when i start recovery mode my laptop recognize the device saying (Nvida Corp. AYX connected) or something like that
also i noticed that inside emummc RAW there is nothing but a file i think named raw based idk if that is normal, many thanks for anyone that helps me

V2 Switch with PicoFly chip FW version 2.80
 
Last edited by Tuto,
I have spended like 8 hours trying to solve this issue and i don't know what do right now i am so desperate

I tryed
Updating Atmosphere and Hekate to last version
Use Hat Packs
Creating EMUMMC more than 2 times
Launching Recovery Mode using + and -
Format SD card to FAT 32 in hekate and Linux laptop
using the Fix Raw and Archive bit function

i have 23 burnt fuses fw 22.0.0+
i don't know what more to i feel i already tryed to do everything but the issue is always the same
also some months ago i was able to launch HOS OFW perfectly fine and i updated the firmware from the OFW
the reason why i say OFW is kinda launching is because when i start recovery mode my laptop recognize the device saying (Nvida Corp. AYX connected) or something like that
also i noticed that inside emummc RAW there is nothing but a file i think named raw based idk if that is normal, many thanks for anyone that helps me

Test your SD Card for hardware damage,
Backup all files on your SD card on your pc, format it to fat 32 using fat32 format (https://gbatemp.net/download/gui-format.33869/) then test your sd card using H2Testw (https://www.heise.de/download/product/h2testw-50539) or from Downloads section https://gbatemp.net/download/h2testw.39119/


Then upgrade your files using https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148
 
If you have an unpatched / orignal v1 Switch, make sure the payload you inject is also matching the version of Hekate/Atmosphere. If you use an old payload with a newer version, you also get error messages like these.
 
Test your SD Card for hardware damage,
Backup all files on your SD card on your pc, format it to fat 32 using fat32 format (https://gbatemp.net/download/gui-format.33869/) then test your sd card using H2Testw (https://www.heise.de/download/product/h2testw-50539) or from Downloads section https://gbatemp.net/download/h2testw.39119/


Then upgrade your files using https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148
Didn't work, same error, my SD card seems fine though the write speed is slow it has 0 errors, trying to launch Fusee.bin says Package1 seems corrupt i don't know if this is a Nand File or an Atmosphere file
CFW sysmmc and CFW emummc gives the same error

Unknow pkg1 version
HOS version not supported
Trying backup bootloader
Found pkg1 (")
Unknow pkg1 version
HOS version not supported
Failed to launch HOS
Press any key

and Stock just doesn't launch it restarts to OFW and stays to a black screen

i see that the Hats pack contains scripts for Tegra explorer maybe something of there can help? system restore v3, my firmware should be 22.1.0 (23 burnt fuses OFW should boot normally), tried to see EMUMMC folders and files on tegra explorer result

Err: 13
Line:90
File:source/storage/mountmanager.c
DESC: No fat
the SD is in FAT 32
 
Last edited by Tuto,
Ok, with a V2 it usually means that the Hekate/Atmosphere version is too old for the firmware you're trying to run.
Could you double check that the HATS package you downloaded is the latest one and that the hats packages was properly installed in the right folders.
If you can boot Hekate, it will show its version number.
 
Didn't work, same error, my SD card seems fine though the write speed is slow it has 0 errors, trying to launch Fusee.bin says Package1 seems corrupt i don't know if this is a Nand File or an Atmosphere file
CFW sysmmc and CFW emummc gives the same error

Unknow pkg1 version
HOS version not supported
Trying backup bootloader
Found pkg1 (")
Unknow pkg1 version
HOS version not supported
Failed to launch HOS
Press any key

and Stock just doesn't launch it restarts to OFW and stays to a black screen

i see that the Hats pack contains scripts for Tegra explorer maybe something of there can help? system restore v3, my firmware should be 22.1.0 (23 burnt fuses OFW should boot normally), tried to see EMUMMC folders and files on tegra explorer result

Err: 13
Line:90
File:source/storage/mountmanager.c
DESC: No fat
the SD is in FAT 32
MATE then is very probable you have a damaged EMMC or your installation become corrupted, you will need to open the console and test the installation of the ModChip because you are having a trouble with EMMC communication.
 
Ok, with a V2 it usually means that the Hekate/Atmosphere version is too old for the firmware you're trying to run.
Could you double check that the HATS package you downloaded is the latest one and that the hats packages was properly installed in the right folders.
If you can boot Hekate, it will show its version number.
Everything is the latest version, i think my nand is corrupted or something
Post automatically merged:

MATE then is very probable you have a damaged EMMC or your installation become corrupted, you will need to open the console and test the installation of the ModChip because you are having a trouble with EMMC communication
Ok thanks for the help i think is the EMMC corrupted, so i can't do anything more? would copying a backup or an emummc folder from someone else solve the problem at least in the case of emummc?
 
Last edited by Tuto,
Sound like problem is the nand if you can't boot even with sysnand cfw, the emummc fail because emummc just a copy of sysmmc. No Nand backup?

I guess on top of what impeeza said check hekate emmc info see if hekate detect emmc
Post automatically merged:

Everything is the latest version, i think my nand is corrupted or something
Post automatically merged:


Ok thanks for the help i think is the EMMC corrupted, so i can't do anything more? would copying a backup or an emummc folder from someone else solve the problem at least in the case of emummc?

Doesn't work that way, each console is unique. If you got nand backup from firmware 22.0.0 to 22.5.0 you can try those , you can also try earlier nand backup if you got any
 
Last edited by Hayato213,
Sound like problem is the nand if you can't boot even with sysnand cfw, the emummc fail because emummc just a copy of sysmmc. No Nand backup?

I guess on top of what impeeza said check hekate emmc info see if hekate detect emmc
Post automatically merged:



Doesn't work that way, each console is unique. If you got nand backup from firmware 22.0.0 to 22.5.0 you can try those , you can also try earlier nand backup if you got any
When i go to Console info eMMC it seems everything normal theres is info, cid, Ext CSD, eMMC physical partitions, GPP eMMC user partition table, what i should look for?, also i have an backup but i don't think is very old like to solve the problem
 

Site & Scene News

Popular threads in this forum