Database Info

Nexus 5 only charges while in Bootloader

Dear XDA-community,
My Nexus 5 (D821 32GB) only charges while in bootloader mode.
Symptoms:
It spontaneously stopped charging in a normal way yesterday. By that I mean, that my Nexus 5 does not charge while switched on. While switched off, it loops the following way: it switches on, shows battery logo with the lightening, then goes to the logo that shows an empty battery (even though it isn`t empty, this logo usually shows loading progress, in my case it is not animated, meaning it just stays "empty"), after what the phone switches off and it goes back on again.
My temporary solution:
To circumvent that, I found out that it always charges while the bootloader screen is on (bootloader version: HHZ20h), and sometimes charges while in recovery mode (I have TWRP 3.0.3.0). So I used this method to load the battery.
My troubleshooting:
After extensive search on Google, the only reasonable thing that was said in one of the forums was that probably Android 6.0.1 detects some kind of danger to charging my battery and refuses to do it (I had the Xtrasmooth 6.0.1 custom rom with Xposed installed, stock kernel). Next thing I did was installing the app "Ampere" which told me that my phone`s battery, even though close to 3 years old, is in "good condition". Assuming that it is the OS that is messing with my charging issue, I completely wiped my phone, only leaving TWRP and an unlocked bootloader.
Please note:
I have tried all kinds of cables and chargers, even tried connecting to the PC to charge. My original charger works perfectly fine, and the charging port itself is clean. Like I said, the phone charges only while in bootloader. Battery life is also normal.
Question to you guys:
Here I am, with a fully wiped Nexus 5, ready to install a new custom ROM and being unsure what the issue might be.
Can anyone help me get my phone back to charging while the phone is on?
Is there a way to separately flash/work with usb connector drivers?
Thank you in advance :fingers-crossed:
Update 1:
Flashed latest factory image and returned phone to complete stock, problem persists. Why would the charging port not work while the phone is on?
Update 2:
Enabled USB debugging. Phone is not only not charging, but also cannot connect via USB to my computer as MTP (it is simply not recognized at all). In Windows Device Manager, it does not show up at all, even under "Other devices" (I uninstalled all possible drivers to see if it Windows 10 would react to it getting plugged in, it does not). I believe the problem is not the hardware of my phone (as it can charge and connect to the PC while in bootloader, fastboot commands work, could not manage to get the ADB commands to work in recovery), it must be some kind of internal driver issue.

Hi,
I have exactly the same issue. I have tryed all. I flash my Nexus 5 to Android 5 and the to 4.4.4 but nothing worked. Have you being able to fix the problem?
I also think this is not a hardware issue since I have changed the charging port and nothing happened and the same with the battery.
Santiago

It could be a defective USB flex cable. There are 4 pins: 2 for charging, 2 for data transfer. It's possible for the phone to charge and not be recognized as a phone when connected to a computer.

audit13 said:
It could be a defective USB flex cable. There are 4 pins: 2 for charging, 2 for data transfer. It's possible for the phone to charge and not be recognized as a phone when connected to a computer.
Click to expand...
Click to collapse
5 pins...

Yes, there are 5 pins but I throught 2 were used for data, two for power. I admit I was wrong in this belief.
http://pinoutguide.com/CellularPhones-A-N/smartphone_microusb_connector_pinout.shtml

Boot Loop Issue, Odd Behavior, & Recovery Attempts

Talk about frustrating. During the exact same week last year my older phone ended up with the dreaded boot loop, and now my new Pixel 2 has done the same (Despite no attempts to unlock, root, or otherwise change the software, and with no physical abuse).
I sideloaded an OTA update via ADB in a recovery attempt, but the device is still stuck on the white "G" screen with the progress bar below it constantly moving as if it's trying to make progress albeit without such.
How many others have experienced this with the Pixel 2, especially since early April? My phone first acted a bit odd earlier this month when it refused to turn on, and it then suddenly came back on as someone called me. When I looked at the battery charge profile, the lines were tightly squiggled up and down, which is something I've never come across before. However, my phone acted fine after that, until now.
My phone's memory was recently low, and I admit that, but could that by itself have caused a boot loop?
Additionally, does anybody else have other ideas for what I can attempt recovery-wise before I'm forced to finally try a factory reset?
Thanks, for any and all replies and help.

Which variant of the pixel 2 do you have? The verizon or google?

I have the Google variant.

I had not only that, but it locked into the bootloader - barcodes, [power off or restart the bootloader were the only things it would do.
Make absolutely certain that you're not on a USB 3.0 port with a USB 3.0 cable. (I ended up using a Type A to microUSB cable with a micruUSB-to-Type C adapter, because even the USB 2.0 ports in that computer cause problems with the P2) and run Duece's Script. It brought me from Google willing to replace the phone (they actually shipped the replacement) to a working phone before the replacement arrived. I'm not an expert on the Pixel (or on Android), but I think it's the reboot after each file load that finally does it.
(Now if only Google would make the phone work on 3.0 ports with 3.0 cables. We're not all going to buy new computers (or even new motherboards) because they forgot one little thing.)

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

Self Resetting Pixel 4a

Hello,
I got a very strange problem with my Pixel 4a I recently got for repair and I need some help.
The failure I experience is that it boots and after a few seconds just reboots again.
So I thought I should put the device into Fastboot or adb and get a new Fimware flashed. Strange enough it shows the same behavior in this modes means I cannot flash anything at all onto this device.
A further defect are 3 vertical green Bars but else it is basically new.
Hope someone has some clue on what's going on.

Bricked my OnePlus 8 beyond anything ive done before

So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.

One option you can try is getting an EDL cable.

Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.