Pixel3 Blueline Slot A is dead

[The Lepricon]

It seems my slot A is dead. No matter what I try I cannot boot to it.

I've tried flash.android.com to flash back to stock, even tried going back to Pie, and back to Q, but still Slot A is dead.
With stock Pie I flashed TWRP and tried flashing custom ROM to both slots, but slot A always fails.
Tried sideloading factory OTA and LineageOS, but it keeps failing.
Tried ./flash-all.sh using a few different ROMs, stock and CalyxOS, but it always fails with the following error.

target reported max download size of 268435456 bytes
sending 'bootloader_a' (8537 KB)...
OKAY [ 0.340s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.2-6374987
(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.279s]
finished. total time: 0.619s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
target reported max download size of 268435456 bytes
sending 'radio_a' (71436 KB)...
OKAY [ 2.050s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00107-200409-B-6382632
(bootloader) Flashing partition modem_a
OKAY [ 0.418s]
finished. total time: 2.467s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (787 MB)...
archive does not contain 'system.sig'
extracting system_other.img (152 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (440 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 96KX220PE
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s

 

[The Lepricon]

When slot A is active and I run fastboot flash boot boot.img for installing LineageOS, it will not boot to recovery, but if I set slot B active and do that then recovery works fine.

 

[sliding_billy]

Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?

 

[The Lepricon]

Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?

Can you explain how to do that?

What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh

Is there a way to run that file from somewhere other than where it is located?

 

[sliding_billy]

Can you explain how to do that?

What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh

Is there a way to run that file from somewhere other than where it is located?

Extract the .zip directly into your platform tools folder and then with that folder open right click and open terminal from the folder. That is easier than changing your terminal path and should result in the ./ running directly from that place. Again, be sure you are running the current platform tools.

 

[Xeust]

Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?

 

[sliding_billy]

Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?

Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.

 

[Xeust]

Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.

I see. Thanks for clarifying that.

 

[The Lepricon]

I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.

@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.

 

[sliding_billy]

I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.

@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.

One other thing... Have you tried a factory reset from recovery?

 

[The Lepricon]

One other thing... Have you tried a factory reset from recovery?

I believe I have. I'll try that tonight

 

[The Lepricon]

Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot

So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.

Does anyone know why I am getting the error when running flash-all.sh?

 

[sliding_billy]

Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot

So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.

Does anyone know why I am getting the error when running flash-all.sh?

I still haven't seen that you are running the current planform tools, so that is my first suggestion. My second one is to sideload the OTA twice (including full boot after of course) so that it will install on both slots and swap. I suspect that you will then have it truly back to normal and can then do a flash-all including the -w to completely wipe.

 

[The Lepricon]

I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.

Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.

Thank you for all your help, sliding_billy

 

[sliding_billy]

I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.

Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.

Thank you for all your help, sliding_billy

Great news, and you are quite welcome.