Develop Bugs

Updated to 8.1 without disabling Substratum overlays... device now unusable

So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!

Ran into almost the same thing last night (not using flashfire, but with the factory flash-all.bat). Forgot to clear my theme and got the system UI error with everything borked. Even had the invalid password in twrp.
I hate to say it, but I had to just flash the factory image with a wipe and start everything over. Lost all my pics and music from the few days I had the phone. I have now learned how not to update in the future.

IrocD said:
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Click to expand...
Click to collapse
What a mess hahah! It sounds like your password file got corrupt; doing all that dirty flashing is messy. If I were you I would connect the phone to a computer and get off what data you can (most stuff is cloud now days anyway). And flash a 8.1 stock factory image using fastboot on the bootloader. You can never go wrong with flash a stock factory image. Yes you loose your data, but you get a working phone haha. If your really worried about data see if you can get MTP to work and transfer it off.

Dumbass me
Yep, that was me yesterday. Genius me sideloaded the 8.1 OTA without disabling my Substratum overlays and so I was met with the "System UI Tuner has stopped" message. Then an automatic reboot to the bootloader asking me to either "Try again" or "Factory reset phone". Guess what I had to do to get my phone working again? Had to factory reset that sh*t.
Oh well, at least I made sure to unlock my bootloader this time around before setting up my phone.
But to be fair, would've been f*cked either way even if I had waited for the OTA because it's essentially the same thing as the zip file anyways. Lesson learned: disable Substratum when you update your sh*t.

Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it

Strange. I didn't disable my Themes and I had no issues at all sideloading.

fantasy2c said:
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Click to expand...
Click to collapse
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.

I only update once a month when a new patch comes out.
I set my apps to not auto update
After a new patch comes out in the first week of the month I
-disable the overlays and remove them
-update swift black and compile new overlays
-update all my apps
-adb to recovery and flash ota
-apply new overlays
- reboot and good to go

I have done it before to you can just boot TWRP as long as you have that rescues zip on your flash drive you can do it that way too

rajlulla said:
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
Click to expand...
Click to collapse
Thought I was screwed, Thank you so much for this post.

Try formatting your internal memory using TWRP. It should be "formatting", no other type of wipe will be sufficient. Then flash your favourite ROM and enjoy!

Really need help, google flash gone bad

At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.

See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698

I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.

JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.

remove the -w from the update line in flash-all.

I have got the same problem since yesterday and search for a solution.

ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631

new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.

Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...

I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.

Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...

I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!

Android Recovery - Cannot load Android system - Your data may be corrupt

Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks

Hyflex said:
Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks
Click to expand...
Click to collapse
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.

Badger50 said:
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.
Click to expand...
Click to collapse
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/

Hyflex said:
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/
Click to expand...
Click to collapse
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.

Badger50 said:
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.
Click to expand...
Click to collapse
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!

Hyflex said:
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!
Click to expand...
Click to collapse
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:

Badger50 said:
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:
Click to expand...
Click to collapse
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do
Code:
fastboot --set-active=a
and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.

Hyflex said:
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.
Click to expand...
Click to collapse
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.

Badger50 said:
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.
Click to expand...
Click to collapse
I tried to switch slots and it threw up:
Code:
> fastboot: error: Device does not support slots
My platform tools are from last month

Hyflex said:
I tried to switch slots and it threw up:
My platform tools are from last month
Click to expand...
Click to collapse
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.

Badger50 said:
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.
Click to expand...
Click to collapse
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.

Hyflex said:
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.
Click to expand...
Click to collapse
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.

Hyflex said:
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.
Click to expand...
Click to collapse
Well done my friend. Goes to show that persistence pays off! :good::good:

Another method I do when I run across issue in the past.
I would lock and unlock my bootloader a few times (of course start the devices after each lock and unlock), which erase everything, then my phone will let me flash Google factory imagine..

hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?

estemanito said:
hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?
Click to expand...
Click to collapse
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:

Badger50 said:
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:
Click to expand...
Click to collapse
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead droid then a "no command" message. The way i installed before is from fastboot with the .img file

estemanito said:
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead ath droid then a "no command" message. The way i installed before is from fastboot with the .img file
Click to expand...
Click to collapse
You have to fastboot the twrp.img file first using your pc.

Badger50 said:
You have to fastboot the twrp.img file first using your pc.
Click to expand...
Click to collapse
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...?

estemanito said:
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...,
Click to expand...
Click to collapse
Bingo! You got it :good::laugh:

Help with flash stock rom

Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?

z3dulik said:
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
Click to expand...
Click to collapse
Just nuke it with flash-all.bat May factory image. You can boot TWRP and flash the R OTA as well.

I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
When I turn it on i have an alert "your device is corrupt."

z3dulik said:
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
Click to expand...
Click to collapse
I would extract the factory image, fastboot erase user data then update bootloader, radio and vendor on both slots(reboot bootloader after each flash) then flash-all or fastboot update with the Taimen file that contains the vendor image
It's a bit longer of a process but it works.

Tried too, same thing. Looks like it's something related to recovery. Can't write to

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
Swap slots and flash to both
Sent from my Pixel 4 XL using Tapatalk

Managed to flash twrp on boot_a

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
I've got out of this before
Boot TWRP
Format data
Pop in an otg with stock OTA hit mount go back and hit mount then it'll appear as auto-1 in TWRP and flash the OTA
It works if you need to go back to previous month or Android version. Just make sure both slots are the same after you boot

OTG not recognised
/vendor error
also the factory images are missing from here? https://developers.google.com/android/images
I can see only OTA

fixed with factory android 10 april. thanks all for help

"Your device is corrupt. It can't be trusted and may not work properly." Pixel 2 XL

I'm about 4 hours of reading in on this matter, and I still don't have a proper answer. I've run through countless threads with similar titles, and found some helpful tidbits, but nothing the resolves or fully explains what is going on here.
I just made the jump from Android 9.0.0 (latest) rooted to Android 10.0.0 (latest.) Here were my steps:
Download the latest Platform Tools & unzip
Download the latest Android 10.0.0 Factory image for Pixel 2 XL & unzip into the platform tools folder
Download the latest USB drivers & install
Hook up my phone to the computer (Windows 10) and verify that ADB & Fastboot are working properly via command prompt
Execute the flash-all.bat (left the -w flag in so that it wiped my data) -- it appeared to be only flashing the one slot except for a couple mentions of the other slot's system towards the end of the commands
The phone booted just fine and I went through and installed TWRP and Magisk 23 and so on
Here's where I encountered the error:
As I was rebooting out of TWRP, I realized I'd never used the "Slot A" or "Slot B" buttons, so I picked one, and it started rebooting the phone. The normal screen with the yellow text about phone being unlocked came up, then switched to the white background with the 'G' as expected. The expected next step would've been the 'G' spinning into a circle for a second, and then going to the homescreen, but instead what happened was the screen went black, and then a screen that said "Your device is corrupt. It can't be trusted and may not work properly." showed. It looked similar to the one when the phone first boots with the yellow text about the bootloader, but this text was red. I attempted to use the power button to bypass it, and when I did, it switched the the normal yellow-text-about-bootloader screen, and then switched to the 'G' with the white background again, but there it stayed, just frozen.
I was still able to boot to bootloader by using the power + down button, and could then boot to the stock recovery, but that was it. After a bit of reading, I discovered the following command:
fastboot set_active a
or
fastboot set_active b
and also fastboot getvar all
The set_active command chooses which Slot is being used, and the getvar command shows all the fastboot variables, one of which shows the "current_slot." Once I set the other Slot to be the active one and rebooted, the phone booted normally. Buuut, now I'm concerned that someone is screwed up with my phone, and it's going to fail at some point when I don't have my computer handy, so I went back to work trying to resolve the error when I booted out of the one slot.
Here's what I've tried:
Run the flash-all.bat file in one slot, let the phone reboot, boot to bootloader, switch slots, reboot to bootloader, flash-all.bat in the other slot.
Same as above, but without the -w flag.
Manually flash the bootloader, radio and image zip on both slots
Install the TWRP while booted into the adb-loaded TWRP img (this seems to write to both slots based on the output)
Install and uninstall Magisk both via recovery and via the patched stock boot image.
After every single attempt, the one slot would work just fine, and the other slot would exhibit the behavior I mentioned. Depending on which Slot is flashed first, the Slot that fails to boot properly does change (ie. it's not always Slot A or Slot B that fails.)
Untested methods:
Screwing with dm-verity -- I saw one thread that gave a few fastboot commands to disable dm-verity, and a couple people reporting success with it. After searching around and doing a bit of reading on dm-verity, I still don't understand what it does, whether disabling it would have any negative repercussions, and whether disabling it would fix the issue legitimately, or just kinda mute it.
Using Deuce's bootloop recovery tool -- again, I don't really know what that thing is running, it hasn't been maintained in quite some time as far as I can tell, and there are several threads indicating that it runs a bunch of haphazard stuff that could cause more problems. Some reports indicated it worked for them, but I'm concerned about what else it might be doing that may negatively affect things down the road.
Re-locking the bootloader -- I saw this one mentioned several times, but I also saw several people warning that you could brick your phone if you do it wrong. I also saw one or two folks who seemed like they couldn't get back to being unlocked after re-locking. I don't want to screw with this option given those risks.
Can anyone give me any more tips on how to resolve this? I'm pretty sure that the Pixels are supposed to run equally well from both slots, so I'd really like to get the matter resolved so I don't have to worry about what would happen if my phone moved me over to the other Slot for some reason. Any insight and explanations are appreciated!

People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.

The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.

runekock said:
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
Click to expand...
Click to collapse
The problem presents with even the stock boot image though.

Strephon Alkhalikoi said:
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
Click to expand...
Click to collapse
Understood on the magisk / twrp thing, but regarding the factory image, that is exactly what I was going. The problem presents even after doing that. That's why it's so puzzling.
Edit: it's admittedly a very long post, but if you look at the section that's numbered, you'll see I'm grabbing the latest factory image for Android 10 and flashing it. Then in the section labeled "Here's What I've Tried" (aka my attempts to troubleshoot) the very first thing I did was flash the factory image (including the wipe) to both Slots and then trying to boot from one slot and then from the other.

Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.

Strephon Alkhalikoi said:
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Click to expand...
Click to collapse
Why would it be any different when I wipe with Android 10 or Android 11? I flashed the latest Android 10 factory image to the phone *with* the -w flag as mentioned in my "here's what I tried" section. I even went so far as to force the phone to Slot A with the "set_active" command, and then set_active Slot B and flashed the factory image (not the OTA) again. After doing that, the one slot will boot just fine while the other gives the error. If I change it up and flash Slot B first and then Slot A the same thing occurs, just in reverse (the slot that booted before throws the error while the slot that threw the error before now boots.)

My initial post explains why I recommended an Android 11 ROM (updated radio). Any of them will of course work, but that's beside the point. Try using ADB to format the partitions and see if that resolves the issue. Otherwise contact Google, as I can't think of anything else that would be blocking you.

I had this same issue and Flashing Android 11 on both partitions (without removing the -w command) resolved it.
I first booted into Recovery Menu and wiped both slots. Then downloaded the factory image (not ota) and flashed each slot separately wiping the device after each flash in recovery menu. it's the only way to fix this just like user @Strephon Alkhalikoi
If that doesn't resolve it then you have an issue that's more serious and will require a repair of some sort (not necessarily hardware).