Develop Bugs

Boot loop after flashing 5.1

Guy Hi. I *really* need help....
I have a rooted nexus 7 2013 running stock 4.4.4. 1 tried flashing the 5.1 factory image and now have what I think is a bootloop. Here's what I did :
1. Downloaded the razor 5.1.1 factory image (LMY47V) from
https://developers.google.com/android/nexus/images
to my windows 8.1 laptop
2. Modified the flash-all.bat to remove the -w so it says "fastboot update image-&.zip"
3. I already had adb and fastboot installed on my windows laptop
4. I restarted my nexus 7 2013 into recovery, fastboot mode
5. Connected the N7 to the laptop
6. Ran the modified flash-all.bat.
Here's what appeared in the command window:
........
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.421s]
finished. total time: 1.556s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 0865c8bf
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7204 KB)...
OKAY [ 0.232s]
writing 'boot'...
OKAY [ 0.414s]
sending 'recovery' (7810 KB)...
OKAY [ 0.252s]
writing 'recovery'...
OKAY [ 0.298s]
erasing 'system'...
OKAY [ 1.362s]
sending 'system' (822862*KB)...
OKAY [ 25.772s]
writing 'system'...
OKAY [ 37.979s]
rebooting...
finished. total time: 66.351s
Press any key to exit...
...........
The nexus 7 2013 went into the Google boot up image sequence with the rotating flashing lights, but they are different from the kitkat lights.
Trouble is they keep repeating forever without fully booting.
I can exit by pressing "power down + power" and I can reenter recovery mode by again pressing "power down + power", but I cannot fully bootup and cannot enter my TWRP.
What should I do to finish flashing 5.1.1?
And then to regain root? What did I do wrong?
Please help. Thank you.

Anderson2 said:
Guy Hi. I *really* need help....
I have a rooted nexus 7 2013 running stock 4.4.4. 1 tried flashing the 5.1 factory image and now have what I think is a bootloop. Here's what I did :
1. Downloaded the razor 5.1.1 factory image (LMY47V) from
https://developers.google.com/android/nexus/images
to my windows 8.1 laptop
2. Modified the flash-all.bat to remove the -w so it says "fastboot update image-&.zip"
3. I already had adb and fastboot installed on my windows laptop
4. I restarted my nexus 7 2013 into recovery, fastboot mode
5. Connected the N7 to the laptop
6. Ran the modified flash-all.bat.
Here's what appeared in the command window:
........
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.421s]
finished. total time: 1.556s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 0865c8bf
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7204 KB)...
OKAY [ 0.232s]
writing 'boot'...
OKAY [ 0.414s]
sending 'recovery' (7810 KB)...
OKAY [ 0.252s]
writing 'recovery'...
OKAY [ 0.298s]
erasing 'system'...
OKAY [ 1.362s]
sending 'system' (822862*KB)...
OKAY [ 25.772s]
writing 'system'...
OKAY [ 37.979s]
rebooting...
finished. total time: 66.351s
Press any key to exit...
...........
The nexus 7 2013 went into the Google boot up image sequence with the rotating flashing lights, but they are different from the kitkat lights.
Trouble is they keep repeating forever without fully booting.
I can exit by pressing "power down + power" and I can reenter recovery mode by again pressing "power down + power", but I cannot fully bootup and cannot enter my TWRP.
What should I do to finish flashing 5.1.1?
And then to regain root? What did I do wrong?
Please help. Thank you.
Click to expand...
Click to collapse
Go into stock recovery and perform a factory reset. If it still doesn't boot, flash the factory image one part at a time. Flash all scripts can act wonky sometimes.
Sent from my SPH-L720 using Tapatalk

Thank you. Will do a factory reset.
Can you explain what you mean by "flash the factory image one part at a time"? How do I do that?
Thanks again.

OK. Got to the factory reset screen and wiped all data. Reflashed 5.1.1 and now booted up.

Anderson2 said:
OK. Got to the factory reset screen and wiped all data. Reflashed 5.1.1 and now booted up.
Click to expand...
Click to collapse
I'm experiencing this or at least a very similar issue and factory reset doesn't help. I flashed the factory 4.4.4 image and it boots up OK. I then allowed the OTA to upgrade 5.02 and yet when that completed flashing and rebooted I get the same thing, boots to 4 spinning colored globes and hangs. Any way to see what's happening here or other suggestions? Thanks!
Edit to add: I first flashed 5.1.1 and get the 4 spinning globes. Factory reset, same. Flash to 4.4.4 and it works. Upgrade to 5.02, back to spinning balls.

Need a Bootloader

Hello,
I'm not new to flashing / rooting / modding or Nexus / Pixel scene.. But that is a first for me.
I've updated my Pixel 2 XL to the latest version and I wanted to try out the P preview.. The problem is that apparently I have an newer version of the bootloader.
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
So if anyone could upload the TMZ20f I would really appreciate it.

That error is usually because you didn't unlock critical.

TonikJDK said:
That error is usually because you didn't unlock critical.
Click to expand...
Click to collapse
Hmm.. So I need to relock the bootloader and unlock it again?

Welp! I've unlocked critical.. But now I get "check console" error. Great.

Bucika said:
Welp! I've unlocked critical.. But now I get "check console" error. Great.
Click to expand...
Click to collapse
Are you using the latest version of fastboot?

RMarkwald said:
Are you using the latest version of fastboot?
Click to expand...
Click to collapse
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.

target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.901s]
writing 'bootloader_a'...
FAILED (remote: Flashing is not allowed in Lock State)
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
but when I do unlock comad (dose not matter if oem unlock, or unlock_critical it says failed cuz is unlocked.
It was all working fine (with unlocked bootloader via oem unlock command) until I've tried to flash the P. .then there was at first the wrong bootloader thing, and then I've just unlocked the unlocked bootloader again this time via the critical unlock, and the phone did not load the P it said the console thing.. and the phone didn't want to boot up, until I've flashed oem lock.. it boots up fine, but it's apperently locked and unlocked at the same time, lol. So I cant flash anything..But the phone does work, tho.
So I am basicially back to start, just can't do anything lol!

Bucika said:
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.
Click to expand...
Click to collapse
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands (back to back)?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?

RMarkwald said:
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?
Click to expand...
Click to collapse
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
OKAY [ 0.371s]
finished. total time: 1.194s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.342s]
writing 'radio'...
OKAY [ 0.579s]
finished. total time: 1.930s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
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'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ20f
Baseband Version.....: g8998-00202-1801251558
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (40960 KB)...
OKAY [ 0.923s]
writing 'boot'...
OKAY [ 0.377s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.593s]
writing 'system'...
OKAY [ 2.431s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.585s]
writing 'system'...
OKAY [ 2.445s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.252s]
writing 'system'...
OKAY [ 2.438s]
sending sparse 'system' (521136 KB)...
OKAY [ 12.083s]
writing 'system'...
OKAY [ 2.412s]
sending sparse 'system' (109860 KB)...
OKAY [ 2.632s]
writing 'system'...
OKAY [ 0.512s]
sending 'vendor' (374836 KB)...
OKAY [ 8.308s]
writing 'vendor'...
OKAY [ 1.734s]
erasing 'userdata'...
OKAY [ 0.289s]
sending 'userdata' (140898 KB)...
OKAY [ 3.125s]
writing 'userdata'...
OKAY [ 1.517s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 78.718s
Press any key to exit...

I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..

Bucika said:
I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..
Click to expand...
Click to collapse
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:

Badger50 said:
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:
Click to expand...
Click to collapse
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.

Bucika said:
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.
Click to expand...
Click to collapse
Oh please bruh!...legend? No..just old. Just helping out my fellow tech brothers/sisters to keep more hair on their heads, and not turn phones into desktop paperweights! ???

Your Device is corrupted and cannot be trusted.

My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks

Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
you're probably gonna get told this anyway but "use search function"
This has been addressed several times,
Download platform tools make sure your adb is in order download the november factory image and run the flash-all.bat script, this will bring your phone back to life, but with no data,

Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
You sure it not already unlocked?
Sent from my crosshatch using XDA Labs

I've had this on my P2XL before. Came about totally randomly. Phone started running extremely slow one day, so I rebooted it to see if it would clear out whatever was causing the issue. It wouldn't boot up and gave the same error. I was able to recover from it and save all my data by flashing factory image without wiping (remove -w in the flash-all script). Unfortunately it looks like you already factory reset so all data would be gone already.

Thanks I will flash it and hopefully it will sort it.
Sorry I did search but saw articles about pixel 2 not the 3.

Demolition49 said:
My Pixel 3 XL completely stock not unlocked just started displaying the following message:
"Your device is corrupt. It can't be trusted and may not work properly"
"Visit this link on another device g.co/ABH"
Spoke to Google and they asked me to perform a factory reset, I have done so with no luck.
Currently on latest November update.
Is the phone a dud and do I need to claim on warranty or is there any solution to this? Thanks
Click to expand...
Click to collapse
Did you get the Nov update OTA, or flash it yourself? I'm stock and still on the Sep update. Thought I saw that updates are rolling out, so just curious.

masri1987 said:
you're probably gonna get told this anyway but "use search function"
This has been addressed several times,
Download platform tools make sure your adb is in order download the november factory image and run the flash-all.bat script, this will bring your phone back to life, but with no data,
Click to expand...
Click to collapse
samnada said:
Did you get the Nov update OTA, or flash it yourself? I'm stock and still on the Sep update. Thought I saw that updates are rolling out, so just curious.
Click to expand...
Click to collapse
I got the OTA quite a few days ago, didn't flash it myself. Hopefully you'll get yours soon.

Demolition49 said:
I got the OTA quite a few days ago, didn't flash it myself. Hopefully you'll get yours soon.
Click to expand...
Click to collapse
Thanks
If it caused your problem I'll be happy to wait.

just download sdk platform tools and factory image and run flash all.bat. My data also got corrupt last night after downloading greenify

samnada said:
Thanks
If it caused your problem I'll be happy to wait.
Click to expand...
Click to collapse
I can confirm the update didnt cause any issue, it happened before that
i tryed to sideload OTA but it didnt work so the device needed a full factory wipe and it has fixed the issue.

Demolition49 said:
I can confirm the update didnt cause any issue, it happened before that
i tryed to sideload OTA but it didnt work so the device needed a full factory wipe and it has fixed the issue.
Click to expand...
Click to collapse
Thanks for the follow-up. I actually just got the OTA Nov update this morning and all is well. Glad yours got fixed also.

Alright, I got the device is corrupt error as well because of force of habit i mistakenly installed twrp.....
So I was trying to avoid wiping the data, and removed -w from the flash-all.bat. But I got the error again. Step two I used the flash-all.bat with -w to wipe.
The following are my results. The error "FAILED (Error reading sparse file)" appears at the end.
Code:
Sending 'bootloader_a' (8489 KB) OKAY [ 0.420s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5004167
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.535s]
Finished. Total time: 1.137s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.052s
Sending 'radio_a' (71148 KB) OKAY [ 3.579s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.425s]
Finished. Total time: 4.187s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 8A2Y0E0CS
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.059s]
Checking version-baseband OKAY [ 0.059s]
extracting boot.img (64 MB) to disk... took 0.245s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.024s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.691s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2158 MB) to disk... took 10.997s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.277s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 2.150s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_a' (65536 KB) OKAY [ 1.586s]
Writing 'boot_a' OKAY [ 0.318s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.271s]
Writing 'dtbo_a' OKAY [ 0.100s]
Sending 'product_a' (199620 KB) OKAY [ 5.847s]
Writing 'product_a' OKAY [ 0.919s]
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 10.910s]
Writing sparse 'system_a' 1/9 OKAY [ 0.363s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 9.863s]
Writing sparse 'system_a' 2/9 OKAY [ 0.364s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 12.823s]
Writing sparse 'system_a' 3/9 OKAY [ 0.366s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 10.361s]
Writing sparse 'system_a' 4/9 OKAY [ 0.322s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 9.411s]
Writing sparse 'system_a' 5/9 OKAY [ 0.364s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 10.273s]
Writing sparse 'system_a' 6/9 OKAY [ 0.366s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 10.251s]
Writing sparse 'system_a' 7/9 OKAY [ 0.365s]
Sending sparse 'system_a' 8/9 (258820 KB) OKAY [ 16.452s]
Writing sparse 'system_a' 8/9 OKAY [ 0.365s]
Sending sparse 'system_a' 9/9 (116824 KB) OKAY [ 5.003s]
Writing sparse 'system_a' 9/9 OKAY [ 0.870s]
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 16.649s]
Writing sparse 'system_b' 1/2 OKAY [ 0.365s]
Sending sparse 'system_b' 2/2 (166548 KB) OKAY [ 10.722s]
Writing sparse 'system_b' 2/2 OKAY [ 1.139s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_a' OKAY [ 0.066s]
Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 16.260s]
Writing sparse 'vendor_a' 1/2 OKAY [ 0.366s]
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Finished. Total time: 198.246s
Press any key to exit...
I've had the phone for all of less than 12 hours.... are you friggin kidding me? Any help??

raleighirishman said:
Alright, I got the device is corrupt error as well because of force of habit i mistakenly installed twrp.....
So I was trying to avoid wiping the data, and removed -w from the flash-all.bat. But I got the error again. Step two I used the flash-all.bat with -w to wipe.
The following are my results. The error "FAILED (Error reading sparse file)" appears at the end.
I've had the phone for all of less than 12 hours.... are you friggin kidding me? Any help??
Click to expand...
Click to collapse
Update your sdk tools.

c_86 said:
Update your sdk tools.
Click to expand...
Click to collapse
Alright it is a new laptop but I was pretty sure it was up-to-date.... although given the error I could be wrong. If any problems persist I'll be back.
Thanks for the heads up!
---------- Post added at 04:08 AM ---------- Previous post was at 04:05 AM ----------
c_86 said:
Update your sdk tools.
Click to expand...
Click to collapse
Yeah, I did have the newest version. Tried it again, and the same result. So currently researching anything I can while sitting in fastboot mode.

raleighirishman said:
Alright it is a new laptop but I was pretty sure it was up-to-date.... although given the error I could be wrong. If any problems persist I'll be back.
Thanks for the heads up!
---------- Post added at 04:08 AM ---------- Previous post was at 04:05 AM ----------
Yeah, I did have the newest version. Tried it again, and the same result. So currently researching anything I can while sitting in fastboot mode.
Click to expand...
Click to collapse
Flash the boot.img to both slots. boot_a and boot_b.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Flash the boot.img to both slots. boot_a and boot_b.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alright, so I began to flash the boot image to each of the slots. But it keeps failing at vendor_a each time. It couldn't be the file, is it my device at this point??
--------
Welp I saw it all over the place that people seemed to just use their friends pc and it worked. So I said screw it. Put down the laptop, went to the desktop. Sure as anything. It flashed the phone no problem and fixed the boot loop. I don't get why, the cable is the same, the files are the exact same... but it worked!

raleighirishman said:
Alright, so I began to flash the boot image to each of the slots. But it keeps failing at vendor_a each time. It couldn't be the file, is it my device at this point??
--------
Welp I saw it all over the place that people seemed to just use their friends pc and it worked. So I said screw it. Put down the laptop, went to the desktop. Sure as anything. It flashed the phone no problem and fixed the boot loop. I don't get why, the cable is the same, the files are the exact same... but it worked!
Click to expand...
Click to collapse
Are you using usb c to usb c cable? I had the same problem and error when I was. If you are switch to a usb a to usb c and try it all again, it worked once I switched cables.
Scratch that just read your edit at the bottom that you used the same cable lol.

I got the same probleme, how did you reset your pixel? I have pixel 3 xl 32gb and i tried to go on recovery mode and idn't work, its go on the page what its say : Your device is corrupt. Its can't be trusted and may not work propely. Visit this link on another device: go.co/ahb
Hope have some help

I have flashed the phone but the error has come back after a few weeks of use... I'm starting to feel like this could be a hardware issue. I am still getting the phone freezing every so often and it doesn't even reboot correctly I have to hold power and volume down to turn the phone on. Something definitely isn't right.

Bootloop after Android 10 OTA uodate!

I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?

You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.

fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP

areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.

fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]

ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

no dice. appreciate the suggestion though

ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…

simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
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-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...

ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
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-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!

Problems flashing a clean crosshatch 10 AOSP build to Pixel3XL

So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....

sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
The only thing I see is that it is only flashing to slot_a. It is my understanding that you need to flash to both partitions a and b before the process will work. For me it has only worked when I flashed to both partitions. Also adding .\ before the command may help. For some reason it only flashes for me when I add it.
Sent from my Pixel 3 XL

Does the AOSP build process generate full OTA images similar to what are found here: https://developers.google.com/android/ota?
If so, try flashing just the bootloader in fastboot, boot into recovery, and sideload the full OTA.

sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
I had this exact error running fastboot from shell on a Chromebook. Simply booting into the full Ubuntu installation I had installed on the Chromebook allowed me to flash.
I believed in my case the error was due to running out of memory. Though using an old fastboot version or a c -> c cable could also cause trouble.
You can also manually flash partitions instead of using the script. Remember, to get to fastbootd, you have to "fastboot reboot fastboot" from the bootloader.

ktmom said:
Though using an old fastboot version or a c -> c cable could also cause trouble.
Click to expand...
Click to collapse
Both of these are good points. You wouldn't think a USB-C to USB-C cable could cause fastboot problems but I've experienced this first hand. I can't quite remember the error I had, but I couldn't flash the stock factory images while using a USB-C to C cable. Switching to a USB-A to C cable (USB 2.0) resolved it.