Related
I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks
I had to go back to 18.0, heard 18.2 works as well.
qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone
I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help
Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me
Build 18120
Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better
Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either
Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden
After two years being stuck on an unrooted phone (Huawei), I'm thrilled to have everything working on OP7 x TWRP x Magisk.
On several threads I have read suggestions of Xposed modules that could be interesting, and saw that @topjohnwu published a thread with an Xposed installer apk and Xposed module for Magisk, which sounds amazing.
My question is: on OnePlus, does this work well, or would it be asking for trouble? The last thing I want now that everything is working is to make a wrong move that gets me into boot loops.
Also, if this is confirmed to work well, I see that there are several Xposed modules in the Magisk download section.
Is it "Xposed Framework, v90-beta3 created by rovo89"? Or the Tai Chi one, or the Riru ones?
Thanks for any advice!
Use edxposed, no problems so far for me
My biggest question is with Snapchat. I've read people getting banned because of using Xposed (even if no Snapchat specific module's are used).
Can anyone confirm or deny this? I just want to use it for a couple of modules like Amplify.
Its a bad idea! Snapchat thinks you use 3rd party app... Been locked out 3 times now...
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
who ah way said:
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
Click to expand...
Click to collapse
That isn't edexposed and isn't supported on pie
Arden144 said:
That isn't edexposed and isn't supported on pie
Click to expand...
Click to collapse
Thank you!
Will try edexposed on the next install, after backing up.
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
who ah way said:
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
Click to expand...
Click to collapse
Either. I used YAHFA with no issues for what i needed. Then i tried SandHook out of curiosity and found no difference.
Asking for trouble
Thank you both.
After TWRP backup, installed edexposed which involved three steps:
- riru exexposed core module (in Magisk)
- riru edexposed module by yahfa (Magisk)
- edexposed installer app (from GitHub)
EdXposedInstaller_v2.2.4-release.apk
https://github.com/solohsu/XposedInstaller/releases
System rebooted, SafetyNet status OK in Magisk.
As far as y'all know is this list of modules known to work on OP7?
Wouldn't even know where to start… But curious.
Edit: when I went to do a new Backup, the TWRP menu was unusual (it asked new questions about modifying the system). Decided to backpedal and restore to before exposed installation.
In the end, I just don't know enough to understand what risks I'm taking. In the hands of an expert user, it's probably safe, in mine, it's asking for trouble.
I'm not able to open the Android camera app anymore. WIth Edxposed disabled it works. So I'm wondering if anyone on Android 11 Nov update with Edxposed has camera working. If so, could you kindly tell me your setup (ie. Edxposed version, etc.)?
Edit: It looks like the Camera update from Nov 17 is what broke this. After uninstalling the update it works.
I have the same problem - how did you uninstall the update?
EDIT: Nevermind I figured it out ?
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Anyone found a solution for this? Only stock version is working.
Apparently if you clear the cache/data of Google Play Services, the APK Mirror Installer will have better luck installing other versions.
jljtgr said:
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Click to expand...
Click to collapse
For pass the dread "verification did not succeed" message, clear your Google Play framework data. You will need to resetting some personalization settings (you will know when it happens) but install of 8.x camera app will work.
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
I have the same problem
neo_lithic3K said:
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
Click to expand...
Click to collapse
I tried it but it didn't work, it only works with v 21.3 but the modules stopped working. Hopefully a solution comes out.
Add gcam to black list and reboot. Just tried and it works
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
I tried updating Google Camera to 8.1, immediately didn't work as expected.
Added to Exposed blacklist, rebooted... still didn't work.
Added to Exposed Compat list, rebooted... still didn't work.
Downgraded to 7.1, works again.
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Added to Magisk Hide, Xposed Blacklist, Xposed Compat list, rebooted; installed 8.1.101.x... force closes immediately.
thx, it worked for me. I did it after I already installed 8.1
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
I did this except add to magiskhide and it worked.. uninstalled updates. Compatibility list camera app, rebooted then open it. After update back to 8.1. and opened camera..works great again
What fixed the problem for me was downloading the latest canary YAHFA build in exposed manager. And flashing it in Magisk. I already had configured the compatibility settings for the camera module.
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
This is all I had to do on my Pixel 4a 5G also. Thanks!
For anyone wondering, in EdExposed, if I go to XHide and hide camera it works. Hope this helps!
Hide camera in black list.
Latest version of exposed, riru, and riruedxposed June 21 update stock rooted. Working flawlessly
LSPosed is a better choice
EdXposed has not been updated for too long
Anyone found a solution? I can't get it to work hiding gcam on xposed blacklist and magiskhide
Hi,
i have updeted to new Version on 9.12.2020 and the EdXposed don't work, have you the same issue?
I use magisk 20.4 and manager 8.0.3
module Riu v23.0(49) (2020-12-02)
Riu - edXposeed v0.4.6.4 (YAHFA)
EdXposed manager v4.5.7
i get after reboot the message "EdXposed Framework is not installed"
can you help me?
Hi,
So, I had to go back from v23.0 to v21.3 from riru-core. Then I had to reinstall EdXpoed, the manager as well. Felt 100 reboot made and now XposedLua is running again, yay.
I love this arogant manner.
I once learned, issue at Github are also there to have discussions so others can understand certain errors.
Be it so...
I hope other users who have the same problem find this post to have a solution.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.