recovery help please

Salman787 · Sep 13, 2014

Vi553r said:
Be sure to have you're device in recovery mode. Not in fastboot mode or hboot.

It's important that adb devices will list your device. Else adb can't do anything.

Try another USB port on you're pc, hopefully it's gonna load some drivers so adb can recognize you're device.

i have booted up in recovery. I sucessfully executed the fist 3 commands;
* adb push mkfs.ext4 /tmp
* adb shell
* chmod 777 /tmp/mkfs.ext4

but the 4th one generates an error saying;

chmod: invalid option -- O
BusyBox v1.21.1-jb bionic (2013-07-25 21:23 +0100) multi-call binary.

Usage: chmod [-R] MODE[,MODE]... FILE...

Vi553r · Sep 13, 2014

I don't know if you have a multi call binary. It doesn't say me anything. You can try to skip the chmod and go on with the procedure.

Salman787 · Sep 13, 2014

Vi553r said:
I don't know if you have a multi call binary. It doesn't say me anything. You can try to skip the chmod and go on with the procedure.

i've copied the command from the page and pasted it in cmw window and pressed enter. following is the message;

~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^ext ra_isize -m 0 /dev/block/mmcblk0p47
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p47
mke2fs 1.41.12 (17-May-2010)
mkfs.ext4: invalid blocks count - /dev/block/mmcblk0p47

Vi553r · Sep 13, 2014

And it doesn't go any further?

Salman787 · Sep 13, 2014

Vi553r said:
And it doesn't go any further?

nope it come back to the previous prompt

i.e, the process stops

Vi553r · Sep 13, 2014

Ok...
I'm afraid that it won't work on verizon models of the M8.
Thing is.... On the m7 the data block is mmcblk0p37 on the m8 international version the block is mmcblk0p47.
I don't know which block is used on you're model.

I'm @ work right now so I can't do any research right away to see if the data block differs from verizon to international models.

---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------

BTW, I read back and saw you are using twrp latest version.
That version has a build in option to repair the data block wich you can't. Mount.
Just in recovery you can fix it.
If you give me a sec I look into twrp and tell you where to go....

Salman787 · Sep 13, 2014

Vi553r said:
Ok...
I'm afraid that it won't work on verizon models of the M8.
Thing is.... On the m7 the data block is mmcblk0p37 on the m8 international version the block is mmcblk0p47.
I don't know which block is used on you're model.

I'm @ work right now so I can't do any research right away to see if the data block differs from verizon to international models.

---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------

BTW, I read back and saw you are using twrp latest version.
That version has a build in option to repair the data block wich you can't. Mount.
Just in recovery you can fix it.
If you give me a sec I look into twrp and tell you where to go....

thanx, i've tried the twrp repair option but issue is as such. I guess I have to live with it

Vi553r · Sep 13, 2014

Salman787 said:
thanx, i've tried the twrp repair option but issue is as such. I guess I have to live with it

But you must not use the repair option but the change filesystem option.
Then you choose ext4 even though you are already on ext4 and then change filesystem

Try that one ...maybe this time youre lucky.

Thus:
In TWRP go to WIPE / ADVANCED WIPE
Tick the data partition and then click on repair or change filesystem
choose ext4 for filesystem.

You must tick the data block and not the internal storage block bhecause internal storage is a partition on youre data block. So id /Data is corrupted...so is your internal storage.

Salman787 · Sep 13, 2014

Vi553r said:
But you must not use the repair option but the change filesystem option.
Then you choose ext4 even though you are already on ext4 and then change filesystem

Try that one ...maybe this time youre lucky.

Thus:
In TWRP go to WIPE / ADVANCED WIPE
Tick the data partition and then click on repair or change filesystem
choose ext4 for filesystem.

You must tick the data block and not the internal storage block bhecause internal storage is a partition on youre data block. So id /Data is corrupted...so is your internal storage.

tried that but failed to.

Looking at the issue i visited the following page;

http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

using these commands similar to yours, i got it to run. after completion when i entered mount /data it said "mounting dta failed on ext4: no such file or directory"

Vi553r · Sep 13, 2014

Salman787 said:
tried that but failed to.

Looking at the issue i visited the following page;

http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

using these commands similar to yours, i got it to run. after completion when i entered mount /data it said "mounting dta failed on ext4: no such file or directory"

That link refers to a m7 solution for the data problem. On m7 it was block 37 on the m8 it's block 47.i think that's why you still can't mount data.
But I'm not sure verizon models use the same block 47 number.

Speckydodge · Sep 26, 2014

so is there a way to find what the verizon block number is on the m8?

Vi553r · Sep 26, 2014

Verizon htc m8 blocks:

mmcblk0p3: 00004000 00000200 "board_info
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_updat
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_con
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1
mmcblk0p26: 00180000 00000200 "modem_st2
mmcblk0p27: 01400000 00000200 "fataldevl
mmcblk0p28: 00001000 00000200 "debug_con
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_reco
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hu
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quali
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"

User data should be the one, I'm not 100% sure... But then it should be block 48.

Speckydodge · Sep 27, 2014

Vi553r said:
Verizon htc m8 blocks:

mmcblk0p3: 00004000 00000200 "board_info
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_updat
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_con
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1
mmcblk0p26: 00180000 00000200 "modem_st2
mmcblk0p27: 01400000 00000200 "fataldevl
mmcblk0p28: 00001000 00000200 "debug_con
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_reco
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hu
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 01000000 00000200 "vzw_quali
mmcblk0p42: 01de6000 00000200 "reserve"
mmcblk0p43: 01000000 00000200 "boot"
mmcblk0p44: 01800000 00000200 "recovery"
mmcblk0p45: 05800000 00000200 "reserve_3
mmcblk0p46: a8000000 00000200 "system"
mmcblk0p47: 40000000 00000200 "cache"
mmcblk0p48: 30000000 00000200 "userdata"

User data should be the one, I'm not 100% sure... But then it should be block 48.

tried 48 instead of 47 still getting an invalid blocks count

cjbart1009 · Sep 29, 2014

Vi553r said:
That link refers to a m7 solution for the data problem. On m7 it was block 37 on the m8 it's block 47.i think that's why you still can't mount data.
But I'm not sure verizon models use the same block 47 number.

I'm getting the error saying
mke2fs 1.41.12 <17-May-2010>
mkfs.ext4: invalid blocks count - /dev/block/mmcblk0p47

Speckydodge · Sep 29, 2014

every rom i try flash I'm getting the message

set_perm: some changes failed

anyone know why this is happening?

mysiak_d · Oct 20, 2014

cjbart1009 said:
I'm getting the error saying
mke2fs 1.41.12 <17-May-2010>
mkfs.ext4: invalid blocks count - /dev/block/mmcblk0p47

Hi, did you find any solution? I have the same problem with the same "invalid blocks count" problem....

Alex-V · Oct 20, 2014

mysiak_d said:
Hi, did you find any solution? I have the same problem with the same "invalid blocks count" problem....

I think this can help

http://android-revolution-hd.blogspot.de/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html?m=1

smeejaytee · Nov 30, 2014

Hi I had unsubscribed from this thread as my problem got solved, it was actually quite easy just flash a full wipe fuu, I got mine from sneakyghosts thread but I see your on a US network I think you have to look in the forums for your device but I know there is a fuu thread, this fixes all partitions and should get you up and running again. I hope this may help if you still have your issue. I have resubscibed so I can keep an eye on the thread sorry I'm late.

Sent from my HTC One_M8 using XDA Free mobile app

xunholyx · Dec 1, 2014

smeejaytee said:
Hi I had unsubscribed from this thread as my problem got solved, it was actually quite easy just flash a full wipe fuu, I got mine from sneakyghosts thread but I see your on a US network I think you have to look in the forums for your device but I know there is a fuu thread, this fixes all partitions and should get you up and running again. I hope this may help if you still have your issue. I have resubscibed so I can keep an eye on the thread sorry I'm late.

Sent from my HTC One_M8 using XDA Free mobile app

Us versions, and only US versions, have actual RUUs they can use.

EDIT: I am wrong here. I just got a download today for an RUU for the international versions. First time I've ever heard of it for non US M8s.

WoodmanMN · May 13, 2015

Vi553r said:
Ok, here we go

First
* Download this mkfs.ext4 binary
https://www.dropbox.com/s/kxpun5kd2rrh28s/mkfs.ext4?dl=0
* Connect your device to the PC
* Boot your device in recovery mode
* Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:

make sure you copy mkifs.ext4 into the directory where you have adb.exe located
* cd "place where you have your fastboot.exe and adb.exe"
* adb push mkfs.ext4 /tmp
* adb shell
* chmod 777 /tmp/mkfs.ext4
* /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p47

You will now see some text scrolling along. Just let the tool finish and youre /data partition is perfect once again.

After everything is done we mount /data and make the virtual sdcard on it.
* mount /data
* mkdir -p /data/media/0

done, you can use "Exit" to go out of the cmd screen.
Now, reflash a rom via recovery and youre up and running again

I am getting an Invalid Blocks Count error when I try this. I tried the same thing on another tutorial I found, but apparently with the wrong block number written on it, mine stated mmcblk0p37 instead of the 47 your tutorial has. Any way to fix?

Nevermind, found the post a few above me that had the other partition fix method. Trying now.

---------- Post added at 12:00 PM ---------- Previous post was at 11:24 AM ----------

Alex-V said:
I think this can help

http://android-revolution-hd.blogspot.de/2014/09/how-to-fix-random-reboots-on-htc-one-m8.html?m=1

Thank you so much, that fixed my problem!

recovery help please

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

Member

Member

Senior Member

Member

Member

Inactive Recognized Developer

Inactive Recognized Contributor

Recognized Contributor

Senior Member

Similar threads

Top Liked Posts