I accidentally pressed update in emummc. After restart and launch, Hekate tells me that it has an unrecognized hos and pkg1 version and that hos failed to launch. I have tried restoring the boot0 and boot1 backup, to no avail. What should I do?
pkg1 not found, restoring boot0&1 doesn't fix it
- Thread starter Aatube
- Start date
- Views 830
- Replies 8
Are your Atmosphere and Hekate updated to the latest versions?
Also, why did you restore boot0/1 but not the rest of the emuMMC backup?
My sd card is currently busy getting the 32g nand backup over, that's why.
How do I check my atmos and hekate versions? I can only access it from the computer right now.
Last edited by Aatube,
If you updated your emuMMC to 13.2.1, for example, then you're going to need to update to Atmosphere 1.2.6 and Hekate 5.7.0.
If that doesn't solve your problem, you're probably going to have to restore your entire eMMC backup since you already restored the boot0/1 backups.
All you probably needed to do was update Atmosphere, Hekate and sig patches but since you have a boot0/1 version that doesn't match your HOS, that won't be enough.
If your sysNAND is up to date I would dump the boot0/1 from it and restore onto emuNAND (uninstall AutoRCM before dumping if you have it) to get back to the state you were in before you restored boot0/boot1 as restoring eMMC RAW will also roll back all your save data to that of the backup so it should be avoided if possible. An eMMC SYS backup is better as it won't affect installed games and save data when restored.
Similar threads
- No one is chatting at the moment.
-
@
Dark_Phoras:
@Veho that's a good observation. I assumed webs were permanent and the authorities and villains studied them. If it is like you say, maybe Pete goes back to clean and the movies don't show it, like they don't show him cleaning the house
you're right. wow
