Database Info

My phone just died

I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on. I pulled the batter out and then went to turn it back on, I would vibrate like it was going to start up and a few seconds it would go black and vibrate again. It did this over and over till I finaly tried a hard reset. I was able to get into the hard reset and it said that it compleated and I hit power up to boot. But then the screen got fuzzy and would not boot, so I pulled the battery again and now I can't get it to start at all! No power, nothing! Even with the power cord pluged in it doesn't do anything, not even light up showing that it's being charged!!
What should I do, or check?

Not knowing particulars I would double check the water intrusion labels and make sure they were both white still. Check your gold battery connectors and make sure those look good. Also check your charger and the USB plug to make sure that it is clean of debris and shiny.
Then I would charge the phone for 4 to 8 hours without attempting any boot ups just to make sure it was fully charged.
I have had 'wonky' issues with the phone being too low of a charge and not booting properly. Sorry I can't be of more help.

I will hook it up to a charge tonight and see if that does anything, but it was atleast at 60% eairlyer and as far as I know should be no reason that it should have discarged that quiclky. Also all the markers look just as they did out of the box. Thanks for the advice!

Your ROM might have gotten corrupted. Try a reflash by booting in bootloader mode.

How? It won't turn on?

wingman1487 said:
How? It won't turn on?
Click to expand...
Click to collapse
Try pulling out the battery (and no USB plugged in) then hold the volume down or up button (I don't remeber which) and hit the power button just once while holding the volume button and if you get to boot loader mode you can go from there. Otherwise I'm afraid you are out of luck.

So with no battery I can get to boot loader mode?

Anyways, in or out, nothing. How does my phone just brick itself? I didn't do anything to it!?

If you could do a hard reset, then you can get into bootloader. Just press and hold volume down and then soft reset. If you have to do, a hard reset first, then go into bootloader when the screen says to press volume up to boot up. Once in bootloader, either flash a rom of your sd card if you know how to or off the usb connection.
What radio do you have, and did you change radios recently? I'd recommend using what nrg says (1.14.25.05) with his rom.

I was able to do a hard reset and now nothing is happening. I cant get it to power up, can't get into boot loader, nothing. It is acting like it is bricked... but I haven't added new software, no new ROM... I just don't understand.

Just pull the battery and let it sit overnight. I've read that that can help.
Oh, yeah, what radio are you using? I ask because there was another poster with a similar problem on that rom. He was using a 1.12.xx.xx radio (I think .25.19), and it appeared to have issues with the included rilphone (1.14.25.05). If you haven't flashed a radio and are using a stock fuze radio, this could well be your problem.

Humm the radio was the most recnet one by HTC. The on that the Energy ROM flashes with stock (not the one he suggests, I never got to flashing that one onto the phone) I'll let it sit tongith and report back in the morning/afternoon.

wingman1487 said:
I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on..
Click to expand...
Click to collapse
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair

nolla said:
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair
Click to expand...
Click to collapse
Well, flash it back to stock and then have it repaired or replaced. You don't need the screen working on the phone to flash it.

To post an update, I pulled the battery and left it all night like that with no resolve. Right now I have my buddy (the one I bought the phone from) on the phone with cingular to see if there is anyway we can get them to replace the phone since it is only 2 months old or so.

Ok! Get an iPhone now

raydm said:
Ok! Get an iPhone now
Click to expand...
Click to collapse
HAHAHAHA Ya that is somthing that isn't going to happen.

so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?

ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
I run any radio I like on my phone and I never got this issue. Sounds like a hardware issue and it just happened to match that the two persons flashed the same ROM without changing the radio to the recommended one because, frankly, I just flash any I want and I haven't gotten that problem yet (mind you I flash sometimes 5 times a day.)

ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
You're probably fine with that radio; you can always install the rilphone.dll for it.
This is the thread I was thinking of. Now that I re-read it, the OP didn't specify the rom, but since everyone is on NRG rom, I guess I just assumed that was what it was. Either way, the 1.12 radio seemed to not get along with the cooked in 1.14 rilphone. Or, it could've just been bad luck on the radio flash.

[Q] LEAD Rom constant reboots while charging

Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?

well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.

Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.

leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.

i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon

x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.

Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?

No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/

x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.

[Q] AT&T SG3 re-boots every 2-3 minutes after OTA upgrade to 4.2.2

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

[Q] Motorola RAZR HD XT925 Doesn't Start (Blinking Green LED)

Hello. I have problems with my device, a Motorola Razr xt925 HD. It doesn't start, it just keeps the green led blinking when connected to wall charger, and when I plug the USB, makes a sound of a new device detected but only for a few seconds then it makes a sound of an unplugged device, and so on. It doesn't respond to any combination of buttons. I let it charging overnight, even though the battery was nearly full before this happened. Don't know if this is relevant but before this happened, I was going to flash stock Retail Brazil firmware by fastboot and got a flash failure. I turned it off and then it wouldn't turn on again. I never had this happened, I had problems but I always solved them all. Not this time hopefully you guys can help me or tell me what it could be, because I doubt it was the battery. I leave you a video showing my case.

i dont know for certain but the only time i see that green light is when battery is ou and i put it to chrge. Could your phone be in apfastboot and can t charge. It is a bit of a tough situation to troubleshoot.
Did you try keys combo to put it in fastboot, and test it by flashing
or maybe use rsd lite see if it shows you device connected? maybe then you can flash stock
i am sure there are other possibilities, let s hear from you

There's no way to enter in Fastboot by key combos and RSD lite doesn't show my device :/ maybe I need a factory cable, just in case that the battery is empty. I need more suggestions please

me paso lo mismo
did you find any solution?

im having this problem after i start using KK 4.4.2 seems like the phone go to sleeping mood by it self while my screen is locked so i have to keep clicking at power and volume up and down to restart the device now im looking for an update or a fix for this problem, another problem is the device WIFI do not catch my house signal while im away 10 feet from the house the software have bugs

I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.

chuYxP said:
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
Click to expand...
Click to collapse
i think your your device is dead.
this exact thing happened to me.
it happened on september, i was forced to get a new device.
i love this phone but it was dead.
i hope a fix comes through i would like to have it back

I ll take one of your hand, I need parts if interested

Any update with this? Did you try with a factory cable?

I'm going through the same thing , I read the other day that and the driver installed and nothing more .
keep trying to revive my device.

I'm going through the same thing. When I plug it into my pc , under device manager it shows "Human Interface Device" then it unmounts itself then remounts itself then unmounts. Over and over..... I've even replaced the battery.

I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you

kilroy1stcav said:
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
Click to expand...
Click to collapse
This thread for the droid Ultra might interest you: http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
There is some discussion of the Razr HD in this thread. It looks like someone with an unlocked device would need to dd their bootloader partition for this method to work.

A few years later .... Any solution? rsrsrs

any update on this scenario?
i have this situation too and the time could give us an answer, i am searching again, i took my device to some 'phone repair stores' and in less than 5 minutes they told me that the phone was dead, but i have my last doubts

Just to add an update here
I ended up with the Green light only and blank screen after trying to fix a battery issue, despite getting a number of batteries my phone wasn't accepting the batteries.
I remembered a battery issue a long while back, so went to reflash my phone to see if it resolved it.
I ended up with the green light and blank screen and no matter what buttons, it would just make a noise then keep rebooting.
I ended up using the Unbrick bat file.
RSD Lite was briefly showing a Medfield device of something starting with Med, but since the phone kept rebooting I couldn't reflash it again.
I did the Pwr and Vol down and as soon as I saw the device, I clicked the UnBrick bat and it managed to get my Moto logo up.
I then booted to Fastboot mode and reflashed and my phone is back,
See this link for the UnBrick, but when you do it, you have to be fast to catch it while the device is seen, otherwise the phone reboots after 4s or soo.
Softely Unbrick XT890 Razr i - Really Unbrick the Zombie
Well do not think that this thread is one among others. It's my experience when i messed up with my Razri. I wish I had this before, so I'm sharing it with you ! Every has his experience and a way to do it, so this is mine First I searched...
forum.xda-developers.com

Slot Unbootable, no USB

Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)

Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.

Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.

somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31

somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.

Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution