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] Endless loop of restarts into recovery

hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>

simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?

redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.

simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.

redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..

simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.

redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:

simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.

redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:

eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error

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!

Motorola G6 Play (Boot loop)

I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy

Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately

Thanks for the reply, please can you put a link to your guide?

Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928

Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.

Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops

sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?

Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?

The phone was bought direct from Amazon so in my mind a generic model to take any SIM.

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.

I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it

Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?

ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?

Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it

Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a

ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..

Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted

I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.

Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant