Related
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Edit: New info added to OP after my answer... Magisk Hide does not work with SuperSU.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
That's a shame ./. I'll ask reddit
Thanks
I'm using phh's superuser and Magisk hide is working for me on the open beta and people seem to say that the current beta and the release versions are virtually the same, so it might be an issue with how SuperSU is handled.
afaik Magisk Hide needs phh's root, not SuperSU
Snappiestjack said:
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
Click to expand...
Click to collapse
Ok... I believe you've added some information since my first answer...
Magisk Hide does NOT work with SuperSU. You have to use topjohnwu's phh's superuser that's provided with Magisk.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
mucha.k1994 said:
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
Click to expand...
Click to collapse
Yeah, I know... OP edited with SuperSU info after my answer. I edited my post as well. Thanks for the reminder.
Not going to quote everyone, but YES! Removing SuperSU and using phh SU works just fine!
Thanks all.
I recently installed magisk and got it all working but after installing a module I cannot find it anywhere on my phone. I don't know where else to look, I installed IYTBP
I noticed something strange, on my phone and I'm trying different ways to solve it, but it just does not "work".
I have 2 x Magisk icons in my phone and I cannot remove them, so that I only have 1 x Magisk.
Here's some background,...
My phone: OnePlus 6 [OP6], with stock Oxygen OS 9.0.9 [OOS 9.0.9] Android and running custom kernel [Omega].
I had been running a ROM [xXx NoLimits] which is a Magisk Module.
For last 11+ months, I have had no issues with my phone, no issues with Magisk, and no issues with root really.
I updated to Magisk v20.0 (but it seems it was the Beta / Canary channel) and also,
I had used the "Hide Magisk Manager" feature, for 1 specific app. to work.
Just this week, I noticed some issues with my phone or that I had 'lost' root
This happens rarely, and I just reinstall Magisk, but it resolves itself.
So, I went looking and saw an odd thing: 2 x Magisk icons.
Since then, I have tried:
- Magisk Uninstaller [Magisk-uninstaller-20191011.zip]
- Flashed unpatched BOOT.img file, Flashed TWRP. Then, rebooted to TWRP.
- Flashed Magisk, flashed the custom kernel.
Still, I saw 2 x Magisk icons.
I could see 1 Magisk was on STABLE channel, while other was on CANARY channel.
This was strange.
So, I changed the CANARY to STABLE, etc. etc...
Anyway, too many combinations of uninstalling and removing root, reinstall Magisk, etc... and I still don't know how to really uninstall Magisk and start from ZERO again.
I have lost Magisk's association to my Magisk modules too.
Can anyone help or advise?
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
I think I resolved my issue now...
I uninstalled Magisk using the official Magisk Uninstaller.
I also uninstalled the 2 x Magisk apps in my launcher, using this .APK ---> "Uninstalled SystemApps" ( https://github.com/nicolaserlonghi/UninstallSystemApps )
Then, I had to go through re-installing the BOOT.img, Magisk and most importantly, the ROM (which itself was a Magisk module).
Slowly, it populated the Magisk module list and 'SuperUser' lists, and I think I got the phone back into how I had it.
Didgeridoohan said:
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
Click to expand...
Click to collapse
Yes, exactly.
Thanks for this tip, but I reached this conclusion anyway...
and used another .apk (Unsinstall SystemApps) to remove the Magisk Manager (which was the result of using "Magisk Manager Hide",
but then I must have mixed up Stable & Canary builds of Magisk on the phone, etc.)
Didgeridoohan said:
Sounds like you just have two Managers installed.
Click to expand...
Click to collapse
One thing weird though is, quite a few modules that were previously installed are missing from the Magisk "modules" section.
When I 're-install' them, they still don't show in the "modules" section.
For Example:
Vanced, Advanced Charging Controller, etc... all have been installed, but not showing up in Magisk.
I just had a weird situation of 2 different Magisk installs (at first it seemed like 2 x Managers), but it could be 2 different Magisk builds:
stable and canary
I don't know how to explain it, but maybe the Magisk Uninstaller doesn't work properly on Canary builds?
Anyway, my issue now is modules don't get listed in the Magisk Manager.
No, you did not have two different Magisk builds installed at the same time. Can't happen...
And without more to go on (logs, etc) it's gonna be real hard to help with the module issue.
After a bit of searching and experimentation I was able to get EdXposed (YAHFA variant) working on my Galaxy A70 with Lineage OS 17 (never had problems with Magisk itself, just EdXposed).
FILES
lineage-17.0-20191203-UNOFFICIAL-a70q.zip
TWRP 3.3.1-0
Magisk Manager_7.5.2-b39f4075 0dc9f5c3.apk (Canary) EDIT: Corrected file version.
Riru_-_Core-v19.6(28).zip
Magisk-v20.4-0dc9f5c3(20303).zip
magisk-EdXposed-YAHFA-v0.4.6.0_beta.4471.-release.zip
EdXposed Manager 4.5.4.apk
The LOS I used is an older version (not sure if this has anything to do with anything, but thought I'd mention it). I chose YAHFA instead of SandHook because I've had better results in the past on other devices.
The Magisk files are a combination of 'Standard/Stable' builds, and Canary builds. For Canary files, start here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
PROCEDURENot sure if reboots are required after each flash, but I did them. Assume LOS & TWRP 3.3.1-0 already installed.
Install Magisk Manager—>Riru Core within it
From TWRP flash Magisk
Within Magisk Manager flash magisk-EdXposed
Install EdXposed Manager
The 99% reason I needed EdXposed was for XprivacyLua, and it's working fine. Here's some other Xposed modules I'm using, although BootManager might not be actually doing anything (haven't tested yet), it's not causing any problems.
Xprivacy Lua
MinMinGuard
Scoop
BootManager
Statusbar download progress
Xposed Edge
[EDIT] EdXposed is showing this error when hitting 'Download':
Downloading https://dl-xda.xposed.info
/repo/full.xml.gz failed: Chain validation
failed
...but I can live that. Just install modules like any other .apk
[EDIT] For some reason, absolutely no idea why, 'Download' in EdXposed now working as expected.
that's great thanks for your contribution to help A70 users.
TiTiB said:
After a bit of searching and experimentation I was able to get EdXposed (YAHFA variant) working on my Galaxy A70 with Lineage OS 17 (never had problems with Magisk itself, just EdXposed).
FILES
lineage-17.0-20191203-UNOFFICIAL-a70q.zip
TWRP 3.3.1-0
Magisk Manager_7.5.2-b39f4075 0dc9f5c3.apk (Canary) EDIT: Corrected file version.
Riru_-_Core-v19.6(28).zip
Magisk-v20.4-0dc9f5c3(20303).zip
magisk-EdXposed-YAHFA-v0.4.6.0_beta.4471.-release.zip
EdXposed Manager 4.5.4.apk
The LOS I used is an older version (not sure if this has anything to do with anything, but thought I'd mention it). I chose YAHFA instead of SandHook because I've had better results in the past on other devices.
The Magisk files are a combination of 'Standard/Stable' builds, and Canary builds. For Canary files, start here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
PROCEDURE
Not sure if reboots are required after each flash, but I did them. Assume LOS & TWRP 3.3.1-0 already installed.
Install Magisk Manager—>Riru Core within it
From TWRP flash Magisk
Within Magisk Manager flash magisk-EdXposed
Install EdXposed Manager
The 99% reason I needed EdXposed was for XprivacyLua, and it's working fine. Here's some other Xposed modules I'm using, although BootManager might not be actually doing anything (haven't tested yet), it's not causing any problems.
Xprivacy Lua
MinMinGuard
Scoop
BootManager
Statusbar download progress
Xposed Edge
[EDIT] EdXposed is showing this error when hitting 'Download':
Downloading https://dl-xda.xposed.info
/repo/full.xml.gz failed: Chain validation
failed
...but I can live that. Just install modules like any other .apk
[EDIT] For some reason, absolutely no idea why, 'Download' in EdXposed now working as expected.
Click to expand...
Click to collapse
Hello there.
I managed to install edxposed on Samsung A70 with stock android 9.
It's working fine, module's works.
But what I have been experiencing is that the phone has gotten very sluggish. The more modules I install the more it hiccups.
I currently have firefds kit [p], adblock reborn, edxposed manager and flat style indicator icons only.
Any advise?
I no longer own the A70...so, no. The only reason I saw your post is because I still had this thread bookmarked. Hopefully someone else has some useful info. gl
Can confirm.
Disabling the xposed modules fixed the lag.
Guess this is how its going to be
Some time ago after opening Magisk > Modules I saw a module called AC5BB80F and the "reboot to install" icon. I have never seen it, so I disabled it for security purposes but not removed because I wanted to discover it. But I haven't found anything. So, is it a virus/spyware/something else what is dangerous? Does anyone know what is it? And is it possible to extract ZIP of an installed Magisk module? I'm on unofficial ArrowOS from this thread.