Hi, i have successfully rooted my oneplus 7t using the guide, installed magisk,
I installed Adaway and tried to enable hosts, it's giving me errors. Please find attached screenshots.. Kindly help
In Magisk enable systemless host module in preferences.
In adaway also check use systemless host option. Reboot needed.
I got Adaway working using these options
jesrani said:
In Magisk enable systemless host module in preferences.
In adaway also check use systemless host option. Reboot needed.
I got Adaway working using these options
Click to expand...
Click to collapse
Hi tried above steps, it asked for reboot, but after reboot still hosts are not enabled..
Try adguard app instead once. See if it is able to modify host or not.
I am having the same problem with adaway. Have tried the above- no dice. Anyone else getting things to work?
It works with systemless hosts for me also!
Yeah it works works with systemless hosts enabled. Both on the app and magisk. I had a similar problem but it's sorted out now
AdAway 4.3, Magisk Canary (newest build) with systemless and works great (default dir for hosts). Thanks for info.
Related
Hello XDA,
As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here
The temporary fix was originally mentioned on this thread by @[email protected]
However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.
All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:
GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15
Download APK
Made a Quick Video Here
Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2
Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]
PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:
Never Settle :highfive:
Reserved
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Interceptor777 said:
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Click to expand...
Click to collapse
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Bewildered Wolf said:
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Click to expand...
Click to collapse
Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.
The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.
Also, theme is also called spectrum on the play store.
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15
hachamacha said:
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
Click to expand...
Click to collapse
Please try the new apk uploaded on the OP :fingers-crossed:
Funk Wizard said:
Please try the new apk uploaded on the OP :fingers-crossed:
Click to expand...
Click to collapse
Just tried it and it works fine as did your first. Thanks!
@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here
Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot
Magisk 13.2 has been released and fixes the SafetyNet test failing.
Magisk 13.2
I can confirm that it's working for me.
Magisk 13.3 already available, and everything is fixed
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
13.3 fixed for me
Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
crumble6 said:
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Click to expand...
Click to collapse
That didn't work for me unfortunately.
ArkAngel06 said:
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
Click to expand...
Click to collapse
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Thanks guys!
Binary Assault said:
That didn't work for me unfortunately.
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Click to expand...
Click to collapse
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
crumble6 said:
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
Click to expand...
Click to collapse
Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.
For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Binary Assault said:
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Click to expand...
Click to collapse
Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.
Magisk Hide doesn't seem to work on the DirecTVnow app. Has anybody else been able to watch shows on a rooted device?
Is anybody rooted using only SuperSU and can turn off Superuser and watch shows? (This works on my Galaxy Tab S2)
I attempted to root only using SuperSU before and my phone went into a recovery loop. It would not boot back into Android.
Any other solutions are appreciated.
Did you ever figure this out? I am having the exact same issue on the exact same device.
drt054 said:
Magisk Hide doesn't seem to work on the DirecTVnow app. Has anybody else been able to watch shows on a rooted device?
Is anybody rooted using only SuperSU and can turn off Superuser and watch shows? (This works on my Galaxy Tab S2)
I attempted to root only using SuperSU before and my phone went into a recovery loop. It would not boot back into Android.
Any other solutions are appreciated.
Click to expand...
Click to collapse
Have you tried magisk hide? It's in the menu of the magisk app
Forgot all about this. Using latest Magisk and Hide I am able to use the DirecTVnow app. Although just updated to Pie and Magisk won't yet pass safetynet check so Hide may not work on some apps.
drt054 said:
Forgot all about this. Using latest Magisk and Hide I am able to use the DirecTVnow app. Although just updated to Pie and Magisk won't yet pass safetynet check so Hide may not work on some apps.
Click to expand...
Click to collapse
I'm using Magisk version 16.7(1674) and Flash Kernel 3.01 on Pie. Magisk passes safety net and I can use the DirecTV app without problems.
Hi.skygo now detects enabled root even if its hided in magisk hide.anyone else with that prob?any suggestions?
Hide magisk Manager in magisk settings. that's all. Works now ?
pa.pn2 said:
Hide magisk Manager in magisk settings. that's all. Works now ?
Click to expand...
Click to collapse
Hide by renaming the package, if someone's wondering... it's the 4th option! :fingers-crossed:
You got Magisk installed on the stock Android 9 ROM? Awesome! But wait, there is more! ?
This thread is meant for the exchange of everyone's experience with Riru and Xposed modules running with EdXposed.
The installation is pretty simple: 1) In Magisk, install "Riru - Core", reboot, 2) install "Riru - EdXposed" (SandHook), reboot, 3) install "EdXposed Manager" (github.com/ElderDrivers/EdXposedManager/releases).
Once everything is set up, install Xposed modules like crazy ... and prepare yourself for a hell of crashes and boot halts ?. Since we do not have TWRP with data decryption yet, you have to be prepared for those boot halts. Therefore, install only one Xposed module at a time, reboot and check if everything is working. If Android does not boot, you can fix your phone using two methods:
Recovering from a boot halt - Method 1
The most obvious way to get around a boot hang is to 1) flash the original boot.img, 2) boot into the UI and uninstall the Xposed module causing the boot halt, and 3) flash "magisk_patched.img" and re-install Magisk from within the Magisk Manager ("Direct install"). SU might stop working if you forget to re-install Magisk (not the Magisk Manager).
The only possible downside is that Magisk and Xposed modules, like XPrivacyLUA, will be inactive during step 2). However, potential privacy/usability issues are less painful than not being able too boot up Android ?.
Recovering from a boot halt - Method 2
If you do not want to disable Magisk and Xposed, flashing the "magisk_patched.img" may make Android boot into the UI ... and give you 10 to 20 seconds before crashing. As a precaution, before you install Xposed modules, 1) remove PIN/password log-on and 2) place a shortcut to the EdXposed Manager and Magisk Manager onto a convenient spot on your desktop. For both managers, you can place a link directly to the Modules tab (at least with Nova launcher).
If things go well, you have 10 to 20 seconds to open the EdXposed Manager and disable the module causing the boot process to fail. If the boot process gets stuck again, even though you flashed "magisk_patched.img", you might succeed by flashing the "magisk_patched.img" several times before rebooting. Even removing the SIM or SD-card may make Android boot up.
If/when you succeed to disable the Xposed module that blocks the boot process, you have to re-install Magisk from within the Magisk Manager ("Direct install"). Otherwise, SU might stop working for you.
Here are Xposed modules that prevent your Pro1 from booting into Pie:
MyAndroidToolsXposed (surely)
DisableFlagSecure (probably)
Screenshot Delay Remover - Mod (probably)
Working fine are:
GravityBox
XPrivacyLUA
AFWall+
Scoop
App Locale 2
InstallerOpt (doesn't crash but doesn't seem to work either)
FakeGApps
I want to install Xposed mainly for MinMinGuard to get ride of these empty ads areas, is this module working fine?
OP 7 Pro Magisk
Sorry for the late reply...
So far, either no one ever tried to run MinMinGuard on the Pro1, or no one ever gave feedback
The riru core update 21.3 seems to remove the play services on my gt-n7000 with lineageos 16 and opengapps pico.
Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?
Antinee said:
Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?
Click to expand...
Click to collapse
You can install the Magisk zip via LineageOS recovery
Antinee said:
Is this thread for Lineage OS only?
Click to expand...
Click to collapse
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.
im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.
cnoevl21 said:
im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.
Click to expand...
Click to collapse
This is about the Fxtec Pro1. Anyway, that's because Riru is v22 or newer. EdXposes currently needs an older riru
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.
peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
cnoevl21 said:
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.
Click to expand...
Click to collapse
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip
nift4 said:
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip
Click to expand...
Click to collapse
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol
cnoevl21 said:
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol
Click to expand...
Click to collapse
Did you enable Pass SafetyNet in EdXposed settings
nift4 said:
Did you enable Pass SafetyNet in EdXposed settings
Click to expand...
Click to collapse
I did. still fails
cnoevl21 said:
I did. still fails
Click to expand...
Click to collapse
If App List mode is enabled, I can't help you
Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!
Rezazahmad01 said:
Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!
Click to expand...
Click to collapse
I just checked i have 23.2 installed not sure if the same issue is here
For some time, the riru core continues to have a very horrible bug for Samsung devices with Snapdragon, it is that once installed it affects the installation of apks and applications from the play store and also in the uninstallation of applications the "installer of packages stays frozen and does not advance "is a very random and very annoying error and you have to restart the device and sometimes it does not work. That's why I ask you to correct that error. It was tested on a S9 + g9600 and a note 9 N9600 both with a Snapdragon processor and latest riru core 25.4.2.
daniel_m said:
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.
Click to expand...
Click to collapse
Working also on Lineage 18.1?
I become an error Riru Core not found in memory
I am on 10.3.2, rooted with Magisk Manager version 07f712a1 and Magisk 87de0e7a. These are the version numbers I can see when i open Magisk Manager. Magisk Hide is enable for banking apps mainly, systemless host module is enabled and Magisk package name is also hidden.
Most apps needing root are working fine and most Banking apps requiring root to be hidden are also working fine.
However BHIM UPI is not working, I get a message of root detected after putting the PIN and it does not open. If I uninstall or clear storage and register my mobile again, it gives the root detected error but still logs in. However as soon as I exit and open again, it does not log in. Any way to get this working?
Adaway had been working properly but now it is not able to update hosts, says Root permission not granted, even though in Magisk default permission is Grant. I have tried to uninstall and reinstall, change options in Magisk, install F-droid version but nothing works. Systemless host is enabled. I have restored a working app version and data using Titanium backup so ad-blocking is working. But unable to update with new host file. How to fix this?
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Macusercom said:
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Click to expand...
Click to collapse
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
gpz1100 said:
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
Click to expand...
Click to collapse
Is this meant as a reply to my post? My issue with Adaway on Magisk Canary is that suddenly it is not able to get root permission.
So it worked before? I had to mess with the systemless hosts to get it working. It didn't have issues acquiring root though.
jesrani said:
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
Click to expand...
Click to collapse
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Macusercom said:
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Click to expand...
Click to collapse
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
jesrani said:
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
Click to expand...
Click to collapse
Afaik only for custom ROMs. Otherwise, you can still remove Magisk in Magisk Manager and then patch the boot.img with the stable Magisk version or you remove ALL modules first, then make an OTA update to your existing version.
Then patch boot.img and flash it via "fastboot flash boot.img".
@jesrani What was the solution finally ?
Yea I'm having the same issue, tried everything i could and even using 'hide my applist' and it IS working. Its just that all apps except BHIM just won't even open now.