Post Reply

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

OP sapplegater

19th August 2014, 06:16 AM   |  #1  
sapplegater's Avatar
OP Senior Member
Flag Florence, KY
Thanks Meter: 90
 
289 posts
Join Date:Joined: Apr 2011
Donate to Me
More


Name:  HTC-One-M8-Gray-Gold-631x378.jpg
Views: 2488
Size:  22.4 KB


**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 by sapplegater; 21st October 2014 at 11:50 PM. Reason: Added Partition Information, Added Stock Nandroid Backups and thread cleanup.
The Following 7 Users Say Thank You to sapplegater For This Useful Post: [ View ]
20th August 2014, 01:53 AM   |  #2  
billydroid's Avatar
Senior Member
Thanks Meter: 191
 
997 posts
Join Date:Joined: Jun 2010
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
20th August 2014, 01:57 AM   |  #3  
sapplegater's Avatar
OP Senior Member
Flag Florence, KY
Thanks Meter: 90
 
289 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Quote:
Originally Posted by billydroid

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

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.)
20th August 2014, 01:59 AM   |  #4  
billydroid's Avatar
Senior Member
Thanks Meter: 191
 
997 posts
Join Date:Joined: Jun 2010
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?
20th August 2014, 02:01 AM   |  #5  
sapplegater's Avatar
OP Senior Member
Flag Florence, KY
Thanks Meter: 90
 
289 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Quote:
Originally Posted by billydroid

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?

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.
20th August 2014, 02:04 AM   |  #6  
billydroid's Avatar
Senior Member
Thanks Meter: 191
 
997 posts
Join Date:Joined: Jun 2010
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?
20th August 2014, 02:05 AM   |  #7  
sapplegater's Avatar
OP Senior Member
Flag Florence, KY
Thanks Meter: 90
 
289 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Quote:
Originally Posted by billydroid

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?

That is correct.

DONT extract the 2.22 zip flash it as a zip.
Last edited by sapplegater; 20th August 2014 at 02:35 AM.
The Following User Says Thank You to sapplegater For This Useful Post: [ View ]
20th August 2014, 11:14 PM   |  #8  
Senior Member
Thanks Meter: 8
 
129 posts
Join Date:Joined: Jun 2010
Best way?
What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.
21st August 2014, 02:11 AM   |  #9  
Luigiesin's Avatar
Senior Member
Flag City of Angels, CA
Thanks Meter: 447
 
1,118 posts
Join Date:Joined: Jul 2010
More
Quote:
Originally Posted by aaronc_98

What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.

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/7dqnr7xrsd...-noredtext.zip
Last edited by Luigiesin; 21st August 2014 at 02:14 AM.
21st August 2014, 05:26 AM   |  #10  
Senior Member
Downers Grove
Thanks Meter: 31
 
112 posts
Join Date:Joined: Feb 2010
More
Quote:
Originally Posted by aaronc_98

What is the best way to flash just the firmware? I am on viper so i think I have everything but the firmware updated.

Quote:
Originally Posted by Luigiesin

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/7dqnr7xrsd...-noredtext.zip

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.

Post Reply Subscribe to Thread

Tags
dump, firmware, ota, recovery, ruu
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in T-Mobile One (M8) General by ThreadRank