Database Develop

[GUIDE][Z2 FORCE XT1789-05] Bootloader/TWRP/Custom ROMs/Root/Dirty flashing/Unbrick

First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.

A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.

B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).

C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.

D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.

E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.

F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).

If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.

I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.

renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).

Great tutorial, but I did not get 4g in any of the roms, only 3g

Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).

Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G

So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again

shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.

41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?

shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.

41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect

shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.

41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration

Lenovo A7020a48/Vibe K5 note [LP/MM]ROOT 10000% Success

ROOT Vibe K5 Note LP or MM​
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device/software.
* Same statement for XDA.
*/
Finally I got the method to root Lenovo Vibe K5 Note/A7020a48. If you are the one who is tired of searching how to root your device then you are at right place
But before we get started here are the things that you need (only for marshmallow user, lollipop user need only 1 thing which is given in method section)
Requirements​
1. Your Device (of course)
2. Your Current Stock Rom's Firmware(You can easily get it in firmwarefile.com)
3. A Working PC (first check whether you can successfully connect your device to your pc or not)
4. ADB and Fastboot Tools
5. A working Brain
BONUS:-You can use this method to root any (5.1+) device (if it has general unlocking system, This method is supported by 95% devices).
Now It's Time To Rock
METHOD for Lollipop users​
Download and install kingroot, open it and follow the tutorial given in that app
METHOD for Marshmallow Users​
1. Make complete backup of your data, Everything except ext. storage of your device will be erased.
Now Follow the steps from 2 to 11 to unlock bootloader (you can skip it if you already unlocked it)
2. Go to your phone settings>About phone, tap on build no. 7 times and then go back you will see a new { } developer option just above the about phone option
3. Go to developer option and enable OEM unlocking and USB Debugging
4. Connect your device to your pc and install adb and fastboot tool system wide
5. Open command prompt or power shell
Note- Windows 10 users have to write .\ as prefix before every command.
6. Type
Code:
adb devices
You will see a prompt on device, just click on always allow this computer and press ok or allow whatever given there. You will see your a long set of random Numbers and letters after that if its written device then your phone is successfully connected to your pc.
7. After that type
Code:
adb reboot bootloader
Your phone will reboot into bootloader mode
8.Type
Code:
fastboot getvar all
There you see at last some lines which tells you about your bootloader status if you see Unlocked = no then your bootloader is locked and if it says Unlocked = yes then it is unlocked and if it is unlocked then you can stop here
Now for those who has a locked bootloader
9. Type
Code:
fastboot oem unlock
(In some devices which is shipped with android 6.0 or higher you may have to write fastboot flash unlock don't write this command for your Vibe K5 note/A7020a48)
10. Most Important step Type
Code:
fastboot format userdata
. If you skip this you may get bootloop (I skipped that and got bootloop)
11. Type again
Code:
fastboot getvar all
Now you will see Unlocked=yes and Congrats!!! you has unlocked your phone's bootloader
12. Disconnect your device and press and hold power button until it reboots
Now follow the steps to root your device
13. Now from your stock firmware file extract boot.img which is given in the folder named firmware and copy it any where in your device
14. Install magisk manager from here -> Official website
15. After opening the app you'll see it is written that Magisk not installed click on the install button and select patch boot.img option,
16. Now select your boot.img file which you have extracted from your firmware file. After selection it will start to patch that boot.img and store patched_boot.img file in download folder of your device internal storage, copy that file at any folder in your pc (not in desktop)
17. Now go to the folder where you copied that patched_boot.img file and press right click on your mouse while holding shift button of your keyboard (Shift + Right click in simple words) and you will see an additional option of open command window/powershell here click on that and connect your device with your pc.
18. Before getting started with commands follow step 2 and 3 again
19. Repeat step 6 and 7
20. After going into bootloader mode Type
Code:
fastboot flash boot patched_boot.img
(in this code boot is partition and patched_boot.img is file name which you are going to flash).
21. Disconnect your phone ,press and hold powerkey until it reboots
Congrats Device ROOTED!!!​

#reserved

But there's a much simpler method to get root access with a single click. i cant able to attach photos.

did not work
Shubham1815 said:
#reserved
Click to expand...
Click to collapse
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help

Tried but not work for MM. The bootloader cannot be unlocked. Maybe your bootloader is different from the others, would you share it out?

mihir999 said:
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help
Click to expand...
Click to collapse
Do you enabled allow oem unlocking?

Shubham1815 said:
Do you enabled allow oem unlocking?
Click to expand...
Click to collapse
I enabled oem unlocking but still it shows "unlock not allowed"

Does this really works?? I want to try it

Did you actually unlock bootloader and root the device ? As far I know, in all other threads, none has confirmed any method.

After "fastboot getvar all" command, nothing happens. (PC => waiting for device.. PHONE => stuck at "Fastbood Mode"text)
Same for "fastboot oem unlock" command
I really want to permanent root for => LENOVO K5 NOTE (a7020a48). Years gone but no luck !
If your method is true then please answer us :crying:

Got stuck at "Unsupportive project for unlock" on my vibe K5note. Any help here please?

so . for those who are stuck at fast boot try and install the driver from this link :
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
this didn't work for me and i had to download and install "rescue and smart assistant" from the lenovo website
Rescue and Smart Assistant (RSA) - Lenovo Support AU
support.lenovo.com
once downloaded and installed , i could update the "Android" driver from device manager --> selecting the moto interface (not the composite one) instead the google one ( step by step : youtube.com/watch?v=nQjg6ePnGAc )
Once that's done , reboot to fastboot via adb
Now when I type fastboot devices I can finally see my device
however... i was getting " (bootloader) Unsupportive project for unlock "
no luck . . .
Edit:
if you however do have an OTG cable maybe try this method :
GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
Unlock Bootloader of any Device using PC or Android. - GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
github.com
good luck

any luck guys!?!?! or should i completey give up )

Root instructions

1/ WARNING: Unlocking the Bootloader WILL PERFORM A FACTORY RESET on your phone. Please backup your data BEFORE PROCEED.
2/ Should you run into any issues, please post here
Here is the good stuff. The rooting process is divided into 2 parts: Bootloader unlock and Rooting itself.
Before you begin, please download the Following
1) Download platform-tools on your computer here 11
2) Optional for Windows PC: MTK VCOM USB drivers here 5 (the default Windows driver works sometimes but not always. If the default driver doesn’t work for you, install this one)
3) Download factory-prepared patched stock BOOT.IMG here (this is patched to Magisk 20.4)
Bootloader Unlock
- Goto Teracube's Developer Options (via Settings/System/About and tap Build number several times to unlock Developer Options if this is not already available)
- Goto Settings > System > Developer settings
- Turn on OEM unlocking
- Shutdown the phone
- Press Vol+ and Power buttons simultaneously for 5/6 seconds
- You’ll see 3 options in tiny fonts. Use Vol+ to toggle option
- Select Fastboot and press Vol- to select it
- Connect Teracube to your PC/computer using the USB-C cable came with the package.
- Using platform-tools on your computer run the command
fastboot flashing unlock
Click to expand...
Click to collapse
- A confirmation message will be displayed on the screen, press Vol+ to say accept
- Bootloader is now unlocked. You will see some messages during the boot sequence each time you boot/reboot your phone. This is an expected behavior.
- Do not reboot or shutdown phone yet if you plan to continue with the root process (see below)
Root
- Perform Bootloader unlock steps (as above). Otherwise, the phone will complain of verification and will not allow you to proceed
- Connect Teracube to your PC/computer using the USB-C cable came with the package.
- Use platform-tools on your computer and run the command to flash the patched bootloader to your phone (your BOOT.IMG filename may vary)
fastboot flash boot teracube_patched_boot_sw1_magisk_20.4.img
Click to expand...
Click to collapse
- Run the following command to complete reboot your phone and complete the process
fastboot reboot
Click to expand...
Click to collapse
That’s it. Your Teracube should be rooted.
Install Magisk manager from github to check and use root.

Thank! Very useful post!

Hi, where can i find platform-tools for Ubuntu 18.04 ?
Thanks

How To Guide [GUIDE] [Magisk] [Unlock / ROOT / Keep Root]

Magisk VariantStable / Beta / CanaryReleaseOfficialAndroid / OOSOOS 11 and aboveMaintainertopjohnwuProject LinkGitHubZygiskNoDenyListNoMagiskHideYesModules RepoYesDownload LinkGitHub
This tutorial will :
provide you with all the steps to root your Oneplus 10 Pro (with your bootloader already unlocked)
provide you with all the steps to unlock your Oneplus 10 Pro bootloader
provide you with all the steps to keep root during/after an OTA (system update)
provide you with a lot tricks if you have troubleshooting questions
provide you with a lot of solutions of you have softbricked your Oneplus 10 Pro
provide you with all the ways if you want to bring back your Oneplus 10 Pro to unroot & lock back the bootloader
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it.
Root your Oneplus 10 Pro (with Bootloader already unlocked)​Step 1 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
{
"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"
}
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
By booting with the patched image, you now have temporary root access. To make it permanent open Magisk app.
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 2 - Reboot and your device is now rooted !​Unlock the Bootloader and Root the OnePlus 10 Pro​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot oem unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Step 3 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
Step 4 - Install magisk​Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 5 - Reboot and your device is now rooted !​Keep Root and OTA updates​How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 10 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​
Troubleshooting questions :​Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
If you can't install/update Netflix install the latest Netflix from apkmirror manually (like any other apk file)
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Clear cache from Recovery​Reboot into Recovery and select wipe CACHE. Recovery boot to be activated from Settings/System/developpers options/advanced restart. Once in Recovery select WIPE & WIPE CACHE Only !
Step 4 - Safetynet Fix​Install Safetynet Fix Magisk Module
Phone Bricked ? :​Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original boot.img​If your device can go to fastboot mode:
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 4 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 5 - Wipe data in Recovery mode or fastboot command​Option A : If your device can still go to Recovery mode (ie thru fastboot mode: "fastboot reboot recovery")
From Recovery Wipe data and reboot
Option B :
Code once in fastboot mode:
"fastboot- w"
Option 6 - MSM​If none of the above works then go for MSM tool
Option 1 to 4 would normally not alter your personal data, applications and own set-up
Option 5 & 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​​Option 1 : Original Boot & relock with fastboot command​Step 1 - Restore orignal boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: "fastboot oem lock"
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Option 2 : MSM Tool ​MSM tool will relock your boaloader !​Option 1 & 2 will wipe your personal data and applications
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
Attachments​
OnePlus-8T-Rooting-fastboot-devices-command.jpg
15.9 KB · Views: 1,964
OnePlus-8T-Install-OTA-After-Rooting.jpg
62.9 KB · Views: 2,086

Decent.
Tbh though, looks like you just added pics to my one.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Even the categories look the same.
FYI, there is no MSM tool for the 10

dladz said:
Decent.
Tbh though, looks like you just added pics to my one.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
Even the categories look the same.
FYI, there is no MSM tool for the 10
Click to expand...
Click to collapse
No MSM yet...

Steve0007 said:
No MSM yet...
Click to expand...
Click to collapse
No mate, fastboot enhance only, which has been hit and miss for most.
I haven't had to use it yet but seemingly it's the only option.
Hope things change but nothing yet

has old outdated info. If you flash, then you can't take ota updates.

Sorry, where is the magisk_boot.img file? I could not find it in this post.

Viewerisland said:
Sorry, where is the magisk_boot.img file? I could not find it in this post.
Click to expand...
Click to collapse
Please refer to this link. I personally used this approach with no issues
click me

use these steps to Unlock the bootloader... https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
after running through this post.. i would advise caution proceeding with the steps outlined ...
for OnePlus 10 Pro NE2213 & Ne 2215 ... you boot into Bootloader (adb reboot bootloader) and use ' fastboot flashing unlock ' to unlock the bootloader... NOT 'fastboot OEM unlock'
for my OnePlus 8T i would use 'fastboot oemunlock' ... not for the OnePlus10Pro

Steve0007 said:
Magisk VariantStable / Beta / CanaryReleaseOfficialAndroid / OOSOOS 11 and aboveMaintainertopjohnwuProject LinkGitHubZygiskNoDenyListNoMagiskHideYesModules RepoYesDownload LinkGitHub
This tutorial will :
provide you with all the steps to root your Oneplus 10 Pro (with your bootloader already unlocked)
provide you with all the steps to unlock your Oneplus 10 Pro bootloader
provide you with all the steps to keep root during/after an OTA (system update)
provide you with a lot tricks if you have troubleshooting questions
provide you with a lot of solutions of you have softbricked your Oneplus 10 Pro
provide you with all the ways if you want to bring back your Oneplus 10 Pro to unroot & lock back the bootloader
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it.
Root your Oneplus 10 Pro (with Bootloader already unlocked)​Step 1 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
By booting with the patched image, you now have temporary root access. To make it permanent open Magisk app.
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 2 - Reboot and your device is now rooted !​Unlock the Bootloader and Root the OnePlus 10 Pro​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot oem unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Step 3 - Booting temporarily root​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 10 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot boot magisk_boot.img" (use the "magisk_boot.img" from the above zip file)
Change to the exact name "magisk_boot.img" of the boot that has been patched in the above zip file
"fastboot reboot"
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
Step 4 - Install magisk​Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.
b. Use Direct Install (Recommended) to root your internal boot.img
Step 5 - Reboot and your device is now rooted !​Keep Root and OTA updates​How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 10 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​
Troubleshooting questions :​Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
If you can't install/update Netflix install the latest Netflix from apkmirror manually (like any other apk file)
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Clear cache from Recovery​Reboot into Recovery and select wipe CACHE. Recovery boot to be activated from Settings/System/developpers options/advanced restart. Once in Recovery select WIPE & WIPE CACHE Only !
Step 4 - Safetynet Fix​Install Safetynet Fix Magisk Module
Phone Bricked ? :​Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original boot.img​If your device can go to fastboot mode:
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 4 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 5 - Wipe data in Recovery mode or fastboot command​Option A : If your device can still go to Recovery mode (ie thru fastboot mode: "fastboot reboot recovery")
From Recovery Wipe data and reboot
Option B :
Code once in fastboot mode:
"fastboot- w"
Option 6 - MSM​If none of the above works then go for MSM tool
Option 1 to 4 would normally not alter your personal data, applications and own set-up
Option 5 & 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​​Option 1 : Original Boot & relock with fastboot command​Step 1 - Restore orignal boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)
Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: "fastboot oem lock"
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Option 2 : MSM Tool ​MSM tool will relock your boaloader !​Option 1 & 2 will wipe your personal data and applications
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.
Attachments​
OnePlus-8T-Rooting-fastboot-devices-command.jpg
15.9 KB · Views: 1,964
OnePlus-8T-Install-OTA-After-Rooting.jpg
62.9 KB · Views: 2,086
Click to expand...
Click to collapse
I have read all text, i cant see if this are only for PC or if i can use whit Mac computer.
Do you know somethinhg about that?

lordxcom said:
use these steps to Unlock the bootloader... https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
after running through this post.. i would advise caution proceeding with the steps outlined ...
for OnePlus 10 Pro NE2213 & Ne 2215 ... you boot into Bootloader (adb reboot bootloader) and use ' fastboot flashing unlock ' to unlock the bootloader... NOT 'fastboot OEM unlock'
for my OnePlus 8T i would use 'fastboot oemunlock' ... not for the OnePlus10Pro
Click to expand...
Click to collapse
It would be great if somehow this (and other) corrections (such as where is the ZIP file that is referenced but not linked) were added to the instructions above. I spent an hour trying to figure out why "fastboot oem unlock" didn't work.

okay, tried updating my phone w/the steps mentioned above w/o, unfortunately disabling my Magisk modules
ended up in Qualcomm Crashdump mode...
I was able to restore back to slot a w/the following command:
fastboot --set-active=a
then used fastboot mode to boot to the following boot image (from this thread: https://forum.xda-developers.com/t/ne2215_11_c22-update.4524469/)
fastboot boot NE2215-C.22_boot_magisk25.2.img
this got me back up & running but I'm still stuck on C21
My question is, how do i upgrade to C22 now w/o losing data/root?

Question How to unlock bootloader and make root?

How to unlock bootloader and make root?
Would you help me?

To unlock the bootloader you must go to the official Motorola website and request a bootloader unlock, it will ask for your IMEI and give you a code and detailed instructions on how to unlock it. For this you will need ADB and Fastboot, you can use the official platform tools by Google or Minimal ADB and Fastboot install that you can find online. After unlocking the bootloader, find your exact device ROM somewhere online, download it and extract the boot.img file, which you will transfer to your phone. After you've done that, install the Magisk app, and inside Magisk you will see at the top a button to install root to your phone, choose the option to patch a .img file (this file will appear in your downloads), extract said file to your PC somewhere other than the C: drive (I usually get errors when it's in the C: drive), boot your phone into fastboot and "fastboot flash boot <drag your file onto the cmd window and it will automatically complete>" then press enter. These are the basics, you must learn your way around rooting otherwise you won't ever be able to do it. Learn about ADB and Fastboot commands, learn about Magisk, and learn about how the ROM is segmented into different files. If it all fails, download the Motorola RSA tool, connect your phone to your PC on Fastboot mode and start the rescue process (it shouldn't ask for your IMEI at this stage, but if it does, the IMEI is printed on the SIM card tray).