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.
Related
Hi guys.
So I've used multiple backups to try to login to my snapchat account (an earlier one that worked before, and another one right before i logged myself out).
BUT, after i restore snapchat to that version and open it, it works for a moment (a second), then freezes, then logs me out with the message (you have been logged out).
I'm completely devastated.
S.O.S.
Thanks .
Phone: SAMSUNG-SM-G935V
Did you ever figuire this one out? Just happened the same to me.
Was without my android for a few days, so I logged into an iphone. Now when I get my android back, Im logged out.
I had a backup from Titanium backup, but - like you - it just logs me in for a short while and then (presumably) calls home and disconnects me.
Edit:
I found this article from yesterday:
"Snapchat will check your SafetyNet status only during your first login. If you root your smartphone after installing Snapchat, you can continue using the app as normal. But this doesn’t work the other way round, as Snapchat will no longer allow you to login after rooting. "
Edit2: (1 hr later, and it is fixed)
I use Superman ROM and Magisk for SU, but should work on any ROM with Magisk.
There are many good tips for bypassin SafetyNet with Magisk on this page:
I ended up using the Module "Universal SefetyNet Fix". Downloaded it, flashed it in Magisk, restarted - DID hide it in Magisk Hide (which they say you don't need to, but I did anyway). Then I loaded my titanium backup, and got the failed login - but that's ok, because now the safetynet hide works, so I just logged in normally. No need for titanium backup version.
he universal fix is working for me too. Also i made a video on how to get multiple accounts on snapchat and other social media apps. Check it out: https://goo.gl/g6d947
Qarie said:
Hi guys.
So I've used multiple backups to try to login to my snapchat account (an earlier one that worked before, and another one right before i logged myself out).
BUT, after i restore snapchat to that version and open it, it works for a moment (a second), then freezes, then logs me out with the message (you have been logged out).
Click to expand...
Click to collapse
I rooted using SuperSU before installing Snapchat and I ran into the same problem. Luckily, an app called 'Root Switch' did the trick for me.
Guide (Assuming you are already rooted using SuperSU and not able to log in at all now or you do not want to switch to Magisk):
1) Install Root Switch https://goo.gl/5nPJUm
2) Open Root Switch > tick on 'Stop all su daemons' > and then toggle 'Enabled' to 'Disabled' (This stops all the apps from detecting root on your phone)
3) Try logging into Snapchat and it should work fine
4) Go back to Root Switch > toggle 'Disabled to 'Enabled' > untick 'Stop all su daemons' and ta da, you are back to your rooted phone. (If you are unable to do this step, just restart your phone)
Optional: You can delete the app now but if you think you will need it for something else, you can keep it.
Cheers
Hello, can you help me a bit, i'm in the same situation:
I have a backup of my snapchat, some days ago the restore with titanium bakcup worked fine, but now like you said in first post after restored data, it log in, then freezes, then logs me out
I have Masgisk v14, tried the Universal SefetyNet Fix module but still got the "you can't loggin", also tried magisk hide but still can't log in
Also tried to uninstaller xposed
I just tried Root Switch and still can't log in snapchat
remi13014 said:
I have Masgisk v14, tried the Universal SefetyNet Fix module but still got the "you can't loggin", also tried magisk hide but still can't log in
I just tried Root Switch and still can't log in snapchat
Click to expand...
Click to collapse
@remi13014
1) Use the Root Switch method after uninstalling Snapchat first:
~ Uninstall Snapchat > Root Switch > Install Snapchat and then try logging in > Root Switch to enable root again
When you flashed Magisk, did you flash the SafeNet tools as well?
I was uninstalling an app inside Es file explorer and as soon as it finished my tablet rebooted. Now the home and app switcher buttons are gone, not invisible but gone. Plus swiping down from the top of the screen only reveals the wifi, Bluetooth, battery indicator. It doesn't even show the settings icon. I can launch the settings app from the app drawer. I tried to go to the developers tab and it says it's not available on this user(though it was before). Trying to open the user tab does nothing. It doesn't open. I can't reenable developer options either. Not working either. Am I screwed or is there a fix. Shield K1 5.1 rooted with Twrp installed and BK 10 Kernel. Any help would be appreciated.
Restore Nandroid or reflash a K1 Rom of choice and done :good:
Ok I factory reset and now everything is working again except I can't get system r/w access. I have SuperSu installed and rooted but terminal doesn't use root access even though I gave it root permission. Weird.
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
My bank says my phone is successfully using the app logging in but the app is throwing an error that says something along the lines of biometrics failed or something, I've uninstalled the app. Factory Reset in TWRP and can't get it to stop. If I factory reset in Android will I get a different result? I can't use my banking app and it's only my device that this is happening on my buddy has same phone same setup same bank only my phone is the issue.
Thoughts??
Can anyone tell me how to perm remove encryption on my device so when I switch slots in TWRP for flashing custom ROMs my files are not encrypted??
TWRP supports encryption.
If it won't decrypt you are using the wrong version.
You are rooted with Magisk? If so, make sure in the Magisk Manager app, that Magisk Hide is toggled "on" for the banking app (3-line menu in Magisk Manager, tap Magisk Hide, and "check" the banking app).
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
LGZACRO said:
Hi,
I have BV9800Pro with Android Pie (MediaTek P70) and now I noticed that after reboot, some banking apls and lockmypix app has problem with fingerprint. Jf I go to settings, remove it and add it again, then all is ok again with all apls, but after reboot, banking apps + lockmypix dows not allow for me to unlock uaing fingerprint because "biometric data changed" as one app tells me.
Any ideas? Has any one had such issue? How to fix this?
P.S., i Have tried ro disable xposed and magisk, nothing helped, only factory reset, but after that, I couldn't identify what caused this issie to come back again.
P.P.S., if I have let's say 2 fingerprints saved, and delete any of them, all appa back to normal until I reboot.
Click to expand...
Click to collapse
Just a issue that had developed while you was building your daily driver
Sent from my moto g(7) play using Tapatalk
PoochyX said:
Just a issue that had developed while you was building your daily driver
Click to expand...
Click to collapse
Any idea what might caused it? P.S., previously I have flashed the complete rom except userdata partition, and the issie was still there. Even if I disable all magic modules and xposed as well, the issue remain.
Has anyone faced something like that? Personally, I think some file is being overwritten after reboot and it might cause this issue. That's the only logical explanation I can figure out.