Unknown pkg1 version

  • Thread starter Thread starter Safirjiiva
  • Start date Start date
  • Views Views 6,635
  • Replies Replies 15

Safirjiiva

New Member
Newbie
Joined
Oct 20, 2024
Messages
4
Reaction score
1
Trophies
0
Age
20
XP
30
Country
France
After updating the switch firmware to 19.0, trying to boot into my sysmmc gives me the unknown pkg1 error. I have the latest atmosphere version and the lastest fusee.bin and booting into the emummc works just fine. Thanks in advance for the help.
 
After updating the switch firmware to 19.0, trying to boot into my sysmmc gives me the unknown pkg1 error. I have the latest atmosphere version and the lastest fusee.bin and booting into the emummc works just fine. Thanks in advance for the help.
So you updated sysmmc to 19.0.0? What version is emummc?
When you say sysmmc is that cfw or ofw? If cfw then update Atmosphere and Hekate (if you use it). Remember to also update your payload
 
update Atmosphere and Hekate (if you use it). Remember to also update your payload
Thank you for the fast replies, I updated Atmo/ hekate and now I get Panic Occurred while running Atmosphere, tried with the latest sig/sys patches and same error. I made sure to put the latest Fusee.bin in payload and yeah, I get that message.
 
So you updated sysmmc to 19.0.0? What version is emummc?
When you say sysmmc is that cfw or ofw? If cfw then update Atmosphere and Hekate (if you use it). Remember to also update your payload
Emummc is 18.1.0. I have atmosphere's latest version and the latest payloads but i will try updating hekate
Edit: forgot to precise, its cfw sysmmc
Post automatically merged:

Do you both also have the latest Hekate and sigpatches? Sounds like you both forgot to update something.
I have syspatch so my sigpatches should already be updated
 
Last edited by Safirjiiva,
Edit for me: Did a format with Rufus and started fresh in Fat 32, installed latest hekate, atmo, fuse.bin and voila it works fine. Thanks again!
 
Its a USB formatting tool, very nice and easy to use. Always had better result with Rufus than reformatting directly with Windows
The panic was probably from either a sysmoduel not being compatible, you have a theme installed for the pervious firmware, or something along those lines. Next time when you get an atmosphere panic like that, write down the program id, then look in "sd/atmosphere/contents" it's a good possibility you'll find them problem in there
 
  • Like
Reactions: BigOnYa
happened to me when i updated sysnand to 19 on stock fw (without hekate cause hekate prevents burning fuses). if your To boot FW is lower than ur burned fuses, youll get that error)
Post automatically merged:

The panic was probably from either a sysmoduel not being compatible, you have a theme installed for the pervious firmware, or something along those lines. Next time when you get an atmosphere panic like that, write down the program id, then look in "sd/atmosphere/contents" it's a good possibility you'll find them problem in there
or this
 

Site & Scene News

Popular threads in this forum