Develop Bugs

Help phone stuck at boot screen

Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.

are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.

same thing here... I posted a request for a LTE boot.img since can still get into the bootloader

Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"

Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot

Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.

qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still

Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.

qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try

I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.

GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.

I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?

qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem

I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.

mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please

I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg

mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.

Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.

Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.

qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/

[Q] [Help] HTCdev bootloader unlock not working

I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks

Dlome said:
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Click to expand...
Click to collapse
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.

xunholyx said:
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
Click to expand...
Click to collapse
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.

Dlome said:
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Click to expand...
Click to collapse
So, have you tried the code again? And/or have you gone back to the HTCDev site for a new unlock code?

I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.

Dlome said:
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Click to expand...
Click to collapse
Are you copying and pasting the very first part of the code?
The part that looks like:
"(bootloader) < please cut following message >
(bootloader)" ?
IMMEDIATELY after that is what you copy and paste.
The copy should start when it says "<<<< identifier token start >>>>"

I am only copying the <<<< identifier token start >>>> and <<<< identifier token end >>>> along with the string between and leaving out the bootloader tag that is on each line.

I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.

Dlome said:
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Click to expand...
Click to collapse
You seem to be doing everything right. I'm stumped. Hopefully someone else comes along with a solution. @redpoint73?

That's what I was afraid of haha. I don't know why but while I am no expert in this area I do not feel I'm ignorant either yet I always seem to have problems even when I follow the steps correctly >.<
I do appreciate the troubleshooting greatly thank you. I will keep trying things and see what I can find and if I figure it out you bet I will add it here because I can't be the only one getting stuck haha.

Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.

xunholyx said:
Hopefully someone else comes along with a solution. @redpoint73?
Click to expand...
Click to collapse
Ummm, yeah . . . in fact I think I do:
Maybe I'm missing something here. But the Dev Edition comes already bootloader unlocked, and therefore should be no reason to do so.
I think the prompt to unlock never comes up on the phone, since its already unlocked.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
bloodhawk said:
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
Click to expand...
Click to collapse
Yes, this will tell us a lot.
Or boot into bootloader and just see if it says LOCKED, RELOCKED or UNLOCKED.
I bet it says UNLOCKED.

Stuck on "Google" screen

I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.

This happened to me and Google sent a replacement phone. However the replacement phone is a refurbished phone that suffers from ghost touches Now trying to get a replacement for the replacement.

Ocelot584 said:
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
can u boot into bootloader mode?

dominoeflux said:
can u boot into bootloader mode?
Click to expand...
Click to collapse
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?

Ocelot584 said:
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Click to expand...
Click to collapse
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems

dominoeflux said:
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
Click to expand...
Click to collapse
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.

Ocelot584 said:
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Click to expand...
Click to collapse
Oh ok I thought it was sorry if I wasn't of any help

dominoeflux said:
Oh ok I thought it was sorry if I wasn't of any help
Click to expand...
Click to collapse
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?

Ocelot584 said:
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Click to expand...
Click to collapse
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?

dominoeflux said:
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
Click to expand...
Click to collapse
nope...what's a bootloader anyway?

Ocelot584 said:
nope...what's a bootloader anyway?
Click to expand...
Click to collapse
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it

dominoeflux said:
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
Click to expand...
Click to collapse
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?

Ocelot584 said:
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Click to expand...
Click to collapse
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative

dominoeflux said:
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
Click to expand...
Click to collapse
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?

Ocelot584 said:
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Click to expand...
Click to collapse
Of course
Edit: have you tried resetting it in the factory recovery?

dominoeflux said:
Of course
Edit: have you tried resetting it in the factory recovery?
Click to expand...
Click to collapse
Nope...I was waiting to see if I could find a way to recover my data first

Ocelot584 said:
Nope...I was waiting to see if I could find a way to recover my data first
Click to expand...
Click to collapse
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.

dominoeflux said:
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
Click to expand...
Click to collapse
Alright, but since all my data won't be recovered, is there a way to get access to files on my phone before I factory reset it?

Ocelot584 said:
Alright, but is there a way to get access to files on my phone before I factory reset it?
Click to expand...
Click to collapse
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way

dominoeflux said:
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
Click to expand...
Click to collapse
oh... wow.
I'll just suck it up and reset it then. I'll let u know how it goes.

Softbricked, locked bootloader ... HELP!!

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!

Any way to fix Bootloader ?

Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ

elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
Is there are any way to fix that with out change motherboard ?
Click to expand...
Click to collapse
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)

andybones said:
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)
Click to expand...
Click to collapse
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ

elween07 said:
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
which app?
also why were you trying to lock?
I can't say but it seems like it could be a pain, but I hope not!

elween07 said:
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
Click to expand...
Click to collapse
and some people say natural selection doesn't exist

Oh dear!
I dont like to tell you this, but you have hard bricked your phone and it cannot be fixed using software.
Locking the bootloader is ONLY for when you are on pure stock. Even having a custom recovery (like TWRP) isnt allowed even if the ROM is stock.
In locking it, you have hard-bricked it, and there isnt ANY way to recover this using software. Nobody on XDA has EVER been able to sort this one out.
Your best bet is one of two options:
1. Buy a new phone. Yeah, pain I know, but the HTC 10 is now 3.5 years old and it might be cheaper to just buy a new phone than try to fix it.
2. Get it fixed at a repair shop. I can imagine that a few local places might not be able to do it, but maybe somewhere can. It's worth an ask?
I seem to recall that using a JAVA card or something like that you might be able to fix it, but if you have locked the bootloader with a custom rom on it, then the chances are it is over for you.
Hey, don't beat yourself up too much about it; we've all done stupid things in the past. I reversed my car into a concrete post last month and it cost me a fortune to fix it!
Such is life.....

elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
Bro, never relock the bootloader. That's just a bad idea. You most likely hard bricked your phone and there is no way back. That's not 100% for sure but if u flashed any non-htc images the bootloader will not boot it. Thats why you keep it unlocked, so it can boot unsigned images. That's why it keeps shutting off.