Just wanted to extend my thanks to those here for all their great notes.
The instructions by
@cloud1250000 in the first post were pretty much spot on, didn't have any issues other than those caused by my own missteps (such as rebooting after installing the TWRP zip since Magisk prompted me to. Whoops, through that I lost root)
I have a V350AWM (AT&T) that I got in July 2021 for $65USD. I got the SIM unlock from AT&T and was able to use LGUP to flash it to the V350U Android 9 Pie image V350ULM20f_00_NAO_US_OP_0218.kdz and used that for the past few months on Verizon. No 3G and not the best 4G signal, but plenty good enough.
Just this past week, I wanted to flash to Android 10 Q, and found this topic. Since the OP noted that the bootloader unlock should be done first, I followed the instructions at
https://forum.xda-developers.com/t/...instruction-no-octoplus-box-required.4052145/ and was able to downgrade to Android 8 for a baseline and then unlock the bootloader. The "button dance" to get the phone into EDL mode was definitely a challenge at first, but I've gotten better. I found that holding PWR and VOL-DOWN while the phone is on and plugged into USB, waiting until the screen flashes, and then (while still holding PWR and VOL-DOWN) clicking VOL-UP 6 or 7 times in 1-2 seconds and then releasing all three buttons was the magic to get into EDL mode.
After the bootloader was unlocked, I followed the instructions in the OP of this topic to download and install the 30b Korean image V350NO30b_00_LGU_KR_OP_1015.kdz. The installation went smoothly, but since it wasn't the OPEN_KR image or the latest 30d Korean image, I wanted to upgrade. However, I wanted to make sure I understood the process first, so I could patch the 30d OPEN_KR image with the US localized files. I also found that Magisk 20, which the 30b boot_a.img in the OP is based on, is not supported by the latest Magisk, and that Magisk Manager and Magisk have merged.
I ended up using Magisk 24.2 installed on the 30b image to patch the 30d boot_a image for future use, and then went through the process of installing V350NO30d_00_OPEN_KR_OP_0929.kdz and patching its boot_a image with Magisk to get root so I could install TWRP and patch the system files. All that went off without a hitch, I just used the vbmeta_a.img and boot_a.img from the 30d firmware instead of the OP's links. I'll attach them here, along with the untampered 30d boot_a.img.
Once all that was done, I was safely running the 30d image patched with the OPEN_US localized files, but the Camera's video was outputting corrupted files as others have experienced.
I saw the post above this by
@cmrntnnr about an OP_a.img patched with Android 10 frameworks that allows the camera to work. Sure enough, I used QFIL to overwrite OP_a and OP_b partitions with the provided V350N-A10C-Localized-for-NA.img and was able to get the camera working.
As far as I can tell now, I'm running an almost-perfect ROM. Camera + Video works, I see an enabled option for Advanced Calling > HD Voice (no WiFi calling but that's fine for me), I'm on the 30d firmware, there's no Korean-localized stuff anywhere to be found.
Just wanted to share that I was able to successfully follow these instructions and get a working AT&T V35 running on Android 10 on Verizon in 2022. Thanks all!
rocess fail
that's somewhat ambiguous, I ended up putting the abl_a in the a slot and the abl_b in the b slot. Not sure if they're interchangeable or if that's the reason why I experienced the issue I experienced. Shouldn't be but who knows.
