Hacking V1 switch emunand 11.0

  • Thread starter Thread starter linkref
  • Start date Start date
  • Views Views 3,107
  • Replies Replies 5

linkref

Well-Known Member
Member
Joined
Apr 14, 2019
Messages
195
Reaction score
19
Trophies
0
Age
46
XP
800
Country
France
Hello,

I have V1 switch with sxos.
I've updated to 11.0, but my emunand is 9.0.

Now when I try to boot to emunand I have an error screen saying that sx os needs to restart.

Is it normal? I just need to wait an update?
Or something I can do?
 
I was reading in the official forum that they said there is no issues with updating to 11.0 for RCM users, including no issue with emunand. I guess they missed disclosing this critical issue.

So is this GC update have a workaround?
 
I was reading in the official forum that they said there is no issues with updating to 11.0 for RCM users, including no issue with emunand. I guess they missed disclosing this critical issue.

So is this GC update have a workaround?
You either prevent the update by breaking the cartridge slot with nogc or update both emuMMC and sysMMC to the same firmware.
 
You either prevent the update by breaking the cartridge slot with nogc or update both emuMMC and sysMMC to the same firmware.
Is there something special in the update routine for emuMMC if there is no game cart in the slot, not to update it? Or is it a bug with the update itself? I mean, if the average person does a system update from OFW with no cartridge in the slot, does it update the cartridge slot?

Just curious.
 
Is there something special in the update routine for emuMMC if there is no game cart in the slot, not to update it? Or is it a bug with the update itself? I mean, if the average person does a system update from OFW with no cartridge in the slot, does it update the cartridge slot?

Just curious.
No the issue is that your emuMMC hasn't received the cartridge slot update yet therefore it is unable to load any cartridges. The only fix is to keep emuMMC and sysMMC on the same cartridge slot firmware which you accomplish by either preventing or installing the update on both. Having it applied on only one breaks it for the other.
 

Site & Scene News

Popular threads in this forum