so i have had a nexus 5 for about a year now, my brother had it from launch, one day it bricked and my brother bought a iphone, so, ofcourse i reflashed the rom, and it worked again, but with weird buggs and quirks, now suddenly it didnt want to charge, so i have decided to factory reset, and ive also replaced the battery (i had one laying around and hadnt come around to puttin it in)
so, heres the issue:
when the device is off, and you plug in the usb cable, it recognizes it, and starts the charging animation, then this animation crashes and it restarts, it does this, over and over again..
when i go to fastboot mode, and i plugg in the usb, my laptop (and pc) recognizes it, and then gives an error, just so it can start the cycle over again, and i cant get adb working like this...
any help?
Which ROM did you flash?
Edit: Oh, and how did you flash it?
Related
OK, never had any auto resets, just had to manually restart often to cure various ills. Then yesterday it was stuck on the dimmest backlight setting. This morning picked it up from charging overnight and it's 100% dead. Switched batteries, plugged it into various computers and USB power sources. Dead.
Anyone brought a G2x back to life?
Have you tried a wall charger? If your battery discharges completely, like deader than dead, then sometimes you have to plug it into a wall charger and leave it there for several minutes before the phone will even show its connected to a charger.
I guess the real question to ask first is, what did you have it plugged in to? What kind of charger? Was it plugged into a surge protector?
It was plugged into the LG wall charger it came with overnight. I tried a iGo USB wall -> USB power supply and a USB port on my desktop windows PC.
dylanear said:
OK, never had any auto resets, just had to manually restart often to cure various ills. Then yesterday it was stuck on the dimmest backlight setting. This morning picked it up from charging overnight and it's 100% dead. Switched batteries, plugged it into various computers and USB power sources. Dead.
Anyone brought a G2x back to life?
Click to expand...
Click to collapse
It depends on how dead it is, if its a hardware defect of some sort then you're probably SOL. But, you don't have to be able to turn it on per se to use NVFlash, so if I were you I would try to see if you can get the device to be recognized using the APX drivers. If you can, then you might have a chance.
My G2x died after freaking up during one of the Davlik cache clears....
It originally would boot up and get stuck at "LG", but after a while it was completely unresponsive (not even a Boot Logo) and wouldn't even turn on. I thought it was fried. Luckily we have NVFlash that you can use without booting the phone up.
Take the battery out and press and hold the VOL keys, then plug it in. Your PC should "ping" letting you know something was connected. Then just reflash a recovery.
I did this a ton of times and it didn't work at first. I kept flashing stock then CWM, then stock, then CWM (different versions too). Eventually it displayed the LG logo and allowed me to boot into CWM where I flashed a new rom.
Been solid ever since.
I also read about this in the Asus Transformer forums (cause I just picked one up) and read about a guy experiencing the same thing.
Worth a shot. The NVFlash method will at least let you know if it is DEAD or just not working. If NVFlash doesn't connect then it is hosed. If NVFlash connects and accepts a new recovery, then something just got corrupted.
All good now! I unplugged, removed battery, let sit a while. Put the battery back in and it booted! Yet more strange behaviour from the G2x, but as usually I get it working again and stick with this phone.
But today I got a second from craigslist to play with alternate ROMs. Trying CM7.1 RC1 first, it's working pretty good on my Nook.
Need a little help here. The other day I turned on our old D2 BC I need aa replacement phone and its given me hell. First boot it went into the Liberty boot animation and wouldn't stop looping. My girl rebooted into recovery and flashed Liberty again and apparently it was working fine which I did not know. When she did this she didn't tell me so I was under the impression I needed to do what she did. I went to recovery, wiped and flashed Liberty, I believe its 2.0. Now I can't get it to even go into recovery. The only thing that happens is sometimes when I plug it in to a power source it will go straight to a liberty screen and just sit there. Not even an animation. Any ideas? I'm fixing my Ubuntu right now so maybe I can access ADB commands from there. It won't detect on Windows.
Sent from my Nexus S 4G using xda premium
update: I finally got this phone to do something and idk how? I have tried to let it charge for a few days now and I'm thinking that 'somehow'(???) the battery got f'd up because just now when I plugged it in to finally try to connect through ADB, a black screen popped up. at top it Read: Bootloader > next line > D2.37 then at the bottom two lines that read Battery Low, Unable to Program. ....any thoughts? other than a new battery?
you need to get the battery charged with another phone or an external charger (stay away from homemade chargers as they can mess up stuff). What happened is the battery got too low to either start or finish sbf'ing so it went to bootloader and the phone won't charge without software so until you charge or buy a charged battery you are stuck. It's very fixable but you are stuck.
Today my nexus 5 is broke.
Few minutes before all warking perfectly. I've got a RASTAPOP and elementalx kernel of course overclocked.
At now my nexus doesnt response to power button but when I connect charger or usb with pc phone was start booting and switching off after one second. Two seconds later it starting again and turning off automatically. Thats happening continously until I dont disconnect the cable.
I tried to go to bootloader then recovery but It isn't possible. Every time I saw the bootloader screen phone reboots itsel again and again and again.
It isn't standar boo loop becouse I have multirom and I dont even have posibillity to choose any rom.
Few weeks ago I bought a cheap battery case. And I saw it doesnt charge battery as ussualy. It charge battery for minute or two then disconnect for while and charge it again diconnect and charge again. Looking like my boot loop. I thing this battery case can broke down my battery in nexus 5 so I order the new one few minutes ago.
Anybody have another solution?
You can be sure Im very sad at this moment.
Stuck power button or other issues.
Send it in for repair/replacement.
Are You sure of it?
It seems like You've got right.
So recently I started having this problem. My Nexus 5 stopped charging all of a sudden.
After messing around I found out that I could charge the phone when it is turned off, but when I boot it (while connected) it doesn't show the charging icon. Only when looking up the battery status at the setting menu it says charging.
To my surprise fastboot was still working (adb wasnt) what brought me to think it's not the hardware.
So far I have done a factory reset, wiped everything, installed stock kernel and recovery, downgraded to stock 5.0 (I don't even know why, just thought its worth a shot...).
At some point I took the phone apart to try to determine whether I tore out the connector itself, and noticed nothing.
I'm really running out of ideas here... I can live with having to reboot the phone for charging, but I really need it to connect to the computer.
Any help will be appreciated!
You tried different USB cables and chargers? USB debugging enabled? Computer is a trusted machine in adb?
I have 2 computers on which adb is trusted. Both stopped working. I tried a few cables, all of them worked with another phone, but did not with mine.
Adb is enabled. :/
Did you try revoking all computers and re-establishing trust after flashing a stock ROM?
Strange that fastboot commands work and adb doesn't.
Nope, but I tried connecting to another one and no dialog popped up.
Btw, an hour ago it just started working... All of a sudden...
I should be happy, but now I have no chance in finding what was the problem.
Anyways thank you for now, if I have any more issues I'll update.
I assume it's physical damage to the usb board/module (since it started working while no change to the software was done in the past few days).
I will order a new one just in case.
Thank you again guys!
Maybe a loose internal connection? You could try removing the back to looking for loose connections.
Did so, didn't notice anything strange.
I do have experience with soldering, but I would rather not touch it before I get a new one, just in case I screw up. Small components are no fun.
The thing that still bugs me though is I had fastboot working perfectly fine all that time. Oh well
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Cloud2F said:
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Click to expand...
Click to collapse
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
cooltt said:
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
Click to expand...
Click to collapse
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Cloud2F said:
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Click to expand...
Click to collapse
the way to test if it has power but blank screen is to hold power+volume down+home. If it has power it will turn off and boot into download mode
After the Forst Crash all such combinations didnt Seen to work either. Once odin recognized is while having a black screen. At that point I flashed stock :/ but still, not even the led was showing something