Database Info

Correct versions of TWRP and Magisk

Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much

I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.

You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp

Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse

maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.

TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you

maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:

Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.

I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom

Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT

maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck

fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?

maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck

fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal

Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.

bad post

dont install official twrp on existing twrp

Guys warning dont install official twrp on existing unofficial one it softbbricks the device i flashed fastboot rom and updated to 5.1.6 and followed the tutorial on official twrp to get it working

I just flashed the zip. I'm sure things go south of you flash the original .IMG by itself. I think you also have to reroot after flashing or you boot loop.

Ascertion said:
I just flashed the zip. I'm sure things go south of you flash the original .IMG by itself. I think you also have to reroot after flashing or you boot loop.
Click to expand...
Click to collapse
You were on unofficial TWRP and just flashed the zip and it worked?

ddominikt said:
You were on unofficial TWRP and just flashed the zip and it worked?
Click to expand...
Click to collapse
No, I did that and didn't worked. Just flash img. from twrp on fastboot and then flash permanent twrp from that temporary twrp

Manivannan9444 said:
Guys warning dont install official twrp on existing unofficial one it softbbricks the device i flashed fastboot rom and updated to 5.1.6 and followed the tutorial on official twrp to get it working
Click to expand...
Click to collapse
I literally just did. And it's totally fine. Just flashed the zip then rebooted recovery then reflashed magisk v16.0 zip then rebooted system. Zero issues whatsoever.
Where do you get oos 5.1.6?
BTW, you can flash official OTA in TWRP then just flash TWRP & magisk again afterwards.
Sent from my OnePlus 6 using XDA Labs

brossovitch said:
I literally just did. And it's totally fine. Just flashed the zip then rebooted recovery then reflashed magisk v16.0 zip then rebooted system. Zero issues whatsoever.
Where do you get oos 5.1.6?
BTW, you can flash official OTA in TWRP then just flash TWRP & magisk again afterwards.
Click to expand...
Click to collapse
You just flashed the installer zip what about twrp img

Key is flashing magisk. It's in every tutorial

Manivannan9444 said:
You just flashed the installer zip what about twrp img
Click to expand...
Click to collapse
No. I already had unofficial TWRP installed so I simply flashed the installer.
Here's exactly what I did:
1. Downloaded the official TWRP installer package
2. Hold power button, selected reboot, select recovery, tap to reboot.
3. In TWRP, confirm Lockscreen code. Select install & selected installer package swipe to flash.
4. Press home button, select reboot, select recovery, reboot.
5. In TWRP again (now official version) confirm Lockscreen code again, select install, select Magisk 16.0, swipe to flash.
6. Select reboot system. System reboots.
7. Go on XDA find this thread and say it worked fine.
8. This is where we are now. LOL
FYI... I used the unofficial TWRP provided by Zedomax (Max Lee from HighOnAndroid) originally. I didn't do all those other crazy versions.
Sent from my OnePlus 6 using XDA Labs

brossovitch said:
No. I already had unofficial TWRP installed so I simply flashed the installer.
Here's exactly what I did:
1. Downloaded the official TWRP installer package
2. Hold power button, selected reboot, select recovery, tap to reboot.
3. In TWRP, confirm Lockscreen code. Select install & selected installer package swipe to flash.
4. Press home button, select reboot, select recovery, reboot.
5. In TWRP again (now official version) confirm Lockscreen code again, select install, select Magisk 16.0, swipe to flash.
6. Select reboot system. System reboots.
7. Go on XDA find this thread and say it worked fine.
8. This is where we are now. LOL
FYI... I used the unofficial TWRP provided by Zedomax (Max Lee from HighOnAndroid) originally. I didn't do all those other crazy versions.
Click to expand...
Click to collapse
Ok

intruda119 said:
Key is flashing magisk. It's in every tutorial
Click to expand...
Click to collapse
Spot on. Most people make this mistake then moan about it not working.
Sent from my ONEPLUS A6003 using Tapatalk

I flashed official twrp on stock recovery and now I can't exit twrp in both slots

Confirmed working fine on official twrp
Reboot recovery
Flash twrp installer zip (official)
Reboot recovery
Flash magisk 16.0
Wipe cache/davlik
Reboot system
*** DO NOT INSTALL TWRP when printed just reboot system
Profit
Rooted running official TWRP 3.2.1 enchilada ??

Alright, this is a bit confusing.
Can someone tell me if I can update to official TWRP from unofficial, without losing my data/settings? The method OP describes (via fastboot) resets all my data I guess? Wish I had never installed the unofficial version....
I have this unofficial version...

I had the unofficial twrp from the very same link you posted. No problem in updating to official TWRP. Just boot into recovery, install, select the official TWRP installer (forget the img file). Reboot in recovery again, install Magisk. Reboot to system. I did not lose any data or settings (keep always a backup of your important files, you'll never know).

Thanks for the quick reply! I dared to try it and I can confirm unofficial TWRP can indeed succesfull be overflashed with the official one. No bootloops, no errors!
Phew... I had a full nandroid backup, but I do not like the hassle of going through unbricking and such....
I had uninstalle Magisk beforehand, could be the trick?
I do not know why OP was not succesful, but it seems not a problem for everyone.

This thread really should be closed because the OP is 100% not true. If you get a softbrick, it's because you didn't install the official twrp correctly. The instructions are bit involved and I see many people skipping steps because they didn't read or don't see why they need to do anything different from previous phones.

Question I updated from an unofficial version. i followed instruction someone posted on here. But since the unofficial and official look exactly same how do I know I have official?

It does work, u just didn't do it right, u can install official TWRP over unofficial.

Well, depends on which unofficial one you use(d) .
The unofficial one I used was quite laggy on first start, I had to flash some additional zips to get it working right (see the link for install process). So concerning that one: when it works fine from start, you have the new one.
Blackout said:
Question I updated from an unofficial version. i followed instruction someone posted on here. But since the unofficial and official look exactly same how do I know I have official?
Click to expand...
Click to collapse

Magisk Root without TWRP for OnePlus 6 Oxygen OS Android 10 Open Beta 5 | OOS 10.3.1

Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.

wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！

Not work here. Bootloop, only see Bootanimation not more.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.

It works for me. That's a great help. Thank you.

SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.

Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.

Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.

geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.

Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.

geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.

What about safety net?

G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first

toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.

MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P

Download link updated with Beta 1 patched image.

Android 10 Root+TWRP

Did someone found the way to have root and TWRP on android 10 beta 5?

Today I tried to root Open beta and I wasn´t successful. fastboot boot twrp.img to boot into twrp and then flash magisk doesn´t work. Idk why.

Marek.N said:
Today I tried to root Open beta and I wasn´t successful. fastboot boot twrp.img to boot into twrp and then flash magisk doesn´t work. Idk why.
Click to expand...
Click to collapse
Check my guide.TWRP GUIDE FOR ANDROID 10

Cristianos102 said:
Did someone found the way to have root and TWRP on android 10 beta 5?
Click to expand...
Click to collapse
Patch boot.img from OB1 with Magisk.
Flash patched boot.img with fastboot.
Reboot and install TWRP with Magisk.

Could someone send me link to patched boot. Img
Or at least tell me how to get it

You'll find the how-to in the linked thread above...

tidschi said:
Patch boot.img from OB1 with Magisk.
Flash patched boot.img with fastboot.
Reboot and install TWRP with Magisk.
Click to expand...
Click to collapse
Root will work TWRP won't

vjendra said:
Root will work TWRP won't
Click to expand...
Click to collapse
Both will... don't talk if you don't tried...

tidschi said:
Both will... don't talk if you don't tried...
Click to expand...
Click to collapse
I tried....Its boots in TWRP but you cant flash anything

vjendra said:
I tried....Its boots in TWRP but you cant flash anything
Click to expand...
Click to collapse
Then tell me why I have both?!
If I flash patched boot.img, I have Magisk, ok.
If I have Magisk and I flash TWRP with it, I have TWRP but after Reboot no Magisk.
But I still have both? Means Magisk is flashed with TWRP?!

tidschi said:
Then tell me why I have both?!
If I flash patched boot.img, I have Magisk, ok.
If I have Magisk and I flash TWRP with it, I have TWRP but after Reboot no Magisk.
But I still have both? Means Magisk is flashed with TWRP?!
Click to expand...
Click to collapse
You can have both. But in TWRP, internal storage is not mounted so you can see your files. You have to wait for TWRP update for that

vjendra said:
You can have both. But in TWRP, internal storage is not mounted so you can see your files. You have to wait for TWRP update for that
Click to expand...
Click to collapse
How can you have both, if you can't fastboot boot TWRP??
Otherwise read again what I wrote before...I flashed Magisk with TWRP, how that if internal storage isn't working like you said?
Really don't know where the problem is...
Flashed TWRP with Magisk, no issues.
Flashed patched boot.img with TWRP, no issues.
Flashed Magisk with TWRP, also no issues.

tidschi said:
How can you have both, if you can't fastboot boot TWRP??
Otherwise read again what I wrote before...I flashed Magisk with TWRP, how that if internal storage isn't working like you said?
Really don't know where the problem is...
Flashed TWRP with Magisk, no issues.
Flashed patched boot.img with TWRP, no issues.
Flashed Magisk with TWRP, also no issues.
Click to expand...
Click to collapse
Are you a noob or what? Just read my comment above.

For me everything just works fine, have a nice day Pro Dev!

I have both TWRP and Magisk and both works I justed tested there

Link to patched boot.img?

djvita said:
Link to patched boot.img?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=80186989&postcount=27

I have lost about 6 hours on flashing 10 OB (all of my mistakes) and finally it works, twrp and root!
But I had to return to 958 patch boot of 10 and then flash 10 again..
The boot file from link above never work for me.

No problems for me with clean flash OB1

i fixed this by going back to pie, then android 10 official (using oxygen updater app), when i flashed in trwp i did oos.zip, then twrp zip then magisk zip. after that, magisk was enabled, and i can reboot to twrp

[REQUEST] NEED a Working TWRP and Magisk Root on MIUI 12.5.1 GLOBAL for POCO F2 PRO

Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,

Any news magisk for latest miui rjomixm v12.0.5.1

Bogazicili90 said:
Guys, I upgraded my POCO F2 PRO to MIUI V12.5.1.0.RJKMIXM (Android 11). Unfortunately TWRP and Magisk versions are not compatible with Android 11 and has problems.
Before upgrading I was on MIUI 12.0.4 Android 10 and both TWRP and magisk was working without problem.
Now, I tried both ManuelBlanco's and LR Team's TWRP versions and the problems is the same. When I click select storage, internal Storage (0.00 MB) seems 0 MB. Data can't be mounted.
Also, Magisk Root does't work on that ROM. I tried to root the phone with several versions of magisk both by patching or flashing zip files but the phone bootloops every time with patched boot.img
As a result now I can't use TWRP and root functions. Are there any one who succeed to make them work on that last update without wiping data or formatting data? I have lots of settings and data on the phone so I don't want to try other options of wiping or formatting.
Thanks,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839

NOSS8 said:
https://forum.xda-developers.com/t/...y-net-pass-without-twrp.4223939/post-85443839
Click to expand...
Click to collapse
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO

Bogazicili90 said:
This method DOES NOT work. I tried this option before opening this thread. Magisk manager doesn't patch the boot. img correctly. After flashing new boot.img the phone doesn't boot and it drops into bootloop. It only boots after reflashing the original boot.img
It seems, still, there is no way to root Android 11 with Miui 12.5.1 on POCO F2 PRO
Click to expand...
Click to collapse
Patched boot.img and working normally like before

Dadovvv said:
Patched boot.img and working normally like before
Click to expand...
Click to collapse
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.

Bogazicili90 said:
Did you formatted data or the internal storage after flashing the patched boot.img?
I read some suggestions to format data after rooting. I didn't try this since I don't want to lose all my settings and internal data.
Click to expand...
Click to collapse
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.

Dadovvv said:
I did clean flash new 12.5.1 fastboot rom, after first boot i flashed patched boot.img.
Click to expand...
Click to collapse
This is why I say it DOES NOT work. I don't have to format my data to only just root. I don't want to lose all my data. And I declared this on the starting thread. It doesn't work just with upgrading the MIUI. Before Android 11 it was working without formatting data.

Any news on this search yet?

HValenti said:
Any news on this search yet?
Click to expand...
Click to collapse
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.

Bogazicili90 said:
No solution. There is not a new version of Magisk that solves this bootloop issue. You have to format all the data after rooting with magisk to make it work. I'm using without root and TWRP.
Click to expand...
Click to collapse
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...

HValenti said:
Are you sure about formating data? I mean, are you sure that if you format the data (after flashing the patched boot) the phone will boot? Myself, I am not sure actually, as I have not seen it anywhere explicitly.
Unfortunately, according to Magisk news, any new version when eventually is published (maybe long enough), will have ditched the Magisk hide feature... So, maybe it is not worth to wait for newer version...
Click to expand...
Click to collapse
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.

Bogazicili90 said:
I'm not sure, I haven't tried it and won't try. I just read it on some comments. They claim that after formatting Data the phone boots normally.
Click to expand...
Click to collapse
I can understand you, I am in the same place.

HValenti said:
I can understand you, I am in the same place.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...-global-for-poco-f2-pro.4303453/post-85449319
Clean flash before not after.

I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).

harisdu95 said:
I'm currently on 12.5.2.0 (RJKEUXM), what I did was :
1) Installed the rom via LM recovery an dpatched boot img via magisk app
2) Installed magisk v22.1.zip (with adb to install recovery (fasboot flash recovery NAMETWRP.img)
3) boot recovery with adb (fastboot boot NAMETWRP.img)
4) In recovery, I installed magisk v22.1.zip). I didn't installed "no verify opt encrypt" as it bootlooped me in fastboot.
Now it is working great ( I didn't factory reset my phone or wiped any data).
Click to expand...
Click to collapse
thanks for the tips but:
what's LM recovery? link please
which rom is better for daily use?
what is a Dpatched you mean a magisk patched boot image?