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.)
Related
So I have a RAZR MAXX HD that has been rooted running Cyangenmod 10.2 and bootloader unlocked for a few months now. But the last couple weeks, each time I plugged phone up to charge, it kept starting a reboot loop. Each time it reached the start of Cyanagenmod boot logo, it restarted. So I thought maybe it was a bug in the latest Cyangenmod. So I tried updating. But I didnt realize that I accidentally chose Cyangenmod 11, thus when it was installing in Clockwork Mod Recvoery, it errored out about 1/3 of the way through. This erased everything.
So I was going to try hooking up to my MacBook and using fastboot to load new OS. However, as soon as i plugged in my phone, my computer shut down and would not turn back on. Had to go to Apple store to do a hard SMC reset. Thought that was a fluke and tried using my computer again and same thing happened. Phone still has CWM recovery working (i think properly). How do I get a working phone again? I tried putting OS on SD card on another phone and putting SD card my MAXX HD in and trying. That installed OS fine but when i rebooted, it still would not go past "bootloader unlocked" warning screen.
Also, I tried once more to plug in to my computer once more last night. However, it did not shut my computer down, but I did get a warning from OSX to unplug the USB device that was consuming too much power.
Any help would be appreciated! Thanks!
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
bweN diorD said:
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
Click to expand...
Click to collapse
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
vol4life27 said:
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
Click to expand...
Click to collapse
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
bweN diorD said:
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
Click to expand...
Click to collapse
Thanks man.. Yea i was kind of thinking the same thing but wasnt too sure. Maybe I can go somewhere locally and see if they can repair it for cheap. After having a phone that goes 1.5 days on one charge, I got spoiled. LOL plus I love the build quality much more than most oter phones like S3/4 etc.
So I'm on my second M8 (first one had some build issues). Only had it about a week and have hardly been using it since I haven't had time to transfer everything from my old phone. To that end, I haven't charged it much, and when it has been charging I haven't really been paying attention.
Today I am paying attention and it is saying that it is "slow charging" and that I should use the supplied adapter and cable.
I am using the supplied adapter and cable. I'm completely stock running only weaksauce (no S-Off, bootloader unlock, etc).
I had USB debugging on, turned that off. I've rebooted the phone, no difference.
I get the error message whether the phone is on, or turned off at only the charging screen.
I've tried some other adapters and get the same results.
Ideas?
TraderJack said:
So I'm on my second M8 (first one had some build issues). Only had it about a week and have hardly been using it since I haven't had time to transfer everything from my old phone. To that end, I haven't charged it much, and when it has been charging I haven't really been paying attention.
Today I am paying attention and it is saying that it is "slow charging" and that I should use the supplied adapter and cable.
I am using the supplied adapter and cable. I'm completely stock running only weaksauce (no S-Off, bootloader unlock, etc).
I had USB debugging on, turned that off. I've rebooted the phone, no difference.
I get the error message whether the phone is on, or turned off at only the charging screen.
I've tried some other adapters and get the same results.
Ideas?
Click to expand...
Click to collapse
I've seen this twice and heard about it once, first time was where I didn't have the usb cable properly plugged into the adapter (might not be your case since you tried different adapters, but you never know) and a second time when I didn't plug in the adapter correctly and only had one prong in the socket lol not sure how I didn't cause a fire that time cause it took me awhile to figure out. (I think you're smarter than I am so this is highly unlikely )
And lastly my cousin had the problem and his was due to a bad usb cable.
The Stig 04 said:
I've seen this twice and heard about it once, first time was where I didn't have the usb cable properly plugged into the adapter (might not be your case since you tried different adapters, but you never know) and a second time when I didn't plug in the adapter correctly and only had one prong in the socket lol not sure how I didn't cause a fire that time cause it took me awhile to figure out. (I think you're smarter than I am so this is highly unlikely )
And lastly my cousin had the problem and his was due to a bad usb cable.
Click to expand...
Click to collapse
Definitely not due to cables being in wrong.
I also tried another 10' 24/28 awg cable I got and the same thing.
It may be the charger, and I think I am going to try to hit up the Verizon store tomorrow and see if I can try one of theirs.
In the meantime, I have access to iPhone/iPad chargers. Can anyone confirm that they don't get the "slow charge" message when using one of these? If so, and I get it on that as well, then we may have an issue.
Ok, I just did a factory reset on my phone and it appears the problem has gone away.
I'm not sure why this would have done it.
I did the following to my phone originally:
1) Rooted with weakauce/SuperSU
2) Attempted to S-off with firewater (unsuccessful)
3) Installed sunshine to test, but did not go through with it to s-off (i.e. pay).
Apart from that, all I have done was install a handful of apps from the store.
I am going to try and recreate what I previously did and see if the issue reoccurs.
UPDATE:
So, things looked fixed after the reset. I re-rooted and loaded some things onto the phone and everything appeared fine.
I then decided to plug my phone into my juicing brick (RAVPower RP-PB17).
As soon as I did that I got the message again that it was slow charging (even though this is 2.1A charger).
After that, I continued to get the message regardless of what I plugged it into to charge...even the original charger..even after a reboot.
I was going to test this again by doing another factory reset and then plugging back into the RAVPower to see if that caused the problem. Before I did that, I looked around and found what is apparently a battery reset procedure documented in several places. The most "official" place I could find it documented was here:
http://support.t-mobile.com/docs/DOC-10943
Basically you hold both volume and the power button down for about 1-2 minutes while connected to the HTC charger. Sure enough, this seemed to clear the "slow charge" indicator again and now whatever I plug it into (including the RAVPower) seems to work fine.
I'm going to call HTC back and see what they say about this.
UPDATE:
Called HTC and told them what happened... that the phone was giving me "slow charge" until I factory reset it, and then started giving it again after I plugged it into my juicing brick.
I then told them about the re-calibration procedure I found and performed and that how now the device appears totally fine regardless of what charger I use.
I told them I was concerned because it was a new phone and asked them to explain why it was necessary. I also asked them if they had anywhere on their site, or publicly available a document explaining the re-calibration procedure and under what conditions it was necessary.
The girl I spoke to was really worthless (more than the guy I web-chatted with who just said "return it"). She said there is no public facing documentation on how to perform the re-calibration. She couldn't explain why I had the problem. Really all she could do was offer a repair/replacement.
I believe I'm still within the return period with Amazon - but I've already returned my first M8 due to build issues. I'm happy with the build quality of this one, but concerned that I had these charging issues already.
Should I return it and hope for a 3rd one with no problems?
I was having the slow charge issue for the past couple of days and tried everything suggested including a factory reset, different chargers, different cords, everything and still could not get my phone back to normal. I then took a really close look at the USB port on the phone and noticed pocket lint in there. It was preventing the plug from seating the whole way and would only slow charge.
To clean it, I shut the phone off and used a small safety pin to get the lint out. After that my charger is working normally again.
jsaxon2 said:
I was having the slow charge issue for the past couple of days and tried everything suggested including a factory reset, different chargers, different cords, everything and still could not get my phone back to normal. I then took a really close look at the USB port on the phone and noticed pocket lint in there. It was preventing the plug from seating the whole way and would only slow charge.
To clean it, I shut the phone off and used a small safety pin to get the lint out. After that my charger is working normally again.
Click to expand...
Click to collapse
Thanks for this. I'd been having this problem for weeks now. I took a small pin and pulled out a TON of lint from in the charger port. Now all is good. Thanks again!!!
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
My Nexus 5x was bought by May 15 2018, i was excited for this phone, but i never knew about all the issues it is inclined to have.
EP 1:
It started with this simple notification that started to appear randomly without any solid cause.
"USB supplying power to attached device"
I tried a couple of fixes, like cleaning the usb port, Factory and Cache wipe, and nothing worked, it was just becoming a real annoyance.
EP 2:
The next day, after i did the factory reset and realized there was nothing different about the issue, i put it to charge, moments later i tried to turn it on but i realized it wouldn't go past the google screen, google screen was just rebooting constantly, it was at this moment i got acquainted with our fellow bootloop.
I started investigating, talked to a couple of people and they recommended flashing.
At that moment i could access bootloader, and recovery...
Ok, i turn it off.
After a while, when im ready to flash, cant access recovery.
Bootloader is accesible, but oem is locked and wont allow.
Later i finally found what could be the way of solving the issue.
And i could sleep peacefully that night.
EP 3:
Now, on top of all the complications, the fatality:
Next morning.
It wont even turn on into bootloader.
But i do see that it is charging, however; it wont turn on.
Is there some way of booting it connected through the pc ?
I think i wont be letting this problem like this anytime soon, im still up and willing to find a way to solve this.
If it's still early, just return it for a refund the Snapdragon 808 and 810 are infamous for problems 9 times out of 10 for not being soldered to the motherboard properly so I would advise to return for refund or replacement
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