My phone is gone into LOOPMODE only showing GOOGLE , and no OEM enabled , no USB debugging Enabled also DEVICE state is LOCKED...
please help me to restore my set.
how to Unlock the bootloader or how to enable USB debugging ?
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
First off , thankyou for replying
sconno said:
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
Click to expand...
Click to collapse
yeah sure, i m on HOLD , i have tried all things such as adb, nexus toolkit and all adb commands .
Reply soon bro !
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
r3act said:
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
Click to expand...
Click to collapse
but how to unlock bootloader , thats the problem bro ! i have done evrytthing to do so !
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
sconno said:
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
Click to expand...
Click to collapse
but i think my Android is corrupt , it showing only google when i press and hold the power button.
give me another solution bro !
And anyone from MUMBAI (BORIVALI WEST)
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
harihacker said:
Try this. It worked for me on 2 devices.]
Thanks for this, I am going to give this a go with a heat gun later on today.
Click to expand...
Click to collapse
harihacker said:
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
Click to expand...
Click to collapse
lol , I think my Phone is dead RIP .
Related
Hi guys, my HTC is stuck in a bootloop after trying to update Cyanogenmod 13. I fixed the error before (by wiping the data via ADB) but I stupidly decided to re-attempt to install the latest update and guess what? I did it again - only this time, the developer options weren't enabled.
So now I currently have a bootlooped HTC with no authorisation to do anything through the ADB shell, so is there any way to authorise my phone since I can't physically use it?
Cheers
(Also how do I get it back to HTC Sense?)
musta_001 said:
Hi guys, my HTC is stuck in a bootloop after trying to update Cyanogenmod 13. I fixed the error before (by wiping the data via ADB) but I stupidly decided to re-attempt to install the latest update and guess what? I did it again - only this time, the developer options weren't enabled.
So now I currently have a bootlooped HTC with no authorisation to do anything through the ADB shell, so is there any way to authorise my phone since I can't physically use it?
Click to expand...
Click to collapse
Just boot into bootloader by holding vol down as it bootloops. Then boot into recovery (TWRP?) and wipe data there.
Or re-flash CM or restore TWRP backup, if needed.
musta_001 said:
(Also how do I get it back to HTC Sense?)
Click to expand...
Click to collapse
Just flash a Sense ROM. Or restore your TWRP backup from before you flashed CM, or from the stock nandroid collection.
redpoint73 said:
Just boot into bootloader by holding vol down as it bootloops.
Click to expand...
Click to collapse
Yeah the problem is that when I try doing that, the phone resets and goes into some black flashing screen now in 4-5 second intervals. I also tried booting it into bootloader using my computer but as I said before, it won't let me due to USB debugging not being enabled beforehand
musta_001 said:
Yeah the problem is that when I try doing that, the phone resets and goes into some black flashing screen now in 4-5 second intervals. I also tried booting it into bootloader using my computer but as I said before, it won't let me due to USB debugging not being enabled beforehand
Click to expand...
Click to collapse
Doesn't matter whether USB debugging is on or not, since adb commands only work in OS or recovery (neither of which are available). Fastboot commands only work in bootloader-fastboot mode (debugging not needed). So if you can't get into bootloader, you're pretty much screwed on both counts (adb and fastboot).
I've seen a couple reports like this on the forum, where trying to get into bootloader results in black screen, then a reboot. Don't think there was ever a solution found, sorry to say.
redpoint73 said:
Doesn't matter whether USB debugging is on or not, since adb commands only work in OS or recovery (neither of which are available). Fastboot commands only work in bootloader-fastboot mode (debugging not needed). So if you can't get into bootloader, you're pretty much screwed on both counts (adb and fastboot).
I've seen a couple reports like this on the forum, where trying to get into bootloader results in black screen, then a reboot. Don't think there was ever a solution found, sorry to say.
Click to expand...
Click to collapse
Well looks like I found the fix XD
I held down the power button and BOTH of the volume buttons at the same so that the phone resets. I kept hold of it until the phone booted to the lockscreen. From there I enabled USB debugging and went to flash the stock ROM.
musta_001 said:
Well looks like I found the fix XD
I held down the power button and BOTH of the volume buttons at the same so that the phone resets. I kept hold of it until the phone booted to the lockscreen. From there I enabled USB debugging and went to flash the stock ROM.
Click to expand...
Click to collapse
Very interesting. That combo is known as the "battery reset" or something to that effect. I'm not sure why/how that would have helped your problem, but I'm glad to see something did!
I suppose the moral of the story, try all button combos before giving up!
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Edit: When I try to run "fastboot flashing unlock" I get "FAILED (remote: oem unlock is not allowed)"
Pattond said:
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Click to expand...
Click to collapse
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options.
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Returned with
FAILED (remote: oem unlock is not allowed)
PiousInquisitor said:
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Click to expand...
Click to collapse
SHA256 Checksums on bullhead-ota-mtc19t-4ea6522b.zip match. When sideloading, at about 50% the phone says
"Warning: no file contextsThis package is for "bullhead" devices: this is a " ".
"E:Error in /sideload/package.zip
(Status 7)
Installation Aborted"
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
I'm going to try that now.
You can use the Nexus root toolkit, manually put the phone in bootloader and click OK to get past the "enable debugging window". It's asking you to do that so it can reboot the phone itself into bootloader.
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Pattond said:
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Click to expand...
Click to collapse
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Pattond said:
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Click to expand...
Click to collapse
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Click to expand...
Click to collapse
All good, got it to 6.01, no internal error message on boot. I did the OEM unlock as you suggested, then let WugFresh's Nexus Root Toolkit take it from there. Thanks!
Damn I'm in the same situation but it will actually boot all the way to the lock screen and as soon as I put in my password it reboots. It actually will reboot regardless after sitting on the lock screen for about 10 seconds.
I really really don't want to lose everything on the phone. I have the factory image and can unzip it and manually install parts. I just don't want to wipe the data. Bootloader is still unlocked and I had oem unlock option enabled prior.
PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
Ok, i feel really stupid asking this.....WHAT ARE YOU TALKING ABOUT WHEN YOU SAY "FLASH" THE LATEST FACTORY IMAGE????
Ive been stuck in a boot loop for 3 days now. it only gets as far as the "google" logo before rebooting agin and again and again and again....:crying::crying::crying::crying:
I tried to root my phone last night, but I stop midway of the process because of some problems like "phone not turning on with no vibrate at all when I restart after its stuck to inverted white screen, when I luckily turn it back on but it bootloops".
Heres the details:
I run unlock.bat then after its done it reboots with inverted white screen with logo then I run restore.bat and after it restart there is no sign of warning "failed verification" until it fully loads up, I go back to fastboot again to flash TWRP after running twrp.bat it says "flash succesfully" and the program closed by itself, then I go to recovery mode after rebooting I saw android error just like how it use to be. I press power button + volume up then release the volume up then I see the stock recovery (which it should be TWRP since I've done flashing it).
I think that my bootloader is still locked since there's no warning display of "failed verification". So I repeat the steps again after running unlock.bat, it reboots and the screen is inverted but it's stuck up to white logo, I waited for a while but nothing happens so I tried to reboot my phone "holding power button (power off)" when power on, it wont turn on, no vibration just a sound on laptop "connected sound and disconnected sound" I tried to power it on many times but still no luck I got panicked, jittery walking back and forth :crying:. Then I disconnect the usb cable and I tried to turn it on and suddenly I feel the vibration on my phone then it boots up but still stuck in white screen then it restart after keeping it for too long (while watching videos related to my problem)...
then my friend here said "ohh it bootloop" he read the instruction and he said to try this
"FAQ 1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode."
and it solve my problem my phone is working again ... But I want to continue to root it but I'm afraid which steps I should go next, I still don't see the warning "failed verification" after my phone boots up and works again... I need HELP thank you
I also got question: is my bootloader unlock since it inverted white screen? or it still locked since there no sign of warning "failed verification"?
@PrinceLys
What is your build number in settings ,about phone ?
timbernot said:
@PrinceLys
What is your build number in settings ,about phone ?
Click to expand...
Click to collapse
ahmm I think this?
model number: ASUS_Z00AD
android version: 6.0.1
software information: WW_4.21.40.223_20161216
P.S my phone is back on working state.
I just don't know if I can proceed to root after the incident. I don't know, I just want to make sure that my bootloader is still unlocked after what I've done (it did white screen with black asus logo) or.... it doesn't unlocked at all since I don't see this warning "your device has failed verification and may not work properly." (I've attach screenshot from the video tutorial)
I tried to manualy check if my bootloader is really on unlock state but I can't using these methods
method 1: on device’s dialer dial *#*#7378423#*#* (failed)
method 2: fastboot oem device-info (failed)
my recovery it still on stock recovery even after I flash twrp
btw guide source: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Q: should I still continue to flash twrp until it install?
Theres 2 bootloader unlock tools in general section , one is automatic
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
timbernot said:
Theres 2 bootloader unlock tools in general section , one is automatic
Click to expand...
Click to collapse
I'm going to look for it... thanks
musicman5844 said:
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've haven't fully read the instruction maybe tomorrow I will read it.
I just downloaded the files early and look into it... it seems like the versions are kinda latest (I don't know much about the droidboot ver. but I just look at the number on it "the higher the latest /heh") also the twrp is 3.0.3.
the ones that I used are all in package and it was 3.0.2 so I kinda go for the link you gave me
Thanks :good:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
nanobrain---- said:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
Click to expand...
Click to collapse
(I've finally think my bootloader is unlock after all.)
btw, did you succesfylly flash twrp?
Mine didn't flash (using twrp.bat), I guess I will try it again tonight if it fails again im gonna dl twrp from official and manually flash it.
Hello everyone,
For no apparent reason, yesterday my Nexus 5X (android 8.0, stock rom) shutdown and since, I can't turn it on again (stuck at google logo then turn off).
I found lot of topics related to this situation except I can't follow any of them since there is always a requirement I can't fullfill:
-I can't access recovery mode (it shows the "google" logo)
-My phone isnt oem unlock, so I tried to use the fastboot utility but it tells me "failed remote oem unlock is not allowed".
I found out that was because of the ADB driver so I tried to install them but I can't : i've tried using the google usb driver from the sdk manager but adb still tells me he can't find any device.
-Lot of tutorial talks about the device manager page but there is no "android phone" in mine...
I can only access the fastboot mode and I can flash some of the part of the tell (like boot, radio...) using nrt but not "recovery".
Someone has a solution ?
Thanks
u are like me bro
try fastboot oem unlock
Sofiane omega said:
u are like me bro
try fastboot oem unlock
Click to expand...
Click to collapse
As i said, i get the "failed remote oem unlock is not allowed"
roxasaxel said:
As i said, i get the "failed remote oem unlock is not allowed"
Click to expand...
Click to collapse
and this one
fastboot flashing unlock
if it work flash a factory image
Sofiane omega said:
and this one
fastboot flashing unlock
if it work flash a factory image
Click to expand...
Click to collapse
Same...
Same issue here, @roxasaxel any solutions ?
Turn off phone put it in refrigerator's top portion for 10 to 15 mints that way u ll boot your phone normally, if you cant then try to put it in there for longer. and once you boot it then go to developers option and enable that OEM unlock thingy and then do the rest. I hope it will work for you.
gmp009 said:
Turn off phone put it in refrigerator's top portion for 10 to 15 mints that way u ll boot your phone normally, if you cant then try to put it in there for longer. and once you boot it then go to developers option and enable that OEM unlock thingy and then do the rest. I hope it will work for you.
Click to expand...
Click to collapse
Exactly this is the only way you could boot the device normally
Do not take it out of the freezer, let it boot completely Toggle the oem unlock and then do all those things
Sad part is, after all of this life of your phone will only extent to max 3-4 more months only
gmp009 said:
Turn off phone put it in refrigerator's top portion for 10 to 15 mints that way u ll boot your phone normally, if you cant then try to put it in there for longer. and once you boot it then go to developers option and enable that OEM unlock thingy and then do the rest. I hope it will work for you.
Click to expand...
Click to collapse
+1 on this. How I got out of the Developer OEM lock situation.
Running AOSPA on my 4 core 5x.
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!