yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] pavo122:
I get this

C:\adb>adb shell
~ # umount /data
umount /data
umount: can't umount /data: Invalid argument
~ # umount /system
umount /system
umount: can't umount /system: Invalid argument
~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # e2fsch

Dont know what is e2fsck :(
[One (M7) Q&A, Help & Troubleshooting] nkk71:
~# e2fsck -n -v -f /dev/block/mmcblk0p35

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

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

those are not changing anything on your filesystem because of the "-n" parameter
[One (M7) Q&A, Help & Troubleshooting] pavo122:
~ # 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
Pass 4: Checking reference counts
Pass 5: Checking group summary information

1802 inodes used (1.52%)
12 non-contiguous files (0.7%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1500
161348 blocks used (33.96%)
0 bad blocks
0 large files

1436 regular files
63 directories
0 character device files
0 block device files
0 fifos
0 links
294 symbolic links (294 fast symbolic links)
0 sockets
--------
1793 files
~ # 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)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?

I dont get the "-n" parameter, im a noob :(

Do you still need the ~# umount /data

~# umount /system

~# umount /cache

Cause i dont get the "-n" parameter, sorry :confused:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
mmcblk0p37 = /date -> is still mounted, you need to:

~# umount /data

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

and check if it's OK, if it is you can go ahead and mount it again:

~# mount /data

then adb push or sideload your rom.zip
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Nice.. if this works, then this is a good shortcut nkk71, if there is a corresponding stock recovery available. Rather than the e2fsck commands?
[One (M7) Q&A, Help & Troubleshooting] chivamex10:
HELP

I figure I would post in this thread instead of making a new one.

I tried to flash Android Revolution HD 5.1 last night. Didn't realize I needed S-OFF. Now my HTC One is stuck in a loop. Worst part is I can't get my PC to recognize the device anymore. I am running windows 8.1

Here is my error message

I tried manually re-installing the drivers

I get a message saying it is not compatible.

I made sure to" Disable driver signature enforcement"

Am I damaged goods? I don't know what else I can do. I even tried using adb on my mac:crying:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
let's hope so :)

though AFAIK, factory reset in bootloader or recovery, only wipes, the partition, doesn't do a real format. so it really depends on how corrupted the filesystem is.

but so far no random reboots, which do suggest a good chance that the wipe worked.

i'm just trying to be on the safe side with fsck, otherwise it's gonna go another xx pages while trying to push or sideload a rom.
[One (M7) Q&A, Help & Troubleshooting] pavo122:
DUDE I LOVE YOU!, Thanks a milion! :highfive: :good::good::good:

You've helped so much, shoud have asked imediately on the forum, not try to fix it myself (that was a stupid idea LOL)

Kinda sad i lost everything on my sdcard :(

Can't thank you enough man!
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Make a NEW thread.

---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------

That's great. Saved you running those crazy commands! :)
[One (M7) Q&A, Help & Troubleshooting] pavo122:
Acually I did the exact same thing :eek:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
All good then? up and running?

And you'll have to thank [MENTION=3525160]SaHiLzZ[/MENTION] too, he suggested the factory reset from within stock recovery.

if all good, would you mind editing the main thread title to include [SOLVED]. thanks
[One (M7) Q&A, Help & Troubleshooting] pavo122:
All running well!

Thanks to SaHiLzZ too,of course!

Ok, ill change it.
[One (M7) Q&A, Help & Troubleshooting] mctodd:
Yeah just saw it.. Its quite a work you have done there! Its so nice to have someone in this page who's patiently spending hours just to Help.. :good::good::good:;)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
thank you :laugh: try my best
[One (M7) Q&A, Help & Troubleshooting] mctodd:
Told yah.. I've said that too.. LMFAO....:D:laugh::laugh::laugh:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
then you're really gonna love this guy: http://xdaforums.com/showpost.php?p=45904336&postcount=19 LOL

hope my wife doesn't get to read these comments :rolleyes:

but then again, she was happy, i took up a new hobby i enjoyed :o
[One (M7) Q&A, Help & Troubleshooting] mctodd:
Lol.. She would be more happy if she found out you made people happy!! Except stealing her time.. :D:D

---------- Post added at 12:30 AM ---------- Previous post was at 12:29 AM ----------

You mean you didnt study for this things?? :eek:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
family and work come first, but when i have time, i like helping out here. a lot of the times she's actually sitting right next to me and we chat even while i'm typing. don't you just love the guys who invented multitasking ;)
[One (M7) Q&A, Help & Troubleshooting] mctodd:
Good for you man.. :good::good::good:

By the way i saw the comment you linked, from "zapp02" I think thats is more dangerous to you if your wife will see it.. hahaha
[One (M7) Q&A, Help & Troubleshooting] pavo122:
Dude, you're awesome! Keep it up!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Thanks man, good to hear that!!!

many times I feel appreciatied, and many (many) times it feels like people just come in, get their issue solved, and are gone... Just like the most of the xda community, I don't ask for payment of any kind (even when they offer), a simple hit of the thanks button, if I actually helped, is thanks, enough.

But some don't even feel that pressing that little button is too difficult.

Thanks again man, for your kind words.
[One (M7) Q&A, Help & Troubleshooting] pavo122:
Good people like you make me try to help other people, not necessarily in xda forums beacuse it seems that I suck with more advanced problems on my phone.

Well now that I think of it, I acually learned alot from bricking my phone and you helping me unbrick it. I will certanly stay on the forum and maybe even help someone when I get more good at adb,fastboot,rooting and other similar stuff. Also I want to say that I thanked almost every post from you, but i have the 8 thanks per day limit. :eek:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That's a better way of saying it, so thanks to you !!!

Life is not about bricked phones, it's about a community, we're all helping each other out here (no why's, no why should I, etc.) I wish the rest of the world would take xda as an example.

Imho
[One (M7) Q&A, Help & Troubleshooting] pavo122:
It's hard to see a person willing to have patience and nerves to help some beginner with his problem. Maybe xda forums will start a new way of life, everybody helping each other, that would be cool!

And now because of you I can send this message proudly from my unbricked One! :D
[One (M7) Q&A, Help & Troubleshooting] whowhatwhen:
Hi,I really need some help, I've stuffed my phone up big time, originally I was trying to put a different ROM on to the one I had, I've tried so many different things, now it just sits at the white HTC logo screen. I can still boot into HBOOT or Recovery.I have TWRP v2.6.33 installed.

I've tried installing executable RUU's which all fail, I've also tried pushing over other ZIP files which all fail.

Can anyone point me in the right direction to resolve this issue? I've spent nearly 20 hours trying all these different options.

I do have backups from when it was working, with files like system.ext4.win and data.ext4.win.

On my main bootloader screen it shows:

Tampered

Unlocked

M7_UL PVT SHIP S-ON RH

HBOOT-1.44.0000

RADIO-4A.14.3250.13

OpenDSP-v2.6.120.274.8202

eMMc-boot

Mar 11 2013

C:\HTC\HTC One>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.841.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT3xxxxxxxx

(bootloader) imei: 35xxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: TELST001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4286mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.048s

Any help will be greatly appreciated. :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
If you just need to get a rom.zip onto your phone, you can use one of three methods:

1- OTG cable

2- adb push, as in "adb push <name of rom>.zip /data/media/"

3- adb sideload, as in: http://xdaforums.com/showthread.php?t=2317986

and install from within TWRP.

just to mention: you're still on hboot 1.44 and can get s-off with revone, you'll need a 4.1.2 ROM, if you do want to s-off and need a rom, send me a PM and I'll send you one that works just fine with revone.
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Hi nkk71,

I'll continue my post here. anyway, I continued on what you told me to do with these commands:

here's the responses I got:

~ # ←[6nunmount /data

unmount /data

/sbin/sh: unmount: not found

~ # ←[6nunmount /sdcard

unmount /sdcard

/sbin/sh: unmount: not found

~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37

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

e2fsck 1.41.14 (22-Dec-2010)

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

Filesystem mounted or opened exclusively by another program?

~ # ←[6n
[One (M7) Q&A, Help & Troubleshooting] nkk71:
it umount (without the N)

umount /data

umount /sdcard

e2fsck -n -v -f /dev/block/mmcblk0p37
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh okay. I didn't notice it should be umount without the N haha. anyways, here is the result:

~ # ←[6numount /data

umount /data

umount: can't umount /data: Invalid argument

~ # ←[6numount /sdcard

umount /sdcard

~ # ←[6ne2fsck -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

/lost+found not found. Create? no

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Block bitmap differences: +(111128--111135) +(925723--925724) +(942104--942111)

+(945688--945695) +(1647643--1647644) +(1650715--1650716) +(1663003--1663004) +

(2914328--2914335) +(5601307--5601308) +(5677080--5677087) +(5681176--5681183) +

(5709848--5709855) +(5759000--5759007) +(6103067--6103068) +(8937499--8937500) +

(9166875--9166876) +(9199643--9199644)

Fix? no

Free blocks count wrong for group #3 (29930, counted=29938).

Fix? no

Free blocks count wrong for group #28 (14797, counted=14815).

Fix? no

Free blocks count wrong for group #50 (14566, counted=14572).

Fix? no

Free blocks count wrong for group #88 (22821, counted=22829).

Fix? no

Free blocks count wrong for group #170 (17871, counted=17873).

Fix? no

Free blocks count wrong for group #173 (23765, counted=23781).

Fix? no

Free blocks count wrong for group #174 (17189, counted=17197).

Fix? no

Free blocks count wrong for group #175 (23012, counted=23020).

Fix? no

Free blocks count wrong for group #186 (20133, counted=20135).

Fix? no

Free blocks count wrong for group #272 (15791, counted=15793).

Fix? no

Free blocks count wrong for group #279 (27987, counted=27989).

Fix? no

Free blocks count wrong for group #280 (29868, counted=29870).

Fix? no

Free blocks count wrong (6177835, counted=6177917).

Fix? no

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

*

24893 inodes used (0.69%)

1035 non-contiguous files (4.2%)

29 non-contiguous directories (0.1%)

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

Extent depth histogram: 24699/186

8272853 blocks used (57.25%)

0 bad blocks

1 large file

21892 regular files

2992 directories

0 character device files

0 block device files

0 fifos

0 links

0 symbolic links (0 fast symbolic links)

0 sockets

--------

24884 files

~ # ←[6n

I'm crossing my fingers on this result =/
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, so /data is somewhat corrupted, if it's not a hardware problem you can actually use TWRP if you prefer, instead of mkfs

what version of TWRP are you running (one user confirmed it to be working on 2.6.3.3), you go to the wipe menu, and select FORMAT

or if you prefer mkfs, let me know
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Uhm how do we know if it's a hardware or software problem? Or we just guess? hehe. I'm using TWRP 2.6.3.3. I don't know what mkfs is. As for the FORMAT method, I've tried Wipe > Advance Wipe > Dalvik Cache, Cache, System, Data. I've tried this a lot of times. And it used to work before, but now I can't complete an AROMA installation or even just copy a file into the sdcard using TWRP. What would you recommend? I saw a tutorial from mike1986 on "How to: Fix a corrupted DATA partition on the HTC One", is his mkfs solution same as yours?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
if it's hardware, then even after the full format (not wipe), the e2fsck will come back with errors, so hopefully not. in TWRP 2.6.3.3 go to the wipe menu:

and select FORMAT DATA, check the log, it should say something like "formatting data using mk2fs" (or similar)
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
This is the result I got after Formatting the Data:

View attachment 2677292

It says "Data Format Complete" "Successful"
[One (M7) Q&A, Help & Troubleshooting] nkk71:
and it did say it used "make_ext4fs", so now reboot recovery

run the mount/umount again and then the e2fsck
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
what will I mount again? hehe. I'm sorry I'm really not used to this. hehe. I tried this:

umount /data

umount /sdcard

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

and I got these results:

~ # ←[6numount /data

umount /data

umount: can't umount /data: Invalid argument

~ # ←[6numount /sdcard

umount /sdcard

umount: can't umount /sdcard: Invalid argument

~ # ←[6ne2fsck -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

13 inodes used (0.00%)

0 non-contiguous files (0.0%)

0 non-contiguous directories (0.0%)

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

Extent depth histogram: 5

272824 blocks used (1.89%)

0 bad blocks

1 large file

0 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

--------

4 files

~ # ←[6n

---------- Post added at 02:27 AM ---------- Previous post was at 02:18 AM ----------

I'm sorry bro. But I'm really excited and optimistic about this. So what does this result mean? hehe. Is this good? Did I just had a software corruption or hardware? I apologize for my many questions! haha but I'd be really really really happy if this is really the fix that I have been looking for 9mos ago!!!!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
looks good now :) let's hope it stays

now go ahead:

adb push or adb sideload or OTG cable

Good luck
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh man. Slight problem here. I was able to successfully flash the ARHD 62.0. But it keeps on rebooting now. I think it rebooted for the 8th time already. It only loaded until the Sense UI once out of 8. =/ Any suggestions?

---------- Post added at 02:51 AM ---------- Previous post was at 02:44 AM ----------

I made another test of umount and e2fsck -n -v -f /dev/block/mmcblk0p37, and here is the result.

C:\mini-sdk>adb shell

~ # ←[6numount /data

umount /data

~ # ←[6numount /sdcard

umount /sdcard

~ # ←[6ne2fsck -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

1493 inodes used (0.04%)

99 non-contiguous files (6.6%)

2 non-contiguous directories (0.1%)

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

Extent depth histogram: 1222/3

747165 blocks used (5.17%)

0 bad blocks

1 large file

703 regular files

521 directories

0 character device files

0 block device files

0 fifos

0 links

253 symbolic links (253 fast symbolic links)

7 sockets

--------

1484 files

~ # ←[6n

The data seems to show normal signs right?

Or should I reinstall ARHD 62.0?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
do you have 53.0? in your particular situation, I would go for a super-stable ROM... remember 62.0 is a ported ROM, and

could

have some problems, get 31.6 or 53.0

and do a clean install of one of those.... first get your phone up and running, then you can try cutting edge ;)

remember to check MD5 on your download to make sure it's not corrupt, and before rebooting wipe dalvik and cache.
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh Okay! haha. I was about to ask about the stability of the 62.0. I'll go for the 53.0 then. I'll give you a feedback on how it goes! But so far man, you just saved this phone's life! I was about to throw it away! hahaha. I only used it effectively for 8 out 11 months in my hands. Now I hope it could be of good service! haha. How could I ever repay you bro?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
62.0 is very stable (i'm using it more or less),

but right now in your situation

, you should fall back to something that is 100% reliable, just to get the phone up and running.

Good Luck
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh I see! Thanks again! I gotta say thanks A MILLION TIMES MAN!!!! haha. So according to the results, could you conclude that the corruption I had was just software?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hopefully yes, once you have a ROM up and running, try an e2fsck again tomorrow, and if no errors show up, you should be good :good:
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
I'll try another e2fsck in a while. But so far, I'm getting several random reboots. I'll post the result of the e2fsck here. Thanks again for your very quick and effective help! Appreciate it a million times!:highfive:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Random reboots, and errors are back, so I must unfortunately conclude it's a hardware problem :(

both /system and /cache get mkfs_ext4 formatted during the install, the only one that doesn't is /data which only gets wiped to protect internal storage (ie /data/media), but you did format it using TWRP.

so if these errors keep creeping back up (and the random reboots), then unfortunately it looks like a hardware problem.
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh man. That's such a bad news. Would you mind explaining mkfs_ext4 in a simplified way to me? How about the method mike1986 posted? Was that a different solution? hehe
[One (M7) Q&A, Help & Troubleshooting] nkk71:
the mkfs_ext4 (make filesystem ext4) is what we would usually call "format"... such as formatting a USB stick, hard drive, etc, whereas wipe means you're just deleting all the files.

so if you take an external hard-drive as an example, you can plug it in to your computer and delete all the files (= wipe), but if the hard-drive has bad sectors on it (or otherwise corrupted) they will not get added to the "bad sector pool", usually you fix this with chkdsk in Windows, or by using format.

now on the M7 /data has sort of two parts:

/data (except /data/media) = user apps + settings, etc

/data/media = internal storage (where all the music, pictures, etc are)

so if you use format on /data you will erase everything including your pictures, music, etc.... hence the ROM installers wipe everything from /data but exclude /data/media, therefore preserving your pictures, music etc.

however, sometimes that partition does become corrupted and you have to do a format (for linux: mkfs_ext4), the get rid of the bad blocks/crossnodes/etc.

Unfortunately in your case, even after you've done that, after a while errors are creeping up again (and not only in /data), so this would indicate a hardware problem, and not solvable through software.

what TWRP does should be the same as mike's procedure, (and confirmed to have worked for another user, also with a corrupt data partition), mike's way is just more manual, and could be because earlier versions of the custom recoveries didn't have that option... though I'm not sure about it, but if I remember CWM correctly, it didn't have that option (could be wrong though)

you are welcome to try mike's method again, but my reasoning is as follows:

1- e2fsck -> confirms corruptions

2- TWRP format works

3- e2fsck -> confirms no more problems

...

4- at some time later, e2fsc reports problems again.

===> best guess, hardware problem

you can always try mike's method on /system and /data partition, and see if that get's you anywhere. since the file is no longer on his blog, i've attached it for you (it's compressed, so you need to unrar it first).
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
Oh okay. Thanks for that quick lesson on these terminologies. Hmmm... I've researched a few on e2fsck. It has some more attributes/options that could execute commands right? I don't know what they mean though, but couldn't one of those commands help repair a corrupt partition? Just a curious thought.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
e2fsck is just like windows chkdsk, if you want to use that to repair, then use it without the -n:

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

^^ should automatically answer yes, but if it says you have to run it manually, then

e2fsck -v -f /dev/block/mmcblk0p37

and answer with "y" for fixing errors.
[One (M7) Q&A, Help & Troubleshooting] ralphphilipgo:
I see! Is it safe enough to try to fix the errors? And a quick question too. Is bad block = bad sector? and is corrupt = bad sector? The results says 0 bad blocks, so shouldn't that say that the disk is still working fine? Or are there other factors that could lead to a disk failure? I apologize for the many questions. I'm just so curious and eager to learn from this experience. :o
[One (M7) Q&A, Help & Troubleshooting] nkk71:
It's safe to run the commands, they won't hurt the filesystem.... they'll try to fix as much as they can. As to your other question about blocks/sectors/etc. I actually, don't know... never really looked into the structure of an ext partition :o

oh and if you ever get a bad "superblock", then e2fsck won't help, only a full format.