Develop Bugs

Pixel XL is bricked.

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.

Issue with touch input after flashing 8.1 factory image

I picked up my Pixel 2 XL yesterday. I set it up to check it out and everything worked fine on it. It is a google version and I haven't put my Verizon SIM in it just yet. I started off with unlocked the bootloader and bootloader_critical without any issues. I then want to upgrade from 8.0 to 8.1 by flashing the stock image. I flashed it using the flash-all.sh on a linux machine. The flash when just fine but now my device won't accept touch input. I am able to interact with it using a wireless mouse via the usb-c to usb adapter.
My question is, has anyone experienced this and what should I do to fix this issue?
I have tried flashing back to the most recent 8.0 using stock factory image on both a linux and windows machine. I haven also used the Android ToolKit with the most update to date version. I've looked around online and I didn't see someone else with this issue but if this has been posted before, I'm sorry for posting this again. I also want to say that I did post this over on reddit on /r/AndroidQuestions last night.

Have you downloaded the 8.1 factory image and just installed from scratch using the flash all?

CyberpodS2 said:
Have you downloaded the 8.1 factory image and just installed from scratch using the flash all?
Click to expand...
Click to collapse
Yeah, I just tried that. I downloaded the 8.1 image and flashed using the flash-all.bat. Below I have the output from the terminal.
Code:
E:\Downloads\taimen-opm1.171019.011-factory-2df1c1cb\taimen-opm1.171019.011>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.769s]
writing 'bootloader_a'...
OKAY [ 0.230s]
finished. total time: 1.002s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.277s]
writing 'radio_a'...
OKAY [ 0.844s]
finished. total time: 2.123s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.160s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 8.534s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 3.011s
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 (349 MB) to disk... took 1.823s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 4b8c28b4-e04f-11e7-9be1-e19bdc4c5f9d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot_a' (40960 KB)...
OKAY [ 0.865s]
writing 'boot_a'...
OKAY [ 0.554s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.174s]
writing 'dtbo_a'...
OKAY [ 0.105s]
erasing 'system_a'...
OKAY [ 0.050s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 11.581s]
writing 'system_a' 1/4...
OKAY [ 2.212s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 11.559s]
writing 'system_a' 2/4...
OKAY [ 2.220s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 11.579s]
writing 'system_a' 3/4...
OKAY [ 2.212s]
sending sparse 'system_a' 4/4 (410112 KB)...
OKAY [ 9.067s]
writing 'system_a' 4/4...
OKAY [ 1.724s]
erasing 'system_b'...
OKAY [ 0.039s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 11.477s]
writing 'system_b' 1/2...
OKAY [ 2.207s]
sending sparse 'system_b' 2/2 (57588 KB)...
OKAY [ 1.262s]
writing 'system_b' 2/2...
OKAY [ 0.247s]
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta_a'...
OKAY [ 0.004s]
erasing 'vendor_a'...
OKAY [ 0.017s]
sending 'vendor_a' (357904 KB)...
OKAY [ 7.623s]
writing 'vendor_a'...
OKAY [ 1.508s]
Setting current slot to 'a'...
OKAY [ 0.013s]
erasing 'userdata'...
OKAY [ 0.813s]
sending 'userdata' (5341 KB)...
OKAY [ 0.115s]
writing 'userdata'...
OKAY [ 0.046s]
rebooting...
finished. total time: 79.315s
Press any key to exit...

Trying to flash factory to my unlocked bootloader P2XL. Please help!

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.

Soft Brick Help

In a boot loop on my rooted Pixel 2XL. Tried patching Magisk image to maintain root and now I'm stuck
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 0.284s]
writing 'radio'...
OKAY [ 0.562s]
finished. total time: 0.850s
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)[/B][/B]
--------------------------------------------
Bootloader Version...: TMZ30l
Baseband Version.....: g8998-00020-1912122233
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (40960 KB)...
OKAY [ 0.192s]
writing 'boot'...
OKAY [ 0.373s]
sending sparse 'system' (524284 KB)...
OKAY [ 3.239s]
writing 'system'...
OKAY [ 2.406s]
sending sparse 'system' (524284 KB)...
OKAY [ 3.251s]
writing 'system'...
OKAY [ 2.425s]
sending sparse 'system' (524284 KB)...
OKAY [ 3.157s]
writing 'system'...
OKAY [ 2.406s]
sending sparse 'system' (524284 KB)...
OKAY [ 3.170s]
writing 'system'...
OKAY [ 2.409s]
sending sparse 'system' (340280 KB)...
OKAY [ 2.064s]
writing 'system'...
OKAY [ 1.570s]
sending 'vendor' (349196 KB)...
OKAY [ 1.615s]
writing 'vendor'...
OKAY [ 1.604s]
erasing 'userdata'...
OKAY [ 0.586s]
sending 'userdata' (140898 KB)...
OKAY [ 0.652s]
writing 'userdata'...
OKAY [ 1.471s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 32.647s
These seem to be issues...
"Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)"
"erasing 'cache'...
FAILED (remote: Check device console.)"
I'm inexperienced and need some guidance. Thanks in advance.

Tried what how? ?
You could try booting a recovery in fastboot; fastboot boot recovery.img
You have an A and B slot to tinker with.

Make sure you have the latest adb binaries and also try a different cable or USB port on your computer.

Maybe try to flash a factory image

Help... Soft-bricked New Pixel 2 XL... Fastboot Flash Stock Does Not Work'

EDIT: I ran this tool and it brought the phone back to life! Not sure why the flash all script is broken. I will keep this thread open and post the log that this tool generated and hopefully the community can figure out what happened. I noticed the all-in-one tool flashed some additional partitions like "dtbo" that the flash all script did not.
Just got a used device, figured i'd unlock bootloader and update it via fastboot instead of OTA. Unlocked bootloader, ddownloaded image from Google site, ran flash-all.bat. Now when device starts, right after the bootloader unlocked warning, I get the Google logo, then device is corrupt and untrusted warning, then a bootloop. Trying to clear the cache does not work (see error in output below). Clearing data via recovery works, but does not help. I have a fair amount of experience with this. What am I missing!?
What I have already tried:
* Update fastboot to latest version:
Code:
> fastboot --version
fastboot version eac51f2bb6a8-android
* Try Different Cable/USB Port
* Try running "fastboot flashing unlock_critical":
FAILED (remote: Device already : unlocked!)
Click to expand...
Click to collapse
* Using the July 2019 update instead of the latest
* Google research
Sometimes I get this from the flash all command. Sometimes writing user-data works, but clearing cache gives "Error: Check device Console":
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.795s]
writing 'bootloader'...
OKAY [ 0.556s]
finished. total time: 1.354s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.285s]
writing 'radio'...
OKAY [ 0.408s]
finished. total time: 1.872s
rebooting into bootloader...
OKAY [ 0.002s]
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'
W/ ( 7216): Zip: unable to truncate file to 357556432: File too large
failed to extract 'vendor.img': I/O Error
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
error: file_write: write: No space left on device
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ30l
Baseband Version.....: g8998-00020-1912122233
Serial Number........: 906KPJP2073036
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (40960 KB)...
OKAY [ 0.865s]
writing 'boot'...
OKAY [ 0.250s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.159s]
writing 'system'...
OKAY [ 3.249s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.145s]
writing 'system'...
OKAY [ 3.265s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.331s]
writing 'system'...
OKAY [ 3.247s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.289s]
writing 'system'...
OKAY [ 3.262s]
sending sparse 'system' (340228 KB)...
OKAY [ 7.984s]
writing 'system'...
OKAY [ 2.102s]
erasing 'userdata'...
OKAY [ 1.127s]
sending 'userdata' (138830 KB)...
OKAY [ 2.923s]
writing 'userdata'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 78.283s
Press any key to exit...
Log from successful flash with all-in-one tool:
Code:
Sending 'bootloader_a' (36356 KB) OKAY [ 0.792s]
Writing 'bootloader_a' OKAY [ 0.547s]
Finished. Total time: 1.412s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
Sending 'radio_a' (60388 KB) OKAY [ 1.325s]
Writing 'radio_a' OKAY [ 0.397s]
Finished. Total time: 1.897s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.006s
--------------------------------------------
Bootloader Version...: TMZ30l
Baseband Version.....: g8998-00020-1912122233
Serial Number........: 906KPJP2073036
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.009s]
extracting boot.img (40 MB) to disk... took 0.277s
archive does not contain 'boot.sig'
Sending 'boot_a' (40960 KB) OKAY [ 0.891s]
Writing 'boot_a' OKAY [ 0.253s]
extracting dtbo.img (8 MB) to disk... took 0.023s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.178s]
Writing 'dtbo_a' OKAY [ 0.057s]
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.001s]
Writing 'vbmeta_a' OKAY [ 0.002s]
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'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (2380 MB) to disk... took 13.415s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 11.907s]
Writing 'system_a' OKAY [ 3.243s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 11.848s]
Writing 'system_a' OKAY [ 3.248s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 12.040s]
Writing 'system_a' OKAY [ 3.243s]
Sending sparse 'system_a' 4/5 (524284 KB) OKAY [ 11.884s]
Writing 'system_a' OKAY [ 3.252s]
Sending sparse 'system_a' 5/5 (340228 KB) OKAY [ 7.723s]
Writing 'system_a' OKAY [ 2.115s]
extracting system_other.img (306 MB) to disk... took 2.303s
archive does not contain 'system.sig'
Sending 'system_b' (313556 KB) OKAY [ 7.041s]
Writing 'system_b' OKAY [ 1.940s]
extracting vendor.img (340 MB) to disk... took 2.480s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (349176 KB) OKAY [ 7.777s]
Writing 'vendor_a' OKAY [ 2.166s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.376s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: 09419b40-81a8-11ea-8938-4b5d199bc358
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4400 KB) OKAY [ 0.095s]
Writing 'userdata' OKAY [ 0.063s]
Rebooting OKAY [ 0.001s]
Finished. Total time: 122.672s
Press any key to exit...