Database Info

My TB is dead...

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.

[Q] Flashed King Runny Rom, now bricked?

I have an Evo 4G revolutionary rooted. Had sinister rom. Flashed the new King Runny and it worked fine starting out. I tried to get into the navigation and it said I needed to download the updates. Then it said I did not have enough memory space and I needed to delete to make space. I then deleted all the pictures off the phone, and that didn't help. So next I went to factory data reset and I believe I pressed on the SD card to be erased too, which may have been an oops on my part. So when it rebooted I got stuck at the boot screen where it is the blue android symbol and it flashes repetitively. I tried multiple things, I have read multiple threads. I tried to flash back the stock ruu. I have been working at it for a couple of days now and I am at a loss. I am on the verge of taking it back to Sprint and eating my $100. Funny thing is, I cannot get into recovery, I can only get into bootloader. Last time I was in recovery, it was saying I could not mount the SD card and I could not mount through usb either. When I try to go to recovery now I get the white evo screen, it goes black, vibrates 5 times and I get a blinking green led. So far the majority of the threads I have read say I have to eat the $100. Others say the battery overheating caused a hardware problem. Just want to see what anyone else thinks. Thanks to all the developers and all the people that can make this stuff happen. I appreciate all the support even if it is to tell me I have to eat the $100.

Looping Factory Reset

About a week ago I picked up my shiny new RAZR HD (Australian Telstra), and the following day the Jelly Bean update rolled out to it - so all was going well. After a few days I was noticing that my phone had a lot of wakelocks and decided to do a factory reset just to see if it was something that came along with the update as I hadn't really paid attention in the 24 hours I first had the phone...
It ran through the wipe process and at the end briefly flashed the red triangle error android, but when I eventually got into the phone it had wiped and I thought nothing more. Jump forward to last night and I'm flying home to my parents place so turned off my phone for the flight - and when I tried to turn it back on later it firstly didn't want to turn on, and when it did it went through the update/wipe screen and the error. When I got into my phone it had wiped.
I have tested a little bit and found the following:
If I try to turn the phone on normally it goes through the process of wipe and error out.
If I try to get to factory recovery on the phone via the boot menu it goes through the process of wipe and error out.
If I power on to the boot menu and select Normal Powerup the phone will turn on without wiping
So obviously I can get the phone on, and avoid wiping the device, but it's a bit of a pain. I don't have root, and am away from my home PC with ADB (and don't really have the bandwidth or equipment at my parents to get access to it) - so I was wondering if there was anything that I could do to rectify the situation without voiding warranty or would I best be served by just going to Telstra and asking for a replacement?

Warranty it, is my suggestion. Updates shouldn't cause those problems. If you hadn't rooted your phone prior to the update, you should be able to get an over the counter replacement.

Return it for sure. Don't put up with a headache that is not common.
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2

[Q] RAZR MAXX HD boot loop

Hey all,
First of all, forgive me if this has already been covered, but I couldn't find any threads that had a solution to this specific problem that worked for me.
That said, I have a Droid RAZR MAXX HD that I rooted and flashed to page plus just about two years ago. I have since unrooted the phone. It was running on jellybean 4.1.2 if I recall correctly. The phone has been great and I've been very happy with it till today. I shut it down, nothing out of the ordinary, just decided to turn it all the way off. When I later went to turn it on, it got stuck in the middle of the little boot animation where the robotic iris opens to reveal the red eye. It froze there for 3-5 seconds and then rebooted only to do it again. Funny thing is, it freezes at a different point every time. Some times the red eye is completely visible and sometimes the iris hasn't even started to open. I tried booting without the sd card and when that didn't work I tried all the other typical stuff: simulated battery removal, cache wipe, factory reset-wipe-format. I also tried a stock system data wipe as well as a stock recovery, both with mattlgroff's Doid RAZR utility from AP Fastboot mode. Still nothing.
At this point I'm at a loss. I bought this phone for $300 back when it was the phone to have and it's been a great phone, I don't want to lose it if I don't have to. Any help would be greatly appreciated.

Just a quick update.
I decided to take my phone apart and see if there were any loose connections that might be causing issues with booting. I didn't find any loose connections so I put it back together, and decided to try booting it on a whim. To my surprise, it booted perfectly. A few weeks ago I installed ancleaner, and app that claims to clean your cache, yada yada. I'm guessing that somewhere along the line, it managed to corrupt a deep system file or the cache or something. Regardless of what really happened, my phone is alive again, and I think that it was probably due to physically disconnecting the battery. So moral of the story is, don't trust the simulated battery pull, and physically disconnect it for a time instead.

Boot Loop, sort of...

I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok

same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out

Ontabok said:
I'm having a weird issue that literally just started yesterday. First of all, I didn't do any changes yesterday before this occurred. Anyway, my G3 just started freezing, then rebooting randomly, BUT that's not all! When it tries to reboot, it flashes the LG screen, and SOMETIMES makes it to the AT&T screen....and even, sometimes makes it all the way booted up. But, at any point, it can/will reboot and start the process all over. I read on another site that it could be a battery going bad, but I only trust XDA. So, could someone chime in with some help or info pointing me in the right direction?
Thanks in advance,
Ontabok
Click to expand...
Click to collapse
Sadly that sounds like a hardware issue

hyelton said:
Sadly that sounds like a hardware issue
Click to expand...
Click to collapse
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.

Ontabok said:
How can I figure out what part of the hardware could be causing this? Is there a diagnostics or something I can use? I've tried factory reset (multiple times), LG Flash Tools to flash previous version, and the strange thing is it may not even make it through the process without restarting again. It's been rooted, but I've never had a problem until this. I never deleted anything.
Click to expand...
Click to collapse
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.

hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
I can try Flash Tools again. Maybe it just didn't take. I just noticed another thing. When it's trying to boot, if the notification light flash when the LG screen is on, it will load. But, if it doesn't flash, then it will just go black, then flash the LG screen again.

Kameirus said:
same issue i am having ..i thought about the battery thing so i pulled it out and put in a fully charged one and no bootloop..but now 3 hours later and 85 percent left on battery and bootloops have started again..btw other battery was a 20 percent when changed it out for fully charged batt..so im just as lost trying to figure it out
Click to expand...
Click to collapse
Yeah. It's really weird. It seems to do it less when the battery is charged, but if I get down to 40-50%, it could go into a loop that runs the battery into the red. Also, it seems to heat up around the power button when it's stuck in the loop. And, to top it off, my software update popped up yesterday. I've been anxiously awaiting Marshmallow for a while, but I'm afraid to update because of boot-looping right in the middle and bricking the whole thing. I already have a bricked G2 due to something weird that happened while trying to update to Lollipop. I'm going to the AT&T store today, I think. I'll let you know what I find out. Maybe, it can help you.
Thanks,
Ontabok

hyelton said:
Not really other than swapping out parts. If using flash tool won't work and it won't go back to stock then it's definitely a hardware issue.
What percent does it get too before rebooting? If 80% that's normal. If before it's definitely a hardware problem.
Click to expand...
Click to collapse
Ok. So, first of all, sorry for the long wait on a reply.
I did manage to get through a factory reset, but it still is doing the boot loop. I'm going to take it in to AT&T today. You can see my reply above to see more info. I unrooted everything and factory reset, but it still loops. I think it's a problem with the phone. I may have to go to LG, depending on what AT&T says.
Thanks for the help!
Ontabok

So, final update. I had to go into the AT&T tech store. I was having the random boot loop for about a week, then, on Saturday, I got the Demigod green screen. I had went in the day before and ordered a new battery, but I couldn't find any information on the green screen error. I took it in and they immediately (after checking for rooting) replaced it (warranty). They said they had never seen/heard of this screen. They had to actually Google it to see if it's attached to rooting. (It's not) Anyway, so I'm back in the saddle with a brand new phone. ?
Sent from my LG-D850 using Tapatalk

Also, thanks for the replies!
Sent from my LG-D850 using Tapatalk

ok so my g/fs g3 just started doing this. updated to mm about 3 or 4 days ago. was doing fine. haven't changed anything software wise. completely stock. no root.
what is really odd is that it doesn't loop when plugged into a power source. take it off the charger= insta loop ...
hoping a rom might solve the issue but from the sounds of the replies maybe that isn't the case.
any help greatly appreciated. i've not owned this phone myself or i would already have it rooted and custom recovery..
is there even a root method for MM? recovery?
i'd love to see if its a software issue. the phone worked swell before the update...
im trying to get to the bottom of this tonight if i can my g/f has a final tmr early in the morning and i'd like to make sure she has a phone to go with her. prob send her with mine if i can't get this working. but thats less than ideal PM if you've got anything i can try or links to get me started... i'll be reading in the mean time...