I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
wrkerr said:
I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
Click to expand...
Click to collapse
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Billys20 said:
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Click to expand...
Click to collapse
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
wrkerr said:
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
Click to expand...
Click to collapse
Same thing here. When I left it for a while I was able to boot to bootloader but when I choose the recovery mode it boots again with the google logo and then turns off. No hope here I guess.
Mine does not care, it does not carry, not the sign of life.:crying:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
um.z said:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
Click to expand...
Click to collapse
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tried, but flash-all failed due to the phone switching itself off in the middle of the process. Here's the relevant content from my terminal window.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4620 KB)...
OKAY [ 0.189s]
writing 'bootloader'...
OKAY [ 0.197s]
finished. total time: 0.387s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.534s]
finished. total time: 1.997s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.033s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB) to disk... took 0.044s
archive does not contain 'recovery.sig'
extracting system.img (1909 MB) to disk... took 10.193s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB) to disk... took 1.107s
ERROR: usb_write failed with status e00002c0
archive does not contain 'vendor.sig'
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
wiping userdata...
ERROR: usb_write failed with status e00002c0
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (Invalid argument))
ERROR: usb_write failed with status e00002c0
--------------------------------------------
ERROR: usb_write failed with status e00002c0
getvar:version-bootloader FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
From here: https://dl.google.com/dl/android/aosp/bullhead-opm2.171019.029-factory-c7ba966b.zip
I did flash each partition separately in the end, but to no avail. Phone doesn't boot.
Hello same issue here with LineageOS 15.1 (+xposed and ElementalX)
It won't boot anymore after three loop to Google Logo and black screen, I was suspecting hardware issue and now, I see I'm not alone.
I'll try to boot to the bootloader this evening and flash factory images. I hope it'll work.
OMG! What's going on? I'm in Scotland right now with our US Nexus 5X's. Afternoon of the 2nd of May, I was using Hangouts when it just went black. Battery had over 40%. I couldn't even get it to turn on for a while. Then, it started with the unlocked bootloader warning screen then the Google screen-looping those for a while. Occasionally, the colored balls would begin but not finish. Sometimes, it wouldn't do anything--nothing but a black screen. I could get to TWRP via bootloader but any action was impossible as it either locked up or just went black. I left it plugged in overnight and eventually, the OS started (stock April update) again. The phone & OS remained on overnight. This morning, I tried to put the main Fi sim back into it but it locked up (froze) again then started the two-screen loop. I honestly didn't think I'd find people with the same issue--esp just happening. I can't get back to my PC until near the end of May so I can't try very much. I probably have the last OS on my 5X storage since I use Flashfire to update, but I really didn't want to try flashing anything since the black screen issue seems inevitable. I hope someone out there gets to the root of this. So far, hubby's 5X is working. Of course, all of ours were working until they weren't! His is locked and stock. We're both on April update.
Has anyone gotten anywhere with correcting this issue?
FWIW, I just contacted LG support today since I'd read that the warranty had been extended to 30 months. I won't know the final results for a few weeks, but I set up a repair and eventually received a shipping label to Fort Worth, TX. As far as I can tell, these behaviors ARE the BLOD. We also have a 27 mos old 5X that is hardly ever used. It currently has no issue; but then, mine didn't either until is just went black and wouldn't restart.
EDIT: In case anyone is still searching solutions for this issue, my phone is on its way back from LG with a new motherboard. All (including shipping both ways) was covered under the new, 30 mos extended warranty.
Related
I flashed system.img and boot.img of Android 6 Factory Image manually and worked so far.After that i want a clean install,so i erased system,userdata and boot Partition and flashed the Factory Image with the included skript.But Android wasn't booting(i waited over 30-35 min.).So did the same again with no success.So i flashed TWRP and flashed CyanogenMod (that worked for me, but TRWP shows Mount Erros with data,cache etc.).But CyanogenMod also stucks in Bootanimation.
Have you tried re-downloading the files? It could be a bad download maybe.
theminikiller said:
Have you tried re-downloading the files? It could be a bad download maybe.
Click to expand...
Click to collapse
Yes.I also tried it with a Lollipop Factory Image.
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
+1
I have the same problem
Dirty flashed the android 6 flash-all.bat and now I am soft-bricked
Fastboot is activate but fails all actions
If you get an answer please let me know
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
Click to expand...
Click to collapse
Now short enough?
Nic2112 said:
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Click to expand...
Click to collapse
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Nic2112 said:
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Unfortunately the MultiROM version is not working,too.The normal version worked well for before(My device wasn't shipped with 5.0.1 or is from best buy or something like that).
david.mueller1013 said:
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Click to expand...
Click to collapse
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Nic2112 said:
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Click to expand...
Click to collapse
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
How bout editing the thread title adding [solved]...
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
david.mueller1013 said:
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
Click to expand...
Click to collapse
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
caolfin said:
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
Click to expand...
Click to collapse
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Hi
Yes, the N7 is stuck in bootloader
I have tried many times to lock and unlock the bootloader and currently the last few lines of the bootloader screen are
SIGNING = yes
SECURE BOOT = enabled
LOCK STATE = unlocked
I am assuming that LOCK STATE means bootloader lock state and therefore this should be ok ?!
This is really stumping me now
Nic2112 said:
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Click to expand...
Click to collapse
Hi, I tried to reset the bootloader and now I cant get it to unlock ggggrrrrr
Comes up with the questions Unlock Bootloader ? and I say yes
I get
C:\adb\razor-lmy47v>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
I'm totally stumped now
can someone with LTE (razorg) please do the OTA using the bootloader method (wiping data and system first) and put TWRP back and then make a TWRP backup without booting into the fresh android install so that people who dont have working USB can possibly get the update. it would be much appreciated and theoretically should work.
I have been trying to flash my tablet back to factory.. everything has failed, I can get into bootloader or it reboots to Google in white font with nothing else, besides the Unlock icon. I had it rooted before and it tried to update the OS then this happened. So i have tried multiple things, and friend software engineer even has tried helping, i have the adb and fastboot files and the factory image for the tablet but when i am done the flash-all.bat script it reboots to the white font Google. Any help!???
Also, When i run the flash-all script I see
sending 'bootloader' (3911 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
OKAY [ 1.364s]
finished. total time: 1.505s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
the script continues.. then finishes with rebooting my device with the White font Google still.
I have also tried the commands manually one by one, and root kit tools. Any advice?
Okay, this might sound weird, but have you tried giving your Nexus 7 a good smack? Mine has been a bit stubborn lately, sometimes also getting stuck on the Google logo. For some reason, when I give it a hard smack on the back when it's stuck, it decides to continue the boot sequence. Otherwise, I'm not sure what would be wrong since you didn't get any errors.
tonytien said:
Okay, this might sound weird, but have you tried giving your Nexus 7 a good smack? Mine has been a bit stubborn lately, sometimes also getting stuck on the Google logo. For some reason, when I give it a hard smack on the back when it's stuck, it decides to continue the boot sequence. Otherwise, I'm not sure what would be wrong since you didn't get any errors.
Click to expand...
Click to collapse
You know I am so pissed off.....that worked. And I was flashing all afternoon and my software engineer buddy gave up he said he couldnt help me.. i wonder why.
Setting up the tablet now.. good grief. THANKS!
What... a smack could solve the problem?
Did you try reboot before I am wondering, because I have same problem.
cmtyresearch said:
What... a smack could solve the problem?
Did you try reboot before I am wondering, because I have same problem.
Click to expand...
Click to collapse
Yes it did. I reflashed the factory image and everything still had same issue until I gave it a smack!
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Popped, hopefully Google charges you for your fraudulent warranty claim
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
DaveHTC200 said:
Will it not boot into recovery from the bootloader menu?
Edit: just realised you said you've relocked the bootloader! Might have been a big nail in the coffin.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
cwalker0906 said:
Popped, hopefully Google charges you for your fraudulent warranty claim
Click to expand...
Click to collapse
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
You can try "fastboot set_active _a" prior to running the script again and see if it'll actually write to slot A
Sent from my Pixel XL using Tapatalk
ko0ky said:
WTF are you talking about? I'm not the guy who was doing warranty claims. Nice try. RMA isn't WARRANTY mister clueless.
Click to expand...
Click to collapse
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
ko0ky said:
Hi, hoping to get some help here. I did some quick google searching and didn't see anything specific to the pixel.
I used Skipsoft android toolkit to unlock and root my pixel xl. Shortly after I started to have some issues and was forced to do a factory reset which I believe removed root (and I'm not sure if it screwed something up with the bootloader or not) but I've never been able to get to stock recovery. For other reasons I was shipped a replacement pixel and now I need to ship this one back. I needed to revert it back to stock before I send it back. Since it didn't have root, i used Skipsoft toolkit to relock the bootloader. I was presented with a screen on the pixel asking if I wanted to relock the bootload (i had to use vol. buttons to move between yes and no and use power to select).. I selected Yes and hit the volume button. Now my phone won't boot any longer. I can get to the bootloader.. or if I try starting the phone I get a message saying my device is corrupt. It can't be trusted and may not work properly. (if its plugged into my computer or whatever I see a battery charging icon for about 10 seconds then the screen goes blank) if the phone isn't plugged into anything after the corruption notice it just goes to a blank screen.
I'm not a complete noob as I've been around rooting my devices for years but at the same time, I am no expert. Does anyone know or can anyone offer any suggestions how I can get the device back up and running stock?
Thanks in advance for any suggestions or tips!
Click to expand...
Click to collapse
Anyone else having this issue I was able to flash my device using directions from this page. (directly from google). https://developers.google.com/android/images You might have to accept their terms before everything gets displayed. I downloaded the image and ran flashall.bat on my windows box - rebooted the device, then got back to bootloader and ran the cmd to lock the bootloader. Everything is STOCK and good to be returned.
cwalker0906 said:
Sure, either way since I'm so clueless...if you read the toolkit thread you would have seen it doesn't work flashing factory images. Multiple people including myself have had this issue, so read and you will find your answers, also if RMA isn't warrant then what is it, you are exchanging a defective device for a new one... warranty lol have a good day buddy
Click to expand...
Click to collapse
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
You are right, I jumped the gun ,all apologies
wtherrell said:
He very clearly said that it was being returned for "other" reasons. Not the flashing fiasco.
Click to expand...
Click to collapse
thanks for being courtesy and helpful! much appreciated!
ko0ky said:
trying to use the toolkit to download and install google factory stock image and I'm getting the following errors..
Flashing update image..
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609150631
Serial Number........: H*
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (26481 KB)...
OKAY [ 0.842s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.296s
An error occured when flashing the image
Click to expand...
Click to collapse
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
dabadoo said:
Did you solve this problem, I'm getting the same thing. Stuck in bootloop, but somehow managed to get it started, now stuck in "checking for updates"
Click to expand...
Click to collapse
To flash use the instructions from the Google page :
https://developers.google.com/android/images
Paolo
The other thing is make sure you're using the latest Fastboot. Old fastboots do not have support for the slot system.
Let this be a huge lesson not to go running to tool kits, the one you used is nice for installing the drivers but ultimately simply using the flash-all.bat is infinitely easier to do at this point if adb/fastboot is configured.
Also don't lock the bootloader if you have modified the system at all =/
Edit: You should probably add your solution to the OP to help anyone else that maybe have done something similar.
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
powdered_donuts said:
I am having a similar issue. All I have done is u lock the bootloader through fastboot. No toolkits involved or anything. Simply plugged in, booted bootloader mode then fastboot OEM unlock and rebooted. I am unlocked but noticed I cannot boot stock recovery. It goes to the dead Android icon and simply says no command below it. No amount of pressing the volume keys or anything changes it. Holding power eventually reboots back to Android. Anyone else experiencing this or have a fix , or better yet a reason for this occurring?
Click to expand...
Click to collapse
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
DaveHTC200 said:
When on the no command screen, have you pressed and held the power button, then the volume up button?
Never fails for me! Trying to press them together I didn't have any luck.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I didn't do it in the correct manner, I'll give it a go and report back
Update: successful! Power first then volume then release.
Thanks!!
ko0ky said:
i've managed to use the toolkit to unlock the bootloader again. I can get the phone to boot again to android. But I'd like to revert it back to stock. I cannot get it to boot to recovery though.
Click to expand...
Click to collapse
How did you manage to unlock bootloader and reboot phone trough toolkit, im in the same situation here . the phone is locked on verizon. Thankyou
Download script: HERE
Download Factory Images: HERE
Download ADB/Fastboot: Platform Tools
Download USB Drivers: USB Drivers -- Driver Installation Video
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This script is for the UNLOCKED BOOTLOADER pixel2 / pixel2 XL, and will help:
Fix Bootloops
Flash both Slots A and B
Work with any Google-provided factory image
Detect bootloader and radio special *.img names automagically
(Optional): Unlock Bootloader and Critical
(Optional): Format Userdata
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions:
Extract factory image zip file, as well as the image zip file within it!
This will lead to ~21 .img files in the same folder, with the deuce-flash-all script!
SEE SCREENSHOT!!.
Once you have all these together, run the Deuce-Flash-All script. ( .bat for Windows, .sh for Linux)
-----------------------------------------------------------------------------------------------------------------------------------------------------------
If you are having issues with this script:
Verify you have the environment variable (path) set for adb and fastboot
Try a different USB port
Try a different cable (preferably USB A -> USB C)
Format Userdata in Stock Recovery
Boot plain factory image before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
This was built for the 2 xl but I have modified it to work with the pixel 2.
The main thread, which has lots of troubleshooting Q/A is here:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Changelog:
06-13-2018: Added support for latest platform tools
01-14-2018: Fixed bug. Made unlocking optional to speed it up, combined scripts for taimen & walleye
01-09-2018: Removed support for locking bootloader, added hard-coded slot selections
12-26-2017: Added support for Pixel 2 (Walleye)
I have been using this on my walleye since v4, guess now we no longer get the errors for the critical unlock status.
Makes sense, thanks as always most beneficial tool besides adb itself for a pixel device!
Hey. When I boot my Pixel 2 XL I get a can’t find valid OS. Will this fix it?
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Matt17000 said:
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Click to expand...
Click to collapse
Unlocking the bootloader always wipes. Magisk, recovery, and other things will not.
You've saved me twice from a brick. Thank you.
Dude you are a freaking god send! THANK YOU!
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Deuces said:
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Click to expand...
Click to collapse
I am about to use it in 3 hrs. I am currently running dec patch with twrp and magisk. Ill try to sideload january patch soon.
I used it to recover from a softbrick, had an error on mac address 02:00 etc and fingerprint hardware, not sure if related to your Tool, but it did let me Boot back into system after everything else failed, all working again after factory flash with wipe
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Deuces said:
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Click to expand...
Click to collapse
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
JayBlack_686 said:
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
Click to expand...
Click to collapse
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Deuces said:
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Click to expand...
Click to collapse
Hi, thanks. I did try holding VOL - and power down for 30 seconds+. Actually, I did feel a vibration, but...nothing after. Couldn't get it to act like it was turning back on. Now that you mention it...I wonder if I did get it to turn on at some point during trying this over and over, because at times I saw the "scan line" appear across the screen briefly, like when I hard power off the device. But I've never seen the display light up at all, and nothing I've done has shown a device when issuing the "devices" command, either via fastboot or adb. I guess I need to screw around until I see that scan line, then it's "off." Then I've gotta get the thing to vibrate again, so it's "on." Then try seeing if I can run your script.
Boy am I glad I didn't try this late at night.
Oh, sorry, I'm on Windows 10.
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Deuces said:
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Click to expand...
Click to collapse
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
JayBlack_686 said:
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
Click to expand...
Click to collapse
If you can't get into bootloader, there's nothing I can do. There's some talk about using LG's downloader mode but LG has not released an image for it that I know of.
You can see this download mode by: Powered Off. Hold Vol+, insert USB cable connected from laptop.
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
You could disable OTA updates via developer options so that the notification goes away.
If you decide to stay stock, you could technically leave the bootloader locked, but the "allow oem unlocking" enabled in developer options. However, if something corrupts your OS, it's unlikely you'd be able to issue the unlocking commands from bootloader. That's the main reason I stay unlocked.
I've got the process down for upgrades myself. Download image, unzip, unzip the image within that, run my deuce-flash-all script. Boot up to Android once. Reboot to bootloader, fastboot boot twrp img, install magisk, reboot.
I do not flash twrp zip b/c it has been problematic for touchscreen drivers, and I'm around a computer anyway when doing these things.
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Deuces said:
If you can't get into bootloader, there's nothing I can do.
...
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
...
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Click to expand...
Click to collapse
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
JayBlack_686 said:
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
Click to expand...
Click to collapse
I can verify! I watch Netflix on my phone at work, downloaded from the play store on a pixel 2 unlocked, twrp installed and rooted with magisk. Not sure why everyone is having problems with it.
Hey everyone,
So my Pixel 2 XL is kinda stuck at the moment. I'm having problems getting stock back up on my Pixel 2 XL, When I click onto flash-all command it does the job till it gets near the end of the process and then comes up with the error as 'Target didn't report max-download-size' I've used other factory images for the Pixel 2 XL CMD and the phone isn't having it at all. I really don't know what to do at this point. I need some kind of fix to this. Any advice would be really great.
** NEW ERROR **
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.799s]
writing 'bootloader'...
OKAY [ 0.370s]
finished. total time: 1.169s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.341s]
writing 'radio'...
OKAY [ 0.570s]
finished. total time: 1.911s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: failed to load 'image-taimen-pq2a.190405.003.zip': Not enough space
Press any key to exit...
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
I usually run into this issue if I don't have enough free space on my C drive (at least 4 GBs; the system partition image is around 2 GBs...). And if it's not the free space issue, usually it's merely just a change/re-initialization of the USB cord. Make sure you have the latest platform-tools (r28.0.2 is the most up-to-date version) as well as using a USB-C to USB-A cord (USB-C to USB-C seems to cause endless amount of issues and is usually the root cause for random unknown reasons...)...it usually sets things up right to work the next time around.
But, if making sure of all the previous things, and you restarted your phone and computer already, then you might try re-downloading the Full Factory image and extracting it once again (don't forget to re-edit the .bat/.sh file to not include the "-w" attribute); and consider even going through the trouble of comparing checksums to make sure you are getting/using the exact proper copy of the factory image...
good luck to you and hope this helps...
Fe Mike said:
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
Click to expand...
Click to collapse
I uninstalled and reinstalled fastboot, re-downloaded platform tools and reinstalled all drivers. I downloaded the factory file straight from google which was the android 9.0 April 2019 update. Yet I'm still having this problem. It was working fine yesterday as I went to reboot it, it just went straight into a bootloop. The phone was rooted via magisk.
So I got a new error now and fastboot is telling me that there is not enough space to load the zip file. Everything is extracted out of the image zip file and moved into the adb folder
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Knxed_ said:
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Click to expand...
Click to collapse
You can boot twrp and flash the ota as well