Hi everyone,
I'm new on xda and I come here because I struggle to install this app on my rooted Galaxy S4 with CyanogenMod 11: "Paiement mobile (pour Orange)" (sorry, I'm new, so I cannot post urls).
In fact, this app has not been declared by the devs (on the Google Play) to be compatible with my phone, despite the fact that I have the specs to run it (NFC payment).
I asked a friend who was able to download the app to upload it on Aptoide, giving me the opportunity to download the apk on my phone (this apk is available in this thread). I tried to install it, but I get the following the error: "app not installed".
I would like to force the installation of the app. I tried many ways, like using apps that use root access on the phone, without success (for example, I tried with "System Apps Installer" on the Google Play, but I get a problem with mounting /system). I also tried to install it with the command line tool, but I get the error "[install_failed_invalid_uri]". I tried to change the permission of the /data/local directory and /data/local/tmp with ES file explorer, but it did not change anything.
In addition to this, I'm not able to enable usb debugging in the developper options (to install the apk with adb), because every time I activate the option, it becomes disabled in the following seconds.
It seems to be a little bit complicated, because I seem to have different problems, but I hope that someone here will be able to help me !
Thanks for your help,
Aquignis.
The issue is most likely Cm. They alter things so some that normally work no longer work
I suceeded to solve the "[install_failed_invalid_uri]" error in the command line tool by also changing the permissions of /data.
After that, I got another error (yes, one more, but the last) that made me discovering what's the real problem in this situation: "install_failed_missing_shared_library". By doing some researches on the web and exploring the apk, I understood that the app use a library called "org.simalliance.openmobileapi" that corresponds to the work of SIMalliance, who developped an API called "Open Mobile API", which notably enables communication with NFC sim cards and must be integrated to the build of the ROM. This system is used by many banks in Europe and has been integrated in the stock ROM of many NFC devices by the important manufacturers, but not by Cyanogenmod devs in the last stable release of CM 11 for the Galaxy S4.
Like you said it, the problem was CM
I asked them if it has been integrated in CM 12, because that is why the app is said to be incompatible with my device by Google Play which automatically checks which libraries are installed on your device (I'm waiting for their answer). The other solution would be to add the library to the CM build by myself, because it seems not to be very complicated, but I'm not qualified enough to do this !
If it is not part of aosp I wouldn't count on it being added to be honest. Not to mention most banking apps refuse to work if the Rom has root as it can cause security issues.
Yes, the root seems to be a problem with some apps according to the work of this man.
On the other hand, I think that this API is important enough to make CM devs pay attention to it, because it is used in many countries (except the USA which use only HCE, I believe). If only I was able to build it myself !
Related
I bought this nice minicomputer - MK812 Mini PC Dual-Core Android Camera Mic BT 4.2.1 and I relied on the fact that since there is Android 4.2 installed, I can use switching users, but unfortunately this function is disabled. I need to get it to work.
Of course, I googled. This is what I've already tried:
http://www.pocketables.com/2013/03/how-to-enable-multiple-user-mode-on-cyanogenmod-10-1-and-some-other-android-4-2-2-roms.html
The problem is that this command pm get-max-users returns Unknown command get-max-users.
Furthermore, when I enter SetProp fw.max_users 8, it has no effect, even after a reboot. The command pm usernameyouwanthere create-user is also without effect.
http://forum.xda-developers.com/showthread.php?t=2187934
App - 4.2 Multiple users feature enabler
This app can't be installed by Google Play (apparently MK812 is not a compatible device). Since I couldn't get APK anywhere to download, I downloaded the source code and compiled it and generated APK. Unfortunately, can't be installed either.
I studied the source code and found out that even if i was able to get it installed, it wouldn't have worked anyway, because this app runs similar commands (as those above) instead of the user.
https://play.google.com/store/apps/details?id=fahrbot.apps.switchme
This could be a solution even for Android 4.0 and 4.1. It works, but switching takes too long, because it requires a reboot and this switching is not integrated into the system. So I do not want it.
Do you know of any other solution or anything what I could try?
I googled again, found this - http://forum.xda-developers.com/showpost.php?p=34362377&postcount=8
But setting fw.max_users=8 in /system/build.prop haven't helped either.
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
H0w4rd said:
Unfortunatelly they answer me, that MK812 mini pc does not support multiple user function. So I have to use SwitchMe Multiple Accounts
Click to expand...
Click to collapse
try
"setprop fw.max_users 8"
Lower-Case setprop without the quotes.
Edit: I see, can you and are you willing to get the source, modify it, build it and flash it? I'm going to have to enable it for my phone so when I figure out what needs modifying I'll let u know.
I have a question, and if possible the answer should be as wide as possible to work on as many systems as possible. While I am not fully conversed in Android functions, syntax, and interfaces, I have been programing various computers since the mid 80's and have applied rooting/jailbreaking methods to several systems (if it functions like a computer, I want my Admin rights, much thanks to each and all authors of these). I know that someone somewhere out there may have asked and already found a solution to this very annoying problem.
Thanks to the Google's decision to increase security in the Android OSes (KitKat and higher) by removing write access to the SD Card (as I call it a very 'bonehead' and brute force decision), most of the older apps do not work properly anymore with the user added SD Cards and most are not being updated with some form of support (create a folder on SD Card). The solution for most persons is to root the system then either run an app that corrects the problem or install a new LRAM image (Lockable RAM: 'unlock' the RAM and overwrite its data with a new image then re-lock it. I don't like the term 'ROM' for this as it has been incorrectly used since the late 80's). I have found at least 2 file managers that say they have a (in-app) solution, but these solutions don't extend to all of your other apps (ie "Root Explorer" or "B1" solution doesn't help your File server/uTorrent/Photo Gallery app).
But what of the owners that for one reason or another can't root their system (unable to root, not authorized or allowed to root, etc.) but want/need to have write access to the user added cards (mainly because their internal storage is just too small)? Example, in my case my personal phone has several apps that require it to remain in an unrooted state for certain work related programs (security issues).
So here is my question:
Is it possible, on an unrooted and stock LRAM android device, using ADB to PULL the "platform.xml" file, add the line '<group gid=”media_rw” />' to it, then PUSH the edited file back to the android device?
I realize this may require entering (various name versions) Recovery or Update mode which is specific to each device (I think Samsung calls their ODIN). But I think the ADB commands and computer side instructions should be the same. So if it is possible, please list all ADB instructions (I know the text editor used will depend on the PC/MAC OS used).
Thank you one and all that give any advice or assistance.
Well it looks like there have been a lot of lookers since I first posted this but still no reply by anyone that knows Android OS inside and out. Most of you are probably thinking "tl:dr" to all of it.
I know there has to be a way to update/upgrade system files that doesn't require rooting or a way to find the manufacturer's or cellular vender's access path or password.
Hello,
I have an external USB camera(endoscope) that I'd like to use with my Huawei Mediapad tablet. I've been googling and its possible, there is no hardware restrictions since USB OTG is working(tested with thumb drive). I'm not sure about UVC drivers but there are a few other problems that might be causing the problem.
Reading a blog i discovered that since KitKat(this tablet has 4.4.4) the SELinux policy is set to "enforced" and therefore apps can't access external USB camera feeds like they used to straight out of the box. There are 3 workarounds which all require rooting.
1. Start the app with superuser rights
2. Configure SELinux to allow USB cam feed
3. Custrom rom
Blog link: htt ps://droidperception.wordpress. com/2013/12/01/webcams-on-android-4-4/
So it all comes down to this - I need to have this device rooted but I haven't even found a single thread about this model in this forum.
NB! I don't have room for experimentation(read: bricking the device) since the device is not mine.
Thanks for you attention,
Pask
You ask quite a while ago and I see no answer. So, just in case, I did root mine in a way I not necessary would recommend, but ... KingRoot latest version can do a trick, but it definitely not kind of software I would keep on my tablet. So after that I install SuperSU, Link2SD ( using it to get rid of applications I do not like) and RootExplorer + Terminal. Give all of them root access using KingRoot manager and with help of Super-Sume App (will cost you some money) start a process of getting read of all related to KingRoot and Co. It is more tricky that one may think but by freezing and killing some processes in "write" time I manage to install SupeSU binaries and remove left overs. I still have problems to get su requests, so just copy config files from my phone with access rights already given to specific applications and deny access to anything else. So far do not see anything I cannot identify running, so my hope KingRoot is completly gone.
So far I did not fine any other tools/methods to get root
Just 2 days ago Entrust published an update to their app containing a new native root checker, looking quickly at it, it seems like librootcheck-lib.so was just added in this new version, but isn't present in the previous 3.5.4.14 release.
APKPure still has the old version and downgrading seems to do the job for now.
https://apkpure.com/entrust-identityguard-mobile/com.entrust.identityGuard.mobile/versions
You can also of course use the identityguard tools to generate your token directly.
https://github.com/ss23/entrust-identityguard-tools
The following functions appear to exist for root checking in it, I haven't investigated which if any is failing yet, but if someone wants to speculate, feel free:
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isAccessedSuperuserApk
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isDetectedDevKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isDetectedTestKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundBusyboxBinary
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundDangerousProps
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundHooks
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundResetprop
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundSuBinary
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundWrongPathPermission
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundXposed
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isNotFoundReleaseKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isPermissiveSelinux
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isSuExists
Just wanted to let everyone know that the downgrade should work if you do experience this issue this morning and see if anyone has ideas for how to bypass this if needed in future versions of the app.
EDIT:
I determined the reason mine was failing, a busybox installer must have created /data/local/busybox, if you have that directory existing, you may need to remove it to get IdentityGuard to start.
ultramancool said:
Just 2 days ago Entrust published an update to their app containing a new native root checker, looking quickly at it, it seems like librootcheck-lib.so was just added in this new version, but isn't present in the previous 3.5.4.14 release.
APKPure still has the old version and downgrading seems to do the job for now.
https://apkpure.com/entrust-identityguard-mobile/com.entrust.identityGuard.mobile/versions
You can also of course use the identityguard tools to generate your token directly.
https://github.com/ss23/entrust-identityguard-tools
The following functions appear to exist for root checking in it, I haven't investigated which if any is failing yet, but if someone wants to speculate, feel free:
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isAccessedSuperuserApk
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isDetectedDevKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isDetectedTestKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundBusyboxBinary
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundDangerousProps
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundHooks
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundResetprop
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundSuBinary
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundWrongPathPermission
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isFoundXposed
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isNotFoundReleaseKeys
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isPermissiveSelinux
Java_com_entrust_identityGuard_mobile_sdk_rootcheck_JniNativeRootCheck_isSuExists
Just wanted to let everyone know that the downgrade should work if you do experience this issue this morning and see if anyone has ideas for how to bypass this if needed in future versions of the app.
EDIT:
I determined the reason mine was failing, a busybox installer must have created /data/local/busybox, if you have that directory existing, you may need to remove it to get IdentityGuard to start.
Click to expand...
Click to collapse
Well just got the same problem, i dont have busybox and it still dont want to load, the old version works though, so theres that... thanks for the sugestion.
Edit: unfortunately playstore keeps updating the app... Tried the detach module, but it does not work with magical canary builds, Don't know what else to try.
I came across this issue 3 or 4 years ago. I searched internet and there were some discussions saying that there is a file (or profile) in Android that contains info on the type of device it is running on. The reason for the Apps not running was because the software (OS or Apps) detected that it is not on the right device. One circumvention is to modify the file (or profile) on the Android box to fool the software that it is running on the right device (e.g. a phone). This kind of modification require root access. At that time, I did not have any spare device to risk with. I did not write down the details. Now I have a spare android box and like to revisit the problem. But I am not able to find the info anymore. I hope my memory is correct. I am not sure if this is still true with the current Android version. If anyone has seen this before, can you kindly point me to the right direction.
There are some protections in app like RootBeer or PiracyChecker that check few things that crash certain apps on rooted phones and android emulators.
Check examples: is there superuser.apk, is there /system/bin access, is there SU binary or magisksu, is there Android_x86/Android_x64/MoboGenie/Droid4X in signature in build.prop, or hacking apps like AC Market, Black market, Lucky patcher etc.