Hi there, I've been lurking for hours in the forums and I figured that I can't seem to find the solution to my problem
I have an OG Pixel XL, I opened chrome earlier to browse about a company, when I opened google chrome, the screen froze and there's some weird rectangle pixel all over the place. I long pressed the power button and now my phone is stuck on a boot loop. I've tried going to recovery mode but it just goes back to the boot loop. I've installed adb and fastboot to flash a factory image (I think) but it just says that OEM needs to be unlocked. I can't seem to find a way to unlock OEM and now I'm stuck with a phone, out of warranty, in a bootloop, forever.
Any help and ideas to fix my phone would be greatly appreciated
blackdigits said:
I have an OG Pixel XL...
Click to expand...
Click to collapse
In the future, you should ask this in your device's forum - you asked this in the Pixel 2 XL forum - as solutions to problems may differ from device to device.
In any event if you cannot access the recovery via keypress or command, you're stuck. You'll have to pay for the privilege of having the device repaired. If you CAN get into the recovery, you can sideload a full OTA image, which supposedly bypasses the OEM lock on the bootloader, to restore the device.
Related
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
This happened to me, I was not able to solve the issue, even though I could push and pull data to and from the device via ADB. I could still not get past the google logo. I decided to lock the boot loader again and return to the store for a new device.
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
Sent from my Galaxy Nexus using XDA App
hartford said:
So I am the proud owner of a shiny, new Galaxy Nexus (GSM). Unlocked the bootloader and installed CWM recovery and was doing great. Today I decided to install the volume fix. Installed the zip through recovery, completed and rebooted. The phone got stuck in a bootloop over and over and over and over and would not boot Android at all. Did a ton of research here and everywhere and, in a panic, I booted into CWM recovery, reset the cache & did a full factory reset. NOW, the phone will not go past the Google bootscreen with the unlock symbol, no matter what I do. AND, I can't even flash the original google image because I can't get in to set USB debugging so my computer won't even recognize the phone (FYI, I'm on a Mac). I am at a complete loss and don't know what to do. If I could only get the computer to recognize the phone I could flash the original google image through Terminal, but alas, I can't. Any ideas? If I can somehow get this phone back up and running I would be eternally grateful. For now, I think I may be SOL. Thanks....
Click to expand...
Click to collapse
One more post like this in Dev section and you'll be banned for 3 weeks
ORIGINAL PROBLEM:
Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with bouncing dots. That was 55-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Here > http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156/page57
cam30era said:
@n3far1us,
A lot of discussion on SuperSU thread about this, but few answers yet.
Thank you @cam30era for sending me to the right direction. Did not realize I needed to look into SuperSU thread for this. I was searching in the wrong areas.
Click to expand...
Click to collapse
Same issue here
Same issues here after taking V update which completed then immediately flashed elemental kernel then rerooted which said ok now stuck on jumping dots for atleast an hour? Any ideas how to fix this I followed the directions of a dveloper on here and it screwed me!
QUOTE=n3far1us;69558628]Pixel XL 128gb VS, received this morning with 63L.
1) Enabled debugging and OEM unlock.
2) Took the update as everyone said 63V is ok. But it turned out to be 63X(?) (I am on VZW network but phone purchased directly from google).
3) Used adb to get into bootloader mode and unlocked bootloader, which reset my phone and started fresh.
4) Enabled debugging again, OEM unlock was greyed out this time.
5) Rebooted, a message popped up something like 'needs to be locked to verify update' then google screen with unlocked lock symbol in the bottom.
6) Robooted again just to test. Still showed same thing, everything else seems to be working fine.
7) went back into adb mode and did fastboot boot boot-to-root.img
8) adb said successful
9) Phone restarted and showed the screen with jumping dots. That was 40-ish minutes ago. Nothing else happening, but the screen with jumping dots.
Anyway to fix it or am I screwed?
Edit: Just tried and see if adb recognizes it now, nope.[/QUOTE]
@kirschdog1,
Follow the SuperSU thread that I referenced above.
On it now but it doesnt look like anyone has an answer for us!
cam30era said:
@kirschdog1,
Follow the SuperSU thread that I referenced above.
Click to expand...
Click to collapse
THE FIX
After about 6 hours of bouncing dots and trying out various things, @dowlf finally saved my life.
To recover the phone, I followed-
1) Boot to bootloader
2) Select 'Recovery' then once in recovery hold power and vol-up buttons for 5 sec then let go of the vol-up (but keep pressing power)
3) From there, choose Apply Update from ADB
4) Run 'adb sideload blahblah.zip' (mine was 63X OTA)
5) Choose 'Reboot system now' once copying done.
THE ROOT
After figuring out how to fix it, I immediately went back trying to root it again.
However, this time I decided to do more research and it appeared that I may have used an outdated boot-to-root.img which kicked off the bootloop. The first file was dated 10/31 and the second one I found was dated 11/03. I decided to try the 2nd one this time with "fastboot boot" command and voila!
My Pixel is successfully rooted on 63x!
Thanks to @Chainfire for all the hard work!
Oh and this is the link where I found the second file from-
https://plus.google.com/+Chainfire/posts/24xhJN724HG
Please help!
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Try flashing everything manually.
Sent from my Pixel XL using XDA-Developers mobile app
YankelMyWankel said:
Guys I have a 32gb Pixel XL from Verizon, I unlocked the bootloader, and today I tried the boot-to-root and now i'm stuck on the bouncing dots, I've downloaded the OTA update, tried the flash-all script, didn't work, failed out at one part,
i tried sideloading the ota.zip and it said failed to sideload ota.zip and i'm FREAKING out i just bricked this phone...
PLEASE ASSIST. My phone is my livelyhood for my job and without it i'm screwed.
Click to expand...
Click to collapse
Make sure you have the latest android SDK for adb and fastboot or it won't play very well
Sent from my Google Pixel XL using XDA Labs
alright, so i got stuck in ALMOST same situation, rooted my device got stuck on dots.
googled my problem and found this thread and found it more helpful, the only thing creating confusion is the OTA required.
got my device on 11th of this month and i guess started using it on 12th or 13th, and when i turned it on it asked me for updates and straight away i downloaded all the updates, but unfortunately i forgot to check what build number i was on.
so could you guys please help me out with the OTA version?
shall i go with the latest one?
and the rest is the same right?
like after sideloading the OTA file my device will be back to stock and unrooted ?
OKAY SO I'VE SOLVED MY PROBLEM BY JUST INSTALLING OTA WITH SIDELOAD COMMAND.
Thank you for the solution guys.
Hi All,
My Nexus 5x 32 GB phone suddenly died on me last night. The situation as of now:
1. Cannot boot normally. Shows Google logo and everything goes dark.
2. Can boot into Fastboot with holding down power and volume down buttons
3. But not able to go into recovery. When I select Recovery in Fastboot mode, it just tries to reboot and the screen stays dark. Nothing happens.
4. The bootloader is locked. I think OEM protection in Developer tools is on, so not able to unlock bootloader through Fastboot commands.
What an I do?? Factory reset would be great, if option is there.
Please help!! Thanks.
Try to flash Factory image by command adb and fastboot if your pc recognized your nexus 5x
unlock oem if necessary After
Funny enough, I've got a very similar issue
I can boot into recovery though, but there's a catch, and I think it applies to everything past boot, the phone freezes and restarts after like 3-5 seconds.
I can't boot to system, as it takes way too long to boot up, but I can only see the first panel of the recovery before it dies and restarts.
I have flash official images, and even TWRP recovery to see what I can do, but this doesn't work out in the long run, as the issues are ever persistent
Thanks for the quick replies!
Tried everything, including Nexus toolkit... But nothing worked. So I finally took it to service center as its still in warranty. They said the problem is hardware related and it might have happened because of recent update. They also said they have been getting lots of phones with this problem. So they they are replacing the motherboard free of cost. Wish they could have given a new phone
Once again, thanks all!
Dude that's wild, this same exact issue literally happened to me 2 weeks ago while I was on tour. Was on 7.1.1 (Pixel ROM to be specific) and my 5X just died on me out of nowhere. Absolutely the same things happening here, would boot up, go black, and then start bootlooping. Could access fastboot, but I couldn't get into recovery. Called Google and got a replacement because it was definitely hardware failure and I was still under warranty (just a few days past a whole year). I wonder if the new 7.1 betas are breaking peoples' phones
Sent from my Nexus 5X using Tapatalk
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Scratch. said:
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Click to expand...
Click to collapse
Have you tried flashing the stock images? If you can get to fastboot, you can flash the stock image and unroot your phone. You should also then be able to lock your bootloader (if it is unlocked) and then do your warranty at that point.
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
so people saying android 7.1.1 brooking devices, so will that be safe to upgrade the phone from 7.0 to 7.1 .1 when stable release will be available ?
Scratch. said:
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
Click to expand...
Click to collapse
Sounds like the hardware bootloop issue that has been hitting 5x devices hard lately. Mine started looping last week and I had to send it in.
Are you still within your 1 year manufacturer's warranty? If so, you can call LG and report the issue to them. Your device may get fixed, but it was also reported Thursday that LG has started issuing full refunds because they ran out of the needed part.
The company have started offering refunds
https://www.neowin.net/news/lg-to-issue-full-refunds-to-customers-with-faulty-nexus-5x-handsets
So i followed the root guide on the pixel 3a forums by accident (google brought that instead of 3aXL)
Did the whole, flash magisk_patched.img root method, and now im getting a bootloop/no command.
My fault, i know. I cant seem to get it into fastboot (button command?)
any fixes? can i install the whole OS as new or does google only offer the boot.imgs now? another option is i have a pixel 1 with magisk. could i patch the proper image on that device and then take that image to flash this one?
im assuming they have different boot images and thats where my mistake is. Unless they're the same. In which case i'm lost.
any help would be greatly appreciated.
AlPoo said:
So i followed the root guide on the pixel 3a forums by accident (google brought that instead of 3aXL)
Did the whole, flash magisk_patched.img root method, and now im getting a bootloop/no command.
My fault, i know. I cant seem to get it into fastboot (button command?)
any fixes? can i install the whole OS as new or does google only offer the boot.imgs now? another option is i have a pixel 1 with magisk. could i patch the proper image on that device and then take that image to flash this one?
im assuming they have different boot images and thats where my mistake is. Unless they're the same. In which case i'm lost.
any help would be greatly appreciated.
Click to expand...
Click to collapse
I would flash the latest stock image and verify operation before doing anything else...
The "No Command" screen you are seeing I think is the recover screen. It shows a green android laying on it's back with a access panel open and a red caution icon above it, correct?
If so, you can press the power button, then while still pressing the power button press the vol up button and release. This should bring up the option available in recovery.
In recovery you could try a factory reset and see if that allows the phone to boot. If it doesn't then you will have to flash a stock OS version using ADB and your computer.
Hi I have a pixel xl that I bricked. Ill give you a quick history of what I did. I had this phone rooted with magisk and on LOS and it is my backup phone that I play with. I had to send my pixel 4 xl in for a warranty exchange. So I had to use my pixel xl for a few days and I decided to return it to stock and lock the bootloader. So I did that but magisk seems to have persisted through the process of returning to stock and the phone worked fine I just got the message that the device has a different operating system installed and I still had root. Anyway I now have the pixel 5 and I was playing with my pixel and it just started boot looping and the phone gets really hot. It could just be that the hardware crapped out.
So I was able to unlock the bootloader and use fastboot to boot twrp and mount the system and I copied the twrp installer over and tried installing it. It did not work and I think i wiped out all recoveries because now when I try to boot recovery it just goes to boot the system like there is nothing there at all. Oh and I tried booting back to twrp and wiping everything. So that's where I'm at now and not sure what to try next. Do I use fastboot to boot into twrp and download the last ota file and sideload it? I'm open to any suggestions that anyone might have.