anyone else notice this rom is a little buggy. I have to turn on airplane mode when switching from wifi to mobile data most of the time
[3-15-15][firmware][all stock img]All files have updated to Lillipop
- Thread starter Tigerstown
- Start date
-
- Tags
- development
dottat
Retired Forum Moderator
Flashing the firmware via HBoot doesn't need to be flashed twice (reflush like on adb)? I'm debating on whether or not to try the new DH ROM but flashing the 5.0 firmware has me skeptical lol. I know 4.4.4 is official and 5.0 is a mock up to make Wi-Fi work.
Flashing via hboot led to a lot of problems with the 4.4.4 firmware update. That's why it's not in the OP and nobody recommends it anymore. Worked just fine for me though...
You be the judge if it is advisable...
lol i meant this firmware
ive tried it with 3 different roms and i need to turn airplane mode on and off on all of them.
Yeah unfortunately I have the same problem. There is a fix for this here:
http://xdaforums.com/verizon-htc-on...andoff-fix-t2868778/post55269814#post55269814
I'm to the point that I'm about to try this. I didn't want to alter the way the radio handles the 4g to 3g hand off and what not because I simply want it to work the way it is supposed to. There was some other talk around the forums that mention doing a factory reset with a stock recovery because it is supposed to rewrite the NV partitions which apparently don't get touched with a normal factory reset/wipe with a custom recovery. I was about to try that as a last resort before doing this fix but after reading of many attempts from other people with no luck at fixing the problem, it just seems a lot of trouble with little hope of solving this issue. I would really like to simply understand why this is happening....what exactly is causing this problem for so many people and not for others. It's so frustrating because it was working just fine up until 4.4.4 and now it doesn't matter what radio I flash, I still have to toggle airplane mode to make it go away.
Hello buddies, I need your help
I'm quite new to HTC so don't be hard, if I don't know much about the different firmwares and methods/workarounds how to get a ROM working on the device.
The last months I was running my European GSM version as GPE and now I want to try another ROM... like Clean ROM..
Will I be able to flash this firmware (3.28... from this thread?)
My phone has SuperCID and is S-Off... Thanks in advance. If you know a webpage / tutorial / video what ever where the most important basics about "flashing a HTC-device" are shown, please let me know.
Thanks in advance.
Martin
I'm quite new to HTC so don't be hard, if I don't know much about the different firmwares and methods/workarounds how to get a ROM working on the device.
The last months I was running my European GSM version as GPE and now I want to try another ROM... like Clean ROM..
Will I be able to flash this firmware (3.28... from this thread?)
My phone has SuperCID and is S-Off... Thanks in advance. If you know a webpage / tutorial / video what ever where the most important basics about "flashing a HTC-device" are shown, please let me know.
Thanks in advance.
Martin
Hello buddies, I need your help
I'm quite new to HTC so don't be hard, if I don't know much about the different firmwares and methods/workarounds how to get a ROM working on the device.
The last months I was running my European GSM version as GPE and now I want to try another ROM... like Clean ROM..
Will I be able to flash this firmware (3.28... from this thread?)
My phone has SuperCID and is S-Off... Thanks in advance. If you know a webpage / tutorial / video what ever where the most important basics about "flashing a HTC-device" are shown, please let me know.
Thanks in advance.
Martin
If you phone is Vzw HTC m8 you can flash this firmware.
Verizon HTC M8, S-Off, TWRP, running Viper 1.8 for months now, 4.4.2 bootloader. I'm trying to update to 4.4.4, but it's not working. I downloaded the file from the OP (3.28.605.4-firmware.zip), followed the instructions on the video, rebooted and it still shows that I'm 4.4.2. I tried this about 6 times, same thing. Do I need to go to 4.4.3 first?
I even removed the SDK from my computer and downloaded a fresh install. Still no go. Any suggestions?
I even removed the SDK from my computer and downloaded a fresh install. Still no go. Any suggestions?
Well that's your problem. That is the info your ROM is based off....in the OP I put when checking to see if update went thru you must be looking in bootloader. Reboot there an check your numbers out an see if your updated all the way...
Well that's your problem. That is the info your ROM is based off....in the OP I put when checking to see if update went thru you must be looking in bootloader. Reboot there an check your numbers out an see if your updated all the way...
thanks, I completely missed that! my bad. One thing though, my OS doesn't show what you have, it just says "OS-" with no numbers after. I haven't flashed a 4.4.4 based ROM yet.
Sounds like you r using a old twrp which had the no os bug. What twrp r you running?
V2.7.0.2.....ya, haven't updated that one
Update that an you will be all set.
?
I am running clean rom 1.3 was waiting to update but now that scott has left the M8 would it be safe or ok to update to 4.4.4 and stay on 1.3 till I find a rom I would like thanks in advance
I am running clean rom 1.3 was waiting to update but now that scott has left the M8 would it be safe or ok to update to 4.4.4 and stay on 1.3 till I find a rom I would like thanks in advance
You should have no issues upgrading firmware an staying on that ROM till you find a 4.4.4 Rom you like.I am running clean rom 1.3 was waiting to update but now that scott has left the M8 would it be safe or ok to update to 4.4.4 and stay on 1.3 till I find a rom I would like thanks in advance
I can reboot my phone into the boot loader with adb, but once I get there I can't run further commands. I don't see my phone in adb devices either after that. anyone know what I can do? I'm using a mac and htc sync manager as my drivers
Similar threads
- Locked
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://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]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:
