[3-15-15][firmware][all stock img]All files have updated to Lillipop

Search This thread

sdana

Senior Member
Jan 7, 2011
73
9
Tried flashing the twrp version of the 5.0.1 firmware twice now, 2 different downloads and both gave me an error that they were unable to flash. Anyone have any ideas as to why?

Sent from my HTC6525LVW using XDA Free mobile app
 
  • Like
Reactions: cmh436

santod040

Recognized Developer / Recognized Contributor
Nov 7, 2008
12,569
23,612
NorCal
Tried flashing the twrp version of the 5.0.1 firmware twice now, 2 different downloads and both gave me an error that they were unable to flash. Anyone have any ideas as to why?

Sent from my HTC6525LVW using XDA Free mobile app
You're not trying to flash it in recovery are you?
Firmware is flashed in fastboot, check the instructions in the OP.
 
  • Like
Reactions: sdana

sdana

Senior Member
Jan 7, 2011
73
9
Ah ha that must be it. I got confused by the TWRP users/CWM users use this. I'll try that later. Thanks!

Sent from my HTC6525LVW using XDA Free mobile app
 

smokawhat

Member
May 12, 2014
28
2
I just installed the firmware file VZWm8LfirmwareTWRP.zip and my phone still says Android 4.4.2? WHY is that? btw I have VenomOne Rom installed and plane on upgrading the Rom to 4.3.0.... Do I now have the newest firmware?


But in my fastboot it has this info:

CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5
eMMC-boot 2048MB
Feb 3 2015,21:50:28.0 .
 

losthyway

Senior Member
Apr 22, 2012
100
29
Minnesota
I just installed the firmware file VZWm8LfirmwareTWRP.zip and my phone still says Android 4.4.2? WHY is that? btw I have VenomOne Rom installed and plane on upgrading the Rom to 4.3.0.... Do I now have the newest firmware?


But in my fastboot it has this info:

CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5
eMMC-boot 2048MB
Feb 3 2015,21:50:28.0 .
You are good to go. 442 is what your rom is based on not the firmware.
 
  • Like
Reactions: smokawhat

Cremnomaniac

Senior Member
Jun 10, 2013
66
5
San Jose
Noob question -
The links in the OP provide separate downloads for KK 4.4.4. Can those be added to a single zip and flashed as a single file?
I'm on 4.42, and have decided which firmware I need (per ROM) but I do want to upgrade to 4.4.4. I'll probably use the FUU 4.4.4 to update initially, but I'd like to have the backup firmware.
thanks for all the great work
 

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Noob question -
The links in the OP provide separate downloads for KK 4.4.4. Can those be added to a single zip and flashed as a single file?
I'm on 4.42, and have decided which firmware I need (per ROM) but I do want to upgrade to 4.4.4. I'll probably use the FUU 4.4.4 to update initially, but I'd like to have the backup firmware.
thanks for all the great work
Not sure what you're asking, but you probably mean this?
http://xdaforums.com/showthread.php?t=2914914

dottat also has one for LP - in case you don't want to lag behind on KK firmware and rom ;)
 
  • Like
Reactions: Cremnomaniac

Cremnomaniac

Senior Member
Jun 10, 2013
66
5
San Jose
Not sure what you're asking, but you probably mean this?
http://xdaforums.com/showthread.php?t=2914914

dottat also has one for LP - in case you don't want to lag behind on KK firmware and rom ;)

berndblb thanks for trying to decipher my post, your link is the thread I refer to when I said "I'll probably use the FUU 4.4.4 to update initially", meaning the DOTTAT_VZWM8_S_OFF_4.4.4_FUU.zip.

What I'm asking is, if I decide to reflash 4.4.4 firmware at anytime, and rather than redoing the entire FUU above, can I put -

4.4.4 STOCK RECOVERY
BOOT.IMG 4.4.4
4.4.4 FIRMWARE ZIP (NO BOOT.IMG OR RECOVERY)
http://xdaforums.com/showthread.php?t=2723159

All of the above, into a single zip to be flashed as a complete firmware package? Maybe I'm asking something I don't need to worry about.
I anticipate flashing a ROM that will need the Lollipop firmware. But if I want to go back to a 4.4.4 firmware ROM, I just wanted to have a firmware only zip with everything in it. I haven't come across one. But, do I even need it, dunno.
Am I making sense? Understanding the firmware options, I'm a bit over my head.
 
Last edited:

berndblb

Inactive Recognized Contributor
Nov 22, 2012
4,875
2,113
Los Angeles, CA
Ah ok, I think I get what you are asking. But I think there is no need for it.
If you want to switch between LP and KK firmwares there is no need to replace your custom recovery and the boot image is going to change anyway with the rom you flash. So why flash them at all?
If you wanted to go back to stock you got dottat's FUU.
If you want to change firmware you got Tigerstown's stand-alone firmware packages.
What's the scenario where you would want to flash just firmware, stock recovery and the stock kernel (which will get replaced anyway when you flash a rom)?
 

cntryby429

Senior Member
Aug 27, 2013
658
258
Washington D.C.
how do you flash the radio only? I tried flastboot flash radio filename.zip both in RUU(zip) and in recovery (img). no dice.

What is the proper command and which mode to be in, ruu or recovery?

I already pointed you to the thread with the answer in your duplicate post in the q/a forum.
http://xdaforums.com/showthread.php?t=3188231 how to flash radio only
If you are opposed to flashing the files as he provided them in RUU mode then you could always dig into the files within the zip and learn how it's done with fastboot.

Edit, link to my first answer didn't work for some reason.
 
Last edited:
  • Like
Reactions: kerryh420

kerryh420

Account currently disabled
Dec 19, 2013
137
5
47
Usa
cutt.ly
Dunno why it didn't work for me the first time z ruu mode.... Must have been syntax error. But the first time I did try flashing an older radio whereas this time I flashed the current 5.0.1 radio...

Do you happen to know the method of nomenclature for htc? For example : 4.16.401.10.
I know that the 401 refers to device or carrier... What about the rest?
 

genious_t

Senior Member
Nov 27, 2007
114
4
Karachi
I tried this firmware on my LRA (LTE Rural America) version of the M8, and ended up without a phone connection. I was able to get it working again with some help.

I didn't test this, but it seems that the rc_data.img from Verizon is not that same as the local LRA carriers. Again, this is untested but aside from rc_data.img, slb*.img and wcnss.img the other files seem to match up. You might be able to flash the firmware listed here if you remove rc_data.img from the zip.

Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-main: 3.31.512.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__001
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

hi
how did you get it working? i am in the same situation, stuck with no connection, also having one more issue that i am only able to flash verizon or aosp rom and that too reboot after every few minutes. can you please help and provide me the firmware needed to get my connection issue fixed.

thank you
 

genious_t

Senior Member
Nov 27, 2007
114
4
Karachi
I tried this firmware on my LRA (LTE Rural America) version of the M8, and ended up without a phone connection. I was able to get it working again with some help.

I didn't test this, but it seems that the rc_data.img from Verizon is not that same as the local LRA carriers. Again, this is untested but aside from rc_data.img, slb*.img and wcnss.img the other files seem to match up. You might be able to flash the firmware listed here if you remove rc_data.img from the zip.

Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-main: 3.31.512.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__001
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Hello,

i have the same device as yours, flashed the wrong firmware and now ended up with no signals, IMEI = null and baseband = unknown under settings > about

if you still have that phone in working condition can you please help me with some partition dumps
 

durgis

Senior Member
Feb 12, 2010
184
41
Hello,

i have the same device as yours, flashed the wrong firmware and now ended up with no signals, IMEI = null and baseband = unknown under settings > about

if you still have that phone in working condition can you please help me with some partition dumps

Unfortunately I don't have the M8 any longer, and I've changed laptops since then too so I no longer have access to the original firmware for that device. Sorry, I wish I could help more.

You might want to contact one of the LRA carriers and see it they can provide it for you. A quick search came up with these that list some carriers.
http://vzwmidwestarea.com/lte-in-rural-america-program-helping-expand-4g-availability/
http://www.verizonwireless.com/news/article/2013/09/4g-lte-rural-america-program-alaska.html
 

Tydeker

New member
Mar 4, 2016
3
0
I have a Verizon unlocked m8 , but I have t-mobile. The phone is stock, and I don't really feel like doing the work to root my phone, so I was wondering if there is a way to update my firmware from my 4.4 to the latest 5.0 and (hopefully) soon 6.0 without root or custom recovery s-off etc. Don't have access to a Verizon SIM either.
 

mannyelite

Senior Member
Oct 20, 2014
236
124
I have a Verizon unlocked m8 , but I have t-mobile. The phone is stock, and I don't really feel like doing the work to root my phone, so I was wondering if there is a way to update my firmware from my 4.4 to the latest 5.0 and (hopefully) soon 6.0 without root or custom recovery s-off etc. Don't have access to a Verizon SIM either.

Have you tried on a PC using HTC sync? I was able to update my VZW m8 on a different carrier that way..
 

Top Liked Posts

  • There are no posts matching your filters.
  • 153
    Current firmware zip will always be posted at top of OP. So if you are wondering what file is the new one this will solve that. All other files current an past will be in the downloads section in post #2

    5.0.1 FIRMWARE(no boot.img or recovery.img I removed those 2 images so you can upgrade firmware on any rom your running

    IF you are using TWRP use this one as it included the latest TWRP which is mandatory for new firmware. Failure to comply will lead to possible bricking!

    :good:https://www.androidfilehost.com/?fid=95916177934537898:good:

    CWM users can use the following which contains no recovery.img

    :good:https://www.androidfilehost.com/?fid=95916177934537415:good:

    Want to remove your red warning message on boot then check my other thread out here http://xdaforums.com/verizon-htc-one-m8/development/mod-t3047228


    Current numbers

    Android 4.4.4
    CID-VZW__001
    HBOOT-3.19.0.0000
    RADIO-1.09.20.926
    OpenDSP-v46.2.2-00564-M8974_FO.0811
    OS-3.28.605.4
    eMMC-boot 2048MB
    Sep 30 2014,01:16:07.0

    Android 5.0.1
    CID-VZW__001
    HBOOT-3.19.0.0000
    RADIO-1.12.20.1211
    OpenDSP-v47.2.2-00564-M8974_FO.1024
    OS-4.17.605.5
    eMMC-boot 2048MB
    Feb 3 2015,21:50:28.0 .

    You can check an compare yours to these to see if your up to date. It is a must you only check for these on your phone in the bootloader


    Also here is a video that was posted that shows how to update via this process.

    http://m.youtube.com/watch?v=e21qb7iZAOo&feature=youtube
    Big thanks to @owenbeals

    There is no need to rename the file just leave it as is so you don't rename it an then get error can not open file because you didn't rename it correctly. A lot of people seem to think they have to rename the file to firmware.zip which isn't correct at all

    Instructions

    Download firmware zip
    reboot your phone to bootloader
    Place your firmware zip in your fastboot folder
    Open CMD terminal on pc in your file you fastboot from.
    Plug phone into pc
    In terminal first cmd you need is
    Fastboot oem rebootRUU
    fastboot flash zip nameofyourfile.zip
    It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
    fastboot flash zip nameofyourfile.zip

    Once all is good on your end an your ready to reboot phone use this final cmd

    Fastboot reboot-bootloader



    All stand alone radios can be found here

    Credit to dottat for 4.4.3 firmware zip
    [/CENTER]
    24
    Vzw lollipop is out once I get ota ill upload firmware rt away.

    Sent from my ADR6425LVW using XDA Free mobile app
    21
    Firmware Flashing - How to avoid getting hung at boot on 4.4.4 based roms

    Firmware Upgrading Announcement:

    Using the SD card method is certainly easy, however it is causing issues that I don't wanna deal with, and I'm sure other devs do not want to deal with and YOU the user will also not want to deal with.

    So please read!

    Explanation:

    Using fastboot mode to flash the firmware, requires you to do a "reflush" of the firmware.
    See my instructions in the OP for fastboot method to see what I am talking about, when I say reflush.
    Basically you do the fastboot flash zip firmware.zip command twice.
    The reason for this, is that some firmwares require it. (our 4.4.4 update does!)
    First it loads important files from the zip that will enable the rest to properly install during the reflush/reflash step.
    Then it will say that part of the process failed and to reflush.
    Then you issue the command a second time, and the device reboots and flashes the firmware zip a second pass.
    This reboot happens so that the first files it flashed, can actually be loaded, in preparation for the rest of the files it flashes in the second pass.
    After it flashes for the second time, you will see success in the command prompt/terminal.
    Then you know you have flashed the entire firmware package in its entirety.

    When doing the SD card method, you are only getting the first pass of files, as you do not see or know that a second pass is needed.
    This will cause you to hang at the splash screen after flashing a new 4.4.4 based rom.
    You will think it's the rom, since you "thought" you flashed the new firmware.
    It's possible, but I cannot confirm, that doing the SD card method twice in a row, would serve the same purpose as doing the "reflush" in terminal.
    But since I can't say that for sure and I know the fastboot method works without a hitch, that is what I am suggesting folks do.
    If you absolutely cannot access a computer and use fastboot, you should at the very least, do the firmware flash twice from your SD card, in hopes that doing so will flash all the files and prevent you from not booting on 4.4.4 roms.

    This is pretty critical, as it may help prevent me and others from reading reports over and over and over again, about flashing a 4.4.4 rom and getting hung at the splash screen.
    So I hope everyone reads this and understands what I am saying and takes the advice I am giving.
    As that's about all I can do at this point to try and avoid these issues from here on.
    This will save me, other devs, and most importantly YOU from having headaches after updating...

    Thanks for taking the time to read this announcement and Happy Flashing!
    19
    There is no need for concern flashing a new hboot, as long as you are already s-off.
    The full firmware does include the stock recovery though.
    I would just flash the one without the Boot.img/recovery...
    Will post an updated NoRedText hboot and Faux Locked hboot later as well.
    15
    First of all thanks to the guy of the OP and for the files..
    Second I'm confused as hell lol.
    So I'm a strong believer of there's no such thing as a stupid question...
    My question is.. Can I update the firmware as it is on the OP when I'm running Skyfall (latest)?
    will it be safe to flash is as it is or is it necessary to delete hboot or any other file that could break root or S-OFF??

    Thanks in advance and excuse my confusion.. I been reading the whole thread and between some Yes and some No and blah blah I don't even know...

    Flash as is, no need to do anything to it.
    It will not break root.
    It will not break s-off.
    It will not wipe device.
    It does not contain the stock recovery(was removed)
    It does not contain the stock boot.img(this is the kernel and ramdisk), as that won't work for many roms and most people are running custom roms with custom kernels.
    Flashing the stock secure boot.img with write protection enabled is not what most users will want.
    So those two items are often removed from uploaded firmware zips(I always do).
    It will not change your rom.
    It will not clean your room.
    It will not eat your dog.
    It will simply update your firmware which includes the new hboot, radio, modem related data and files, touchscreen driver, adsp and other misc firmware.
    So it is safe to flash as is on pretty much any and all current roms. Sense or Aosp, doesn't matter, 4.4.2, 4.4.3, 4.4.4.
    :good: