FORUMS

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

recovery help please

4,497 posts
Thanks Meter: 1,489
 
By smeejaytee, Senior Member on 17th August 2014, 02:18 PM
Post Reply Subscribe to Thread Email Thread
26th September 2014, 08:11 PM |#51  
Junior Member
Thanks Meter: 0
 
More
so is there a way to find what the verizon block number is on the m8?
 
 
26th September 2014, 09:53 PM |#52  
Member
Thanks Meter: 15
 
More
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.
The Following User Says Thank You to Vi553r For This Useful Post: [ View ]
27th September 2014, 11:25 AM |#53  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Vi553r

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
29th September 2014, 06:38 AM |#54  
Senior Member
Flag Los Angeles
Thanks Meter: 2
 
More
Quote:
Originally Posted by Vi553r

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
29th September 2014, 05:57 PM |#55  
Junior Member
Thanks Meter: 0
 
More
every rom i try flash I'm getting the message

set_perm: some changes failed

anyone know why this is happening?
20th October 2014, 10:01 PM |#56  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by cjbart1009

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....
20th October 2014, 11:42 PM |#57  
Alex-V's Avatar
Recognized Developer
Thanks Meter: 4,963
 
More
Quote:
Originally Posted by mysiak_d

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.blogspo...ne-m8.html?m=1
The Following User Says Thank You to Alex-V For This Useful Post: [ View ]
30th November 2014, 10:19 PM |#58  
smeejaytee's Avatar
OP Senior Member
Flag kent
Thanks Meter: 1,489
 
More
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
1st December 2014, 12:12 AM |#59  
xunholyx's Avatar
Senior Member
Flag Vancouver
Thanks Meter: 1,489
 
More
Quote:
Originally Posted by smeejaytee

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.
Last edited by xunholyx; 3rd December 2014 at 02:51 AM.
The Following User Says Thank You to xunholyx For This Useful Post: [ View ]
13th May 2015, 06:00 PM |#60  
Senior Member
Flag Duluth
Thanks Meter: 69
 
Donate to Me
More
Quote:
Originally Posted by Vi553r

Ok, here we go

First
* Download this mkfs.ext4 binary
https://www.dropbox.com/s/kxpun5kd2r...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,^ext ra_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 ----------

Quote:
Originally Posted by Alex-V

I think this can help

http://android-revolution-hd.blogspo...ne-m8.html?m=1

Thank you so much, that fixed my problem!
Last edited by WoodmanMN; 13th May 2015 at 05:39 PM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes