Database Develop

Root on Oxygen OS 4.0.3

Hey guys, can anyone tell me which version of supersu you used to install root on the latest 4.0.3 rom?
I tried flashing the latest UPDATE-SuperSU-v2.79-20161211114519 and the older SuperSU-v2.79-201612051815, but both seem to get stuck on boot. I tried waiting for an hour just to be sure. I also tried flashing no-dmverity after flashng supersu, but that didn't help either.
Will appreciate some help.

Hey,
I used SuperSU v2.79-20161211114519
https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip
Worked without problems for me.
Are you clean flashing?
EDIT: also, are you using the latest 3.0.4-1 TWRP?

knijntjes said:
Hey,
I used SuperSU v2.79-20161211114519
Worked without problems for me.
Are you clean flashing?
EDIT: also, are you using the latest 3.0.4-1 TWRP?
Click to expand...
Click to collapse
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.

Azureum said:
Yeah, I clean flashed it. Used twrp 3.0.4-1 , 3.0.4-0 and 3.0.3-1 - but none worked.
Also tried going stock recovery, flashing ROM, flashing twrp and then supersu. That didn't work too.
Click to expand...
Click to collapse
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?

knijntjes said:
You could try to flash only no-dmverity without superuser to see if you can get twrp working with 4.0.3.
If that works you could try again, or maybe use PHH Superuser?
Click to expand...
Click to collapse
Yeah I did that too. The ROM works without supersu. But after that when I flashed supersu, it got stuck on boot.
Will try PHH superuser at a later time. Also there's no way to remove dm-verity warning message on 4.0.3, right?

I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).
Haven't tried it without SuperSU so for now sticking to 4.0.2
Also have the same question about removing the dm-verity message on boot.

gigo08 said:
I'm having the same issue - installing 4.0.3 and then flashing SuperSU 2.79 results in a boot sequence that never ends (not a loop, just sits there with spinning icons forever).
Haven't tried it without SuperSU so for now sticking to 4.0.2
Also have the same question about removing the dm-verity message on boot.
Click to expand...
Click to collapse
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware

kunal1540 said:
No problems here with SuperSU 2.79 sr3
For removing dm verity error you can search for a thread here on xda
It involves flashing 4.0.2 firmware image then executing fast boot commands to remove that error and then flash back 4.0.3 firmware
Click to expand...
Click to collapse
Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.

Interesting, I hadn't tried any of the beta SuperSu releases. What version of TWRP did you use? I'll give this a try later.
Click to expand...
Click to collapse
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.
Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).
How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.

Hi, is it possible to update to Oxygen 4.0.3 after rooted and having magisk 11.1? I am currently on 4.0.2

HolyJeepers said:
I used a Twrp 3.0.4-1 image. The official Twrp 3.0.3-2 may have a problem with Oxygen 4.0. But instead of SuperSU, after unlocking and installing Twrp, I flashed Magisk 11.1.zip from Twrp. Magisk 11.1 contains its own MagiskSU. After installing Magisk, install "Magisk Manager" from the Playstore. In Magisk Manager open the menu (tap the 3 horizontal lines at top left) and select settings. Turn on Enable BusyBox, Magisk Hide, and Systemless hosts. Press the back arrow at the top to get the menu back and select status. Now check SafetyNet and it should pass. If you passed SafetyNet, your can safely set up your security (PIN and fingerprint). Try starting an app that needs root. In the Magisk Manager menu select SuperUser and it will list all the apps granted root permission. Each entry there has an on/off switch. If you tap an entry more options will be shown.
Instead of unlocking your phone in order to flash twrp, try booting twrp: "fastboot boot twrp-3.0.4-1-oneplus3.img". Then use this temporary twrp to install Magisk. If it works, you can root your phone without unlocking it and wiping your data. (I would try it, but I'm already unlocked).
How I rooted details: I already had abb and fastboot installed on my pc. After the OEM upgrade to Oxygen 4.0.3, change lock screen security to swipe (no security). Connect phone to pc using the original charging cable. Enable Developer options (by tapping "about phone" in Settings 7 times). In Developer options turn on OEM unlocking, Advanced reboot, and USB Debugging. Hold the power button until it offers to Reboot or Power off. Select Reboot, then select Bootloader, then touch to reboot. Open cmd window in adb folder (hold shift and right click on a blank spot in folder and select Open command window here ) In cmd prompt type fastboot devices and press enter. If it finds your device type fastboot oem unlock and press enter. Use volume keys to select >> YES and briefly press power key. Wait for it to finish wiping the data partition. Now you are "unlocked" (flashing enabled). Type fastboot flash recovery <twrp image> and press enter where <twrp image> is your TWRP 3.0.4-1.img file name (the official twrp, 3.0.3-2 has problems with Oxygen 4) Type in the name of this file, or drag and drop the file to the cmd window, or copy it's name (with just one .zip on the end) and paste it into cmd window by clicking on the black icon in the upper left corner, scrolling to Edit, then click Paste). After it's finished flashing, use the volume keys to select recovery and briefly press power button to boot into TWRP. In TWRP swipe right to enable writing to the system partition (however we will NOT change a single bit in system so we can pass SafetyNet). Install your Magisk v 11.1 zip file (it's a system-less app). Reboot to system. Proceed with downloading Magisk Manager from the PlayStore.
Click to expand...
Click to collapse
Is twrp. 3.0.4-1 and magisk v. 11.1 zip.. Adb folder.
Thats all..

Can anyone make a video of it please thanks

Mate 10 Pro lost root

Hi guys
I have rooted my mate 10 pro using the guides from this forum and everything worked like a charm.
Now I wanted to check on my adaway to install the latest block lists and it said that the phone has to be rooted. So I opened my SU and it said root undetected.
I haven't done any updates or what else could have caused the loss of root.
Any ideas on how that could have happened?

Aval0n1979 said:
Hi guys
I have rooted my mate 10 pro using the guides from this forum and everything worked like a charm.
Now I wanted to check on my adaway to install the latest block lists and it said that the phone has to be rooted. So I opened my SU and it said root undetected.
I haven't done any updates or what else could have caused the loss of root.
Any ideas on how that could have happened?
Click to expand...
Click to collapse
Which SU were you using? SuperSU, PHH Superuser or Magisk?
I do know that SuperSU sometimes loses root, a reboot usually fixes it. Or flash it again.
If SuperSU or PHH I recommend switching to Magisk. It has modules that you can install and uninstall easily and ad-blocking is one of them (Unified hosts block).
You would need Twrp to install it the easiest way, you can get that here: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
And Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flash TWRP if you don't have it already, and if your current doesn't have decrypt support:
Then simply reboot to fastboot mode (Vol down + USB + power).
Then use the command
fastboot flash recovery_ramdisk twrp.img
After you have flashed TWRP, type 'fastboot reboot', and hold Vol up + Vol down (while USB is still plugged in).
When in TWRP, enter pin/password to enable decryption.
Transfer Magisk to sdcard and flash using Install button.
If it says ramdisk is already patched you will have to restore stock image. You can do this by downloading your current firmware update.zip from http://pro-teammt.ru/firmware-database/
When you have update.zip, extract update.app from it and download Huawei Update Extractor.
Extract and open Huawei Update extractor, then go to settings and disable Header check (else it will give you an error when you open update.app).
Open update.app in the program and rightclick on Ramdisk and Extract Selected. Now go to fastboot mode and flash 'fastboot flash ramdisk ramdisk.img'.
After this go back to TWRP and flash Magisk again.
After it is flashed open Magisk Manager, tap the hamburger menu and then on Downloads. Here you can download modules. Unified Hosts block is the one you'd want for ad-block. When it is flashed, reboot and open a terminal app. Use the command 'hosts' to enter the Unified hosts block interface. I only use 'm' for ad blocking.
You could set up Adaway systemless blocking with Magisk too if you prefer Adaway.

Thank you for your help! I have Super SU and the reboot fixed the problem.
I will go through your post and use the tips you gave!
Thank you again!!

Alternative method magisk root [stock android 9][NO TWRP][Samsung A70 FN/DS]

purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
 @raeumler for his guide.

Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.

kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10

Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka

Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?

DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods

i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....

raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.

Is there a guide on updating to the newest firmware and Magisk

Fairly newbie user here. I'm looking for a guide that lists how to upgrade the P5 to a new firmware and keep Magisk and all of that. I've looked at the thread below and it is good for getting started up in the beginning, but I'm not following how it works for a new firmware.
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Like how do I flash the new February firmware onto my phone?
Do I then copy the boot.img to the P5 and patch it with Magisk?
Then do I copy the patched boot.img back to my PC and flash it back onto the P5?
Are there are new step or process for unlocking SafetyNet?
I'm just very confused and would appreciate something simple and basic to follow, please.
Thanks!

1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot

UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com

You can bypass safetynet perfectly with hiddencore module for xposed.
HiddenCore Module | Xposed Module Repository
repo.xposed.info

Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.

hanni2301 said:
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol

hanni2301 said:
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
I have tried few years ago, in some previous version of android, instead of running flash-all.bat, I flash each image individually, (fastboot flash bootloader..., fastboot flash boot..., fastboot flash recovery.... etc. ). If I took the shortcut of not flashing the original boot image first and then the patched one, but flash the patched boot directly, then the phone run into a bootloop.

cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.

Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.

VD171 said:
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
Click to expand...
Click to collapse
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.

Ewto16 said:
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Click to expand...
Click to collapse
Next time, don't flash the factory image. Sideload the OTA.zip instead. That way you won't lose any of that.
Sideload the OTA, flash the patched boot.img (the boot.img you need to get from the factory image though), and you won't lose Magisk, your modules, or your root settings.
I used to do the same. Edit out the -w flag from the flash-all and re- setup my phone. Sideloading the OTA is easier and quicker in the end.

Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
1. Yes
3. Edit the flash-all.bat file with any editor, e.g. notepad in windows, you will see -w near the end of the file, remove it, then save and run the file. You must make sure the -w is removed, otherwise all the data will be wiped
4. To boot into bootloader: adb reboot bootloader
To flash the patched boot image: fastboot flash boot magisk_ patched.img (the file name changes every time, just use the one you have when you patch the boot image)

It's easier to replace the "-w" with "--skip-reboot" (first one is double dashes). The phone won't reboot when the image flashing is complete so you can immediately re-flash the patched boot img.
This youtube video is great to follow and has clear step by step guide.

Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?

Ewto16 said:
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Click to expand...
Click to collapse
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.

swangjang said:
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
Click to expand...
Click to collapse
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.

Ewto16 said:
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Click to expand...
Click to collapse
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.

swangjang said:
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
Click to expand...
Click to collapse
Interesting....I thought those were one and the same. Thanks for the tip. I'll give that a try.
I'd still like to get GPay working again though.

VD171 said:
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
Click to expand...
Click to collapse
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2

hanni2301 said:
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
Click to expand...
Click to collapse
Grow up, my friend.
Anything can changes from device to device.

How To Guide Rooting the Mi 11 with the latest Xiaomi.eu ROM

EDIT: This is not for the TWRP version. I will update this thread soon!
Hello!
Since I saw a lot of people asking, I decided to post how to root a Mi 11 (as of 2021-02-11).
Install the Xiaomi.eu ROM. You can find more details in this post. Keep the ROM's files, you will need some of them!
Connect your phone to the PC and put it into file transfer mode.
Download Magisk Manager from the official GitHub repository and install the APK. DO NOT DOWNLOAD MAGISK MANAGER FROM ANYWHERE ELSE. THIS GITHUB REPOSITORY IS THE ONLY OFFICIAL, TRUSTED SOURCE.
In the directory you extracted the ROM zip file to, there's a directory called images. This directory contains a file called boot.img. Copy the boot.img to your phone's Download folder.
Open the Settings app, go to My Device, then tap MIUI Version until it says You are now a developer.
Go back to your Settings app and use the search bar to search for USB Debugging and enable it. Click on Yes when it asks whether you want to trust this computer.
Once the file is completely copied, open Magisk Manager on your phone. There will be 2 categories: Magisk and Manager. On the Magisk category, click on Install and choose Select and Patch a File. Navigate to your downloads and select boot.img. Click on Let's go.
When Magisk has finished patching your boot.img file, it will say Output file written to /storage/emulated/0/Download/magisk_patched_XXXXX.img, where XXXXX is 5 random letters/digits.
Open a command prompt on your computer and run adb pull /sdcard/Download/magisk_patched_XXXXX.img , replacing XXXXX with the random characters Magisk showed you earlier. This will copy the file to the directory you are currently in; on Windows, if you are using cmd, this will be C:\Users\[your username].
Reboot your phone into fastboot mode by turning it off, then holding the power and volume-down buttons until it vibrates.
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b). Don't forget to replace XXXXX with the random characters Magisk Manager generated. Run the command fastboot reboot and open the Magisk Manager app when your phone has finished rebooting. The app should say that it needs to install some other components; click yes and let it do its thing. It will reboot the phone, and after that, Magisk and therefore the root should be working!
When I first did this, my SafetyNet check failed. I fixed this by repeating all the steps, except that I updated the ROM instead of reinstalling it. You can update it even if it's the same version; it will just flash everything again. You may need to clear the cache of Google Play and reinstall Google Pay if the SafetyNet check initially failed.

Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?

PandaKiller said:
Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?
Click to expand...
Click to collapse
You do not need to use the OEM Unlock option in the developer options. Mine is still off even after I unlocked my bootloader. You need to use the Xiaomi Unlock Tool found at https://en.miui.com/unlock/ .
Before using this tool, you need to log in to you Mi account on your phone. Then, reboot the phone into fastboot mode, connect it to your PC, and use the unlock tool. It will tell you to wait 168 hours (1 week) before trying again. DO NOT RETRY BEFORE THE 168 HOURS ARE OVER OR THE TIMER RESETS! Even if you are a single minute early, it will reset the timer.
Once the week has passed, do this again and your phone will be unlocked. Warning: This will erase your data.
You should prepare the boot image BEFORE unlocking, because otherwise you will have to go through the phone's setup, install Magisk, patch the image, and wipe the phone again.
Another warning: Do not re-lock your bootloader. If the bootloader is re-locked with any ROM other than the one the phone shipped with installed, the phone gets bricked.

Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.

PandaKiller said:
Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.
Click to expand...
Click to collapse
If you use the Xiaomi.EU ROM, you can update without wiping your data. They give you 2 scripts - 1 for installing and 1 for updating.

Thanks for the write-up. Worked like a charm (Y)

Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?

Giova19 said:
Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?
Click to expand...
Click to collapse
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.

Lucavon said:
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.
Click to expand...
Click to collapse
Ok noted. I rooted following the full process 3 times and cannot get the safenet.

If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!

Giova19 said:
Ok noted. I rooted following the full process 3 times and cannot get the safenet.
Click to expand...
Click to collapse
That's weird, it works perfectly fine for me. Maybe you need to re-download your Xiaomi.eu ROM.
xXSkylinexX said:
If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!
Click to expand...
Click to collapse
Yes, you need to repeat it. After updating, copy the boot image, patch it again, etc, like in this post.

Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?

Plathoon said:
Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?
Click to expand...
Click to collapse
Do you have magisk hide enabled?
If you do and you're checking safetynet status with a different app than magisk manager, you need to add it to hide.

Magisk hide is enabled too

SOLVED
- enable magiskhide
- download "magiskhide props config"
- use app like termux and follow steps :
* "su"
* "props"
* "1" (edit device fingerprint)
* "f" (pick a certified fingerprint)
* select your phone
* accept and reboot.
and now it work.

Hello,
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Note: I installed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot
After installing the Rom, the following error message appeared at the end.
fastboot: error: Cannot generate image for userdata
Can it have anything to do with it?

Lucavon said:
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b).
Click to expand...
Click to collapse
Why don't write directly fastboot flash boot_ab magisk_patched_XXXXX.img ? Is that intended ?

bert4711 said:
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Click to expand...
Click to collapse
Idk if I was having and same issues, but for me on 3.31 xiaomi.eu I was having issues with the superuser prompt not appearing. I found it happened only when the magisk app was repackaged. Approving prompts while it was unhidden then hiding magisk worked great.

Edited

I use the root explorer, the root query also appears with Magisk. But I still don't get write access to the root directory. I originally had the Global Rom V12.0.4.0.RKBMIXM on it. After the bootloader was open, I flashed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot. The following error message occurred at the end of the flash process. fastboot: error: Cannot generate image for userdata I am currently assuming that the problem with root has something to do with it. I have already tried the Version xiaomi.eu_multi_MI11_V12.5.1.0.RKBCNXM_v12-11-fastboot. The result is the same... fastboot: error: Cannot generate image for userdata and no write permissions in the root directory ...