Develop Bugs

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!!

Moto e4 (XT1768): Unlock Bootloader/root permission - corrupted /system partition

Hi,
This is less of a question and more of an experience. That being said, if anyone has any suggestions, I still do not have a correctly mounted /system partition (I think).
Background:
I am new to the world of custom ROM's and the community with which it resides. I did dabble in it a few years back with the original casio commando, but that was before I ever touched a linux machine or read a line of code. I decided to mess with my new Moto e4 (XT1768), mostly to remove bloatware and maybe flash a custom ROM, though I did like the factory.
Procedure:
I unlocked the bootloader and flashed a custom recovery (TWRP) through fast boot. Flashed Magisk and got superuser permissions. Everything seemed to go fine. I didn't notice it at first, so I'm not exactly sure which step caused it, but every time I would reboot the phone, it would boot to recovery.
I was able to boot into fastboot from TWRP. From there I could start the OS. So i ignored it. But upon trying to run system updates they would fail.
Problem:
NOW I decided this minor glitch was the result of a larger issue. Turns out, somewhere between flashing TWRP recovery and flashing Magisk, I inadvertently removed/corrupted my /system partition. I get a error on reboots "unable to mount partition." When I tried to flash a custom rom RR, it would raise errors about /system not existing. In the TWRP "mount" menu, "system is unchecked, even when I check it and reboot. When I reboot the bootloader from TWRP I would get a msg NO OS Installed. This last one is contradictory because I can still access the OS, could make calls, etc.
Troubleshooting:
I tried remounting the /system partion, though I don't think I did it correctly. I couldn't find much about fixing partitions, and do not feel like breaking my phone, since it still works. Unfortunately I did not take a backup of the factory installation (won't do that again). The only backup I had was after the bootloader was unlocked and Magisk was installed. Rolling it back to this image, I am able to flash RR custom rom and it works fine, though the original issue still exists. I tried a few attempts to remove Magisk from the backup image, but results in a boot loop when booting to the OS. When it went well, I was able to boot straight to the OS, without it automatically booting to recovery, but the boot loop prevented any advancement.
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Nich

I know of one instance which can cause rebooting to result in recovery mode and system mount issues, as well as a solution to resolve it. When installing firmware via fastboot, or any other files via fastboot (even unlocking the bootloader with fastboot), it is extremely important that your first command is this:
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Sometimes, a failure to initiate and close fastboot with the above command lines will result in exactly what you are describing. Of course, to fix the issue, you will need to flash a compatible stock firmware package with the opening and closing lines I've listed. I will check my sources and try to find a package for your model.
Update: I have found a factory firmware package for the xt1768, which I am downloading now. I'll get you a link as soon as I get it downloaded, then uploaded to my cloud host.

Amazon xt1768 Moto E4 stock firmware package -- Build No. NPQS26.69-64-8
https://drive.google.com/file/d/12hABSzvUpSZOYEUdX5ssCXYZmjA-Z10n/view?usp=drivesdk

nich42 said:
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Click to expand...
Click to collapse
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).

hitokage004 said:
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).
Click to expand...
Click to collapse
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear

nich42 said:
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,

nich42 said:
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,
Click to expand...
Click to collapse
Yes if you flash it with fastboot you do it one image at a time. You can also install RSD Lite on a Windows computer and it will do it all for you by selecting either the flashfile.xml or the service file. XML.

UPDATE:
Thanks for the assistance. I know it's been a while, but I've been busy the past few months.
I found a guide that had all the pieces I was looking for. As far as I can tell it went well, though it doesn't seem to be completely back to normal. I was able to unmount the recovery partition, but it was not re-mounted/installed.
I plan to unlock and install TWRP as the recovery. I may also try and root the phone, but keep the factory OS. But we'll see...

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:

Question Recovery boots into fastboot

Hey guys, got myself into a sticky situation by doing a lot of stuff without really thinking about it. I'm in a state where my slot a is pretty much borked I think. Anytime in slot a I try to reboot into recovery I just get put back into fastboot mode. in slot b I still have the LOS recovery. I've tried running the copy-partitions script on slot b to try to fix a but it didn't make a difference. Any help to get my slot a back up?

what I've done that doesn't seem to work:
Code:
fastboot --set-active=a
fastboot fastboot flash boot lineage-18.1-20210706-recovery-lemonadep.img
and my terminal response:
Code:
Sending 'boot_a' (196608 KB) OKAY [ 4.306s]
Writing 'boot_a' OKAY [ 0.604s]
Finished. Total time: 5.012s
It looks like it goes through successfully but when I try to fastboot reboot recovery I just get brought back to the bootloader/fastboot screen.
I accidentally did this to my slot B after I ran the copy-partitions script and I didn't lose my recovery, so it's not something with the recovery image. It's something wrong with my slot a. Any easy way for me to go back to stock or something?

Ok I'm back booted directly into OOS. I'll keep story time brief. Downloaded the OOS zip from the pinned OOS thread here. Downloaded payload-dumper-go from: here
Used payload-dumper-go to dump all the images out of the zip. Then, went into Sconny's thread, downloaded his zip, copied all of the fastboot commands he had in his flasher.bat and made my own shell script with just those commands. Ran the script and Viola. Thanks a ton Sconny! You saved my butt

shmallow said:
Ok I'm back booted directly into OOS. I'll keep story time brief. Downloaded the OOS zip from the pinned OOS thread here. Downloaded payload-dumper-go from: here
Used payload-dumper-go to dump all the images out of the zip. Then, went into Sconny's thread, downloaded his zip, copied all of the fastboot commands he had in his flasher.bat and made my own shell script with just those commands. Ran the script and Viola. Thanks a ton Sconny! You saved my butt
Click to expand...
Click to collapse
hm I'm in something of a similar situation, where slot b is f'd up but slot a is fine, but my problem is I can't update oos either in twrp or local update, so I'm going to try what you did to reflash oos (I used payload dumper already). so in short, did you essentially reflash oos on your phone? and I'm glad you didn't wipe first bc I do not want to lose data.

thirtythr33 said:
hm I'm in something of a similar situation, where slot b is f'd up but slot a is fine, but my problem is I can't update oos either in twrp or local update, so I'm going to try what you did to reflash oos (I used payload dumper already). so in short, did you essentially reflash oos on your phone? and I'm glad you didn't wipe first bc I do not want to lose data.
Click to expand...
Click to collapse
Yeah it gave me stock OOS, I used the newest version for global. I think you will lose your data; my rom was really messed up. I had dirty flashed stock OOS through TWRP (sideloaded) on top of Lineage OS... So my OS was probably completely messed up on that slot. I thought I would have needed a fastboot -w (which I think is wipe? not sure about that)
So mine booted OOS when it booted even though I forgot to do that, so I think it did some sort of wipe.

Well maybe you're right and you don't lose data. I just accidentally did it again after flashing magisk and I still have magisk. Though now I have to flash it again lol

shmallow said:
Hey guys, got myself into a sticky situation by doing a lot of stuff without really thinking about it. I'm in a state where my slot a is pretty much borked I think. Anytime in slot a I try to reboot into recovery I just get put back into fastboot mode. in slot b I still have the LOS recovery. I've tried running the copy-partitions script on slot b to try to fix a but it didn't make a difference. Any help to get my slot a back up?
Click to expand...
Click to collapse
May i ask what is this Slot A and Slot B? i never heard about smth like this in previous phones i used...

Ninxha said:
May i ask what is this Slot A and Slot B? i never heard about smth like this in previous phones i used...
Click to expand...
Click to collapse
Me too, honestly the only reason I looked into it was because I was forced to. From what I've gathered, it seems like slot b is a staging area for updates when downloaded. It's an entirely separate partition but I'm not sure it's fully functional. I really don't know much and would appreciate anyone that has some insight into that.

@Ninxha and @shmallow
while slots can be confusing, and even though this is in the op6 forum it greatly helps explain the new(er) slot a/b system
[GUIDE] The Noob's Guide to A/B Partitions and Other OP6 Idiosyncrasies
If you've just arrived on the phone modding scene, or are coming from another phone that uses traditional approaches to flashing, you've likely come across people talking about the "A/B partitions." If you don't have any experience with this...
forum.xda-developers.com

"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).