Develop Bugs

Help with bypassing safetynet, magisk v16.0, Google Pixel 2 XL

Hey guys, I just recently did a systemless root of my pixel 2 XL and I haven't been able to get it to bypass safetynet, the only app I use right now that requires root is Adaway and I had tested to see if it was causing the trouble by uninstalling it which has proven fruitless, any ideas on how to get past safetynet would be great, even if it means rooting my phone again differently.

Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager

Pyr0x64 said:
Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager
Click to expand...
Click to collapse
I'm not running a custom kernel, and the apps I want to use won't work even if root is hidden, one's my banking app for my bank back in england.

If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.

Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too

Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
henderjr said:
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too
Click to expand...
Click to collapse
Okay, I'll try doing that, will update on the results

No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.

Are you using Xposed?

No, I'm not using xposed

Brawler6216 said:
No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.
Click to expand...
Click to collapse
Why are you flashing the dtbo.img???

Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Click to expand...
Click to collapse
Did it work?

Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.

Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.

Brawler6216 said:
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.
Click to expand...
Click to collapse
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:

Badger50 said:
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:
Click to expand...
Click to collapse
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.

Brawler6216 said:
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.
Click to expand...
Click to collapse
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:

TonikJDK said:
Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.
Click to expand...
Click to collapse
Badger50 said:
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:
Click to expand...
Click to collapse
It passed! Awesome thank you, guys so much!!

Brawler6216 said:
It passed! Awesome thank you, guys so much!!
Click to expand...
Click to collapse
Congrats my friend. Well done! ???
Now you just need to dark theme that sucker! ?

Badger50 said:
Congrats my friend. Well done!
Now you just need to dark theme that sucker!
Click to expand...
Click to collapse
When you're too excited that it passed safetynet

March update with Magisk

Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?

Daisymae said:
Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
Click to expand...
Click to collapse
What do you mean when you say you "checked
select and patch'? Do you mean you opened Magisk Manager tapped install (next to Magisk),tapped install, tapped select a boot image to patch. Selected it and tapped the check mark? If yes, try again.

Homeboy76 said:
What do you mean when you say you "checked
select and patch'? Do you mean you opened Magisk Manager tapped install (next to Magisk),tapped install, tapped select a boot image to patch. Selected it and tapped the check mark? If yes, try again.
Click to expand...
Click to collapse
Tried it several times with same result. When I get to "method" I tap "select and patch". It immediately takes me to the download directory where the boot.img is. I tap that and it takes me back to the screen with the methods. I tap next and then "lets go" appears.. I tap that and it closes. Nothing happens.
Update: found the problem. It was a canary magisk manager. DL the stable one and patched image was created.

Daisymae said:
Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
Click to expand...
Click to collapse
Had exactly the same thing today. I cleared cache and data on Magisk Manager, uninstalled it and then reinstalled. Worked fine after that. Might be able to skip the uninstall step, I just do things that 2ay to be complete. Make sure you get the APK from a legit source, there are fakes out there.
Ahhh, just saw the post above. Yep I was on Canary and when I reinstalled I went back to stable.

Yes, it is a bug in the latest canary magisk manager. It should be fixed in next canary release.

Stable version roots fine so that's an option until canary builds are fixed.

rspkt said:
Stable version roots fine so that's an option until canary builds are fixed.
Click to expand...
Click to collapse
Beta works without issue as well.

Where is DL for APK...

imaverik said:
Where is DL for APK...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/

thx!

imaverik said:
thx!
Click to expand...
Click to collapse
You're welcome!

When I patch the March boot.img with Magisk Manager 7.5.1 stable and Magisk 20.3 I get a boot loop at the "G" screen after the progress bars cycle for a few seconds. I actually got the same result when I did the Magisk method of accepting the March OTA which is why I'm trying this method. I've tried reflashing both slots with factory March and then flashing patched image to both slots, so far no love. If I flash the stock boot.img back to the active slot it boots right up without root. Any ideas? TIA!

ktdt00 said:
When I patch the March boot.img with Magisk Manager 7.5.1 stable and Magisk 20.3 I get a boot loop at the "G" screen after the progress bars cycle for a few seconds. I actually got the same result when I did the Magisk method of accepting the March OTA which is why I'm trying this method. I've tried reflashing both slots with factory March and then flashing patched image to both slots, so far no love. If I flash the stock boot.img back to the active slot it boots right up without root. Any ideas? TIA!
Click to expand...
Click to collapse
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel3xlRemove
-
Code:
fastboot flash boot magisk_patched.img --slot all
-
Code:
fastfoot boot image-newpixel3xl.img
- Use a root file manager to open data/adb/modules folder
- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!

Homeboy76 said:
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel4xlRemove
-
Code:
fastboot flash boot magisk_patched.img --slot all
-
Code:
fastfoot boot image-newpixel4xlRemove.img
- Use a root file manager to open data/adb/modules folder
- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!
Click to expand...
Click to collapse
That worked! I actually had to use the image-newpixelxx vs image-newpixelxxRemove as the latter also boot looped for me. Who knows what state I'd gotten myself into to cause that. I also had to manually take Magisk out of core only mode afterwards in the app settings in order to get systemless hosts working again. Anyway - it definitely was a bad module and you put me directly on the right track! Thanks so much!

ktdt00 said:
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel4xlRemove
-
-
That worked! I actually had to use the image-newpixelxx vs image-newpixelxxRemove as the latter also boot looped for me. Who knows what state I'd gotten myself into to cause that. I also had to manually take Magisk out of core only mode afterwards in the app settings in order to get systemless hosts working again. Anyway - it definitely was a bad module and you put me directly on the right track! Thanks so much!
Click to expand...
Click to collapse
Glad you got it working.

Hey all, anyone having the issue of the Play Store not being certified after updating to the March update? I'm rooted after using the patched image with Magisk but I can't get certified. Thanks in advance.

My phone boots fine after root but the touch screen is not working. After flashing the stock boot.img again then everything works fine. Any suggestions? Thanks in advance.

JayYip said:
My phone boots fine after root but the touch screen is not working. After flashing the stock boot.img again then everything works fine. Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
If I may ask, what version Magisk are you using? Stable or Canary?

rsnyc said:
If I may ask, what version Magisk are you using? Stable or Canary?
Click to expand...
Click to collapse
Stable.

JayYip said:
Stable.
Click to expand...
Click to collapse
I can't figure it out on my Pixel 3 XL. Hopefully someone will update us.

Question [CLOSED] POCO F3 GLOBAL STUCK ON BOOT LOGO. HELP NEEDED.

Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.

just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there

metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Free phones welcomed.

pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.

Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.

Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.

Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found

Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.

Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.

reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails

Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?

Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.

Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol

Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?

have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here

Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse

reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/

pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/

Question Can someone explain to me how to root this phone using ArrowOS ROM?

Hi all, I am very confused. I am trying to figure out how to root this phone. I read the instructions for magisk and attempted to patch the boot.img file linked in the ArrowOS post (https://drive.google.com/file/d/1o-4T4hfEtxECIss-DVSSYAM1Kvy2iDN9/view?usp=sharing)
But whenever I flash that patched boot.img I am getting stuck on a bootloop. And then I found someone already patched the boot.img on August (this post) but that boot.img does not pass safetynet.
Can someone explain to me what I am doing wrong and how to properly root this phone? Thanks!

litetaker said:
Hi all, I am very confused. I am trying to figure out how to root this phone. I read the instructions for magisk and attempted to patch the boot.img file linked in the ArrowOS post (https://drive.google.com/file/d/1o-4T4hfEtxECIss-DVSSYAM1Kvy2iDN9/view?usp=sharing)
But whenever I flash that patched boot.img I am getting stuck on a bootloop. And then I found someone already patched the boot.img on August (this post) but that boot.img does not pass safetynet.
Can someone explain to me what I am doing wrong and how to properly root this phone? Thanks!
Click to expand...
Click to collapse
Open developers options enable usb debugging , connect pc type in CMD :
adb reboot bootloader && fastboot boot
( After fastboot boot space and then you drag and drop twrp file )
Phone boots into twrp , copy magisk from pc and paste to phone , press install in twrp and choose magisk. That's it , I make sure to leave inject twrp as disabled. If you want to install twrp first reboot into system make sure magisk works alright then boot into twrp again and install via advanced menu

Can you explain the "copy magisk from pc and paste to phone , press install in twrp and choose magisk" part? It is not very clear?
Is this a different method instead of patching the boot.img? If so, is this permanent or temporary and I need to use recovery every time to re-enable root?

Just flash the magisk apk file using twrp, yes you can flash apk file on twrp. Make sure 'inject twrp' is unchecked! Reboot then wait till magisk app appears on app drawer and run it then follow the steps it will tell.

Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?

litetaker said:
Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?
Click to expand...
Click to collapse
you really cant do anything about that now, google recently announced that they are implementing a hardware attest method for every phone. That means once you root the device, you wont be able to pass safety net, given that its hardware level now, its near impossible to find a solution now but im pretty sure there are some ways to trick it into giving the safety net a pass status, but im currently not aware of one.

litetaker said:
Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?
Click to expand...
Click to collapse
You can enable MagiskHide in the settings

Noe367 said:
You can enable MagiskHide in the settings
Click to expand...
Click to collapse
Wow, I did not double check it after hiding magisk but it works now! Thanks!

litetaker said:
Wow, I did not double check it after hiding magisk but it works now! Thanks!
Click to expand...
Click to collapse
Be sure, to enable MagiskHide to the apps that needs it, otherwise you can also install the module "MagiskHide Props Configs"

How To Guide TWRP + Root

Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.

Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.

Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?

pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.

regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?

pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.

When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?

__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple

still works like a charm

thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?

katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.

regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit

Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?

Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com

Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?

Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options

How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.

Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.