Develop Bugs

Can't root through SuperSU or Magisk on open beta 25 (android O)?

I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?

Not yet. Did this really require a thread of its own ?

skymera said:
Not yet. Did this really require a thread of its own ?
Click to expand...
Click to collapse
I just want to know how much will take so that it will be available.

rsm23 said:
I just want to know how much will take so that it will be available.
Click to expand...
Click to collapse
Nobody here can see in the future...

https://forum.xda-developers.com/showpost.php?p=74161852&postcount=3634
here try this Good Luck !

On my phone SuperSU 2.82 SR5 works fine. On other phones not, or SR3 woks....
Magisk 1.4 or 1.42 beta not working. I did not get boot loops, but not working.

rsm23 said:
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Click to expand...
Click to collapse
Follow this guide brother

Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
How did you achieve this?

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
This is a good news. Cannot wait for more details!

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?

ashokmor007 said:
Follow this guide brother
Click to expand...
Click to collapse
Thanks, but I don't like SuperSU
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
mr.charlie said:
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
Click to expand...
Click to collapse
Thanks, but too much of a hassle for me right now.
I think I'll just wait for an official Magisk update to be released, at this point

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
! We are looking forward to your description: how to take the steps? !

papzi57 said:
! We are looking forward to your description: how to take the steps? !
Click to expand...
Click to collapse
Be carefully, you can lose you data!!! For me all work fine)))
1.Flash Oreo via trwp
2.Downgarde bootloader for DM-Verity
3. Flash Magisk via twrp
4. Turn off the phone manualy
5.Turn on & boot in twrp
6.Do the backup of boot
7.And edit boot.win in hex editor on pc
Code:
androidboot.selinux=permissive
screen in attachment
8.And flash boot back, reboot.
P.S When you set selinux permissive via fastboot you'll have freeze (braking) in system - i don't know how it say

baskaflyfer said:
edit boot.win in hex editor
Click to expand...
Click to collapse
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK

Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Sent from my Pixel 2XL using XDA-Developers Legacy app

papzi57 said:
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Click to expand...
Click to collapse
I am not able to tell you how safe this method is.
Yes, i did a dirty flash of OOS Open Beta 25, but some apps lost their data (Jodel, photoTAN, ...) but not Google Authenticator :fingers-crossed:
I think the modification of the boot.img is device-specific. I can not tell you details about this because i don't know that either.
There might be another way to set selinux=permissive as recently described in this thread, but your bootloader need to allow the following command:
Code:
fastboot oem selinux permissive
If you are able to perform this command in fastboot mode, maybe you don't need to modify the boot.img manually. Just reboot to fastboot mode after the installation of Magisk in TWRP and type that command.

davidlueder said:
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Click to expand...
Click to collapse
Is Magisk stable? Did you try any modules and which ones? Are they working fine?

ishanp said:
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
Click to expand...
Click to collapse
I did not try any modules but multiple apps that require root: AirDroid, AFWall+, Amaze (Root enabled). They're working fine.
Additionally, this magically fixed my ctsProfile. Magisk's SafetyNet-Test is successful on my device now.
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.

davidlueder said:
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
Click to expand...
Click to collapse
Try in terminal after boot:
Code:
su
setenforce 0
Restart ViperFX app. Please report, I am on SuperSU but will jump the moment my fav modules start working
Also I'm using Viper4Arise (bundled with Magnum Opus) right now. If that didn't work you can use that.

My complete bootloader unlock and root guide.

So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted.
I want to thank everyone who made different threads about rooting and installing Magisk on this phone, i have read so many guides now so i cant remember their names!.
BUT THANK YOU!.
Let's get to it
Here is what I did for to unlock the bootloader, install magisk and root my Huawei P20 Lite ANE-LX1
First you need to install HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
and then install ADB and Fastboot drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
(extract the platform-tools folder to the root of your C: drive)
Plug in your phone and let it install drivers.
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
I used "Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.146(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX androidhost.ru.zip" (https://androidhost.ru/6ti)
When finished downloading, open the zip file, open software and copy the folder "Dload" to the root of your EXTERNAL SD CARD, not internal storage!.
Now take your phone and "dial" *#*#2846579#*#* go to Software Upgrade -> SdCard Upgrade and click OK.
Your phone should now begin installing the old firmware, when the phone first boots up, dont set it up, turn it off and hold Volume up + Power and select Wipe Data/Factory Reset, Wipe Cache, and then reboot.
With the phone booted, enable USB Debugging (Settings > System > About Phone > version number > Tap it 7 times to become developer, AND click OEM-Unlock, then go to Settings > System > Developer Options > USB Debugging).
Now we need to buy 4 credits from DC-Unlocker (4 Euro) ( https://www.dc-unlocker.com/buy ) when you have 4 credits on your account, go and download https://hcu-client.com/download/hcu-client-v1-0-0-0287/ Password: hcu
extract the contents of the zip to a folder called HCU in the root of your C: drive
Open up HCU.exe, type in your username and password (check your mail, the info will be there).
Grab your phone and dial *#*#2846579#*#*, go to Background Settings -> USB Port Settings -> Manufacture Mode and press close.
Plug in your phone and let it install drivers.
Open up HCU client, select Unlock, and then Read Bootloader Code.
when you have the code, save it!
Turn off your phone
Hold volume down and power, now we are in fastboot mode.
Open CMD and write:
CD C:\platform-tools
fastboot oem unlock YOUR UNLOCK KEY HERE
Accept the stuff and unlock your bootloader, your phone will be factory reset, and all your data lost if you dont have a backup.
Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)
Now re-enable USB Debugging option in Developer Options.
install Magisk Manager (https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip)
Download patched_ramdisk.img (https://mega.nz/#!GWp1ia6R!xUcg_T_17v1ktlFQPq-Ujo4DRKfAg8E4-_k2J2zLO60)
and place it in the root of your phones internal storage
Open up Magisk Manager, press install -> install -> Patch Boot Image File -> find the patched_ramdisk.img and click OK.
Now open CMD and write:
CD C:\platform-tools>
adb pull /storage/emulated/0/download/patched_boot.img
Now you should have the patched_boot.img in your platform tools folder.
Turn off your phone, hold volume down and power to get to fastboot mode.
in CMD write:
CD C:\platform-tools>
fastboot flash ramdisk patched_boot.img
reboot your phone and check if magisk was installed correctly and check if you have root.
Hope this works for you!

Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time

Thank you for this, but I have a question about this part:
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
Click to expand...
Click to collapse
Mine is ANE-LX3, what would be the equivalent to 146 so that DC-unlocker can read it?

Yes, you just need to find a firmware for LX3, i dont think flashing a 64gb firmware on a 32gb device is smart.

dcduartee said:
Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time
Click to expand...
Click to collapse
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.

Where could i find the correct firmware of ANE-LX1

Just use the address bar
brugernavn said:
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.
Click to expand...
Click to collapse
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/

LLoTE said:
Where could i find the correct firmware of ANE-LX1
Click to expand...
Click to collapse
Use the link in my guide.
lalovzg said:
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/
Click to expand...
Click to collapse
Sweet thanks!.
Try and use this firmware:.
https://androidhost.ru/9V2

Using that as a reference I found one for my region I think (C69) that says:
Integrates Google security patches released in Apr 2018 for improved system security.
Click to expand...
Click to collapse
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?

lalovzg said:
Using that as a reference I found one for my region I think (C69) that says:
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?
Click to expand...
Click to collapse
If its single sim, you need a single sim firmware and just use a firmware under 150, you should be okay

Would someone like to pay for me cuz I don't got a way to pay i don't have any credit cards..i know this is stupid but im just a teenager and my parents wouldn't pay for it so here i am lol

@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like This post forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad

HEKER510 said:
@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the dam to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like aky maš na forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad
Click to expand...
Click to collapse
Im sorry, i dont understand what you are writing

brugernavn said:
Im sorry, i dont understand what you are writing
Click to expand...
Click to collapse
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?

HEKER510 said:
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?
Click to expand...
Click to collapse
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu

brugernavn said:
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu
Click to expand...
Click to collapse
Bro 166 firmware for servis menu yes ? thankx you very much

thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again

Hey, to root my p20, flashing magisk via recovery, don't need ramimage, all works fine

how to do it
how to flashing magisk via recovery? (whit TWRP or not??) you can explain the passage?

cirovi said:
thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again
Click to expand...
Click to collapse
what software are you running now?

10.0.6 OTA filenames HD65BA

I noticed a system update was announced, grabbed the data from ADB and sharing them here.
Not sure how usefull this is, but perhaps someone can figure out the URL that hosts them and share the downloads.
I have not been able to find the url, but you can copy the file from .Ota directory on the sdcard
OnePlus7TOxygen_14.E.08_OTA_006-008_patch_1911061922_db44361aba217b4.zip
OnePlus7TOxygen_14.E.08_OTA_008_all_1911061922_1846b.zip
Task thread startDownload currentType:http patchFile:id:0 fid:0 name: OnePlus7TOxygen_14.E.08_OTA_006-008_patch_1911061922_db44361aba217b4.zip md5:8746fcd2a75dd7abe4bdf91c4c47f411 size:186116097 downloadedSize:0 downloadFinished:0speed0extract#OnePlus 7T Oxygen OS 10.0.6.HD65BA
Task thread startDownload currentType:http patchFile:id:0 fid:0 name: OnePlus7TOxygen_14.E.08_OTA_008_all_1911061922_1846b.zip md5:d9846a7a941786fed60ad54a0a2b096c size:2710484155 downloadedSize:0 downloadFinished:0speed0extract#OnePlus 7T Oxygen OS 10.0.6.HD65BA

https://otafsg1.h2os.com/patch/amaz...ygen_14.E.08_OTA_008_all_1911061922_1846b.zip

supaflyx3 said:
https://otafsg1.h2os.com/patch/amaz...ygen_14.E.08_OTA_008_all_1911061922_1846b.zip
Click to expand...
Click to collapse
Thx
Now we need someone to extract boot image from this ota ,so we can magisk patch it
No patched boot image for 10.0.6 global around yet

Why you need patched_boot.img?
I have downloaded ota file, put it into root directory, install it through setting>System update>local update, open magisk and made "Install to inactive slot (after ota), reboot, once phone started I open magisk and made "Direct install (Recommend)". Everything is fine.
If it's mater, my phone is unlocked and rooted.

You find it her
spoonymoon said:
Thx
Now we need someone to extract boot image from this ota ,so we can magisk patch it
No patched boot image for 10.0.6 global around yet
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-european-t4006559

[ROM] LINEAGEOS [Android 11] [OFFICIAL] [Nightly]

I'm not sure why no one has posted this on here yet. I see the unstable google drive linked Android 11 Lineage but not the official download links and instructions...
i run this rom on my daily driver.
here is the link:
https://download.lineageos.org/walleye
the instructions are what you should foolow as they know alot more than me about all this but they say to temp flash the recovery, that has never worked for me.
WARNING!!!
IT IS NOT RECOMENDED BY LINEAGE TO USE GAPPS, AS SOME OF THEM WILL OVERWRITE/REMOVE OPTIMIZED LINEAGEOS SYSTEM APPS, AND REDUCE SECURITY/STABILITY!
THE SYSTEM WORKS JUST FINE WITHOUT GAPPS BUT IF YOU CHOOSE TO USE THEM LIKE I DO HERE IS THE INSTRUCTIONS I FOLLOW:
-----------------------------------------------------------------------------------------------------------------------
1. remove password on system
2. copy the downloaded system zip to sdcard
Google usb driver found here: https://developer.android.com/studio/run/win-usb
3. adb reboot-bootloader
google platform tools adb & fastboot found here: https://developer.android.com/studio/releases/platform-tools
4. fastboot boot [twrp]
do not allow modifications, do not change any settings and do not install twrp to recovery
Twrp found here: https://dl.twrp.me/walleye/
5. install [Lineage.zip]
sometimes you can sideload this pkg but others not so i just send it to the sdcard and install from there in twrp, ive had issues with usb 3.1 ports with system pgk but not with gapps.
6. reboot to bootloader and fastboot boot [twrp]
if you do not do step 6 the boot slot will not be correct for installing the gapps and will not be able to boot the system
7. adb sideload [gapps-core] and then adb sideload [addons] (without booting system before all gapps installed)
i get these from here: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/
i only do the core first, then i have a short batch file sideload all the addons i want from here:
https://sourceforge.net/projects/nikgapps/files/Releases/Addons-R/ choosing which ones i need because there is not always enough space.
the ones i sideload in order are named like this [NikGapps-Addon-11-*-signed.zip] below:
GBoard
Gmail
GoogleClock
GoogleContacts
GoogleDialer
GoogleMessages
GoogleCalculator
GoogleCalendar
GooglePhotos
Velvet
GoogleChrome
GoogleFi
GoogleTalkback
GoogleTTS
8. reboot system, and let boot up.
9. adb reboot-bootloader
enable usb debugging first
10. fastboot boot twrp
if you wanted to install twrp to system as recovery do it before magisk at this step.
11. adb sideload magisk.zip
magisk.zip is the magisk.apk, just rename the apk found here: https://github.com/topjohnwu/Magisk/releases
12. reboot
If magisk doesn't seem to want to work at this step:
open app while online, reboot, test again, if still no:
adb install -g [magisk.apk]
did i do something wrong? miss something? want me to take this down? make this better?
any feedback is welcome as this is mainly because i've spent many hours trying to figure all this out so i hope it helps someone.

The original post it's at Pixel 2 XL forum

Tony Ronaldo Matute said:
The original post it's at Pixel 2 XL forum
Click to expand...
Click to collapse
why, because the walleye and taimen kernel merge?
link please?

Solomon M said:
why, because the walleye and taimen kernel merge?
link please?
Click to expand...
Click to collapse
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session

kurokuroninja said:
Here is the link
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
When will it be getting official and updated to December patch?
forum.xda-developers.com
Maybe you can ask permission to @Eamo5 for make thread in P2 session
Click to expand...
Click to collapse
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this. Also maybe they should post in the Walleye form instead of the other to help people find walleye related roms or rom info.
Whoever decided to put all walleye stuff with taimen just because they are both wahoo is dumb.
That's like saying let's put all the phone a with b just because some of it is the same. If they where the same then at least they would both be made by the same hardware manufacturer LG != HTC nor vice versa.

Solomon M said:
Oh! This is a duplicate. My apologies.
I'm not sure how to delete this.
Click to expand...
Click to collapse
Thread has been closed.

How To Guide [Guide] Xiaomi Mi Pad 5 MIUI12/13 ROOT Step-by-step - Pass SafetyNet, Widevine L1

Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5​EEA 13.0.3​Global 13.0.1​​​Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader

Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01

Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.

Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01

Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.

Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.

Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!

Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.

thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks

Can i update ota to 13.0.2 after rooted? Just update and root again?

Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2

How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?

Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5

Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...

Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?

thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.

vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img

kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks

Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?

cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet