FORUMS

Mysterious GG1 Google Device Stops by FCC. Glass v2?

As the year progresses, we draw further away from Google’s annual I/O … more

Material and Material Dark Hit Samsung’s Theme Store

The latest version of Touchwiz, launched alongside the Galaxy S6 and S6 Edge, … more

Swappa’s New App Helps You Value Your Device

There comes a sad time in everyone’s life where you must part ways with your … more

Xiaomi Sold 34.7 Million Phones In 6 Months

2015 has been a phenomenal year for Xiaomi so far. With a stellar rise in 2014, 2015 saw … more

[Q] How do I edit/restore the mmcblk0 partition.

316 posts
Thanks Meter: 43
 
By davidrol, Senior Member on 20th August 2014, 11:30 PM
Post Reply Subscribe to Thread Email Thread
22nd August 2014, 08:53 PM |#11  
clsA's Avatar
Senior Member
Flag Central Florida
Thanks Meter: 1,811
 
Donate to Me
More
Have to agree with nkk71 here. You have a normal AT&T phone, it should be easy to RUU back to stock from your current settings.

relock bootloader
fastboot oem lock
Run the 3.17.502.3 RUU and you should be all set
 
 
23rd August 2014, 04:37 AM |#12  
OP Senior Member
Flag Brooksville, FL
Thanks Meter: 43
 
More
Installing an RUU didn't solve restoring all partitions, only a small portion. The upper (1-5) is where the overlap occurred and RUU's dont' effect those partitions, at all. I deleted mmcblk0p4, because it was way too large and should be 1MB. After, a few restarts and 3 attempts at gaining s-off with firewater, the phone now functions correctly! I have tested and confirm a working GPS, phone radio recognizing sim, google sync, etc, etc. The imei and broadband version show correctly in phone info. I cant explain or fully understand why it's fully working. I will examine the partitions again and post the results.

BTW, I haven't tried installing a sense rom (current Android Revolution) to check for the constant boot loops I was getting.

Next step would be to sim unlock and test phone reception and signal strength.

I thank you all for your assistance.
23rd August 2014, 11:20 AM |#13  
Quote:
Originally Posted by davidrol

Installing an RUU didn't solve restoring all partitions, only a small portion. The upper (1-5) is where the overlap occurred and RUU's dont' effect those partitions, at all. I deleted mmcblk0p4, because it was way too large and should be 1MB. After, a few restarts and 3 attempts at gaining s-off with firewater, the phone now functions correctly! I have tested and confirm a working GPS, phone radio recognizing sim, google sync, etc, etc. The imei and broadband version show correctly in phone info. I cant explain or fully understand why it's fully working. I will examine the partitions again and post the results.

BTW, I haven't tried installing a sense rom (current Android Revolution) to check for the constant boot loops I was getting.

Next step would be to sim unlock and test phone reception and signal strength.

I thank you all for your assistance.

hmm, interesting, I've never seen that done before, but just for info:
fdisk -ul
Code:
...
/dev/block/mmcblk0p4 262111 61071358 30404624 5 Extended
...
the rest are exactly like the ones you posted earlier.

but if you actually "dd" the partition, you'll get a 1KB (not MB) file, which starting ot offset 0x200 (ie 1 block) shows the HTC-BOARD-INFO from p5

so seems p4 is only 1 block plus some kind of container for the rest of the partitions.


Anyway, very glad that worked out for

PS: and you were able to change the partition layout with S-ON.... didn't / don't think that's possible
Post Reply Subscribe to Thread

Tags
mmcblk0, overlapping partitions, superblock invalid
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes