• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Bootloader Unlock and Root Instruction - No Octoplus Box Required

Search This thread

zfk110

Senior Member
Jan 11, 2014
1,031
204
Atlanta
I hesitate to respond to this because it has been covered again and again. Sim lock and bootloader lock are entirely different. You should strongly consider purchasing a sim-unlock code and applying it before flashing another rom to a carrier branded phone! There are instructions in one of the threads on how to get out of this pickle. It involves flashing a v35 rom for Mexico region.
links dont work

Boot+TWRPv3.3.1_only-V35-Pie-ULM20F.img - boot.img from latest V350ULM20f firmware
 
Last edited:

zfk110

Senior Member
Jan 11, 2014
1,031
204
Atlanta
If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.
after flashing twrp on a/b, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (http://Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip), and Magisk, my v35 wont boot, it got stuck on LG logo, I can go back to TWRP.

Is there any kernel, boot img I have to flash it? Im on this V350ULM20f_00_NAO_US_OP_0218.kdz Pie build
 

dbaldock9

Member
Feb 27, 2013
13
1
Houston
I have a couple of questions regarding rooting the LG V35 - but first a bit of background:
.
AT&T got more heavy handed about my LG V30 not being supported (it's rooted and running LineageOS 16.0 (Android 9)) - by texting & emailing me - saying that I had 30 days to activate a compatible phone, or they'd send me one & activate it, while deactivating my V30.
.
In the online AT&T documentation, I found that the LG V35 will definitely support the VOLTE / WiFi calling that AT&T is moving to.
.
So, I bought a new AT&T model of the LG V35 from Amazon, installed the nano-SIM from the V30, and it immediately activated.
.
.
Now, the questions:
1.) How far can you go with the procedures in this thread - and have the V35 remain compatible with AT&T's new requirements?
2.) I've read that the 3rd party ROMs don't support the AT&T VOLTE requirement - so do I have to stick with upgrading back to the stock LG ROM (current SW is V350AWM20c), or is there a more stripped-down version of Pie from Google, that also supports VOLTE?
.
Thanks,
David Baldock
 

cmrntnnr

Senior Member
Jan 11, 2017
278
211
I have a couple of questions regarding rooting the LG V35 - but first a bit of background:
.
AT&T got more heavy handed about my LG V30 not being supported (it's rooted and running LineageOS 16.0 (Android 9)) - by texting & emailing me - saying that I had 30 days to activate a compatible phone, or they'd send me one & activate it, while deactivating my V30.
.
In the online AT&T documentation, I found that the LG V35 will definitely support the VOLTE / WiFi calling that AT&T is moving to.
.
So, I bought a new AT&T model of the LG V35 from Amazon, installed the nano-SIM from the V30, and it immediately activated.
.
.
Now, the questions:
1.) How far can you go with the procedures in this thread - and have the V35 remain compatible with AT&T's new requirements?
2.) I've read that the 3rd party ROMs don't support the AT&T VOLTE requirement - so do I have to stick with upgrading back to the stock LG ROM (current SW is V350AWM20c), or is there a more stripped-down version of Pie from Google, that also supports VOLTE?
.
Thanks,
David Baldock

You should read the thread. You can root the phone and stay on the AT&T rom. To answer your questions, there are no debloated roms a la John Fawkes' for the V30, just stock roms in kdz format when published. AT&T is not part of that set. It would be helpful if you posted a dump of the AT&T A10 rom or even just the the OP partition.

If you do decide to move to another rom, be sure to sim-unlock the phone beforehand. The GoogleFi rom is where most go. It was never updated to A10. It's OK and VoLTE works great. VoWIFI is a dud.

There is a procedure in the Guides section of the forum to flash a Korean rom and localize to NA. It only sort-of works. That.is where the AT&T A10 OP image comes in.

Good luck and report back.
 

dbaldock9

Member
Feb 27, 2013
13
1
Houston
So far, the experiences I've had with rooting my phones (Nexus 5 and LG V30), and tablet (Nexus 7 (2013)), have all been using adb and fastboot from the command line, to flash a TWRP recovery partition - and then ROMs and Magisk are installed with TWRP.
.
Does the fact that my LG V35 has Android version 9 (Pie) mean that it's "A10"?
Which tool would I use to get "a dump of the AT&T A10 rom" from my LG V35?
.
When you say that "VoLTE works great" with the GoogleFi ROM, do you mean that AT&T is OK with it being used on their network, after they shut down the 3G voice network? Also, if the GoogleFi ROM was never updated to A10, does that mean it's Android 8 (Oreo)?
.
If I want at least Android 9 (Pie), I can stay on the stock ROMs, downloaded from LG (which I guess have the AT&T branding) - and just use root tools to deactivate / remove the LG & AT&T "cruft".
 

gitgudgusgus

Member
Jul 22, 2021
6
1
I know I'm late to the party with this thread, but I thought I'd say thank you for all the effort you put into putting this together. And thank you to all the contributors of the software and software to make it possible!

The most difficult part was getting it to boot in EDL 9008 mode. It took multiple tries every time I had to get into it. I started to wonder if my phone was just not meant to do it the first times I tried.

I actually first looked into rooting my device when I first got it, but it was basically only possible if your phone was from Tmobile or something (It was years ago so I don't recall the actual hangup). Eventually I just gave up until today when I thought to look again to see if people figured it out.

Fortunately, my not-so-smart self found this thread where far more capable people were able to figure it out. This way I can call myself "techy" without knowing anything about tech.
 
  • Like
Reactions: dbaldock9

zfk110

Senior Member
Jan 11, 2014
1,031
204
Atlanta
Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
I can't pass this Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified I have been trying since two days, with windows 7, 10, 11
 

TheCurtisNad

New member
Jul 29, 2021
3
0
Okay I have a problem. I have not unlocked the bootloader yet. My issue is that when I Boot the phone in EDL 9008 mode, the port does register that my phone is there! but it says COM11 and not COMXX so I can't do anything in QFIL. If I could have help with this it would be greatly appreciated

Edit: SO I fixed the problem! It's funny how every time I reach out for help I ALWAYS find the answer somehow. But what I did was I installed the driver that came with the qfil folders, and it worked!

Edit 2: OKAY LMAOOO I never considered until just now that XX would be just in general like it could mean any number. But either way, There was a problem that I ended up fixing so that's all that matters haha. It's like 1:53 AM and I am very tired LMAO
 
Last edited:

sgdubz

New member
Jul 15, 2021
3
1
Two things I learned in doing this process: first thing is that you don't have to use the specific EDL 9008 driver linked in OP, the one that requires you to disable driver signing, you can actually use a more modern and properly signed driver-- I'm using one I found on Acer's support pages, see attached.

The other thing I learned is that EDL mode needs to have a totally uninterrupted connection to the computer via the USB cable. If your USB-C connection on the phone is flaky like mine and the connection is interrupted even for a split second, you'll have to reboot and try to enter EDL mode again. This makes it *incredibly* frustrating to follow all of the steps in OP and I wouldn't recommend anyone even try if they have a flaky USB-C port.

Having said that, I did end up with an unlocked bootloader, TWRP and have the Korean V350NO30c_00_OPEN_KR_OP_0125 firmware installed and modded for US carriers. Still not sure if it was worth it, only because I wasted to much time fighting with EDL mode.
 

Attachments

  • 4G_Quectel_15.55.24.445_W10x64_A.zip
    2.7 MB · Views: 2
  • Like
Reactions: alonzo_ama26

Nlee009

New member
Mar 23, 2020
2
0
Thanks to this post, I could root my LG V350N. It's easy if read carefully and watch Rooting G7 video for new users.
 

ianruto

Member
May 3, 2016
39
3
LG V35
I have followed every step from the OP my device was on AT&T 10 firmware up until i flashed the Oreo NAO kdz. I wished to flash the Korean firmware and started by trying to unlock the bootloader as it was originally locked. However, the "oem unlock" command kept throwing the error

FAILED (Write to device FAILED (Too many links))​

and immediately after i could not get the phone to stick to the fastboot page as it kept looping and only stopped when the cable was removed. I tried using my back ups for the abl, laf and boot partitions and now it says "all slots are unbootable" at the g.co/afh, red icon, page.
I have even tried the engineering lafs to get back download mode but the pc wont detect it anymore.
Fix please??
 

Top Liked Posts

  • There are no posts matching your filters.
  • 19
    Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.

    This is what you will be doing in a nutshell.

    • Setting the phone into a baseline Oreo conditions
    • Extraction of abl, laf, and boot partititions
    • Installation of the engineering abl and erasing the laf's using QFIL
    • Unlocking the phone
    • Flashing to Pie and maybe Q in the future if you want to update from Oreo
    • Generation and installation of a magisk-patched boot image for root

    Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.

    Preparation and requirements:

    On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.

    Download and install each of these programs on your PC in the listed order.

    You are also going to need some super important supporting files that make all of this magic possible.


    Troubleshooting:
    These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.

    1. Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
    2. Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
    3. Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
    4. Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
    5. Re-install LG mobile drivers, https://is.gd/Jbrvx1.
    6. Try another USB cable.
    7. Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
    8. Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
    9. Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
    10. Reboot the computer.
    11. Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
    12. Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.

    Step 1: Setting an Oreo baseline:

    The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider

    1. AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
    2. AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!

    To set the baseline:
    • If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
    • If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version

      To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!

    Step 2: Partition Extraction, Modification and Bootloader Unlock

    • Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
    • Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
      “Qualcomm HS-USB QDLoader 9008 (COMXX)”
      where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
    • Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
      • You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
      • There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
      • There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
      • Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
    • Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
      • Right click on “abl_a”
      • Select “Manage Partition Data”
      • Select “Read Data…”
      • Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
      • “C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
      • Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
    • Use QFIL to get fastboot:
      • Write the engineering abl’s: In QFIL, do the following:
      • Right click on abl_a.
      • Select “Manage Partition Data”
      • Select “Load Image”
      • In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
      Repeat this same procedure for abl_b.
    • Erase laf’s: In QFIL, do the following:
      • Right click on “laf_a”
      • Select “Manage Partition Data”
      • Select “Erase”
      • Confirm that you want to erase
      Repeat for laf_b.
      • Unplug the phone from USB
      • Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
      • Turn the phone off.
    • Unlock the bootloader:
      • Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
      • Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
      • Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
      • Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
      • Reboot the phone


    Step 3: Restore download mode and flash to desired rom:
    • If the current version of Oreo is where you want to be then skip to Step 4.
    • If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
    • Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
    • To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!

    Step 4: Install Magisk for Root:
    • Re-enter EDL mode with the above button dance procedure
    • Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
    • Generate a Magisk-patched booted image working directly with the phone:
      • Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
      • In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
      • Open the “File Manager” app and navigate to the Download folder.
      • Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
      • Connect the phone to USB and place it in file transfer mode.
      • Copy boot_a.img and boot_b.img to the phone Download folder
      • Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
      • Navigate to the “Downloads” folder where and select boot_a.img.
        There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
        Repeat this process with boot_b.img.
      • Install the Magisk-patched boot images using the PC:
      • Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
      • Put the phone into 9008 EDL mode with the button dance described above.
      • Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
      • Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
      • Repeat the previous step for boot_b and load the magisk_patched_b.img file
    • Reboot your rooted phone.

    Step 5: Remove Root Checker: (Added 20200409)

    I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.

    • Put the phone in USB debug mode
    • Connect to your computer
    • With adb from a command prompt on the computer do the following

      • adb devices <-- If your devices is properly connect and recognized, adb will respond
        List of devices attached
        LMV350XXXXXXXXX device

      • adb shell <-- If you have a shell into the phone you will now see
        judyp:/ $

      • pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
        Success

      • pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
        Success

    Happy Rooting!
    4
    There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
    Wow,
    Thanks for the great guide, can't wait to try this.
    One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
    4
    It is great to see people unlocking their V35's.
    It is disheartening to hear so many problems. I'll make updates to the original post. I've been taking notes where people have had difficulty and want to make sure that I pull in as much as possible. Thank you @larciel for the list of improvements, @Android# for guiding others through this journey and others not named. I'll be making changes to the OP to hopefully make this process smoother.

    The biggest source of avoidable difficulty seems to be with Pie. The guidance will be to flash last stable Oreo kdz and then upgrade to Pie afterwards.

    I am at a loss about what to suggest regarding PC's, software, and cables. Digging out an old PC from the closet, basement, or attic just doesn't seem helpful. LG phones like USB 2.0. It is not easy to tell a good cable from a bad one. The Windows handling of drivers is an utter nightmare. I agree with @asltLies comment aboit this and feel your pain. Personally I have used an old Win7 laptop that never connects to the internet.

    A potential side effect of driver and cable issues is that Qfil appears to work but gives corrupt backup files. I will post md5 sums to use as verification.

    One especially irritating problem is inability to get back to download mode regardless of the cause or symptoms. Being able to blast the problems away by flashing a kdz is reassuring and anxiety provoking if lost. Download mode functionality resides within laf. Just as there is an engineering abl that gives fastboot function, there is an engineering laf at this link.

    https://www.androidfilehost.com/?fid=1395089523397937620

    It can be written with qfil and has helped get me out of some pinches. Perhaps it will do the same for others.
    3
    The biggest source of avoidable difficulty seems to be with Pie. The guidance will be to flash last stable Oreo kdz and then upgrade to Pie afterwards.

    Sure, sort of like how you need early Oreo for V30. I know it's not the same situation, but it's an analogy.

    If people say the procedure isn't working, first ask what firmware they are on. ;)


    I am at a loss about what to suggest regarding PC's, software, and cables. Digging out an old PC from the closet, basement, or attic just doesn't seem helpful. LG phones like USB 2.0. It is not easy to tell a good cable from a bad one. The Windows handling of drivers is an utter nightmare.

    Personally I have used an old Win7 laptop that never connects to the internet.

    In a similar vein, I give you permission to copy and adapt my V30 WTF Section 7 Trouble Shooting Tips for the V35. I even have links to different resources in those tips.

    There's a dozen tips. First one is firmware version. The other 11 deal with ADB/fastboot communication issues. Reinstall drivers, different port, different cable, different ADB installation, different computer. Bonus points for old Win7 Intel PC with USB 2.0. Also people have used cheap USB 2.0 hub. All that is in my Section 7 Trouble Shooting Tips.

    Already written out and when people ask for help, point them to that first. Of course your version incorporating some V35 points. You can post it bottom of your instructions. Just say "adapted from @ChazzMatt Trouble Shooting Tips for V30". ;)
    3
    FYI... I went ahead and unlocked the bootloader on my stock AT&T ROM and rooted with Magisk. I had a heck of a time with a fastboot bootloop after flashing with QFIL. I did go ahead and unlock the bootloader (and restored the abl's and laf's) but remained in a bootloop to fastboot. In a last ditch effort, I changed boot slots with fastboot and was able to recover and then root. Note that widevine changed to L3 (although safetynet passed) and relocking the bootloader resulted in a failed boot that I could not recover from. I used QFIL to reflash the engineering abl's, nuked laf's and restored the unrooted boot images and the stock abl and laf. Once again I was in a bootloop (without fastboot this time). I switched slots again and finally was able to boot back to a locked and unrooted phone. Widevine was restored back to L1 as well.

    This was pretty hairy. Anyone have any ideas about why I had to switch slots to get the phone to boot? I'm pretty new to this A/B stuff....

    Ultimately, I didn't want to give up widevine L1 for root but I wanted to see if L1 was possible with root on this device.