Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
See this thread and good luck.
http://forum.xda-developers.com/showthread.php?t=2013977
Sent from my Nexus 4 using xda app-developers app
chelsierae said:
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
Click to expand...
Click to collapse
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
elliot.newnham said:
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
Click to expand...
Click to collapse
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
chelsierae said:
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
Click to expand...
Click to collapse
This happened to me today. The battery indicator is incorrect, and shuts down before notifying you sometimes.
Phone shut down on me randomly and wouldn't turn back on today. Plugging into the wall didn't help. It was only when I plugged it into my PC and let it charge for 5 minutes that it came back. Scary bug.
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
elliot.newnham said:
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
Click to expand...
Click to collapse
I thanked you on accident, you didn't deserve it. There is no evidence that his phone is bricked, a user above reported the same thing happening and how he resolved it.
Also, he can type in bold if he wants to.
I hope the OP issue gets resolved. Wish you all the best buddy!
I'm having the same issue. Except this happened when I pulled the device new out of the box. Can't even get it to stay on long enough to get into bootloader mode. :-/ RMA time
Good luck on fixing the problem.
Sent from my Nexus 4 using Tapatalk 2
Related
Hi, yesterday I installed CM7 on my android, all went well, very awesome.
Soon the LED Light messed up when I would plug the phone in via usb.
The LED had colors that were like mixed and all.
Searched on Google, and found nothing... So I then did the whole process over (wiped data...) And near the last step I wiped data instead of wiping cache.
It was like 5 in the am and I got sleepy so when I restarted the phone(Of course it would take a while), I went to lie down, then fell asleep. Woke up and my phone was still at the Motorola Logo screen. I also seen that I forgot to put it on the charger before went to sleep.
Long story short, My phone won't get past the logo screen, I would try to go back to 2.2 sbf but when I get into the bootloader screen the battery low cannot program.. error comes up.
Yeah, I explained practically everything..
What can I do to get it back to normal, so I can get CM7 back?
I only got to enjoy 20 minutes of the rom...
My phone: Motorola Bravo
Service: AT&T
You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App
rdannar said:
You need to charge your battery some how? Does it charge at all
Do you know someone with phone?
If not ask for a battery replacement from at&t store and hope it has enough charge
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
My thought on charging was when the phone is off and you charge it, it goes to the charging screen, then eventually the display turns off.
Instead of that, it just stays at the Motorola Logo screen..
I've also had it on the charger for about 4 hours now. Still remaining at the logo screen, BUT it has also gotten warm..Maybe that means its charging? (right??)
2. Since I've moved, nope. Don't know anyone that has this phone and is near me.
3. Battery Replacement. It's 1am here so, I guess I'll just keep it on the charge till the morningmorning..
I could do the bootloader sbf back to froyo thing but since the phone's battery is dead to the max, I get the error, meaning I can't do that option.
I'll call my local AT&T store to see if I could get a battery replacement if I can't get it to turn on to at least the Recovery or bootloader.
Pain.. pain in my brain.
try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)
You have soft bricked your phone, so the only way to get it working is to sbf back to 2.2. The problem is, the bootloader doesn't allow you to sbf if your battery is below a certain point. You need to either get that battery charged or get a new one.
If you can't get anything at your store, I will cross-ship/trade you a charged battery (1 year old) for your current one and $3 for shipping? Let me know if you'd be interested in something like that...
I also bought a battery from Amazon (OEMShop or something), and I think it came 40%ish charged... You could try your luck?
Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App
dontbejeff said:
Just so you understand the charging, Android uses the OS to monitor the charging. If the phone is bricked it doesn't charge… plain and simple. It sucks if you try to sbf after the battery is drained, but the only thing you can do is get another one. Hope your search for one comes up well.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.
Before you send other phone back... sbf with other battery back to stock.
AndroidRocksSocks said:
Yeah..no.. I'll be getting a replacement phone (same one). Basically in 4 to 6 days..
I'm so happy, my phone kept restarting anyway when using data.. But yeah, thanks though.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
rdannar said:
Before you send other phone back... sbf with other battery back to stock.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeah, I thought of that when I got of the phone with them. Thanks for the heads up though!
My replacement phone came in the mail earlier this afternoon! Thanks for all the help you guys. Glad I came here. So excited, just 10% more and it's fully charged.
I think I may get a extra battery just in case for my phone. Great post!
This just happened to me too. I thought what to do...
Spliced one of my old car phone chargers and hooked it to my phone battery... plugged it into my car fir 5 minutes and was charged enough to sbf.
Don't recommend it if you don't know what your doing
Cheers
Sent from my MB525 using XDA App
rubbachicken said:
try to get it plugged in w/ no logo, to ensure it's off off... if not you might have to let it sit off the charger till it's dead enough that it doesn't try to boot...
i think it's trying to boot, but boot looping and not aquiring enough of a charge,
do you have it on a wall charger? make sure it's like 800 mah or higher, i think the phone comes with a 5.1v 800mah which was weird to me tha tit was 5.1 cause all other phones are 5.0 but anyway maybe you're not getting enough of a current to it to overcome the drain from the bootloop?
Are you able to get into custom recovery? (Do you see the blue LED at any point when the phone begins to try to power on?)
Click to expand...
Click to collapse
Volume up... not down... got it
Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?
Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.
Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App
Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...
did you try booting in recovery? vol down ±power
zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.
You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium
Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.
So about a week or two ago my phone randomly shut itself off. I'm not sure exactly what happened but I just locked it and slid it in my pocket and an hour or so later I checked it and it wouldn't turn on, yet I could feel the gpu/processor getting extremely hot after a minute or so of failed attempts. Also the trackpad would flash red, which I had never noticed before. Prior to this I had been noticing my battery was draining quicker.
So when I try to charge it will charge itself for approximately a minute or so and then the orange LED will go out, again the processor/gpu gets very hot. After about an hour if I come back the phone will feel cold again as if It had been off and the phone won't turn on. I was able to buy a new battery today, because I read it could be related to a dead battery. This new battery boots to the familiar HTC mytouch4g intro (which is good, considering the old battery doesn't even power on), but then will shut off immediately after that or occasionally just get stuck at that screen. I can boot into recovery but then it says low battery voltage. I tried to do a factory reset but it just takes me back to the bootscreen again and shuts off.
I'm not sure what to do, as I've bricked a previous phone before and this doesn't really seem similar. I'm thinking about leaving the phone on charge, even though the orange LED is off with the hopes that it will charge. Anyone else have similar experience to this?
You tried different chargers?
estallings15 said:
You tried different chargers?
Click to expand...
Click to collapse
Yeah, like 4 or 5 different mini usb's.
Can you get into the bootloader?
estallings15 said:
Can you get into the bootloader?
Click to expand...
Click to collapse
Yes, by holding down on the volume and the power button right? Almost every option leads back to the phone rebooting.
greeny996 said:
Yes, by holding down on the volume and the power button right? Almost every option leads back to the phone rebooting.
Click to expand...
Click to collapse
Try installing PD15IMG.zip.
estallings15 said:
Try installing PD15IMG.zip.
Click to expand...
Click to collapse
Sorry about the long response time. Unfortunately now my phone will not turn on with either battery, so I couldn't flash the img. I think it could be possible that my phone is not actually charging the battery and both of them have died. I'm not entirely sure, I'm going to charge it overnight and hope for the best.
greeny996 said:
Sorry about the long response time. Unfortunately now my phone will not turn on with either battery, so I couldn't flash the img. I think it could be possible that my phone is not actually charging the battery and both of them have died. I'm not entirely sure, I'm going to charge it overnight and hope for the best.
Click to expand...
Click to collapse
Perhaps your USB port is broken
Sent from my GT-I9300 using xda premium
bas3balman said:
Perhaps your USB port is broken
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I doubt it, my phone will charge off the USB for a minute or so when I plug it in.
I don't know how I did it. I've been rooted/unlocked for over a month (running CM the whole time) with stock kernel. Last night I upgraded to the 03.24 nightly and everything was fine. 3 hours later I downloaded a franco kernel after some reading and I wanted to try it out. I used Rom Manager to reboot into recovery (like I always do) and install the kernel and as soon as I hit "restart now" apps started FC'ing and my phone never came back on. It never made it to recovery mode or anything. It just died completely and I was around 40-50% battery life.
Currently this is what I'm dealing with:
Holding the power button down for 10 seconds flashes a red LED light. No changed on the screen
Holding any combo of the volume keys (up, down, and both) + power does the same as above
The only time the LED flashes red is when I'm plugged in via USB or AC. Otherwise nothing
I've had to charging for nearly 10 hours now... it's like it has no power at all
When plugging it into a PC I see "QHUSB_DLOAD" in my device manager.
I have the Android SDK and Nexus 4 drivers installed
I have seen NOTHING On the screen since this has happened - no charging animations, fastboot, not even a flicker
I've down A LOT of reading and the only thing I haven't tried is charging it for days at a time and taking it apart (which I'm not opposed to doing) but I'd prefer not to. Is there anything else I can try? Thank you
Sounds like you flashed the franco kernel for the Nexus 7. You aren't the first and probably won't be the last. Unfortunately if you see QHUSB_DLOAD its dead.
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
That's what I was afraid of... do you think this is legit? I saw the video and it looks good. Says it fixes phones that don't boot at all. I e-mailed and asked them about my situation but I'm curious if you have heard anything about them?
http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/
blahblah13233 said:
You can try to get Google to RMA it. Yeah man, its bricked. Next time make sure you look at what your flashing.
Click to expand...
Click to collapse
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
blitzzz3434 said:
Not to be an ass but it's his fault for flashing the wrong kernel. Google shouldn't have to pay for his mistakes.
Sent from my Nexus 4
Click to expand...
Click to collapse
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
Most of them are pretty reliable. The one that you linked to, they have their own YouTube channel where people have left pretty positive comments. They seem legit. I'd try them out if you want to be nice and not RMA it.
https://www.youtube.com/user/MobileTechVideos
Yeah its really legit. I got my HD2 Unbricked from there. I flashed a wrong radio and came back with a "RESURRECTED" Bootloader and just flashed a new rom. Its probably different on the Nexus 4.
duckwizzle said:
I understand it was my fault. I wouldn't expect them to because it was my fault. Have you heard anything about the legitimacy of JTAG repair?
Click to expand...
Click to collapse
I would still google them to see if there are actually legit. But hope it all works out for you!
Thanks for the replies everyone. I'm going to send it to them to fix it... I'll post back here with the results so other people can search this thread for answers
its bricked. Next time make sure you look at what your flashing.
I got the red light of death, just charged the phone for around 8 hours and it came back.
Sent from my Nexus 4 using xda app-developers app
2 days ago my phone (for the first time) just shut off and wouldn't turn back on even if I held the power button. It turned back on after plugging it into an outlet and holding the power button. The same thing happened today.
I'm using the stock battery (I just bought the Anker battery because I figure it's the battery causing issues) and I'm on Scott's CleanROM. I've had the phone since July (brand new) and haven't had any problems since.
How long have you been on this rom/release version? Got a new kernel or try any new kernel settings? Maybe try using the new battery for a few days to see if that's the problem?
xBeerdroiDx said:
How long have you been on this rom/release version? Got a new kernel or try any new kernel settings? Maybe try using the new battery for a few days to see if that's the problem?
Click to expand...
Click to collapse
+1. Sound kernel related. Did you mess with any voltage settings?
Sent from my SGH-I337 using XDA Premium HD app
AT&T - S4 - CleanROM 1.5 is the exact ROM I've had since I installed it. I'm not too sure what "kernal" means so I didn't change any voltage settings or anything like that.
Br4nd3n said:
+1. Sound kernel related. Did you mess with any voltage settings?
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
iTech02 said:
AT&T - S4 - CleanROM 1.5 is the exact ROM I've had since I installed it. I'm not too sure what "kernal" means so I didn't change any voltage settings or anything like that.
Click to expand...
Click to collapse
OP, test that secondary battery out and see if that's your problem. keep us posted.
Br4nd3n, your device configuration is almost identical to mine. cheers.
Great setup isn't it? Cheers!
Sent from my SGH-I337 using XDA Premium HD app
iTech02 said:
2 days ago my phone (for the first time) just shut off and wouldn't turn back on even if I held the power button. It turned back on after plugging it into an outlet and holding the power button. The same thing happened today.
I'm using the stock battery (I just bought the Anker battery because I figure it's the battery causing issues) and I'm on Scott's CleanROM. I've had the phone since July (brand new) and haven't had any problems since.
Click to expand...
Click to collapse
I had a problem like this too, running a different ROM, CM 10.1, a nightly - I removed my battery and fully charged it in a stand-alone charger and returned it to my device and haven't had an issue since.
FourPointedFreak said:
I had a problem like this too, running a different ROM, CM 10.1, a nightly - I removed my battery and fully charged it in a stand-alone charger and returned it to my device and haven't had an issue since.
Click to expand...
Click to collapse
I think I just got unlucky with a defective OEM battery. The new battery comes in tomorrow so I'll stick it in there and let you guys know what happens.
Ironically, my phone has this issue when the battery discharges to around ~40%. It's fully charged right now so I want to test that theory as well.
iTech02 said:
I think I just got unlucky with a defective OEM battery. The new battery comes in tomorrow so I'll stick it in there and let you guys know what happens.
Ironically, my phone has this issue when the battery discharges to around ~40%. It's fully charged right now so I want to test that theory as well.
Click to expand...
Click to collapse
Well whatever works for ya. I'd hate to be that one case of a bad battery. Let us know.
So that didn't fix anything since I got the same issue again today with the Anker battery. I have a feeling it's the "hover your hand over the phone" gesture since this happens when the phone is in my pocket pressing against my wallet.