[Xpost from Q&A] Can't delete, flash, wipe atrix

[boonemeat]

Its really strange that you are having the EXACT same problem as me, cannot wipe or change anything... digitizer failing along the left side (not the edge, but middle left)

I am gonna try the "dd" command, but I assume it wont work since... we have done all the same things and neither of us had any success so far.

yeh I know what you mean. My digi is failing in what sounds like the exact same spot. I try to type e and it types q and r.

 

[sjbayer3]

yeh I know what you mean. My digi is failing in what sounds like the exact same spot. I try to type e and it types q and r.

hahahahah, yep same thing. Thats hilarious.

Maybe we bought from the same batch (Southern California around march 2011)

 

[coolnow]

You guys sure it's definitely the digitizer, or a corrupted PDS partition (which makes sense considering the corrupted emmc partition)?

 

[boonemeat]

Pds fix didn't help by the way I give up and need a new phone lol.

Sent from my MB860 using Tapatalk 2

---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------

Pds fix didn't help

Sent from my MB860 using Tapatalk 2

---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------

@sbayer did you use that battery fi x app??

Sent from my MB860 using Tapatalk 2

 

[sjbayer3]

check 1
Error: File system was not cleanly unmounted!  You should run e2fsck.  Modifying an unclean file system could cause severe corruption.
Ignore/Cancel? I
I
Error: File system has an incompatible feature enabled.  Compatible features are has_journal, dir_index, filetype, sparse_super and large_file.  Use tune2fs or debugfs to remove features.
(parted)

Anyone have thoughts on this output from my partition?

 

[boonemeat]

check 1
Error: File system was not cleanly unmounted!  You should run e2fsck.  Modifying an unclean file system could cause severe corruption.
Ignore/Cancel? I
I
Error: File system has an incompatible feature enabled.  Compatible features are has_journal, dir_index, filetype, sparse_super and large_file.  Use tune2fs or debugfs to remove features.
(parted)

Anyone have thoughts on this output from my partition?

I cant even recreate this.

 

[ravilov]

I think I can make a fairly good sense of these messages, but I don't have enough context to explain what's going on. Can you explain exactly how you got here, right from the beginning?

 

[sjbayer3]

I think I can make a fairly good sense of these messages, but I don't have enough context to explain what's going on. Can you explain exactly how you got here, right from the beginning?

Yeah, i ran

C:\Users\ofsstbay>adb shell
~ # parted /dev/block/mmcblk0p16
parted /dev/block/mmcblk0p16
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p16
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p16: 2147MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2147MB  2147MB  ext3

(parted) check 1
check 1
check 1
Error: File system was not cleanly unmounted!  You should run e2fsck.  Modifying an unclean file system could cause severe corruption.
Ignore/Cancel? I
I
I
Error: File system has an incompatible feature enabled.  Compatible features are has_journal, dir_index, filetype, sparse_super and large_file.  Use tune2fs or
debugfs to remove features.

 

[ravilov]

Yeah, i ran

...

Like I said before, mmcblk0pXX devices are ALREADY partitions so you can't run partitioning software on them directly.
Try this:

parted /dev/block/mmcblk0
check 16

 

[sjbayer3]

Like I said before, mmcblk0pXX devices are ALREADY partitions so you can't run partitioning software on them directly.
Try this:

parted /dev/block/mmcblk0
check 16

C:\Users\ofsstbay>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) check 16
check 16
check 16
Error: Unable to satisfy all constraints on the partition.

In response, I understand it is a partition, but you can run commands from the partition directly. Instead of editing the partition from the mmcblk0, you go directly to partition and run the commands there.

 

[ravilov]

In response, I understand it is a partition, but you can run commands from the partition directly. Instead of editing the partition from the mmcblk0, you go directly to partition and run the commands there.

I'm not familiar enough with parted, but I do know quite a bit about partitions. If what you're saying is true, I would think your method of running the command and mine would yield the same results, right?
I can't reboot into recovery right now as I'm doing some testing, but I will as soon as I can and try to run the command myself. Will report back after that.

 

[sjbayer3]

I'm not familiar enough with parted, but I do know quite a bit about partitions. If what you're saying is true, I would think your method of running the command and mine would yield the same results, right?
I can't reboot into recovery right now as I'm doing some testing, but I will as soon as I can and try to run the command myself. Will report back after that.

I don't know enough either.

I like your method since it lets me see all the partitions, but this error is kicking my butt. I have searched over XDA and other forums and can find no solution to what this error means or how to correct it.

 

[boonemeat]

Still trying stuff on my side no fix. I was searching on google and this exact problem was listed on the atrixforums website a few days back with no luck fixing. I saw an old Defy thread with the same problem with no posted fix so I pmed the person and haven't got a response. Also I saw on the motorola support forums that someone with a photon had the same problem as well as two others. They sent them back and never heard what actually caused the problem so I have found no leads either.

 

[sjbayer3]

Yeah, I am having no luck as well... may be game over for my dear atrix

 

[coolnow]

FYI, my problems have come back. My cache, data and emmc keep on getting corrupt and cause a load of problems with any rom. Parted method works for a few of the partitions, but one will inevitably get an i/o error while reformatting which probably means wear leveler or actual internal sectors are corrupt beyond repair. Next step would be to bypass these partitions and run them from an sdcard. I'll research and post my findings.

 

[berkay28]

I have the same problem. I delete files, install files and when i reboot my phone it returns old situation. Any solutions of this problem? What should i do??

 

[sjbayer3]

FYI, my problems have come back. My cache, data and emmc keep on getting corrupt and cause a load of problems with any rom. Parted method works for a few of the partitions, but one will inevitably get an i/o error while reformatting which probably means wear leveler or actual internal sectors are corrupt beyond repair. Next step would be to bypass these partitions and run them from an sdcard. I'll research and post my findings.

Any progress... I hadn't logged in in a while. Mind explaining how you went through Parted?

 

[sjbayer3]

I have the same problem. I delete files, install files and when i reboot my phone it returns old situation. Any solutions of this problem? What should i do??

No solutions yet.

 

[sjbayer3]

So I had some positive results with EMMC and fortunately it is now functioning.

What is still not functioning is /dev/block/mmcblk0p16 (data)

If I try to format this in recovery, I get

Error Formatting /data!

going into ADB Shell:

~ # parted /dev/block/mmcblk0p16
parted /dev/block/mmcblk0p16
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p16
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print

Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p16: 2147MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2147MB  2147MB  ext3

(parted) rm 1
rm 1
rm 1
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p16: 2147MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  2147MB  2147MB  ext3

(parted)

This means that I am unable to remove the partition. Which is strange because I was able to for /dev/block/mmcblk0p18 (EMMC) and this fixed my problems there.

Now if I try using e2fsck I get this short read error:

~ # e2fsck /dev/block/mmcblk0p16
e2fsck /dev/block/mmcblk0p16
e2fsck 1.41.11 (14-Mar-2010)
Error reading block 271896 (Attempt to read block from filesystem resulted in short read).  Ignore error<y>? II
yes

Force rewrite<y>? y
y
yes

/dev/block/mmcblk0p16: recovering journal
Error reading block 271896 (Attempt to read block from filesystem resulted in sh
ort read).  Ignore error<y>? yes

Force rewrite<y>? y
y
yes

e2fsck: unable to set superblock flags on /dev/block/mmcblk0p16

So I get three errors: 2 of which are short read erros, and the final is an unable to set superblock flags.

I have no idea what to do here... so I anyone has any hint at all...


Edit:

One additional issue I have had since step 1, this "unable to satisfy all constraints" problem...

parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Unable to satisfy all constraints on the partition.

 

[Avrojet111]

I just wanted to state that I have the same problem on my Atrix (european model). I am running mrom.

My atrix simply cannot write to the internal memory anymore. I can't delete files, I can't flash a ROM, installting a new sbf with rsd lite does not do anything, formatting with CWM does nothing. Every time I reboot the phone it resets its status to that of a certain date. Nothing since the last reboot is saved (call log, SMS, internal photos, apps, etc).

So, a few of us are unlucky enough to have this problem which apparently cannot be fixed?