Related
Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.
Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app
Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk
I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?
I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.
Have you found any solution?
vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
mrafee113 said:
I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
Click to expand...
Click to collapse
Can you boot into the stock recovery? Try sideloading the latest Oreo update zip. I'm not sure that will do anything, but worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
mrafee113 said:
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
Click to expand...
Click to collapse
No, it shouldn't.
Sent from my [device_name] using XDA-Developers Legacy app
Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.
blueren said:
Hello.
Yesterday my pixel xl (non-carrier-locked model) suddenly rebooted and got into a bootloop. It never gets past the white google loading screen.
It's fully stock, running the latest Pie + update. Bootloader is locked and the allow oem unlock in developer mode is also disabled.
I though I could just get into bootloader and swap the active partition using fastboot --set-active=(a or b) whichever works. But I soon realized that this is not allowed when the bootloader is locked. I can't unlock the bootloader using fastboot flashing unlock because oem unlocking is disabled in the developer settings. I can't obviosly get to the developer options without getting my phone to boot.
As an alternative I thought I could simply factory reset / erase user data from the recovery. However, when I try to get into android recovery from the bootloader, the phone reboots!
Things at the moment are looking grave. I don't have much data to lose on the device. What are my options given this predicament?
Thanks.
Click to expand...
Click to collapse
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?
same issue happeend now to me. any updates?
hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.
Apologies for such a long delay in my response.
Phalanx7621 said:
Have you tried rebooting with Volume down+ power held in? Or has the battery died? Also what exactly were you doing when this happened?
Click to expand...
Click to collapse
ferydaboss said:
same issue happeend now to me. any updates?
Click to expand...
Click to collapse
godkingofcanada said:
hey whats weird... ive got the same issue, December security patch stock pie....
---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------
ive tried other stock pie, stock oreo, custom kernels, I cant even boot into twrp... anything I try to boot up it just bootloops.
Click to expand...
Click to collapse
The only thing that loads up fine is the bootloader menu via vol down + power. I can't even get into the recovery from there. When I do, the phone simply reboots and continues it's bootloop.
I've already tried reflashing the latest stock rom on both the slots. Still no juice. The same thing happens. Powers on, I see the white google logo screen with the small unlocked icon to the bottom. Then reboots into the same screen forever. I thought doing a clean flash would most certainly fix this issue. But seems like I was wrong.
Looks like hardware (eMMC, main board) fail, not soft brick...
Hi there,
Did anyone tried to heat their phone a bit with a hair dryer or something to see if the phone boot? Could be another bootloop fiasco similar to LG crap and Nexus 6P chip solder getting loose?!
People got their Nexus 6P temporary booting heating the device...
If nothing else works, you guyz could try it? ?
Good luck...
I gave up. I opened the phone and looted it for parts.