Develop Bugs

One-X not charging whilst powered on after JB update

Hi all
Updated my One-X last night via the over the air update, and thought all was great.
Unfortunately, the phone does not recognise the charger when plugged in whilst it is on. It doesn't work either when plugged into a PC, no charging and no HTC Sync etc.
If I turn it off, it seems to charge OK.
Anyone else seen this and can anyone offer any suggestions?
Would a factory reset or is there an RUU that would work? I assume these would be fine if I have to send my phone off to HTC...
Thanks.

rowlarry said:
Hi all
Updated my One-X last night via the over the air update, and thought all was great.
Unfortunately, the phone does not recognise the charger when plugged in whilst it is on. It doesn't work either when plugged into a PC, no charging and no HTC Sync etc.
If I turn it off, it seems to charge OK.
Anyone else seen this and can anyone offer any suggestions?
Would a factory reset or is there an RUU that would work? I assume these would be fine if I have to send my phone off to HTC...
Thanks.
Click to expand...
Click to collapse
Anyone? Please?
Update- it doesn't charge consistently even when turned off. Left it charging all night and woke up to 3% battery.
Done a factory reset, no change.
Went into fastboot menu and got an error message that 'failed to open USB master mode' before giving the usual options.
Thanks.

You are probably going to have to get your carrier or the place you bought it from to look into it.

rowlarry said:
Anyone? Please?
Update- it doesn't charge consistently even when turned off. Left it charging all night and woke up to 3% battery.
Done a factory reset, no change.
Went into fastboot menu and got an error message that 'failed to open USB master mode' before giving the usual options.
Thanks.
Click to expand...
Click to collapse
Send it in for repair if you can. Mine stopped responding and charging but I couldn't access fastboot at all.

[Q] Battery doesn't seem to charge, can't get into Odin

I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?

jonnierod said:
I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?
Click to expand...
Click to collapse
The easy options are to borrow a battery from a friend with a s2 phone, or get a charger off ebay, or buy a new battery from the store which will probably come with a partial charge.
Sounds like your usb port may have died. That happens sometimes.

I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk

jonnierod said:
I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
It is possible. I had a phone that the data burnt out on, but would still charge. Just one pin needs to be bad to cause some issues, but not break everything.
Could just be the battery is totally empty too. Getting a known good battery with a charge is the first step to troubleshoot this.

I have encountered this problem a time or two before when testing some of my many attempted multiwindow mods, the device will in fact charge, but it is going to take forever. After a double shift I would imagine you'd have enough charge to flash properly, so try it again afterwards. Also have you attempted to return to recovery? If Odin only partially completed, your custom recovery may still be there and you might be able to use the power off option from recovery, while the device is plugged in, and possibly tricking it into not powering on to the error screen.
WARNING! Everything in blue is simply conjecture and has not been proven to work, it is simply a working theory. If it does not work don't say I didn't warn you.

[Q] Device suddenly won't turn on

Before last week I never rooted the device Nexus 7 2013(WiFi) or did any other modification.
Last Friday I decided to root the device using towelroot(used it on my Nexus 5 as well) in order to download and install Android 5.0 using an app from the Play Store (I forgot the name it had a nexus logo and it downloaded OTA Image and installed it).
Up until an hour ago everything was fine and the device had 42% of Battery, 10 minutes after the last time I used the device I tried to wake it and the screen just didn't turn on(still won't).
I know the device is on because when I plug it in the USB the computer does the sound of a connected device.
Could anyone please help me solve the problem?

gp2004 said:
Before last week I never rooted the device Nexus 7 2013(WiFi) or did any other modification.
Last Friday I decided to root the device using towelroot(used it on my Nexus 5 as well) in order to download and install Android 5.0 using an app from the Play Store (I forgot the name it had a nexus logo and it downloaded OTA Image and installed it).
Up until an hour ago everything was fine and the device had 42% of Battery, 10 minutes after the last time I used the device I tried to wake it and the screen just didn't turn on(still won't).
I know the device is on because when I plug it in the USB the computer does the sound of a connected device.
Could anyone please help me solve the problem?
Click to expand...
Click to collapse
Do you get the charging icon when you plug into the OEM Charger, or nothing at all?
You might have a failure on the board. I had the same issue, and would get a weird driver when I plugged into my computer. I was still in the warranty period, so I RMA'ed, however, if you are not, folks have had luck with opening the tablet, disconnecting the battery, and then reconnecting.

ariesgodofwar said:
Do you get the charging icon when you plug into the OEM Charger, or nothing at all?
You might have a failure on the board. I had the same issue, and would get a weird driver when I plugged into my computer. I was still in the warranty period, so I RMA'ed, however, if you are not, folks have had luck with opening the tablet, disconnecting the battery, and then reconnecting.
Click to expand...
Click to collapse
Unfortunately nothing at all and I am after the warranty period,
Could you maybe recommend me a guide on how to open the tablet and disconnecting/reconnecting the battery?

Recieved OTA software update now phone will not power on unless connected to charger

Samsung S6 Edge+ SM-G928A
Baseband: G928AUCU5ERB5
Build: NRD90M.G928AUCU5ERB5
Received an OTA software update yesterday and as far as I know it downloaded ok, but since then my S6 Edge+ has become a nitemare. Here's whats happened since I received that update:
1- phone will only power on when connected to a wall charger. Will not power on when connected to my car charger and will power on when connected to a portable charger after several reboots
2- when off, the large green battery gauge will go from 76% reboot to 100% reboot 76% reboot 90 or 100% when finally powered on the battery shows full
3- even when I do finally get it to come on I have to leave it alone for about 15 mins (no screen touches no touching buttons) or the phone will reboot. I *THINK* the reboot happens as soon as I access an app that needs internet but I"m not sure. Once THAT reboot happens I'm usually good to go as long as I'm connected to the wall charger.
3- cleared cache partition and factory reset
4- when connected to laptop it will constantly reboot after Samsung logo. After I factory reset the device the phone will only allow me to select English (initial setup wizard) and when it gets to which wifi network I want as soon as I select the appropriate one it will reboot. I can let it set for hours and its fine until I select which network to use.
5-contacted Samsung they just want me to send it to be looked at.
So, I need help please. I realize this seems like a battery issue and maybe it is but the timing with the update and various things I've read online make me think something went janky with whatever AT&T sent me. I just don't know what to do at this point since I can't flash firmware since I can't stay on when connected to USB.
Open to any and all suggestions, thanks.

Pixel selective charging and won't connect to PC

A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A

Same problem
Jank4AU said:
A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A
Click to expand...
Click to collapse
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.

ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
Mine sees a Samsung device!

Jank4AU said:
Mine sees a Samsung device!
Click to expand...
Click to collapse
My PC keeps trying to install a Samsung device driver for some reason.

I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.

Thanks
boe323 said:
I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.
Click to expand...
Click to collapse
Thanks I was going to start your procedure but I hesitate. I had a second laptop that I had just restored to factory default and the phone communicates fine with it. In fact I am transferring music files to the phone as I write. So this leads me to the computer being the problem. On my working laptop the phone shows up as a portable device\Pixel 3 XL. On my problem laptop it is showing as an ACER Device\ACER ADB Interface and I have tried to update & uninstall this device but it always returns when I do a scan for hardware changes.

Had a very similar problem where all of a sudden all of my chargers would only slow charge except for the type C fast chargers, it wouldn't recognize the headphone jack adapter and my phone wouldn't deep sleep at all due to a kernel wakelock that only applies to when a cable is plugged into the phone (can't remember the exact name of it).
Multiple fresh flashes including one with a complete wipe and fresh start would not fix it. I even tried blocking the wakelock and nothing.
Unfortunately the problem has fixed itself randomly and hasn't shown up again so I have no clue what caused it and what fixed it. I thought it was maybe a bad charger port or something got stuck in there but no clue. The only remnant is that the phone will say charging slowly when it gets to around 80-85%.
Forgot to add that I'm actually on the last update for Android 9 instead of 10 but figured I'd chime in just in case