Related
Can anyone recommend a working adaway app or zip for the mix 2, I've tried several and it's not working. I am rooted.
Just download it off fdroid. You're rooted right?
sbeaber4 said:
Just download it off fdroid. You're rooted right?
Click to expand...
Click to collapse
Yeah I did, but it's not working. I've tried using the module from magisk and even with that it's not working.
I'm using the Unified Hosts Adblock Magisk module (available in the app repository). I have the systemsless hosts option enabled in Magisk settings. Then I installed Unified Hosts Manager from the playstore to enable it. Not a ton of options. But seems to be working. That being said, I am on XenonHD. It seemed to work on Epic ROM as well. But I was only on it a day.
I have a whitelist to allow 2 Google urls that seem to drive Google Play Music crazy.
no problem here,watch your permission
***TAPATALKING***
juggaknot77 said:
Can anyone recommend a working adaway app or zip for the mix 2, I've tried several and it's not working. I am rooted.
Click to expand...
Click to collapse
I did notice a issue in the past on stock miui using magisk 15.2 adaway wasn't working. Latest version is working now.
Take DNS66 from fdroid ... no root needed!
Works perfect for me since months
For whatever reason Adaway has stopped working for me on the EU MIUI ROM, there's been 3 weekly releases since my current version but I'm waiting on the Oreo release to bother updating again. It did work on the version before this but I only realised due to this thread it wasn't - just gave me a black screen on loading the APK to update the hosts file.
I've since swapped to the magisk unified hosts module like above and it works perfectly - wish I'd not bothered with Adaway.
I have a Globe Rom installed.
My first try was with magisk and adaway did not function.
Second try using SU without magisk and adaway worked perfectly!
Adaway worked for me on xiaomi.eu 7.12.21 with magisk
lapocompris said:
Adaway worked for me on xiaomi.eu 7.12.21 with magisk
Click to expand...
Click to collapse
not working in this release but with oreo it works for me
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
SOLVED: New substratum update available on play store.
sidhg said:
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
Click to expand...
Click to collapse
No such issue on my P2XL. Have you tried clearing substratum app cache and data? And/or uninstall/install substratum again?
Badger50 said:
No such issue on my P2XL. Have you tried clearing substratum app cache and data? And/or uninstall/install substratum again?
Click to expand...
Click to collapse
Yes I've reinstalled both the app and the theme.
Still nothing shows in the Overlay Manager.
sidhg said:
Yes I've reinstalled both the app and the theme.
Still nothing shows in the Overlay Manager.
Click to expand...
Click to collapse
Does substratum have root privileges?
sidhg said:
Hey everyone
I just installed the December security patch.
Now that I have installed substratum, I can't find the installed overlays in the Overlay Manager. Tried themes like Swift dark and other themes. It still doesn't work.
Also I've updated the magisk manager to version 18.0 today.
Anyone facing the same issue with their device?
I'm using Pixel 2 XL
Click to expand...
Click to collapse
Substratum is not compatible with the new Magisk 18. As far as I know, a new version is worked on right now. You either have to wait or use Magisk 17.3.
Badger50 said:
Does substratum have root privileges?
Click to expand...
Click to collapse
Yes it has the access to the root.
May be the new magisk update is the problem.
kost7 said:
Substratum is not compatible with the new Magisk 18. As far as I know, a new version is worked on right now. You either have to wait or use Magisk 17.3.
Click to expand...
Click to collapse
I'll wait for the substratum update. Thanks.
sidhg said:
I'll wait for the substratum update. Thanks.
Click to expand...
Click to collapse
I just can't stand the white pages everywhere; it drives me both blind and crazy, so I'll stick to 17.3 for the time being.
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
CamoGeko said:
Yeah I can confirm latest Magisk 18 breaks Substratum, so either stay on 17.3 or deal with being blinded by white backgrounds. Tbh I'm really surprised Google hasn't managed to figure out a way to actually turn all white backgrounds either grey or black, Samsung a has actually done it before them with the new OneUI lol
Shame on you Google.
Click to expand...
Click to collapse
This explains the difficulties I was having getting some overlays to work. Thank you
Try flashing Magisk 18 in the Magisk manager app itself instead of in twrp, I was having problems gaining root until I did that. I'm currently on ver 18 with Substratum working.
There is a new update available for substratum on the Google play. I hope this resolves the issue.
Edit: It's working fine now.
JoeNeckbone said:
Try flashing Magisk 18 in the Magisk manager app itself instead of in twrp, I was having problems gaining root until I did that. I'm currently on ver 18 with Substratum working.
Click to expand...
Click to collapse
Thats how I installed mine and Substratum still broke.
Anyways that's a moot point now, new Substratum release on Play Store fixes the problem.
Sent from my Essential Products PH-1 using XDA Labs
CamoGeko said:
Thats how I installed mine and Substratum still broke.
Anyways that's a moot point now, new Substratum release on Play Store fixes the problem.
Click to expand...
Click to collapse
Even with Substratum taken out of the equation, I was having problems getting root with Magisk 18 until I flashed within Magisk app and chose recommended install option.
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
davidisflash said:
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
Click to expand...
Click to collapse
Latest substratum works only with Magisk 18 afaik.
davidisflash said:
I'm on December update, have latest substratum after fresh install of latest update from Google. Magisk 17.1
I can compile a theme and they all show. When I restart and then try and change overlay state, it tells me to compile first ??!! Any idea
Click to expand...
Click to collapse
kost7 said:
Latest substratum works only with Magisk 18 afaik.
Click to expand...
Click to collapse
Kost7 is correct. You must be on magisk 18.0 if you want to use substratum :good:
Badger50 said:
Kost7 is correct. You must be on magisk 18.0 if you want to use substratum :good:
Click to expand...
Click to collapse
You guys are awesome ?
I've bootlooped before when installing the 17.3 zip in twrp. What's the safest way to upgrade to 18
davidisflash said:
You guys are awesome ?
I've bootlooped before when installing the 17.3 zip in twrp. What's the safest way to upgrade to 18
Click to expand...
Click to collapse
Just let magisk upgrade itself from within the magisk manager app. Worked without issue for me :good:
Did it with twrp and worked. Thanks again!!!
Simple magisk module that modifys the powermenu behaviour to boot directly back into magisk when selecting the reboot option.
I created this for personal use, thought I would share just in case someone else finds it useful.
I've also added the patches to "smali patcher" for future firmware updates which will allow you to generate your own updated modules based on new firmware bases!
You can find smali patcher: HERE
It uses the same module ID as smali patcher generated modules, this by design they should overwrite one another.
PATCHES ::
Mock locations - Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
Magisk reboot (Galaxy S10) - Reboot directly back into magisk from powermenu.
High volume warning - Disable high volume popup dialog.
If for whatever reason you find yourself in a boot loop caused by using this mod on a different rom base than the one specified in the thread title:
fOmey said:
You can remove magisk modules from recovery mode.. dont need any third party tools.
Boot into TWRP
Advanced -> File Manager
Navigate to: data -> adb -> modules -> module directory (in this case "fomey.smalipatcher") -> Folder icon (bottom right) -> Delete
Click to expand...
Click to collapse
I've removed any posts regarding xposed from this thread.. this was done to prevent this thread being filled up with "xposed support" posts. Please take all future xposed discussion to their own relevant threads.
Installed it and phone is now stuck in a boot loop -.-
Thanks! Working for me on S10+
FPSkillerPC said:
Installed it and phone is now stuck in a boot loop -.-
Click to expand...
Click to collapse
You are using this on a ASCA base rom right?
Not sure if this is relevant but there appears to be a bug with the TWRP magisk patched root method where trying to get into TWRP after the first boot causes a Bootloop. I've experienced this also but it's not caused by this module. A few people have reported it to Geite on his post so hopefully he can replicate it in the coming days
edited: working fine with s10+ thanks
fOmey said:
You are using this on a ASCA base rom right?
Click to expand...
Click to collapse
what does this mean?
IsocolXDA said:
what does this mean?
Click to expand...
Click to collapse
You shouldn't be playing with root twrp and roms if you don't understand what that means :/
Very good work!! Thanks!!
Working perfect on S10+ 975F
aussiesausage said:
You shouldn't be playing with root twrp and roms if you don't understand what that means :/
Click to expand...
Click to collapse
Im not, i was just wondering. I am using root for greenify and some minor customisation.
IsocolXDA said:
what does this mean?
Click to expand...
Click to collapse
ASCA is the end of the rom build number this module was created with, every rom build/update has a unique build number (you can find this in settings -> about -> software).
General rule of thumb is use mods that match your rom build number to avoid any funny business (crashing & boot loops).. if your using mismatch mod/rom build numbers it can cause havoc.
An alternative method of achieving the same thing without the hassle of having to wait for an updated Magisk module every time Samsung releases new firmware is to use the FireFDS Xposed module in combination with EdXposed. This will work transparently across firmware versions.
Screenshot of my S10+'s power menu attached.
ianmacd said:
An alternative method of achieving the same thing without the hassle of having to wait for an updated Magisk module every time Samsung releases new firmware is to use the FireFDS Xposed module in combination with EdXposed. This will work transparently across firmware versions.
Screenshot of my S10+'s power menu attached.
Click to expand...
Click to collapse
Offtopic: Are you passing safetynet with EdXposed? I miss xposed..
fOmey said:
Offtopic: Are you passing safetynet with EdXposed? I miss xposed..
Click to expand...
Click to collapse
I certainly am. That's one of the best side-effects of running EdXposed as opposed to Rovo's original.
A few months ago, EdXposed was looking like a pale shadow of the original, but the work that GravityBox's developer has done in the last month or so to make that project work on Pie with EdXposed has really put EdXposed on the map.
Sent from my SM-T830 using XDA Labs
ianmacd said:
I certainly am. That's one of the best side-effects of running EdXposed as opposed to Rovo's original.
A few months ago, EdXposed was looking like a pale shadow of the original, but the work that GravityBox's developer has done in the last month or so to make that project work on Pie with EdXposed has really put EdXposed on the map.
Sent from my SM-T830 using XDA Labs
Click to expand...
Click to collapse
That's awesome, will have to check it out for myself.
@fOmey
any love for latest patch ?
Removed
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
ianmacd said:
An alternative method of achieving the same thing without the hassle of having to wait for an updated Magisk module every time Samsung releases new firmware is to use the FireFDS Xposed module in combination with EdXposed. This will work transparently across firmware versions.
Screenshot of my S10+'s power menu attached.
Click to expand...
Click to collapse
I already use this module but the reboot button do not do the trick (magisk sys reboot). Did I miss something?
Dockyy said:
I already use this module but the reboot button do not do the trick (magisk sys reboot). Did I miss something?
Click to expand...
Click to collapse
Choose the Recovery button, not the normal Restart one.
ianmacd said:
Choose the Recovery button, not the normal Restart one.
Click to expand...
Click to collapse
Nice thanks!!
TheUndertaker21 said:
@fOmey
any love for latest patch ?
Click to expand...
Click to collapse
I havnt installed the latest patch yet, I'm sticking with my region update cycle.
You can generate a new module yourself tho, visit the smali patcher thread linked on the first post.. the entire process is automated, you simply need to select the patches you want to use and install the module.
has anyone got viper4android working? I try every way I could when using OnePlus 9Pro A11, A12, and A13 where it work.
are the partitions different where the post-fs-data.sh file redirects?
This is the easiest v4a yet and I have it working on my OnePlus 11 with no issues
Releases · AndroidAudioMods/ViPER4Android
ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.
github.com
since this is still being developed, there are certain features unavailable
JWhetstone02 said:
This is the easiest v4a yet and I have it working on my OnePlus 11 with no issues
Releases · AndroidAudioMods/ViPER4Android
ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.
github.com
since this is still being developed, there are certain features unavailable
Click to expand...
Click to collapse
this great! everything worked, no extra modules or steps. thanks
不成功
Has anyone this working with the newest Magisk Canary version? Mine says the driver isnt installed anymore.
Anders Mogensen said:
Has anyone this working with the newest Magisk Canary version? Mine says the driver isnt installed anymore.
Click to expand...
Click to collapse
Mine stopped working as well after updating Magisk. Also lost AdAway because systemless hosts isn't working anymore. Hopefully they will release a fix soon
Anders Mogensen said:
Has anyone this working with the newest Magisk Canary version? Mine says the driver isnt installed anymore.
Click to expand...
Click to collapse
Official magisk changed something about sepolicy and some modules stopped working.
You can use magisk delta instead.
Magisk Canary 25210 Magisk Magic Mount is not working. Use 25206 as it's stable as of now.
My Viper installation has the driver's working until you play any type of audio and then the driver stops working.
surajpai524 said:
Magisk Canary 25210 Magisk Magic Mount is not working. Use 25206 as it's stable as of now.
Click to expand...
Click to collapse
25208 also works
I installed Magisk Delta, the "new" Magisk hide helped with hiding root to a problematic app
JWhetstone02 said:
This is the easiest v4a yet and I have it working on my OnePlus 11 with no issues
Releases · AndroidAudioMods/ViPER4Android
ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.
github.com
since this is still being developed, there are certain features unavailable
Click to expand...
Click to collapse
But dolby is not working 🥹🥹🥹🥹
I've searched XDA and tried all the suggestions, but I still can't get Magisk to open on my Tab S. It is rooted with Lineage 17.1. I downloaded Magisk V26.1, renamed it to a zip file and installed with TWRP. I uninstalled and installed 3 times and still no luck. I also cleared cache and storage. There is no hidden version of Magisk. Anything else I can try? Maybe an older version of Magisk? Should I try wiping Dalvik cache using TWRP and if so, before or after installing Magisk?
Thanks!
Tom
try magisk canary or magisk delta
lapsmith said:
I've searched XDA and tried all the suggestions, but I still can't get Magisk to open on my Tab S. It is rooted with Lineage 17.1.
Click to expand...
Click to collapse
As you say it's rooted already why do you need to install Magisk 26 again at all, the current version already is 26.2 btw.
Cheers
Toscha
toscha42 said:
As you say it's rooted already why do you need to install Magisk 26 again at all, the current version already is 26.2 btw.
Cheers
Toscha
Click to expand...
Click to collapse
Good question. I'm a noobie and thought that Magisk provided more features or capabilities. But maybe I've been wasting my time on something I don't need!
Fytdyh said:
try magisk canary or magisk delta
Click to expand...
Click to collapse
Thanks, but it looks like canary only supports 64 bit systems. What is the difference between delta and the official Magisk? And if my tablet is already rooted, do I even need Magisk?
You don't need the Magisk app any longer. But honestly, as long as it is rooted I simply wouldn't touch it anyway. Just leave as it is.
The newer Magisk version is rather suitable for Android 13 and younger. Doesn't need to bother you and for < A12.
Cheers
Toscha
toscha42 said:
You don't need the Magisk app any longer. But honestly, as long as it is rooted I simply wouldn't touch it anyway. Just leave as it is.
The newer Magisk version is rather suitable for Android 13 and younger. Doesn't need to bother for you and < A12.
Cheers
Toscha
Click to expand...
Click to collapse
Well, that's great to hear, I don't have to mess with it any longer. Thanks so much Toscha!
Tom
Now I remember why I was trying to install Magisk I can't install Netflix from the play store (message says will not run on my device). But I found some comments here (https://forum.xda-developers.com/t/...m-t705-sm-t800-sm-t800-sm-p600.4270943/page-6) who used Magisk to get it to run:
mp1967 said:
I installed magisk v23 via twrp (renamed apk to zip first),
rebooted, used magisk modules liboemcrypto disabler and magiskhide props config and rebooted, enabled magisk hide
installed netflix app via sideload and tick box in magisk to hide this app
went to netflix account to enable HD streaming for the device
Click to expand...
Click to collapse
I tried searching that thread for any more clues, but I can't get the "Search this thread" tool to work and didn't want to read 73 pages of posts. Anyway, do you know another way to get Netflix to work on LineageOS 17.1?
I've Netflix installed on my SM-T805 (LineageOS 18.1) without any Magisk modules. Runs fine.
Cheers
Toscha
Thanks again, Toscha. I wonder if it is because I only have LineageOS 17.1, the latest available for my T700. Do you remember if you downloaded it from apkmirror?
Actually I'm not sure. At least in the settings for Netflix app it says 'Installed from Play Store'. Not sure though whether it's the same for apps installed from APKmirror.
I did that a while just for test purpose. Not using Netflix actively on the tablet. And yes, it might have been from APKmirror.
Cheers
Toscha
I appreciate all your help, Toscha. I'll try some other versions....though I think the one I used should work on the T700 processor.
Much obliged!
Hey Toscha, just wanted to let you know I got it to work. I was using TWRP to install but all I needed to do was use APKmirror installer app! All is good now
Tom
Glad it worked finally!
Cheers
Toscha