There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
TekGnosis said:
There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
Click to expand...
Click to collapse
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
bacon612 said:
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
Click to expand...
Click to collapse
I have all of the ruu in one thread which is stickied in the general section.
dottat said:
I have all of the ruu in one thread which is stickied in the general section.
Click to expand...
Click to collapse
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
bacon612 said:
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
Click to expand...
Click to collapse
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
dottat said:
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
Click to expand...
Click to collapse
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
bacon612 said:
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
Click to expand...
Click to collapse
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
dottat said:
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
bacon612 said:
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
Click to expand...
Click to collapse
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
bacon612 said:
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
Click to expand...
Click to collapse
Yeah. That's always been the old standby as it sets the nv golden config back.
Sent from my HTC6535LVW using Tapatalk
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
bacon612 said:
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
Click to expand...
Click to collapse
You can use a Java Card to S-OFF your M8 - check out the Verizon M9 Java Card thread.
(@dottat has one, he is my recommendation - but all are very trustworthy and if someone is closer it may be easier on you to go with them)
Been having this issue myself. Tried RUU, flashing all radios from 4.4.2 on up, factory reset, etc. I'm only getting 3G-- not LTE whatsoever. Any ideas?
Edit: Got a new SIM-- no cigar. Unless there are some network settings that I don't know about, the 4G antenna might just be broken or something
dottat said:
Factory reset on stock recovery now?
Click to expand...
Click to collapse
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
meskibob said:
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
Click to expand...
Click to collapse
It's not possible to lose s-off? Did you turn it on yourself?
Sent from my Nexus 6 using Tapatalk
dottat said:
It's not possible to lose s-off? Did you turn it on yourself?
Click to expand...
Click to collapse
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
meskibob said:
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
Click to expand...
Click to collapse
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Sent from my Nexus 6 using Tapatalk
dottat said:
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Click to expand...
Click to collapse
Sorry for the confusion, and thanks again!
No dice. On any of these fixes. I've gone through all the RUUs that dottat has posted, full back to stock (with root /s-off). I'm at a complete loss. Does anyone have any other suggestions to try and get this fixed?
After I flashed on of the RUUs I have 4G for about 10 mins, then it bumps back down to 3G. I've checked this in three different cities (Home, Work, Friends) so its not the network in my area. I was thinking of stopping at Verizon, maybe get a new SIM, but I'm not sure if that would work.
Related
Hey Guys! I recently picked up the HOX after three solid years on the Captivate. The rooting/flashing experience has been more difficult thus far but the device is pretty friggin' sweet. I unlocked and rooted with minimal issues and went to the latest CM10 nightly out of the gate. No issues were encountered at least during boot up. Once up and running however, the only network available is EDGE. I searched around and found posts in other device forums stating this is due to corrupt/missing IMEI. Did not see anything about this for the dual core HOX. I checked the ATT APN details and they matched what people were posting around. The IMEI is correct in the about phone->status info. Available networks shows ATT and US only. If I try to manually select ATT, it states it cannot reach this network at this time. So it appears I am lost at the moment. Should I reflash CM10? or start over at stock? Any feedback would be greatly appreciated.
do you have at&t branded evita? what radio, hboot and base is on your phone?
DvineLord said:
do you have at&t branded evita? what radio, hboot and base is on your phone?
Click to expand...
Click to collapse
Yes, it is AT&T branded. This is the info listed on the bootscreen:
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
About phone lists the Baseband as: 0.19as.32.09.11_2_10.105.32.25L
radaghast196 said:
Yes, it is AT&T branded. This is the info listed on the bootscreen:
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
About phone lists the Baseband as: 0.19as.32.09.11_2_10.105.32.25L
Click to expand...
Click to collapse
i have same. i see ups and downs from build to build and rom to rom sometimes specially lately with 4.2.x. usually i toggle airplane mode and it fixes the problem for awhile, but i've never been stuck on edge unless it was a build my phone really didn't like. what gapps are you using? are you using stock kernel? are you s-off?
DvineLord said:
i have same. i see ups and downs from build to build and rom to rom sometimes specially lately with 4.2.x. usually i toggle airplane mode and it fixes the problem for awhile, but i've never been stuck on edge unless it was a build my phone really didn't like. what gapps are you using? are you using stock kernel? are you s-off?
Click to expand...
Click to collapse
I flashed a gapps-jb-20121212-signed version. Stock CM kernel and left it s-on. The instructions I was following did not mention adjusting this, so I left it alone. Would it be a potential starting point you think? I tried the airplane mode after each reboot, but EDGE only sadly. I tried different APNs, but again EDGE only.
radaghast196 said:
I flashed a gapps-jb-20121212-signed version. Stock CM kernel and left it s-on. The instructions I was following did not mention adjusting this, so I left it alone. Would it be a potential starting point you think? I tried the airplane mode after each reboot, but EDGE only sadly. I tried different APNs, but again EDGE only.
Click to expand...
Click to collapse
try gapps-jb-20121130-signed.zip
DvineLord said:
try gapps-jb-20121130-signed.zip
Click to expand...
Click to collapse
Done. Still no joy though. It did take several minutes before it found a network but still living on EDGE.
well, by now i'd say try another rom. or ruu back to stock and see if your phone has issues. or you might need a new sim.
I don't really have a solution for you but you're not alone. I was having a lot of issues with my phone dropping its data or telling me there's not SIM in it.
DvineLord said:
well, by now i'd say try another rom. or ruu back to stock and see if your phone has issues. or you might need a new sim.
Click to expand...
Click to collapse
Understood. I think I'll RUU back to stock. Just to be clear, I came from 2.20 firmware. Do I need to fallback to the same version coming from CM10? Or can I use 1.85?
Found a thread on RUUs, looks like it recommends staying at your version minimum. Grabbed a copy of the 2.20 RUU but my comp won't even run the thing. Locks the joint up before it even prompts for step 1. Bad download maybe?
it takes awhile for ruu to load. i use winxp and don't bog my computer down with crap like "most" people.
those are the download links and md5 sums for 1.85 and 2.20
http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe 63d903db858667b82b5186456d0039c1
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe a40cd830e8c57109d140e1e68e2d1328
DvineLord said:
it takes awhile for ruu to load. i use winxp and don't bog my computer down with crap like "most" people.
those are the download links and md5 sums for 1.85 and 2.20
http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe 63d903db858667b82b5186456d0039c1
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe a40cd830e8c57109d140e1e68e2d1328
Click to expand...
Click to collapse
Turned out the issue was hard drive space. Dumped a buncha old albums onto an external drive and the RUU completed its run successfully. Sadly there was no change in the issue. The device remains on EDGE and I'm stuck with crummy Sense. Very deflating.
if you have an at&t evita and you are on at&t i think your problem is your sim card.
I'll attempt to get a new sim tomorrow. The office did do a "reset" on the sim but there was no change to the service. I did notice in the boot menu the S/N is different than what is listed on the sticker located on the back of the phone. Is this usually the case? or a sign of a potential conflict?
Tried a couple of different SIM cards at the office and remained on EDGE at all times. Tried the same card in a new HOX and it gained access to the 4G network with alacrity. So issue appears to be device related. Almost as if the ATT network denies the phone access to the HS networks. Possible conflict somewhere?
I recently ran the bell ruu on my phone for my 1.08 hboot which reinstalled the stock Rom for my phone which worked well. I then did the ota update which updated my phone to 2.15 hboot and 3.16.666.9 version (jb) and now the signal keeps switching between no signal and near full strength. Please help.
Sent from my baked HTC One S
Fredfly said:
I recently ran the bell ruu on my phone for my 1.08 hboot which reinstalled the stock Rom for my phone which worked well. I then did the ota update which updated my phone to 2.15 hboot and 3.16.666.9 version (jb) and now the signal keeps switching between no signal and near full strength. Please help.
Sent from my baked HTC One S
Click to expand...
Click to collapse
Shouldn't pose a problem with stock OTA though.
Have you S-OFF'ed previously
Sent from my HTC One S using Tapatalk 4 Beta
I have not s-offer before. I only did the ota to acheieve moonshine s-off. Now I have done the s-off and tried several radios and Roms with no luck. If I pull the SIM card I can get signal back for a minute or two before it goes back to no service
Fredfly said:
I have not s-offer before. I only did the ota to acheieve moonshine s-off. Now I have done the s-off and tried several radios and Roms with no luck. If I pull the SIM card I can get signal back for a minute or two before it goes back to no service
Click to expand...
Click to collapse
Maybe the S-OFF has got something to do with it.
Sent from my HTC One S using Tapatalk 4 Beta
Well the problem appeared after the ota and I s-offed later thinking that I would be able to fix the problem with s-off. I have a feeling its my hboot being too high (2.15) but was reading that downgrade after the ota causes brick for some.
Sent from my baked HTC One S
Fredfly said:
Well the problem appeared after the ota and I s-offed later thinking that I would be able to fix the problem with s-off. I have a feeling its my hboot being too high (2.15) but was reading that downgrade after the ota causes brick for some.
Sent from my baked HTC One S
Click to expand...
Click to collapse
If you have applied Moonshine S-OFF, it installed HBOOT 2.15.4444 ... Don't know but it might be related to the signal issue. You can confirm from the relative thread.
did this problem ever get fixed?
Still haven't been able to figure it out. I have since tried ruu's and hboot downgrades and tried all radios and multiple roms. Broke down to calling Bell who told me to buy a new sim card. After using a strangers phone to activate the sim card because it my only phone, i got the sim activated but the phone kept dropping signal. I called back Bell and they said they will report it and then they gave me HTC's number. I called HTC and they asked me to go into recovery; having a custom recovery at the time made me have to admit that i had an unlocked bootloader. They suggested i send in the phone for repair. The guy on the phone told me to just relock the bootloader and flash the stock rom and they will still lock at it. He even remarked that they have fixed some phones with unlocked bootloaders and custom recovery's. I will report back when i hear from HTC about the repair estimate.
Got the estimate for the phone and it will cost 250$ to fix. They told me that the main board and the battery are broken. O have since denied the repair since I can't afford that. Now I am forced to use my old Samsung T746. Ps they did t care that I was s-offend.
Sent from my HTC One S using XDA Premium 4 mobile app
Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?
Yeah that's the one you need.
Sent from my MID-1040
Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk
No problems.
Sent from my MID-1040
timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita
timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012
The latest RUU is probably your best bet.
Sent from my Evita
timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.
deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.
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!
Hi,
I can't seem to get any signal, can't call text or use data on my HTC desire 620. But it is finding the networks as when I search to select networks it can find O2 (I'm on giffgaff. And it claims to have registered on network. I've refreshed back to stock,but I don't know where to go from here.
Do I need to reflash the radio.img? If so how would I go about doing that? I've searched allover but can't find the file online.
Thanks
Sent from my X98 Air 3G(C9J7) using Tapatalk
Jessooca said:
The easiest way to fix your issue is to factory reset it, if that doesn't work, then restore your phone entirely using the stock files, IF that isn't something you want to do then yes, flash the radio and flash the modem as well. It can't hurt.
In most cases just start back at square 1; going entirely back to stock. In so many cases that will fix your issue the fastest.
-Jessica
Click to expand...
Click to collapse
Thanks for the reply,
I've flashed the stock rom already, but that didn't seem to fix it.
But I read somewhere that flashing a stock rom doesn't actually flash the radio or modem, just the system, boot and recovery.
In which case do you know where I could find a download for the modern and radio?
Thanks
Jessooca said:
Well if you want to be certain you have your phone entirely back to stock...
Factory reset the phone.
Power it off, and reflash the stock files
Flash the modem and radio
Once it powers back up factory reset it again
Let me know what happens after that, I'll look into your particular HTC so I can help you fully this evening, Get back to me after you've done the above again, even if you've already done it already.
Click to expand...
Click to collapse
I've flashed and reset everything except the modem and radio, as I'm still searching for the files. Is there anyone with this device who could upload their's. It is the HTC desire 620, unlocked from H3G (Three).
Jessooca said:
Well if you want to be certain you have your phone entirely back to stock...
Factory reset the phone.
Power it off, and reflash the stock files
Flash the modem and radio
Once it powers back up factory reset it again
Let me know what happens after that, I'll look into your particular HTC so I can help you fully this evening, Get back to me after you've done the above again, even if you've already done it already.
Click to expand...
Click to collapse
Right I finally found the radios, modems etc on IR File, and have flashed them all, along with stock roms. Then have done factory resets, the lot. But I'm still having the same issue. Any suggestions.
Hi,
It's an HTC Desire 620 (the single sim version) aka HTC A31_UL
UK version
Its S-on (can't find a way to get s-off :'()
Hboot 3.19.0.0000
Radio-00.03.013_U10012131_41.09.0423
OS-1.50.771.2
Bootloader Unlocked
Unrooted :'(
First registered May 8th 2015
I'm running all the latest htc updates
If you need any other details just let me know, I appreciate the support
Thanks
Sent from my X98 Air 3G(C9J7) using Tapatalk
Jessooca said:
Hmmm, that's odd.
What's your device model (country as well; us version? India? Etc) what's the latest firmware and boot loader you know you were on?
Have you flashed all of the latest updates for your phone? I ask because if you've updated and you're using a previous version to try to fix your phone, that will not work.
Let me know all the pertinent details about your device and firmware/bootloader so i can provide a bit of better assistance
Thanks
Click to expand...
Click to collapse
..
I still haven't solved the issue. Anyone got any ideas???