Develop Bugs

[Guide] Unlock/Root/Update/Relock for BQ Aquaris X2 pro (zangyapro)

Introduction
I'm writing this thread to summarize useful information about the BQ Aquaris X2 pro such as:
preliminary actions (adb and fastboot configuration)
unlocking the bootloader
flash a factory image
root the device (currently without TWRP)
updating the device without losing root
relocking the bootloader
I own this phone since July 2018. I started writing my notes in August 2018 in the form of a Google document (link here). I shared this document with some telegram groups and some people I know.
Now I that I think it can be more useful to summarize all my notes here on XDA so that all interested people can access it.
DISCLAIMER:
By attempting any of the processes listed in this thread you accept full responsibility for your actions. I have no responsibility about your actions.​
1) Preliminary actions
1.1) Developer options, USB debugging and Unlock OEM
The first thing you need to do is to enable Developer options, USB debugging and Unlock OEM. Hence:
enable “Developer options” by hitting 7 times on the build number (Got to settings --> about phone)
enter the new menu “Developer options” and,
enable “USB debugging”
enable “Unlock OEM”
1.2) Download and configure abd and fastboot
All steps listed in this guide will require the use of Google Platform tools. I suggest the use of the one provided by Google here: https://developer.android.com/studio/releases/platform-tools.
Download the one for your operating system:
View attachment 4655394
Be sure that your terminal can access adb and fastboot from every position by configuring the PATH. I'm use to configure the PATH on the fly when I need it. As I said before, I work on Linux/macOS where you can set the PATH by:
opening a terminal and running:
Code:
export PATH=$PATH:path_to_platform_tools
2) Unlock the bootloader
Unlocking the booloader will wipe your phone. So backup your data first.
The good news here is that this phone can be handled like a Nexus/Pixel phone. Therefore, the procedure to unlock the bootloader is straightforward:
do all stuff at point 1.1 and 1.2
open a terminal
plug your phone to the PC
reboot into the bootloader
Code:
adb reboot bootloader
run the code:
Code:
fastboot flashing unlock
now you have to wait until your phone reboots. It takes a while, don't panic!!! When the phone is on the initial screen turn it off and reboot into the bottloader again by holing 'power + volume down'.
run the code:
Code:
fastboot flashing unlock_critical
it's done. Your bootloader is completely unlocked. Now, you only have to wait again for the reboot.
3) Flash a factory image
As you probably know, BQ releases a factory image at each update at this link factory images. Factory images are very useful to perform a very clean install. Are you experiencing some issues with your phone and none of the trick you tried solved it? If it is a software issue a clean flash with a factory image will likely remove the issue.
Keep in mind that by flashing a factory image you will wipe also the userdata partition. So backup your data first. Now let's see how to flash the factory image:
you need an unlocked bootloader (see previous sections)
download the factory image from this link
unzip the archive
open a terminal at this folder
be sure to have abd and fastboot properly configured (see previous sections)
run the script to flash all (*):
Code:
./sdm660_fastboot_all_images.sh
wait the end of the process. The phone will reboot.
(*) on Windows you have to deal with the file sdm660_fastboot_all_images.bat. I suppose it's similar but I've never done it on Windows.
4) Obtain ROOT privileges
Nowadays, the most common tool to obtain root privileges is Magisk. Many people here know very well what Magisk is and how to install it with TWRP. However, TWRP is not yet ready for BQ Aquaris X2 pro, hence, we must follow the procedure for installing it without the custom recovery.
When I wrote the document in August I find very informative this guide by @nathanchance. It's for the pixel 2XL but, as I told you before, it works perfectly also for the BQ Aquaris X2 pro (zangyapro). So here I summarize what @nathanchance already posted. All credits must go to him.
Here you have the steps:
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Please note that it exists also a specific thread where the author also provides the patched boot.img files for download. Hence, you can start from point 6 without patching the boot.img by yourself. Take care of selecting the right one. Here you have the thread link.
5) Update the ROM without loosing root
To the best of my knowledge, the only way to update keeping root is by using the factory images provided by BQ.
Download the factory image of the latest firmware (link)
Extract the file zip and upload the file boot.img on your phone
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt and then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Place the file patched_boot.img in the folder of the BQ firmware unzipped at point 2
Make a copy of the file sdm660_fastboot_all_images (.sh in Mac/Liux and .bat on Windows).
Rename the file, I called it sdm660_fastboot_upgrade.sh
Change the following lines (this will preserve root privileges on your phone):
Code:
fastboot flash boot_a boot.img # <-- delete this line
fastboot flash boot_a patched_boot.img # <-- add this line
Delete the following line (this will prevent your data to be wiped):
Code:
fastboot flash userdata userdata.img # <-- delete this line
Run from your terminal
Code:
./sdm660_fastboot_upgrade.sh (or bat)
I think that one can also update using the OTA. This will make you lose the root privileges and therefore, you will have to repeat the procedure at section 4. I've never tested this so, if you decide to do it, you are on your own.
6) Relock the Bootloader
By relocking the bootloader you will lose all your data, hence, backup them first.
To relock the bootloader you only need the following commands:
Code:
fastboot flashing lock_critical
fastboot flashing lock
Each command will wipe your data and will reboot the phone. Be patient waiting for the reboot and do not panic.

Reserved.
(work in progress)

First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
3. Open Magisk Manager and click the Install button.
Click to expand...
Click to collapse
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
with this I can patch the boot image successfully
But unfortunately I can not run the "sdm660_fastboot_upgrade.sh.bat" it does not recognize my device.
When checking the commands in the batch I found that my device is acting really strange, sometimes giving different errors for the same command like:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
Setting current slot to 'a'...
FAILED (remote: Invalid Slot)
finished. total time: 0.004s
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
also strange:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot flash boot patched_boot.img
target didn't report max-download-size
sending 'boot' (50749 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...

raudidroid said:
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
Click to expand...
Click to collapse
Thanks. I was not aware of this. And now I can't check this on my device because I started using GPay and I prefer to stay with no root and locked bootloader.
Maybe I will play again with the bootloader when TWRP for this device will be released. If it will

got it running!
raudidroid said:
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
Click to expand...
Click to collapse
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Short moments of panic due to boot-loop included (I flashed a defective boot image [vmware drag and drop files obviously did not copy the whole file] )
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)

Hey @raudidroid, when I answered to you the first time I did not read all the message or you edited it later. Only now I'm reading the issues you faced.
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Click to expand...
Click to collapse
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Click to expand...
Click to collapse
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.

luk.giak said:
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Click to expand...
Click to collapse
I was using CMD / Command Prompt on win10, but maybe I have to many ADBs/Drivers/... installed. got a really weird behavior...
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
Click to expand...
Click to collapse
without root it wouldn't work, i got "no permissions (user in plugdev group; are your udev rules wrong?)"
with root everything ran smoothly
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
Click to expand...
Click to collapse
Oh! Yep, that sounds like it would have been the better way to do it
Thanks for your post and your answers.
BTW: half-OT do you know any way to get netflix running after the rooting?

For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
Click to expand...
Click to collapse
Your welcome!

For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
Click to expand...
Click to collapse
Thanks for sharing.
I'm on PIE as well. Today I flashed the factory image to make a clean install.

Hello, maybe someone can be of help to my situation.
I had my phone rooted in the last firmware version (1.7.3), and I was getting notifications to update to Android 9 pie for some time, however I was waiting to have some time to spare and first backup my files and do a factory update to pie and then root.
However, last nigh without warning my phone just rebooted and updated to pie, (firmware ver 2.0.2) and I lost root obviously. However, all my files, apps, etc were intact.
So today I decided to root my phone again. I download the firmware zip from BQ's site and then used Magisk (ver. 19.2) to patch the boot.img.
I rebooted to fastboot and did "sudo fastboot flash magisk_patched.img", and rebooted but the phone got stuck in the logo screen.
Then I used method 5 of this tutorial and ran ./sdm660_fastboot_upgrade.sh (with the mentioned modifications), however it bootlooped again. Then I flashed the original boot img and my phone booted just fine again, I tried to patch the img again, did again step 4 and it bootlooped again.
Any clues on how to successfully root ? Never had any problems updating and rooting from firmware 1.4.0 to 1.7.3.
Thank you for your time

Rooting pixel 2xl

I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks

grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.

grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?

What happens when you run the fastboot command "fastboot flashing unlock"?

Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks

OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.

grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.

Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?

grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:

Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.

grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.

Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.

grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679

Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?

grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.

Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.

grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.

Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?

grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........

Bootloader Unlock and Root Instruction - No Octoplus Box Required

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.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
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.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
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.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
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.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
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.)
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
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.
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
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712​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!

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?

THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?

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.
fpozar said:
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?
Click to expand...
Click to collapse

cmrntnnr said:
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.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!

Thanks, I follow your steps very carfully, and now I have a rooted v35.

Nicely done. Thank yoh for sharing the result.
fpozar said:
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?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse

So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?

I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?

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.

dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.

vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!

Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.

vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone

I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.

Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.

so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do

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.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse

Will this help me sim/carrier unlock my v35awm?

Can you lock the bootloader after this is done and keep root? Need it for banking apps.

(GUIDE) Unlocking bootloader, Rooting - from start to finish UPDATED.

Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the bootloader unlocking and root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods but I can confirm that this 100% works
NOTE* This guide is intended for all OnePlus 8 devices but the boot image files are for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
It is possible to extract the boot IMG from any firmware using the payload extractor tool which can be found online, then change the commands to reflect the files you obtain, for the sake of clarity I'll be using 10.5.12
Hope this helps.
Pre-requisites
A European variant of the Oneplus 8 Pro: IN2023
Running the following firmware: 10.5.12 IN11BA
ADB Access to your phone
A decent amount of charge, eg: 80%
A Windows 10 based computer
The cable that came with your phone
Obtaining ADB access to your device using your computer
1. Connect your phone to your computer using the cable that you charge it with
2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then install the driver you can obtain from the drive which will appear on screen within "This PC" (i won't detail this as it's pretty self explanatory)
3. On your phone Open settings and navigate to "About phone"
4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"
5. Back out, then click "System"
6. Scroll down to "Developer Options" and open it.
7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it, also turn on) also turn on "OEM Unlocking" in the same section and agree to any prompts.
8. On your computer Download this folder https://drive.google.com/drive/folders/1S-yNzdvOvdZzPuxhYuEuwnelzfdEd0K2?usp=sharing
This is adb and fastboot so you can talk to your phone via your PC.
9. Move it to the root of the C: drive, so it looks like this in the filepath
C:\Android
10. Navigate to the folder and perform the following:
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
11. In the window type the following command
adb devices
press enter
If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.
You should see a readout of a device followed by a code, you now have ADB access and can continue.
Unlocking the bootloader
NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO
1. Connect your phone to your computer
2. On your computer Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
3. Type the following command into the window
adb reboot bootloader
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
4. On your computer Type the following command into the window
fastboot oem unlock
press enter
NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE
5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots
You have just unlocked the bootloader to your phone
Once the device has booted, set it up again and then follow the steps to unlock "developer options" and "USB Debugging" once more.
Installing Magisk Manager and obtaining Root access
Before you begin, please follow these two steps to install the magisk manager
Magisk manager
i) On your computer download this folder https://drive.google.com/drive/folders/1VH_2Ql6L5580rVYvRZ5l8t7cX2XENEAG?usp=sharing and move the file inside to your internal storage on your phone, the file is called "MagiskManager-v7.5.1.apk"
ii) On your phone using a file manager navigate to where you moved the file and open it, this will install the Magisk Manager used to manage root access, open the Magisk Manager once, you'll see it does not have root access.
Rooting
1. On your computer Go here https://drive.google.com/drive/folders/189DlZH1NSMrgVF996S7y3q5_IG9RAFIr?usp=sharing and download the folder
2. Copy the file inside the folder which is called "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. There are two options for rooting, the first is to boot it first, this is safer as it is not permanent and a reboot will rejoice the booted image, the second is to flash it, this is a one step option but if the image isn't right then you could end up in a bootloop so id recommend the first.
Type the following into the window
To boot:
Fastboot boot magisk_patched.img
(Your phone will reboot automatically)
To flash:
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
then
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
NOTE* If you booted the image then simply click the top install option then go to install directly, this will make root permanent.
That's it, you've now unlocked your bootloader and rooted using the most current boot img at the time of writing.
------------------------------------------------------------------------------------------------------------------------------------
Please don't quote the entire thread!!!!!
If i've missed anything out or anyone notices a mistake please let me know and i'll amend accordingly.
Alternate second guide here on post #55 thanks to @flushell
https://forum.xda-developers.com/showpost.php?p=83534273&postcount=55

dladz said:
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods.
NOTE* This guide is intended for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
Hope this helps..
Click to expand...
Click to collapse
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though

pyry666 said:
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
Click to expand...
Click to collapse
Ok so by not specifying a slot you are flashing to both afaik
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.

dladz said:
Ok so by not specifying a slot you are flashing to both.
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
Also please don't quote the entire guide it makes reading threads awful, edit your post please.
Click to expand...
Click to collapse
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too

pyry666 said:
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
Click to expand...
Click to collapse
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?

dladz said:
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
Click to expand...
Click to collapse
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now

pyry666 said:
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
Click to expand...
Click to collapse
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway

dladz said:
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
Click to expand...
Click to collapse
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues

pyry666 said:
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
Click to expand...
Click to collapse
Or just follow the above guide if you meet the requirements
Command for swapping slot is
fastboot --set-active=a
Or b

Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Bootloader unlock works same no matter what model you are using. You can just boot twrp and flash magisk from there

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.

dladz said:
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
Click to expand...
Click to collapse
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So in order.
1 Download the full ROM for your device and region.
2 Open it in on a computer and extract the bin file called payload, it'll be about 2.4GB.
3 Then copy it to the payload dumper input folder and run the exe
4 You'll get the boot image as well as some other files, copy the boot image to your phone and patch it using magisk.
5 Then pull the output magisk patched.img to your adb folder and flash to slot A or B or both. I did both

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So how did it go?? All good?

dladz said:
So how did it go?? All good?
Click to expand...
Click to collapse
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!

I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file

A.Priori said:
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
Click to expand...
Click to collapse
Well done, always good to come back from the dead

N'ash said:
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
Click to expand...
Click to collapse
Yea that annoys me too.
There will be a way I'd imagine, but you wouldn't want to get that script wrong..
Might look into getting that gone, HTC had this too as do a few devices.
Possible a precious guide for an older device may work but using it to test would be a risk..

After doing this, is it still possible to install official OS builds from OnePlus whenever a new build comes out? Either via a zip or OTA?
For instance when 10.5.13.IN11BA comes out or whatever?

How to root a OnePlus 7T Pro with Magisk, For Noobs!

In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!

Thnx for the post , and confirming that this worked perfectly with OP7T PRO Android 11 official ROM

Do I assume correctly that I would wipe everything?
astroarchcraft said:
In this guide, ill be showing you how to root your device using Magisk. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Magisk Manager APK - https://magiskapp.com/apk/
Your phones current software boot.img! You can either get this from the vendors website, or if you are running a custom OS, you should already have the file.
*Ill be assuming you are familiar with cmd, fastboot commands, and that your bootloader is already unlocked, and you are running a custom recovery! For a guide on how to do the last two things, part of my last guide can help you - https://forum.xda-developers.com/t/how-to-install-android-12-derpfest-for-noobs.4385171/ *
Step 1: Download the magisk apk from the website and install it to your device. After this, copy over the boot.img file that is from your current rom into the downloads folder of your phone! Now, open up magisk manager, and press install beside the 'Magisk' Section on the home screen. Then press 'Select and Patch a FIle'. Now you can select the boot.img file and let Magisk do its thing.
Step 2: Once that process has been completed, you should have a file beginning with 'magisk_patched....img' in your downloads folder. Copy that file over to the platform tools folder in your computer. Now boot your phone into fastboot mode and connect it to your computer. Then on your computer, go to where you placed the magisk_patched file and in the search bar in file explorer type cmd. This should open a cmd window. Then type 'fastboot reboot fastboot' in order to enter your phone into fastbootd mode.
Step 3: Type 'fastboot flash boot 'PATH TO MAGISK_PATCHED FILE'
Let this run and once its done, reboot your phone.
Go to Magisk and Voila you should be rooted!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
Click to expand...
Click to collapse

Hello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?

powerfulnacho said:
roidHello, up to step 3 everything was fine. I let it run its thing, and reboot, BUT it became stuck in fastboot, forever. What can I do? I tried to wipe data and everything, but it's still stuck. Is there anything I can do?
Okay, so I manage to get my phone unbricked and is now running TWRP, which it was not before doing this. Am I correct to assume that doing all this without TWRP breaks the phone?
Click to expand...
Click to collapse
Same here, not work too.
For OxygenOS latest, in Android 12.
--- EDIT ---
Personally I install TWRP to do mostly backups, if needed.
But you have to use this twrp for Android 12 :
OnePlus 7T Android 12 TWRP?
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but...
forum.xda-developers.com
For the moment, after flash boot.img builded by Magisk is not work. But i dont try with this twrp. I dont now if this have a link...