Develop Bugs

[Q] need help to restore to GPE stock rom

Hello, I'm new to HTC phone. I can't enter system now. Please help!.
my phone's information:
CID: GOOGL001
ROM: Google stock 4.4.2
Recovery: CMW latest.
bootloader: unlocked.
SHIP-s: ON
What I did:
I copied the stock google rom 4.4.3.zip to the internal sd card, and use recovery installed the zip file. then reboot,
current status:
the phone can't enter the system, it enters the recovery everytime reboot.
I can enter the bootloader
PC can do fastboot,and adb commands, PC can find the phone.
What I want now is to restore to the unrooted GPE stock ROM 4.4.3. What shall I do now.
thanks,

heartready said:
Hello, I'm new to HTC phone. I can't enter system now. Please help!.
my phone's information:
CID: GOOGL001
ROM: Google stock 4.4.2
Recovery: CMW latest.
bootloader: unlocked.
SHIP-s: ON
What I did:
I copied the stock google rom 4.4.3.zip to the internal sd card, and use recovery installed the zip file. then reboot,
current status:
the phone can't enter the system, it enters the recovery everytime reboot.
I can enter the bootloader
PC can do fastboot,and adb commands, PC can find the phone.
What I want now is to restore to the unrooted GPE stock ROM 4.4.3. What shall I do now.
thanks,
Click to expand...
Click to collapse
Did you flash the Ruu?you can follow this guide:http://forum.xda-developers.com/showthread.php?t=2706441

Jyotirdeb said:
Did you flash the Ruu?you can follow this guide:http://forum.xda-developers.com/showthread.php?t=2706441
Click to expand...
Click to collapse
Thanks, I think I did use fastboot oem rebootRUU and flash the RUU google edtion conversion following the thread http://forum.xda-developers.com/showthread.php?t=2708589 but it's failed. and then I tried flash the zip in the thread you just mentioned, still failed. got an error message and installation aborted. the following msg is the one I use cwm flash the zip in recovery:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully! @symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.

I tried factory reset, and wipe everything, flash the gpe4.4.3_m8 zip, still failed. I have used, phil cwm recovery and twrp recovery.
thanks,

Soft bricked and can't flash any ROM

So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )

What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.

redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S

tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.

Did you fastboot erase cache before installing TWRP, as I suggested?

Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.

It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.

[Q] GPE 5.0.1 Bricked my phone - can anybody help?

Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!

should be in Q&A mate
I have requiested the mods to move this

So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.

tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...

I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..

tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode

UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...

Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...

TWRP Backup failed

I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.

nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!

Kyuubi10 said:
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Click to expand...
Click to collapse
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.

nerodarknight said:
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
Click to expand...
Click to collapse
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.

Kyuubi10 said:
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Click to expand...
Click to collapse
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?

nerodarknight said:
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
Click to expand...
Click to collapse
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again

Kyuubi10 said:
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Click to expand...
Click to collapse
Doesn't not seems to work, formatted the system partition but it still failed

If this is any help, I successfully converted it to WWE but since I got a bug with the service : LTE (data) is good but no call or text whatsoever so that's why I'm trying to convert back, flashed the firmware zip and then restore back up. The firmware zip worked out fine but the restore always failed. To add to that, when I'm on WWE firmware I can restore the WWE firmware backup just fine.

I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?

nerodarknight said:
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
Click to expand...
Click to collapse
I believe TWRP should be capable...
Google for a guide.

nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
I have the same problem this happened after I formatted the date to blink rom

How can I solve this problem after I tried to install the rom maximos hd and I did not succeed I returned my bachup from the stock more now this giving error in the horade do the same I am with bild 2.41.401.3 cid HTC__M27 mid 2PS62000
Can someone help me please ???

Stuck after trying to upgrade to Pie.. worried I bricked it.

Having an issue with my XL. I've been on LOS 15.1 for a while and wanted to try out the new Pie image. I made a backup and fired up fastboot as usual. I left the -w tag on as I wanted a complete wipe. Fastboot failed while wiping userdata and now bootloops twice before dumping me in stock recovery. I am completely unable to format data while in stock recovery. Same when I boot TWRP through the PC. Stock recovery says it can't write a new EXT4 partition and TWRP says I have no internal storage, then throws a ton of errors. Flashing OEM images from Google (Oreo or Pie) results in the same thing.
Any ideas? For the first time in years I am stumped.

I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.

caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
Is your platform tools updated to the newest one?.
Edit I thought I was on the pixel 2 forum.

Could try to repartition the storage using a method similar to this one for the nexus 7? https://forum.xda-developers.com/nexus-7-2013/general/guide-repartition-nexus72013-to-t3599907
You would need to figure out the proper partition table for the Pixel though.

If you're 100% sure your platform-tools are fresh, you've got me stumped as well. I ran into tons of errors and such due to out of date tools when flashing Pie - obviously updating the tools fixed the issue.

Well I'd try external Type-C USB drive it enables external storage even if internal isn't working and fastboot flash your backup.

caain said:
I'm able to flash just about anything with fastboot, but it will always fail on writing to userdata. I'm unable to erase, format, or mount the userdata partition, and fastboot will always reply "FAILED (remote: flash write failure)". This is using the most recent platform-tools under a root shell in Linux. Device and bootloader are unlocked.
I recently tried the original factory firmware (which includes a userdata.img fastboot file) to no avail. The same "FAILED (remote: flash write failure)" error persists.
Click to expand...
Click to collapse
i got the same problem, i just downloaded the Platform-Tools and opened it in PowerShell and executed flash-all script and it worked

Flash all script is good but I'd rather use external storage .. it's nice to know that there's more than one way to fix the problem outside of platform tools

I had issues with Pixel before and the multi partition thing screwed me up, but the Unified_Android_ToolKit was able to fix it for me. Worth a try for sure. Download Google Factory Image and use the tool.

Thanks for all the help everyone. Lots of good ideas here that I'll save for next time. Ten years tinkering with phones and I've never gotten this stuck.
In the end I flashed back to the factory Pixel XL image (October 2016). Like the previous attempts, it failed on accessing userdata. I used fastboot to flash a userdata.img file again, which similarly failed but somehow the phone still booted after about 20 minutes.
I found similar threads for other phones where people were in the same situation, but nothing they tried did the trick.
Back up and running now.
Sent from my Pixel XL using Tapatalk

Very odd. Based off your last post I'm going to assume you are not sure what triggered the issue?