Database Info

Unable to update to 8.1 in anyway

Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!

Did you update your fastboot tools? That is needed for 8.1

TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...

If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.

Thanks, I'll try and report back

roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.

cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...

nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...

cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...

nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.

Currently, I'm on 8.0, build number OPR3.170623.013

cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs

Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me

Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
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 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
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 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
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 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs

cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues

cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.

i soft bricked my pixel 2.. can anyone help?

i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated

xsanikax said:
i unlocked the bootloader used twrp to install magisk and installed a custom kernel, all of that went fine, then i decided to try and flash twrp which also worked... reinstalled magisk and kernel etc and it was getting stuck at the google logo,
i then decided to try and uninstall twrp and now i do not get the google logo, it won't go past the bootloader screen, bootloader seems to be functional and is accepting fastboot requests, however, the recovery is not working no matter what option i choose it will always take me back to the bootloader, tried reflashing stock images to get it working again but im getting an error with the bootloader remote command flash error.
any help is appreciated
Click to expand...
Click to collapse
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.

Diesel_Jeremiah said:
Download the factory image for your current build.Unzip.
In flash-all, remove the -w so it doesn't wipe your device.
Ensure you have newest ADB &Fastboot.
While your device is in fastboot:
Code:
fastboot devices
Ensure you see your device serial number
Double click flash-all
That should reflash recovery so you can start over.
NOTE: You cannot flash TWRP, Kernel, and Magisk all at the same time. It causes issues.
Read this thread: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye). There are a lot of people that have had issues and have had help solving within it.
Click to expand...
Click to collapse
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s

xsanikax said:
thanks for the reply but i'm still getting the same error doing that.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 0.895s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.902s
Click to expand...
Click to collapse
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.

Diesel_Jeremiah said:
Are you on 8.0 or 8.1?
Which bootloader are you on?
If you are in the bootloader, does it have the error line at the bottom?
If you cycle your volume buttons and reboot bootloader, does the error go away?
If the error goes away, try flash-all again.
If not:
From the bootloader, try booting the TWRP image.
If that works, reinstall TWRP using the zip.
Ensure you are using the 3.2.1.0 IMG and ZIP. Mismatching will cause problems.
I think you might have caused an issue when you deleted the TWRP recovery without replacing the stock recovery.
This post here might help.
Replace the Magisk with current version.
Click to expand...
Click to collapse
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them

xsanikax said:
was running 8.1 before this happened. bootloader version says mw8998-002.0059.00
there is no error that i can see in the bootloader, looks the same as when it was all functional
trying to boot twrp gives me this error
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.689s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.696s
it seems most things that i try and do give me a remote error, i feel like the partitions might be jacked up but i have no idea how to fix them
Click to expand...
Click to collapse
You probably have already done it, but ensure you have the newest ADB, that's what screwed me up.

I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html

iamnotreallyhere said:
I had the same problem turns out I wasn't using the latest platform tools.
I couldn't do anything. Would boot strait to bootloader. I couldn't even power down and plug I to charge. It would take me to bootloader with an error. I managed to screw up even more by flashing the wrong image using old tools. Then I lost all options except bootloader ( no recovery or download mode).
I feel as long as you have an unlocked bootloader and you are able to use fastboot you shouldn't worry. I'm only saying this because I was scared as hell haha.
I did notice it would try to boot when switching boot slots. But I screwed that up too by trying to flash with old tools. In the end all I needed was latest Platform tools:
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
thanks a lot dude this is what im getting at the minute
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.818s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.825s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.270s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.815s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.009s
Press any key to exit...
however i have found a problem when i tried just reflashing the recovery by itself
C:\Unified_Android_Toolkit\recovery\GooglePixel2>fastboot flash recovery recovery-twrp-3.2.1.0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
OKAY [ 0.689s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.691s
seems my partitions are all jacked up, is there a way to sort that out?
oh as a side note my problems are all the same as yours i can only access the bootloader and adb will not recognize my device but fastboot will

this is what happens if i try to flash the version with the same bootloader as the one that it says is on the device
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.821s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.271s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.544s]
finished. total time: 1.816s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
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: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA7AK1A08325
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (32768 KB)...
OKAY [ 0.690s]
writing 'boot'...
OKAY [ 0.300s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.668s]
writing 'system'...
OKAY [ 4.745s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.632s]
writing 'system'...
OKAY [ 4.755s]
sending sparse 'system' (524284 KB)...
OKAY [ 11.597s]
writing 'system'...
OKAY [ 4.732s]
sending sparse 'system' (322348 KB)...
OKAY [ 7.126s]
writing 'system'...
OKAY [ 2.915s]
sending 'vendor' (346992 KB)...
OKAY [ 7.342s]
writing 'vendor'...
OKAY [ 3.169s]
erasing 'userdata'...
OKAY [ 0.736s]
sending 'userdata' (140906 KB)...
OKAY [ 2.954s]
writing 'userdata'...
OKAY [ 1.502s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 75.881s
Press any key to exit...

It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
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.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 (347 MB) to disk... took 1.721s
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 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
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
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip

iamnotreallyhere said:
It still sounds like you are not using the latest tools. Are you installing the platform tools or are you using the extracted zip?
the script is going to use whatever is installed on your system.
The first thing I did was download: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I used this image Android 8.1 stock: https://dl.google.com/dl/android/aosp/taimen-opm1.171019.011-factory-2df1c1cb.zip
I extracted platform tools to my desktop. I opened the file location and did a Shift > Right click - within the folder containing the tools and opened CMD or Powershell( or you can just CD to the directory).
I copied all the commands from the script and ran them one at a time making sure I was using the tools from the zip file and not my system.
and just went down the line.
Like this:
PS C:\Users\myusername\Desktop\platform-tools> C:\Users\myusername\Desktop\platform-tools\fastboot.exe --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.017s
PS C:\Users\myusername\Desktop\platform-tools> cd C:\Users\myusername\Downloads\nv3
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash bootloader bootloader-walleye-mw8998-002.0066.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00048000
(bootloader) Updating: cmnlib @0008C000 sz=00037000
(bootloader) Updating: devcfg @000C3000 sz=0000F000
(bootloader) Updating: hyp @000D2000 sz=00040000
(bootloader) Updating: keymaster @00112000 sz=00046000
(bootloader) Updating: lockbooter @00158000 sz=00016000
(bootloader) Updating: pmic @0016E000 sz=0000D000
(bootloader) Updating: rpm @0017B000 sz=0003A000
(bootloader) Updating: tz @001B5000 sz=001DB000
(bootloader) Updating: xbl @00390000 sz=003A2000
(bootloader) Updating: apdp @00732000 sz=00004000
(bootloader) Updating: msadp @00736000 sz=00004000
(bootloader) Updating: hosd @0073A000 sz=01E1E000
(bootloader) Updating: abl @02558000 sz=00065000
OKAY [ 0.894s]
finished. total time: 1.724s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe flash radio radio-walleye-g8998-00164-1710262031.img
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.293s]
writing 'radio_b'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.552s]
finished. total time: 1.848s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\Users\myusername\Downloads\nv3> C:\Users\myusername\Desktop\platform-tools\fastboot.exe -w update image-walleye-opm1.171019.011.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.134s
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.020s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1920 MB) to disk... took 8.309s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 2.987s
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 (347 MB) to disk... took 1.721s
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 13933563 4k blocks and 3489792 inodes
Filesystem UUID: 1f46fc9a-edc7-11e7-aa2c-2daa660ba492
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
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT696969696969
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot_b' (32768 KB)...
OKAY [ 0.699s]
writing 'boot_b'...
OKAY [ 0.001s]
sending 'dtbo_b' (8192 KB)...
OKAY [ 0.477s]
writing 'dtbo_b'...
OKAY [ 0.001s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 11.667s]
writing 'system_b' 1/4...
OKAY [ 0.001s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.907s]
writing 'system_b' 2/4...
OKAY [ 0.001s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.876s]
writing 'system_b' 3/4...
OKAY [ 0.002s]
sending sparse 'system_b' 4/4 (393508 KB)...
OKAY [ 11.018s]
writing 'system_b' 4/4...
OKAY [ 0.001s]
erasing 'system_a'...
OKAY [ 2.084s]
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 11.561s]
writing 'system_a' 1/2...
OKAY [ 0.001s]
sending sparse 'system_a' 2/2 (57592 KB)...
OKAY [ 3.758s]
writing 'system_a' 2/2...
OKAY [ 0.001s]
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.288s]
writing 'vbmeta_b'...
OKAY [ 0.001s]
erasing 'vendor_b'...
OKAY [ 0.116s]
sending 'vendor_b' (355428 KB)...
OKAY [ 7.594s]
writing 'vendor_b'...
OKAY [ 0.001s]
Setting current slot to 'b'...
OKAY [ 1.722s]
erasing 'userdata'...
OKAY [ 0.759s]
sending 'userdata' (4669 KB)...
OKAY [ 0.108s]
writing 'userdata'...
OKAY [ 0.001s]
rebooting...
finished. total time: 80.060s
fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot-bootloader
fastboot -w update image-walleye-opm2.171019.012.zip
Click to expand...
Click to collapse
im doing exactly what i'm being told to but i'm still getting the same remote command flash error and the boot slot is set to a it won't let me change it to b

okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input

Nice! Now that I think of it I did try flashing Oreo 8.0 before I tried flashing 8.1. 8.0 didn't work by itself tho. So then I flashed 8.1. Maybe that's the trick to fix the partitions.

Thanks a lot
xsanikax said:
okay i have an update i'm all up and running again everything is fine, turns out i had to download the older version of oreo 8.0.0 from november the latest november update, then i had to download a slightly older version of fastboot and that seems to have fixed it just ran the flash-all batch file thanks everyone for their input
Click to expand...
Click to collapse
Thank you for the idea of using an older version of fastboot. I somehow screwed up my Pixel 2 and loaded bootloader 59 on it and couldn't update it back to 66. I had the right image but was still using the newest version of fastboot. Ended up with 26.0.2 which was the first version with Pixel 2 support. It can be found here: https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
Thanks again! :good:

Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...

jzablocki15 said:
Unlocked my pixel 2 and tried to root through magisk and kinda screwed it up. Tried flashing older Oreo 8.0 and 8.1 as you guys tried before but now I cant get past the fastboot screen. Whenever I try to load the earlier 8.0 it tells me it requires 8.1 to upgrade. any ideas would help
target reported max download size of 536870912 bytes
sending 'bootloader' (38644 KB)...
OKAY [ 0.829s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.848s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.296s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.543s]
finished. total time: 1.845s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
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: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: HT7AR1A01164
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0066.00'.
finished. total time: 0.070s
Press any key to exit...
Click to expand...
Click to collapse
My dude, you would not believe the hell I went through to figure this out. So it started with me getting the Verizon Pixel 2's bootloader unlocked. I downloaded TWRP onto it, rooted it, and then downloaded a ZIP that would add various modifications to my version of android. Well, I downloaded it, flashed it , and of course it didn't work as intended. Tried finding a way to undo what I'd done (absolutely imbecilic me, I didn't back up my phone WHEN THERE WAS NO SYSTEM IMAGE FOR A VERIZON PHONE YET). I figured the Google images would work fine, but they put you through hell and highwater before they do. I attempted to revert to the current stock image. It screwed my whole system up. Couldn't boot into android, couldn't boot into ANY recovery, etc. It was essentially bricked. I went through countless different errors and threads and forums and files, until I found this one right here. Tried reverting to the old version of Oreo with old ADB and fastboot. Progress, no more error popping up. Then I tried booting up and it stayed in fastboot. Tried then updating to the latest version available from Google as you had and got the exact same line of code. With the OLD ADB AND FASTBOOT and with a file I had downloaded and tinkered with earlier and with the LATEST IMAGE FROM GOOGLE (after your step), I tried it, came up with several "faileds" and other errors, but after the script was done, I rebooted and it got to the boot animation (as it had done before) and FINALLY brought my phone to the setup wizard.
The file I used was this one: https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Recap:
Download old ADB and Fastboot
Download the latest Android 8.0 Oreo Stock Image
Flash all bat
Download latest Android 8.1 Oreo Stock Image
From there, put the downloaded script in with the image file of the latest available Android 8.1 Oreo Stock Image and run the script.
Should show errors
Reboot once it's finished
Should be fine.
Keep in mind, this was a Verizon Pixel 2 and it worked fine for me. Couldn't guarantee it'd work for you, and there may have even been precursor steps before this post that I took and didn't keep track of that might have contributed to an extremely lucky brick save.
Long story short folks, if you're on an unlocked bootloader Verizon, don't do anything you can't live with for a while until we've got a proper backdoor developed for us.

Read my message right above your original post. Get the image for oreo 8.0 (nov) and use the fastboot version fron the site I linked to. Should have the 59 bootloader. After it boots, just do the OTA update twice. Check the build number and then get that image from Google to root the boot.img file. All good.

Yupp, just used the tool and saved a couple hundred bucks and a pair of underwear. Really is phone saver. And I'm for sure going to wait until a less risky root is available. I was able to flash the tool with factory image 66 version bootloader, just make sure to have tool in the same folder as the unzipped bootloader and files.

I haven't posted in at least 2 years. Wanted to thank everyone in this thread for the detailed troubleshooting. I locked my bootloader without doing the prep work and this saved me from a fiasco the week before my vacation.

Unable to flash stock Google Pixel 3 - "Sending sparse 'vendor_a' 1/2 (262140 KB)

Unable to flash stock Google Pixel 3 - "Sending sparse 'vendor_a' 1/2 (262140 KB)
Hey
I am trying to flash the factory image for Google Pixel 3.
"blueline-qp1a.a190105.004-factory-49adfd52"
I had some issues with fastboot at first. But after updating adb/fastboot I got passed them
Android Debug Bridge version 1.0.40
Version 4986621
Installed as /usr/lib/android-sdk/platform-tools/adb
All seems to be working fine: This is my cmd:
./flash-all.sh
Sending 'bootloader_a' (8489 KB) OKAY [ 0.350s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
(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.694s]
Finished. Total time: 1.175s
rebooting into bootloader OKAY [ 0.053s]
Finished. Total time: 0.103s
Sending 'radio_a' (71148 KB) OKAY [ 2.490s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.500s]
Finished. Total time: 3.129s
rebooting into bootloader OKAY [ 0.046s]
Finished. Total time: 0.096s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 898X06K3Z
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.060s]
Checking version-baseband OKAY [ 0.060s]
extracting boot.img (64 MB) to disk... took 0.246s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (195 MB) to disk... took 0.602s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2155 MB) to disk... took 8.607s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.904s
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 1.800s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_a' (65536 KB) OKAY [ 2.320s]
Writing 'boot_a' OKAY [ 0.375s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.405s]
Writing 'dtbo_a' OKAY [ 0.102s]
Sending 'product_a' (200036 KB) OKAY [ 6.748s]
Writing 'product_a' OKAY [ 1.170s]
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 8.970s]
Writing sparse 'system_a' 1/9 OKAY [ 0.063s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 8.337s]
Writing sparse 'system_a' 2/9 OKAY [ 0.366s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 7.684s]
Writing sparse 'system_a' 3/9 OKAY [ 0.366s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 8.484s]
Writing sparse 'system_a' 4/9 OKAY [ 0.367s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 8.523s]
Writing sparse 'system_a' 5/9 OKAY [ 0.366s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 8.784s]
Writing sparse 'system_a' 6/9 OKAY [ 0.366s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 8.334s]
Writing sparse 'system_a' 7/9 OKAY [ 0.366s]
Sending sparse 'system_a' 8/9 (258816 KB) OKAY [ 8.104s]
Writing sparse 'system_a' 8/9 OKAY [ 0.366s]
Sending sparse 'system_a' 9/9 (113572 KB) OKAY [ 3.994s]
Writing sparse 'system_a' 9/9 OKAY [ 0.960s]
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 9.330s]
Writing sparse 'system_b' 1/2 OKAY [ 0.366s]
Sending sparse 'system_b' 2/2 (166540 KB) OKAY [ 5.884s]
Writing sparse 'system_b' 2/2 OKAY [ 1.290s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_a' OKAY [ 0.063s]
Sending sparse 'vendor_a' 1/2 (262140 KB)
And then it just stops. Had it running for 1600s+ the first time. Tried again and now it has been staying there for beyond that time.
Thanks

osunde said:
Hey
I am trying to flash the factory image for Google Pixel 3.
"blueline-qp1a.a190105.004-factory-49adfd52"
I had some issues with fastboot at first. But after updating adb/fastboot I got passed them
Android Debug Bridge version 1.0.40
Version 4986621
Installed as /usr/lib/android-sdk/platform-tools/adb
All seems to be working fine: This is my cmd:
./flash-all.sh
Sending 'bootloader_a' (8489 KB) OKAY [ 0.350s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
(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.694s]
Finished. Total time: 1.175s
rebooting into bootloader OKAY [ 0.053s]
Finished. Total time: 0.103s
Sending 'radio_a' (71148 KB) OKAY [ 2.490s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00023-180917-B-5014671
(bootloader) Flashing partition modem_a
OKAY [ 0.500s]
Finished. Total time: 3.129s
rebooting into bootloader OKAY [ 0.046s]
Finished. Total time: 0.096s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 898X06K3Z
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader OKAY [ 0.060s]
Checking version-baseband OKAY [ 0.060s]
extracting boot.img (64 MB) to disk... took 0.246s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (195 MB) to disk... took 0.602s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2155 MB) to disk... took 8.607s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 1.904s
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 1.800s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_a' (65536 KB) OKAY [ 2.320s]
Writing 'boot_a' OKAY [ 0.375s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.405s]
Writing 'dtbo_a' OKAY [ 0.102s]
Sending 'product_a' (200036 KB) OKAY [ 6.748s]
Writing 'product_a' OKAY [ 1.170s]
Sending sparse 'system_a' 1/9 (262140 KB) OKAY [ 8.970s]
Writing sparse 'system_a' 1/9 OKAY [ 0.063s]
Sending sparse 'system_a' 2/9 (262140 KB) OKAY [ 8.337s]
Writing sparse 'system_a' 2/9 OKAY [ 0.366s]
Sending sparse 'system_a' 3/9 (262140 KB) OKAY [ 7.684s]
Writing sparse 'system_a' 3/9 OKAY [ 0.366s]
Sending sparse 'system_a' 4/9 (262140 KB) OKAY [ 8.484s]
Writing sparse 'system_a' 4/9 OKAY [ 0.367s]
Sending sparse 'system_a' 5/9 (262140 KB) OKAY [ 8.523s]
Writing sparse 'system_a' 5/9 OKAY [ 0.366s]
Sending sparse 'system_a' 6/9 (262140 KB) OKAY [ 8.784s]
Writing sparse 'system_a' 6/9 OKAY [ 0.366s]
Sending sparse 'system_a' 7/9 (262140 KB) OKAY [ 8.334s]
Writing sparse 'system_a' 7/9 OKAY [ 0.366s]
Sending sparse 'system_a' 8/9 (258816 KB) OKAY [ 8.104s]
Writing sparse 'system_a' 8/9 OKAY [ 0.366s]
Sending sparse 'system_a' 9/9 (113572 KB) OKAY [ 3.994s]
Writing sparse 'system_a' 9/9 OKAY [ 0.960s]
Sending sparse 'system_b' 1/2 (262140 KB) OKAY [ 9.330s]
Writing sparse 'system_b' 1/2 OKAY [ 0.366s]
Sending sparse 'system_b' 2/2 (166540 KB) OKAY [ 5.884s]
Writing sparse 'system_b' 2/2 OKAY [ 1.290s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_a' OKAY [ 0.063s]
Sending sparse 'vendor_a' 1/2 (262140 KB)
And then it just stops. Had it running for 1600s+ the first time. Tried again and now it has been staying there for beyond that time.
Thanks
Click to expand...
Click to collapse
I would start by trying a different USB cable and ports. Use an A/B to C cable if you aren't already. Also do a fastboot --version just to make sure you have the latest fastboot. It should be 28.0.1.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I would start by trying a different USB cable and ports. Use an A/B to C cable if you aren't already. Also do a fastboot --version just to make sure you have the latest fastboot. It should be 28.0.1.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks. I used a USB Type C - USB Type C cable
Had the 28.0.1 Fastboot version. But switching the cable did the trick. Thanks!

Pixel bricked, need help

My Pixel( G-2PW4100) doesn't boot up. I tried some steps to flash, unbrick it, but no success so far. Can someone help?
I put it to fastboot, and downloaded the latest factory image, run flash-all command (as below).
The device still doesn't power up, showing "Your device software cannot be checked for corruption......"
then I ran "fastboot flashing lock" to relock the bootloader, it still failed to power up, showing "no command"
I tried: "adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip". It still doesn't power up. What should I do??? Thanks in advance.
adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip
serving: 'sailfish-ota-qp1a.191005.007.a3-394b5899.zip' (~94%) adb: failed to read command: No error
sailfish-qp1a.191005.007.a3>flash-all.bat
Sending 'bootloader_a' (32480 KB) OKAY [ 0.840s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.996s]
Finished. Total time: 3.037s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.014s
Sending 'radio_a' (57156 KB) OKAY [ 1.492s]
Writing 'radio_a' OKAY [ 0.448s]
Finished. Total time: 2.120s
Rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.044s
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: xxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.048s]
Checking 'version-bootloader' OKAY [ 0.048s]
Checking 'version-baseband' OKAY [ 0.048s]
Setting current slot to 'a' OKAY [ 0.069s]
extracting boot.img (30 MB) to disk... took 0.177s
archive does not contain 'boot.sig'
Sending 'boot_a' (30793 KB) OKAY [ 0.784s]
Writing 'boot_a' OKAY [ 0.263s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.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 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1989 MB) to disk... took 9.375s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 13.014s]
Writing 'system_a' OKAY [ 3.399s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 13.087s]
Writing 'system_a' OKAY [ 3.430s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 13.161s]
Writing 'system_a' OKAY [ 3.409s]
Sending sparse 'system_a' 4/4 (464416 KB) OKAY [ 11.451s]
Writing 'system_a' OKAY [ 3.095s]
archive does not contain 'system_ext.img'
extracting system_other.img (293 MB) to disk... took 1.669s
archive does not contain 'system.sig'
Sending 'system_b' (300296 KB) OKAY [ 7.362s]
Writing 'system_b' OKAY [ 2.009s]
extracting vendor.img (253 MB) to disk... took 1.414s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (259272 KB) OKAY [ 6.421s]
Writing 'vendor_a' OKAY [ 1.743s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.652s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: ffe940a8-945f-11ec-8982-07edb72ed496
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.057s]
Writing 'userdata' OKAY [ 0.046s]
Rebooting OKAY [ 0.039s]
Finished. Total time: 100.707s
Press any key to exit...

Hello, have you solved this problem?

No.

eso esta gratis en google

raikigsm said:
eso esta gratis en google
Click to expand...
Click to collapse
Any pointers? I searched a lot, but cannot find a solution.
After relocking bootloader and reboot, it shows a google screen, and then "No command"

Is it because bootloader is locked? I did try to use fastboot command to unlock. It said "success".

Question Android 14 Beta 1 factory image flash fails with error

# Phone Config
Pixel 7 Pro, running Android 14 DP2, Magisk 26.1.
I downloaded the 14 Beta 1 factory image today from the official site, and verified that the checksum matches.
Extracted the zip into my existing platform-tools folder (on Windows), removed the -w flag from the flash-all.bat and ran it. (After connecting the phone in bootloader mode to the computer via USB cable.)
Everything runs fine, until the very end, where it failed to flash the vendor img. Here's the full log -
Code:
Sending 'bootloader_a' (13927 KB) OKAY [ 0.109s]
Writing 'bootloader_a' (bootloader) Flashing pack version cloudripper-14.0-9701414
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.262s]
Finished. Total time: 0.380s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.003s
< waiting for any device >
Sending 'radio_a' (111960 KB) OKAY [ 0.917s]
Writing 'radio_a' (bootloader) Flashing pack version g5300q-230217-230224-M-9650069
(bootloader) Flashing partition modem_a
OKAY [ 0.571s]
Finished. Total time: 1.496s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.196s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.535s]
Writing 'boot_a' OKAY [ 0.231s]
extracting init_boot.img (8 MB) to disk... took 0.022s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.068s]
Writing 'init_boot_a' OKAY [ 0.015s]
extracting dtbo.img (16 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.139s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' OKAY [ 0.003s]
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' (12 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.186s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.128s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.554s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.080s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (5 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 1.039s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.002s]
Resizing 'system_dlkm_a' OKAY [ 0.002s]
Resizing 'system_ext_a' OKAY [ 0.003s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.002s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2925 MB) to disk... took 11.503s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.008s]
Sending sparse 'product_a' 1/12 (262112 KB) OKAY [ 0.996s]
Writing 'product_a' OKAY [ 0.753s]
Sending sparse 'product_a' 2/12 (262124 KB) OKAY [ 0.982s]
Writing 'product_a' OKAY [ 0.944s]
Sending sparse 'product_a' 3/12 (262128 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 1.011s]
Sending sparse 'product_a' 4/12 (262120 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.936s]
Sending sparse 'product_a' 5/12 (262124 KB) OKAY [ 0.979s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 6/12 (262128 KB) OKAY [ 0.970s]
Writing 'product_a' OKAY [ 0.933s]
Sending sparse 'product_a' 7/12 (262124 KB) OKAY [ 0.984s]
Writing 'product_a' OKAY [ 1.052s]
Sending sparse 'product_a' 8/12 (262124 KB) OKAY [ 0.966s]
Writing 'product_a' OKAY [ 0.999s]
Sending sparse 'product_a' 9/12 (262128 KB) OKAY [ 0.971s]
Writing 'product_a' OKAY [ 1.063s]
Sending sparse 'product_a' 10/12 (262124 KB) OKAY [ 0.977s]
Writing 'product_a' OKAY [ 0.968s]
Sending sparse 'product_a' 11/12 (262092 KB) OKAY [ 0.968s]
Writing 'product_a' OKAY [ 0.819s]
Sending sparse 'product_a' 12/12 (102712 KB) OKAY [ 0.394s]
Writing 'product_a' OKAY [ 0.161s]
extracting system.img (899 MB) to disk... took 3.753s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.042s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 1.028s]
Writing 'system_a' OKAY [ 0.526s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 0.994s]
Writing 'system_a' OKAY [ 0.965s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 0.972s]
Writing 'system_a' OKAY [ 1.174s]
Sending sparse 'system_a' 4/4 (131716 KB) OKAY [ 0.496s]
Writing 'system_a' OKAY [ 0.556s]
extracting system_dlkm.img (0 MB) to disk... took 0.001s
archive does not contain 'system_dlkm.sig'
Resizing 'system_dlkm_a' OKAY [ 0.006s]
Sending 'system_dlkm_a' (340 KB) OKAY [ 0.003s]
Writing 'system_dlkm_a' OKAY [ 0.045s]
extracting system_ext.img (256 MB) to disk... took 1.042s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.008s]
Sending sparse 'system_ext_a' 1/1 (262068 KB) OKAY [ 1.016s]
Writing 'system_ext_a' OKAY [ 0.939s]
extracting system_other.img (16 MB) to disk... took 0.086s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.011s]
Sending 'system_b' (17264 KB) OKAY [ 0.064s]
Writing 'system_b' OKAY [ 0.093s]
extracting vendor.img (699 MB) to disk... took 2.624s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.007s]
Sending sparse 'vendor_a' 1/3 (262120 KB) OKAY [ 0.996s]
Writing 'vendor_a' OKAY [ 1.194s]
Sending sparse 'vendor_a' 2/3 (262116 KB) OKAY [ 0.992s]
Writing 'vendor_a' OKAY [ 0.504s]
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Press any key to exit...
I noticed that the platform-tools was an old version (33.0.3). So, I downloaded the latest 34.0.0 RC2 from the Android developer site and reran the falsh-all.bat. This time, the flash fails with a different error (I'm not pasting the bootloader / radio part of the log here, as they were fine.) -
Code:
--------------------------------------------
Bootloader Version...: cloudripper-14.0-9701414
Baseband Version.....: g5300q-230217-230224-B-9650069
Serial Number........: REDACTING
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.186s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.529s]
Writing 'boot_a' OKAY [ 0.075s]
extracting init_boot.img (8 MB) to disk... took 0.020s
archive does not contain 'init_boot.sig'
Sending 'init_boot_a' (8192 KB) OKAY [ 0.069s]
Writing 'init_boot_a' OKAY [ 0.017s]
extracting dtbo.img (16 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.134s]
Writing 'dtbo_a' OKAY [ 0.019s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.004s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.009s]
Writing 'pvmfw_a' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.173s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 0.542s]
Writing 'vendor_boot_a' OKAY [ 0.075s]
extracting vendor_kernel_boot.img (64 MB) to disk... took 0.122s
archive does not contain 'vendor_kernel_boot.sig'
Sending 'vendor_kernel_boot_a' (65536 KB) OKAY [ 0.553s]
Writing 'vendor_kernel_boot_a' OKAY [ 0.074s]
extracting super_empty.img (0 MB) to disk... took 0.001s
extracting product.img (2925 MB) to disk... took 10.295s
[liblp] Partition product_a will resize from 0 bytes to 3067695104 bytes
extracting system.img (899 MB) to disk... took 3.202s
[liblp] Partition system_a will resize from 0 bytes to 943325184 bytes
extracting system_dlkm.img (0 MB) to disk... took 0.001s
[liblp] Partition system_dlkm_a will resize from 0 bytes to 348160 bytes
extracting system_ext.img (256 MB) to disk... took 0.948s
[liblp] Partition system_ext_a will resize from 0 bytes to 269307904 bytes
extracting system_other.img (16 MB) to disk... took 0.074s
[liblp] Partition system_b will resize from 0 bytes to 17678336 bytes
extracting vendor.img (699 MB) to disk... took 7.555s
[liblp] Partition vendor_a will resize from 0 bytes to 733212672 bytes
extracting vendor_dlkm.img (42 MB) to disk... took 0.115s
[liblp] Partition vendor_dlkm_a will resize from 0 bytes to 44281856 bytes
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Press any key to exit...
Platform tools 34.0.0 RC2 throws this same error when trying to flash 14 DP2 too. Platform tools 33.0.3 flashes 14 DP2 fine.
Anyone else has faced this issue and knows a fix?

People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.

synesthete said:
People have been having issues with Platform Tools 34 since its release. The only fix I know is to uninstall 34 and revert to installing 33.03. I haven't had any problems flashing the latest stable build on 33.03 and it looks like people have had success with flashing the latest Android 14 beta with it as well.
Click to expand...
Click to collapse
I get the platform tools from here. The download is just a portable zip, not an installer needing any uninstall / install. I deleted the 34 RC2 download and went back to my previous 33.0.3 download. But through that too, I'm getting this error for 14B1 -
Code:
Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))
14DP2 flashes fine with 33.0.3.

I got this also as did others in the Android 14 thread. I don't know what Google are on. First the platform tools bug which still isn't fixed and now this. I get and fully expect to run into issues within the OS itself, but not even being able to flash the build?
I'll laugh/cry if this also affects the non-pro and even the Pixel 6, but even without that just a single device failing flash seems like a complete amature mistake to have made.
We are all just going to have to avoid the build and hope someone at Google cares enough to fix it, or wee just wait until beta 2 next month I guess, and rely on having to use using OTA updates until then.

Dave_247 said:
I got this also as did others in the Android 14 thread.
Click to expand...
Click to collapse
Can you please give me a link to that thread?

Just use android flash tool to install this a14 beta
Working properly

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?

bagarwa said:
I haven't used that before. Does that provide an option to flash without wipe or does that mandatorily wipe the device while flashing?
Click to expand...
Click to collapse
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...

cultofluna said:
Yes you can choose any option you want ..
With or without wipe/ or disable verity/ verification
Click to expand...
Click to collapse
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.

simplepinoi177 said:
I only used Android Flash Tool once, but I don't believe it could disable verity & verification...
Did you by chance mean badabing2003's PixelFlasher? I know for sure that that program does this, and it most likely can flash Android 14 as well...
Click to expand...
Click to collapse
You can disable verity/ verification with android flash tool
And i don't mean Pixel flasher

bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
Interesting, I always get 6 seconds using my C-to-C cable too.

bagarwa said:
Can you please give me a link to that thread?
Click to expand...
Click to collapse
Here's the thread. It was started folowingf the devloper preview versions of 14 but has not sahifted to the beta versions.
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com

cultofluna said:
Just use android flash tool to install this a14 beta
Working properly
Click to expand...
Click to collapse
bagarwa said:
I tried the flashing tool now, but that too kept failing, this time at flashing product 11/12.
View attachment 5887309
But I finally managed to finish the flash on my local. I used a different USB C to C cable (previously I was using A to C) on a different port of the laptop. The file transfer from PC to phone (the "Sending sparse..." parts) were much slower this time (~6 seconds for each part, compared to less than 1 second before). But the flash finally successfully finished. And now I've booted into 14B1.
Click to expand...
Click to collapse
I was getting the same error so I gave up and manually flashed the developer preview 2 then did a OTA update to get to Beta 1. There has to be something wrong with the build itself to be having this many issues for so many people.