Nexus Player 5.1 LMY47D Rooted

We recently featured the Nexus Player, Google’s second attempt at a digital media … more

Should You Get Wear? Wearer’s Practical Observations

Wear is said to not offer enough for mass adoption, even though its been in … more

SlimRoms: Updates on the Horizon

SlimRoms’ website has been experiencing technical difficulties for the last month or so, but … more

Your Favorite Wireless Charger?

Wireless charging is becoming more and more common as many OEMs are now starting to include this feature … more
Post Reply Subscribe to Thread Email Thread

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

22nd August 2014, 08:53 PM   |  #11  
clsA's Avatar
Senior Member
Flag Central Florida
Thanks Meter: 1,567
 
5,700 posts
Join Date:Joined: Aug 2010
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
 
315 posts
Join Date:Joined: Aug 2009
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