[OTA/RECOVERY/HBOOT/RUUS/FIRMWARE/DUMPS] T-Mobile HTC M8 - AndroidFileHost & How Tos

Search This thread
By:
Advanced…
sapplegater

sapplegater

Senior Member
Apr 26, 2011
326
108
32
Florence, KY
[OTA/RECOVERY/HBOOT/RUUS/FIRMWARE/DUMPS] T-Mobile HTC M8 - AndroidFileHost & How Tos


IF SOMEONE IS INTERESTED IN TAKING OVER THIS THREAD CONTACT ME I NO LONGER HAVE A M8


HTC-One-M8-Gray-Gold-631x378.jpg


**ALL FILES ARE USE AT YOUR OWN RISK!**


All Files Are Untouched Stock
**CLICK GROUP TITLE FOR FOLDER**

OTA's:


Stock Firmwares:


Stock H-boot (All Hboots include a MD5 file) [Make sure to unzip do not flash zip.]:

Non IMG:

IMG:


Recoveries:

RUUS (EXE):

Having issues? RUU won't load?
Make Sure To Have VC REDIST 2005, 2008, and 2010 Installed


RUUS (ZIP):


Stock Dumps:


Stock TWRP Nandroid Backups: COMING SOON
Android 4.4.2 - 1.57.531.7
Android 4.4.3 - 2.22.531.5
Android 4.4.3 - 2.22.531.6

How tos:

Backup Hboot (MUST HAVE ROOT):

To back up hboot use the following code in cmd prompt:

Code: 
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11

This will back up your hboot to your internal sdcard.
If you want a hboot image use this:

Code: 
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11.img

Restore Hboot backup from either booted inside Android or from Recovery:

BEFORE FLASHING MAKE SURE TO CHECK MD5 IF YOU DOWNLOADED ONE OF MY FILES!

Make sure the backup hboot is on your internal sdcard and then issue this command in cmd prompt:

Code: 
adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11

Next run this code to make sure it flashed correctly if it says they differ DO NOT REBOOT!
Code: 
diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11

If you use a .img run this:
Code: 
adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11.img

And just like the other one run this:
if it says they differ DO NOT REBOOT!
Code: 
diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11.img
Are you S-ON?
***IF YOU ARE S-ON THEY WILL DIFFER CAUSE YOU CAN"T FLASH THESE***


HTC M8 Partition Information

lrwxrwxrwx root root 2014-09-30 00:08 adsp -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-09-30 00:08 board_info -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-09-30 00:08 boot -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2014-09-30 00:08 cache -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 2014-09-30 00:08 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2014-09-30 00:08 cdma_record -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-09-30 00:08 cir_img -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 2014-09-30 00:08 control -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-09-30 00:08 custdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-09-30 00:08 ddr -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-09-30 00:08 debug_config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-09-30 00:08 devlog -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 2014-09-30 00:08 dsps -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-09-30 00:08 extra -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-09-30 00:08 fataldevlog -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-09-30 00:08 fsc -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2014-09-30 00:08 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-09-30 00:08 hboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-09-30 00:08 local -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-09-30 00:08 mfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-09-30 00:08 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-09-30 00:08 modem_st1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-09-30 00:08 modem_st2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-09-30 00:08 pdata -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-09-30 00:08 pg1fs -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-09-30 00:08 pg2fs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-09-30 00:08 radio -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-09-30 00:08 radio_config -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-09-30 00:08 recovery -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2014-09-30 00:08 reserve -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 2014-09-30 00:08 reserve_1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-09-30 00:08 reserve_2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-09-30 00:08 reserve_3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2014-09-30 00:08 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-09-30 00:08 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-09-30 00:08 sbl1_update -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-09-30 00:08 sdi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-09-30 00:08 sensor_hub -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 2014-09-30 00:08 skylink -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2014-09-30 00:08 sp1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-09-30 00:08 ssd -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2014-09-30 00:08 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2014-09-30 00:08 tool_diag -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-09-30 00:08 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-09-30 00:08 userdata -> /dev/block/mmcblk0p47
lrwxrwxrwx root root 2014-09-30 00:08 wcnss -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-09-30 00:08 wifi -> /dev/block/mmcblk0p13



More to come...





​
 
Last edited:
  • Like
Reactions: KHALMO, rnrstar, A_1st and 10 others
billydroid

billydroid

Senior Member
Jun 24, 2010
1,599
481
Do I have to s-off to flash the Ota? Just go go to stock 1.57 w/ stock recovery. Then just put it on the root of my sdcard and boot into fastboot and let it update right? Since it's a tmobile update and the Id matches. Have have not done it this way in a really long time
 
sapplegater

sapplegater

Senior Member
Apr 26, 2011
326
108
32
Florence, KY
billydroid said:
Do I have to s-off to flash the Ota? Just go go to stock 1.57 w/ stock recovery. Then just put it on the root of my sdcard and boot into fastboot and let it update right? Since it's a tmobile update and the Id matches. Have have not done it this way in a really long time
Click to expand...
Click to collapse

You don't need S-off for this all you need to have is a complete stock ROM including the file that bootloader unlock deletes (if you've unlocked bootloader) and the stock recovery. And the easiest way to flash it is going to be to put the OTA on the root of your internal storage boot into stock recovery and when you see just an image of a phone hold the power button and then press up on the volume key and it will give you the option to install from internal storage. (It may be power and volume down if up doesn't work.)
 
billydroid

billydroid

Senior Member
Jun 24, 2010
1,599
481
The file unlocking the bootloader deletes? I never knew of such a file

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

If I restore a stock backup. It's that file in there?
 
sapplegater

sapplegater

Senior Member
Apr 26, 2011
326
108
32
Florence, KY
billydroid said:
The file unlocking the bootloader deletes? I never knew of such a file

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

If I restore a stock backup. It's that file in there?
Click to expand...
Click to collapse

It deletes the calculator app, flashlight and some other file when you unlock the bootloader I know the stock backups I've used don't have them so I followed this thread to get them back and you should then be full stock.
 
billydroid

billydroid

Senior Member
Jun 24, 2010
1,599
481
Restore stock backup, downloaded off xda. Fish stock recovery. Then flash Ota through the stock recovery. Thats it right?

---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

I don't need to relock first, correct?

---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------

Sorry for all the questions. I haven't flashed through a stock recovery in years.

Do I extract this 2.22 zip and then put on the root of the sdcard or leave it as is?
 
sapplegater

sapplegater

Senior Member
Apr 26, 2011
326
108
32
Florence, KY
billydroid said:
Restore stock backup, downloaded off xda. Fish stock recovery. Then flash Ota through the stock recovery. Thats it right?

---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

I don't need to relock first, correct?

---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------

Sorry for all the questions. I haven't flashed through a stock recovery in years.

Do I extract this 2.22 zip and then put on the root of the sdcard or leave it as is?
Click to expand...
Click to collapse

That is correct. :)

DONT extract the 2.22 zip flash it as a zip.
 
Last edited:
  • Like
Reactions: billydroid
Luigiesin

Luigiesin

Senior Member
Jul 16, 2010
1,172
471
City of Angels, CA
Last edited:
B

Badcam3

Senior Member
Feb 17, 2010
119
31
Downers Grove
aaronc_98 said:
What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.
Click to expand...
Click to collapse

Luigiesin said:
That's been my issue too.. It's a mission to get just the firmware without replacing custom recovery and such... I got a FW from another member that just flashes the firmware and new radio.. Uploading now... You have to flash it through Hboot.


Here you go : https://www.dropbox.com/s/7dqnr7xrsdeyb93/2.22.401.4-noredtext.zip
Click to expand...
Click to collapse

As I recall you will need to go back to complete stock and relock your bootloader. I think you should be able to back up your rom and restore it after you update the firmware and unlock it again.
 
Luigiesin

Luigiesin

Senior Member
Jul 16, 2010
1,172
471
City of Angels, CA
Badcam3 said:
As I recall you will need to go back to complete stock and relock your bootloader. I think you should be able to back up your rom and restore it after you update the firmware and unlock it again.
Click to expand...
Click to collapse

I haven't tried it yet but from what I know this only updates the necessary partitions without locking the bootloader.. This is just the bare firmware... It won't replace recovery and won't lock bootloader.
 
You must log in or register to reply here.

Similar threads

Garmig
[Recovery] [RUU 4.20.531.4] [TWRP Nandroid Backups] [Radio IMGs][ OTA 4.20.531.4 ]
Replies
784
Views
231K
T
Technoolli
VolcanicSkunk
[GUIDE] [T-Mobile] Unlock Bootloader, Install Custom Recovery, Root, S-Off
Replies
126
Views
126K
wakas_razaq
wakas_razaq
Behold_this
  • Locked
[COLLECTION][FIRMWARE][RUU][BACKUPS] T-Mobile US - Release Builds (Update 5/16)
Replies
78
Views
70K
Behold_this
Behold_this
C
[Q] HTC One M8 dropping data connectivity but showing 4G LTE...
Replies
49
Views
96K
F
fullshred
x714x
T-Mobile HTC M8 Free $50!
Replies
18
Views
57K
Rydah
Rydah

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 13
    sapplegater
    sapplegater
    [OTA/RECOVERY/HBOOT/RUUS/FIRMWARE/DUMPS] T-Mobile HTC M8 - AndroidFileHost & How Tos


    IF SOMEONE IS INTERESTED IN TAKING OVER THIS THREAD CONTACT ME I NO LONGER HAVE A M8


    HTC-One-M8-Gray-Gold-631x378.jpg


    **ALL FILES ARE USE AT YOUR OWN RISK!**


    All Files Are Untouched Stock
    **CLICK GROUP TITLE FOR FOLDER**

    OTA's:


    Stock Firmwares:


    Stock H-boot (All Hboots include a MD5 file) [Make sure to unzip do not flash zip.]:

    Non IMG:

    IMG:


    Recoveries:

    RUUS (EXE):

    Having issues? RUU won't load?
    Make Sure To Have VC REDIST 2005, 2008, and 2010 Installed


    RUUS (ZIP):


    Stock Dumps:


    Stock TWRP Nandroid Backups: COMING SOON
    Android 4.4.2 - 1.57.531.7
    Android 4.4.3 - 2.22.531.5
    Android 4.4.3 - 2.22.531.6

    How tos:

    Backup Hboot (MUST HAVE ROOT):

    To back up hboot use the following code in cmd prompt:

    Code: 
    adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11

    This will back up your hboot to your internal sdcard.
    If you want a hboot image use this:

    Code: 
    adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11.img

    Restore Hboot backup from either booted inside Android or from Recovery:

    BEFORE FLASHING MAKE SURE TO CHECK MD5 IF YOU DOWNLOADED ONE OF MY FILES!

    Make sure the backup hboot is on your internal sdcard and then issue this command in cmd prompt:

    Code: 
    adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11

    Next run this code to make sure it flashed correctly if it says they differ DO NOT REBOOT!
    Code: 
    diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11

    If you use a .img run this:
    Code: 
    adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11.img

    And just like the other one run this:
    if it says they differ DO NOT REBOOT!
    Code: 
    diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11.img
    Are you S-ON?
    ***IF YOU ARE S-ON THEY WILL DIFFER CAUSE YOU CAN"T FLASH THESE***


    HTC M8 Partition Information

    lrwxrwxrwx root root 2014-09-30 00:08 adsp -> /dev/block/mmcblk0p16
    lrwxrwxrwx root root 2014-09-30 00:08 board_info -> /dev/block/mmcblk0p3
    lrwxrwxrwx root root 2014-09-30 00:08 boot -> /dev/block/mmcblk0p42
    lrwxrwxrwx root root 2014-09-30 00:08 cache -> /dev/block/mmcblk0p46
    lrwxrwxrwx root root 2014-09-30 00:08 carrier -> /dev/block/mmcblk0p37
    lrwxrwxrwx root root 2014-09-30 00:08 cdma_record -> /dev/block/mmcblk0p33
    lrwxrwxrwx root root 2014-09-30 00:08 cir_img -> /dev/block/mmcblk0p40
    lrwxrwxrwx root root 2014-09-30 00:08 control -> /dev/block/mmcblk0p30
    lrwxrwxrwx root root 2014-09-30 00:08 custdata -> /dev/block/mmcblk0p22
    lrwxrwxrwx root root 2014-09-30 00:08 ddr -> /dev/block/mmcblk0p14
    lrwxrwxrwx root root 2014-09-30 00:08 debug_config -> /dev/block/mmcblk0p28
    lrwxrwxrwx root root 2014-09-30 00:08 devlog -> /dev/block/mmcblk0p39
    lrwxrwxrwx root root 2014-09-30 00:08 dsps -> /dev/block/mmcblk0p15
    lrwxrwxrwx root root 2014-09-30 00:08 extra -> /dev/block/mmcblk0p32
    lrwxrwxrwx root root 2014-09-30 00:08 fataldevlog -> /dev/block/mmcblk0p27
    lrwxrwxrwx root root 2014-09-30 00:08 fsc -> /dev/block/mmcblk0p34
    lrwxrwxrwx root root 2014-09-30 00:08 fsg -> /dev/block/mmcblk0p19
    lrwxrwxrwx root root 2014-09-30 00:08 hboot -> /dev/block/mmcblk0p11
    lrwxrwxrwx root root 2014-09-30 00:08 local -> /dev/block/mmcblk0p31
    lrwxrwxrwx root root 2014-09-30 00:08 mfg -> /dev/block/mmcblk0p5
    lrwxrwxrwx root root 2014-09-30 00:08 misc -> /dev/block/mmcblk0p24
    lrwxrwxrwx root root 2014-09-30 00:08 modem_st1 -> /dev/block/mmcblk0p25
    lrwxrwxrwx root root 2014-09-30 00:08 modem_st2 -> /dev/block/mmcblk0p26
    lrwxrwxrwx root root 2014-09-30 00:08 pdata -> /dev/block/mmcblk0p29
    lrwxrwxrwx root root 2014-09-30 00:08 pg1fs -> /dev/block/mmcblk0p2
    lrwxrwxrwx root root 2014-09-30 00:08 pg2fs -> /dev/block/mmcblk0p6
    lrwxrwxrwx root root 2014-09-30 00:08 radio -> /dev/block/mmcblk0p20
    lrwxrwxrwx root root 2014-09-30 00:08 radio_config -> /dev/block/mmcblk0p18
    lrwxrwxrwx root root 2014-09-30 00:08 recovery -> /dev/block/mmcblk0p43
    lrwxrwxrwx root root 2014-09-30 00:08 reserve -> /dev/block/mmcblk0p41
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_1 -> /dev/block/mmcblk0p4
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_2 -> /dev/block/mmcblk0p23
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_3 -> /dev/block/mmcblk0p44
    lrwxrwxrwx root root 2014-09-30 00:08 rpm -> /dev/block/mmcblk0p8
    lrwxrwxrwx root root 2014-09-30 00:08 sbl1 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root root 2014-09-30 00:08 sbl1_update -> /dev/block/mmcblk0p7
    lrwxrwxrwx root root 2014-09-30 00:08 sdi -> /dev/block/mmcblk0p10
    lrwxrwxrwx root root 2014-09-30 00:08 sensor_hub -> /dev/block/mmcblk0p38
    lrwxrwxrwx root root 2014-09-30 00:08 skylink -> /dev/block/mmcblk0p36
    lrwxrwxrwx root root 2014-09-30 00:08 sp1 -> /dev/block/mmcblk0p12
    lrwxrwxrwx root root 2014-09-30 00:08 ssd -> /dev/block/mmcblk0p35
    lrwxrwxrwx root root 2014-09-30 00:08 system -> /dev/block/mmcblk0p45
    lrwxrwxrwx root root 2014-09-30 00:08 tool_diag -> /dev/block/mmcblk0p21
    lrwxrwxrwx root root 2014-09-30 00:08 tz -> /dev/block/mmcblk0p9
    lrwxrwxrwx root root 2014-09-30 00:08 userdata -> /dev/block/mmcblk0p47
    lrwxrwxrwx root root 2014-09-30 00:08 wcnss -> /dev/block/mmcblk0p17
    lrwxrwxrwx root root 2014-09-30 00:08 wifi -> /dev/block/mmcblk0p13



    More to come...





    ​
    View
    2
    OfficialLocdoGg
    OfficialLocdoGg
    sapplegater said:


    View attachment 2904317


    **ALL FILES ARE USE AT YOUR OWN RISK!**


    All Files Are Untouched Stock
    **CLICK GROUP TITLE FOR FOLDER**

    OTA's:


    Stock Firmwares:


    Stock H-boot (All Hboots include a MD5 file) [Make sure to unzip do not flash zip.]:

    Non IMG:

    IMG:


    Recoveries:

    RUUS (EXE):

    Having issues? RUU won't load?
    Make Sure To Have VC REDIST 2005, 2008, and 2010 Installed


    RUUS (ZIP):


    Stock Dumps:


    Stock TWRP Nandroid Backups: COMING SOON
    Android 4.4.2 - 1.57.531.7
    Android 4.4.3 - 2.22.531.5
    Android 4.4.3 - 2.22.531.6

    How tos:

    Backup Hboot (MUST HAVE ROOT):

    To back up hboot use the following code in cmd prompt:

    Code: 
    adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11

    This will back up your hboot to your internal sdcard.
    If you want a hboot image use this:

    Code: 
    adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11.img

    Restore Hboot backup from either booted inside Android or from Recovery:

    BEFORE FLASHING MAKE SURE TO CHECK MD5 IF YOU DOWNLOADED ONE OF MY FILES!

    Make sure the backup hboot is on your internal sdcard and then issue this command in cmd prompt:

    Code: 
    adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11

    Next run this code to make sure it flashed correctly if it says they differ DO NOT REBOOT!
    Code: 
    diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11

    If you use a .img run this:
    Code: 
    adb shell
su
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11.img

    And just like the other one run this:
    if it says they differ DO NOT REBOOT!
    Code: 
    diff /sdcard/mmcblk0p11 /dev/block/mmcblk0p11.img
    Are you S-ON?
    ***IF YOU ARE S-ON THEY WILL DIFFER CAUSE YOU CAN"T FLASH THESE***


    HTC M8 Partition Information

    lrwxrwxrwx root root 2014-09-30 00:08 adsp -> /dev/block/mmcblk0p16
    lrwxrwxrwx root root 2014-09-30 00:08 board_info -> /dev/block/mmcblk0p3
    lrwxrwxrwx root root 2014-09-30 00:08 boot -> /dev/block/mmcblk0p42
    lrwxrwxrwx root root 2014-09-30 00:08 cache -> /dev/block/mmcblk0p46
    lrwxrwxrwx root root 2014-09-30 00:08 carrier -> /dev/block/mmcblk0p37
    lrwxrwxrwx root root 2014-09-30 00:08 cdma_record -> /dev/block/mmcblk0p33
    lrwxrwxrwx root root 2014-09-30 00:08 cir_img -> /dev/block/mmcblk0p40
    lrwxrwxrwx root root 2014-09-30 00:08 control -> /dev/block/mmcblk0p30
    lrwxrwxrwx root root 2014-09-30 00:08 custdata -> /dev/block/mmcblk0p22
    lrwxrwxrwx root root 2014-09-30 00:08 ddr -> /dev/block/mmcblk0p14
    lrwxrwxrwx root root 2014-09-30 00:08 debug_config -> /dev/block/mmcblk0p28
    lrwxrwxrwx root root 2014-09-30 00:08 devlog -> /dev/block/mmcblk0p39
    lrwxrwxrwx root root 2014-09-30 00:08 dsps -> /dev/block/mmcblk0p15
    lrwxrwxrwx root root 2014-09-30 00:08 extra -> /dev/block/mmcblk0p32
    lrwxrwxrwx root root 2014-09-30 00:08 fataldevlog -> /dev/block/mmcblk0p27
    lrwxrwxrwx root root 2014-09-30 00:08 fsc -> /dev/block/mmcblk0p34
    lrwxrwxrwx root root 2014-09-30 00:08 fsg -> /dev/block/mmcblk0p19
    lrwxrwxrwx root root 2014-09-30 00:08 hboot -> /dev/block/mmcblk0p11
    lrwxrwxrwx root root 2014-09-30 00:08 local -> /dev/block/mmcblk0p31
    lrwxrwxrwx root root 2014-09-30 00:08 mfg -> /dev/block/mmcblk0p5
    lrwxrwxrwx root root 2014-09-30 00:08 misc -> /dev/block/mmcblk0p24
    lrwxrwxrwx root root 2014-09-30 00:08 modem_st1 -> /dev/block/mmcblk0p25
    lrwxrwxrwx root root 2014-09-30 00:08 modem_st2 -> /dev/block/mmcblk0p26
    lrwxrwxrwx root root 2014-09-30 00:08 pdata -> /dev/block/mmcblk0p29
    lrwxrwxrwx root root 2014-09-30 00:08 pg1fs -> /dev/block/mmcblk0p2
    lrwxrwxrwx root root 2014-09-30 00:08 pg2fs -> /dev/block/mmcblk0p6
    lrwxrwxrwx root root 2014-09-30 00:08 radio -> /dev/block/mmcblk0p20
    lrwxrwxrwx root root 2014-09-30 00:08 radio_config -> /dev/block/mmcblk0p18
    lrwxrwxrwx root root 2014-09-30 00:08 recovery -> /dev/block/mmcblk0p43
    lrwxrwxrwx root root 2014-09-30 00:08 reserve -> /dev/block/mmcblk0p41
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_1 -> /dev/block/mmcblk0p4
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_2 -> /dev/block/mmcblk0p23
    lrwxrwxrwx root root 2014-09-30 00:08 reserve_3 -> /dev/block/mmcblk0p44
    lrwxrwxrwx root root 2014-09-30 00:08 rpm -> /dev/block/mmcblk0p8
    lrwxrwxrwx root root 2014-09-30 00:08 sbl1 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root root 2014-09-30 00:08 sbl1_update -> /dev/block/mmcblk0p7
    lrwxrwxrwx root root 2014-09-30 00:08 sdi -> /dev/block/mmcblk0p10
    lrwxrwxrwx root root 2014-09-30 00:08 sensor_hub -> /dev/block/mmcblk0p38
    lrwxrwxrwx root root 2014-09-30 00:08 skylink -> /dev/block/mmcblk0p36
    lrwxrwxrwx root root 2014-09-30 00:08 sp1 -> /dev/block/mmcblk0p12
    lrwxrwxrwx root root 2014-09-30 00:08 ssd -> /dev/block/mmcblk0p35
    lrwxrwxrwx root root 2014-09-30 00:08 system -> /dev/block/mmcblk0p45
    lrwxrwxrwx root root 2014-09-30 00:08 tool_diag -> /dev/block/mmcblk0p21
    lrwxrwxrwx root root 2014-09-30 00:08 tz -> /dev/block/mmcblk0p9
    lrwxrwxrwx root root 2014-09-30 00:08 userdata -> /dev/block/mmcblk0p47
    lrwxrwxrwx root root 2014-09-30 00:08 wcnss -> /dev/block/mmcblk0p17
    lrwxrwxrwx root root 2014-09-30 00:08 wifi -> /dev/block/mmcblk0p13



    More to come...





    ​
    Click to expand...
    Click to collapse



    This is the official 5.0.1 Lollipop (4.20.531.4) Sense 6.0 OTA for T-Mobile HTC One M8. (4.20.531.4)

    Nothing modified. Just a straight copy. Enjoy!


    If you just need the firmware or rom you can download the zip and extract what you need from it. It's pretty simple.

    I'll try to get around to extracting everything and posting links for the individual firmware as well. Don't get mad if I don't get around to it though. :)

    Don't do anything with this unless you know what you're doing.


    Download Link: https://docs.google.com/uc?export=download&confirm=mOs6&id=0B83tee7zNQDVTTRsTjJ1dzhHeUU
    View
    1
    sapplegater
    sapplegater
    billydroid said:
    Restore stock backup, downloaded off xda. Fish stock recovery. Then flash Ota through the stock recovery. Thats it right?

    ---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------

    I don't need to relock first, correct?

    ---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------

    Sorry for all the questions. I haven't flashed through a stock recovery in years.

    Do I extract this 2.22 zip and then put on the root of the sdcard or leave it as is?
    Click to expand...
    Click to collapse

    That is correct. :)

    DONT extract the 2.22 zip flash it as a zip.
    View
    1
    B
    Badcam3
    Luigiesin said:
    I'm S off actually
    Click to expand...
    Click to collapse

    I would go with relocking your bootloader and going the safe way but you can still flash the firmware with S-off it's just not as safe.

    http://venomroms.com/firmware_443/
    View
    1
    M
    Miguel97
    Flashing a new Hboot.

    Can I simply flash Hboot version 3.19.0.0000 with the following command
    Code: 
    sudo fastboot flash hboot Hboot-3.19.0.0000+-+3.32.531.2.zip
    Another question do I flash the entire zip over or extraxt the file and send only the binary file "mmcblk0p11" over. Will doing this wipe any data on the device?
    View

New posts