Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
You have to install the Magisk zip with TWRP then the Magisk manager apk.
@sp4r3h did you manage to get it working?
@ashyx can you give me some more details?
This is what I tried.
1. Restore stock firmware
2. Flash TWRP
3. Choose Read Only
4. Install zip - Magisk
5. Reboot
Then I get the verification failed error. But from my understanding.. if I use your dm-verify patch then I can't pass SafetyNet?
Which kind of negates the point of magisk?
Thanks for your time.
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
The manager was removed from the appstore. I'll try manually installing an APK.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
If I try patching the Magisk then I get the verification failed. If I patch the dm-verify then I can't pass SafetyNet.
Any ideas?
Magisk 12 can't pass SafetyNet anymore.
I also tried the beta Magisk 13.0 but I ran into the same error, so I can't even check if it can pass ...
Follow instructions in first post (in TWRP thread) and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
That works for me.
napx said:
Magisk 12 can't pass SafetyNet anymore.
Click to expand...
Click to collapse
Google Tweaked Some S**ta again
So What you Gotta do is -
1. Goto Magsisk Manager Settings
2. Enable Core Only and Magisk Hide and select the app (Also Disable the other two adblocker and BusyBox)
3. Reboot
Worked for me (Verified Snapchat and Then Undo all got root back)
But I did one my S4mini
I was just surfing and saw the post and Share it with you guys
Magisk
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
Well, I also like to try magisk because SU does not work proper. Is there a way to uninstall SU
without a wipe in TWRP ??
Hi. This might be interesting for ALL.. After me Tab hangs, I downloaded the latest OFFICIAL ROM from Samsung,
in my case "DBT-T825XXU1AQF3-20170713092645.zip"...
Extract and place AP, BL, CP and CSC. I decided not to use CSC-home.
Now, reboot.
Activate the developer-option and activate USB Debug.
Restart phone in download-mode (you will need 3 hands Menu, vol-down, power keys at the same time..
Again use odin. This time flash TWRP "twrp_3.1.0-1_sm-t825_AQD6.tar" as AP.
In ODIN, you might select the auto-reboot option because after flashing, you will only need to press
menu + vol-up keys.. Easier with two hands
Now proceed as already described in this thread (format data, wipe etc...) for rooting your tab, BUT (!!!!) do not use supersu. Use magisk "Magisk-v14.0.zip".
After flashing magisk, flash "no-verity-no-encrypt_ashyx.zip".
Now reboot and enjoy a rooted tab. This does not modify the knox counter, warranty is not void. I still use the original samsung firmware..
Lets see if a suitable custom ROM will show up soon. Would be nice if Lineage was available, for tab S3 and phone S8..
ashyx said:
raymondbernard
Need some help with magisk I downloaded the magisk v14.0 and it still says that it's not install just magisk manager is installed I'm trying to root a samsung sm-j320w8
---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------
ashyx said:
You have to install the Magisk zip with TWRP then the Magisk manager apk.
Click to expand...
Click to collapse
Hey it's raymondbernard trying to get help from you about magisk manager app to root a Samsung sm-j320w8
Click to expand...
Click to collapse
Click to expand...
Click to collapse
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
Hi,
I'm using a T820 with Stock Android v8.0.0, TWRP installed and SuperSU. Everything is working fine, but I can't use Samsung's security updates ("Failed - unauthorized changes") and thus am rather behind in "Android Security Level" (April 1st, 2018).
I'd like to change from SuperSU to Magisk, but when I try to install via Magisk Manager it says "boot image patched by unsupported program" and aborts installation. This "unsupported program" could either be SuperSU or the "no-verity-no-encrypt_ashyx.zip" I used in rooting.
Is there a way to change to Magisk without reformatting Data? Can I just reflash a stock boot image and then install Magisk, or would that mess with this encryption thingy? Would I need to flash anything else on the stock image, like the "Tabs3_oreo_forced+encryption_disabler.zip" I read about? What would be the correct sequence?
Regards
Hello all!
Code:
Standard disclaimer, don't blame me if your house catches fire, you're choosing to mod your device.
Device must (obviously) be bootloader-unlocked.
Steps (do them in order):
Magisk 19.3
Download magisk and flash in TWRP, then reboot.
riru-core 19.5
Download riru-core and either flash from Magisk Manager or flash in recovery, and then reboot again.
EdXposed 0.4.6.0 and EdXposed Manager
This version of EdXposed is the only one that supports Android Q, even the beta doesn't yet. So you have to use this specific version. Install the manager apk, then flash the zip in either magisk or TWRP. Reboot to apply changes.
Now you can use any xposed module that you wish.
https://forum.xda-developers.com/Mi-9/help/edxposed-xiaomi-eu-9-8-29-android-q-t3963437
safety net passing?
gryffynmp said:
Hello all!
Device must (obviously) be bootloader-unlocked.
Steps (do them in order):
Magisk 19.3
Download magisk and flash in TWRP, then reboot.
riru-core 19.5
Download riru-core and either flash from Magisk Manager or flash in recovery, and then reboot again.
EdXposed 0.4.6.0 and EdXposed Manager
This version of EdXposed is the only one that supports Android Q, even the beta doesn't yet. So you have to use this specific version. Install the manager apk, then flash the zip in either magisk or TWRP. Reboot to apply changes.
Now you can use any xposed module that you wish.
Click to expand...
Click to collapse
Why magisk 19 3? 19.4 not working?
smohanv said:
safety net passing?
Click to expand...
Click to collapse
SafetyPatch-v3.zip, it's a magisk module.
g_seva said:
SafetyPatch-v3.zip, it's a magisk module.
Click to expand...
Click to collapse
Hi, Thank you so much.
I was trying MagiskHide Prop (https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228) and failed flashing on my Android Q (Xiaomi Mi 9, MIUI 11 running). I flashed the patch you shared here. I flashed in Magisk and it passed safety net (CTS Profile pass).
I am now able to use Google Pay.