Database Develop

[Wrong Section][Q] Xposed NFC unlocking related

Hi everyone, I posted a reply in the NFC unlocking module thread but i guess its better to ask question here?
I installed the NFC Unlocking module by MohammadAG and it works great, however I am encountering a small problem.
the NFC unlocking module works by recognizing the NFC chip ID, however if the NFC tag has some message already stored in it ie: website URL, when using that tag to unlock the device the browser will be activated at the same time. I wonder how do I prevent this? I am working on a small app and want it to work together with the NFC unlock, that is the APP will be only triggered after the screen has been unlocked, (in practice, the first tap unlock the screen, and second tap trigger the app)
I tried few days and couldnt figure it out, any suggestions will be very helpful
Thank you very much for your help!

You should ask in the module's thread: http://forum.xda-developers.com/showthread.php?t=2478163
Please read the stuck threads of this section, it's not for module specific support.

Xposed module "Xprivacy" gets detected and force closes app - Please help!!

I have installed XPOSED and with that XPRIVACY to control what information apps like FACEBOOK and MESSENGER leaks over the internet, and what information they can access on my phone....
But recently my banking app was updated, and it now detect the XPRIVACY Module, if that module is ACTIVE inside XPOSED INSTALLER... If i deactivate the XPRVACY Module, and restart, then I can start the banking app with no problem...
Obviously its a drag to DISABLE MODULE-->RESTART-->DO BANKING-->ENABLE MODULE-->RESTART-->BE PROTECTED AGAIN
So can anyone point me in the right direction on how to keep XPRIVACY enabled, while still being able to use the banking app...
The banking app in question is:
https://play.google.com/store/apps/details?id=no.spv.mobilbank
So if you have XPOSED and XPRIVACY, you can download this app, and see that it FORCE CLOSES as long as the XPRIVACY Module is active inside XPOSED...
If you disable XPRIVACY you will see the app starting up, and displaying some login screen...
Can anyone help me in this endavour??
I've tried using SudoHide & MinMinHide, but those did not work for this... as long as the module is active inside XPOSED, then the app will force close...
Rootcloack did also not do anything for this specific problem...
Im not sure what method the app uses to detect that the module is installed and active... but the app does not care, if the XPRIVACY module is installed, but not active, also it doesn't seem to care about XPOSED itself, and the rest of XPOSED's modules... Its just when XPRIVACY Module is activated inside XPOSED...
Please give me suggestions as where to go... what to do... what to test...
Since Xprivacy is freeware, I was considering downloading it, and renaming all the files and the code in the files, to not include "xprivacy" text or "bikhorst" text (package name), but building the app, seems to be my problem...
My pc is old, and does not support the never versions of android studio...
Is there something in the banking app itself, that i could edit, using APK EDITOR perhaps... (or similar programs) to stop the app from checking for XPRIVACY (active) Module...

Is there some other apps that I could try, that might somehow stop only that one app from detecting that I use XPRIVACY to protect my privacy where I can....
I have tried:
"No Device Check"
"RootCloack"
"SudoHide" & "MinMinHide"
What I seem to need is some XPOSED MODULE, or other app that can "hide the presence of the active XPRIVACY module"...
I've tried to use XPRIVACY itself to deny the https://play.google.com/store/apps/details?id=no.spv.mobilbank (no.spv.mobilbank) app from checking the system for the presence of XPRIVACY, and if I put checkmarks on categories "IPC" and "SHELL" inside XPRIVACY for the "no.spv.mobilbank" then XPRIVACY starts up, and asks if I want to allow or deny access to shell/ipc and then the app crashes... (as it detects xprivacy if allowed that access, or it just crashes fast, if denied that access, so what can i do inside XPRIVACY to force a false check and then avoid a crash, so that the app keeps loading)
I've also tried to use APKTOOL to reverse engineer the app, since there is a config.xml file that contains the two following lines of code, that seems to have something to do with the checking, but the apktool fails at rebuilding the edited apk file, so those changes cannot so far be saved (by me) to that apk file...
(the file with the xml I want to change: c:\OUTPUTFOLDER\res\xml\confiig.xml)
(correct path if you let APKTOOL decompile the app to c:\OUTPUTFOLDER\)
And the CHANGES i think will stop the behavoiur:
(when i set the ONLOAD to FALSE in these two paragraphs)
<feature name="Whitelist">
<param name="android-package" value="org.apache.cordova.whitelist.WhitelistPlugin" />
<param name="onload" value="false" />
</feature>
<feature name="ExternalAppBlock">
<param name="android-package" value="no.spv.mobilbank.lib.SPVExternalAppBlock" />
<param name="onload" value="false" />
</feature>
Too bad there is no way to try this for me, ass I cannot get the APKTOOL to reassemble the files back to an APK file... It only does the decompiling correctly (im using APKTOOL 2.2.1)
Anyone with any good ideas, or suggestions as what to try, or what to do different?
If anyone could build an XPOSED module that somehow disabled this check, performed by no.spv.mobilbank then I'd be most gradeful !! (but I don't know how to build that myself)

alexdata said:
I have installed XPOSED and with that XPRIVACY to control what information apps like FACEBOOK and MESSENGER leaks over the internet, and what information they can access on my phone....
But recently my banking app was updated, and it now detect the XPRIVACY Module, if that module is ACTIVE inside XPOSED INSTALLER... If i deactivate the XPRVACY Module, and restart, then I can start the banking app with no problem...
Obviously its a drag to DISABLE MODULE-->RESTART-->DO BANKING-->ENABLE MODULE-->RESTART-->BE PROTECTED AGAIN
So can anyone point me in the right direction on how to keep XPRIVACY enabled, while still being able to use the banking app...
The banking app in question is:
https://play.google.com/store/apps/details?id=no.spv.mobilbank
So if you have XPOSED and XPRIVACY, you can download this app, and see that it FORCE CLOSES as long as the XPRIVACY Module is active inside XPOSED...
If you disable XPRIVACY you will see the app starting up, and displaying some login screen...
Can anyone help me in this endavour??
I've tried using SudoHide & MinMinHide, but those did not work for this... as long as the module is active inside XPOSED, then the app will force close...
Rootcloack did also not do anything for this specific problem...
Im not sure what method the app uses to detect that the module is installed and active... but the app does not care, if the XPRIVACY module is installed, but not active, also it doesn't seem to care about XPOSED itself, and the rest of XPOSED's modules... Its just when XPRIVACY Module is activated inside XPOSED...
Please give me suggestions as where to go... what to do... what to test...
Since Xprivacy is freeware, I was considering downloading it, and renaming all the files and the code in the files, to not include "xprivacy" text or "bikhorst" text (package name), but building the app, seems to be my problem...
My pc is old, and does not support the never versions of android studio...
Is there something in the banking app itself, that i could edit, using APK EDITOR perhaps... (or similar programs) to stop the app from checking for XPRIVACY (active) Module...
Click to expand...
Click to collapse
Have you tried to post this question on the XPrivacy thread?
Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).

Ibuprophen said:
Have you tried to post this question on the XPrivacy thread?
Click to expand...
Click to collapse
Well, not yet.... mostly because asking the same question, several places in the same forum, is not so much liked in the other forums I use...
There is no bug with Xprivacy itself, nor with Xposed, but since this is a setup that runs Xposed, i found it most logically to ask it here first...
As more people might visit the Xposed part, than the Xprivacy part of the forum...
But... I might repost the question in Xprivacy aswell...
Would you perhaps have a direct link to the Xprivacy part of this forum (im still quite new on this forum) ??

alexdata said:
Well, not yet.... mostly because asking the same question, several places in the same forum, is not so much liked in the other forums I use...
There is no bug with Xprivacy itself, nor with Xposed, but since this is a setup that runs Xposed, i found it most logically to ask it here first...
As more people might visit the Xposed part, than the Xprivacy part of the forum...
But... I might repost the question in Xprivacy aswell...
Would you perhaps have a direct link to the Xprivacy part of this forum (im still quite new on this forum) ??
Click to expand...
Click to collapse
Here it is but, keep in mind that if there's a support thread for something, it's better to post within that thread so a dev or someone else can help you out.
http://forum.xda-developers.com/showthread.php?t=2320783
Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).

I know this is an old thread, but people still come here from google search looking for solutions to their issues. So, here is what you can try:
I think you have tried it, but still. On the main window of xprivacy, uncheck the 2 boxes beside the banking app. Xprivacy will not block anything for this app. Now clear all the data of the banking app from settings > applications or wherever it is on your phone. Check it the app works now.
If the above does not work do this. Go back to xprivacy > tap the icon of the banking app on left side. This will let you change permissions only for that app. Make sure all the boxes are clear. Go to bottom > check the first box next to System > tap the arrow on the left side of system. Now, check the first box of these 6 sub-permissions under system:
getInstalledApplications
getInstalledPackages
getRecentTasks
getRunningAppProcesses
getRunningServices
getRunningTasks
Now clear all the data of the banking app like in the 1st step and check if it works.
One of these 2 steps should work.
NOTE: Just installing Rootcloak does not do anything. You need to add the package name of the banking app to make it work. Which can be done by opening Rootcloak and going to manage apps and adding it from the list.

[Mod][Xposed] Hide X for driver online

MOD EDIT: Closing until information is updated and guide exists (and is in English).
Original OP Text Translated from Indonesian said:
Intro
This is a very simple module that tries to prevent the app from detecting "Allow mock locations" in the developer settings.
This system responds as if the setting is off.
Purpose
Eliminate detection in online driver application In Indonesia
Settings
By default, this module affects every application in your phone.
Use it wisely.
Click to expand...
Click to collapse

enable biometrics with no screenlock

Pretty basic questions whether i need an app that does this or a workaround i just want to use my biometrics without a dam screenlock? Such as samsung pay, samsung pass, my bank apps and others. Dam google phone arent adding feature like before they are going back in time.

Except without root.

saulc1981 said:
Pretty basic questions whether i need an app that does this or a workaround i just want to use my biometrics without a dam screenlock? Such as samsung pay, samsung pass, my bank apps and others. Dam google phone arent adding feature like before they are going back in time.
Click to expand...
Click to collapse
Actually you can without root. Set your biometrics normally with a password or a pin then go back to lock screen options and change it to swipe or no lock. And from there you will get a warning and it will have 2 options. One is remove data and the other is keep it. If you keep it it will work with the other apps. I have PayPal installed and I did the same thing also Samsung Pay.
And I'm not rooted using stock

Stevieboy02008 said:
Actually you can without root. Set your biometrics normally with a password or a pin then go back to lock screen options and change it to swipe or no lock. And from there you will get a warning and it will have 2 options. One is remove data and the other is keep it. If you keep it it will work with the other apps. I have PayPal installed and I did the same thing also Samsung Pay.
And I'm not rooted using stock
Click to expand...
Click to collapse
No dice. I know that already. My fault i did say basic. Thats the problem. When i put keep data like ice done for a long time but now i get this message and i cant use the fingerprint or iris with any app.

saulc1981 said:
No dice. I know that already. My fault i did say basic. Thats the problem. When i put keep data like ice done for a long time but now i get this message and i cant use the fingerprint or iris with any app.
Click to expand...
Click to collapse
Well then you might need root access. I don't have root access but it works for me just fine so im not sure.

use a secure settings app to set automatic lock delay to something ridiculously high like 540000(several days)
and turn off "lock instantly with power key".
normally you're limited to 30 minutes by the settings app, but if you use a secure settings app you can manually change it to something much higher.
using this setup you no longer need a pin coming from standby(lockscreen is skipped completely) unless you don't touch your phone for several days.
you'll still need a pin when turning on your phone or accessing lockscreen settings, but that's not something you'll do multiple times a day.
this does require ADB(to grant the hidden "secure settings" permission to the secure settings app once) but doesn't require root.

You can't do it anymore. AFAIK, Samsung changed this with the Jan or Feb patch. There's an article on sammobile that highlighted the change.
Edit : Here's the article : https://www.sammobile.com/news/on-o...ed-and-stored-only-with-a-secure-screen-lock/
Sent from my ONEPLUS A5010 using Tapatalk

saulc1981 said:
Pretty basic questions whether i need an app that does this or a workaround i just want to use my biometrics without a dam screenlock? Such as samsung pay, samsung pass, my bank apps and others. Dam google phone arent adding feature like before they are going back in time.
Click to expand...
Click to collapse
I don't use any screenlock etc on my phone.
What i have done is place all my relevant apps eg banking, password manager etc in the Secure folder
(knox protected) If i want to use them i use fingerprint to unlock my secure folder.
Then i use fingerprint, to log into my banking app or use fingerprint for my password manager.
Further, I only install the relevant app (Google Play) that i want, inside secure folder. So no duplication of app.

saulc1981 said:
Pretty basic questions whether i need an app that does this or a workaround i just want to use my biometrics without a dam screenlock? Such as samsung pay, samsung pass, my bank apps and others. Dam google phone arent adding feature like before they are going back in time.
Click to expand...
Click to collapse
I found a small loophole if you have a bluetooth device. You can turn smart lock on and have it stay unlocked as long as its connected to that device be it headset, smartwatch, etc. You can also do it based on location.

Stevieboy02008 said:
Actually you can without root. Set your biometrics normally with a password or a pin then go back to lock screen options and change it to swipe or no lock. And from there you will get a warning and it will have 2 options. One is remove data and the other is keep it. If you keep it it will work with the other apps. I have PayPal installed and I did the same thing also Samsung Pay.
And I'm not rooted using stock
Click to expand...
Click to collapse
It will On SOME apps paypal abd lastpass for example but not others Chase bank for example. Also whos bright idea was it to remove app long press option functionality? No more app info, uninstall etc. Why do they do this s%it?

demize! said:
It will On SOME apps paypal abd lastpass for example but not others Chase bank for example. Also whos bright idea was it to remove app long press option functionality? No more app info, uninstall etc. Why do they do this s%it?
Click to expand...
Click to collapse
Lol. I know but actually some functions still work on the app long press

thedicemaster said:
use a secure settings app to set automatic lock delay to something ridiculously high like 540000(several days)
and turn off "lock instantly with power key".
normally you're limited to 30 minutes by the settings app, but if you use a secure settings app you can manually change it to something much higher.
using this setup you no longer need a pin coming from standby(lockscreen is skipped completely) unless you don't touch your phone for several days.
you'll still need a pin when turning on your phone or accessing lockscreen settings, but that's not something you'll do multiple times a day.
this does require ADB(to grant the hidden "secure settings" permission to the secure settings app once) but doesn't require root.
Click to expand...
Click to collapse
Hi @thedicemaster this sounds like a great solution. I have been trying, but can't get it to work. Can you tell me more on how to do this? Appreciate it!
EDIT: Nvm, I managed to do it

Delete me

It's been years already but I have a way to get it to work without root without installing any apps. I hope it helps some one.
You will need adb and usb debugging on. Open cmd / terminal and execute these 2 commands:
Code:
adb shell settings put secure lock_after_timeout_rollback 86400000
adb shell settings put secure lock_screen_lock_after_timeout 86400000
86400000 = 24 hours in miliseconds. You can change to a number that you find suitable.
This secure settings will survive after reboot so you only need to do once.

com.adobe.ims.accountaccess (Adobe Account Access) seems to detect Magisk, even while hidden.

H! So I am actually unsure where to post this..
Here's hoping you can figure something out and not be mad at me if this is the wrong place to post this.
Initially, i was going to post this as a Bug report on Github. However, I figured this was not correct.
Technically speaking this also isn't really an issue with magisk itself, more that adobe might have found a way to circumvent magisk anti detection methods.
In short: The App "Adobe Account Access" (com.adobe.ims.accountaccess on the play store: https://play.google.com/store/apps/details?id=com.adobe.ims.accountaccess) seems to have found a way to detect magisk and/or root, even though root detection is hidden in magisk.
The App just displays a prompt, saying "Device not supported. Sorry, your phone is not supported for Adobe Account Access.", even though the device used should be supported.
I checked with adobe community support on whether my Phone is supported or not and according to them, it should indeed be supported: https://community.adobe.com/t5/acco...-access-app-device-not-supported/m-p/11696613
I suspect they have found a way to get around all magisk anti detection methods and i would be grateful if someone would be kind enough to check if there is a workaround or if magisk's detection prevention needs an update.
Unfortunately, i don't have much more to say other than that..
There aren't any magisk log entries that would indicate something went wrong (only entries mentioning the app are"i" loglevel, one coming from hide_list_add and one coming from proc_monitor).
I could not find anything out of the ordinary in the logcat, although i suppose i could be more thorough with my search.
My technical/general info would be:
Magisk Version used: 22.0 (22000) (18)
SafetyNet integrity: Both basicIntegrity AND ctsProfile = pass; evalType = BASIC
ROM used: OxygenOS 10.0.11.GM21BA
Android version: 10
Device name: OnePlus 7 Pro
"Adobe Account Access" App version: 1.6
+++ Please feel free to ask for any additional info in case I missed it +++
Thanks in advance for any productive suggestion!

When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list, and with the Magisk app unhidden.

Didgeridoohan said:
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list.
Click to expand...
Click to collapse
Oh? That is peculiar.. Damn, that implies an issue somewhere else i reckon ://
It displays it immediately after launching the app. The very first screen..
What phone and which OS (/ROM) are you using? Might just be that my phone is genuinely not supported and the folks over at the adobe community forum lied when saying my phone should be compatible..
Also, which android version are you on if you don't mind me asking?

You don't have any modules installed? No edxposed or lsposed, or magisk modules?
Have you tried root detection apps like Root Beer Fresh to see if indeed the app is unable to detect root? If you try any such app, remember to add it to the Magisk Hide list beforehand, otherwise the app will clearly detect root.

It's a OnePlus 3T with Android 9 ArrowOS. As stated above, it could very well be a module, like EdXposed. Or a root app, or a file or folder on your device, or something completely different.
It's not detecting Magisk at least, that's for sure...
General root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

@Barrel Titor
Samsung Galaxy S7 Custom 9.0 Pie, Magisk 22 root with random name, application without hiding works fine.

Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.

Barrel Titor said:
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Click to expand...
Click to collapse
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.

mario0318 said:
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
Click to expand...
Click to collapse
I cannot find any results using this search term on google other than my own post on the adobe community forums.. This one: https://community.adobe.com/t5/acco...access-app-device-not-supported/td-p/11695914

@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?

Barrel Titor said:
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Click to expand...
Click to collapse
Well, the well known magisk module MHPC or Magisk Hide Props Config comes to mind. You can change device fingerprints and maybe also give the Device Simulation feature a go, or custom edit any range of configurable props.
You could do so without the module editing the build.props yourself. Or if you stick with edxposed and deal with not having magisk manager's hide enabled, perhaps any of the device spoofers on the xposed repo could fool the app. Or Sudohide if you set Adobe app to hide from any and all apps that are root relevant. May also consider removing directories in your internal and removable storage for things like TWRP or PBRP, Titanium Backup, xposes, etc, you know, things that a simple media scan looking for any sign of root apps might pick up.
But for now, I'd give MHPC a try and change device fingerprint and maybe enable device simulation if simple fingerprint change doesn't work.

I'm having the same issue on a rooted OnePlus 8T

Same for me on op7 pro. Hiding with somiko but Adobe still not working. Nor could I bypass square, it notes root when it pairs Bluetooth