Develop Bugs

[Q] Rooted CM7 Incredible will not turn on or charge

First of all I'm new here so apologies if I'm asking a question that's been asked before.
My situation is this:
My girlfriend has an HTC Incredible. It's going on 18 months old. I rooted it a while back with unrevoked and loaded CM7 on it. It ran perfectly for quite a while. Lately, she's been experiencing a problem with random reboots, I'd say over the past month or so. She said it would reboot when she had it plugged in to her work PC so she can listen to Pandora and keep a charge. Last night in an attempt to stabilize it and prevent the reboots I loaded Go Launcher on it and made sure she didn't have an malicious apps. Well, today apparently while she was working and had it plugged in to her PC via USB it rebooted and got stuck at the HTC Incredible screen. So she pulled the battery. Since she pulled the battery, the phone will not come on. I've tried the power button plus the volume down, the power button plus the optical button, everything. The charge light won't even come on. So, any help from anyone would be much appreciated!

bamajag said:
First of all I'm new here so apologies if I'm asking a question that's been asked before.
My situation is this:
My girlfriend has an HTC Incredible. It's going on 18 months old. I rooted it a while back with unrevoked and loaded CM7 on it. It ran perfectly for quite a while. Lately, she's been experiencing a problem with random reboots, I'd say over the past month or so. She said it would reboot when she had it plugged in to her work PC so she can listen to Pandora and keep a charge. Last night in an attempt to stabilize it and prevent the reboots I loaded Go Launcher on it and made sure she didn't have an malicious apps. Well, today apparently while she was working and had it plugged in to her PC via USB it rebooted and got stuck at the HTC Incredible screen. So she pulled the battery. Since she pulled the battery, the phone will not come on. I've tried the power button plus the volume down, the power button plus the optical button, everything. The charge light won't even come on. So, any help from anyone would be much appreciated!
Click to expand...
Click to collapse
This may sound stupid but did she put the battery back in right?

Yeah, she did. I don't get it, I've googled the issue and I can't really find anyone having the same problem.

If you can't even get into hboot, it ain't good. Any way to try another battery just to rule it out?

power button + volume down + middle button is the ultimate reboot.
and yea I say try another battery -or- charge the same battery in an external charger and try it again. If not then something really weird happened to that phone..

I'm going to try a new battery tomorrow. Dumb question : Can a battery just die like that? I've always thought there would be warning signs.

The random reboots are the warning signs. My phone was randomly rebooting last month about twice a week then one day it rebooted as I stared at it six straight times. Apparently my battery (it was a Seido 1750) was known to flake out after a few months according to reviews on Amazon reviews. These reviews were posted after I had my extended battery for a few months so I was unaware. I switched to my stock battery and I have gone four weeks without an issue.

My seidio 3500 occasionally likes to discharge in an extremely rapid fashion. I hope I don't have to go back to my stock battery... Ever!

Happens to computers. Power supply starts to go bad and you begin to get phantom restarts. Then your PC is dead.
Sent from my ADR6300 using XDA Premium App

Tried a different sd card? Note that cm interacts with the sd card during boot.
Sent from my ADR6300 using XDA Premium App

Thanks for the help everyone. I finally tried a new battery. Doesn't work. The phone still will not charge. I'm at a total loss as to what to do. If nothing else works, I'm upgrading my Droid X to the Droid Prime (when it's released) and giving her my X. If anyone has any additional suggestions...it would be greatly appreciated.

I would throw that usb cable away...
If the cable is shorting out it can kill our phones because of the extra pins for TV out in the micro-usb port on Inc. +5dc on a video out line might have toasted it.
Just a thought.
good luck

[Q] Sleep of Death on GN

Has anyone else experienced this on the GN?
I've had this happen twice in the two weeks since I got it.
The device is stock.
The only common thread I can think of is that in both instances I had plugged the phone into my PC via the USB cable.
I only use 3 sources to charge, my PC at home, laptop at work, or wall charge overnight.

Meh, it is the Nexus (tame dev device). The S was way more unstable. Just pull the battery and all is well.
If you want to be cutting edge then you have to take the rough with the smooth.
R
Sent from my Galaxy Nexus using XDA App

Never happened to mine. You might have a buggy app that doesn't play well with ICS.

Thanks lads, I'm not massively concerned, and yes, it may well turn out to be a bad app, was just posting to find out if it was more "common".
I have of course just seen another thread in this same forum dealing with the same topic (funny that my post flagged up a bunch of other threads in unrelated forums), so this'll probably be closed down...
Think I'll go wade into that other thread now

I've had it twice since I got mine, wasn't plugged in both times so for me it's not down to charging.

mine reboots everytime i try to use the picture frame widget. i select the pic, then it reboots.

The day I got my phone, I had 2 SOD's.
This morning after I woke up, it was in a SOD and 2 minutes ago, the screen went off and I had to take the battery out.
Really strange
Someone have a solution?

I noticed this issue too, whether charging from the PC or the mains charger once the phone hit 100% on the battery it would turn off and could not be started without pulling the battery. I read somewhere that resetting the phone could cure this so, as much of a pain in the ass as that is, that is what I did. SO FAR this seems to have worked for me. I was charging the phone via the USB cable to the PC yesterday and no shut off and when I went to bed last night the phone was on charge all night and again when I woke this morning all seemed good. I'm not sure if this will work for everyone suffering this issue but it worked for me (for now) so thought I would share my experience.
Good luck !

This is so weird, hasn't happened to me since that day. I was able to reproduce the issue after reading another thread on battery saving. Someone mentioned limiting background processes to 3 in Developer Options, when I did this, my phone SODed within seconds. Twice!
Think I mentioned this elsewhere and someone said he used that option with no problems so it's clearly inconclusive. I'm just going to steer clear of that for now.
Sent from my Galaxy Nexus using XDA App

Skysurfer69 said:
Has anyone else experienced this on the GN?
I've had this happen twice in the two weeks since I got it.
The device is stock.
The only common thread I can think of is that in both instances I had plugged the phone into my PC via the USB cable.
I only use 3 sources to charge, my PC at home, laptop at work, or wall charge overnight.
Click to expand...
Click to collapse
This has happened to me a number of times, usually when I was multitasking while listening to the Google Music app. It's a good thing that back cover is easy to pull off and put back on.

[Q] Bricked for Good? Help!!

Okay I've tried everything i can think of with my kindle here's what happened.
I rooted on thursday, played with a few roms ended up going with one of the cyanogen mod 9 roms i cant remember the name of it exactly off the top of my head.
Charged all night thursday
played with my kindle almost all day friday til the battery died.
Here's where it went wrong.
I plugged it into my desktop with the dead battery to charge it, and ever since it has gone to the boot screen with the yellow triangle and stays there for 3 seconds almost exactly, then off, then 3 seconds on that screen, then off on a continuous loop.
I left it plugged in all night and it did the same thing all night and i've tried using the unbrick utility and kindle fire utility to try and fix it and possibly force it to boot into recovery mode, but neither will even recolonize it because i guess it doesn't stay on long enough if i need to i will post a video to show you all exactly what is happening just let me know
I'm positive its not fully bricked for good, I'd just love to know why the hell its doing this and what i can do to fix it without taking it apart.
Thanks Everyone.

I have noticed that Windows does not always load the drivers/etc fast enough to use fastboot. If you have a USB thumb drive I would recommend trying Firekit LiveUSB repair kit 1.1. It has saved me from tossing mine out the window a few times already. When I am playing with roms etc, I keep it handy for when I break something.

jedens said:
Okay I've tried everything i can think of with my kindle here's what happened.
I rooted on thursday, played with a few roms ended up going with one of the cyanogen mod 9 roms i cant remember the name of it exactly off the top of my head.
Charged all night thursday
played with my kindle almost all day friday til the battery died.
Here's where it went wrong.
I plugged it into my desktop with the dead battery to charge it, and ever since it has gone to the boot screen with the yellow triangle and stays there for 3 seconds almost exactly, then off, then 3 seconds on that screen, then off on a continuous loop.
I left it plugged in all night and it did the same thing all night and i've tried using the unbrick utility and kindle fire utility to try and fix it and possibly force it to boot into recovery mode, but neither will even recolonize it because i guess it doesn't stay on long enough if i need to i will post a video to show you all exactly what is happening just let me know
I'm positive its not fully bricked for good, I'd just love to know why the hell its doing this and what i can do to fix it without taking it apart.
Thanks Everyone.
Click to expand...
Click to collapse
You have a dead battery. Use the charger you got with the Kindle Fire and try to charge it. The power coming out of your desktop's USB port is insufficient to recharge the battery in this condition.

[Q] Phone gives no response, but heats. Fixable?

Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c

Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.

Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?

Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck

[Q] Flashed ROM, worked perfectly, won't turn on now

So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?

NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.

FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...

2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.

NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.

FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?

NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.

NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app

a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).

NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.

FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!