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.
Related
I tested it and this works:
Bought N950F DS.
Instaled TWRP as in this guide:
https://forum.xda-developers.com/showpost.php?p=73817280&postcount=3
Part 3 - Magisk.
I did not flash custom rom, i wanted to stay on stock. (no system format)
Flashed Magisk 14.5
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Boot into system, configure in Magisk
install xposed (api 25),
finally you will have after few reboots xposed v89.
(Install some modules, but remember to backup in TWRP before every module installation.
For me, some of them caused TouchWiz to not show on start, had to do few reboots (bixby + power + volume down long press).
For example do not install firefdskit.
GravityBox is working fine for me now.
Also Kmod for whatsapp.)
In this state Android Pay wont work.
To get it working there is currently only one option i know:
Install this:
RootSwitch 1-3-3-16
https://www.asus.com/zentalk/tw/for...5MjEyfDVlYzZhYzljfDE1MTM3NDk3NzN8MHwxNzM1NDI=
After installing DO NOT TOUCH TOP ROOT SECTION.
Only use xposed section:
Switch xposed to off, soft reboot, install Android Pay, add card.
Whenever you need to pay in shop you have to do it (turn xposed off), later you can switch on, soft reboot and use modules.
Waiting for better way....but everyone says that Android Pay will never work with xposed so this is currently only option for me since phone without xposed is unusable.
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Interceptor777 said:
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Click to expand...
Click to collapse
in xposed settings?
I did that but SN wont allow for that, fail.
xtam said:
in xposed settings?
I did that but SN wont allow for that, fail.
Click to expand...
Click to collapse
No, you disable the Xposed module in magisk. That basically.uninstalls Xposed on next boot. And you can re-enable it.
Interceptor777 said:
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Click to expand...
Click to collapse
Interceptor777 said:
No, you disable the Xposed module in magisk. That basically.uninstalls Xposed on next boot. And you can re-enable it.
Click to expand...
Click to collapse
no, in magisk 14.5 i have few modules installed, but there is no xposed, when i was installing xposed magisk told me to download xpsed apk installer, so xposed is separated, not as uncheckable module.
Hi all?
Can someone confirm that we can be on stock rom while using magisk and twrp?
I mean replace stock recvery by twrp, root with magisk and continue to use stock rom instead of flashing custom rom.
I m on iron man rom (custom) wich is very nice. I want to try the lastest samsug rom (lastest firmware BQKG) with twrp, magisk and xposed?
Do you think it s possible without any issue like popup error windows or other problems?
Thank for your help
What cpu?
Does this work for snapdragon orrr...?
@RyleyDyck
RyleyDyck said:
Does this work for snapdragon orrr...?
Click to expand...
Click to collapse
Depends.
Definitely check the Snapdragon root section and check your Bootloader version, how to is described in the SamFail thread.
@jkr192
jkr192 said:
Hi all?
Can someone confirm that we can be on stock rom while using magisk and twrp?
I mean replace stock recvery by twrp, root with magisk and continue to use stock rom instead of flashing custom rom.
I m on iron man rom (custom) wich is very nice. I want to try the lastest samsug rom (lastest firmware BQKG) with twrp, magisk and xposed?
Do you think it s possible without any issue like popup error windows or other problems?
Thank for your help
Click to expand...
Click to collapse
You could, yes. There's no rule to must have a custom rom in order to use Magisk/ have root. Just be sure to check the "How-To root" thread for simple instructions.
@xtam
xtam said:
no, in magisk 14.5 i have few modules installed, but there is no xposed, when i was installing xposed magisk told me to download xpsed apk installer, so xposed is separated, not as uncheckable module.
Click to expand...
Click to collapse
Not sure how that is, but you installed Magisk first and then Xposed with Magisk.
It's by that definition a Module of Magisk, which you can just disable inside Magisk regardless what Xposed's actual status is (ON or OFF).
No need to worry, just toggle it OFF inside Magisk. Your Xposed apps may FC, but that's the tradeoff for being able to use SafetyNet at will.
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 guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
After clean flashing my ROM today I just can not get cts check-in Magisk to pass. Tried different ROMs (Xiaomi.eu, crDroid etc), Magisk Canary, Magisk Stable, manually selected Poco fingerprint with MagiskHide Props Config
Any ideas?
Currently on Xiaomi.eu 11.0.6 with the stock kernel
dustojnikhummer said:
After clean flashing my ROM today I just can not get cts check-in Magisk to pass. Tried different ROMs (Xiaomi.eu, crDroid etc), Magisk Canary, Magisk Stable, manually selected Poco fingerprint with MagiskHide Props Config
Any ideas?
Currently on Xiaomi.eu 11.0.6 with the stock kernel
Click to expand...
Click to collapse
Yep having the same problem....... don't know what is going on........
Yep having the same problem
Users who have not even unlocked bootloader ever will also fail safety net test
As this is an issue from Google and we all are waiting for a fix from their side
I tried this from other post and it worked. running miui 11.0.6. with lawrun kernel, be magisk hide off, selinux permissive and usb debugging on.
1. From your magisk, install these 2 modules: Riru - Core, and Riru - EdXposed (Sandbox or Yahfa is okay]
2. Reboot your device to activate both modules.
3. Install Xposed Installer APK by DVDandroid.
4. Reboot to activate the Xposed Installer app
5. Inside Xposed Installer app, go to downloads and install the HiddenCore Module.
6. Reboot and go back to Magisk and test the SafetyNet.
So I have finally updated my s9+ (exynos) to android 10 and now I can't get edxposed (yahfa/sandhook) to work. After successfully installing them through either magisk manager or directly from TWRP it now boots to download mode?? However, I can successfully go back to TWRP and remove the modules and boot as normal.
Does anyone have a working version of edxposed installed on their android 10 device or know how to resolve this?
I've had edxposed worked on previous soldier rom but the modules rarely supports android 10. Now I'm on alexander rom, waiitng the modules to keepup. I can't share how, but xposed ing android 10 isn't worth now because of the modules not working. And maybe that's your bootloop cause.
sarjarim said:
I've had edxposed worked on previous soldier rom but the modules rarely supports android 10. Now I'm on alexander rom, waiitng the modules to keepup. I can't share how, but xposed ing android 10 isn't worth now because of the modules not working. And maybe that's your bootloop cause.
Click to expand...
Click to collapse
Have you got it working on stock? Fortunately, the modules I use are sparse and they should be working. Though I might have to revert to Pie if I can't get it to work. Can't live without those modules XD
Regarding your mention of the modules causing bootloop, it is not because of them. I think. Edxposed is supporting android Q and the other modules from Magisk is running fine on android Q atm. It's EdXposed that causes the phone to boot to download mode.
Custom Soldier rom
Very strange, because I'm having this issue on LineageOS 17.1 on my S9.
Flashed twrp on g965f with android 10 cant boot on it why?
Tried many versions of twrp
If you have Edxposed Manager try canary release of Edxposed.
Edxposed exynose
I don't know how by I managed to install edxposed on galaxy s9+ G965f and it's working perfectly. I was having problem with boot at first when I installed it as normal as we always do. Then when I boot it enters to Download mode. So I uninstalled Edxposed from twrp recovery and it booted. I stil wanted Xposed on my phone so I kept latest Riru core v21.2 and Riru (YAHFA) v0.4.6.1 and rebooted my phone. Afterwards I installed edxposed manger n rebooted again by this time around it hanged again. Went to recovery and uninstalled Edxposed n rebooted the system. I went to Edxposed manager by it says Xposed is not installed.ok I then installed Xposed MANAGER BY DVD and rebooted agn ...u may wondering why I installed 2 Xposed manager by it did the magic after I rebooted my phone.BOOOM