Database Info

Flash OTA with root

Is this the most up to date instructions? https://www.xda-developers.com/flash-monthly-security-update-google-pixel/

Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!

Oof, I'm in the same boat. I messed installing TWRP and had to flash the factory images over the weekend, so I'm a little gun shy to flash this until I know exactly what to do.

On my Pixel 2 I've been doing the below -- I do not install TWRP but I do have a custom kernel and magisk:
1) flash stock boot img from previous month to remove Magisk and custom kernel (I *assume* that removing magisk via magisk manager would also accomplish this if magisk was installed before custom kernel - but I have never bothered doing this)
2) sideloading OTA (via stock recovery)
3) installing magisk and custom kernel
There are cases where Google says on their factory image page that you must take the OTA (rather than flashing to a new image) - that fact is enough reason to me to sideload the OTA rather than flashing the entire new month's image

ktdt00 said:
Pixel noob alert! I have basically the same question. I've done a bunch of reading and it seems like I can:
1) Use flash-all on the factory image after removing "-w"
2) ADB sideload the OTA zip file
3) TWRP install the OTA zip file
I'm not clear which, if any, is really "best" and in each case whether I'll need to reboot TWRP, reinstall TWRP and reinstall Magisk?
Thanks for any help on this!
Click to expand...
Click to collapse
1 or 2. Not 3. Either way you will have to re root and install TWRP if you want.
Both are equally good.

Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.

Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
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.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
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 (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...

I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Troy The Great said:
I've tried to flash-all the Nov. factory image like 4 times now, and every time I check the build number and it's still the Oct version. Can someone please help me figure out what I'm doing wrong? I've extracted and copied all the .img files into the adb directory. This is super long but here is the cmd readout I get after flash-all:
PS - what is the -w thing about? I don't see it in the names of any downloaded files.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8489 KB)...
OKAY [ 0.289s]
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.642s]
finished. total time: 0.936s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (71148 KB)...
OKAY [ 1.659s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.463s]
finished. total time: 2.122s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.070s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.226s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2157 MB) to disk... took 9.974s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.930s
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 (444 MB) to disk... took 2.022s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5004167
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 897X0687T
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Press any key to exit...
Click to expand...
Click to collapse

Archangel said:
Sideloading through TWRP did not work for me at all with this phone so I had to download the Nov factory firmware, delete the -w on the flash-all.bat file. Then flashed this through fastboot, rebooted to make sure I was on the Nov update. After that, booted back to bootloader and reflashed TWRP and Maigisk, now all is fine.
Click to expand...
Click to collapse
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
You are a genius, the updated platform tools worked; all rooted and good to go. Thank you so much for your help

Why does the XDA guide not talk about re-rooting?
Followed XDAs instructions on unlocked bootloader, rooted with Magisk and now getting the "device is corrupt" message. Ugh.

I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.

Update your platform tools often.

so is there a working step by step somewhere now?

Updated tools
Archangel said:
I had this happen to me and the variable not found error is due to your platform tools being out of date. I updated mine,,, unfortunately I cant remember where,,or I would give that you to,,,if you do a google search on updated platform tools/xda it will come up and just take the most recent one you see. Once you swap out the platform tools folders you should be good to go. Once I did mine the flash completed and I am on Nov update.
Oh and the -w is a part of a line of code that you will find in the flash-all.bat file once you have extracted the Nov system image. Look for that flash-all.bat file then right click on it and open it up with Note+. Find the line at the bottom that has a -w in it and delete it out. Once that is done go to the top and hit save just dont exit out or it will not work. Once you hit save then you can hit the flash-all.bat and it will flash the Nov entire system up without erasing your current data. Hope this helps.
Click to expand...
Click to collapse
Glad I found your post. I bricked my new 3XL I received today and was unable to get the factory image installed. Getting the new tools resolved the problem. I bricked when I used Magisk 17.1. After I got it going again, I used 17.3. Now she runs great.

km8j said:
I'm now 100% back to stock. Took forever. How the heck do I do this right next time? Working on restoring my data.
Click to expand...
Click to collapse
Anyone?

km8j said:
Anyone?
Click to expand...
Click to collapse
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Sent from my [device_name] using XDA-Developers Legacy app

gvsukids said:
Look at post 6
https://forum.xda-developers.com/showthread.php?p=78083312
Click to expand...
Click to collapse
#1 is basically what I did already

km8j said:
#1 is basically what I did already
Click to expand...
Click to collapse
I have sideloaded the Nov OTA zip in stock recovery and not lost data. Pixel 3, unlocked bootloader, unrooted.

Q Beta

I just found this. I haven't tried it yet.
https://developer.android.com/preview/download.html

same here
don't want to lose root, twrp and xposed.
i'm fine not having xposed but i need root and twrp

TheUndertaker21 said:
same here
don't want to lose root, twrp and xposed.
i'm fine not having xposed but i need root and twrp
Click to expand...
Click to collapse
I'm guessing twrp won't work. But topjohnwu supposedly has rooted it.

jd1639 said:
I'm guessing twrp won't work. But topjohnwu supposedly has rooted it.
Click to expand...
Click to collapse
Have you read this: Android Q - Magisk

any idea?
Code:
sudo ./flash-all.sh
< waiting for any device >
Sending 'bootloader_b' (8501 KB) OKAY [ 0.170s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b1c1-0.2-5260815
(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_b
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.200s]
Finished. Total time: 0.610s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 1.701s
Sending 'radio_b' (71164 KB) OKAY [ 0.740s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g845-00017-190123-B-5251681
(bootloader) Flashing partition modem_b
OKAY [ 0.414s]
Finished. Total time: 1.352s
Rebooting into bootloader OKAY [ 0.054s]
Finished. Total time: 1.657s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5260815
Baseband Version.....: g845-00017-190123-B-5251681
Serial Number........: 89HY07A6G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.060s]
Checking 'version-bootloader' OKAY [ 0.060s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'b' OKAY [ 0.076s]
extracting boot.img (64 MB) to disk... took 0.280s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.680s]
Writing 'boot_b' OKAY [ 0.320s]
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.170s]
Writing 'dtbo_b' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.063s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.060s]
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Homeboy76 said:
Have you read this: Android Q - Magisk
Click to expand...
Click to collapse
You should read this!
Sieh dir den Tweet von @topjohnwu an: https://twitter.com/topjohnwu/status/1105968107011665920?s=09
Gesendet von meinem Pixel 3 XL mit Tapatalk

b0uNz said:
You should read this!
Sieh dir den Tweet von @topjohnwu an: https://twitter.com/topjohnwu/status/1105968107011665920?s=09
Gesendet von meinem Pixel 3 XL mit Tapatalk
Click to expand...
Click to collapse
I couldn't, no Twitter account. Thanks for the link.
Well, that changes my outlook on Android Q.

y2kbugleung said:
any idea?
Code:
sudo ./flash-all.sh
< waiting for any device >
Sending 'bootloader_b' (8501 KB) OKAY [ 0.170s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b1c1-0.2-5260815
(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_b
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
(bootloader) Flashing partition logfs
OKAY [ 0.200s]
Finished. Total time: 0.610s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 1.701s
Sending 'radio_b' (71164 KB) OKAY [ 0.740s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g845-00017-190123-B-5251681
(bootloader) Flashing partition modem_b
OKAY [ 0.414s]
Finished. Total time: 1.352s
Rebooting into bootloader OKAY [ 0.054s]
Finished. Total time: 1.657s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5260815
Baseband Version.....: g845-00017-190123-B-5251681
Serial Number........: 89HY07A6G
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.060s]
Checking 'version-bootloader' OKAY [ 0.060s]
Checking 'version-baseband' OKAY [ 0.060s]
Setting current slot to 'b' OKAY [ 0.076s]
extracting boot.img (64 MB) to disk... took 0.280s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 0.680s]
Writing 'boot_b' OKAY [ 0.320s]
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.170s]
Writing 'dtbo_b' OKAY [ 0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.063s]
archive does not contain 'vbmeta_system.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.060s]
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
I have got it fixed.
Thanks.

Are you serious? Couldnt you tell how you fixed it???
i have the same damn issue ple halp
y2kbugleung said:
I have got it fixed.
Thanks.
Click to expand...
Click to collapse

Are you serious? Couldnt you tell how you fixed it???
i have the same damn issue ple halp
Click to expand...
Click to collapse
Classic DenverCoder9!
I ran into the same issue and had the same response as you. But then I reran the script a second time, without moving anything and the setup was successful. So if you didn't, give it a second try before giving up.

y2kbugleung said:
I have got it fixed.
Thanks.
Click to expand...
Click to collapse
how did zou get fixed?

Stelsinki said:
how did zou get fixed?
Click to expand...
Click to collapse
Sorry too long time ago. I forget.
Try using latest ADB and Fastboot:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Make sure the driver on computer is update.

i m able to send some flashing command but when i try to boot in fastbood with command fastboot reboot fastboot i get the error message. i dont think the problem is drivers

Soft Brick when trying to apply April update

Soft Brick recovery help
So my Pixel 3 is soft bricked and I can't seem to rescue it this time. I am bootloader unlocked and rooted on the stock rom. I was trying to update through fastboot to the April update and the flash all batch file wasn't working, I kept getting the following error
"target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.261s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(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.213s]
finished. total time: 0.475s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.742s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.407s]
finished. total time: 2.151s
rebooting into bootloader...
OKAY [ 0.049s]
finished. total time: 0.049s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1999310544 bytes
error: update package missing system.img
Press any key to exit..."
I tried updating all my ADB and SDK tools. Formatting slot a and b and boot a and b then ran the batch file again and same error. Tried flashing each image file individually and the same error. I'm stuck in Fastboot. Any help would be greatly appreciated!

Try redownloading the .img and check CRC to make sure it's good, shouldn't be missing stuff

Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.

Kandern97 said:
Sorry to resurrect a dead thread, but did you ever figure out how to fix your issue?
I've got the same problem over here.
Click to expand...
Click to collapse
Are you using the latest SDK platform tools, fastboot?

Soft brick while attempting to root

I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(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.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.

cmorin543 said:
I tried rooting my Pixel 3 - - OEM Unlock, bootloader unlocked, got into TWRP, but for some reason couldn't access any files on the system to install a zip. I tried wiping the file system to start from scratch and that didn't work. I then rebooted multiple times and fastbooted back into TWRP -- I had found a thread saying to change the file system type if you couldn't see the internal storage in TWRP -- I think that's where I went wrong. After I did that, I could no longer fastboot into TWRP. I tried downloading a factory image from google and fastbooting the recovery with no luck. I even tried the guide here : https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849 to un-brick without success. I performed the erase commands "fastboot erase system_a
, fastboot erase system_b, fastboot erase boot_a, fastboot erase boot_b, fastboot reboot-bootloader then running the flash all command and the results below show and still unable to boot:
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.308s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5191736
(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.899s]
finished. total time: 1.208s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.907s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.482s]
finished. total time: 2.393s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.072s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.376s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.041s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2189 MB) to disk... took 24.932s
archive does not contain 'system.sig'
extracting system_other.img (419 MB) to disk... took 4.880s
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 5.342s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5191736
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: 89DX08FVQ
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.362s
Press any key to exit...
any advise would be greatly appreaciated.
Click to expand...
Click to collapse
Hello,
I wonder ? do you have pixel 3 phone?
I see that you have the bootloader of the crossheath for the google pixel 3 XL installed.
bootloader-crosshatch-b1c1-0.1-5191736.img
Maybe you should download the google pixel 3 OTA or Factory.img.

That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.

cmorin543 said:
That's so weird -- I used the blueline factory image from here: https://developers.google.com/android/images#blueline
I'll try it again though. Thanks for noticing that.
Click to expand...
Click to collapse
Succes, and let me know if you succeeded flashing.
9.0.0 (PQ2A.190405.003, Apr 2019) Link c12f40f0b189eb2daa80d029917bc9a8841da89cfcafa21b8f61b0d9f90826e7

Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.

I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.

cmorin543 said:
Still no luck. I double checked and then redownloaded the .img file you referenced and it is the same as I tried and gives the same results.
Click to expand...
Click to collapse
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!

wangdaning said:
I think you need to fastboot format userdata, but I have not used that command on this device. If it wont do it automatically you probably need to do it manually. Look into that option. There should have never been a need to mess with any of the file systems on this device.
Click to expand...
Click to collapse
I should've mentioned that I did do the format of userdata at one point and it didn't make a difference.
sakerhetz said:
Strange, and if you download the factory image?
You can flash it in all in one tool or with ADB.
So try factory with flash_all .bat
Succes!!
Click to expand...
Click to collapse
I tried using the flash_all.bat with no joy and I also tried using twrp (when I was actually able to boot into it) to sideload the OTA zip still with no joy.
I think I'm just going to contact Google and see what they can do -- the phone is technically still under warranty and I am still able to re-lock the bootloader... I appreciate the help.

Maybe try:
1) fastboot erase userdata
2) flash-all.bat
If no good:
1) fastboot erase userdata
2) fastboot format userdata
3) flash-all.bat
Everything will be gone, but already is from what you have said.

if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.

SacredDeviL666 said:
if you have downloaded the correct factory image as you mentioned then it should wipe out everything and fix your userdata even if its corrupt with flash.all bat script.
you could alternatively take a look at the detailed steps here just download the blueline img instead of crosshatch... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
Steps are exactly the same.
Click to expand...
Click to collapse
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
I will double check that. Thanks!

cmorin543 said:
That link you provided is the guide I attempted to use when the flash_all.bat didn't work.
Click to expand...
Click to collapse
just to confirm.
a) you booted to bootloader using power + volume down key and then use volume down key to change it to bootloader and press power again (this reboots the bootloader)
b) while you are inside the ADB folder use shift + right click while you are inside the adb folder and then select the option -- open command window here.
c) considering that you have already connected your pixel to pc via usb type the command " fastboot devices " in the command prompt window to ensure that your device is detected.
d) once it has detected the device/s proceed to unzip the april factory image from https://dl.google.com/dl/android/aosp/blueline-pq2a.190405.003-factory-c12f40f0.zip in the same folder as ADB
e) Double click on flash.all bat file and let us know the result.
I am sure you might have followed above steps but just to make sure if everything is covered. as the above should actually fix all partition errors.

pacman420 said:
Are you using the most recent ADB? I have had that exact missing variable error during a factory image flash and updating to the newest ADB fixed it for me.
Click to expand...
Click to collapse
You are a genius -- apparently I did have the newest version of ADB in my downloads folder, but I was so used to using a specific directory with platform-tools for my old phone, I didn't realize it was an old version -- tried it with the newest version of ADB and it worked like a charm... too bad I already contacted google and they're sending me a new phone.. :-\
Thanks again for all your help guys.

[Solved] Can't update OTA with flash_all.bat

Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 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'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.

oldbear3 said:
Hi,
I wanted to use the method described here to flash the last update to my Pixel3a, stuck to the october update : https://forum.xda-developers.com/t/...ut-twrp-take-ota-updates-once-rooted.3929053/
I did everything described, but the update doesn't work.
Here what I have in the end of the flash process on the CMD window :
Code:
target reported max download size of 268435456 bytes
sending 'bootloader' (8373 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.3-6863017
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.235s]
finished. total time: 0.525s
rebooting into bootloader...
OKAY [ 0.053s]
finished. total time: 0.053s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.734s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00084-201008-B-6891501
(bootloader) Flashing partition modem_b
OKAY [ 0.550s]
finished. total time: 2.309s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.074s
target reported max download size of 268435456 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'
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00084-201008-B-6891501
Serial Number........: [HIDDEN FOR THIS POST]
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking version-bootloader...
OKAY [ 0.059s]
checking version-baseband...
OKAY [ 0.055s]
sending 'boot' (65536 KB)...
OKAY [ 1.519s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 1.982s
Press any key to exit...
I see that the "fail" happens while writing 'boot' but I ignore while it does fail. *
Could you please help me ?
Thanks in advance.
Click to expand...
Click to collapse
Did you try flashing the system image instead of the OTA? Also did you try a different cord?

MoistPicklez said:
Did you try flashing the system image instead of the OTA? Also did you try a different cord?
Click to expand...
Click to collapse
Sorry, in fact I use the factory image because there is no flash_all.bat in the OTA zip.
I will try with another cord but I'd be surprised it would change anything, as all other operations worked well with this cable...
Also, I can't enter in recovery mode : when I enter into recovery mode, I don't have any options : it says "No Command"... I don't know why.

Ok i tried the other way with OTA updates via recovery.
Thanks for yout help !