Database Info

[GUIDE] A faster and updated guide to root, magisk and return to stock

#Prerequisites:
Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img
Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for custom roms, when you need to install GApps.
Magisk: https://github.com/topjohnwu/Magisk/releases/download/v19.0/Magisk-v19.0.zip
Magisk Manager: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.1/MagiskManager-v7.1.1.apk
DM Verity Disabler: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
Unlocked Bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal ADB/Fastboot (Windows only): https://androidfilehost.com/?fid=962187416754459552
Moto USB Drivers (drivers only, no manager): https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
Windows hint:
For all what you want to do with your Motorola phone, you need the above provided Minimal ADB/Fastboot environment.
Download and extract it,
Move the files you want to flash into the folder
Open CMD (Windows Key and R - then type cmd) and navigate into the extracted folder.
//It's easier when you type cd into the cmd and drag the folder from your adb/fastboot environment into the cmd window and hit enter.
And that's it. The patched boot image is no longer needed.
Rooting the Moto G6
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
5. Repeat the wiping and reboot another time into recovery.
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
7. Go to Install and flash dm-verity disabler first, then magisk.
Thats it. You're rooted.
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Wait until it finished, disconnect your phone, wait and set it up.
That's it.
Simple and easy.

So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.

madbat99 said:
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
Click to expand...
Click to collapse
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.

And for root not need boot.img file?

cecogor said:
And for root not need boot.img file?
Click to expand...
Click to collapse
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.

ThisIsRussia said:
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
Click to expand...
Click to collapse
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?

cecogor said:
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
Click to expand...
Click to collapse
Due to OS changes and it's a feature bundle.
It edits DM-Verity, ForceEncrypt and Disk Quota.

Can't get root
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.

mward7221 said:
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
Click to expand...
Click to collapse
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.

ThisIsRussia said:
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
Click to expand...
Click to collapse
I tried all that and couldn't get it to work, I downloaded everything from your links above but no go. Someone posted a no-verity boot image in another thread. post 598 I believe and I flashed that file, flashed Magisk 18.1 in twrp and now I have root so I'm set, Thanks for your reply

ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
Of course on Linux no drivers are needed. But most running Linux don't need instructions. It's usually windows users needing such instructions.
That's the only reason I chimed in.
Carry on.
Nice guide.

ThisIsRussia said:
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Click to expand...
Click to collapse
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR

kmssd said:
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Click to expand...
Click to collapse
If you Change major OS Version, you always need a clean Flash and rerooting.

ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
I would change official TWRP to Dejello's unofficial TWRP as official one won't install Gapps
https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn

Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
Click to expand...
Click to collapse
>> Here is ok,
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
Click to expand...
Click to collapse
>> Here is ok too
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
Click to expand...
Click to collapse
>> Here is ok too, similar to flash my Sony
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
Click to expand...
Click to collapse
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
5. Repeat the wiping and reboot another time into recovery.
Click to expand...
Click to collapse
>> The phone will be need a wipe two wipes? or only one?
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
Click to expand...
Click to collapse
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
7. Go to Install and flash dm-verity disabler first, then magisk.
Click to expand...
Click to collapse
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.

brunogroa said:
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
>> Here is ok,
>> Here is ok too
>> Here is ok too, similar to flash my Sony
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
>> The phone will be need a wipe two wipes? or only one?
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
Click to expand...
Click to collapse
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.

Stuck on Booting screen
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen

theseeker2654 said:
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Click to expand...
Click to collapse
Ohh sure... So need twrp to do, I Will trie this, thx a lots, here is the same with pie

Tom Swift said:
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
Click to expand...
Click to collapse
On top of using the disabler download and flash the no verity boot.img from the link below. Works great on my xt1925-6 with pie.
Also, use Magisk 19.0
https://drive.google.com/file/d/1JLMVRBCsMnr7RYxdRFjFLOwVSy8r8hSQ/view

The DM Verity Disabler link not working:
https://zackptg5.com/downloads/Disab...02.04.2019.zip

[Closed] Android 12 Update and Root ***Obsolete***

Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.

@V0latyle Can you help me out I installed a magisk module that caused a bootloop and I tried the adb wait-for-device shell magisk --remove-modules and it doesn't work for me I'm on the P5 a12 beta 5 I have since flashed the stock boot.img. What can I do to remove this module?

elong7681 said:
@V0latyle Can you help me out I installed a magisk module that caused a bootloop and I tried the adb wait-for-device shell magisk --remove-modules and it doesn't work for me I'm on the P5 a12 beta 5 I have since flashed the stock boot.img. What can I do to remove this module?
Click to expand...
Click to collapse
I'm honestly not that familiar with Magisk, sorry. I suggest you ask in the Magisk thread, they'll be of more help to you over there. Magisk modules live in /data, not /boot, so a data wipe would get rid of the module...and all your user data too.

V0latyle said:
I'm honestly not that familiar with Magisk, sorry. I suggest you ask in the Magisk thread, they'll be of more help to you over there. Magisk modules live in /data, not /boot, so a data wipe would get rid of the module...and all your user data too.
Click to expand...
Click to collapse
Ok thanks for your help I appreciate it

elong7681 said:
@V0latyle Can you help me out I installed a magisk module that caused a bootloop and I tried the adb wait-for-device shell magisk --remove-modules and it doesn't work for me I'm on the P5 a12 beta 5 I have since flashed the stock boot.img. What can I do to remove this module?
Click to expand...
Click to collapse
Wiki:
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Scroll down to read how to disable modules through Safe Mode
There is also a section how to manage modules from custom Recovery (if TWRP applies to your phone)

You seem to understand the issue with vmeta (and the associated data wipe). So I went from android 11 to android 12 beta without a wipe and although on andorid 11 i could flash my kernels, on android 12 i cannot without vmeta/wipe. I thought I read that it was because 12 was in beta. I plan to flash the factory image of 12 today, withotu doing a wipe of course. Will i be able to flash my custom kernles again?

How do we get in the download mode to install the OTA?
I do use adb reboot recovery
but every time, I got this.
E:\platform-tools>adb sideload E:\platform-tools\blueline-ota-sp1a.210812.015-cee465f5.zip
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
E:\platform-tools>adb sideload E:\platform-tools\blueline-ota-sp1a.210812.015-cee465f5.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found

ShadowJP88 said:
How do we get in the download mode to install the OTA?
I do use adb reboot recovery
but every time, I got this.
.....
Click to expand...
Click to collapse
Once you're in recovery, are you going into ADB sideload (hold the power button, then press the volume up key, then choose "Apply update from ADB")?

kfhughes said:
Once you're in recovery, are you going into ADB sideload (hold the power button, then press the volume up key, then choose "Apply update from ADB")?
Click to expand...
Click to collapse
I can't find out how... I only have the droid page with "no command" text

sorry i cant understand this:
* If, after flashing a patched boot image, you get the "unable to load/verify boot image", you probably didn't get the flags quite right. Just reflash vbmeta with the disable flags and that should fix the problem.
pixel 5 here, unlocked bootloader, did a clean flash, booted magisk , after direct install and restart i was stuck at booloader menu with that message, i don't understand what i have to do reading your post
where can i do this and how? Just reflash vbmeta with the disable flags
i had to clean flash again to use the phone

For re-flashing the vbmeta.img, my command has always been a little different than yours.
I use: fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
It's only a little different and your way might work, but if anyone has issues you could try this different command instead.

ShadowJP88 said:
I can't find out how... I only have the droid page with "no command" text
Click to expand...
Click to collapse
Hold down the power button and tap volume up to bring up the recovery menu.

V0latyle said:
With the Android 12 stable release just around the corner, I would like to make sure we have clear instructions on how to update with root.
These instructions work with the beta as well. This may seem redundant compared to other threads, but I wanted to consolidate the relevant information to one place.
WARNING: MANUALLY INSTALLING FACTORY UPDATES OR IMAGES REQUIRES AN UNLOCKED BOOTLOADER. If your bootloader is locked, DO NOT ATTEMPT THIS. You can, however, update using the OTA via ADB Sideload on a locked bootloader. DO NOT INSTALL THE BETA OTA WITH A LOCKED BOOTLOADER. BETA SOFTWARE IS EXPERIMENTAL AND MAY BE UNSTABLE, AND YOU MAY BE UNABLE TO RECOVER YOUR DEVICE IF SOMETHING GOES WRONG.
WARNING: MODIFY YOUR DEVICE AT YOUR OWN RISK. YOU ALONE WILL BE RESPONSIBLE FOR MALFUNCTION, DAMAGE, OR LOSS OF ANY KIND IF SOMETHING GOES WRONG.
Root will be done via Magisk. If you aren't already using it, download and install to your phone.
Warning: For the sake of simplicity, I frequently will use generalizations when referring to files ("[patched boot image]" instead of "magisk_patched-23001_xxxxx.img" for example). It is YOUR RESPONSIBILITY to ensure you are flashing the correct file. The easiest way to do this is type the command in the command line without the file itself, then drag and drop the file you want to flash into the command line window.
For those of you with a locked bootloader:
Simply install the update as usual via OTA, whether automatically through Android Update, or manually via adb sideload.
First, a bit of information on why you need to follow this guide (See this post)
Two new Verified Boot features implemented in Android 12 will interfere with attempts to root. A more detailed explanation is below if you would like.
Spoiler
Dm-verity (device-mapper-verity) is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.
Vbmeta verification is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.
This was implemented to prevent persistent rootkits by means of a hardware level security check, to prevent "potentially harmful applications" such as Magisk from evading detection, as such applications residing within the kernel will have higher privileges than the detection applications.
What this means is that with these two enabled, a modified boot image will cause a verification error when flashed to the device, preventing boot. Interestingly, this check is not performed against "live" boot images loaded via ADB, so with dm-verity and vbmeta verification enabled, a modified image can be booted as long as the image in /boot is intact.
To update to Android 12 with data intact and reroot:
WARNING: Per Google, an Android 12 OTA should only be installed on a device running 12 DP or 12 Beta. However, other users were able to manually install the OTA via ADB without losing data, so DO THIS AT YOUR OWN RISK! It is currently unknown what Google's official instructions will be for installing the update, so the "best" current method is wait for automatic OTA.
Spoiler
If you update via automatic OTA:
1. Download the factory image (Yes, this is required) to your computer. Connect your device via USB.
2. Extract the contents of the factory image, then extract both boot.img and vbmeta.img from the image-[device].zip (where [device] is the codename for your device, such as Redfin for Pixel 5
3. Continue to Reflash vbmeta below
To manually install the OTA:
1. Download the OTA for your device, as well as the factory image (Yes, you need both) to your computer.
2. Install the OTA
3. Extract the contents of the factory image, then extract both boot.img and vbmeta.img from the image-[device].zip (where [device] is the codename for your device, such as Redfin for Pixel 5
4. Let the update complete, including reboot. Wait until you are in /system with the update process finished (no update notification)
5. Continue to Reflash vbmeta below
Reflash VBmeta
1. With device connected via USB, Developer Options enabled and USB Debugging enabled, reboot to bootloader using ADB:
Code:
adb reboot bootloader
2. Reflash vbmeta with dm-verity and boot verification disabled:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Reboot to bootloader:
Code:
fastboot reboot bootloader
Continue to Patch Boot Image below.
To update to Android 12 using Android Flash Tool:
Spoiler
1. Open this link in Google Chrome (DO NOT USE MICROSOFT EDGE OR MOZILLA FIREFOX) Here is the link for beta
2. Connect your device via USB (make sure USB Debugging is enabled)
3. Enable ADB access in the browser
4. Select your device
5. Select the Android 12 build
6. IMPORTANT: Click the pencil icon next to the selected build
7. Ensure Wipe Device, Disable Verification, and Disable Verity are checked. DATA WIPE IS REQUIRED when updating from an older version of Android. Don't lock your bootloader if you want root. Force flash all partitions should not be necessary (but use this if you've run into problems and are starting over). Skip Secondary and Force Debuggable should be unchecked, unless you want to use ADB for root access on the stock kernel for some reason.
8. Click Install Build.
9. Wait until the update finishes.
10. Continue to Patch Boot Image below.
To update to Android 12 via ADB using the factory image:
Spoiler
1. Download the factory image to your computer and connect your device via USB, with USB debugging enabled.
2. Extract the contents of the factory ZIP
3. Reboot to bootloader:
Code:
adb reboot bootloader
4. If necessary, update the bootloader: WARNING: IF DONE INCORRECTLY THIS WILL BRICK YOUR DEVICE!
Code:
fastboot flash bootloader [bootloader image]
Reboot back to bootloader.
5. If necessary, update the radio:
Code:
fastboot flash radio [radio image]
Reboot to bootloader.
6. Install the update:
Code:
fastboot --disable-verity --disable-verification -w update [factory image zip]
DATA WIPE IS REQUIRED when updating from an older version of Android.
7. Let the update complete
8. Continue to Patch Boot Image below
Patch Boot Image:
Spoiler
1. Extract boot.img from the factory image ZIP if you haven't done so already
2. Install Magisk on your phone
3. Move the boot image to your phone via USB, and patch it using "Select and Patch a File" in Magisk
4. Move the patched boot image back to your PC
5. Reboot to bootloader
6. Flash the patched boot image:
Code:
fastboot flash boot [patched boot image]
7. Reboot to system.
For subsequent updates to Android 12:
Either install the update via OTA Sideload, then reflash vbmeta with disable flags set, or dirty flash the factory image with disable flags set.
Live boot your patched boot image from bootloader (as long as you're still on Android 12, the old kernel should work fine):
Code:
fastboot boot [patched boot image]
In system, launch Magisk then select "Direct Install" to patch the stock image in /boot.
Key reminders:
* The OTA does not have a way to set the disable flags for vbmeta, so if you update via OTA, you will have to reflash vbmeta with the disable flags every time you update.
* If you forget to do this and have a patched boot image, bootloader will return an error: "failed to load/verify boot image"
* The fastest and easiest way to update is via OTA, but remember you will lose root until you're able to reflash vbmeta and repatch the boot image.
* Manually patching the new boot image in Magisk via "Select and Patch a File" should be unnecessary every time you update. You can, instead, just keep the image you originally patched, boot it every time you update, and flash the stock image in /boot using Magisk.
* If, after flashing a patched boot image, you get the "unable to load/verify boot image", you probably didn't get the flags quite right. Just reflash vbmeta with the disable flags and that should fix the problem.
Click to expand...
Click to collapse
@V0latyle I think I know why some people are having issues with obtaining root or maintaining root on Android 12 official release... When you use the following command,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I think after this command and then flashing the patched magisk boot image their might be a check on both slots. Would I be wrong suggesting for the disable vbmeta command be this instead?
Code:
fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
I was having the same issue where it was saying that the system was corrupt and having to do a factory wipe after doing the command without --slot=all for the vbmeta disable flag command.

rester555 said:
@V0latyle I think I know why some people are having issues with obtaining root or maintaining root on Android 12 official release... When you use the following command,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I think after this command and then flashing the patched magisk boot image their might be a check on both slots. Would I be wrong suggesting for the disable vbmeta command be this instead?
Code:
fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
I was having the same issue where it was saying that the system was corrupt and having to do a factory wipe after doing the command without --slot=all for the vbmeta disable flag command.
Click to expand...
Click to collapse
I haven't read his full instructions hidden behind the spoiler tags, but in my experience after flashing the vbmeta.img the first time, I needed to follow it with "fastboot -w" and wipe my phone, then flash the patched boot.img.
On subsequent updates as long as I booted to bootloader immediately after flashing the OTA.zip to flash vbmeta, I didn't have to wipe. If I boot to system by mistake, I'll need to fastboot -w again

rester555 said:
@V0latyle I think I know why some people are having issues with obtaining root or maintaining root on Android 12 official release... When you use the following command,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I think after this command and then flashing the patched magisk boot image their might be a check on both slots. Would I be wrong suggesting for the disable vbmeta command be this instead?
Code:
fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
Click to expand...
Click to collapse
xunholyx said:
I haven't read his full instructions hidden behind the spoiler tags, but in my experience after flashing the vbmeta.img the first time, I needed to follow it with "fastboot -w" and wipe my phone, then flash the patched boot.img.
On subsequent updates as long as I booted to bootloader immediately after flashing the OTA.zip to flash vbmeta, I didn't have to wipe. If I boot to system by mistake, I'll need to fastboot -w again
Click to expand...
Click to collapse
@xunholyx I did what you suggested, flashing the vbmeta.img and then patching the magisk boot image and I got the corrupt system message in recovery. So I ended up reflashing stock image with wipe through adb.. did minimal initial setup, then reflashed the vbmeta.img to all slots and then immediately flashed the patched magisk image. That seemed to work for me to gain root on A12.

Did as you showed , and it works well .Thank!

4a 5G here (sorry, I know that this is the section for Pixel 5, but I assume most or all things are the same). I rushed and installed the OTA the normal way, thinking I'll be able to patch and flash boot.img afterwards (like normally). Update went fine (upgrading from 11, haven't used any of the DPs/betas), but after I flash the patched boot.img, I get "failed to load/verify boot images" in fastboot. Am I out of luck?

rester555 said:
@V0latyle I think I know why some people are having issues with obtaining root or maintaining root on Android 12 official release... When you use the following command,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I think after this command and then flashing the patched magisk boot image their might be a check on both slots. Would I be wrong suggesting for the disable vbmeta command be this instead?
Code:
fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img
I was having the same issue where it was saying that the system was corrupt and having to do a factory wipe after doing the command without --slot=all for the vbmeta disable flag command.
Click to expand...
Click to collapse
So are you saying that using the slot all flag fixed your problem?

killchain said:
4a 5G here (sorry, I know that this is the section for Pixel 5, but I assume most or all things are the same). I rushed and installed the OTA the normal way, thinking I'll be able to patch and flash boot.img afterwards (like normally). Update went fine (upgrading from 11, haven't used any of the DPs/betas), but after I flash the patched boot.img, I get "failed to load/verify boot images" in fastboot. Am I out of luck?
Click to expand...
Click to collapse
Did you follow the instructions on flashing vbmeta with the disable flags set?

Another 4a 5G owner here. I installed the OTA via recovery yesterday and tried to flash a patched boot.img, but got "failed to load/verify boot images". Reanimated the phone using a factory image, then tried to flash vbmeta.img with verification disabled (but no wipe) and patched boot.img. The phone couldn't boot into the system and offered to perform factory reset. I didn't want to wipe anything so I didn't go with it, but it seems like there is no way to root 4a 5G and keep your data (at least for now).
But I will be happy to be proven wrong!

Question Proper Rooting for OnePlus 9?

Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused

You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11

I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help

xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link

ROOT RMX2117 Realme Narzo 30 Pro

GSI flashing guide for mediatek uplaoded- checkout
Rooting Realme Narzo 30 Pro:
New Method (Android 10 and above)
Go to this link
Also checkout how to flash stock rom if you face any problems such as bootloop:
link
Old Method (Android 11 and below)
Prerequisite :
Unlocked Bootloader
How to unlock bootloader: Phone will be formatted
Backup your data.
Install deeptesting.apk
Open the app and click start applying
Wait for application to be summited and processed
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader
Connect phone to PC. Open platform-tools folder and type cmd in address bar
Type fastboot flashing unlock
Use volume and power button to select unlock the bootloader
Phone will format and reboot.
Realme Narzo 30 Pro (C.12) :
How to root ? Can cause bootloop or even brick your device
Download boot.img and vbmeta.img
Patch only the boot.img using this version of Magisk
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file
Now flash patched boot.image file
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file
Reboot your device with command : fastboot reboot
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.12) :
Recovery.img
For rooting older versions :
Follow the same procedure, using the files, boot.img and vbmeta.img for specific version.
Extras:
Scatter file :
MT6853 Scatter.txt

Please Share Boot.img Of C.09

Files required for C.09 have been uploaded please check

I think the end command is : fastboot reboot

Ignacius57294 said:
I think the end command is : fastboot reboot
Click to expand...
Click to collapse
Yup

NinjaChunks said:
Yup
Click to expand...
Click to collapse
Ohh nice man you corrected it...

NinjaChunks said:
Files required for C.09 have been uploaded please check
Click to expand...
Click to collapse
Please share files boot.img of c11

please share boot.img of c.11

KIRANKEJITON said:
please share boot.img of c.11
Click to expand...
Click to collapse
It will be posted soon

NinjaChunks said:
Realme Narzo 30 pro (C.011) :
How to unlock bootloader Phone will be formatted :
Backup your data.
Install deeptesting.apk.
Open the app and click start applying.
Wait for application to be summited and processed.
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader.
Connect phone to PC. Open platform-tools folder and type cmd in address bar.
Type fastboot flashing unlock.
Use volume and power button to select unlock the bootloader.
Phone will format and reboot.
How to root Can cause bootloop or even hardbrick your device :
Download boot.img and vbmeta.img.( Credit : ashkir05)
Patch only the boot.img using this version of Magisk other versions of Magisk doesn't seem to be working.
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file.
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file.
Now flash patched boot.image file.
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file.
Reboot command: fastboot reboot.
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.011) :
MT6853 Scatter.txt
Recovery.img
For rooting older versions :
Follow the same procedure, just use the files provided for specific version.
Realme Narzo 30 pro (C.09) :
Download boot.img and vbmeta.img.
Other Files (C.09) :
MT6853 Scatter.txt
Recovery.img
Realme Narzo 30 pro (C.08) :
Download boot.img and vbmeta.img.
Other Files (C.08) :
MT6853 Scatter.txt
Recovery.img
Click to expand...
Click to collapse
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help

rizwanp880 said:
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
Click to expand...
Click to collapse
Go to bootloader and flash stock boot.img
You would used other version of Magisk maybe

Bro how about realme 8 5g?

Please share img files for UI 3.0

It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock.

TOPDOG3518 said:
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock
Click to expand...
Click to collapse
Stock boot.img is required for ota. Flash stock boot image then update.
To root again, get the boot.img for the software version your phone is running on and patch with magisk. Flash the patched boot.img and voila you have rooted.

Glad that you did. Any idea about custom rom on Narzo 30 Pro? as Realme excluded this device in her Android 14 update.

I am using Realme 3.0. Any good way to root and unlock bootloader without getting bricked?

Oops! We broke the matrix. Someone call Neo!
getting this error while try to download any file

Question Anyone have Oxygen OS 2115_F20 Full rom or patched boot image?

Has the full rom been released yet?

arsalturtle891 said:
Has the full rom been released yet?
Click to expand...
Click to collapse
No, at least on Oxygen Updater. Are you on F20 and you want to root?

TheNewHEROBRINE said:
No, at least on Oxygen Updater. Are you on F20 and you want to root?
Click to expand...
Click to collapse
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being

arsalturtle891 said:
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
Click to expand...
Click to collapse
When you rooted did you do fastboot flash or fastboot boot and then direct install in Magisk app?

I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img

arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
Then you can't restore your original boot image from Magisk. You should only ever do fastboot boot and then use direct install in Magisk. Unfortunately the latest full rom available for your device is LE2115_11_F.17, so I think your only chance is that someone share a stock F18 boot image so that you can flash it and then update.

arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.

shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
Appreciate it!

shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
I'm not seeing the attachment

Here is the stock unrooted F.18 boot.img. Make sure to extract it first.

So I was able to remove root by first following the same commands I used to root in the first place with the boot image you provided. However, I cannot update to F20 using the system update. It keeps failing

Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.

shadabkiani said:
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
Click to expand...
Click to collapse
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?

arsalturtle891 said:
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
Click to expand...
Click to collapse
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?

shadabkiani said:
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
Click to expand...
Click to collapse
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"

arsalturtle891 said:
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
Click to expand...
Click to collapse
Why do you always "fastboot boot......" and then "fastboot flash boot...."?
Generally, fastboot boot.... will make you phone boot up the given image temporarily (whether it's a boot image or a bootable recovery image). Whereas, fastboot flash boot.... will permanently flash the given image. Normally, you only have to go with one of these methods depending on your task/goal.
Anyway, since you have flashed the stock unrooted boot.img and OTA is still failing, I suggest you just back up your personal data (photos, stuff) to PC or whatever, and then go with the MSM tool method. It will wipe all your data on phone, and revert your phone to OOS11 with locked bootloader. From there, you can take OTA updates all the way upto OOS13 F.20. This seems to be the simpler way to get out of your current predicament.

How to use MSM tool:
1. Download the package according to your device/variant, and extract it.
2. Power off your phone and keep it aside. DO NOT connect your phone to PC for now.
3. Run the MSM tool exe. It will take a couple of minutes to load.
4. Click on Target drop-down menu and choose O2 if you are on Global.
5. Click Start. It will go to Waiting for Device mode.
6. Now on your phone (which should already be powered off), press & hold both the vol+ and vol- buttons (NOT the power button) and connect the data cable from PC to your phone. Your phone's screen will still stay black and it will enter EDL mode.
7. The MSM tool will start flashing as soon as the connection is successful.
Note: You need to have OnePlus device drivers on PC.

I appreciate the support. Can you also provide me with the F20 boot image by any chance.

Sure. Stock unrooted F.20 boot.img attached. Make sure to unzip it.
By the way, if you have MSM tool, you can get your current boot.img from its readback feature. Super simple. Launch MSM tool. Press F8. Select the desired boot image (boot_a or boot_b). Enter the password as: oneplus. Click read. Power off phone, and get it into EDL mode by pressing holding vol- vol+ buttons then connecting data cable from PC. The desired boot.img will be dumped in C: drive.
Also, F.21 has just been released, so you better update to that. I haven't yet as I am currently on crDroid.
Anyway, F.20 boot has been attached.

Hello sir Can I get F.21 boot
vendor boot
dtbo
there're no FULL package out there for Global variant
Just only incremental update
How can I get that Full Image?
Or Should I extract it from India Variant Full Image F.21
will It work normally?