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
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!
Hello,
yesterday I got a notification to update Magisk to v.21.3. I did it directly with Magisk Manager.
Since then I'm having problems with some apps and I notice that a new version of Magisk was release just to fix this problem.
When I try to install the v.21.4 with the Magisk Manager there is an option unchecked but I do not know if I have to check it or no.
Keep AVB 2.0/dm-verity
I do not know what is this. When I update to v.23.1 I did not have that option, was direct but now when I want to update to 21.4 from Magisk Manager I have this option and I do not know what to do.
Thanks
I assume nobody answered you because you could have just googled it.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com
Waking up with a sleepy head I wanted to swipe the new version notification away, but didnt swipe well enough and it actually upgraded. I need to downgrade to v23 again but for whatever reason, its not working. Here's what I tried:
1. Reboot to fastboot and do fastboot boot magisk_patched.img (boot img with magisk 23 I use after OTA's). This boots but its not rooted. Magisk mgr is 24 though.
2. Rebooted to system, uninstalled Installed magisk manager 24, rebooted and retried the above. Installed Magisk mgr 23. No root.
I then unpacked the latest full oos 11 for my phone with payload_dumper, copied the boot.img to my phone and patched it using magisk manager 23. Copied it back to the PC.
retried step 1. No root.
Rebooted to fastboot again, checked current slot, its A.
fastboot flash boot magisk_patched.img (the new one I patched in the step above).
Rebooted, no root.
What am I supposed to do to get Magisk 23 back on my phone?
The reason is I'm dependent on riru/lsposed for a couple of xposed modules. If I disable zygisk in magisk 24 I won't have root hide, if I enable that, riru/lsposed isn't working.
Thanks for the help!
Yeah I had a similar issue on A12 rom, Magisk 24 just doesn't allow me to pass safety net due to Google play services in Magisk 24 deny list unselects after a reboot, so downgrading to 23 which just works after using hide list.
I had to disable and remove any modules, unhide Magisk 24 then restart.
Use Magisk 24 uninstall in the app and restart.
Install Magisk 23 and Install to boot image file to payload Boot.img, restart to Fastboot and flash as you did.
Then again in Magisk install select Direct Install then restart.
Reapply Magiskhide to apps google pay/services etc restart and check root.
I still have an issue with Magisk hiding the app installs the proxy app but it doesn't open so isn't working, so still working on this. Root is working tho with the above.
Thanks, I still cant get it to work though.
I can patch the boot.img, but when I try to boot it I don't get root.
When I flash and boot it, there still is no root available.
Possibly i had the same issue, no root after flashing the 23-modified boot image. I solved it by, upgrading the app to 24.3, patch the boot image, reboot to fastboot, flash it, reboot it so i was back at Magisk 24.3 Then i did a full uninstall of Magisk, via the app. Then installed app v23. Patched the boot image etc as per https://topjohnwu.github.io/Magisk/install.html#patching-images
Key here was, i think the full removal of Magisk 24 before downgrading.
Hello,
Is it possibly to OTA Update a rooted Nord2 5G (DN2103) without TWRP without data loss ?
I rooted it with patched magisk boot image with DN2103_11_A.14 found here on XDA.
Tried OTA update for SN2103_11.A.16 from the phone menu, but got error from updater:
"Could not update: Verification problem" (translated by me, the original english message may be different)
I reverted to stock boot.img but the update fail again with the same error.
Now I am back with the magisk's patched one with root.
Which scenarios I have to update to the A.19 without lost data and without need to install TWRP.
Thanks.
Updated: March 28, 2022
Perhaps I am a bit late to respond, but for future users running into this issue (including myself lol), you first need to install TWRP, otherwise the following instruction won't work. Since you're rooted, you can install TWRP as well (and its really not hard to do)
for DN2103 you have to download the OTA update zip, boot image and vbmeta, see:
[STOCK][DN2103][EU] Incremental update packages & Boot images
Hi All, Below you can find a couple of incremental update packages that you can use for updating from various versions of your device. Incremental update packages These can be installed using TWRP by following this tutorial...
forum.xda-developers.com
After you downloaded the correct files, do the following:
boot into TWRP and flash the boot image corresponding to your update.
(optional) by flashing the boot image, you lose root. to prevent that, you can patch the boot image first with the magisk app. you can always do this step after updating, in case you forget it.
!!! some updates do not have boot image.
flash the <ota_update>.zip
flash the vb.meta image
reboot phone normally
Also, before doing all this, i recommend (temporarily) turning lockscreen security off, in case something goes wrong, you can always recover data then since the phone won't be encrypted.
Thank you, for the answer.
This is the correct way to do update.
Best,