Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
tuskan_supa said:
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
Click to expand...
Click to collapse
superminnu said:
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
Click to expand...
Click to collapse
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Are you on the Indian build or EU build?
tuskan_supa said:
Are you on the Indian build or EU build?
Click to expand...
Click to collapse
Indian
KartikBapna said:
Indian
Click to expand...
Click to collapse
I did successfully on the EU build not on Indian. I guess you should wait few days maybe someone will try and figure it out.
KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Isn't flash Magisk will always disable dm-verity?
Never_Sm1le said:
Isn't flash Magisk will always disable dm-verity?
Click to expand...
Click to collapse
It didn't disable it in my POCO....
KartikBapna said:
It didn't disable it in my POCO....
Click to expand...
Click to collapse
And now I realize the problem in you answer. Why did you need to write into the system partition?
Never_Sm1le said:
And now I realize the problem in you answer. Why did you need to write into the system partition?
Click to expand...
Click to collapse
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
KartikBapna said:
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
Click to expand...
Click to collapse
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Never_Sm1le said:
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Click to expand...
Click to collapse
I don't want any free space just want to remove bloatware and install some apps in system like appninja's app
KartikBapna said:
I don't want any free space just want to remove bloatware and install some apps in system so like appninja's app
Click to expand...
Click to collapse
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Never_Sm1le said:
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Click to expand...
Click to collapse
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
KartikBapna said:
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
Click to expand...
Click to collapse
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Never_Sm1le said:
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Click to expand...
Click to collapse
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
KartikBapna said:
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
Click to expand...
Click to collapse
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Never_Sm1le said:
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Click to expand...
Click to collapse
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
KartikBapna said:
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
Click to expand...
Click to collapse
Try my way: boot TWRP then flash TWRP.img from TWRP. Reboot to recovery again then flash Magisk zip. Flash patched boot.img is unnecessary, like Topjohnwu said it's only for devices without TWRP. Beside if you want to use the patched method, you must patch the stock recovery image not TWRP.
Related
Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!
Edit: Screenshots
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then
joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick
dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always
Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?
dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me
Yup that's it
joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?
Maybe someone will upload the full rom?
anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?
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.
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
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
zioloiso said:
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
Click to expand...
Click to collapse
Yes, this here is that stock recovery WITH ADB ENABLED.
iruiz2 said:
Yes, this here is that stock recovery WITH ADB ENABLED.
Click to expand...
Click to collapse
default recovery is without ADB Enabled?
zioloiso said:
default recovery is without ADB Enabled?
Click to expand...
Click to collapse
no stock recovery does not come with module enabled...you can try it yourself just boot to recovery and try adb shell
thats why i did it.
parag60288 said:
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
believe it should its just a recovery, i believe the ROM localization is where the real difference is...the stock recovery eitherway comes in some chinese and english...no indian language.. and in the end you can still reflash stock if you need to do anything there with it. Eventhou i am flashing only through bootloader...never really used it except adb shell
killswitx said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
Click to expand...
Click to collapse
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
bynarie said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
reboot into recovery u can use as well:
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
In theory, we should be able to make a backup of our own boot.img with this?
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
I just DD'd boot.img. This seemed to work for backing up partitions.
Recovery images don't differ across variant models do they?
This would work on global version for instance?
shorty1993 said:
Recovery images don't differ across variant models do they?
This would work on global version for instance?
Click to expand...
Click to collapse
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
grandpajiver said:
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
Click to expand...
Click to collapse
Please do. Would rather use the global if possible.
shorty1993 said:
Please do. Would rather use the global if possible.
Click to expand...
Click to collapse
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
grandpajiver said:
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
Click to expand...
Click to collapse
Are there differences between the Global and EU recoveries?
iruiz2 said:
Are there differences between the Global and EU recoveries?
Click to expand...
Click to collapse
wouldn't say there ist much difference.. its just recovery
Sent from my [device_name] using XDA-Developers Legacy app
obol2 said:
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
Click to expand...
Click to collapse
Can you please explain me how you did it ?
samyhaff said:
Can you please explain me how you did it ?
Click to expand...
Click to collapse
Boot into recovery, go in cmd and type adb.
type
dd if=/dev/block/bootdevice/by-name/boot_a of =/data/media/0/nameoffile.img
dd if=/dev/block/bootdevice/by-name/boot_b of =/data/media/0/nameoffile.img
patch one of them in magisk manager, fastboot boot patched img, direct install magisk in magisk manager
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?