Hacking emuMMC corrupted?

  • Thread starter Thread starter zRicky
  • Start date Start date
  • Views Views 2,466
  • Replies Replies 10

zRicky

Member
Newcomer
Joined
Dec 26, 2024
Messages
6
Reaction score
1
Trophies
0
Age
24
XP
23
Country
Italy
Im sorry if this is a repost but im going insane i've checked many posts (including in this forum) and got nothing
I just re-modded my switch after a long time and i've been running in the same error over and over again. I was pretty dumb to update my switch (19.0.1) before this new mod and thats probably why im getting this error but maybe theres a way to fix this, can someone help?

Atmosphere 1.8.0-C6014B53 Max HOS: 19.0.0 Found pkg1 ('') Unkown pkg1 version. HOS version not supported! Or emuMMC corrupt!

Just to be clear, everything in the sd its already at the latest patch (atmos and hekate mostly)
 
Im sorry if this is a repost but im going insane i've checked many posts (including in this forum) and got nothing
I just re-modded my switch after a long time and i've been running in the same error over and over again. I was pretty dumb to update my switch (19.0.1) before this new mod and thats probably why im getting this error but maybe theres a way to fix this, can someone help?

Atmosphere 1.8.0-C6014B53 Max HOS: 19.0.0 Found pkg1 ('') Unkown pkg1 version. HOS version not supported! Or emuMMC corrupt!

Just to be clear, everything in the sd its already at the latest patch (atmos and hekate mostly)
Damn buddy! Sorry this happened to you. Let me ask you this first.is your SD card formatted in FAT32 or exfat? If it's exfat,that's likely why,99% sure. Let's see what the great minds here recommend.
 
Damn buddy! Sorry this happened to you. Let me ask you this first.is your SD card formatted in FAT32 or exfat? If it's exfat,that's likely why,99% sure. Let's see what the great minds here recommend.
nope it is FAT32
 
nope it is FAT32
So you didn't update Atmosphere before updating to 19.0.1? If not,you just need to take your SD card and put it in a PC. Download the latest HATSpack.zip from sthetix. Overwrite your current atmosphere folder copying from the HATS zip file. That should do it. Next time,update your atmosphere and sysmodules before the firmware update. Don't forget to uninstall any themes you might have as well.
 
So you didn't update Atmosphere before updating to 19.0.1? If not,you just need to take your SD card and put it in a PC. Download the latest HATSpack.zip from sthetix. Overwrite your current atmosphere folder copying from the HATS zip file. That should do it. Next time,update your atmosphere and sysmodules before the firmware update. Don't forget to uninstall any themes you might have as well.
I didnt update anything cuz its a fresh new microsd
I booted up my switch (on the stock system, not the one modded) afer a long time, noticed that there was a system update, did that, and thoughy "mh maybe i messed up something updating, let me re-mod everything"
Everything that is in the sd is "fresh" and on the latest version
Just wanted to clarify

Btw thanks for the tip i'll try literally now
EDIT
I only moved the atmosphere folder from tha hats zip to my sd's root but not much has changed
When i boot the atmosphere emuMMC the console says
failed to init or mount sd
and whenever i realod into hekate i get the same error as the original post
 
Last edited by zRicky,
I didnt update anything cuz its a fresh new microsd
I booted up my switch (on the stock system, not the one modded) afer a long time, noticed that there was a system update, did that, and thoughy "mh maybe i messed up something updating, let me re-mod everything"
Everything that is in the sd is "fresh" and on the latest version
Just wanted to clarify

Btw thanks for the tip i'll try literally now
Oh!! Ok then the problem is your fuses showing your firmware update. Try the stuff in this thread. I had a similar issue after updating my OFW and not CFW. Post #11 with the warmboot fix fixed it.
https://gbatemp.net/threads/nxboot-...iko-warmboot-firmware-ofw-doesnt-work.643522/
Post automatically merged:

I didnt update anything cuz its a fresh new microsd
I booted up my switch (on the stock system, not the one modded) afer a long time, noticed that there was a system update, did that, and thoughy "mh maybe i messed up something updating, let me re-mod everything"
Everything that is in the sd is "fresh" and on the latest version
Just wanted to clarify

Btw thanks for the tip i'll try literally now
EDIT
I only moved the atmosphere folder from tha hats zip to my sd's root but not much has changed
When i boot the atmosphere emuMMC the console says
failed to init or mount sd
and whenever i realod into hekate i get the same error as the original post
Have you tried to reseat the SD card? Could be the SD card reader is bad or wasn't reconnected if you opened the switch up. I say this because your able to read the SD card and copy HATS over to it. Things are pointing to your SD reader. Clean the SD card contacts with an eraser to polish them up and retry it.
 
Last edited by anon730,
Im not sure im following the thread, i need to edit the ini file? because i did that and tried to launch both the Warmboot and emuMMC and nothing changed; only that when i launch warmboot i just boot the stock system

Also this is my second time modding the switch but now that you mentioned it, i should have the fusee bin in my sd right? because i have no idea where is it
 
Im not sure im following the thread, i need to edit the ini file? because i did that and tried to launch both the Warmboot and emuMMC and nothing changed; only that when i launch warmboot i just boot the stock system

Also this is my second time modding the switch but now that you mentioned it, i should have the fusee bin in my sd right? because i have no idea where is it
Yeah you need to edit the hekate_ipl.ini file located in the bootloader folder. Add that set of options to the end of your file. Save it, and restart. Get back into Hekate and click on launch, and a new icon should be there now with the fix code. Select that one. It will boot into your sysmmc. Once the boot is done restart the system again and let it boot to your CFW.
 
Yeah you need to edit the hekate_ipl.ini file located in the bootloader folder. Add that set of options to the end of your file. Save it, and restart. Get back into Hekate and click on launch, and a new icon should be there now with the fix code. Select that one. It will boot into your sysmmc. Once the boot is done restart the system again and let it boot to your CFW.
nothing has changed
i boot up the warmboot, reboot into hekate, boot the emuMMC and got the same error
Post automatically merged:

UPDATE:
in a really stupid and ignorant way i replaced the atmos and bootloader folders in my sd card with the one i found on the hats zip
the sysMMC works fine and i can boot into it, same thing ofc for the stock one
the emuMMC still has that same problem

and im specifyin this because im pretty new to this world and i assume that the emuMMC is the "main" cfw becasue you can homebrew unlike the sysMMC that will likely get you banned
so the problem still persist about the emuMMC, and i have no idea on what to do
 
Last edited by zRicky,
nothing has changed
i boot up the warmboot, reboot into hekate, boot the emuMMC and got the same error
Post automatically merged:

UPDATE:
in a really stupid and ignorant way i replaced the atmos and bootloader folders in my sd card with the one i found on the hats zip
the sysMMC works fine and i can boot into it, same thing ofc for the stock one
the emuMMC still has that same problem

and im specifyin this because im pretty new to this world and i assume that the emuMMC is the "main" cfw becasue you can homebrew unlike the sysMMC that will likely get you banned
so the problem still persist about the emuMMC, and i have no idea on what to do
Have you tried to reset the Archive Bit in Hekate? You can try that. Should be under tools menu on the bottom left side of the screen. It's great your sysmmc is working. Replacing the atmosphere and bootloader folder contents was necessary. The only things you lose are the hekate_ipl.ini and exosphere.ini settings. They are both replaced with default settings which should boot just fine.
 
Have you tried to reset the Archive Bit in Hekate? You can try that. Should be under tools menu on the bottom left side of the screen. It's great your sysmmc is working. Replacing the atmosphere and bootloader folder contents was necessary. The only things you lose are the hekate_ipl.ini and exosphere.ini settings. They are both replaced with default settings which should boot just fine.
already tried the archive bit and it changed nothing, still no idea why the emuMMC is not working
Post automatically merged:

UPDATE
i just found out that my sd card its fake (my dad brought it so idk where he got it from) so im pretty sure thats the problem
 
Last edited by zRicky,
  • Like
Reactions: anon730

Site & Scene News

Popular threads in this forum