Hello, new member here. I recently purchased an HTC One M8 from AT&T, unrooted to put superuser on my phone since I really disagree with an operating system telling me what I can and cannot do with the device I purchased. I did not know about S-OFF before this issue so no, it is currently S-ON I believe.
Just to be clear, my phone worked fine after this for ~2 months at least.
Anyways, to the issue. When I try plugging in my charging cable it says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although, I do have to say not even all the time. Most of the time when it's plugged in I get zero response that it is. It didn't use to be that way, this was a progression. It started charging fine, then the Car app started booting up asking to accept or decline. The car app doesn't even open up anymore.
So here I'm thinking, either the battery is broken, or the micro USB port.
However, I CAN charge the phone if I have fastboot turned ON and I turn off the phone. It's my understanding that fastboot only puts the phone in a hibernation state and it's not really turned off. When it is in this state, I can plug my charger in and I see the battery appear on the screen charging.
This is the only way I can charge my phone, by turning it off.
I cannot communicate with a PC, I cannot charge while it is turned on. This leads me to believe that this is in fact a software issue and not a hardware issue. However, this issue prevents me from communicating with a PC through USB which removes a number of options for me to test why this is happening.
I can transfer files over WIFI, and I have done so. Yesterday I transferred Android Revolution HD 11.1 to my phone over WIFI and was able to flash it, though I think I have a bad flash and just need to reflash due to a few minutes boot time, and I already read up that you need to try a few times until you get a fast response signifying you got a good image or something like that.
If anyone has any suggestions I am willing to try them, I have everything I need from the phone backed up. I have subscribed to this thread so I should receive a notification.
Tricks that I have tried:
Turning the phone on while the sensor is facing a bright light. Not sure why that would do anything but it was a common "solution".
Powering off the device and holding the power button as well as both volume buttons. This supposedly resets the "charge mode", no result. I was able to boot up to safe mode so I learned that I guess. No it doesn't charge in safe mode.
Draining the battery 100%, holding the power button until no response. Then charging. However, this was a nightmare, as when I tried doing this I got this guys problem: youtube.com/watch?v=r_Nll_01jG0 — This only happens when fastboot is off, or in this case, the power drained and the phone actually turned off, so it clearly only charges in hibernation.
Tricks that I have not tried:
Spraying the port with WD-40 while the device is turned off. Yea okay, I guess I'm worried about putting a liquid/oil in my phone.
They ended up only being tricks, not solutions to the problem. IF it was hardware I would understand completely. I no longer get a response from the phone when it is plugged in except for the occasional error message as the image above. HOWEVER, it charges in hibernation mode, every attempt, nothing weird, it just charges like it should. This is weird to me, because if it was hardware then this should not work. It makes no sense.
I tried an app called USB Host Diagnostics, I'm not sure if this is even going to provide any information to help or not but here is the result: usbhost.chainfire.eu/?search=455254
Since I've changed the ROM / OS of the phone to Android Revolution HD 11.1, and the problem still persists, then the next step down would be the... kernel? So it is either hardware or the kernel? That's just me guessing really... it's so hard to imagine it's the hardware. I take great care of my phone, never dropped it, don't overcharge it, I just don't understand what it could be other than the software of the phone just not recognizing the port while it is turned on, and whatever functions are turned on during hibernation are working correctly. Unless it's a voltage issue where it disables it to protect the motherboard, and during hibernation it isn't a risk, if that's even a thing. If it was a voltage thing, why then would it not charge when fastboot is turned off and the phone is off? It starts up with a battery on the screen then reboots in an endless loop like the video showed above. I just don't understand, wish there was something more to figure out other than it telling me that it's in host mode and can't charge, and by extension can't connect to a PC.
I found something out while just randomly rebooting the device. I rebooted my phone while it was still plugged into the computer and opened up the... bootloader? (Power button + volume down), and then I went to the Fastboot option and I heard the chime on my computer of a new device being detected, and it installed android 1.0 driver or something. I wasn't able to see storage or anything (probably because I was in a bootloader), but I actually heard a response from my computer.
If I toggled between the main menu and FASTBOOT the chime would go on and off between detected and removed.
This really makes me confused, it has to be a software issue right? I've reflashed the android revolution HD ROM multiple times so I don't think it's that... is it my kernel? I am so lost here. The fact that my computer made that chime and installed a driver proves that it can work, but why won't it work when it's turned on?
Hi b.white,
Have you found any solution.
My HTC has shown the same USB in OTG so can't charge problem. It is the first time I have seen this message and problem on my phone. I have my phone for the last few months. I also want to mention that it is as stock as it can get. Never even rooted. I have no popping up CAR app problem. Maybe because it is just been a few minutes the problem showed up. So maybe I'll be seeing the car app later on. But I had about 10% battery on my phone which died out during the few tests I've made.
So right now my phone is turned off (because of battery got to 0%) and is plugged in using standard cable and charger in to a wall socket. It shows that it is charging by using the animation and the percentage is growing continuously. The LED is stable and Amber which means that it is charging.
During the last few battery moments, I turned off the car app through its settings. Never had the daydream setup or turned on anyway. But my fastboot from the settings is off. It was like this when the phone came, and never needed to change this setting.
I also tried this but I'm not sure that I did it correctly and it hasn't showed any difference either.
http://forum.xda-developers.com/showpost.php?p=46415840&postcount=1
While I was keeping the three buttons pressed the phone kept turning on the the htc logo and going back to black screen. I don't think that should have happened, or at least the original thread didn't mentioned this behavior.
This is my main phone. And I am really worried about this problem.
Please help. :crying:
USB Host Mode charging issue (plus Car Mode) just started happening to me last night. I can intermittently charge while the phone is on, but it's inconsistent. Nothing I've tried so far has fixed it for more than a few minutes. Probably will have to send it in for warranty service.
Sent from my Nexus 7 using Tapatalk
OK, so now after I charged my phone to 100% while it was off and turned it back on, I am also having the same CAR mode app problem.
Maybe the latest update that is coming our way can solve this problem. I am talking about the update with the EYE enhancements etc.
Related
This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?
Try to charge the battery in another phone and then try to turn it on using power+vol down. If that works 2.3 ruu is a solution for everything.
In my signature you have the explanation how HTC works, go to the thread and download the image.
Thanks nloooo but as I already said it - battery is ok. Tried it in another Desire - works, tried battery from another Desire in mine - phone wont work. Believe me - If there was a way for me to get into bootaloder or fastboot, I would do so by now. I am trying everything to avoid JTAG, and I wanna know why it will start once in 100 times, and why is this even happening.
looking for a motherboard online - boy those are expensive! they cost more than whole used unit ...
Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?
I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire
jmcclue said:
I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire
Click to expand...
Click to collapse
+1
HTC Sync or HTC drivers.
I installed SYNC but now im freezing phone again (so I could enter HBOOT), will post results in couple of minutes.
As im figuring out - device surely has Hardware failure, being that only frozen is able to boot. since freezing shrinks matter, my conclusion is that EMMC or CPU solder got melted by the working temperature, thus making Tin (or whatever is used for soldering these days) touching somehow on two sepparate solders, but when is frozen, they "go apart".
Once I start it, will check this -
http://forum.xda-developers.com/showthread.php?t=1284196
to determine if EMMC is fried or unsoldered.
Not sure about that thread, it points to problem with eMMC chip that Desire S has not regular Desire. For Desire the most common hardware problem is overheating motherboard issue, usual for PVT1 devices.
And that's just what im going to do - it lays opened on my table now, and there is a big design flaw - NOTHING disperses heat from the CPU cover!!!
I cant believe that HTC did this, this is just like not plugging a CPU cooler onto the motherboard of a PC.
all things aside, the problem lays in bad motherboard, and even if I purchase another one, same thing will happen over time cause CPU cant get rid of the heat.
- reflow solder (im good with that, have proper tools)
- thermal paste over cpu, before covering it back with metal
Im pretty sure this will work. phone is brand new, could get out of the factory if it had such a big flow, it must be overheating problem caused by high CPU usage. will post results later this evening, when I do a reflow soldering.
Well, I have mine for almost 2 years, used it with advance roms (sense 3.0 and 3.5) usually overclocked, sometimes it gets hot, but I can't say I had overheating issue.
The problem is not related to all devices, it's usually connected to PVT1 version of device (which was the first series) that later got fixed.
havent checked my version, but the fact is - it works! (partially) Oh, and on that topic - how do I find out my version .. ? is there a hard print .. ?
After hot air gun (reflow pin by pin could not be done, this shi* is small!) and after putting thermal paste onto the CPU - it goes past HTC logo, tries to load Sense, and then freezes. So all this trouble with software/firmware was for nothing, I guess .. I just need to reflow it a bit more, I got scared that those small pins would melt fast. Boy, I really hope this will work, cause when HW is the problem, I know my stuff, or at least I think I do ..
EDIT: well FOK MI! I dont believe this ...
I am the first to ever open this unit. I removed all the warranty stickers. On top of CPU, there IS NO METAL COVER! Nothing to act as a Heat sink! this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess this gray plate is Aluminum or iron, and the other one small is copper, but I dont have none. No wonder phone hangs 10sec after boot. Im off to make a cover, damn you HTC, how did this ever got out of the factory .. ?
Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?
ludemon said:
Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?
Click to expand...
Click to collapse
same here.. ANY SOLVE ?
Igoritza said:
Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?
Click to expand...
Click to collapse
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Igoritza said:
This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?
Click to expand...
Click to collapse
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.
Begin12 said:
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.
Click to expand...
Click to collapse
Post in the desire x forum they will help you.
Sent from my HTC Desire using XDA Free mobile app
even my htc desire x has same problem
before this happened i dropped my phone 3 times in 2 months...but the phone was still normal..but suddenly it did'nt start then i gaved my phone to a private phone repairing shop..the man told me that therz a circuit problrm in the phone and difficult to fix it.....before it i tried by power+vol down but any option does not work..same it keeps on vibrating 7 times ...what should i do now...
Hello guys,
I was in Crete last week and on the last day I had the dumb idea to take the device into the sea. (I knew it was water-proof but I didn't know that I should not put it into seawater)......
Note: I never kept it underwater for more than a minute and only below the water surface and not lower. All closures were closed.
After ~10 minutes in the sea it started to behave strange: Display went black and it showed no reaction to any Actions. I took it out of the sea immediately and cleaned it with freshwater. After 5 more minutes it started to vibrate for around a minute. This happened a few times when I tried to turn it on again. Finally I was able to turn it back on but after a short time it auto-shutdown for this reason: "Emergency shutdown. Phone is to hot." (something like that at least). Strange. It was not in the sun and did not feel hot. Whenever I tried to reboot it it turned of during the sony boot animation. After that I opened all closures and removed the SIM Card and the microSD Card. They both had small water drops on it :S I kept the closures open and shaked it really hard a few times to make sure theres no water inside the phone.
3 hours later without touching it a single time I reinserted the cards and was able to turn it back on but it shut down itself very soon for a new reason: "SIM Card has been removed. Rebooting.." Well.. I did not remove the SIM Card. After a reboot it shut down again for the first shutdown reason (to avoid overheating).
Info: During all that reboots etc I was able to enter cwm recovery all the time.
Another few hours later I decieded to restore a CWM backup I created a few days before. I turned it on afterwards and it still "crashed" during the blue Sony boot animation.
Another few hours later I was finally able to start it. Everything seemed to work ok. But then the haptic feedback issues started: Sometimes it started to vibrate for no reason, sometimes it did not vibrate when it should have and finally it's not vibrating anymore. Not even during boot.
I aready found this thread: http://forum.xda-developers.com/showthread.php?t=2641694 where op described that it worked after shaking the phone. For me it's not working after shaking the phone.
Long text short question: Any chance to send the device back to amazon to get a new one? (I guess they can't detect that I put it into salty seawater?)
Edit: Forgot to mention that it had water fog inside the camera lens and the LED for a few hours...
Thanks for reading
[email protected] said:
Hello guys,
I was in Crete last week and on the last day I had the dumb idea to take the device into the sea. (I knew it was water-proof but I didn't know that I should not put it into seawater)......
Note: I never kept it underwater for more than a minute and only below the water surface and not lower. All closures were closed.
After ~10 minutes in the sea it started to behave strange: Display went black and it showed no reaction to any Actions. I took it out of the sea immediately and cleaned it with freshwater. After 5 more minutes it started to vibrate for around a minute. This happened a few times when I tried to turn it on again. Finally I was able to turn it back on but after a short time it auto-shutdown for this reason: "Emergency shutdown. Phone is to hot." (something like that at least). Strange. It was not in the sun and did not feel hot. Whenever I tried to reboot it it turned of during the sony boot animation. After that I opened all closures and removed the SIM Card and the microSD Card. They both had small water drops on it :S I kept the closures open and shaked it really hard a few times to make sure theres no water inside the phone.
3 hours later without touching it a single time I reinserted the cards and was able to turn it back on but it shut down itself very soon for a new reason: "SIM Card has been removed. Rebooting.." Well.. I did not remove the SIM Card. After a reboot it shut down again for the first shutdown reason (to avoid overheating).
Info: During all that reboots etc I was able to enter cwm recovery all the time.
Another few hours later I decieded to restore a CWM backup I created a few days before. I turned it on afterwards and it still "crashed" during the blue Sony boot animation.
Another few hours later I was finally able to start it. Everything seemed to work ok. But then the haptic feedback issues started: Sometimes it started to vibrate for no reason, sometimes it did not vibrate when it should have and finally it's not vibrating anymore. Not even during boot.
I aready found this thread: http://forum.xda-developers.com/showthread.php?t=2641694 where op described that it worked after shaking the phone. For me it's not working after shaking the phone.
Long text short question: Any chance to send the device back to amazon to get a new one? (I guess they can't detect that I put it into salty seawater?)
Edit: Forgot to mention that it had water fog inside the camera lens and the LED for a few hours...
Thanks for reading
Click to expand...
Click to collapse
if you are covered with warranty please do, it happened to me also (but this time i blame sony for lack of quality of service).. it happened when mine is still new i tried to wash it in the faucet then few hours later, haptic or vibrate doesn't work anymore, too bad i didn't have official warranty that's stupid on my part, but what do you know it supposed to be waterproof phone
Why didn't/don't you have official warranty? Country related?
It still doesn't work so I'm going to send it back. Ordered it on 31. January and had the Flash bleed bug also, if they accespt it and send me a new device this bug will be fixed also I guesss
Edit: Amazon wont take it, I have to contact Sony. Lets see what happens
Problem is covered by warranty!
They found the issue:
Please do not share this picture!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also added the "flash-bleed-bug" to the problems list - they detected it also!!
End of the story: I'm getting a new Z1 compact!
That's good news. I'm having the same issue with the phone not vibrating (or rather.. only when it feels like it) although mine has yet to be in water.
I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?
buugiewuugie said:
I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?
Click to expand...
Click to collapse
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.
sb1893 said:
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.
Click to expand...
Click to collapse
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.
buugiewuugie said:
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.
Click to expand...
Click to collapse
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also noticed from your link that my USB options look completely different than Oreo and Pie
sb1893 said:
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....
Click to expand...
Click to collapse
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.
buugiewuugie said:
I also noticed from your link that my USB options look completely different than Oreo and Pie
Click to expand...
Click to collapse
Ehhh - that article was from back in March 2018 so likely based on one of the developer previews of Android P....I'm guessing it evolved a bit since then from a visual standpoint - mine looks the same as yours does...
---------- Post added at 10:50 AM ---------- Previous post was at 10:47 AM ----------
buugiewuugie said:
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.
Click to expand...
Click to collapse
If you are unlocked I would just flash the latest factory image. Be sure to remove the "-w" from the flash-all.bat if you want to retain your data. (Although, depending on where that default preference for charging behavior is stored - retaining data may retain that "bad" default value as well.) Maybe try factory flash with retaining data first and see if it works...before doing the full factory flash and needing to reset up the entire phone and restore your data manually.
Another one bites the dust
Exact same problem with my Pixel XL.
It's difficult to charge the phone because every short power disconnect I have to manually choose "this device" again on else it won't charge.
I'm not rooted but bought it unlocked.
Grts
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
https://www.multitopicblog.com/usb-supplying-power-attached-device-pixel/#comment-133
Same Problem
I have the same problem with my Pixel 3 XL. Did you find a solution?
Just started experiencing this issue 8/1/2019 on a standard Pixel XL
Same issue, started in September. It's completely killed Android Auto for me and routinely leaves me with a dead battery. I've found mention of the issue all over the net but no solution. If anyone comes up with something, please share, it's driving me nuts.
Pixel 2 XL on Android 10 (QP1A. 191005.007.A1)
Downloaded a link from this article on XDA https://www.xda-developers.com/pixel-6-november-update-fingerprint-bug-fixed/
but didn't realise they had posted the wrong link and instead used the link for pixel 5a. Phone will connect and disconnect whenever i press power button or either volume buttons. Tried the usual force restart and bootloader button but still black screen and laptop not recognising phone except showing as USB serial device briefly when it does connect
muzab a said:
Downloaded a link from this article on XDA https://www.xda-developers.com/pixel-6-november-update-fingerprint-bug-fixed/
but didn't realise they had posted the wrong link and instead used the link for pixel 5a. Phone will connect and disconnect whenever i press power button or either volume buttons. Tried the usual force restart and bootloader button but still black screen and laptop not recognising phone except showing as USB serial device briefly when it does connect
Click to expand...
Click to collapse
I was messing around with my 6 Pro and ended up in recovery mode. None of the normal button combos were wrorking.
I ended up holding the power button / vol down for nearly 30 seconds and it rebooted back to the fastboot/bootloader mode.
Not sure if this will help you but the usual shorter time needed to boot wasn't working for me, but holding for 30 seconds did.
Good luck!
You could always try Official Google Pixel Update and Software Repair or Official Google Android Flash Tool.
Also, always go directly to the source Pixel 6 Pro Factory Images, don't trust anyone else's links.
didn't work but i can see it connecting and disconnecting constantly. did you have the device show up as USB serial device. Also what kind of cable did use (usbc to usbc?)
muzab a said:
didn't work but i can see it connecting and disconnecting constantly. did you have the device show up as USB serial device. Also what kind of cable did use (usbc to usbc?)
Click to expand...
Click to collapse
You might want to "Reply" or "Quote" the person you're responding to, so they get a notification that they're tagged and know that you have a question for them. I assume you're responding to @Az Biker.
When you have it plugged into your computer, do you see it in Device Manager? USB-C <-> USB-C or USB-A <-> USB-C shouldn't matter, as long as it's the original or a quality cable (Anker or from a previous PIxel or other quality OEM cable).
You can attach a screenshot of your Device Manager if you're not sure what you're looking for.
roirraW edor ehT said:
You might want to "Reply" or "Quote" the person you're responding to, so they get a notification that they're tagged and know that you have a question for them. I assume you're responding to @Az Biker.
When you have it plugged into your computer, do you see it in Device Manager? USB-C <-> USB-C or USB-A <-> USB-C shouldn't matter, as long as it's the original or a quality cable (Anker or from a previous PIxel or other quality OEM cable).
You can attach a screenshot of your Device Manager if you're not sure what you're looking for.
Click to expand...
Click to collapse
sorry , its showing as USB serial device (COM3) under ports section.
muzab a said:
sorry , its showing as USB serial device (COM3) under ports section.
Click to expand...
Click to collapse
No sweat! And it doesn't have an exclamation point through it's icon in Device Manager, right? (which would mean you need to install the latest Google USB Driver).
roirraW edor ehT said:
No sweat! And it doesn't have an exclamation point through it's icon in Device Manager, right? (which would mean you need to install the latest Google USB Driver).
Click to expand...
Click to collapse
nope no exclamation mark. google USB driver installed too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
muzab a said:
nope no exclamation mark. google USB driver installed too
Click to expand...
Click to collapse
Are you able to shut the phone off? If so, shut it off, wait 10 minutes, then try it again.
Follow Google's instructions exactly on the Official Google Pixel Update and Software Repair or Official Google Android Flash Tool web page.
Try another USB port.
Try another USB cable.
If a desktop PC, try one on the back instead of the front - although I think this has been making less and less of a difference in recent years.
Try rebooting the PC/laptop.
Have a spare PC/laptop to try fresh?
roirraW edor ehT said:
Are you able to shut the phone off? If so, shut it off, wait 10 minutes, then try it again.
Follow Google's instructions exactly on the Official Google Pixel Update and Software Repair or Official Google Android Flash Tool web page.
Try another USB port.
Try another USB cable.
If a desktop PC, try one on the back instead of the front - although I think this has been making less and less of a difference in recent years.
Try rebooting the PC/laptop.
Have a spare PC/laptop to try fresh?
Click to expand...
Click to collapse
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
muzab a said:
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
Click to expand...
Click to collapse
I think it's time that you need to contact Google, unfortunately. Unless someone else has some better ideas. Sorry to hear.
muzab a said:
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
Click to expand...
Click to collapse
Try just power button for 30-45 seconds.
Long shot idea here.
Plug the phone into the charger, see if you get a charging symbol (indicating it is off).
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Like I said, long shot idea..
Best of luck!
Az Biker said:
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Click to expand...
Click to collapse
I agree. I have definitely had to do something similar, I believe with my LG G3 once or twice. Had to turn it off or let it die, then leave it alone for a while. Sounds crazy, but whatever works...
roirraW edor ehT said:
I agree. I have definitely had to do something similar, I believe with my LG G3 once or twice. Had to turn it off or let it die, then leave it alone for a while. Sounds crazy, but whatever works...
Click to expand...
Click to collapse
When they switched to non-removable batteries and you had to let it die instead of simply pulling the battery
Good times
Az Biker said:
Try just power button for 30-45 seconds.
Long shot idea here.
Plug the phone into the charger, see if you get a charging symbol (indicating it is off).
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Like I said, long shot idea..
Best of luck!
Click to expand...
Click to collapse
Thanks will try this. I have spoken to google to get a replacement but hopefully i can get this current one working again
This isn't the kind of mis-flash I'd expect a phone to survive. Pixels tend to accept whatever firmware you throw at them with practically zero version or compatibility checks. In your case, going from a Qualcomm to a Samsung bootloader is likely fatal.
I'm surprised it even shows a device. Maybe a rescue path, but I wouldn't even know where to begin with drivers if generics aren't good enough. If you aren't getting a "fastboot devices" response, that's game over. How did you flash this in the first place? How far did it get?
just a heads up, that link under pixel 6 pro Global is still incorrect and is pointing to pixel 5a
LLStarks said:
This isn't the kind of mis-flash I'd expect a phone to survive. Pixels tend to accept whatever firmware you throw at them with practically zero version or compatibility checks. In your case, going from a Qualcomm to a Samsung bootloader is likely fatal.
I'm surprised it even shows a device. Maybe a rescue path, but I wouldn't even know where to begin with drivers if generics aren't good enough. If you aren't getting a "fastboot devices" response, that's game over. How did you flash this in the first place? How far did it get?
Click to expand...
Click to collapse
wasn't familiar with the p6 pro codename so when i used the link under the XDA article i guess i didn't pay attention to the name of the file. Lesson learnt
Reported it and it's fixed now.
@muzab a
Kindly share the hardware ID of the USB Serial Device.
Since the Pixel 6 family's Google Tensor silicon is somewhat based on the Exynos chipset, it could be possible to use the Exynos hard brick recovery method to revive the device (context: 1, 2).
If possible, initiate the replacement process. But discovering a community-supported method for unbricking these devices would be great. For your information, we never got our hands on the low-level firmware packages for the older Pixels with Snapdragon family of SoCs.
Friends,
First I apologise for the WOT.
Background:
My OP 3 died on me last week. It was working at 3.00 pm, I went for a nap and at 4.00 pm woke up to see my phone with a black screen. My volume down key isn't working from even before. I use Havoc OS, TWRP, rooted with Magisk and no modules. Since I am bootloader unlocked, I use the startup screen using the volume up key to navigate between recovery, fastboot etc because of the volume down key not working. My device had roughly 70% charge when it died. Fortunately I had completely backed up my data from the phone to the laptop the previous week along with a TWRP backup.
What I tried:
Connecting it to the charger starts the screen but after the OnePlus logo it starts bootlooping. So not charging even if left on the charger for extended periods of time. Starting with the power button results in identical behaviour. While connected to the charger, from the startup screen, I am able to choose the bootloader and sort of boot into bootloader. But if the charger is unplugged, the phone dies. So not able to use fastboot.
Using the charger, from the startup screen, I am able to choose Recovery (TWRP) but after the OnePlus logo, the TWRP screen flashes and then the phone starts to bootloop. If charger is disconnected, phone dies. So not able to use recovery too.
When trying to hold volume up button for 10 seconds and connecting to laptop, the 9008 driver flashes for a second in Device Manager and vanishes. Phone is not otherwise recognised on laptop even as a charging device. When trying to charge on laptop, the phone behaves as it did on the regular charger ie. bootlooping.
If the MSM tool (version 3.0 and 4.0 as Administrator) is running (with the start button clicked) when I connect the phone holding the volume up button for 10 seconds, it starts the download and then (in one second) in the Tool, I get the message "Try Firehose communication handshake". Then the laptop freezes and I can switch off the laptop only by holding the power button down for 8+ seconds. I have tried both USB 2.0 and 3.0 ports with the same result.
The fact that the laptop freezes makes me suspect a short somewhere. I have ordered a new OP 9 Pro and it was delivered today. Now is there anyway of resurrecting my OP 3 without changing the motherboard?
Thanks in advance for any suggestions.
TNSMANI said:
When trying to hold volume up button for 10 seconds and connecting to laptop, the 9008 driver flashes for a second in Device Manager and vanishes.
Click to expand...
Click to collapse
I remember such behaviour from my OnePlus One back in the day. I solved it by trying numerous different drivers, A LOT of trial and error. But considering it's a 6 year old device and you were still using it as a daily driver, I'm afraid it's not software – as you've also hinted at. I hope it'll be a fun hardware project though! Not my cup of tea ^_^
Update:
Visited OnePlus service center. They initially said that it was only a question of flashing the software and asked me to wait while they flashed it. One hour later, I was informed that an IC in the motherboard seemed to have shorted and that they no longer stock the motherboard of OP 3. Even if they had stock, I was not going to buy it since it simply is not worth that much money to revive a 6 year old phone. Using it as a paper weight now.
End of story.
Sorry to hear that, mate...
Spoiler: RIP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}