[Android Q&A, Help & Troubleshooting] ghirux:
Hi everybody,

I'm in deep troubles with my nexus (maguro).

Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.

the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.

twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.

And then the weird part begins:

it's like every partition is read only, but from the mount command it doesn't look like it.

flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.

factory reset successful, and everything is like before.

wiping sdcard, nothing happens.

if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).

Try to fix or to change the partitions filesystem in twrp doesn't change anything.

I tried also to change the file system in parted, through the adb shell,this happens:

~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?

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.

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

...

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

...

for further information.

Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Error: SEGV_MAPERR (Address not mapped to object)
Aborted

and of course nothing changes.

so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?

If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.

this is my mount result:

~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)

and remounting in rw the partitions has no effect.

Even the parted, e2fsck, etc files disappear from /sbin after each reboot.

thank you

edit:

Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.

I'm looking for a procedure to make them "ordered" as the other phone.

edit2:

/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12

/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*

/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.

Stuck here at the moment, cannot set superblock flags..

edit3:

Tested every possible superblock position, no luck.

I'm starting to think that the internal memory could be dead.

I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.