Hi guys I was able to root my P10 using magisk and the new treble project on oreo very easily.
All credit goes to @topjohnwu as he's the creator of Magisk and this method all i'm doing is sharing his work and adding the boot image for the P10
Requirements:
Your PC
P10 ON OREO B360 (this only works on oreo if you try to do it on nougat you could easely brick your device)
Bootloader Unlocked (?)
ADB & Fastboot
I actually don't know if you need to have your bootloader unlocked as it's using the treble project to update the boot partition.
I had mine unlocked when i did this.
Step 1:
Get your boot image from update files (huawei update extractor > settings > uncheck the first 3 checkboxes) here i have the boot image from my VTR-L29C432B360
Install the latest Magisk Manager apk from here.
Step 2:
Open Magisk Manager, go to Settings > Update Channel > Custom Update channel with this link http://goo.gl/jefZKH
after that check if the latest magisk update is v15.4 (as the time of posting this guide)
if it says Invalid Update Channel you probably misspelled the link
Step 3:
Copy your boot image to your internal storage/sd card
Go on Magisk Manager > Install > Patch boot image file > Select the boot image on your internal storage/sd card
when it finishes go on your pc and pull the patched boot image to your desktop or desired folder. it will be stored on your internal memory/MagiskManager/patched-boot.img
Step 4:
Open cmd on the same folder as your patched boot image
Go to fastboot (Power-off then Vol+ and Power)
now on cmd type
Code:
fastboot devices
should come as response a serial number and fastboot
this means your device is connected to you pc and on fastboot
after that type
Code:
fastboot flash ramdisk patched_boot.img
it will flash the patched boot image
when it's done just reboot
and you're set!!
You'll have root with Magisk and pass safety net without a problem.
Friend, thanks for the information. Sorry you know how to install viper4android in B360
DarkPJV said:
Friend, thanks for the information. Sorry you know how to install viper4android in B360
Click to expand...
Click to collapse
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
D4XT3R said:
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
Click to expand...
Click to collapse
It would be fantastic.friend
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
smashedup said:
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
Click to expand...
Click to collapse
well the modified channel update is one that @topjohnwu modified for huawei's treble enabled phones like the P10 so that we wouldn't have any problem with safety net or flashing the boot partition but if it worked for you it might work for others too
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
samy0x said:
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
Click to expand...
Click to collapse
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
D4XT3R said:
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
Click to expand...
Click to collapse
Yes
Phone Locked
FRP Unlock
have you tried it again and worked? if not it only works with unlocked bootloader
D4XT3R said:
have you tried it again and worked? if not it only works with unlocked bootloader
Click to expand...
Click to collapse
Yes i tried again no solution i'll wait for sometime if no solution i'll unlock bootloader
I'm exploring that solution maybe : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
How did you do that
samy0x said:
How did you do that
Click to expand...
Click to collapse
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Jannomag said:
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
Click to expand...
Click to collapse
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
urbanboymne said:
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
Click to expand...
Click to collapse
Oh, of course. Sorry, I meant with "not flashing with TWRP" that I didn't need to flash the zip for v16 manually, just install it within the app. But of course you need to install 15.4 first.
meh , cant extract ramdisk.img from update.zip...
About magisk...is the root gone away finally fixed ?
on my old nova plus,when rooted whit magisk,we had to flash that darn patched boot img every 1-2 weeks in order to re have root again
is that finally fixed ?
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
Exactly the same for me... and passes safety net
---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------
Can we flash TWRP 3.1.1 after rooting with Magisk ?
Big thankyou it worked like a charm
Related
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse
SUCCESSFULLY ROOTED...
Just received my BL code and I'm so excited to root my P30 Pro. I will share my experience about rooting here.
Complete Guide with required tools for BL Unlocking & Rooting with Magisk. Thanks to @Athanatos81
I don't want to write whole thread here that's why just share direct thread link.
====================================================================================================
ROOTING GUIDE & TOOLS CLICK HERE
====================================================================================================
ROOT WITH BELOW MENTIONED STEPS:
i. BL Unlock code needed for BL Unlocking.
ii. Patch your RAMDIS with magisk 7.2.0 manager.
iii. Flash patched img with fastboot commands mentioned below.
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk magisk_patched.img
fastboot reboot
iv. Remove USB cable press volume + button until it boot.
That's it...Safety Net Passed
====================================================================================================
FIRMWARE UPDATE WITH EMUI FLASHER TOOL:
Successfully updated firmware with " EMUI Flasher 1.1 " tool.
EMUI FLASHER TOOL 1.1 LINK Click Here
====================================================================================================
SIDE EFFECTS OF ROOTING...!
+ Stock Phone app is not opening, force close.
+ Stock Google Message not receive or send any message, force close.
solution~) Backup your sms and contact first.
This solved messages issue :
adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*
Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery
- Root explorer not mount system as R/W even granted root permission, so we can't copy, past or delete files in system partition - No solution till now, Due to EROFS (Extendable Read Only File System) working on it.
==================================================================================================
I have received my BL code from this guy +375257585263 You can contact him on whatsapp.
Anybody who got BL code are welcome:highfive:
Thanks to
@topjohnwu - magisk developer
@gmanrainy (Team MT) - Huawei Firmware Finder
@worstenbrood - Huawei Update Extractor
@OldDroid - EMUI Flasher 1.1 tool developer
@ante0 - Fix Messages and Dialer in 9.1 [Root required]
Thanks,
goldybewon
Huawei P30 Pro 8/256
Looking foward to know about your acomplishment.
goldybewon said:
Just received my BL code and I'm so excited to root my P30 Pro. Now a days I don't have much time to backup all my data, may be after two or three days I will unlock my phone and trying to root. I will share my experience about rooting here.
Complete Guide for BL Unlocking & Rooting with Magisk. Thanks to @Athanatos81
I don't want to write whole thread here that's why just share direct thread link. There are many guide available on xda but I personally prefer this one because it's more detailed.
ROOTING GUIDE CLICK HERE
I have received my BL code from this guy +375257585263 You can contact him on whatsapp.
Anybody who got BL code are welcome:highfive:
Thanks to
@topjohnwu - magisk developer
@gmanrainy (Team MT) - Huawei Firmware Finder
@worstenbrood - Huawei Update Extractor
Thanks,
goldybewon
Huawei P30 Pro 8/256
Click to expand...
Click to collapse
That guide will likely not work, due to fastboot being disabled.
How much was the bl unlock code?
See my thread in this section. I've already tried this method several days before. Does not work. Seems like EMUI 9.1 is a lot different than EMUI 9.0
goldybewon said:
I will unlock my phone and trying to root. I will share my experience about rooting here.
Click to expand...
Click to collapse
Is the Google Pay works?
zhangyang_haha said:
See my thread in this section. I've already tried this method several days before. Does not work. Seems like EMUI 9.1 is a lot different than EMUI 9.0
Click to expand...
Click to collapse
Exactly. The OP shouldn't be making threads that make it sound like we have the ability to root when he even admits he's not done it yet.
https://forum.xda-developers.com/showpost.php?p=79681506&postcount=9
Solution is
Backup all, then factory reset. After reset don't allow phone to boot, immediately go to fastboot and flash recovery_ramdisk with magisk. Then reboot and wait for phone first init. It tells that root is found, press ok.
After that we hawe root and SMS working/QUOTE]
Might be worth trying for someone that has their bootloader unlocked and is willing to factory reset, provided the OPs link with instructions for creating the modified recovery_ramdisk works. I just ordered my code yesterday so I'm not expecting it until the end of the week to do any testing.
Recovery mode should still work, even if the phone starts boot looping. It's on a separate partition and downloads a fresh copy of the firmware from Huawei to install. It saved me a few times when experimenting in the early days of the P20 pro
Click to expand...
Click to collapse
@op - Did you get rooted?
Just Tried Again,
Extracted the Ramdisk from 153 (C185) Update file using Update Extractor
Patched using Magisk 19.3 - Magisk Manager
Flashed in Fastboot after a Factory Reset, Flashing went fine. No Errors.
Phone boots fine in Normal Mode, setup done - booted to System (Root Not available)
Turned off - Boot in Recovery Combination - Goes into Bootloop. After 3 Bootloops, Phone boots to eRecovery for Restore.
EMUI 9.1 doesn't support the Magisk patch method used for EMUI 9.0.
Any other ideas guys?
JazonX said:
@op - Did you get rooted?
Just Tried Again,
Extracted the Ramdisk from 153 (C185) Update file using Update Extractor
Patched using Magisk 19.3 - Magisk Manager
Flashed in Fastboot after a Factory Reset, Flashing went fine. No Errors.
Phone boots fine in Normal Mode, setup done - booted to System (Root Not available)
Turned off - Boot in Recovery Combination - Goes into Bootloop. After 3 Bootloops, Phone boots to eRecovery for Restore.
EMUI 9.1 doesn't support the Magisk patch method used for EMUI 9.0.
Any other ideas guys?
Click to expand...
Click to collapse
Fastboot works once the bootloader is unlocked? I thought it was locked or disabled.
---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------
I can help experimenting since the recovery partition seems quite save. However, how do i make a backup of everything? All apps, their settings, icons on home screen etc?
Would this work? https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
Hell everyone thanks for sharing your experience here. I want to clarify that I'm not a developer, what I have learnt from xda I shared here. I am a guy who wants to root his phone no more mods needed. These are the experience we have to share with each other. Will will find a way... I want to be rooted at any cost.
See my attachment, there is a hope. Magisk creator is trying hard for EMUI, every new build comes with EMUI bug fixes.
Thanks again for sharing rooting experience:good:
goldybewon
borgqueenx said:
Fastboot works once the bootloader is unlocked? I thought it was locked or disabled.
---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------
I can help experimenting since the recovery partition seems quite save. However, how do i make a backup of everything? All apps, their settings, icons on home screen etc?
Would this work? https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
Click to expand...
Click to collapse
Nah, Bootloader was always accessible to me. There was no issue with it.
Try Uninstalling Hisuite and installing Google ADB. Hisuite installs a modified version called HDB which might mess up things sometimes.
For a complete backup without root, HiSuite is the only way.
OK, Tried with 7.2.0 and it worked!
Root is working guys. Safety Net is Passed!
Success Story Posted here!
Does anyone knows how to install viper sound or any other app that actually and truly makes it louder?
JazonX said:
OK, Tried with 7.2.0 and it worked!
Root is working guys. Safety Net is Passed!
Success Story Posted here!
Click to expand...
Click to collapse
Do you add cards to Google Pay?
s_b81 said:
Do you add cards to Google Pay?
Click to expand...
Click to collapse
Google pay not work with bootloader unlocked
sug010 said:
Google pay not work with bootloader unlocked
Click to expand...
Click to collapse
for this install magisk.
that's why I asked: Do you add cards to Google Pay? for the pharse "Safety Net is Passed! "
Flash update_full_base.zip (FULL OTA) firmware with EMUI Flasher v1.1
Hy guys,
Can someone with unlocked bootloader and root install EMUI Flasher and flash the update_full_base.zip (FULL OTA) on device and report if it's working? Below you'll find the MEGA mirror for latest firmware v.176 downloaded from Firmware Finder.
MEGA link for VOG-LGRP2-OVS 9.1.0.176 - MD5 checksum value 4dbe96c1b4fbc29aaa67cae2f3778517
LINK for [GUIDE] Manual updating/Firmware Collection/Rooting and EMUI Flasher ( thanks @OldDroid )
BEFORE proceding, make sure to patch RECOVERY_RAMDIS.img from v176 firmware while you are rooted on current firmware version.
REMEMBER that after succesfull firmware update you'll have to reflash the patched_boot.img to recovery_ramdisk (via fastboot) to regain root access.
Your userdata should stay intact - at least that was it back when i flashed on P20 Pro
s_b81 said:
for this install magisk.
that's why I asked: Do you add cards to Google Pay? for the pharse "Safety Net is Passed! "
Click to expand...
Click to collapse
Yeah mb
But now I'm rooted, and you can add cards but you can't confirm coz messages crash and you can't receive sms...
JazonX said:
OK, Tried with 7.2.0 and it worked!
Root is working guys. Safety Net is Passed!
Success Story Posted here!
Click to expand...
Click to collapse
But why your guide is referring to Mate 20 Pro?
October security patches released...
https://dl.google.com/dl/android/aosp/blueline-qp1a.191005.007-factory-c36610c6.zip
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
4.3 MB from the C3 update.
After the C3 update I had an improvement in the battery's life but after few days was the same. I hope this will better this time.
Edit : multi-tasking freeze is here again...
sliding_billy said:
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
Click to expand...
Click to collapse
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
Click to expand...
Click to collapse
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
Click to expand...
Click to collapse
Good deal. I just never leave Canary for my Pixel 3 and Pixel 3 XL despite having other devices on stable or Beta.
what Google Play System update patch level are you guys on? I'm back to August, 1 from September, 1 after installing the October OTA.... so what's going on here?
Installed yesterday. Now wireless provider signal only shows as 4G, no LTE.
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
gmmurphy said:
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
Click to expand...
Click to collapse
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
dcarvil said:
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
Click to expand...
Click to collapse
Did you uninstall all the modules before doing this?
georgs_town said:
Did you uninstall all the modules before doing this?
Click to expand...
Click to collapse
No, I did not uninstall the modules, I just followed the instructions in the tutorial.
I was able to flash the factory image by running the "flash.bat" script with "-W" removed. Security update is dated Oct 5, Google Play system is dated Sept 1. Just to be safe, I uninstalled Cerberus before running the script as Cerberus caused me issues transitioning from Android Pie to Android 10 last month.
Other than Cerberus, I only have magisk for rooting, no modules loaded, no edXposed. I re-routed using the latest Canary build for Magisk, patching the boot.img and then flashing the magisk_patched.img in fastboot mode.
So I'm having another major problem. When I updated to 10 from 9 running dirty unicorns, everything flashed fine except for the image update zip. I remember it had something to do with the active slot but I cant remember for the life of me what I did last time to get the image to flash. Currently when I run flash all bootloader and radio flash fine, but flashing the image zip my phone boots into the fastbootd recovery screen and fastboot command screen shows fastboot: error: command failed. Sending sparse product b FAILED.
Any help would be greatly appreciated. Right now I'm stuck in fastboot on my phone.
Edit: I just did a factory wipe and it's flashing fine now. I'm guessing it had something to do with the magisk patched boot img I was using. I really don't know what the problem was.
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Ipeacocks said:
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Just download the full factory image, edit the flash all file to remove the -w, and then flash that in fastboot mode. Make sure you save the flash all file and the -w is removed before you use it. Trying to take the ota on a rooted device doesn't work well.
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Ipeacocks said:
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Click to expand...
Click to collapse
Yes, you'll loose root but your data will all be there. You'll have to move a copy of the stock boot.img file to your device, let magisk patch it, then move the patched file to your pc and flash that with fastboot. Almost all of us do this process with each update.
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Ipeacocks said:
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Click to expand...
Click to collapse
No. Download the factory image to your pc and extract it, it's a zip file. In there you'll see a flash-all.bat file. Edit that. I use notepad ++. Then save it and just double click on the edited file (I'm assuming your using a windows pc). There is also another zip file you'll find after you've extracted the factory image. Extract that too and you'll find the boot.img file you'll need to patch with magisk for root.
Edit, sorry, I didn't look at the image you uploaded that closely. It is the -w I was referring to.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed