EmuMMC broke after istalling Kirby (Unknown pkg1 version hos version not supported)

[Amingo]

Hi everyone,

I recently installed Kirby and the forgotten land through the DBI (MTP responder over USB). After installation my system crashed and now when I'm trying to boot into EmUMMC i get the error "Unknown pkg1 version. HOS version not supported! Or emuMMC corrupt!". I have to mention that I did not updated to OFW 14.0.0.

As of now I have updated Atmosphere to version 1.3.0 (pre-release), updated Hekate to version 5.7.2 and put on the latest sigpatches but still get the error. I also just now removed fusee_primary.bin in the bootloader folder and put fusee.bin there.

Any idea what I can still try? Maybe delete the atmosphere folder and put it there from scratch?

Atmosphere without EmuMMC is still working.

Thanks for any help!

Edit: To anyone reading this in the future. For mer personally the "unknown pgk1" error can be resolved by going into Hekate -> emuMMC -> migrate emuMMC. On the popup which comes up you can choose to "Fix RAW" which made me able to boot into Atmosphere/emuMMC again.

 

[Cyan]

If you have all latest AMS files and patches, then it's probably your emuMMC.


random suggestions only:

- Be sure you have all the compatible and proper AMS version. don't mix files (like old Hekate boot file with newer AMS, or the contrary, etc.)
Check your hekate ini file to be sure it's loading fusee and not primary.
check your hekate ini file to be sure it's loading the proper secondary file if you don't use fusee

don't just overwrite files when updating from an old AMS! you have to edit the hekate ini file.
you don't have the same error message, but I put it here just in case someone is interested
https://gbatemp.net/threads/error-f...here-fusee-secondary-bin.603097/#post-9694221

- Restore your last backup (if you did any) of your emuMMC.
if not, you might have to redump MMC to emu.
I do emuMMC backup at times, in case something like this happen.

- You could try to open emuMMC in TegraExplorer and delete kirby files and folders.
I have no idea how easy it is. never tried.

 

[Amingo]

If you have all latest AMS files and patches, then it's probably your emuMMC.


random suggestions only:

- Be sure you have all the compatible and proper AMS version. don't mix files (like old Hekate boot file with newer AMS, or the contrary, etc.)
Check your hekate ini file to be sure it's loading fusee and not primary.
check your hekate ini file to be sure it's loading the proper secondary file if you don't use fusee

don't just overwrite files when updating from an old AMS! you have to edit the hekate ini file.

- Restore your last backup (if you did any) of your emuMMC.
if not, you might have to redump MMC to emu.
I do emuMMC backup at times, in case something like this happen.

- You could try to open emuMMC in TegraExplorer and delete kirby files and folders.
I have no idea how easy it is. never tried.

Thank you so much for your extensive reply.

I have AMS, Hekate, Sigpatches all on the currently most recent available version.

My hekate_ipl.ini looks like this:

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

{hekate with sigpatches}
{}
{Provided by: WiiDatabase.de}
{}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

Seems like CFW EMUMMC is neither loading fusee_primary.bin (which i deleted) nor fusee.bin but atmosphere/package3? Is this correct?

I tried TegraExplorer, good idea! But when I want to browse emuMMC it just freezes (normal MMC can be browsed no problem).

I actually do have an EmuMMC backup made through hekate but it it's almost one year old so I really only want to go back to this as a last resort..

 

[Cyan]

atmosphere/package3? Is this correct?

yes, this is good.

There are two ways to boot AMS, either with fusée.bin (old primary method) or with Hekate fss0 launching package3 (old secondary method).

You could try to boot Fusée.bin directly.
copy Atmosphere's latest "fusee.bin" into sd:/bootloader/payloads/ folder
Launch Hekate, select "payload" menu instead of "boot" menu. and choose to launch Fusée.bin from the payload list.

note: fusee.bin (primary method) will always launch EmuMMC if present.

But when I want to browse emuMMC it just freezes

It really feels like your emuMMC is corrupted.

I would suggest to wait for other user's opinions before replacing your emuMMC. Maybe someone has other ideas.

 

[urherenow]

package3 is correct. You either crashed during a system update, or your hekate and Atmosphere files are NOT the latest, even if you think they are. If in Windows, right-click on the .zip for both of them and check for a security thing on the bottom with a check box next to "unblock". You should be able to self-intuit what to do from there (if you see it)...

 

[Cyan]

I have no idea what this zip security and unblock thing you are talking about are. never seen that. It might be a new thing on recent winzip, or recent windows only.
I also don't see how it can help him know if he has latest version of hekate/AMS.

 

[Amingo]

yes, this is good.

There are two ways to boot AMS, either with fusée.bin (old primary method) or with Hekate fss0 launching package3 (old secondary method).

You could try to boot Fusée.bin directly.
copy Atmosphere's latest "fusee.bin" into sd:/bootloader/payloads/ folder
Launch Hekate, select "payload" menu instead of "boot" menu. and choose to launch Fusée.bin from the payload list.

note: fusee.bin (primary method) will always launch EmuMMC if present.

It really feels like your emuMMC is corrupted.

I would suggest to wait for other user's opinions before replacing your emuMMC. Maybe someone has other ideas.

Directly launching fusee.bin results in "Invalid GPT signature" error.

package3 is correct. You either crashed during a system update, or your hekate and Atmosphere files are NOT the latest, even if you think they are. If in Windows, right-click on the .zip for both of them and check for a security thing on the bottom with a check box next to "unblock". You should be able to self-intuit what to do from there (if you see it)...

I have done the unblock thing and re-copied all the files. Also renamed atmosphere and bootloader folder to "atmosphere_old" and "bootloader_old", coppied everything from AMS and hekate again and it's still not working.

Really sucks but I guess my EmuMMC is actually corrupted.

After restoring my EmuMMC backup from about one year ago (done while at FW 12.0.1) what would be gone? Savegames probably and every NSP I installed from there? Ams / Hekate should still be up to date since they are on the other SD-card partition, right?

I also have a complete image from my SD card from only November 2021. Since the image also contains the hidden EmuMMC partition I could also try to restore the entire SD card no? I know that my savegames would be gone but all the NSPs since then i could reinstall.

 

[Takokeshi]

I'd be tempted to consider your emummc as corrupted, given that everything was working just fine beforehand and that stuff stopped working after some amount of SD card writes...

 

[Amingo]

I'd be tempted to consider your emummc as corrupted, given that everything was working just fine beforehand and that stuff stopped working after some amount of SD card writes...

Yeah it kinda makes sense like this. Thanks for your reply.

 

[Cyan]

after restoring the backup, you'll have to update HOS, reinstall the titles (nsp/xci), restore the savegames if you made regular backup on SD card with homebrew you'll still have them.

 

[urherenow]

I have no idea what this zip security and unblock thing you are talking about are. never seen that. It might be a new thing on recent winzip, or recent windows only.
I also don't see how it can help him know if he has latest version of hekate/AMS.

I fixed someone's problem just yesterday because of it. It's a "feature" that's been around for a hot minute, since at least the beginning of windows 10 as part of "smart screen". When you download files from the internet and the files are unknown, it puts a block on them. I'm guessing that package3 is one of those files. And it's not only a complete block, but some kind of metadata gets tacked on, so that it sees it as blocked. This has caused problems with people who supposedly could launch emummc, but could not use hekate's "stock" option (because "stock" still uses exosphere from package3).

https://thegeekpage.com/disable-blocking-of-downloading-files-in-windows-10/
https://www.majorgeeks.com/content/page/unblock_blocked_files.html

 

[Takokeshi]

Yeah that's the risk with emummc. SD cards corrupt easier than on-board emmc would. I'd suggest making regular savegame backups to PC just in case, so you can recover without losing too much progress if corruption happened again. Hopefully you didn't lose too much :x

Actually, even if hekate can't boot it, it's possible you might be able to decrypt and open your emummc with nxnandmanager or hacdiskmount, and salvage your save data from it. Then you could inject it into a fresh emummc and not lose progress. I would at least try that before wiping and starting over.

 

[Cyan]

When you download files from the internet and the files are unknown, it puts a block on them.

Oh, I completely forgot about this annoying thing, I always disable it at windows install since WinXP
Thanks for sharing

 

[bibliomon]

"Invalid GPT signature"

Definitely a corruption error especially since it occur after putting/installing a large file. Just ensure the SDcard being used is 100% original and for future set-up, format to fat32 to reduce risk of corruption.

 

[Amingo]

So thanks again everyone for the help.

I restored my older SD-image, updated everything again and while re-installing some .NSPs it crashed again leaving me with the error from my initial poast. Could be a problem with DBI-Installer (installing over MTP / USB), a bad microSD card or a bad switch sd card slot.

 

[urherenow]

So thanks again everyone for the help.

I restored my older SD-image, updated everything again and while re-installing some .NSPs it crashed again leaving me with the error from my initial poast. Could be a problem with DBI-Installer (installing over MTP / USB), a bad microSD card or a bad switch sd card slot.

post a pic of your sd info screen from nyx

Is your emuMMC file or partition based, and how did you format it?

Also... I personally have 1 (out of 4) ports on the front of my computer that glitches all the time. disconnects and reconnects. Perhaps I fried it using the MSI supercharger...

 

[urherenow]

crap. Double post. Sorry.

 

[Sheriff]

Adding to the discussion. I tried to install Brilliant diamond moments ago on my emuMMC on the 14.0.0 operating system, and I'm running into the same issue. Really strange.

It was perfectly fine, right after I installed the game my Atmosphere crashed due to an error, and now I'm experiencing the same symptoms as you... I guess this is why you avoid the pre-releases.

 

[Amingo]

Adding to the discussion. I tried to install Brilliant diamond moments ago on my emuMMC on the 14.0.0 operating system, and I'm running into the same issue. Really strange.

It was perfectly fine, right after I installed the game my Atmosphere crashed due to an error, and now I'm experiencing the same symptoms as you... I guess this is why you avoid the pre-releases.

Strange, but for me personally I can say that the problem has nothing to do with the pre-release because the first time it appeared I was still on AMS 1.2.6.

I actually found out that the "unknown pgk1" error can (atleast in my case) be resolved by going into Hekate -> emuMMC -> migrate emuMMC. On the next screen you can choose to "Fix RAW" which made me able to boot into Atmosphere/emuMMC again.

I also used Goldleaf (instead of DBI), another USB cable and another USB port on my PC to re-install all the missing NSPs and it worked without crashing. This at first led me to the conclusion that either DBI, the usb cable or the usb port was the initial problem. However I once again had another system crash yesterday while casually trying to check my system data (through the switch settings menu) which resulted in an unbootable emuMMC with the error "unknown pgk1"...

So lastly some kind of underlying problem seems to persist with my install. I will now test the SD card itself for problems with h2testw and if it turns out fine I will try to completely setup my SD from scratch again.

 

[bibliomon]

Strange, but for me personally I can say that the problem has nothing to do with the pre-release because the first time it appeared I was still on AMS 1.2.6.

I actually found out that the "unknown pgk1" error can (atleast in my case) be resolved by going into Hekate -> emuMMC -> migrate emuMMC. On the next screen you can choose to "Fix RAW" which made me able to boot into Atmosphere/emuMMC again.

I also used Goldleaf (instead of DBI), another USB cable and another USB port on my PC to re-install all the missing NSPs and it worked without crashing. This at first led me to the conclusion that either DBI, the usb cable or the usb port was the initial problem. However I once again had another system crash yesterday while casually trying to check my system data (through the switch settings menu) which resulted in an unbootable emuMMC with the error "unknown pgk1"...

So lastly some kind of underlying problem seems to persist with my install. I will now test the SD card itself for problems with h2testw and if it turns out fine I will try to completely setup my SD from scratch again.

would love to know the h2testw result...wonder if the gpt error is in fact usually caused by failing sdcard.