Database Info

Root Infinix Zero 5 (X-603) (Systemless root Support OTA)

Systemless Root Magisk Beta 15.2 ( Thanks @topjohnwu for Magisk)
As it is systemless so it doesn’t change system file. It only changes in Boot image.
Whenever you got OTA just Reflash Stock Boot img and update your device to latest version.
This Boot.img is taken from latest version of XUI 3.0 Nougat version Build No. X603-H575A-N-IN-171227V175. So When it will update need to Patch again boot.img with updated version or this can also be used.
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Follow Step as Mentioned Below:
1. Unlock Boot loader as mentioned on following link:
https://forum.xda-developers.com/android/development/unlock-bootloader-infinix-zero-5-t3715360
2. If you want to install TWRP recovery then follow:
https://forum.xda-developers.com/android/development/infinix-zero-5-x-603-twrp-recovery-t3712491
Now the step for Systemless root with unlocked bootloader and usb debugging on is must. (with stock recovery no need TWRP)
1. Download the Zip file on following link: https://drive.google.com/open?id=1vne0IdPrW1isGoCJbYTCl4GRG5mh6QF5
2. Extract zip file in a folder.
3. Press and ctrl+Shift and right click on mouse.
4. Now press option open cmd window here, in window 10 it may be open powershall window here just select it.
5. In cmd window follow the following command.
A. adb reboot bootloader (phone will reboot and light blank dark screen)
B. fastboot devices (it will show your device if connected well)
C. fastboot flash boot patched_boot.img (it will flash new boot img in your phone.
D. fastboot reboot (will reboot your phone)
E. Install magisk manager app from XDA lab or from attached here in zip just extract it.
Your phone is rooted now with stock recovery.
OTA Update Support: Just follow above cmd again and at point C. just change flash cmd to stock boot. (fastboot flash Stock boot.img) then reboot and update your system OTA.
Thanks.
Last Updated on 05/01/2018

I can't install any module
/data/adb/xxx.img mount failed
Failed
Installation failed

{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }

{ ROOT } Twrp & Magisk Installation in Official Oreo { (N2G47H.7.12.29 (Android O) }
Needed Files :
1. Fastboot Rom
Http://bigota.d.miui.com/7.12.29/tissot_images_7.12.29_20171228.0000.00_8.0_c9a6ea979b.tgz
2. Platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
3.Twrp recovery
https://androidfilehost.com/?fid=962157660013069602
4.. Twrp Installer
http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
5. Magisk 15.2
http://www.stechguide.com/download-magisk-v15-2/
Flashing Guide:
Download all the needed files copy magisk zip file in your device.
1. Flash Fastboot rom using Mi flash tool. ( clean install recommended )
2. After flashing, complete setup and other setting.
( Note : Please Skip adding Finger print. if you are added by mistakenly kindly delete your finger print in settings. )
3. Enable oem unlocking & usb debugging in developor options.
4. Extract platform tool in your pc.
5. Paste the downloaded twrp recovery(3) & twrp installer(4) in platform tools folder.
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
9. Type following command in command window
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
10. reboot to recovery.
11. your internal storage is available in twrp now.
12. Flash Magish 15.2 ( strictly use this version )
13. Goto to reboot option in twrp and select your current slot a or b . ( twrp will showing your current slot )
14. reboot system and enjoy.
***** Sorry for my bad english ****

will try soon and will update you.
please let me know if after following this method are we able to install Magisk modules and does it work?

Yes.

Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.

ota updates
after root by this method ..how to install ota updates

navneet1 said:
after root by this method ..how to install ota updates
Click to expand...
Click to collapse
1. Download and flash stock rom (same version that you are currently on) using mi flashtool with save user data option.
2. Your device will be in the same condition (including apps, settings, data etc.) but unrooted.
3. You'll have an ota notification. Install it with normal procedure.
4. Follow the op from step 3.

Apoorv AR said:
Did not work at first. I had installed magisk using patched boot method. Installed twrp using given method. Device was booting into twrp after selecting reboot system. Decided to install magisk again. As I already had magisk installed, tried flashing uninstaller.zip and got an error saying stock boot image was found which means that magisk was uninstalled. Flashed magisk 15.2 and it worked. I was able to boot into system with twrp installed.
Moral : Flashing magisk is a necessary step even if you are already rooted with magisk.
Click to expand...
Click to collapse
Follow the steps with clean flashed rom.

Spk1690 said:
Follow the steps with clean flashed rom.
Click to expand...
Click to collapse
It worked when I flashed Magisk again without loosing any modules or anything.

get block at
adb sideload twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
the first file i downladed got different name and when i put this command they tell me
No such file or directory

@Spk1690 SO this file twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip only for show internal storage?
edit
After enter this command fastboot boot recovery-3.2.1-1.img my device boot into system, not twrp, how to solve?

Does this work on the January Oreo STABLE patch??

KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
upp

KalolParty said:
Does this work on the January Oreo STABLE patch??
Click to expand...
Click to collapse
I have tried , it works, but do it on your own risks

root
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?

Spk1690 said:
6. Boot your device to fastboot Mode and connect to pc.
7. Open Command Window ( shift + right click ) and enter the following commands
fastboot oem unlock
fastboot boot recovery-3.2.1-1.img
8. Your device will be booting to Twrp. In twrp select Advanced -----> Adb sideload.
Click to expand...
Click to collapse
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.

These files are old, a new ones have been released some time ago:
An updated ROM file:
http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
An updated recovery:
https://www.androidfilehost.com/?fid=818070582850498337
Updated TWRP installer:
(check the attachment section)
Updated Magisk 16.0:
(Check the attachment section)

realtebo said:
My A1 reboor into system, not into TWRP.
What am I doing wrong?
I've already done all previous steps, and device is unlocked now.
Click to expand...
Click to collapse
Have you selected the partition you've installed your recovery to?
Because if not, boot the TWRP .img again and switch the partitions.
Reboot afterwards.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
cregen said:
i have problem. When i try to root phone i get command:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-kitkat sideload method...
adb: pre-kitkat sideload connection failed: no devices/emulators found
what im doing wrong?
Click to expand...
Click to collapse
You might want to try this: https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
Check steps 7-10. Read the whole instructions even if they aren't for your ROM. (Skip the copying process and other LOS related stuff.)

I have a problem while flashing twrp on march patch after flashing twrp on both slots android will automatically degrade to February patch ? I'm fed up of trying things please anyone help me

Im new in mi a1, why we need to flash new rom before flash twrp? My rom position on latest update

[GUIDE] Install Magisk with proper support for OTA updates

Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* 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 could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Here's an alternative method to install Magisk that support OTA updates (copied from the Mi A1 forum and expanded )
You need a PC with Android platform tools (they exist also for MacOS and Linux). When using Windows, you should also install MiFlash tool to get the required drivers to recognize the device.
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options" (on Andoird 9 "About phone" is right at the top of the Settings app).​2. Go back to the previous page (i.e. Settings > System), where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).​3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen You can also use the command "adb reboot-bootloader" if you already connected the phone to the PC.​4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.​
Now you unlocked your phone's bootloader and can continue to the next section.
MAGISK INSTALLATION
5. Download and install on the smartphone the latest version of Magisk Manager's apk available.
You need the smartphone to be connected to the internet, because Magisk won't install and won't work properly without a connection.​
6. Now you can easily download an already patched boot.img from the following list and jump straight to point 10 of this guide, or you can continue to the next point and learn to patch yourself an original boot.img
If you choose the short way, be sure that you select the patched_boot.img with the same "Build number" currently installed on your phone (see point 1 of this guide), and don't flash the file directly on the phone memory, because Magisk will not work properly (do exactly what this guide says, and you will not find problems, hopefully).
For our convenience, extract the patched_boot.img file in the same directory where Android platform tools are located.
patched_boot 9.6.4.0 (2018 July update) - patched with Magisk 17.1
patched_boot 9.6.6.0 (2018 August update) - patched with Magisk 17.1
patched_boot 9.6.8.0 (2018 September update) - patched with Magisk 17.1
patched_boot 9.6.9.0 (2018 October update) - patched with Magisk 17.1
patched_boot 9.6.10.0 (2018 November 1st update) - patched with Magisk 17.1
patched_boot 9.6.11.0 (2018 November 2nd update) - patched with Magisk 17.1
patched_boot 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - patched with Magisk 18.0
patched_boot 10.0.3.0 (2019 January update) - patched with Magisk 18.0
In case you erroneously flash those patched files directly on the phone, flash back the original boot.img via fastboot and follow the guide:
original boot.img 9.6.4.0 (2018 July update) - taken from fastboot ROM
original boot.img 9.6.6.0 (2018 August update) - taken from OTA update
original boot.img 9.6.8.0 (2018 September update) - taken from OTA update
original boot.img 9.6.9.0 (2018 October update) - taken from OTA update
original boot.img 9.6.10.0 (2018 November 1st update) - taken from OTA update
original boot.img 9.6.11.0 (2018 November 2nd update) - taken from OTA update
original boot.img 10.0.2.0 (2018 December upgrade to Android 9.0 Pie) - taken from fastboot ROM
original boot.img 10.0.3.0 (2019 January update) - taken from fastboot ROM
7. You need the original boot.img to patch. You can find it inside the official fastboot ROM zip for daisy. Check that the downloaded ROM version is the same as the "Build number" currently installed on your phone (see point 1 of this guide). If the versions are different, update (or downgrade if possible) your phone to that version. You can also download original boot.img elsewhere (for example at the point 6 of this guide), but always pick the same "Build number" of your phone.
After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).​
8. Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you get on the point 7 of this guide.​
9. Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, inside the same folder where the Android platform tools are located, for our convenience.​
10. Reboot the phone in fastboot mode (as already explained in point 3 of this guide), open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
fastboot boot patched_boot.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.​
11. Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates". From now on, you should check manually if a new OTA update is available.​
Now the installation is finished, you can use Magisk Manager to install modules and manage root permissions.
HOW TO APPLY OTA UPDATES
UPDATE 9 February 2019 It seems that with the latest Magisk (v18.1) and Magisk Manager (v7.0.0) the following procedure is working fine again. I didn't test it personally, but some users gave positive feedback.
WARNING! January 2019 Since the arrival of Android 9 Pie, the OTA update with Magisk as described in the following section, doesn't seem to work anymore. It could work, but you could also get a bootloop with the risk of losing your data.
Before upgrading from Android 8 to 9, or doing an OTA update after Android 9 you should:
- backup your data;
- remove any lockscreen password or fingerprint;
- uninstall totally Magisk and reboot.
If after doing this you get a bootloop, you could try to manually flash the vanilla boot.img via fastboot on the current slot (the same version as the last installed OTA). If you managed to fix the bootloop you can then install Magisk anew, from step 5 of this guide.
If the phone wants your PIN or password to proceed after the OTA update or after fixing the bootloop, and your PINs or passwords doesn't work, then you could have to reset the phone (or erasing the data partition, that should be the same thing), losing all your data.
Last chance if everything fails, you can flash the latest fastboot ROM from the official Xiaomi site and the phone will be working again.
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.​
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.​
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".​
After the reboot you will have the updated Android version with Magisk already working.
Thanks to user @jashancheema for the Mi A1 guide and a bigger thanks to @topjohnwu for the OTA part and above all for developing Magisk.

TROUBLESHOOTING
WARNING: before attempting any of the following operations, you must disable any screen lock, PIN or password, because you risk to not get back your data (encryption issues). It is recommended to take a backup, too (as every time a custom modding is involved).
You can get errors when installing OTA updates if you didn't follow meticulously the guide.
Check this list to try to find where the problem lies:
- when a new version is found, the updater will check if all the partitions on the device are untouched. If there is a partition that has been modified, the OTA updater will not proceed with the installation;​- typically, the two partitions commonly modified by user modding are the boot partition (that's where Magisk and TWRP are installed) and the system partition (when you change a config file, add or remove a system app, etc.);​- a system partition modified only by using Magisk modules is effectively untouched, because Magisk register all changes to /system in a file in the /data partition and then trick Android to believe those changes are really applied to /system;​- boot partition instead is really modified, but if you install Magisk following this guide, Magisk will save a copy of the untouched boot partition, and restoring it before applying OTA update will make the update work.​
Now, if you didn't follow this guide to install Magisk and you installed it in other ways, Magisk could alert you that he cannot restore the original boot.img (the boot partition) when you try to apply the OTA update.
To fix this, you can flash directly the vanilla (original, unmodified, untouched) boot.img taken from the point 6 of this guide, using those commands:
Code:
fastboot getvar current-slot
fastboot flash boot_? boot.img
the first command will tell you what is the current slot in use (a or b), the second command will flash the original boot into the phone, but you have to change the "?" in the command with a or b (i.e. the current slot that the first command provided).
Remember that the boot.img file version must correspond to the Android build version currently running in your phone.
If the OTA update will still refuse to apply, probably you changed something directly in the /system partition (for example you changed something in the build.prop without using a Magisk module to do this).
In this case you have to flash the original system.img in the phone with those commands:
Code:
fastboot getvar current-slot
fastboot flash system_? system.img
and as before, the first command will tell you the right slot to use instead of the "?" in the second command.
Here you can find the system.img extracted from the OTA updates zip (along with every other .img file inside that):
9.6.6.0 (August 2018) OTA update dump as .img files
9.6.8.0 (September 2018) OTA update dump as .img files
9.6.9.0 (October 2018) OTA update dump as .img files
9.6.10.0 (November 2018) full fastboot ROM
9.6.11.0 (November 2018) OTA update dump as .img files
If you want to obtain the system.img by yourself, you can find it inside the fastboot images but usually they are not updated monthly like OTA updates. But you can extract the system.img directly from the OTA update zips found in this thread (as I did above with my dumps), using the Python scripts found here.
To make the Python scripts work in Debian/Ubuntu and derivatives, you have to download both "extract_android_ota_payload.py" and "update_metadata_pb2.py", give them execution property and then install the package "python-protobuf". After this you can give this command to unpack the payload.bin file (that you must extract from the OTA update zip):
Code:
./extract_android_ota_payload.py /path/to/payload.bin
This will extract in the current directory all the .img files inside payload.bin, including the system.img
I don't know how to proceed in Windows, probably you only need to install the latest Python2 release and the script will work.​
As the last resort, you can flash directly with MiFlash the latest fastboot image available (even if older than your current version). Use the "flash_all.bat" script but before take a backup of your data, because the phone will be fully reset.
If you don't want to take the risk of not doing a backup, use the script "flash_all_except_storage.bat" when flashing, so you will keep all your data, but be warned that sometimes you will not be able to access the data anymore, because of encryption problems.
Right after the flash, you can start following the guide from point 5 or 6.
It should not be a problem downgrading the build version via fastboot, as long as the Android main version remain the same (Oreo 8.1 at the moment).

Thx, nice work :good:

Thanks to the OP. Great post! Totally noob friendly guide. Nice work.

It should also work on mi a2, thanks!

Lione2 said:
It should also work on mi a2, thanks!
Click to expand...
Click to collapse
Sure, but you can't use the posted patched_boot.img, because they're designed for Mi A2 Lite (daisy) and not for Mi A2 (jasmine).
EDIT: I posted the patched and original boot files for Mi A2 jasmine in the second post. I don't know if I can make a thread in the Mi A2 forum section with an adapted copy of my guide, there are already two guides there (even if not polished like this) and I don't want to create more confusion with a third guide about the same argument...

i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?

krzygaj said:
i've installed magisk from previous guide - what steps should I take to apply OTA update? - 12 to 14?
Now magisk informs me that there is 17.1 version - how to update it?
Click to expand...
Click to collapse
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.

BubuXP said:
If you flashed directly the patched_boot.img via fastboot in both slots A and B as the other guide said previously, you must flash the original boot.img to both slots, then start the guide from point 10.
Click to expand...
Click to collapse
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?

krzygaj said:
I did as you wrote but still can't install August update - is there any log?
- extracted boot.img from rom: http://en.miui.com/download-354.html
- did fastboot flash boot_a boot.img and fastboot flash boot_b boot.img and rebooted
- next rebooted and did fastboot boot patched_boot.img with patched_boot 9.6.4.0 (July update) - patched with Magisk 17.1
later did steps in guide - but when i do system update it stops on first stage
Any ideas?
Click to expand...
Click to collapse
You tampered the system partition? Try flashing also the system.img in that case.
Another case could be that you made an OTA update from the June build to July: in this case the partitions on the other slot (probably only the boot partition) where lost when overwrited with fastboot (and cannot be restored, as we don't have any June build ROM or OTA).
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk, but I suggest after installing Magisk so you can test if the guide works fine).

BubuXP said:
If everything fails, do a full fastboot flash with MiFlash tool, but using the flash_all_except_storage.bat script, that should keep your data intact, restore all partitions (A and B) to stock versions and you can then apply OTA (before or after installing Magisk).
Click to expand...
Click to collapse
Thanks above worked :good:
Hope the next update will go smoothly

September?

When booting comes a warning message because of the unlocked boot loader. How can I disable this message?

PC295 said:
When booting comes a warning message because of the unlocked boot loader. How can I disable this message?
Click to expand...
Click to collapse
you can't turn that off with open bootloader

Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?

proton242 said:
Guys, after i have unlocked bootloader i cannot charge my phone when is off because he go on when I insert the plug, it's normal?
Click to expand...
Click to collapse
No

ConradB said:
No
Click to expand...
Click to collapse
ConradB you have some suggestion? Thank you

proton242 said:
ConradB you have some suggestion? Thank you
Click to expand...
Click to collapse
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.

BubuXP said:
Same problem on mine, I don't know if it's a ROM bug or it's caused by unlocked bootloader or Magisk.
The only solution at the moment is charging while the phone is switched on.
Click to expand...
Click to collapse
Ciao BubuXP, provando a rimuovere Magisk (lasciando il bootloader sbloccato) tutto torna alla normalità, cosa dici, crea casino quando patcha il boot.img?

[GUIDE][OP7][9.0/10.0/11.0] Unlock Bootloader | TWRP | Root with Magisk | Update

Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)​
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)​
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)​Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!

@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.

Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough

Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel

AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512

Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?

Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard

strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?

Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.

Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well

murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.

murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.

strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.

murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?

murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.

strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help

I believe the default file system is ext4, is there any benefits changing it to f2fs?

Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/

[Guide][Root Magisk Only][OTA Compatible] Moto G6 Play

* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.

Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!

gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.