Unknown pj1 version, HOS version not supported ! or emuMMC corrupt!

  • Thread starter Thread starter satoruyan
  • Start date Start date
  • Views Views 1,065
  • Replies Replies 2

satoruyan

New Member
Newbie
Joined
Apr 23, 2024
Messages
4
Reaction score
0
Trophies
0
Age
26
XP
42
Country
United States
Hi, I tried searching around for a month for a fix but still haven't found one.

All was well with my switch until I pulled the SD card while it was on, and it started spitting out "cannot mount SD card glitches"

So, stupidly, I tried to made a drag-and-drop SD Card backup onto a hard drive, formatted my SD card and tried to simply drag and drop my files back in, but all my stuff was missing.

I thought all was lost and tried making a new EmuMMC in RAW1. But it turns out, I actually had a file-based EmuMMC in ER00.

So I tried to set my EmuMMC to the ER00 in Hekate after deleting my old one, but now I'm back to getting this error:

"Unknown pkg version.
HOS version not supported!
Or emuMMC corrupt!

Trying backup bootloader...
found pkg1 ('').

Unknown pkg1 version
HOS version not supported!
Or emuMMC corrupt!

Failed to launch HOS!
press any key..."

How do I fix this?

For reference, here is the drag-and-dropped backup
1750379036846.png

This is the EmuMMC folder:
1750379065394.png

1750379090155.png

1750379113591.webp

192GB was the same GB size my SD card held before all the errors.
1750379101872.png

Here is my current SD card set up, I tried (and probably messed up) trying to update my Atmosphere, Bootloader, switch, hbmenu.nro, hekate.bin, and payload.bin files.
1750379236314.png
 
Usually those kinds of errors are solved automagically by installing the latest versions of Hekate/Atmosphere /Sigpatches.
Some people just use the all-in-one HATS package while others just grab the latest releases from GitHub.

Take care not to delete your filebased emummc.
 
Usually those kinds of errors are solved automagically by installing the latest versions of Hekate/Atmosphere /Sigpatches.
Some people just use the all-in-one HATS package while others just grab the latest releases from GitHub.

Take care not to delete your filebased emummc.
Unfortunately, the problem wasn't automagically solved by dragging and dropping the HATS package. Downloaded the latest pack, dragged, dropped, replaced files on SD card.

I'll try it with a different SD card and report back.

Also, I was thinking: maybe my problem is the file-based EmuMMC? Maybe Hekate is having problems accessing it?
This is what the EmuMMC.ini file looks like on my backup:
1750446644616.png
This is what it looks like on my current SD card, the id changed.
1750446578742.png
The files within the EmuMMC/Nintendo folder look like this, does this look correct for a file-based EmuMMC?
1750446808660.png

The Album photo is a bunch of saved screenshots and stuff.

Contents is full of various folders.
1750446892684.png

placehld is empty, registered has 2.18GB of folders, though some are empty:
1750446967329.png


save has two files from 2021:
1750447000067.png


A lot of files seem to be missing though, the ER00 on my backup drive is 192GB with 700+ files. Should I try to drag and drop the backup into the SD card?

Backup drive:
1750448067402.png


The backup drive's two "save" folder files are from 2023.
Every folder in Registered is full with at minimum two files.


Switch SD card:
1750448106168.png

It's been a really long time since I've had to backup my SD card to change to a bigger size, I'm 99% sure I picked the "file based EmuMMC" option instead of the partition based one.
 

Site & Scene News

Popular threads in this forum