Well i am not so convinced it is the radio so much as the hardware, my original tbolt would reboot every 5 min or so no matter what. so read the forums,researched the web,talked to s friend at htc,verizon and vodafon. then i rooted it flashed different roms and radios nothing helped,along comes the official update do i reroot the phone and restore it the way i got it,set it up and let it do the ota update by itself,after 3 tries it finally took it,then a day or so later it froze so i pulled the battery booted back up once it was running started all over with the reboots every 5 min,the all at once it started to reboot all the time ,htc and verizon both said it is a known hardware failure and i got this bolt the same day ,rooted flashed,reflashed ran it to hell and back and not one reboot other than by drastic mistakes. both phones have the same chip so i would think its not a different chip but a defective series of chips, in closing i suffered the reboot problem on in the gb radio but with stock rooted ota setup.
I talked to them about it today "Verizon / HTC" and they said to do a factory reset that it fixes it, and it did. They said that it's the radio interacting with their cell towers and something glitches and it reboots. They're working on fixing the issue right now, HTC that is.
But yeah, my wifes stock phone has stopped rebooting now. We just received the phone Thursday.
Related
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.
I am having issues with the radio on EC10. After a about 10 hours the radio will turn off all by itself or just lock up. The US Cellular tech said it must be the other software on the phone that is causing it. This phone is a replacement for my original phone that the USB port stop working with the computer. My question is by updating to another radio offered in the development forum, would that fix the problem? For the moment I downgraded back to 2.1 to see if the radio works with the software loaded. I think its a defective phone and will do warranty service again if it turns off again or lockes up under 2.1.
I'm willing to vote defective phone. I had the exact same symptoms on my Mez. I got mine back in October when they were originally released. Worked great until about 2 months ago. USB stopped connecting for anything other than charge.
About a week ago, it began randomly rebooting itself and coming up in Airplane mode. A battery pull would fix it.
Then it started going into airplane mode randomly, without a reboot. But it would not come back unless I factory wiped the phone.
Did a replacement swap with USCC, had no problems at all with the replacement phone.
Rooted the first try with super one click, restored my apps from Titanium Backup, and moved on.
I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229
Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.
No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).
Sent from my LG-P999 using xda premium
i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3
The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.
Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry
I have had nothing but problems with the two G3s I have had. One had a broken screen (not its fault) so was retired. One the screen started doing this weird backlight problem. So I swapped out the internals from one into the other. to make one good one. Both the same exact ATT LG G3 D850s.
Worked fine for a year. Then today the phone just turns itself off. So I tried to turn it back on, no response. Remove the battery, turn back on. Looks like it is going to boot, gets to the ATT screen, then loops back to boot again and again.
So I said screw it, everything on it gets backed up daily, so lets factory reset it. No go, it starts to do the factory reset then reboots over and over.
So I said fine, and started to follow this guide:
lgg3root com/lg-g3-root/how-to-unrootunbrick-lg-g3/
I downloaded the proper TOT and DLL files, but when it goes to do the update, it says Model Information CHECKFAIL
Any thoughts? I do not care if I have to put a custom ROM on or whatever, I just need it to work for a few more months.
Thanks!
Update today.
Not sure if this is a battery problem or hardware problem. I do not think it is a software issue. I suspected a battery issue, which is why I tried swapping them before. I have two genuine original LG G3 batteries. One used for a year and one for two years.
I decided to say screw it and see if maybe sitting overnight with the battery out did anything.
I have two batteries, both were at around 70% originally. I think through testing yesterday one had gotten up to 80%. I had tried swapping them at various times yesterday while troubleshooting. I put one in again. It came up and started optimizing apps like it was doing the reset. I said ok great! But then it crapped out after like 5 or 6 apps. So I put in the other battery, and it made it through the entire process and has been staying on without issue.
The thing is, it would stay on the DOWNLOAD MODE without issue before, so I am not sure it is a battery problem. But I am wondering if there is a problem now with both batteries where if it gets below say 70% it doesn't work.