[3-15-15][firmware][all stock img]All files have updated to Lillipop
- Thread starter Tigerstown
- Start date
-
- Tags
- development
Scott
Retired Recognized Developer
NVM, I downloaded the zip and it doesnt have an ADSP.
Thats why you are showing HK ADSP. It never updated because it doesnt exist.
Thats why you are showing HK ADSP. It never updated because it doesnt exist.
You might be right. I did just install the firmware package that was released by dottat. I don't see an ADSP.img file in it. Do you know what the original name for that img file should be?
Just flashed the firmware via adb fastboot and it failed like stated in the op. After redoing the adb commands it went threw perfect without problems and it booted up. Time to reflash the Rom. Good looking guys
Sent from my Insanely powered M8 using Tapatalk
Sent from my Insanely powered M8 using Tapatalk
Thanks for the updates and assistance. I just flashed mine, now will flash ViperOne ROM.
It was so strange that this was the first time I flashed the firmware and it told me it Failed... no matter, re-flashed and worked like a charm!
EDIT:
Why does my OpenDSP show v38.2.2-00542-M8974.0311 ? My firmware and radio are showing the correct new versions.
It was so strange that this was the first time I flashed the firmware and it told me it Failed... no matter, re-flashed and worked like a charm!
EDIT:
Why does my OpenDSP show v38.2.2-00542-M8974.0311 ? My firmware and radio are showing the correct new versions.
Last edited:
Normally when flashing firmware you have to flash twice but it didn't ask that on 1.55 firmware that's why I stated that in the OP..
Flashed in hboot from microsd card as 06PBIMG.zip. Loaded up and ran, rebooted to hboot then finished.
Hboot is 3.18.0.0000 (has the red lettering again, of course)
Radio 1.09.20.0702
OpenDSP V38.2.2-00542-M8974.0311
OS-2.21.605.2
File date 8/7/2014.
I believe that's the nonHK version, vanilla Verizon ADSP (I never flashed that mod).
Now just waiting for the ROM devs to catch up.
Hboot is 3.18.0.0000 (has the red lettering again, of course)
Radio 1.09.20.0702
OpenDSP V38.2.2-00542-M8974.0311
OS-2.21.605.2
File date 8/7/2014.
I believe that's the nonHK version, vanilla Verizon ADSP (I never flashed that mod).
Now just waiting for the ROM devs to catch up.
Last edited:
I never did the H/K mod and my openDSP is different. Mine shows this:
OpenDSP-v44.2.2-00542-m8974_him.0314
Last edited:
Worked like a charm from my sd card. Thanks for sharing!
Sent from my HTC6525LVW using Tapatalk
Sent from my HTC6525LVW using Tapatalk
Your flashing the full firmware through hboot off the SD card? Currently on specs below, do I need to flash stock back?
HTC One M8/CM11/Excalibur 0.5
HTC One M8/CM11/Excalibur 0.5
The firmware yes. An if you flash the firmware zip posted here you should have no issues. As there is not boot.IMG or recovery in it.
Got it running via extSD method, thanks for the clarification and assistance @Tigerstown it is much appreciated.
Last edited:
Flashed new firmware, no more delay booting up. Running Viper2.4
Thanks.
Thanks.
Glad to hear my wife will be happy as she runs viper.
Mine is not working from SD. Renamed to above and entered hboot and it cycles but does not update.
HTC One M8/CM11/Excalibur 0.5
HTC One M8/CM11/Excalibur 0.5
Either you have it named wrong or its not on your root of your SD card.
No problem. You can return the favor by hitting the thanks button
thanks whore.... lol..
RUU is now up too
Btw, not sure if anyone needed or posted this in the past...
Stock VZW ADSP for anyone who flashed HK mod and wanted back without RUU.
https://www.androidfilehost.com/?fid=23622183712470135
Ran it again and it finds 06PBIMG.zip, and says wrong image. Not sure.
HTC One M8/CM11/Excalibur 0.5
Last edited:
thanks whore.... lol..
RUU is now up too
Btw, not sure if anyone needed or posted this in the past...
Stock VZW ADSP for anyone who flashed HK mod and wanted back without RUU.
https://www.androidfilehost.com/?fid=23622183712470135
I take it any way I can get it. Hehe get it rt dirty whore. Lmao downloading ruu now!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
153Current 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://forum.xda-developers.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]24Vzw lollipop is out once I get ota ill upload firmware rt away.
Sent from my ADR6425LVW using XDA Free mobile app21Firmware 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!15
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:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone