Hi folks. Friend managed to brick his pixel XL. Keeps booting into the no-command image, and cannot boot into safe mode. He would like to avoid factory resetting it as not all of his pictures are uploaded into his google drive. (He doesn't like the idea of big brother spying on him). Is there any way to recover the images?
How did he brick it?
ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.
Mr. Orange 645 said:
How did he brick it?
Click to expand...
Click to collapse
He has no idea. According to him, it just happened during the day.
CZ Eddie said:
I can't think of what this is.
Are you talking about the android laying on its side like in my forum picture?
If the phone can be rebooted to Recovery mode, then your friend can use a Computer to transfer the files off the phone.
Click to expand...
Click to collapse
Sadly, he cannot boot into Recovery mode. It say "/cache not found" or something like that. Sorry, I don't have the phone with me, and I'm not at his house right now.
If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.
ThatZeldaFan50 said:
Keeps booting into the no-command image
Click to expand...
Click to collapse
Oh, is that the stock Recovery?
Cool.
He can use ADB from there to recover and transfer files & stuff.
CZ Eddie said:
If he can get to Fastboot then he can flash the stock image on top of the current image without losing any setup apps/data/pics.
Just remove the -w from the script.
My guide will walk him through the process.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Remember to remove the -w from the script though!
Or download the -w modded script I added to my thread.
If he can't get to either Fastboot OR Recovery then I'd consider that a "hard brick".
Are you sure he really knows how to boot to Fastboot and Recovery? Maybe he's doing that wrong. It's easy to mess up.
Click to expand...
Click to collapse
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app
yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've never tested that before.
It does write *something* to both slots though.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.909s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.709s]
finished. total time: 5.617s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.062s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.445s]
writing 'radio_a'...
OKAY [ 0.570s]
finished. total time: 2.015s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for any device >
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-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (26209 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.298s]
erasing 'system_a'...
OKAY [ 0.367s]
sending sparse 'system_a' 1/4 (515538 KB)...
OKAY [ 13.254s]
writing 'system_a' 1/4...
OKAY [ 5.541s]
sending sparse 'system_a' 2/4 (521786 KB)...
OKAY [ 13.566s]
writing 'system_a' 2/4...
OKAY [ 5.138s]
sending sparse 'system_a' 3/4 (491987 KB)...
OKAY [ 12.766s]
writing 'system_a' 3/4...
OKAY [ 6.688s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.848s]
writing 'system_a' 4/4...
OKAY [ 0.350s]
erasing 'system_b'...
OKAY [ 0.402s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.417s]
writing 'system_b' 1/4...
OKAY [ 3.986s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.119s]
writing 'system_b' 2/4...
OKAY [ 4.297s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.508s]
writing 'system_b' 3/4...
OKAY [ 3.888s]
sending sparse 'system_b' 4/4 (85782 KB)...
OKAY [ 2.247s]
writing 'system_b' 4/4...
OKAY [ 0.810s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235322 KB)...
OKAY [ 5.841s]
writing 'vendor_a'...
OKAY [ 3.752s]
Setting current slot to 'a'...
OKAY [ 0.058s]
erasing 'userdata'...
OKAY [ 2.286s]
sending 'userdata' (138957 KB)...
OKAY [ 3.450s]
writing 'userdata'...
OKAY [ 1.300s]
rebooting...
finished. total time: 132.460s
Press any key to exit...
yankeesfan714 said:
If I am running Resurrection and I am on slot B, can just use the flashall in adb regardless of which slot I'm on?
Click to expand...
Click to collapse
It doesn't matter which slot you're on. You can use the flash all. It will automatically flash to the active slot.
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
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'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!
I'm trying to flash a factory image. I'm using the guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 . I really have no idea what I'm doing wrong... the procedure is so simple, download the factory image and run flash-all.bat It goes, but I get errors. I searched but all I could find was a guy flashing the wrong image. I am using "taimen-opd1.170816.025-factory-907c4030" from https://developers.google.com/android/images. I was on 8.1.1 and want to go back due to multi-touch issues. Below is my log:
target reported max download size of 536870912 bytes
sending 'bootloader' (55680 KB)...
OKAY [ 1.252s]
writing 'bootloader'...
OKAY [ 0.564s]
finished. total time: 104.574s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.358s]
writing 'radio'...
OKAY [ 0.563s]
finished. total time: 1.931s
rebooting into bootloader...
OKAY [ 0.004s]
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...: TMZ10n
Baseband Version.....: g8998-00122-1708311414
Serial Number........: 712KPHG1155193
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (40960 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 0.376s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.421s]
writing 'system'...
OKAY [ 2.436s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.139s]
writing 'system'...
OKAY [ 2.408s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.975s]
writing 'system'...
OKAY [ 2.416s]
sending sparse 'system' (338968 KB)...
OKAY [ 8.364s]
writing 'system'...
OKAY [ 1.568s]
sending 'vendor' (349428 KB)...
OKAY [ 7.941s]
writing 'vendor'...
OKAY [ 1.607s]
erasing 'userdata'...
OKAY [ 0.591s]
sending 'userdata' (140898 KB)...
OKAY [ 3.031s]
writing 'userdata'...
OKAY [ 1.496s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 72.790s
Press any key to exit...
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
machx1111 said:
Well, it always happens this way - I create the thread and the issue is instantly fixed. I was using a usb2 hub hearing it was more stable. Remove the hub and flash and it works... FYI if anyone runs into the same issue.
Click to expand...
Click to collapse
Glad you got it fixed.
Adb & flashing rules:
1. Connect phone directly to computer. Don't use USB hub
2. Use the USB cable that came with phone, if possible
3. If it still fails, try a different cable or USB port
If adb recognizes the device, that means your adb environment is setup correctly and adb is working. If flashing still fails at this point, that means your cable or port is bad.
Yesterday I got notification from Motorola Update Services about system update version OCXS27.1.2 (Android security updates thru March 1 2018). I download but it fails to install. [Software updated unsuccessful - Sorry, there was a problem updating your Moto Z². No changes were Made. √ OK]
I bought the phone used so dunno it's history. After purchase I unlocked bootloader and installed TWRP but have not rooted. I had it carrier unlocked thru an online service that enabled the T-mobile app on the server side (cellunlocker.net), and installed FreedomPop SIM card.
I called Motorola tech support. They first had me reset app preferences then passed me off to level 2 support after that didn't work, who had me factory data reset, and now they're passing me off to level 3 who may call me next week, since that didn't work either. Note when I did the factory data reset, it rebooted into TWRP automatically which asked for my lockcode, before (apparently) handling the reset request. After reboot I skipped the google login to make sure nothing conflicted, but it still won't do the system update.
I'm wondering if it possibly has to do with the phone's history somehow, or because I unlocked bootloader, or because I'm not using a T-Mobile SIM card, or because I installed TWRP. I dunno. I told this to Moto support and they didn't seem to care or think it mattered. They could see my resets from their side after I provided my IMEI.
Any ideas?
Having twrp flashed modifies /boot as our recovery is in the ramdisk in our /boot, which causes ota to fail. Fastboot flash stock boot.img for your current os (ncx26.2, ncx26.7, ocx27 or, ocx27.1) from the corresponding firmware package (flashall .zip) and you should be good to go. The official twrp can be booted now so no need to have it installed. If you do root in the future the same rule will apply as systemless root is also in /boot.
Sent from my Moto Z (2) using XDA Labs
Installing twrp mounted system as rw. You need to actually do a flash all with the official firmware by the Motorola Firmware Team on AFH. I have a thread in the guides section that educates on how to do this. Tier 3 will probably suggest the same.
You are probably getting this same error. It means you need to flash all with an official zip to have the update go through correctly.
Thanks much. I was a little worried as there seems to be an error message about file system, a scary looking warning, and FAILURE message near the end, but seems to have worked, and was able to OTA update after flashall. The only thing the instructions didn't specifically mention was to start phone with volume down+-power for fastboot, once I figured that out all was well.
Code:
Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\>mkdir \Z2-Util
C:\>cd \Z2-Util
C:\Z2-Util>dir
Volume in drive C has no label.
Volume Serial Number is B45D-BE40
Directory of C:\Z2-Util
05/06/2018 03:45 PM <DIR> .
05/06/2018 03:45 PM <DIR> ..
12/30/2017 04:19 PM 1,784,320 adb.exe
12/30/2017 04:19 PM 97,792 AdbWinApi.dll
12/30/2017 04:19 PM 62,976 AdbWinUsbApi.dll
01/30/2018 02:22 PM 16,777,216 adspso.bin
01/30/2018 02:22 PM 23,905,510 boot.img
01/30/2018 02:22 PM 10,121,472 bootloader.img
01/30/2018 02:22 PM 4,604,160 BTFM.bin
12/30/2017 04:19 PM 853,504 fastboot.exe
04/23/2018 09:17 PM 1,433 flashall.bat
01/30/2018 04:24 PM 3,009 flashfile.xml
01/30/2018 02:22 PM 5,730,304 fsg.mbn
01/30/2018 02:22 PM 211,712 gpt.bin
01/30/2018 02:22 PM 3,227,518 logo.bin
01/30/2018 04:24 PM 911 NASH_TMO_C_OCX27.109-51_subsidy-TMO_regulatory-DEFAULT_CFC.info.txt
01/30/2018 02:22 PM 99,753,156 NON-HLOS.bin
01/30/2018 02:17 PM 179,898,736 oem.img
01/30/2018 04:23 PM 0 regulatory_info_default.png
01/30/2018 04:24 PM 2,701 servicefile.xml
01/30/2018 04:22 PM 610 slcf_rev_d_tmo_rsu_v1.1.nvm
01/30/2018 04:23 PM 528,589,836 system.img_sparsechunk.0
01/30/2018 04:23 PM 507,000,512 system.img_sparsechunk.1
01/30/2018 04:23 PM 531,596,644 system.img_sparsechunk.2
01/30/2018 04:23 PM 536,338,408 system.img_sparsechunk.3
01/30/2018 04:23 PM 528,569,592 system.img_sparsechunk.4
01/30/2018 04:23 PM 430,677,116 system.img_sparsechunk.5
01/30/2018 04:24 PM 527,547,620 system_b.img_sparsechunk.0
01/30/2018 04:24 PM 314,597,544 system_b.img_sparsechunk.1
27 File(s) 4,251,954,312 bytes
2 Dir(s) 250,683,760,640 bytes free
C:\Z2-Util>flashall
C:\Z2-Util>fastboot oem fb_mode_set
< waiting for any device >
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\Z2-Util>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.012s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.250s]
finished. total time: 0.267s
C:\Z2-Util>fastboot flash bootloader_a bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (9884 KB)...
OKAY [ 0.454s]
writing 'bootloader_a'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.661s
C:\Z2-Util>fastboot flash bootloader_b bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (9884 KB)...
OKAY [ 0.365s]
writing 'bootloader_b'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.243s]
finished. total time: 0.627s
C:\Z2-Util>fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97415 KB)...
OKAY [ 4.009s]
writing 'modem_a'...
OKAY [ 1.047s]
finished. total time: 5.055s
C:\Z2-Util>fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5596 KB)...
OKAY [ 0.266s]
writing 'fsg_a'...
OKAY [ 0.078s]
finished. total time: 0.344s
C:\Z2-Util>fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (97415 KB)...
OKAY [ 3.016s]
writing 'modem_b'...
OKAY [ 1.031s]
finished. total time: 4.063s
C:\Z2-Util>fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (5596 KB)...
OKAY [ 0.172s]
writing 'fsg_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot flash bluetooth_a BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_a'...
OKAY [ 0.047s]
finished. total time: 0.234s
C:\Z2-Util>fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.625s]
writing 'dsp_a'...
OKAY [ 0.156s]
finished. total time: 0.781s
C:\Z2-Util>fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3151 KB)...
OKAY [ 0.141s]
writing 'logo_a'...
OKAY [ 0.047s]
finished. total time: 0.187s
C:\Z2-Util>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.937s]
writing 'boot_a'...
OKAY [ 0.391s]
finished. total time: 1.344s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516201 KB)...
OKAY [ 20.836s]
writing 'system_a'...
OKAY [ 5.582s]
finished. total time: 26.434s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (495117 KB)...
OKAY [ 20.062s]
writing 'system_a'...
OKAY [ 4.869s]
finished. total time: 24.930s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519137 KB)...
OKAY [ 20.861s]
writing 'system_a'...
OKAY [ 5.812s]
finished. total time: 26.689s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523767 KB)...
OKAY [ 22.962s]
writing 'system_a'...
OKAY [ 4.966s]
finished. total time: 27.928s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (516181 KB)...
OKAY [ 25.824s]
writing 'system_a'...
OKAY [ 5.688s]
finished. total time: 31.512s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (420583 KB)...
OKAY [ 18.590s]
writing 'system_a'...
OKAY [ 3.969s]
finished. total time: 22.559s
C:\Z2-Util>fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (175682 KB)...
OKAY [ 7.904s]
writing 'oem_a'...
OKAY [ 1.781s]
finished. total time: 9.686s
C:\Z2-Util>fastboot flash bluetooth_b BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot flash dsp_b adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_b' (16384 KB)...
OKAY [ 0.750s]
writing 'dsp_b'...
OKAY [ 0.156s]
finished. total time: 0.922s
C:\Z2-Util>fastboot flash logo_b logo.bin
target reported max download size of 536870912 bytes
sending 'logo_b' (3151 KB)...
OKAY [ 0.172s]
writing 'logo_b'...
OKAY [ 0.047s]
finished. total time: 0.219s
C:\Z2-Util>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (23345 KB)...
OKAY [ 0.812s]
writing 'boot_b'...
OKAY [ 0.391s]
finished. total time: 1.203s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (516201 KB)...
OKAY [ 22.460s]
writing 'system_b'...
OKAY [ 5.437s]
finished. total time: 27.898s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (495117 KB)...
OKAY [ 20.393s]
writing 'system_b'...
OKAY [ 4.872s]
finished. total time: 25.281s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (519137 KB)...
OKAY [ 21.401s]
writing 'system_b'...
OKAY [ 5.859s]
finished. total time: 27.260s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_b' (523767 KB)...
OKAY [ 22.156s]
writing 'system_b'...
OKAY [ 4.984s]
finished. total time: 27.141s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_b' (516181 KB)...
OKAY [ 21.069s]
writing 'system_b'...
OKAY [ 5.667s]
finished. total time: 26.767s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_b' (420583 KB)...
OKAY [ 17.404s]
writing 'system_b'...
OKAY [ 3.994s]
finished. total time: 21.398s
C:\Z2-Util>fastboot flash oem_b oem.img
target reported max download size of 536870912 bytes
sending 'oem_b' (175682 KB)...
OKAY [ 6.563s]
writing 'oem_b'...
OKAY [ 1.766s]
finished. total time: 8.328s
C:\Z2-Util>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Z2-Util>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.203s]
finished. total time: 1.203s
C:\Z2-Util>fastboot --set-active=other
Setting current slot to 'b'...
(bootloader) WARNING: Bootloader images on target slot b are not valid!!
(bootloader) There is risk of bricking HW. Please flash valid bootloader
(bootloader) into slot b before activating it. OR you could force to
(bootloader) switch to slot b by running the same command again
(bootloader) within 30 s if you understand what you're doing
FAILED (remote failure)
finished. total time: 0.141s
C:\Z2-Util>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>
I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.
Unseeablething said:
I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.
Click to expand...
Click to collapse
You installed magisk which mounted a partition as r/w
Uzephi said:
You installed magisk which mounted a partition as r/w
Click to expand...
Click to collapse
Got it! Guess at this point, I'll just go over to DU.
So is there anything we can do to keep root and install updates?
teradark said:
So is there anything we can do to keep root and install updates?
Click to expand...
Click to collapse
Not really. The Motorola OTA checks the hash sum of each partition and if there is any discrepancy on partitions you wouldn't be able to edit without unlocking, it will fail as shown in the ota error message image a few posts back.
So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?
teradark said:
So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?
Click to expand...
Click to collapse
Root mounts system and maybe other partitions as read/write when they aren't supposed to be, making the hash sum different. You would need to at least flash the official system sparses from the Motorola firmware team's flash all if not more than that. (Root is nestled in boot, so you'd need to flash that as well).
Well I can't update again but for some other reason, even after flashall.
Previously it was cuz of TWRP so flashall then OTA update no problem. Then I installed magisk and adaway and all fine. Then I was trying to figure out how to get rid of tmobile stuff, tried a couple apps on playstore, including titanium backup, but couldn't figure it out. Then I saw someone wrote an exe to do it (debload) and running that made phone not boot. flashall again, try debload, it works, happy, but can't find update (different message, says there are no updates). Disappointed but decide rather have no t-mobile apps than update, so move on and install magisk. Then it can't boot. Decide I'd rather have adaway than no t-mobile so flashall again, but still can't update.
So other than installing magisk or twrp, what could make it so I can't update immediately after flashall? I imagine that debload did something that flashall doesn't undo, but there's no real detail or source/etc about what it's doing other than removing oem partition, but I see flashall puts that back so doesn't seem like that's it...
So I flash all and installed the OTA, does this mean that since i installed the OTA that i cant install the flash all manual update(btw updating this device is a pain on linux)
I'm trading my Pixel 3 for the Pixel 3 XL.
I received the 3XL and I first want to update to the latest image.
About says Build Number PQ2A.190205.001.
I downloaded "crosshatch-pq3a.190801.002-factory-15db810d.zip", and unzipped to a temporary directory on a Windows 10 system (the same system I successfully performed a factory flash on the Pixel 3, using the same process, in April)
I ran flash-all.bat, and have the following log output:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.253s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(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.591s]
finished. total time: 0.850s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.657s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.282s]
finished. total time: 1.945s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 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...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A******C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.365s
Press any key to exit...
After this process the phone boots to the factor reset startup process. It is still at Build Number PQ2A.190205.001.
In the log (above), there are multiple messages of the form "archive does not contain '*.img'"
At the end "FAILED (remote: variable not found)"
Any guidance on what went wrong?
I can verify that in the Temp folder I extracted the downloaded ZIP file to, there is another ZIP. image-crosshatch-pq3a.190801.002.zip. That ZIP passes an integrity check. Inside that ZIP there are 20 files (.img and other)
timg11 said:
I'm trading my Pixel 3 for the Pixel 3 XL.
I received the 3XL and I first want to update to the latest image.
About says Build Number PQ2A.190205.001.
I downloaded "crosshatch-pq3a.190801.002-factory-15db810d.zip", and unzipped to a temporary directory on a Windows 10 system (the same system I successfully performed a factory flash on the Pixel 3, using the same process, in April)
I ran flash-all.bat, and have the following log output:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8493 KB)...
OKAY [ 0.253s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.1-5578427
(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.591s]
finished. total time: 0.850s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 bytes
sending 'radio_a' (71132 KB)...
OKAY [ 1.657s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.282s]
finished. total time: 1.945s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.074s
target reported max download size of 268435456 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...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A******C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.365s
Press any key to exit...
After this process the phone boots to the factor reset startup process. It is still at Build Number PQ2A.190205.001.
In the log (above), there are multiple messages of the form "archive does not contain '*.img'"
At the end "FAILED (remote: variable not found)"
Any guidance on what went wrong?
I can verify that in the Temp folder I extracted the downloaded ZIP file to, there is another ZIP. image-crosshatch-pq3a.190801.002.zip. That ZIP passes an integrity check. Inside that ZIP there are 20 files (.img and other)
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools.
Tulsadiver said:
Make sure you have the latest sdk platform tools.
Click to expand...
Click to collapse
Code:
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
>fastboot --version
fastboot version 0e9850346394-android
I'll check to see if there are any newer, but this version worked properly on Pixel 3 in April.
Updated Android Platform Tools to platform-tools_r29.0.2-windows.zip
Code:
>fastboot --version
fastboot version 0e9850346394-android
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
Same result:
Code:
>fastboot -w update image-crosshatch-pq3a.190801.002.zip
target reported max download size of 268435456 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...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A*****C1
--------------------------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.364s
This item seems odd: "target reported max download size of 268435456 bytes"
That logged after command "fastboot -w update image-crosshatch-pq3a.190801.002.zip", which is 1.75 Gbytes in size.
The reported max download size is 268 Mbytes 268,435,456
The phone has 128 Gbytes of storage.
No the download size is normal. You're not writing directly to the internal storage but to a ramdisk, where stuff gets unpacked and written to the correct partition afterwards. Your problem is definitely the "checking partition-exists... FAILED" part. Don't know what could cause that off the top of my head though.
timg11 said:
Updated Android Platform Tools to platform-tools_r29.0.2-windows.zip
Code:
>fastboot --version
fastboot version 0e9850346394-android
>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
-------------------------
checking product...
OKAY [ 0.061s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.364s
[/CODE]
This item seems odd: "target reported max download size of 268435456 bytes"
That logged after command "fastboot -w update image-crosshatch-pq3a.190801.002.zip", which is 1.75 Gbytes in size.
The reported max download size is 268 Mbytes 268,435,456
The phone has 128 Gbytes of storage.
Click to expand...
Click to collapse
I believe that is why system images are broken down into parts. This isn't the problem. At this point your phone is supposed to boot into fastbootd and something is preventing this. Have you tried doing a factory reset first?
Edit: can you run bash script? I run flash-all.sh on my windows 10.
Tulsadiver said:
I believe that is why system images are broken down into parts. This isn't the problem. At this point your phone is supposed to boot into fastbootd and something is preventing this. Have you tried doing a factory reset first?
Edit: can you run bash script? I run flash-all.sh on my windows 10.
Click to expand...
Click to collapse
Download the ota image, and ad sideload from recovery, providing you've not corrupt the phone, it will work. The full factory image flash is messed up imho. Having to unlock the phone to flash a factory image just says it all.
I found the issue - A Windows Path problem. The path was pointing to an older installation of Android Platform Tools different from where I installed the update.
I looked at the versions before and after updating and they were the same. There should have been at least some change.
I fixed the path, and just copied the tools to the update directory as a short term fix.
Here is how the versions look for the latest tools:
Code:
>fastboot --version
fastboot version 29.0.2-5738569
Installed as D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002\fastboot.exe
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>adb version
Android Debug Bridge version 1.0.41
Version 29.0.2-5738569
Installed as D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002\adb.exe
Here's how a successful factory update flash looks for anyone else who needs a reference:
Code:
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>flash-all.bat
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5578427.img
Sending 'bootloader_a' (8493 KB) OKAY [ 0.284s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
(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.512s]
Finished. Total time: 1.050s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.052s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>ping -n 5 127.0.0.1 1>nul
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot flash radio radio-crosshatch-g845-00017-190312-b-5369743.img
Sending 'radio_a' (71132 KB) OKAY [ 1.689s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00017-190312-B-5369743
(bootloader) Flashing partition modem_a
OKAY [ 0.296s]
Finished. Total time: 2.300s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.046s]
Finished. Total time: 0.053s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>ping -n 5 127.0.0.1 1>nul
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>fastboot -w update image-crosshatch-pq3a.190801.002.zip
--------------------------------------------
Bootloader Version...: b1c1-0.1-5578427
Baseband Version.....: g845-00017-190312-B-5369743
Serial Number........: 8A*****C1
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.050s]
Checking 'version-bootloader' OKAY [ 0.058s]
Checking 'version-baseband' OKAY [ 0.058s]
Setting current slot to 'a' OKAY [ 0.071s]
extracting boot.img (64 MB) to disk... took 0.263s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.567s]
Writing 'boot_a' OKAY [ 0.209s]
extracting dtbo.img (8 MB) to disk... took 0.055s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.273s]
Writing 'dtbo_a' OKAY [ 0.071s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.114s]
Writing 'vbmeta_a' OKAY [ 0.054s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (194 MB) to disk... took 0.669s
archive does not contain 'product.sig'
Sending 'product_a' (199284 KB) OKAY [ 4.628s]
Writing 'product_a' OKAY [ 0.572s]
extracting system.img (2201 MB) to disk... took 9.765s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 6.222s]
Writing 'system_a' OKAY [ 0.062s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 6.132s]
Writing 'system_a' OKAY [ 0.059s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 6.184s]
Writing 'system_a' OKAY [ 0.362s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 6.186s]
Writing 'system_a' OKAY [ 0.361s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 6.215s]
Writing 'system_a' OKAY [ 0.363s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 6.076s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 6.199s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 8/9 (258820 KB) OKAY [ 6.068s]
Writing 'system_a' OKAY [ 0.364s]
Sending sparse 'system_a' 9/9 (160160 KB) OKAY [ 3.829s]
Writing 'system_a' OKAY [ 0.762s]
archive does not contain 'system_ext.img'
extracting system_other.img (422 MB) to disk... took 1.934s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 6.162s]
Writing 'system_b' OKAY [ 0.363s]
Sending sparse 'system_b' 2/2 (170820 KB) OKAY [ 4.096s]
Writing 'system_b' OKAY [ 0.853s]
extracting vendor.img (446 MB) to disk... took 1.973s
archive does not contain 'vendor.sig'
Sending sparse 'vendor_a' 1/2 (262140 KB) OKAY [ 6.295s]
Writing 'vendor_a' OKAY [ 0.364s]
Sending sparse 'vendor_a' 2/2 (195404 KB) OKAY [ 4.609s]
Writing 'vendor_a' OKAY [ 0.870s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 15.316s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.100s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.044s]
Finished. Total time: 128.702s
D:\Download\Hardware\Google\Pixel3XL\Temp\crosshatch-pq3a.190801.002>
Interesting to note that there are still various "archive image does not contain...." and "file system not supported" messages, but apparently they are normal.