yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] enel_:
Sorry sorry, my mistake, here it is:

~ # cat /proc/emmc

cat /proc/emmc

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p33: 01000000 00000200 "boot"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: 680000000 00000200 "userdata"

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p31: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yep, missing spaces is no good, let's go ahead and check the partitions:

~# umount /data

~# e2fsck -n -v -f /dev/block/mmcblk0p35

~# e2fsck -n -v -f /dev/block/mmcblk0p36

~# e2fsck -n -v -f /dev/block/mmcblk0p37

just report back, nothing else ;)
[One (M7) Q&A, Help & Troubleshooting] enel_:
First:

~ # e2fsck -n -v -f /dev/block/mmcblk0p35

e2fsck -n -v -f /dev/block/mmcblk0p35

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

/lost+found not found. Create? no

Pass 4: Checking reference counts

Pass 5: Checking group summary information

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

*

2632 inodes used (2.29%)

122 non-contiguous files (4.6%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 2538/12

442710 blocks used (96.50%)

0 bad blocks

0 large files

2470 regular files

80 directories

0 character device files

0 block device files

0 fifos

0 links

73 symbolic links (73 fast symbolic links)

0 sockets

--------

2623 files

~ #
[One (M7) Q&A, Help & Troubleshooting] enel_:
Second:

~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p

36

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.

[MENTION=2459038]xavier_largeaux[/MENTION], how is he going to run a downgrade with S-On??

[MENTION=1989366]enel_[/MENTION] I'll post back in a few minutes.....
[One (M7) Q&A, Help & Troubleshooting] enel_:
Oh God, I hoped not to hear this... No problem man, I'm going to wait for your instructions. And thank you for helping me out.
[One (M7) Q&A, Help & Troubleshooting] enel_:
Bad news, my phone was connected to my laptop, in cwm, suddenly it rebooted, rebooted twice, and booted back to my homescreen. And at my homescreen it rebooted again...

So I think we are again in the reboot horror story and it's going to reboot itself when he wants...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Download this: http://goo.gl/pmZ9Mt (credit to [MENTION=1631739]mike1986.[/MENTION] for his excellent article: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)

now open a new command prompt (but leave the shell one open as well, we're going back to that in a minute), and push the downloaded file:

adb push mkfs.ext4 /tmp

now go back to the shell and type:

~# chmod 777 /tmp/mkfs.ext4

and then format the data partition, we're going to leave /system (doesnt look bad) and /cache (

looks bad

:() for later, if we need to:

~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]

Once it formats successfully:

~# mount /data

~# mkdir -p /data/media/0

NOTE: THE ABOVE PROCEDURE WILL COMPLETELY WIPE ALL DATA INCLUDING INTERNAL STORAGE

your phone is going to be completely empty, so you will have to push your rom to your phone, so exit the shell "~# exit" and

adb push <name of rom>.zip /data/media/ <- this will take 5 to 15 minutes depending on the ROM and should come back with success

then in recovery select "install zip" -> "choose zip" -> select the ROM, and go through the installer (hopefully with Success) and reboot.

post back when done, and what's happening

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

OK, just saw that, you'll probably have to format /cache as well

Can you get back to recovery? (if need be, do the fastboot commands from before again)

EDIT: i'll be back in 10 minutes
[One (M7) Q&A, Help & Troubleshooting] enel_:
We are again in the same horror story as before. I can't boot my phone, as far as I can see I'm going to need like 50 attempts to boot it once.

If I should boot it, can I flash again the boot.img? Flashing it today gave as this time window when my phone was stable?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
we are now at over 70% chance that it is a hardware problem, I'm sorry to say, even if you flash boot.img or whatever, you're phone may be stable for 10 minutes or 10 seconds.

In my humble opinion:

fastboot erase cache

fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img

fastboot erase cache

fastboot reboot-bootloader

-> enter RECOVERY

adb push mkfs.ext4 /tmp

adb shell

~# chmod 777 /tmp/mkfs.ext4

~# umount /data

~# umount /cache

--> nevermind if it gives an error, then

~#[B] /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p36[/B]

~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]

/system didnt look to bad so we'll not format it.

then

~# mount /data

~# mkdir -p /data/media/0

~# exit

adb push <name of rom>.zip /data/media/

and try installing it.

Good luck, hope for the best, and post back
[One (M7) Q&A, Help & Troubleshooting] enel_:
Thank you very much nkk71, I'm just fu*king sad about this.

I'm going to do all your steps once I've booted into recovery and I hope this will solve my problem.

Just one more question, is unlocking my bootloader the reason for all this?

Or is it flashing TWRP? Or something else...?
[One (M7) Q&A, Help & Troubleshooting] r.ciesla:
The Link what I posted earlier is Signed RUU for HTC One Europe HTC__001 PN071000 There will be a signature check and it will reflash entire all partitions but bootloader must be locked otherwise it will fail on first stage. This is only 1 solution what I can think of if the partition table is corrupted and some blocks are not allocated properly. I'm just trying to help :(
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Unlocking -> NO

Flashing anything -> NO

TWRP -> highly unlikely (though the two cases I was able to

successfully

help, had a version of TWRP installed, so there could have been something in one of the versions), but again

HIGHLY

unlikely, those devs are great and test their stuff to the limit.

if the "real format" doesnt work, then it's a hardware fault. not because you flashed anything!

I'm checking something with mike, and when he get's back to me, if the info has changed I'll let you know. try the steps and post back. wish you best of luck

---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------

Salut Xavier, I wasn't trying to be disrespectful or anything really!! Sorry if I offended you, I apologize, and I know you are trying to help :good:

But even with a signed RUU, it will fail because it's an older version than the one on his phone. the only way to downgrade is if you have S-Off.
[One (M7) Q&A, Help & Troubleshooting] enel_:
I was able to boot into recovery and I did all steps to

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37

In the middle of this step my phone rebooted. When I boot again into recovery, should I countinue from this step?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hold, were you able to format partition mmcblk0p36 properly?? copy/paste please
[One (M7) Q&A, Help & Troubleshooting] enel_:
Here is a copy of cmd:

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb push mkfs.ext

4 /tmp

3398 KB/s (3537143 bytes in 1.016s)

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell

~ # chmod 777 /tmp/mkfs.ext4

chmod 777 /tmp/mkfs.ext4

~ # umount /data

umount /data

~ # umount /cache

umount /cache

umount: can't umount /cache: Invalid argument

~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p36

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p36

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

40960 inodes, 163839 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

5 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304

Writing inode tables: done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p37

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p37

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

1703936 inodes, 6815744 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

208 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000

Writing inode tables: 171/208

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ok both formats look successfull, now run e2fsck to confirm to more errors:

~# e2fsck -n -v -f /dev/block/mmcblk0p36

~# e2fsck -n -v -f /dev/block/mmcblk0p37

if it says "in use", then ~# umount /cache and/or ~# umount /data and run again
[One (M7) Q&A, Help & Troubleshooting] enel_:
My problem now again is that I can't boot my phone to fastboot, I'm holding power+down for about 20 sek 10 times now, but nothing. When my phone rebooted, it booted back to my rom, and because there was nothing it stayed on the htc logo screen so I held the power button, the back key and home key started to blink and it turned off. After that I can't boot to faastboot.

Should I again copy/paste when I type in these two commands?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Once your phone is off or rebooting, let go of the power button, just keep holding voldown!!
[One (M7) Q&A, Help & Troubleshooting] enel_:
~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p

36

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

~ #

~ # e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

1425 inodes used (0.08%)

167 non-contiguous files (11.7%)

1 non-contiguous directory (0.1%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 1136/1

155912 blocks used (2.29%)

0 bad blocks

1 large file

463 regular files

673 directories

0 character device files

0 block device files

0 fifos

0 links

278 symbolic links (278 fast symbolic links)

2 sockets

--------

1416 files

~ #
[One (M7) Q&A, Help & Troubleshooting] enel_:
Here are the two commands what should I do next?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
OK, data partition is now good but /cache is still messed up, do it again:

~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p36[/B]

then exit the shell ~# exit

adb reboot recovery

and run the e2fsck again on mmcblk0p36
[One (M7) Q&A, Help & Troubleshooting] enel_:
This is what I got:

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext

ra_isize -m 0 /dev/block/mmcblk0p36

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

40960 inodes, 163839 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

5 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304

Writing inode tables: done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 24 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # exit

exit

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb reboot recove

ry

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell

~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p36

Filesystem mounted or opened exclusively by another program?

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ok good! now ~# umount /cache and run the e2fsck
[One (M7) Q&A, Help & Troubleshooting] enel_:
Here it is:

~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

14 inodes used (0.03%)

0 non-contiguous files (0.0%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 4

6682 blocks used (4.08%)

0 bad blocks

0 large files

2 regular files

3 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

--------

5 files

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
WOW WOW, hold on, and let's BOTH of us calm down (especially me)..... next post coming shortly :)
[One (M7) Q&A, Help & Troubleshooting] enel_:
Please tell me that this is something good :fingers-crossed:?

The one good thing I can see is 0 bad blocks, the rest, I don't understand it :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes it's good, i need 5 minutes and will be back, just leave everyhting the way it is, no messing around now !! and keep your fingers crossed !!
[One (M7) Q&A, Help & Troubleshooting] enel_:
You can have all the time you want, I'll be waiting. No no, my phone is in cwm, connected to my laptop, I'm not going to touch anything.

:fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I'll be back.... (Arnold) LOL

gimme 30 minutes....
[One (M7) Q&A, Help & Troubleshooting] enel_:
LOL!

No problem, I'll be here.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
ok, i'm back, are you still in the shell? if so "~# exit"

now "adb reboot recovery" and let's check again, to make sure everything held through reboot (KEEP YOUR FINGERS CROSSED):

adb shell

~# umount /data

~# umount /system

~# umount /cache

--> nevermind if something gives an error, it would just mean it's not mounted

~# e2fsck -n -v -f /dev/block/mmcblk0p35

~# e2fsck -n -v -f /dev/block/mmcblk0p36

~# e2fsck -n -v -f /dev/block/mmcblk0p37

post back, minor error OK, major ones NOT OK. so go for it and HOPE/WISH all good.... waiting for your feedback before I start signing off....
[One (M7) Q&A, Help & Troubleshooting] enel_:
Second:

~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

14 inodes used (0.03%)

1 non-contiguous file (7.1%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 4

6683 blocks used (4.08%)

0 bad blocks

0 large files

2 regular files

3 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

--------

5 files

~ #
[One (M7) Q&A, Help & Troubleshooting] enel_:
Third:

~ # e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

1425 inodes used (0.08%)

167 non-contiguous files (11.7%)

1 non-contiguous directory (0.1%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 1136/1

155912 blocks used (2.29%)

0 bad blocks

1 large file

463 regular files

673 directories

0 character device files

0 block device files

0 fifos

0 links

278 symbolic links (278 fast symbolic links)

2 sockets

--------

1416 files

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
so far so good, have you recreated media? (sorry lost track), open a shell

adb shell

~# mount /data

~# mkdir -p /data/media/0

~# exit

then push the rom.zip to your phone

adb push <name of rom>.zip /data/media/ <- yes it will take 5 to 10 minutes, and should report success

then in recovery "install zip" -> "choose zip" -> select the rom.zip and INSTALL (in installer choose WIPE)
[One (M7) Q&A, Help & Troubleshooting] enel_:
No I haven't. But before I do that, I got this ROM from mike: One_3.62.401.1_odexed, can I flash it?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, once you recreate /data/media you can flash anything you like !! keep your fingers crossed anyway, and hope the format was successful, and not a hardware problem!!
[One (M7) Q&A, Help & Troubleshooting] enel_:
This looks bad...

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell

~ # mount /data

mount /data

~ # mkdir -p /data/media/0

mkdir -p /data/media/0

~ # exit

exit

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb push One_3.62

.401.1_odexed.zip /data/media/

protocol failure

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>
[One (M7) Q&A, Help & Troubleshooting] nkk71:
push another rom, cant remember what "protocol failure" was about but i don't think it was about bad partitions (i could be wrong, it's getting late), I'll wait for your first flash....
[One (M7) Q&A, Help & Troubleshooting] enel_:
But is it normal, when I got the message protocol failure my phone rebooted into HTC logo?

At that point I turned it off. I don't have another ROM, I'm now downloading the latest android revolution. It will take about 30 min. If you can't wait, please just tell me should I use the same steps again:

adb shell

~# mount /data

~# mkdir -p /data/media/0

~# exit

then push the rom.zip to your phone

adb push <name of rom>.zip /data/media/ <- yes it will take 5 to 10 minutes, and should report success

then in recovery "install zip" -> "choose zip" -> select the rom.zip and INSTALL (in installer choose WIPE)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you might wanna go back to recovery, open the shell again and umount /data, umount /cache, umount /system and run the e2fsck command again

the "lost & found" is not a problem, if however it gives you another superblock fault, then THAT IS A PROBLEM, try it, I'll wait for the your last e2fsck post before signing off....
[One (M7) Q&A, Help & Troubleshooting] enel_:
All of them?

~# e2fsck -n -v -f /dev/block/mmcblk0p35

~# e2fsck -n -v -f /dev/block/mmcblk0p36

~# e2fsck -n -v -f /dev/block/mmcblk0p37

****... My phone was in recovery, connected to my laptop and it rebooted itself again...

I'm going to do what you have told me with the e2fsck.
[One (M7) Q&A, Help & Troubleshooting] enel_:
Second:

~ # e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

15 inodes used (0.04%)

0 non-contiguous files (0.0%)

0 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 5

6683 blocks used (4.08%)

0 bad blocks

0 large files

2 regular files

4 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

--------

6 files

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
"****... My phone was in recovery, connected to my laptop and it rebooted itself again..." doesn't look good :( :crying: :mad::mad::mad:

I'll wait 3 more minutes, and after that I'll check in on you tomorrow; if it's just mmcblk0p36, maybe we can format it differently, but I'll have to do some major checking on that!!! (hopefully [MENTION=1631739]mike1986.[/MENTION] will help out).
[One (M7) Q&A, Help & Troubleshooting] enel_:
After 5 reboots, the third:

~ # e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck -n -v -f /dev/block/mmcblk0p37

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

1454 inodes used (0.09%)

173 non-contiguous files (11.9%)

1 non-contiguous directory (0.1%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 1165/1

181868 blocks used (2.67%)

0 bad blocks

1 large file

484 regular files

681 directories

0 character device files

0 block device files

0 fifos

0 links

278 symbolic links (278 fast symbolic links)

2 sockets

--------

1445 files

~ #
[One (M7) Q&A, Help & Troubleshooting] enel_:
Before pushing the ROM, it was stable, but after that failure, it's again unstable :crying:

No problem nkk71, if you find something new, just send me a private message or write here in the thread.

I'm so sorry for wasting your time and night :(

Thank you for everything!