I just installed a clean install of the April update following which I installed TWRP, ElementalX, and Magisk 16. Previously on the March update, I would enable systemless hosts in Magisk and I would then go to Adaway and check the settings to see the enable systemless mode box checked and grayed out. After the April update, when I do the same steps, The checkbox is empty and the option is grayed out. I have tried reinstalling Adaway, reinstalling magisk, and reinstalling the April update but none of these have fixed the issue. Is there a way to fix this?
darkfire404 said:
I just installed a clean install of the April update following which I installed TWRP, ElementalX, and Magisk 16. Previously on the March update, I would enable systemless hosts in Magisk and I would then go to Adaway and check the settings to see the enable systemless mode box checked and grayed out. After the April update, when I do the same steps, The checkbox is empty and the option is grayed out. I have tried reinstalling Adaway, reinstalling magisk, and reinstalling the April update but none of these have fixed the issue. Is there a way to fix this?
Click to expand...
Click to collapse
Is it working??
Badger50 said:
Is it working??
Click to expand...
Click to collapse
That's kind of my question. If you mean does it block ads, it works perfectly fine. I don't know if the systemless aspect of it is working. I checked /magisk/.core/hosts and it was edited but I just want to be sure there's no errors with it
darkfire404 said:
That's kind of my question. If you mean does it block ads, it works perfectly fine. I don't know if the systemless aspect of it is working. I checked /magisk/.core/hosts and it was edited but I just want to be sure there's no errors with it
Click to expand...
Click to collapse
Your good then. Read about that the other day from another user that said not to worry about the check box not being checked, and that as long as the thing was greyed out, systemless mode is working fine :good:
Related
Just heard Super Mario Run has came out on android but its not showing as supported for my HTC 10 on the play store?? I tried the app from an alternative store and got an error message after being able to do the first level. Why would the HTC 10 not be supported. would a build prop edit make it work?
Edit: Looks like it might be because Im rooted, going to try Magisk.
Edit 2: seems to be working with Magisk installed, still not available on playstore though.
I installed it through the play store without any problem(root-magisk)
fratorga100 said:
I installed it through the play store without any problem(root-magisk)
Click to expand...
Click to collapse
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
tokuzumi said:
I have downloaded it, and played the game successfully. I am stock, non-rooted. I have the unlocked version sold from HTC.
Click to expand...
Click to collapse
Yes, it is working for un-rooted users. Rooted users, not so well in most cases.
Ariac Konrel said:
If you flashed Magisk, it would (attempt to) remove SuperSU and replace it with MagiskSU afaik. Incorrect on my part, apologies. It only removes SuperSU if it is not systemless.
If you have SuperSU, I think that may be the issue but I am not entirely sure. I remember issues with Magisk hide and SuperSU back on an earlier build.
EDIT: Have you togged Super Mario Run in the Magisk hide section of the Magisk Manager app?
Click to expand...
Click to collapse
Yes. I am able to run the tutorial level, then I receive error 804-5100.
typhoonikan said:
I'm glad this is working for someone.
Perhaps you could add some insight into what my issue may be? I'm sure others might be experiencing it.
I've Magisk v11.6 installed, "Properly rooted" via 2.79 SuperSu.
SafetyNet Failed: CTS Profile mismatch- is occurring though.
I followed these steps, but no success.
What could I try? Does anyone have advice?
Click to expand...
Click to collapse
you need magisk SU to be able to use magisk hide and pass safety net. supersu won't work.
Coming from Android P dp3, I wiped and clean flashed dp4. Set up as new, then flashed Magisk.
I have tried different settings, but for the life of me, I cannot get ctsProfile to pass.
Anyone else having a similar issue?
I was on DP3 and both failed for me.. so I just assume wait for an update from the Magisk dev.
Same, will be waiting...
mine was working fine on dp3 but fails cts profile on dp4 (pixel 1 though)
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
i don't know it was passing on DP3
Did you guys clear data on play services and play store?
The funny thing is that I flashed without wipe and not installing magisk. The cts profile still failed.
Haven't tried fully wipe though.
Sent from my Pixel 2 XL using Tapatalk
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Ah -- yes, I probably was on Flash on dp3 -- hard enough to remember what I had for lunch yesterday let alone recall the modding I do to my phone from weeks prior
ram4ufriends said:
Did you guys clear data on play services and play store?
Click to expand...
Click to collapse
Yup. -- think the Flash Colonel will help.
Nope. On my DP3 with magisk, CTS passed.
henderjr said:
I thought ctsProfile always failed with just Magisk and you need a custom kernel too? I'm waiting for an update to Flash Kernel.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Magisk only worked on boot on DP3 for me. After a couple of minutes it nagged about Magisk v16.4 (which was installed) being available.
So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work
KevinThaKid said:
So in dp3 I got safety net to pass by clearing Google play services and and the playstore, and after updating to dp4 nothing I did work
Click to expand...
Click to collapse
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).
wassco said:
I noticed safety net does not pass on DP4 also. have not been able to figure it out either ( may just have to wait for update to magisk ).
Click to expand...
Click to collapse
Not Magisk. Google seems to have done it intentionally.
Guess we've been spoiled the previous builds
https://twitter.com/topjohnwu/status/1014059549643247616?s=09
and
https://developer.android.com/preview/release-notes
"Android P beta devices aren't Compatibility Test Suite (CTS) approved, but they have passed preliminary testing and provide the same set of APIs for developers. Apps that depend on CTS-approved builds might not work normally on supported devices."
I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.
techlogik said:
I rolled back to DP3, will wait for DP5 to see if it is fixed. I need GPay and that safetynet to pass for stuff daily.
Oh well...working fine on DP3 for me everything I use! Spoiled is right.
Click to expand...
Click to collapse
Look after flash kernel thread..seems like Google fixed it
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
Good to know I will update back to dp4 later and do that
widezu69 said:
The SafetyNet issue has been fixed with a server-side update by Google. I only cleared storage on my Google Play Store app and the device has become 'Certified'. SafetyNet passes and I've just added my card to Google Pay again.
Click to expand...
Click to collapse
I tried that but no luck
Can anyone tell me how they rooted?
I tried booting twrp, installing magisk 16, 14.4., 16.4
Installing twrp, flash 16, 14.4, 16.4
Copy the stock boot and patch via the magisk manager, install in twrp,
No luck anyway.
Edit: Twrp can't decrypt a pattern.
Wanted to do the old hotspot trick (net.tethering.noprovisioning=true) but the build prop won't save. Any ideas?
Also trying to load adaway in data/hosts and data/data/host fail.
But magisk modules will install and work.
Search on XDA for Tethering Enabler for Magisk. It's working for me not sure about Adaway.
AlPoo said:
Wanted to do the old hotspot trick (net.tethering.noprovisioning=true) but the build prop won't save. Any ideas?
Also trying to load adaway in data/hosts and data/data/host fail.
But magisk modules will install and work.
Click to expand...
Click to collapse
Regarding adaway, make sure you set "systemless hosts" mode in Magisk settings. Not sure of the exact name of the setting at the moment as I do not currently have Magisk installed...
I wasn't able to get /system rw which limited options on enabling tether.
Adjusting magisk for systemless hosts worked fine for me but I was never able to get tethering working on q. I went back to 9 until things smooth out a bit.
KillerVamp09 said:
Search on XDA for Tethering Enabler for Magisk. It's working for me not sure about Adaway.
Click to expand...
Click to collapse
Huh. I'll have to keep it in mind if I try to re enable tether after an OTA. I managed to find a guide that worked by setting it in terminal.
PhoenixPath said:
Regarding adaway, make sure you set "systemless hosts" mode in Magisk settings. Not sure of the exact name of the setting at the moment as I do not currently have Magisk installed...
Click to expand...
Click to collapse
Oddly enough I couldnt get any of that to work. Until I installed busy box and installed the system less host module via magisk.
Aridon said:
I wasn't able to get /system rw which limited options on enabling tether.
Adjusting magisk for systemless hosts worked fine for me but I was never able to get tethering working on q. I went back to 9 until things smooth out a bit.
Click to expand...
Click to collapse
As for tethering I got it working cherry! I can't find the exact guide I found but this is the same. Had to install busy box and whatnot but, it worked. Found this guide on XDA but this link has the same steps. Be warned though, 4 isn't "add new/custom", for me, I had to press 5 not 4. https://www.getdroidtips.com/how-to-enable-native-tethering-on-rooted-pixel-3-3xl/
Not sure what tether_dun_required 0 does. But it worked like a charm and persists after reboot now.
Thanks everybody, got it all working now. Couldn't have done it without ya!
What is the name of the system less magisk module you installed so I use the right one.
AlPoo said:
Huh. I'll have to keep it in mind if I try to re enable tether after an OTA. I managed to find a guide that worked by setting it in terminal.
Oddly enough I couldnt get any of that to work. Until I installed busy box and installed the system less host module via magisk.
As for tethering I got it working cherry! I can't find the exact guide I found but this is the same. Had to install busy box and whatnot but, it worked. Found this guide on XDA but this link has the same steps. Be warned though, 4 isn't "add new/custom", for me, I had to press 5 not 4. https://www.getdroidtips.com/how-to-enable-native-tethering-on-rooted-pixel-3-3xl/
Not sure what tether_dun_required 0 does. But it worked like a charm and persists after reboot now.
Thanks everybody, got it all working now. Couldn't have done it without ya!
Click to expand...
Click to collapse
Archangel said:
What is the name of the system less magisk module you installed so I use the right one.
Click to expand...
Click to collapse
Click the systemless option in the Magisk settings. It will install the correct module for you.
I did that is just causes a pop up that says added systemless host module. Adaway still gives me a syslink error?
sic0048 said:
Click the systemless option in the Magisk settings. It will install the correct module for you.
Click to expand...
Click to collapse
Archangel said:
I did that is just causes a pop up that says added systemless host module. Adaway still gives me a syslink error?
Click to expand...
Click to collapse
You need to reboot after that and then enable Adaway.
ctfrommn said:
You need to reboot after that and then enable Adaway.
Click to expand...
Click to collapse
This worked perfectly. Adaway is my favorite piece of software. Thank you. I had also installed busybox, based on an earlier comment. Not sure if that was necessary.
When I first got my 7T I managed to root it and install Intune rather easily - just hid a bunch of things in Magisk Hide. Last night I boneheadedly reset my device to factory settings and had to start all over again. However when I attempted to install Intune root was detected. Tried removing device from company portal, clearing cache, uninstalling, reinstalling, adding a bunch more things to Magisk Hide - no luck, root is always detected.
Two questions to get me going
a) I used to be on an older version of Magisk Manager, don't remember which one, but am now on the newest version. Has anyone had any luck with MH and Intune with the latest versions
b) I vaguely recall that once Intune detects a root it "brands" the device serial number and the only way to work around that is to change the serial number. Is that correct?
Thanks
You musst rename the magisk manager with random name on magisk settings and hide root then it should work again
ChrisFeiveel84 said:
You musst rename the magisk manager with random name on magisk settings and hide root then it should work again
Click to expand...
Click to collapse
Nope. I had done that and it did not work. Just tried it with the old MM (7.5.1) and it worked beautifully. That is why I never update Magisk once I get it running on a particular device
I only use the latest version of magisk canary myself and haven't had any problems so far (so far I haven't found an app that recognized the root despite magisk hide)
Interesting. Does this include Intune? I saw TopJonWu post on twitter that the latest version handles Intune "out if the box" but that is not my experience so far.
Since updating to C.48 (2125 [phone], coming from C.47, my Google Play and Pay have stopped working on my rooted phone (Magisk 24.3), even though it passes SafetyNet with YASNAC. When I try to open Play I get a "Try Again" screen. When I try to open Pay, I get "Google Pay is updating right now...". I've got Universal SafetyNet Fix 2.2.1 and MagiskHide Props Config installed, and Play and Pay in the Deny List. Tried using Shamiko 0.4.4 (while disabling deny) with no better results. Cleared cache and data on both apps multiple times. Uninstalled Magisk and unrooted, and everything worked again. Re-rooted w/o opening either app, put them both into "deny" and, for a brief time, both worked -- but eventually (without my doing anything that I could tell), they both reverted to the behavior described above.
I'm wondering if this behavior has anything to do with the April security update included in C.48? Because it's really odd that I YASNAC still shows safetynet as having passed. More likely, it's user error on my part, but has anyone else run into this yet on C.48?
I have a LE2127 running your firmware and I don't notice issues. One thing you could try is just flashing the update zip over your current OS using the OPlocalupdate apk here https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
rogerinnyc said:
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
Click to expand...
Click to collapse
Yes, I'm rooted. I'm using Denylist on Magisk 24.3.
No problems on my end with Gpay while rooted
I gave up and did a total restore with MSM and then made sure to root and fill up the Deny List (and add SafetyNet Fix) before opening up Google Pay or Play. That seemed to work. Not sure how I messed it up in the first place, but I think it was in upgrading from C47 to C48 and my sequencing of unrooting, upgrading, clearing storage in the apps and re-rooting. Thanks all.