Related
This guide provides all the steps and patches required to root the Stock system and having Xposed installed while maintaining SafetyNet (Android Pay, Pokemon Go, etc) compatibility. There are some problems of this method that Magisk is supposed to fix, however the latest Magisk v10 is not supporting our stock ROM yet.
The prerequisites of this guide is to have the bootloader unlocked and TWRP recovery.
DOWNLOADS
The recipe require the following ingredients to be downloaded to your internal or external storage:
1. TWRP 3.0.3 (This is the last release at this moment). more info in the Official Thread. Thanks to @jcadduono . TWRP 3.0.2 can't succesfully flash SuperSU 2.79
2. Default Stock ROM for your phone (Required only if you have modified your system or boot partition). You can download them from this thread. Thanks to @DrakenFX . You can alsouse any other custom ROM based on stock such as ZADMix or HelsAx7 SubMix (both tested).
3. SuperSU v2.79. more info in its official thread.
4. SUhide 0.55. More info in its official thread. Thanks to Chainfire.
5. SafetyNet-KCAL Kernel patch, thanks to @jcadduono also for this one!
6. Xposed v86.2 So far only this version is compatible with SUhide.
7. Material Design Xposed Manager app by DVDandroid. More info about this release in its official thread.
8. Root Switch 1.3.3.2 app. Thanks to shakalaca. More info in its official thread.
INSTALLATION
1. Do a backup of your system, I recommend Boot+System+Data partitions. The next steps will modify at least your boot and data partitions, and some Xposed modules will modify also your system partition.
2. If you already have TWRP 3.0.3 then just boot to recovery and proceed to step 3. If you are still using TWRP 3.0.2 please upgrade to the latest TWRP 3.0.3 and reboot to recovery again.
3. I recommend to flash the default Boot and System Partitions and reboot directly to recovery. You can also use any other custom ROM based on the stock ROM such as ZADMix or HelsAx7.
4. All this step must be done without leaving TWRP. Flash SuperSU 2.79 adding also the zips for SUhide 0.55, Xposed v86.2 and the SafetyNet Kernel patch in that order. They must be flashed together. Without leaving TWRP, navigate from the main menu to Advanced > Terminal, introduce the command reboot disemmcwp and the system will reboot by itself once or twice while configuring the settings for SuperSU. Do not be alarmed.
5. Install Xposed Manager and Root Switch apps.
6. Now you have your system fully rooted and you can now install Xposed modules. However you will see the test app SafetyNet Helper reporting a validation failure. Do not worry about it anymore! When you want to initiate a SafetyNet sensitive application (Android Pay or Pokemon Go among others), just open Root Switch and disable root, no need to reboot. SafetyNet will pass and all your apps will work. You can see that Xposed continue working even after disabling root since it was started before. Do not forget to enable root again otherwise new apps requiring root won't load.
Magisk v10+ promises auto root hide per app, but sadly our stock ROM is not yet supported and the method psoposed here requires the user to disable root before loading any SafetyNet protected app.
Enjoy
Reserved for future Magisk guide.
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
H0lmEd said:
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
Click to expand...
Click to collapse
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Oki said:
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
Click to expand...
Click to collapse
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
tron1 said:
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
Click to expand...
Click to collapse
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Oki said:
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Click to expand...
Click to collapse
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
tron1 said:
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
Click to expand...
Click to collapse
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Tikerz said:
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Click to expand...
Click to collapse
For some reason Magisk is not compatible with the Axon 7 kernel. Not yet. This is why it is so complicated and requires a guide. Last time I tested this was yesterday using Magisk v10.2 and phh Superuser r2, and they still failed to root the system.
le_cactus said:
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Click to expand...
Click to collapse
Yes you can try to begin with step 4 with SUhide on. It should work. However I recommend you to upgrade to TWRP 3.0.3 and do the whole step 4.
Gr8. Thanks.
Cheers,
/Cacti
Oki said:
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
Click to expand...
Click to collapse
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
H0lmEd said:
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Oki said:
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
Click to expand...
Click to collapse
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
corpdecker said:
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Click to expand...
Click to collapse
Don't install beast mode yet, from my experience all the steps from op worked fine until I flashed beast mode and it broke safetynet.
lexman098 said:
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Click to expand...
Click to collapse
Are you using TWRP 3.0.3? SuperSU 2.79 installs fine and in systemless mode when flashed with the latest TWRP. TWRP 3.0.2 can't flash it properly.
Yes this method has been tested, not only with stock Roms, but also with ZADmix.
If you are doing a complete cleanup before flashing the ROM, boot into system at least once after installing the ROM so the data tree structure is setup. You actually don't need a full cleanup.
Kingo64 said:
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
Click to expand...
Click to collapse
H0lmEd said:
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
Please ensure you have flashed the right stock ROM for your unit. I have modified Ingredient 2 in the OP since it was highly misleading. Ensure you have unlocked bootloader, TWRP 3.0.3 and flash the right ROM for your system: ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip and ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip. And boot to the system at least once before continue to the rest of the procedure.
Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse
Hey I just picked up this phone and decided I would like to maximize it to its fullest potential, and root it as I have done with previous phones. This ones giving me a hard time, and I just can't seem to find the proper info for it.
I have unlocked the bootloader, flashed TWRP 3.1.1 and want to gain root access. I have followed several guides, used every possible one-click unsuccessfully, and tried installing SuperSU with TWRP. After I reboot, SuperSU is installed. I'll open it up and it tells me the binaries are occupied. I've tried downgrading and updating the binaries but I get errors. (I believe this is because it must be rooted first - of course.)
So I'm stuck unable to get any further. If anyone has any suggestions, I would appreciate it. Is this phone with this configuration unrootable? There must be a way if I have recovery right?
Asus Zenfone 4 Z01KD/ZE554KL
Android Nougat 7.1.1 - 14.1060.1708.63 (NOT 1708.70)
TWRP 3.1.1 installed
One thing I have not tried is using Magisk. When I try it, it stops because I already patched with SuperSU (even though it failed). I never backed up before I did it with SuperSU I really thought it would work.
I read of people doing it with Magisk after updating to Oreo. I want to give that a try but I can't OTA or flash from TWRP. All attempts result in error 7.
I can't find a stock recovery to flash to do the update either. Is there a way to undo this, OTA and repatch with Magisk? Even if I don't bother updating, I would like to find a stock image to flash so I can try patching with Magisk.
Stock rom recovery.img anywhere? Am I alone?
i dont own this device but i read this and it might apply to you. also did you flash the supersu uninstaller and them try magisk?
https://forum.xda-developers.com/zenfone-4-2017/development/twrp-3-1-zenfone-4-2017-ze554kl-t3690349
hey i have the zenfone 4 ze554kl i updated it to android 9 unlocked the bootloader and got Twrp running but not correctly and i can't root the phone .....
As SuperSU causes nothing but trouble in terms of being able to use android pay, many apps, and the like, I wanted to move over to magisk, but I have SuperSU by virtue of a flashed boot image, so no matter what I try I can't get rid of superSU (even been rooting around in the system files to try and get rid of it and it just comes back).
Is there a magisk boot image for the E2303, and if not does anyone have a stock boot.img for the e2303 on hand, as I have managed to lose mine
Flobbity said:
As SuperSU causes nothing but trouble in terms of being able to use android pay, many apps, and the like, I wanted to move over to magisk, but I have SuperSU by virtue of a flashed boot image, so no matter what I try I can't get rid of superSU (even been rooting around in the system files to try and get rid of it and it just comes back).
Is there a magisk boot image for the E2303, and if not does anyone have a stock boot.img for the e2303 on hand, as I have managed to lose mine
Click to expand...
Click to collapse
Open supersu app Go to>setting's>select Full Unroot (clean up for permanent unroot)
Or do a clean install ( reflash ftf on flashtool ) then go get sorted with magisk
You can get everything you need to root with magisk for your M4 by LOOKING HERE.
Or checking out HERE.
Good luck
So, there are a few different methods to deal with Magisk when you want an OTA - but the question is, just how far do we have to go when it comes to the S9/S9+?
Will OTAs fail if you have TWRP installed? Will OTA's fail if you've ever done anything to your system partition? (I've installed an app and converted it to a system app)
If they're really not that sensitive, then my understanding of the procedure is this:
1. Uninstall the Magisk Manager app as well as any apps you installed and converted to system apps.
2. Boot to TWRP and flash the Magisk Uninstaller.
3. Boot normally.
4. Re-enable updates in Developer Options and check for the OTA update.
5. Let the OTA finish updating.
6. Boot to TWRP and flash the Magisk Installer.
Can someone tell me if my procedure is correct, or if not, what I'm missing?
Thanks!