Moto E4 Guide To Rooting Mediatek Variant SKU XT1760 - Moto E4 Guides, News, & Discussion

About :​This guide is only meant for mediatek variant of Moto E4 which is SKU XT1760. Only phh's Superuser able to root Moto E4 :fingers-crossed: . SuperSU & Magisk isn't fully compatible with Moto E4 and failed to root this device .Unofficial Xposed works with Moto E4 :laugh: but not Xposed module's (force close error !)
Procedure :
Step 1 : Installing Recovery
- Install Ported TWRP recovery first
- if you haven't installed it yet ! Get it from below thread.
Thread link :
https://forum.xda-developers.com/moto-e4/development/available-moto-e4-ported-twrp-recovery-t3656286
Step 2 : Opening TWRP Recovery
- Boot into recovery
- Install phh's supersu zip file
- Select storage and locate to zip file
- Swipe to install
- Done
Download link for phh's superuser zip file:
http://www.mediafire.com/file/8h4k4enel9uh4u7/superuser.zip
Step 3 : Disable dm-verity and Force encryption
This step is crucial else you won't able to boot into system again !
It has two steps to follow whether select my modified boot image to disable
dm-verity and force encryption else use this no-verity-opt-encrypt zip file
to disable dm-verity and force encryption.
If you were going through Boot image process !
Download link for Kernel(Boot image) :
http://www.mediafire.com/file/y4160sl13ibyx8q/boot.img
- Boot your device into recovery
- Select Reboot
- Choose bootloader
- Now attach your device with laptop/desktop
Type this fastboot command :
- "fastboot flash boot boot.img"
- Wait until process finish
- Now disconnect
- Press and hold power button
- Release when you see full black screen
If you were going through zip file flashing process !
Download link for zip file :
http://www.mediafire.com/file/m0w6zu83am6z38i/no-verity-opt-encrypt.zip
- Reboot into recovery again
- Install no-verity-opt-encrypt zip file
- Reboot into system
Step 4 : Installing phh's Superuser Application
- Install phhsuperuser app (Get this app from Googleplay)
- Within phhsuperuser app < open settings
- Superuser access set to Apps and ADB
- Done
Credits :
@phhusson
Thread link :
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394​

add link of this thread there in your twrp recovery thread,

drganbds said:
add link of this thread there in your twrp recovery thread,
Click to expand...
Click to collapse
already added in step 1

Kartik bro kindly organize all of your thread from unlocking bootloader, flashing twrp and rooting our mediatek variant in a single thread because it's not confusing as it is in various sections.....thanks and I obey for the time which you spend here...

drganbds said:
Kartik bro kindly organize all of your thread from unlocking bootloader, flashing twrp and rooting our mediatek variant in a single thread because it's not confusing as it is in various sections.....thanks and I obey for the time which you spend here...
Click to expand...
Click to collapse
ok.
So, i will make a single thread in Guide & news section.
:highfive:

Kartik first of all thanks for mediatek variant works and I have successfully unlocked my bootloader and flashed twrp recovery...now I have some doubts.
1. After flashing phh's superuser do we really need to flash boot.img? Or simply install no Verity opt zip file?
2.After flashing twrp recovery is that backup of stock ROM working?
3.Do we need to install no Verity opt zip everytime when we reboot from twrp recovery?
4.After unlocking my bootloader when I reboot the start up screen shows some "orange state" "your bootloader unlocked and can't be verified" is that normal?

drganbds said:
Kartik first of all thanks for mediatek variant works and I have successfully unlocked my bootloader and flashed twrp recovery...now I have some doubts.
1. After flashing phh's superuser do we really need to flash boot.img? Or simply install no Verity opt zip file?
2.After flashing twrp recovery is that backup of stock ROM working?
3.Do we need to install no Verity opt zip everytime when we reboot from twrp recovery?
4.After unlocking my bootloader when I reboot the start up screen shows some "orange state" "your bootloader unlocked and can't be verified" is that normal?
Click to expand...
Click to collapse
@drganbds
about verity it has two simple steps:
if you were going through zip file process you may need to flash no verity zip many times for disabling dm-verity & force encryption (when using rooting method other than this). if you want to know how to use zip file, simply flash phh's superuser than reboot to recovery again and flash no verity zip file. thats it.
if you want a permanent solution than use my modified boot image. how to install... first flash boot image in fastboot mode than install phh's superuser.
backup of stockrom working well and the warning message is normal, nothing to worry.
once you flash no verity zip file you don't need to flash it everything time in twrp in order to boot into system.
if you face any problem simply flash stock boot image

Ok as for as I understood if I flash your modified boot image first then no need to flash no Verity everytime when I install something in twrp right and it's a permanent solution otherwise we need to depend on no Verity zip everytime?

drganbds said:
Ok as for as I understood if I flash your modified boot image first then no need to flash no Verity everytime when I install something in twrp right and it's a permanent solution otherwise we need to depend on no Verity zip everytime?
Click to expand...
Click to collapse
yes no need to flash no-verity-force-encrypt file every time directly install phh's superuser zip file when using boot image.
with verity zip you need to flash it once after rooting, also if you unroot your device and again going to root you have to install no verity file after rooting.
Remember if you flash boot image other than this plus you will loose root & permanent sol. of dm-verity fix.

Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.

drganbds said:
Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.
Click to expand...
Click to collapse
yes :fingers-crossed:

drganbds said:
Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.
Click to expand...
Click to collapse
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
kartik verma said:
yes :fingers-crossed:
Click to expand...
Click to collapse
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser because in Kyle Qualcomm thread it's written as just flash phh's superuser, no need to flash no Verity file even again and reboot system that's it.

drganbds said:
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser.
Click to expand...
Click to collapse
3rd file is the actual boot image.

drganbds said:
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser because in Kyle Qualcomm thread it's written as just flash phh's superuser, no need to flash no Verity file even again and reboot system that's it.
Click to expand...
Click to collapse
you need to flash as i already tested else you won't able to boot into system !

kartik verma said:
you need to flash as i already tested else you won't able to boot into system !
Click to expand...
Click to collapse
Sorry for asking too many times but I need clear my doubts....if I flash your boot image after install of superuser then no need to flash no Verity zip right? Or I need to flash boot image and install no Verity zip both before I reboot?

drganbds said:
Sorry for asking too many times but I need clear my doubts....if I flash your boot image after install of superuser then no need to flash no Verity zip right? Or I need to flash boot image and install no Verity zip both before I reboot?
Click to expand...
Click to collapse
after installing boot image < install phh's superuser zip file
that's it.

kartik verma said:
after installing boot image < install phh's superuser zip file
that's it.
Click to expand...
Click to collapse
Done all superbly...took backup of rooted ROM and unroot ROM...next waiting for custom ROM...

drganbds said:
Done all superbly...took backup of rooted ROM and unroot ROM...next waiting for custom ROM...
Click to expand...
Click to collapse
:highfive:

kartik verma said:
:highfive:
Click to expand...
Click to collapse
Kartik twrp 3.1.1 usually take backup files in .sha2 and .win000 formats? Not in zip?

drganbds said:
Kartik twrp 3.1.1 usually take backup files in .sha2 and .win000 formats? Not in zip?
Click to expand...
Click to collapse
let me check first

Related

How do I update the ROM OTA with rooted device?

Hi guys,
I'm on an outdated version of the global beta ROM and have received an OTA notification.
Unfortunately I can't run this as I'm rooted.
Please could you tell me the easiest way of updating the ROM without wiping everything and maintaining root?
Many thanks,
Andy
After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all
sarthakwarlock said:
After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all
Click to expand...
Click to collapse
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?
andypa1 said:
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?
Click to expand...
Click to collapse
Reflash Twrp from fastboot.
I've just found in a thread elsewhere:
"It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it"
I don't really understand this, or understand / remember how I managed to flash the global beta rom in the first place?!

Pixel 2 XL Root [Going Mad About]

Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
[Edit]
Theese are the steps i take
-flash recovery twrp (ok)
-reboot to recovery (ok)
-flash magisk v18 (loop)
megamarini said:
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
Click to expand...
Click to collapse
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
djcrystals said:
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
Click to expand...
Click to collapse
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
megamarini said:
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
Click to expand...
Click to collapse
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Badger50 said:
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Click to expand...
Click to collapse
Thank You mate, when I'll get home I'll try to follow yor steps and I'll let you know. Any suggestion about kernel on stock firmware? ElementalX it's ok?
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Sui77 said:
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Click to expand...
Click to collapse
Tryed everything but nothing works..
megamarini said:
Tryed everything but nothing works..
Click to expand...
Click to collapse
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Az Biker said:
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Click to expand...
Click to collapse
SOLVED
The only way (for me) to root my Pixel 2 XL is follow theese steps:
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Source: XDA Post
Thank you so much to everyone who tried to help me!

TWRP

How can i Install TWRP in PIE v10.0.7 with Magisk root? please show me how ?
I'm also need to know what is the proper and right way to install twrp (offain ver.) There's so many conflicting and difference opinion in the thread...its so confusing which one is the right step...why do i need to fastboot twrp img first then flash the trwp installer zip? Do i really need to flash disable force encryption fix? Why is it necessary? Why can i just fastboot flash the twrp img like any other phone?
You can probably install in any order but I did Magisk first. You must have an unlocked bootloader.
Use the standard Magisk process:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
TWRP also has a standard process:
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
I had a bootloop after installing TWRP that I fixed by reinstalling Magisk (fastboot the patched image and install again). Other people seem to have success flashing an older aboot image.
If you need more information you're going to have to be clearer about what you have now.
The phone seems reasonably brick-proof. If you can get to fastboot you can restore a fastboot ROM.
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
secondkai said:
why do i need to fastboot twrp img first then flash the trwp installer zip?
Click to expand...
Click to collapse
TWRP lives in boot, not a separate recovery partition because this is an A/B phone.
TWRP installs by patching boot but you cannot do that from fastboot. So you boot into TWRP and patch boot from there.
secondkai said:
Do i really need to flash disable force encryption fix? Why is it necessary?
Click to expand...
Click to collapse
I didn't do it. But I'm on stock.
I think it's mostly a problem for custom ROMs and GSIs. With encryption on they cannot read the data partition.

Unable to encrypt after root

Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear

Question Magisk is not installing

The magisk apk, when flashed in TWRP flashes as normal but the app does not show up in the ROM, and the phone doesn't get rooted.
I had this problem on both ArrowOS and Syberia OS now, and I clean flashed both times directly from MIUI.
Can anyone help me out with this?
Install the magisk app
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
zhyylz0201 said:
Install the magisk app
Click to expand...
Click to collapse
I already tried, this happened -
Iceman66 said:
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
Click to expand...
Click to collapse
It didn't work either, when I open magisk app it shows this -
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Iceman66 said:
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Click to expand...
Click to collapse
No change
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Iceman66 said:
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Click to expand...
Click to collapse
I am using a custom kernel, will that change the process?
You need to reflash the custom kernel again after flashing the patched boot.img, but first check if your phone is rooted. (check in magisk app or install a root check app.)
The boot backup that I took before I flashed my custom kernel is the one that needs to be patched right?
If this isn't the case, can you guide me on how to get the boot.img? I only see payload.bin in my ROM.zip .
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Dhruv.m said:
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Click to expand...
Click to collapse
You have to patch the boot IMG with the TWRP already flashed, our phone doesn't have a recovery partition, so it's saved in the boot partition and installing Magisk from TWRP deletes the recovery, here is a good tutorial:
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com

Categories

Resources