Running the 4.4.2KK and the radio still seems to suck compared to 4.4? Is it just me? Is anyone going back to try the .17, 4.4 radio on 4.4.2?
mattfox27 said:
Running the 4.4.2KK and the radio still seems to suck compared to 4.4? Is it just me? Is anyone going back to try the .17, 4.4 radio on 4.4.2?
Click to expand...
Click to collapse
You're not the only one, quite a lot have noticed it too, myself included. Just no one has provided any solid instructions/links to flash the radio back for those that don't dabble in this sort of stuff on a daily basis.
mattfox27 said:
Running the 4.4.2KK and the radio still seems to suck compared to 4.4? Is it just me? Is anyone going back to try the .17, 4.4 radio on 4.4.2?
Click to expand...
Click to collapse
t0p8uzz said:
You're not the only one, quite a lot have noticed it too, myself included. Just no one has provided any solid instructions/links to flash the radio back for those that don't dabble in this sort of stuff on a daily basis.
Click to expand...
Click to collapse
4.4.1 and 4.4.2 radio are the same.
To go back to 4.4 radio, download the factory image. Open the file with any archive program and extract the file named radio*.img. Rename it to radio.img. fastboot flash radio radio.img.
I noticed the same thing and flashed back to the .17 radio. Could there be any negative side effects with using an older radio with 4.4.2?
Sent from my Nexus 5 using Tapatalk
.2 radio is slightly better/more consistent than 4.4 for me. Very pleased
NX5
Im on 4.2.2 and flashed .17 because it's better for me.
Sent from my Nexus 5 using Tapatalk
No its the crappy antenna they used to save costs
Sent from my Nexus 5
Fire Ball said:
I noticed the same thing and flashed back to the .17 radio. Could there be any negative side effects with using an older radio with 4.4.2?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, keep it if it works better 4 u.
Ya I'm back on the .17 radio...gonna take it for a spin on the town tonight.
Sent from my Nexus 7 using Tapatalk 4
I've heard from a few people that .15 is even better than .17.
t0p8uzz said:
You're not the only one, quite a lot have noticed it too, myself included. Just no one has provided any solid instructions/links to flash the radio back for those that don't dabble in this sort of stuff on a daily basis.
Click to expand...
Click to collapse
Not so complicated really.
http://forum.xda-developers.com/showthread.php?t=2514095
Go there and read some.
If you have a custom recovery then download the ZIP file. If you have the normal recovery (meaning you haven't modified your phone at all) then download the IMG file.
KRT16M was the standard 4.4 modem (.17).
So once you have that you have to setup ADB (google it) and then flash the modem to your phone by putting your phone in bootloader mode (google it) and then type:
fastboot flash radio MODEMNAME.img
Make sure you put the file you download in the same folder as fastboot from ADB and you'll be all set.
shotta35 said:
Not so complicated really.
http://forum.xda-developers.com/showthread.php?t=2514095
Go there and read some.
If you have a custom recovery then download the ZIP file. If you have the normal recovery (meaning you haven't modified your phone at all) then download the IMG file.
KRT16M was the standard 4.4 modem (.17).
So once you have that you have to setup ADB (google it) and then flash the modem to your phone by putting your phone in bootloader mode (google it) and then type:
fastboot flash radio MODEMNAME.img
Make sure you put the file you download in the same folder as fastboot from ADB and you'll be all set.
Click to expand...
Click to collapse
Doesn't work. Looks like the boot loader must be unlocked for the ADB fastboot way to work. I get FAILED (remote: not supported in locked device)
richport29 said:
Doesn't work. Looks like the boot loader must be unlocked for the ADB fastboot way to work. I get FAILED (remote: not supported in locked device)
Click to expand...
Click to collapse
This is correct you need to have an unlocked bootloader to Flash the radio.img via the bootloader. Unlocking the bootloader will wipe your device.
jdawg0024 said:
This is correct you need to have an unlocked bootloader to Flash the radio.img via the bootloader. Unlocking the bootloader will wipe your device.
Click to expand...
Click to collapse
Decided to do it. And the result, well worth it. I went with the .15 radio and the improvement over .23 is significant. I went from barely having a LTE connection (1 bar dropping to no connection, 110-115db) to (1-2 bars -100db-105db). Very pleased.
Its the hardware, not the radio. I've tried the 4.4 and 4.4.2 radio. My Nexus 5 consistently gets 3-6dbm less than my Moto X on LTE.
m0biusace said:
Its the hardware, not the radio. I've tried the 4.4 and 4.4.2 radio. My Nexus 5 consistently gets 3-6dbm less than my Moto X on LTE.
Click to expand...
Click to collapse
Try the .15 modem.
m0biusace said:
Its the hardware, not the radio. I've tried the 4.4 and 4.4.2 radio. My Nexus 5 consistently gets 3-6dbm less than my Moto X on LTE.
Click to expand...
Click to collapse
Not really, my signal was superb before 4.4.1 landed ... going to flash back .15 later
Flashed back to .17 radio
I kept 4.4.2, but flashed back to the .17 radio. Using T-Mobile in eastern Mass and the latest radio that came with 4.4.2 switched to HSPA+ in areas that had been solid LTE. Not good. I flashed the radio that I had originally (.17) and which gave me such superb results. Going back to my original radio has resulted in two improvements that I noted in my area. First, my known LTE connection areas are back. The radio doesn't "shift" to HSPA+ from LTE as readily. Second, the .17 radio shows consistently stronger signals from the cell towers when measured in dBm with the Network Signal Info app.
I am curious if anyone has compared the .17 radio performance to the .15 radio performance? I am pleased for now with being back on .17, so do not contemplate loading .15 unless there is consensus that .15 is that much better. Thoughts?
John
Unlocked the bootloader and flashed .17 modem back on ... going to see how it compares to .23 and make sure my signal is back to normal over the next few days, if not then i'll flash .15 on and take it from there
Appreciate your help
richport29 said:
Try the .15 modem.
Click to expand...
Click to collapse
.15 modem doesn't help either.
Related
Would it be possible to downgrade to the stock (1.04.01.09.21) radio while keeping the 2.1 ROM? I tried following the steps from http://geekfor.me/faq/flash-radio/ but the update does not seem to stick - the baseband version doe snot change after final reboot. If it's not possible to to downgrade the baseband alone, can I downgrade both ROM and baseband using the recovery bootloader? If so, a link to some sort of tutorial would be much appreciated.
Belongs in Q&A...
Not really sure why you would want to seeing as from what I've read, the newer radio increases battery life and signal strength.
But yeah you can. I just downloaded the stock radio to test it out HERE. flashed it, and it stuck for me.
kyouko said:
Belongs in Q&A...
Not really sure why you would want to seeing as from what I've read, the newer radio increases battery life and signal strength.
But yeah you can. I just downloaded the stock radio to test it out HERE. flashed it, and it stuck for me.
Click to expand...
Click to collapse
Thats not been my case. New radios have been worse in signal strength vs original stock. -80 db vs -95db. Battery like has been the same.
kyouko said:
Belongs in Q&A...
Not really sure why you would want to seeing as from what I've read, the newer radio increases battery life and signal strength.
But yeah you can. I just downloaded the stock radio to test it out HERE. flashed it, and it stuck for me.
Click to expand...
Click to collapse
Just won't stick, unfortunately - the phone reboots back into recovery bootloader about 5 seconds after the box and phone screen pops up. Did you follow the steps from geekfor.me tutorial?
Is it just my device or is it T-Mobile on edge this device is super slow loading web pages. My signal strength is always bouncing about but usually its -85dBm 15asu. Should I take the device in or am I just thinking to much. I just got the replacement.
Sent from my Nexus S using XDA App
Did you try the new radio introduced in 2.3.3?
Nope does it work with cm7? Can you link me to it?
Sent from my Nexus S using XDA App
Darrien13 said:
Nope does it work with cm7? Can you link me to it?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11661588&postcount=2596
bootloader.img and radio.img must be in your sdk\tools folder.
Boot into bootloader/fastboot mode
To flash the radio, use the fastboot command:
fastboot flash radio radio.img
select "reboot bootloader" and you should see the new version of the radio
To flash the bootloader:
fastboot flash bootloader bootloader.img
select "reboot bootloader" and you should see the new version of the bootloader
The new version numbers:
radio I9020XXKB1
bootloader I9020XXKA3
The versions that came with my phone:
radio I9020XXJK8
bootloader I9020XXJK1
Click to expand...
Click to collapse
also. if you haven't make sure you wipe dalvik/factory/cache to see if it would fix it.
its just difficult whether or not to say if your device is defective because you flashed a custom rom.
was it like this when you were on stock?
try flashing netarchy's 1.2.5 cm7 compatiable kernel as well
- Incorporate many updates from the newer 2.3.3 kernel sources,
including wifi driver updates, touchscreen updates, drivers for
future SLCD nexus-s variants, and more
Click to expand...
Click to collapse
If I wanted to would I be able to go back to the old radio
Sent from my Nexus S using XDA App
Darrien13 said:
If I wanted to would I be able to go back to the old radio
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
you can but there is no fastboot for the old radio available. it might be in the 2.3.2 OTA and you can pick it out from there but im not sure if its there since there wasn't a radio change in 2.3.2.
There wouldn't really be a reason for me to go back though right? Also I would still be able to flash, things from the bootloader?
Sent from my Nexus S using XDA App
Darrien13 said:
There wouldn't really be a reason for me to go back though right? Also I would still be able to flash, things from the bootloader?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes. flashing the updated bootloader is optional, but thats up to you. im not responsible for any bricks, i would just update both of them.
both of those two files are extracted from the 2.3.3 OTA.
there has been a great number of feedback that says that this radio definitely helps.
to figure out if your device is defective or not (it probably isnt).. return back to stock and see how it is. it could be based on your location since you are in a EDGE only area.
Thanks for your help. I put my sim in my G1 and it was even slower so I don't think it's my device
Edit:it was just like this when I restored back to stock
Sent from my Nexus S using XDA App
Darrien13 said:
Thanks for your help. I put my sim in my G1 and it was even slower so I don't think it's my device
Edit:it was just like this when I restored back to stock
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
It's most likely your area then. If you could get a backup of the old radio, you could try the new radio and see which one is better performance.
Rooted Inspire 4G running AndroidRevolution 3.2 Rom my signal strength is always very low 1 to 2 bars only. How can I make it have better signal. Very new to android.
pokeguy said:
Rooted Inspire 4G running AndroidRevolution 3.2 Rom my signal strength is always very low 1 to 2 bars only. How can I make it have better signal. Very new to android.
Click to expand...
Click to collapse
Which radio version is on the phone now? Is it Radio_12.41.60.19_26.06.04.14_M?
This is a quote from his thread:
"Using a "non matched" radio could have a negative effect on performance, battery life & signal strength."
Go to> Settings> About phone> Software version> and see what it says under Baseband version.
I am running 12.39.60.19_26.06.04.06_M
Bars mean nothing and are calculated differently between manufacturers and devices. Go by your db in settings about.
pokeguy said:
Rooted Inspire 4G running AndroidRevolution 3.2 Rom my signal strength is always very low 1 to 2 bars only. How can I make it have better signal. Very new to android.
Click to expand...
Click to collapse
Switch to Verizon... hehe, sorry, just had to...
pokeguy said:
I am running 12.39.60.19_26.06.04.06_M
Click to expand...
Click to collapse
That might be your problem. You need to flash the proper radio and you should get better signal.
Thanks for all the replies. See my problem is I don't know how to flash the radio. Ive been reading about it but seems very difficult. I've come from the ios devices that was very easy, just install the newest software and your done no need to flash this or that. I think I read if you messed up on flashing your radio it can brick your phone. Not willing to go back to ios. Loving android at the moment.
pokeguy said:
Thanks for all the replies. See my problem is I don't know how to flash the radio. Ive been reading about it but seems very difficult. I've come from the ios devices that was very easy, just install the newest software and your done no need to flash this or that. I think I read if you messed up on flashing your radio it can brick your phone. Not willing to go back to ios. Loving android at the moment.
Click to expand...
Click to collapse
Download the radio you need. It will probably be in a .zip, so open it in your favorite unzipper (I like 7zip) and pull out the radio.img file. Now go to the hack kit and find the radio folder. In the radio folder will be a PD98IMG.zip file, open this with 7zip, and replace the radio.img file that's currently there with the one you just downloaded (you can just delete the original from within 7zip, then copy/paste the new one), then close 7zip. Now redo step 5 from the hack kit (flashing the radio) and your new radio will be flashed.
If you feel comfortable that you understand this step, all you need to do is get your newly created PD98IMG.zip on your SD Card, boot to bootloader, then let HBoot start the update.
See I used the one click or step root. I don't think it was the hack kit. Anyways are you talking about unzipping it through the phone or computer?
I think some of these rooting programs/routines like Bubby's root are causing the loss of hsupa. See my post here about it: http://forum.xda-developers.com/showpost.php?p=12828255&postcount=2961
I extracted the radio.img from the PD98IMG.zip file in the \ace\tools\dngrd\ folder from the hack kit. I opened it up in a hex editor and found the version - 26.03.02.26
You can download the radio in PD98IMG.zip form from here: http://wiki.cyanogenmod.com/index.php?title=Support_Downloads#HTC_Ace
So now we just need someone whose HSUPA is not working to downgrade to this radio and see if HSUPA comes back. If it does, then you can flash to 26.06.04.14 or 26.08.03.07 from the same link above.
I am thinking you may be onto something..........
I flashed the downgrade radio. Upload speeds still slower than before I flashed the stock radio. Now I am going back to the radio I had before stock and see what happens.
darkside1904 said:
I am thinking you may be onto something..........
I flashed the downgrade radio. Upload speeds still slower than before I flashed the stock radio. Now I am going back to the radio I had before stock and see what happens.
Click to expand...
Click to collapse
This is interesting. Let us know.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Maybe you need to flash the downgraded kernel from the hack kit as well? Does anyone know if that would even work - flashing the downgraded kernel on top of a custom rom like cm7 or mui?
EvoXOhio said:
Maybe you need to flash the downgraded kernel from the hack kit as well? Does anyone know if that would even work - flashing the downgraded kernel on top of a custom rom like cm7 or mui?
Click to expand...
Click to collapse
Not a good idea. Flashing froyo kernel on a gb rom
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
lrs421 said:
Not a good idea. Flashing froyo kernel on a gb rom
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Click to expand...
Click to collapse
worst case scenario, wouldnt it just prevent android from booting up? if so, you could always put the correct kernel on the SD cad and reflash it from recovery right?
Per the hack kit thread: http://forum.xda-developers.com/showthread.php?t=952352
I believe the kernel he links to in there is the downgraded Telus kernel: http://forum.xda-developers.com/attachment.php?attachmentid=518730&d=1297824204
EDIT: I believe its the boot.img in the hack kit in he \ace\tools\dngrd\ folder as well.
Before I went back to stock I was Uploading @ 1.50Mbps. Went to stock radio because of the ROM I am on and my Upload speeds won't go over .30Mbps. Using the downgrade radio didn't help. It was a good idea.
darkside1904 said:
Before I went back to stock I was Uploading @ 1500Mbps. Went to stock radio because of the ROM I am on and my Upload speeds won't go over .30Mbps. Using the downgrade radio didn't help. It was a good idea.
Click to expand...
Click to collapse
I had the exact same issue. Like I said re-rooting fixed the issue for me. I was thinking that loading the downgraded radio would fix it, but maybe you need the downgraded kernel as well?
did you confirm it was the downgraded radio in "about phone"
Yeah, that was the first thing I did. Check to make sure the radio flashed correctly. I have to go put the kids in bed now. I am pretty bummed about my new slow upload speed.
darkside1904 said:
Yeah, that was the first thing I did. Check to make sure the radio flashed correctly. I have to go put the kids in bed now. I am pretty bummed about my new slow upload speed.
Click to expand...
Click to collapse
You'll have to flash back to stock and reroot to get it back
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
lrs421 said:
You'll have to flash back to stock and reroot to get it back
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Click to expand...
Click to collapse
There has to be an easier way. I can confirm that HSUPA came back for me after the downgrade, before I rooted or flashed another ROM. I've looked through the hack kit and what gets pushed to the phone during the downgrade, there's not a lot of files in there:
android-info.txt
boot.img
hboot_7230_0.85.0007_101011.nb0
radio.img
rcdata.img
recovery.img
splash1.nb0
splash2.nb0
system.img
tp_ACE_SYN3KT0108.img
tp_ACE_SYN3KW020B.img
tp_atmel224_20aa.img
tp_atmelc12_20aa.img
userdata.img
We've tried radio.img and that didn't do it, m next guess would be boot.img, which is the kernel if I'm not mistaken. I am not sure what all the other files do specifically.
I like your dedication. We'll figure this out...
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
So this guy claims to have fixed the HSUPA issue simply by reflashing the downgraded radio: http://forum.xda-developers.com/showpost.php?p=11847379&postcount=17
Maybe it's because he flashed radio.img directly instead of the PD98IMG.zip method?
I see we are still trying to figure this out???
darkside1904 said:
Yeah, that was the first thing I did. Check to make sure the radio flashed correctly. I have to go put the kids in bed now. I am pretty bummed about my new slow upload speed.
Click to expand...
Click to collapse
For a quick test, can you reboot the phone again? I know when you edit build.prop, most people say it takes two reboots for it to take effect. Maybe just for the hell of it, reboot a second time and then try another speedtest? It's probably worth a try.
lrs421 said:
I like your dedication. We'll figure this out...
Click to expand...
Click to collapse
Thanks. I got mine working but it involved going through the hack kit and losing all my data and then having to re-root and all of that. I'd love to find out what part of the PD98IMG.zip file fixed the issue, so that hopefully people can flash just that and fix their issue without losing data, re-rooting, reflashing ROMs, etc.
I am half tempted to purposely break my HSUPA just to figure out the fix but I'm not feeling that masochistic just yet.
Right now I am back to the stock radio and looking into some things. I will be back in a bit, hopefully with some info.
darkside1904 said:
Right now I am back to the stock radio and looking into some things. I will be back in a bit, hopefully with some info.
Click to expand...
Click to collapse
Cool good luck. I wish I would have caught you in time to try the second reboot. Maybe you will be brave enough to reflash the downgraded radio and then also do the downgraded Telus kernel?
I am going to read up on what all of these files in PD98IMG.zip do. Maybe the answer is in one of those other files.
So after reading up on the files some more, I now believe it could be rcdata.img, which has something to do with controlling the radio. I opened it up in a text editor and its a small file that contains a handful of line:
QCT_UMTS_RADIO_VER=1
DisH=2
HSDPACat=10
HSUPACat=6
QCT_UMTS_RADIO_END=1
That's the entire file. What I posted there is the one from the downgraded radio in the hack kit. Maybe this file needs to be reflashed in conjunction with the downgraded radio? In theory you could open up the PD98IMG.zip file that you downloaded for the downgraded radio, and then add the rcdata.img from the hack kit to the PD98IMG.zip file, and then flash PD98IMG.zip and it should flash both the radio and the rcdata.
I was experimenting my M8 with T-Mobile sim card. I flashed 5.0.1 GPE ROM and everything worked fine. I also changed its CID to T-MOB010 and flashed ViperOneM8 3.2.1. It worked fine as well. But after I reverted everything back (by loading 3.28.605.4 0P6BIMG and firmware, and restoring a TWRP backup), I discovered I can no longer get 4G/LTE signal. I can only get 3G. I tried flashing to RUU M8_VZW 4.4.3 (firmware &0P6BIMG). But it doesn't help. I dialed *#*#4636#*#* but didn't see any option/menu. When I use 4G Switcher app to select band, 1900MHz band isn't available. The network type is set to "CDMA/EvDo/GSM/WCDMA/LTE auto". I am using CleanROM 3.0. Any advise will be greatly appreciated.
HBOOT-3.19.0.000
RADIO-1.09.20.0926
OpenDSP-v38.2.2-00542-M8974_F0.0811
OS-3.28.605.4
2ndLeaf said:
I was experimenting my M8 with T-Mobile sim card. I flashed 5.0.1 GPE ROM and everything worked fine. I also changed its CID to T-MOB010 and flashed ViperOneM8 3.2.1. It worked fine as well. But after I reverted everything back (by loading 3.28.605.4 0P6BIMG and firmware, and restoring a TWRP backup), I discovered I can no longer get 4G/LTE signal. I can only get 3G. I tried flashing to RUU M8_VZW 4.4.3 (firmware &0P6BIMG). But it doesn't help. I dialed *#*#4636#*#* but didn't see any option/menu. When I use 4G Switcher app to select band, 1900MHz band isn't available. The network type is set to "CDMA/EvDo/GSM/WCDMA/LTE auto". I am using CleanROM 3.0. Any advise will be greatly appreciated.
HBOOT-3.19.0.000
RADIO-1.09.20.0926
OpenDSP-v38.2.2-00542-M8974_F0.0811
OS-3.28.605.4
Click to expand...
Click to collapse
Try a factory reset using stock recovery. Not twrp or any custom recovery. Has to be stock recovery.
Sent from my HTC6525LVW using Tapatalk
I understand completely where you are coming from. I flashed the same rom and my phone stop connecting to LTE when in global mode. I have flashed the 4.4.2, 4.4.3, and 4.4.4 RUU and went into the stock recovery and did a factory reset and it still does not work.
Right now I am running cleanrom 3.0 also. The only time I can get LTE is when I go into settings and switch it to LTE only.
The only thing I think it can be is when I do the factory reset on the RUU, the says restoring Verizon NV flash rather than formatting it. I want to try and flash a T-MOBILE RUU to see if it will format it and clear it out then switch back to Verizon but I don't know if that will brick my phone. If I can't find a way to wipe the NV the only thing else to do is run the phone over with my car a couple times then claim warranty.
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
I hope you find a fix and if you do please let me know. Good luck.
Sent from my HTC6525LVW using XDA Free mobile app
dottat said:
Try a factory reset using stock recovery. Not twrp or any custom recovery. Has to be stock recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Factory reset using stock recovery does the trick. 4G/LTE is back. Thanks a lot for the suggestion. Much appreciate it.
2ndLeaf said:
Factory reset using stock recovery does the trick. 4G/LTE is back. Thanks a lot for the suggestion. Much appreciate it.
Click to expand...
Click to collapse
No problem.
Sent from my HTC6525LVW using Tapatalk
Ruffroc02 said:
I understand completely where you are coming from. I flashed the same rom and my phone stop connecting to LTE when in global mode. I have flashed the 4.4.2, 4.4.3, and 4.4.4 RUU and went into the stock recovery and did a factory reset and it still does not work.
Right now I am running cleanrom 3.0 also. The only time I can get LTE is when I go into settings and switch it to LTE only.
The only thing I think it can be is when I do the factory reset on the RUU, the says restoring Verizon NV flash rather than formatting it. I want to try and flash a T-MOBILE RUU to see if it will format it and clear it out then switch back to Verizon but I don't know if that will brick my phone. If I can't find a way to wipe the NV the only thing else to do is run the phone over with my car a couple times then claim warranty.
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
I hope you find a fix and if you do please let me know. Good luck.
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
Please try dottat's suggestion and follow the instruction below to reset:
http://www.htc.com/us/support/htc-one-m8/howto/465049.html
It should work.
Ruffroc02 said:
Not trying to knock digital high's rom because he and several others put a lot of work into the stock 5.0 rom and I really appreciate the effort, but I wish I didn't flash it because I think there is an underlying issue with the rom that is affecting a small portion of our phones. And it is so small that there is no support to fix it. I have scoured the forum to find a fix and nothing has worked so far. But these are the problems we accept when we hack our phones and flash non factory software.
Click to expand...
Click to collapse
I'm having the LTE issue as well. I'm currently running DigtalHigh's GPE 12/18 release with the updated firmware. LTE works on first boot until I connect to my Wi-Fi network, after that I never see LTE again. I tried everything, and I mean everything. I tried the RUU back to 4.4.4 and doing a factory reset from that... I get the same result, LTE on 1st boot until the WiFi connects and then it's gone for good again until the next complete reset.
The most recent thing I tried was replacing the SIM card (while on the GPE rom)... this worked flawlessly. I had LTE again for a few days... until I made a phone call from my car using Bluetooth, at which point the phone geeked out, switching from speaker to line-out to bluetooth audio and eventually dropping my call (not sure if that is somehow related to the LTE issue), but now I'm back to no LTE again.
But I get full bars of 3G, so I've got that going for me... which is nice.
Is it possible for you to put in a new SIM while on another Rom like clean rom to see if LTE will stay?
Sent from my HTC6525LVW using XDA Free mobile app
Ruffroc02 said:
Is it possible for you to put in a new SIM while on another Rom like clean rom to see if LTE will stay?
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
DH GPE with custom firmware has hooped the VZW LTE radio settings, it has overwritten them...no amount of custom rom re-installations will fix this.
As stated above, the easiest way to fix this is to simply flash a stock Verizon RUU, and THEN do a factory reset from the stock recovery. I used http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914 with the SD card method and it worked fine.
After you do the stock factory reset you can then install DH GPE again, without using custom firmware.
Croak said:
DH GPE with custom firmware has hooped the VZW LTE radio settings, it has overwritten them...no amount of custom rom re-installations will fix this.
As stated above, the easiest way to fix this is to simply flash a stock Verizon RUU, and THEN do a factory reset from the stock recovery. I used http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914 with the SD card method and it worked fine.
After you do the stock factory reset you can then install DH GPE again, without using custom firmware.
Click to expand...
Click to collapse
I tried installing the stock ruu and using the stock recovery to fix it. It hasn't worked. Did you use the method of installing through the phone or the computer?
Sent from my HTC6525LVW using XDA Free mobile app
Ruffroc02 said:
I tried installing the stock ruu and using the stock recovery to fix it. It hasn't worked. Did you use the method of installing through the phone or the computer?
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
I put 0P6BIMG.zip in ext SD card and booted from HBOOT.
My LTE just automagically kicked back on after I reset it three weeks. Glad it doesn't have to meet the tire of my car. I pray it stays on
Sent from my HTC6525LVW using XDA Free mobile app
dottat said:
No problem.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I posed this question on another thread, but I'm trying to understand what you mean when you say "stock recovery". I know what it is, but what I don't know is what stock are you referring to; do I have to downgrade to 4.4.4 or when you mean stock it doesn't matter if it's Lollipop 5.0.1.? Thank you sir!
berrywr said:
I posed this question on another thread, but I'm trying to understand what you mean when you say "stock recovery". I know what it is, but what I don't know is what stock are you referring to; do I have to downgrade to 4.4.4 or when you mean stock it doesn't matter if it's Lollipop 5.0.1.? Thank you sir!
Click to expand...
Click to collapse
I mean the matching HTC provided recovery img for the firmware version you are on.
Sent from my Nexus 6 using Tapatalk
Boy this horse is getting beat to death. Go to Dottat's RUU posts where he explains it all. I used the 5.0.1 S-Off one. Once it's installed, boot, and then reboot to it's stock/factory recovery and do a factory reset. That will fix your 4G/LTE problem. Then you get root back and flash a "custom" recovery like TWRP. I followed the Sunshine instructions. If you don't want/need root or TWRP skip it and you'll have an S-off stock not rooted phone.
dottat said:
I mean the matching HTC provided recovery img for the firmware version you are on.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's been a few years since I wore my horse, the HD2 to death and I didn't stumble on to the cure until the wee hours this morning. It eventually comes back and like the wife hitting your head with the iron skillet...ding, ding, ding....external micros SD card and RUU; I remember how to do that. I'm S-Off, this will work. What I didn't know is what is "stock"; factory state you walked out the store with or matching the ROM to the firmware and if I'm going to downgrade to reset the NV configuration, what all that entails. It's the jargon, I need to learn and that takes time. I sincerely appreciate what the OPs do and where they direct me to; thanks!
berrywr said:
It's been a few years since I wore my horse, the HD2 to death and I didn't stumble on to the cure until the wee hours this morning. It eventually comes back and like the wife hitting your head with the iron skillet...ding, ding, ding....external micros SD card and RUU; I remember how to do that. I'm S-Off, this will work. What I didn't know is what is "stock"; factory state you walked out the store with or matching the ROM to the firmware and if I'm going to downgrade to reset the NV configuration, what all that entails. It's the jargon, I need to learn and that takes time. I sincerely appreciate what the OPs do and where they direct me to; thanks!
Click to expand...
Click to collapse
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
dottat said:
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
1droidmod said:
Well, not all brains are wired the same. I do understand providing a direct link again or now would be like defeating the purpose. Although sometimes some words in some directions or answers are misleading to One and very confusing.
Sent from my HTC6525LVW using Tapatalk 2
Click to expand...
Click to collapse
Point is the information is already out there. Nothing misleading about it.
There are some basic premises that better be understood first lest he avoid failure by leaving that boot loader locked and s on.
Capiche?
Sent from my Nexus 6 using Tapatalk
dottat said:
Answered this once already in the last 24 hours and this will be the last time.
Stock recovery is the matching HTC provided recovery img that is from the matching firmware version you are currently on. If you are on 1.X firmware it's best to find stock recovery from the 1.X ruu or firmware zip file.
Stock recovery is only provided by HTC.
Why is this so dang difficult to understand folks and why does the question need to be repeatedly posed?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Because, those of us doing the asking while we truly and sincerely appreciate the work all of you do, and believe me "I" do, some of you, not all of you completely fail at the teaching aspect of the knowledge you possess. That said, thank you very much; it worked. I can't tell you whether it was the factory reset or performing the edit inside ##778; the moment I put the wife's Straight Talk (Verizon) SIM card in; 4G LTE returned. I did not have access to the dial code until now. Again, thank you!