"bricked" my eMMC
05-09-2023, 09:05 AM
(This post was last modified: 05-09-2023, 10:54 AM by tigerbalm69.
Edit Reason: I cleared eMMC and wiped tow-boot, enabling auto-load from SD. This resolves the issue as it no longer tries to load invalid data
)
(05-09-2023, 07:22 AM)mikehenson Wrote: Try using a computer to flash the eMMC.Thanks a lot for the help!
I documented the whole process here:
https://www.youtube.com/watch?v=FBGVUq3DGK4
I didn't find anything about volume+ key for accessing eMMC in the documentation that I'd viewed. 5 minutes into the first video I already had all I needed to fix my entire problem.
I had a feeling tow-boot was still in working condition and it was just the OS causing issue. and I'm glad I got a response so fast.
I now still get the message I thought I could circumvent by re-flashing.
Quote:The filesystem according to the superblock is 3764531 blocks
The ophysical size of the device is 1515187 blocks
Either the superblock or the partition table is likely to be corrupt
I ran
Code:
sudo dd if=input.img of=/dev/mmcblk2 bs=1M status=progress conv=fsyncThe .img flashed to system was the original from manjaro and previously was running on SD card (STILL runs actually) since the crash it has always been like this