Database Info

Fingerprint not working / wickr me (login) . APP

Anyone here using wickr me ?
I had it working some time ago. Now, on my new OP6 ( coming from OP2). The login screen shows option for Password AND Fingerprint but pressing Fingerprint-Sensor does not do anything, I always have to type in the normal password.
I alread resetted the app (removed all registered devices in wickr me), reinstalled it, cleared dalvic cache. Nothing helped so far. All permissions are granted for the app.
Any Ideas? TIA!
Oxygen OS 5.1.9, Magisk 16.7, Xposed Systemless, TWRP

I use Wickr Me but have not rooted my phone. Fingerprint sensor is working for me during login. But you have to touch the fingerprint icon first before you can use your fingerprint.

thanks for your input, but that didn't help. pressing the fingerprint-icon does nothing, unfortunately...

Solved. Complete uninstall, device removal.
That helped.

Can't successfully hide root with magisk 18.1 for square reader app

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

Settings Force close

I installed a new version of the settings app (I'm assuming from the OnePlus 7) and now it only Force closes. Any suggestions on how to downgrade it? I can't access the app info. I'm not rooted and don't want to. I also can't access recovery because I guess my phone is encrypted and asking for a password but I never set it.

What did you download, from where? What OS? Substratum (this could be it if your themed)? Logs?

It's the OnePlus settings app from apkmirror. No root or mods or themes. Open Beta 18

doalittledanse said:
I installed a new version of the settings app (I'm assuming from the OnePlus 7) and now it only Force closes. Any suggestions on how to downgrade it? I can't access the app info. I'm not rooted and don't want to. I also can't access recovery because I guess my phone is encrypted and asking for a password but I never set it.
Click to expand...
Click to collapse
The password for recovery is the PIN you have on your phone.
https://forum.xda-developers.com/showpost.php?p=79552325&postcount=16

Hi,
I had the same issue as you but I was rooted and had TWRP. I tried to install OOS 9.0.5 again but it didn't worked...
So the last idea I had was to boot on the second partition.
And it worked.
You can try to boot on fastboot and type : "fastboot--setactive=_a" or "fastboot--setactive=_b" to switch partition and reboot. It should work for you too.

Oh that's a good idea. I ended up getting one of the app uninstaller apps from the play store and was able to uninstall the settings update.

Can I install SuperSU on the OnePlus 7 Pro?

Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay

TomatoesOnBluRay said:
Hi everyone,
I'm curious if anyone has gotten the SuperSU root method running on this phone. I know that magisk exists but snapchat has problems with magisk for some reason so I would prefer to use SuperSU instead. I already have the latest twrp installed if that helps at all. Flashing the SuperSU zip doesn't seem to do anything so I'm hoping somebody has figured this out already.
Thanks,
TomatoesOnBluRay
Click to expand...
Click to collapse
just realized i put this in guides instead of questions and answers. Is there a way to move it? Serious noob here.

Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?

Snapchat wont get along with Supersu either. At least you could try to hide Magisk from Snapchat

I'm abit curious now, why would you prefer having supersu when magisk works the same way but even better?

schmeggy929 said:
Do not think anyone has used SuperSU in a few years really. What is wrong with Snapchat and rooted with Magisk?
Click to expand...
Click to collapse
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.

TomatoesOnBluRay said:
it seems like supersu hasn't been updated in a couple years now, so you're absolutely correct. Snapchat keeps locking me out of my account for "using a third party app" even though I haven't been using a third party app. My guess is that it's detecting root somehow even when I have magisk hide enabled, magisk changed to manager, and xprivacylua restricting snapchat's access to files. I even tried using parallel space to copy snapchat into an isolated environment, but it doesn't even log in. It might have something to do with Oxygen OS, but I'm not sure. Although it's unlikely, I'm trying to see if there is a way to install SuperSU on this phone because I know snapchat works as it did on my old phone (if you log in before you root, of course). If it's not possible, I'll just have to figure something out.
Click to expand...
Click to collapse
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.

schmeggy929 said:
You need to Magisk hide Snapchat. Go to menu(top left, 3 lines) click Magisk Hide. Scroll to Snapchat and check it. Clear data for Snapchat. Log back in.
Click to expand...
Click to collapse
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.

TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Weird, never had an issue with Snapchat and was always rooted.

I used to have the same issue with snapchat until I started using the Magisk Beta versions, since then I haven't had that issue at all. Which version of Magisk are you using?

TomatoesOnBluRay said:
I did this but it didn't work, it still locks my account. Snapchat seems to have some weird form of detection that can't be worked around.
Click to expand...
Click to collapse
Get it up and running, create a backup with titanium and when you are on magisk, restore the data.
Thats how i used to do it when it wouldnt let me log in. But I havent had the issue for years with magisk. Ensure you are using the current and ensure you pass safety net.

Bypass SafetyNet Attestation

I'm trying to bypass the SafetyNet chore by using MagiskHide and tools like this one.
I have yet to have success.
I have read lots of information about the topic, but most seems irrelevant and obsolete.
I use a custom ROM with Root enabled.
Can anyone please point me in the right direction of solving this issue?
Thank you.

It would help if you stated which ROM or Android version you are on...

pnin said:
It would help if you stated which ROM or Android version you are on...
Click to expand...
Click to collapse
Android 11, Octavi OS.

I see... can't really help, no experience.

Magisk, Universal SafetyNetFix and MagiskHideProps

robogo1982 said:
Magisk, Universal SafetyNetFix and MagiskHideProps
Click to expand...
Click to collapse
Of course, I have that installed and working according to tutorials, already...
Still, not working.

"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.

Another reboot seems to have fixed the SIM service issue.
Is this really it? Is the NFC problem really fixed after such a long time?
I cannot believe it.
I will test this for some time, just to be sure....

Did you force basic attestation in props?

I'm using ArrowOS 12 (ArrowOS 11 before that) and never had problems with SafetyNet.
Using latest Magisk, Zygisk and DenyList enabled. As for modules, I use GPay SQLite Fix and Universal SafetyNet fix. No other fixes or modules were necessary

if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
there's no need to install modules or do anything else, just check all apps U need on DenyList but the main app to deny is still "Google Services"

xSokol said:
if it's for banking apps, just check "Google services" on DenyList (first of all click the dots on right upper corner and check system apps). I was fighting that some time ago.
Click to expand...
Click to collapse
Enabled DenyList, checked Google Play Services and it stays checked. Checking Google Services Framework gets reverted each time I visit DenyList. There is no "Google services".
I found `*.gservices` as a sub-category of Google Services Framework. Disabled. Rebooted several times, after trying out multiple possibilities, but none did work. One time, even basic attestation was broken, which needed another reboot to fix.

no, sorry for my rush, it was about Google Play Services. I have never "denied" Google Services Framework.
what I would do is uninstall modules like "safetynet fix" and reboot to twrp, there's a fix for zygisk, install that one.
then reboot to system, clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services and search for Google Play Services again (I have to check it aftet every reboot somehow).
I just have had similar issue an hour ago with Revolut app because I crashed my system and had to dirty flash what swiped Magisk.
just be patient, it's not hard or complicated work

xSokol said:
there's a fix for zygisk, install that one.
Click to expand...
Click to collapse
Which one? Where? How?
xSokol said:
clear all the data of an disobedient app, then go to Magisk DenyList and look for the app, check all services
Click to expand...
Click to collapse
Check the app or what services? What exactly?

ok, then..
if You go in TWRP to "advanced" and then to "magisk" (sorry if the name isn't correct, I don't focus on names of options) and there are options like "install magisk 24..." or "uninstall magisk 24...", under that there are fixes, so You should find it, it's under "SafetyNet Fix". You need Zygisk, so get fix for Zygisk.
I was about the app that's not working, if You click on the bar with the name it will show its services. in standard Magisk denies only the main service of an app, but some apps require checking all of them.

hello @Aki-to , did U manage?

xSokol said:
hello @Aki-to , did U manage?
Click to expand...
Click to collapse
I did not dare to go into TWRP, because I am not absolutely sure if data or storage encryption works perfectly fine with TWRP on Android 11. I don't want to boot into TWRP and have everything encrypted and therefore unusable.
I did so many flashes and some of them had this problem, but I cannot remember if it was because of a failed flash or because it actually did not work.
I also do not want to remove encryption in Android Security Settings every single time I visit TWRP.
Posts like the following also sound very concerning.
[FIXED] How to remove data encryption in TWRP
Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+...
forum.xda-developers.com

there's no need to remove encryption, nothing abiut that.
I just have changed MIUI to 13 today, didn't change anything on TWRP, just installed Magisk from TWRP and checked all the bank apps, GPay and Google Play Services

Aki-to said:
"Fixed" it by appending `LEGACY_MIFARE_READER=1` to `/system/vendor/etc/libnfc-nci.conf`.
However, this breaks my SIM service. Not sure, how those features are related, but here we are.
Click to expand...
Click to collapse
Hi, could you share your Magisk module?

Haobin said:
Hi, could you share your Magisk module?
Click to expand...
Click to collapse
Sure, wanted to do that, anyway, but forgot about it.