Hello Everyone!

[Blue]

Hi Everyone! I'm Blue, and I'm glad to be here

I have an Incredible, rooted (and I have issues )... I appear to have repartitioned my internal memory area. Thankfully, the phone is useable, but it's not quite right including either corrupt data or areas stomped on by other areas due to incorrect partition information. If certain files get touched, then the phone immediately protects itself by flagging the internal memory as read only.

I've been searching for a loonngg while to find somewhere someone has info on how to fix the Internal SD partition information, but have yet to find anything. Reflashing ROM, "factory reset", etc. appear to just repopulate the already partitioned areas. If anyone can point me in the right direction to properly repartition the *internal* areas, I'd really appreciate the help!

Thanks,
Blue

[Ads]

[jpr]

Just what tells you that your "internal memory area" has been repartioned?

[Blue]

Mostly strong hunch. This happened while using a Partitioning tool (specifically Acronis, making a "secure zone") on my PC while my incredible was charging in the USB port and I accidentally used the wrong drive. It was one of those "oh crap" moments.

parted also reports that there are problems:

~ # parted /dev/block/mmcblk0p3
parted /dev/block/mmcblk0p3
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p3
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p3: 7088MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End     Size    Type      File system  Flags
 2      123MB  7082MB  6959MB  extended               boot
 5      123MB  7074MB  6950MB  logical   fat32

(parted) check 2
check 2
check 2
Warning: Partition 5 is 6950MB, but the file system is 6959MB.
Ignore/Cancel? I
I
I
Error: Could not detect file system.

(parted) check 5
check 5
check 5
Warning: Partition 5 is 6950MB, but the file system is 6959MB.
Ignore/Cancel? I
I
I
Error: The file system is bigger than its volume!
Ignore/Cancel? I
I
I
Warning: File system is reporting the free space as 1695549 clusters, not
1695559 clusters.
Ignore/Cancel? I

In addition, now when connecting to PC, the internal drive comes up as being unformatted and windows asks if I want to format. Another disk utility (EASEUS) sees the drive, and I can explore within to see that the files exist.

[doug piston]

Challenge to members... Help me fix internal partitions without recovery.

Look there

[Blue]

Challenge to members... Help me fix internal partitions without recovery.

Look there

Hi Doug,

Thanks for the link. I actually tried that exact procedure last week to no avail. Thinking perhaps I had an old stock PB31IMG.zip, I downloaded the latest and greatest from your site (thanks very much, btw) and repeated the procedure tonight. Same thing. The overall process went fine, but the /mnt/emmc area was untouched by the repartitioning/formatting & flashing.

One of the corrupt areas is the "factory installed" music, specifically the "/mnt/emmc/MP3/People Under The Stairs" directory. There's a bunch of garbled file names within (or incorrect file pointers because perhaps the partitions overlap?). Before I reflashed, I had used Root File Manager to remount the / and /emmc areas as R/W, then renamed the directory to just "People". Trying to delete the files causes the phone to immediately remount the Internal SD as Read Only. After I redid the procedure in the above link, the directory is still called "People" and the garbled files are still within. So, it appears that when reflashing stock PB31IMG.zip, the emmc area remains untouched

Does the RUU repair/repartition/reformat/replace the emmc areas?

Is there a resource that might show what all of the partitions listed in /etc/fstab and /etc/recovery.fstab should look like for the Incredible?

Not entirely sure where to go from here...

Thanks again,
Blue

[doug piston]

RUU does not touch the emmc, Thus the above method beinbg needed. Otherwise flashing a RUU would fix people with this issue. I wish it did though. I think I have a list of the partitions, let me look.

[Blue]

Thanks! I look forward to seeing the partition sizing info. Maybe I can find the differences between the correct/non-corrupted device and mine, then reset/re-size the blocks back to normal with parted...

EDIT: I attached a couple of txt files that show parted information for the mounts listed in recovery.fstab and fstab. Both were done in an ADB Shell while the phone was booted into Recovery. If someone would please take a look and/or duplicate the exercise with a known good Incredible and let me know their results, I'd really appreciate it.

Thanks again,
Blue