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

Question Rooting - anyone successful?

I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com

Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks

I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.

sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .

dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.

dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance

Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.

I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)

chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).

Android 11 Stock ROM for Moto G9 Plus and root with Magisk (Odessa - XT2087-1)

This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!

Gg I'll try it tomorrow

UsmanQ said:
Gg I'll try it tomorrow
Click to expand...
Click to collapse
Great! Tell me about your experience with this rom or if something goes wrong!

Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.

oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.
Click to expand...
Click to collapse
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.

christjeam said:
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.
Click to expand...
Click to collapse
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious

oscararm10 said:
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious
Click to expand...
Click to collapse
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!

christjeam said:
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!
Click to expand...
Click to collapse
Super, I will fit certain apps with the full screen option. Thanks

lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.

Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
You don't want to use the same bat file without checking the flash_file.xml commands can change with updates.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.
(Moto g9 plus Odessa xt2087-2)
Click to expand...
Click to collapse

Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
Wow, that's weird, but I see that you could solve it and that makes me happy, enjoy your Android 11!

christjeam said:
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
Click to expand...
Click to collapse
This link, don't work dude! :-(

ice.modding said:
This link, don't work dude! :-(
Click to expand...
Click to collapse
Use this: https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037

hi, what stock roms and other roms do i download? or do i just download them all?

Godfather096 said:
hi, what stock roms and other roms do i download? or do i just download them all?
Click to expand...
Click to collapse
You only download one, let it be one that aligns with your country and smartphone model

Stock rom links are broken please update

adamtarek said:
Stock rom links are broken please update
Click to expand...
Click to collapse
Links are still active, check your connection!

christjeam said:
This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!
Click to expand...
Click to collapse
I tried to use that method since I found it in a youtube video but when I used the patched boot.img file the system took too long to start and when I finished loading the device the touch didn't work, and it didn't matter if I repeated the command "fastboot flash boot" with the original boot.img file of the rom since it kept starting but at the same time the touch did not work.
(the boot.img file that I use was extracted from the "Rescue and smart assistant" program).

How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet

WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

Thanks! Awesome write-up/explanation.

Now THIS is a useful thread! Thanks
I might try to root my P6P this week-end.
If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)
"6. Reflash vbmeta to disable boot verification"

Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img

Ghisy said:
Now THIS is a useful thread! Thanks
I might try to root my P6P this week-end.
If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)
"6. Reflash vbmeta to disable boot verification"
Click to expand...
Click to collapse
Yes. You're basically on a clean factory flash. It might still throw a "corrupted" error at you but a factory reset fixes it.
Cares said:
Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img
Click to expand...
Click to collapse
Not really; I prefer to do that after OTA because OTA is an out of band update that installs to the inactive slot. You don't really have to use the slot commands at all, but I've come into the habit of using them.

The steps for a rooted update via OTA worked perfectly for me! Thank you a tonne for the guide. I was thinking I would have to factory reset for every monthly update, glad we dodged that bullet!
Thanks again.

Is there any way to go back to DM Verity + AVB enabled without wiping after this?

Bandsalat said:
Is there any way to go back to DM Verity + AVB enabled without wiping after this?
Click to expand...
Click to collapse
See @V0latyle's more informed answer below.

Thank you for your time. This thread should be sticky

Bandsalat said:
Is there any way to go back to DM Verity + AVB enabled without wiping after this?
Click to expand...
Click to collapse
Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.

@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​

For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?
Someone needs to make a batch file for the above.

xpdragon said:
@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​
Click to expand...
Click to collapse
Nope, no downside that I'm aware of; many people used the factory images for updates on Android 11 and prior without any problems. Just make sure you flash it with --disable-verification --disable-verity
mkhcb said:
For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?
Someone needs to make a batch file for the above.
Click to expand...
Click to collapse
I think you're confusing Android Flash Tool with something else. Take a look at the link - you connect your phone via USB and can install firmware direct from Google. There is no option to substitute your own files, which is a good thing.
As for adding the boot image to the flash process...I would avoid this, personally. You CAN edit the flash-all.bat to do this and some members here have. But, P6 and P6 Pro users have run into problems using a boot image they patched prior to updating, so here is my recommendation:
Flash the factory image with verity and verification disabled, and let the update complete including a boot to system. Once in system, you can then patch the boot image, reboot to bootloader, and flash it to /boot.

> Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.
Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.

Bandsalat said:
Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.
Click to expand...
Click to collapse
Tried what, exactly? It's easier to help if you're more specific about what you did and what result you're getting. Is there a message at the bottom of the bootloader screen?

I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Are they equivalent i.e., does the order matter?

biTToe said:
I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Are they equivalent i.e., does the order matter?
Click to expand...
Click to collapse
No, the order doesn't matter; yes, they're equivalent.

roirraW edor ehT said:
No, the order doesn't matter; yes, they're equivalent.
Click to expand...
Click to collapse
The way I like to think of it is like this:
[Application: Fastboot/adb] [Command: What you want to do] [Destination: Where you want it to be done] [Modifiers: How you want it to be done] [Payload: What you want to be put there]
Those of us who grew up with DOS would probably do it like this:
Code:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
But I believe it could also be done like this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

V0latyle said:
Those of us who grew up with DOS would probably do it like this:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Click to expand...
Click to collapse
I'm the old DOS guy. THIS makes sense

biTToe said:
I'm the old DOS guy. THIS makes sense
Click to expand...
Click to collapse
Right? Imagine feeling old because you were born prior to 1990

Bootloader problems

Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone

You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.

Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks

chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.

Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.

If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion

type fastboot devices and show me the result.
maybe you do not have correct fastboot driver

It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable

Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice