Hardware Corrupted SD Partition Table after Hekate Upgrade.

  • Thread starter Thread starter H0ppus
  • Start date Start date
  • Views Views 1,705
  • Replies Replies 0

H0ppus

Member
Newcomer
Joined
Dec 16, 2014
Messages
22
Reaction score
6
Trophies
0
Location
Santa Bárbara Do Oeste, Sao Paulo, Brazil
XP
218
Country
Brazil
Hi everyone,

I have recently decided to update my Nintendo switch emuMMC and sysMMC. My setup consists of :
  1. emuMMC running in a 400GB SD, currently on firmware 10.x.x ( not sure the exact version ) ;
  2. sysMMC running in the switch NAND on version 9.x.x ( Not sure the version now ).
I now know that the order I have decided to start the upgrade was wrong, but the idea was to update the sysMMC to the latest for online play and emuMMC to the latest recommended.

I started updating the stock firmware and following the safeguards to avoid the fuses burning. That is when the console restarts the JIG was inserted and the volume + was pressed to put the console instantly in RCM mode avoiding the fuses to burn since I had auto RCM enabled and the stock firmware disables it.


I have injected the payload and launched emuMMC from the menu, but I got the following error :

Code:
A fatal error occurred when running Atmosphere.
Program ID: 010000000000bd00
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_000000000c0024e6.bin
Press POWER to reboot

After a google search it seems that the issue was a sysmodule ( https://github.com/ndeadly/MissionControl/issues/76 ).

I have decided to rename the folder `010000000000bd00` and in my mind disable the module. But after renaming it and trying to boot the emuMMC the Atmosphere failed with a different error ( I do not remember now ) and I tried again, but this time it was like there was no SD inserted.

I poped my SD back into my OS and it is not being recognised anymore. It seems that the partition table got corrupted as seen on the images below ( attached ) :

lsblk.jpeg


fdisk.jpeg


mount-attempt.jpeg


Has anyone already experienced the same issue and how got it fixed ?

Many Thanks. :D
 

Site & Scene News

Popular threads in this forum