[Android General] kxkixi:
I've have spent well over 48 hours flashing my PVG100 from Verizon over the past few days, but I'd just like to point out a few things that I've noticed:

If you get stuck in EDL, hitting "Get Version" in Sugar might be an easier/faster way of getting out over holding the button.

There is a somewhat hidden option in Sugar to preserve the files in the install directory so that you don't have to copy a backup back in every time you restart it. Go to Options > Options and hit tab on your keyboard until you find "Keep User Data".

Regardless of what I use, be it the disable_dm-verity zip or a patched magisk boot image, no matter the ROM, my data partition becomes encrypted.

I've installed Lineage 16 and 17, as well as Phh AOSP 9 and 10, all of them have the same issue with VZW where it says "No SIM Card", but shows Verizon as the carrier, and correctly reports the IMEI. They receive phone calls, but cannot send them, or use data.

If you are having problems with LineageOS 17 not having root, there is an option in ADB settings that will allow you to use `adb root` to escalate permissions, there may be a way to get root via that, or at least do some other customizations if you don't need rooted apps.

I had an issue with LineageOS 17 after about an hour of using it where the screen went to the startup animation. I still had ADB access, so I tried firing a reboot. It came back, and when it loaded, the screen was black. Backlight would turn on and off when hitting the power button, still could use ADB, but it would not come back regardless of how many times I rebooted.

Phh AOSP 10 will not reboot for me. After the first reboot, I am stuck on the startup animation.

Phh AOSP 8.1 seems to be the best GSI for me on VZW at the moment. After setting the preferred network to include LTE, I am able to receive phone calls, send/receive texts, and use mobile 4G data. Still cannot send phone calls.

There are a few resources around for fixing VoLTE such as https://github.com/KhushrajRathod/VoLTE-Fix, but after doing the setprops required by it, either nothing will happen, the phone will become stuck on the loading screen, or it will sit at the loading screen for a minute before booting itself into recovery.

I also tested Havoc OS and LOSQ GSI's, both booted (and rebooted, in contrast to Phh AOSP 10). Both also lack any functioning telephony with a VZW sim, other than receiving calls.

For the moment, being that I haven't found a reliable way to be able to make phone calls on this device, I'm going to be sticking with a slimmed-down stock ROM with Magisk. I have a feeling that the telephony issues are something fairly trivial and that somebody will crack it at some point, (possibly copying IMS files or something like that from stock ROM? VoLTE support seems absent on any GSI, and running this device on Verizon is "CDMA-less") but I have spent three days working on this phone and it's about time that I put it back into service. I'll keep an eye out here for any further developments, though ;)

If it wouldn't be too much to ask, when we're talking about success and failure here, could you guys please specify whether you have the US or Euro version of the phone, as well as your carrier? Seems like some issues are specific to some phone/carrier combinations and I feel that it would be good to be able to put together some statistics on what works and what doesn't for a given combo.

Many thanks to all of the people in this thread who have spent their time figuring this stuff out. I've read the entire thread at least three times over now, and although the bits and pieces of information are a bit scattered across the pages, I've gotten something useful from just about everyone here.

---- update

I ended up bootlooping my device while trying to slim it down, so I did a bit more looking into VoLTE support. Looks like there is an overlay in Phh-treble (and derivatives which looks to be just about every GSI at this point) that enables CAF modem software or something like that. I'm not sure whether that's what would be needed to get the VoLTE issues fixed, or whether it's even compatible, but setting "persist.sys.phh.ims.caf=true" should enable the overlay. Any time that I put that into my build.prop, the phone becomes stuck on the loading screen. Removing it allows the phone to boot again. My best guess would be that we probably need to try to make and merge a preset to Phh-treble that'll get everything working, and probably before that, figure out what has to be done to the ROM to get it to work.

As a side note, it looks like there's some stuff in /vendor having to do with IMS. I'm not sure if /vendor is used much if any in other ROMs (and if I remember correctly, only certain GSIs pull from /vendor, some of the GSI's I've loaded don't have the Verizon crap on them). It's also possible that the stuff in /vendor is conflicting with the overlay. Overlays might also explain why I can't boot Phh AOSP 10 more than once without formatting. /vendor is located at /dev/block/mmcblk0p28, by the way, and can be accessed in recovery with `mkdir /vendor; mount /dev/block/mmcblk0p28 /vendor`.

Also, it would be cool if we could get our own forum for the Palm Phone instead of just having a tag :P