Banking App - Barclays Variant (Absa Bank)

Banking App - Barclays Variant (Absa Bank) - Magisk

Background - Barclays owned banks in Africa (for ease of simplicity let's call it Absa) they have since sold. There is still probably some lingering software between them.
Problem - The Absa app detects Magisk everytime for probably last the 3 months
So Magisk is running on my OPO3T using Validus 8.1 - 7 Jul 18 Build - I realise I think the keys are 8.0.0 when running props?
So I have attached 3 files:
1 - AbsaLogcat.txt
2 - AbsaLogcatNoMagisk.txt
3 - magisk.log
Code:
[b]File 1[/b]
Boot phone
Run App
Get logcat from adb
Code:
[b]File 2[/b]
Boot phone
Uninstall Magisk Manager
Run App
get logcat from adb
Code:
[b]File 3[/b]
Boot phone
Uninstall Magisk Manager
Run App
get logcat from adb
get /cache/magisk.log
I am intrigued that without Magisk there's a whole lot more information. Is the stuff in ActivityManager the ones I should be looking out for?
From File 1
Code:
$ cat AbsaLogcat.txt | grep ActivityManager
08-02 22:16:14.349 2534 2585 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity (has extras)} from uid 10020
08-02 22:16:14.391 2534 4437 I ActivityManager: Start proc 6469:com.barclays.absa.banking/u0a246 for activity com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity
08-02 22:16:18.863 2534 4435 I ActivityManager: START u0 {cmp=com.barclays.absa.banking/.phone.login.RootTamperActivity} from uid 10246
08-02 22:16:19.367 2534 2618 W ActivityManager: Activity pause timeout for ActivityRecord{b2bee4e u0 com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity t13938 f}
08-02 22:16:24.862 2534 3370 I ActivityManager: Killing 6469:com.barclays.absa.banking/u0a246 (adj 900): remove task
[/code]
From File 2
Code:
$ cat AbsaLogcatNoMagisk.txt | grep ActivityManager
08-02 22:30:07.725 2458 7396 I ActivityManager: Start proc 7487:com.barclays.absa.banking/u0a246 for broadcast com.barclays.absa.banking/com.imimobile.connect.core.internal.services.BootCompleteReceiver
08-02 22:30:15.125 2458 6584 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.barclays.absa.banking/.v4.presentation.launch.SplashScreen2faActivity (has extras)} from uid 10020
08-02 22:30:23.519 2458 7027 I ActivityManager: START u0 {cmp=com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity (has extras)} from uid 10246
08-02 22:30:32.684 2458 7599 I ActivityManager: START u0 {flg=0x4000000 cmp=com.barclays.absa.banking/.rebrand.home.HomeContainerActivity (has extras)} from uid 10246
08-02 22:30:40.490 2458 3337 I ActivityManager: START u0 {flg=0x14008000 cmp=com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity} from uid 10246
08-02 22:30:40.505 2458 2475 W ActivityManager: Duplicate finish request for ActivityRecord{25f32ea u0 com.barclays.absa.banking/.rebrand.home.HomeContainerActivity t13940 f}
08-02 22:30:41.765 2458 2634 I ActivityManager: Displayed com.barclays.absa.banking/.v4.presentation.passcode.passcode_login.SimplifiedLoginActivity: +1s247ms
08-02 22:30:48.976 2458 8419 I ActivityManager: Killing 7487:com.barclays.absa.banking/u0a246 (adj 900): remove task

I'm replying to you here instead of in the MagiskHide Props Config thread...
Your issue has nothing to do with build.prop. The app is simply detecting Magisk.
Not sure which specific app is causing you issues, but I tested the Barclays app from the Play store and can start it just fine with Magisk active, after setting everything up properly.
The trick is that you also have to add the phone app (com.android.dialer) to the Hide list. Notice how the app asks for phone permission? With both the app and the phone on the Hide list it no longer detects root, during my test.
Also, if the app has detected root once, you have to clear data for the app since it seems to store your device state.
Edit: Never mind... I found the app and it's much simpler. It's looking for "Magisk" in the app name. That kind of detection will be fixed in a future Magisk release. Meanwhile you can uninstall the Manager whenever you need to use the banking app, or try this, some have reported success with changing the app name with that:
https://play.google.com/store/apps/details?id=com.gmail.heagoo.apkeditor

yeah i've been uninstalling magisk when i need to use it.
will try that app as well in the meanwhile

Used this solution from another thread (edited it)
Pietolsen said:
You can change the app name with the app called APK Editor on the playstore. Works for me, just select Magisk Manager and select common edit, change the name (to Magic or whatever), also tick the "Rename package name in DEX file(s)" box and install the new APK you generate (you will need to uninstall first if it is still installed). I just changed the name to Magic and it works just fine for me now.
Click to expand...
Click to collapse

Related

How to launch an application from Terminal?

Hi guys,
I want to know how to launch an application installed in my Android from command line?
In windows, for example, exists "start" command:
Code:
C:\>start notepad.exe
It Starts notepad application.
Exists something like that in Android?
Thanks in advance.

tolemac said:
Hi guys,
I want to know how to launch an application installed in my Android from command line?
In windows, for example, exists "start" command:
Code:
C:\>start notepad.exe
It Starts notepad application.
Exists something like that in Android?
Thanks in advance.
Click to expand...
Click to collapse
there is a way of doing it, but its a lot more complicated lol .. lemme look for a link
actually i cant find it right now lol but i know it has to do with the "am" command and intents
yup just tried the am command and it tells you how to use it ... hope i pointed you in the right direction

Yeah!!
Thanks xidominicanoix, searching "android am start" I have found this:
http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
The sintax (resumed for this case) is:
Code:
am start -a android.intent.action.MAIN -n package/class_fullname
Example:
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
Now, I´m trying to launch this as root with from Java with:
Code:
process = Runtime.getRuntime().exec("su");
os = new DataOutputStream(process.getOutputStream());
os.writeBytes("am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass"+"\n");
os.writeBytes("exit\n");
os.flush();
The application start but don´t have root permissions :/
Any idea?

I suppose that "am start" command send some signal to other process to launch this application and the other process don´t have root permissions.
Other way?
Thank you so much.

tolemac said:
Yeah!!
Thanks xidominicanoix, searching "android am start" I have found this:
http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
The sintax (resumed for this case) is:
Code:
am start -a android.intent.action.MAIN -n package/class_fullname
Example:
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
Now, I´m trying to launch this as root with from Java with:
Code:
process = Runtime.getRuntime().exec("su");
os = new DataOutputStream(process.getOutputStream());
os.writeBytes("am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass"+"\n");
os.writeBytes("exit\n");
os.flush();
The application start but don´t have root permissions :/
Any idea?
Click to expand...
Click to collapse
would
Code:
os.writeBytes("su");
right after you initialize os work?

humn??
This code:
Code:
process = Runtime.getRuntime().exec("su");
Do it.
Thanks,

When using "su" in linux, when one attempts to execute a command as root, the proper invocation is as follows:
Code:
su -c "[[b]COMMAND GOES HERE[/b]]"
Might help you.
In this case; you'd want:
Code:
os.writeBytes("su -c 'am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass'"+"\n");
That ought to do it, IF I understand this correctly. IANAP.

Thanks IConrad01, I will try it as soon as possible.

Thanks other time IConrad01, I have tried your command.
1) I have created an Android application called TestBackup that try to write a simple file on startup in this path: /system/bin/hello.txt
2) I have ran the application in my device and I get a normal exception:
Code:
(new File("/system/bin/hello.txt")).createNewFile();
java.io.IOException: Parent directory of file is not writable: /system/bin/hello.txt
3) I have opened an "adb shell" shell and I have ran this commands:
Code:
# busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
# su -c 'am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test'
su -c 'am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test'
Starting: Intent { act=android.intent.action.MAIN cmp=org.jros.TestBackup/.Test }
# busybox mount -o ro,remount /system
busybox mount -o ro,remount /system
The application started but don´t have root permissions (I think), this is the LogCat from "am start":
Code:
11-05 13:21:32.082: DEBUG/su(1175): 0:0 /system/bin/sh executing 0:0 am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test
11-05 13:21:32.462: DEBUG/AndroidRuntime(1176): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
11-05 13:21:32.462: DEBUG/AndroidRuntime(1176): CheckJNI is OFF
11-05 13:21:32.642: DEBUG/AndroidRuntime(1176): --- registering native functions ---
11-05 13:21:32.672: INFO/jdwp(1176): received file descriptor 30 from ADB
11-05 13:21:32.842: INFO/BluetoothOppService.cpp(1176): register_android_server_BluetoothOppService
11-05 13:21:32.872: DEBUG/ddm-heap(1176): Got feature list request
11-05 13:21:33.202: INFO/ActivityManager(129): Starting activity: Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=org.jros.TestBackup/.Test }
11-05 13:21:33.232: DEBUG/AndroidRuntime(1176): Shutting down VM
11-05 13:21:33.242: DEBUG/dalvikvm(1176): DestroyJavaVM waiting for non-daemon threads to exit
11-05 13:21:33.242: DEBUG/dalvikvm(1176): DestroyJavaVM shutting VM down
11-05 13:21:33.242: DEBUG/dalvikvm(1176): HeapWorker thread shutting down
11-05 13:21:33.242: DEBUG/dalvikvm(1176): HeapWorker thread has shut down
11-05 13:21:33.242: DEBUG/jdwp(1176): JDWP shutting down net...
11-05 13:21:33.242: DEBUG/jdwp(1176): +++ peer disconnected
11-05 13:21:33.242: INFO/dalvikvm(1176): Debugger has detached; object registry had 1 entries
11-05 13:21:33.262: DEBUG/dalvikvm(1176): VM cleaning up
11-05 13:21:33.272: ERROR/AndroidRuntime(1176): ERROR: thread attach failed
11-05 13:21:33.302: INFO/ActivityManager(129): Process com.android.vending (pid 1046) has died.
11-05 13:21:33.332: ERROR/Error Test SU(1072): Parent directory of file is not writable: /system/bin/hola.txt
11-05 13:21:33.332: WARN/System.err(1072): java.io.IOException: Parent directory of file is not writable: /system/bin/hola.txt
11-05 13:21:33.342: WARN/System.err(1072): at java.io.File.createNewFile(File.java:1208)
11-05 13:21:33.342: WARN/System.err(1072): at org.jros.TestBackup.Test.TestSU(Test.java:32)
11-05 13:21:33.342: WARN/System.err(1072): at org.jros.TestBackup.Test.onCreate(Test.java:24)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2417)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.access$2100(ActivityThread.java:116)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
11-05 13:21:33.362: WARN/System.err(1072): at android.os.Handler.dispatchMessage(Handler.java:99)
11-05 13:21:33.362: WARN/System.err(1072): at android.os.Looper.loop(Looper.java:123)
11-05 13:21:33.362: WARN/System.err(1072): at android.app.ActivityThread.main(ActivityThread.java:4203)
11-05 13:21:33.362: WARN/System.err(1072): at java.lang.reflect.Method.invokeNative(Native Method)
11-05 13:21:33.362: WARN/System.err(1072): at java.lang.reflect.Method.invoke(Method.java:521)
11-05 13:21:33.362: WARN/System.err(1072): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
11-05 13:21:33.372: WARN/System.err(1072): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
11-05 13:21:33.372: WARN/System.err(1072): at dalvik.system.NativeStart.main(Native Method)
11-05 13:21:33.372: DEBUG/dalvikvm(1176): LinearAlloc 0x0 used 685236 of 4194304 (16%)
11-05 13:21:33.442: INFO/ActivityManager(129): Displayed activity org.jros.TestBackup/.Test: 218 ms (total 218 ms)
Perhaps is impossible to start an application with root permissions.
I don´t now.
And you?
what are you think about?
Thanks in advance.

What you are asking for makes no sense.
The user who starts an android application has nothing to do with the user who the application RUNS AS.
Whether you use "am start" or click on the button, the SAME THING HAPPENS -- the user who runs the application is the user assigned to THAT application by the PACKAGE MANAGER.
am start does NOT start the application. It sends an INTENT that the application is *to be* started.
If you want your application to have root access, you need to gain root access *from within* that application, and having root access is restricted to executing SHELL COMMANDS.

Thank you very much lbcoder.
I suppose this.
Ok, while I have been trying it I have learned other things, doesn´t loss time
Thank you so much.

Is there any way to work out what package/class_fullname is for specific apps? I want to autostart my IM program at boot (Nimbuzz) - how would I go about determining a command line for it?

I guess everyone forgot to mention that this is in the wrong section?
-.-

Start Android app from terminal
So when I start
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
e.g.
Code:
am start -a android.intent.action.MAIN -n com.google.browser/com.google/browser
will start the standard browser ? As I only have a root terminal (via ssh using SSHDroid) does this mean that the apps are started as root ?
I prefer them starting normally except for root specific apps like vnc server.
When I try this I get errors.
Code:
pocketpenguin:~ #am start -n com.google.android.contacts/.ContactsActivity
Starting: Intent { cmp=com.google.android.contacts/.ContactsActivity }
Error type 3
Error: Activity class {com.google.android.contacts/com.google.android.contacts.ContactsActivity} does not exist.
pocketpenguin:~ #
Does somebody know this ?

mermaidkiller said:
Does somebody know this ?
Click to expand...
Click to collapse
Um:
Code:
# am start -a android.intent.category.DEFAULT -n com.android.contacts/com.android.contacts.DialtactsContactsEntryActivity
For your contact list (in the aosp gingerbread contacts apk anyway), read the AndroidManifest for othe links, or cortect names in other versions of the apk.
Of course to open a page in your default browser try:
Code:
# am start -a android.intent.action.VIEW http://www.google.com/

Thanks anywY, but how can I start any app from the command line ?

Is there any way at all to run Java code as root, maybe by exec'ing the dalvikvm itself?
==EDIT==
Nevermind, I got it.

I can understand the command but may I know how to find out the exact folder or com description for the app that I intend to start at command-line ? for example, let's say I wish to start the FIREFOX browser, can someone show me how to find out the com description to use in the command line and give me an example of the command line. Thank you in advance.

cd /data/app
ls
cd /system/app
ls
Etc etc
Sent from my Nexus 4 using XDA Premium 4 mobile app

Launch an Application from Terminal
You dont need to know the location of the app on the phone. However you need to know the package name (application name) and various activities in the app. Basically if you intend to just launch the app then you need yo know the main activity that triggers the application to start. So suppose that your package name is, com.mozilla.firefox and the start activity is say MainActivity. Then you can launch the app from terminal with su privilage with following command,
Code:
am start -n com.mozilla.firefox/.MainActivity
Thats it.
Coming to knowing the package name for your application, use
Code:
pm list packages
And if you want know the location of the apk, use
Code:
pk list packages -f
And if you intend to know names of the third party apps installed only use
Code:
pm list packages -3 -f
Now to know various activities in an app, see the AndroidManifest.xml. You will see names of activities. Most probably the first activity is the start activity ie., MainActivity.
To see the contents of androidManifest.xml you need to extract it from apk file. Online tools are available to do so.
Hope this helps.
sent from my huewei honor 4x

No media found in storage in any jelly bean rom.

I've searched a lot on the Internet regarding this issue, but could not find any fixed solution to it.
I've tried installing multiple jelly bean ROMs including Androxide and CNA and even stock ROM.
Any music app (except power amp) including jetaudio, default, playerpro, win amp can not see any of my music stored in /sdcard/media/Songs. The default gallery app also can not see any images including ones in /sdcard/DCIM/Camera.
I did a cut paste on PC and then again adb pushed all files to /sdcard/DCIM/Camera and /sdcard/Music and then I could see everything again. Again when I installed new ROM (CNA 3.5) and everything is gone again. I tried adb pushing again but it does not work. I tried clearing cache partition. I tried clearing data for music app, gallery, media storage. I have tried installing and running media scan app from play store. I can not wipe data repeatedly.
I am so frustrated because of the issue. I can see all music files are there on sdcard using file manager. I also verified that there are no .nomedia files anywhere. I see that sdcard is mounted on /mnt/sdcard0 instead of old /mnt/sdcard if that has anything to do with it.
Please help if anyone else has faced this issue and know concrete solution about it. I've searched a lot but could not find solution. Please help.

kaustubhg123 said:
I've searched a lot on the Internet regarding this issue, but could not find any fixed solution to it.
I've tried installing multiple jelly bean ROMs including Androxide and CNA and even stock ROM.
Any music app (except power amp) including jetaudio, default, playerpro, win amp can not see any of my music stored in /sdcard/media/Songs. The default gallery app also can not see any images including ones in /sdcard/DCIM/Camera.
I did a cut paste on PC and then again adb pushed all files to /sdcard/DCIM/Camera and /sdcard/Music and then I could see everything again. Again when I installed new ROM (CNA 3.5) and everything is gone again. I tried adb pushing again but it does not work. I tried clearing cache partition. I tried clearing data for music app, gallery, media storage. I have tried installing and running media scan app from play store. I can not wipe data repeatedly.
I am so frustrated because of the issue. I can see all music files are there on sdcard using file manager. I also verified that there are no .nomedia files anywhere. I see that sdcard is mounted on /mnt/sdcard0 instead of old /mnt/sdcard if that has anything to do with it.
Please help if anyone else has faced this issue and know concrete solution about it. I've searched a lot but could not find solution. Please help.
Click to expand...
Click to collapse
Update ROM manager. Then delete the .nomedia files you can find either at the root of your sdcard, in the DCIM, Camera, media or Songs folder.

I have already removed all .nomedia files. What can I do by updating ROM Manager?

What on earth made you post this in the development section?
But while I am here I will try to help, have you tried formatting your sdcard? When you copied the files back to your phone did you do it after installing the new ROM?
Sent from my Nexus S

XxSilent22xX said:
What on earth made you post this in the development section?
But while I am here I will try to help, have you tried formatting your sdcard? When you copied the files back to your phone did you do it after installing the new ROM?
Sent from my Nexus S
Click to expand...
Click to collapse
I am sorry to post it in wrong section. I did not know where to post it.
Yes I did erase USB Storage from settings and then again wipe the ROM and then copy music again. no luck though.
However, I installed app called SDrescan and then turned on logcat and here are the results, if that helps... I think the media scanner is crashing:
09-10 22:39:48.599 W/ActivityManager(290): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 35012ms
09-10 22:40:40.039 I/ActivityManager(290): Start proc android.process.media for service com.android.providers.media/.MediaScannerService: pid=1545 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-10 22:40:48.343 W/ActivityManager(290): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 140048ms
09-10 22:43:26.824 I/ActivityManager(290): Start proc android.process.media for service com.android.providers.media/.MediaScannerService: pid=1661 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-10 22:43:43.160 W/ActivityManager(290): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 560192ms
09-11 00:54:34.254 I/ActivityManager(2488): Start proc android.process.media for broadcast com.android.providers.media/.MediaScannerReceiver: pid=6278 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 00:54:34.547 D/MediaScannerReceiver(6278): action: android.intent.action.MEDIA_MOUNTED path: /storage/sdcard0
09-11 00:54:34.902 W/MediaScanner(6278): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 00:54:48.808 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 28526ms
09-11 00:55:17.414 I/ActivityManager(2488): Start proc android.process.media for service com.android.providers.media/.MediaScannerService: pid=6417 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 00:55:19.304 W/MediaScanner(6417): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 00:55:42.004 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 114104ms
09-11 00:55:52.418 I/ActivityManager(2488): Start proc android.process.media for broadcast com.android.providers.media/.MediaScannerReceiver: pid=6456 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 00:55:52.789 D/MediaScannerReceiver(6456): action: android.intent.action.MEDIA_MOUNTED path: /storage/sdcard0
09-11 00:55:53.390 W/MediaScanner(6456): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 00:56:11.129 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 36674ms
09-11 00:56:47.886 I/ActivityManager(2488): Start proc android.process.media for service com.android.providers.media/.MediaScannerService: pid=6485 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 00:56:48.636 W/MediaScanner(6485): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 00:57:04.050 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 146696ms
09-11 00:59:31.070 W/MediaScanner(6514): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 00:59:44.785 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 586784ms
09-11 00:59:56.761 I/ActivityManager(2488): Start proc android.process.media for broadcast com.android.providers.media/.MediaScannerReceiver: pid=6609 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 00:59:57.152 D/MediaScannerReceiver(6609): action: android.intent.action.MEDIA_MOUNTED path: /storage/sdcard0
09-11 00:59:57.597 W/MediaScanner(6609): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 01:00:05.390 D/MediaScannerReceiver(6609): action: android.intent.action.MEDIA_MOUNTED path: /storage/sdcard0
09-11 01:00:10.855 W/ActivityManager(2488): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
09-11 01:00:10.855 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 27390ms
09-11 01:00:26.050 I/ActivityManager(2488): Start proc android.process.media for broadcast com.android.providers.media/.MediaScannerReceiver: pid=6635 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 01:00:26.476 D/MediaScannerReceiver(6635): action: android.intent.action.MEDIA_MOUNTED path: /storage/sdcard0
09-11 01:00:26.933 W/MediaScanner(6635): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 01:00:43.660 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 34348ms
09-11 01:01:18.058 I/ActivityManager(2488): Start proc android.process.media for service com.android.providers.media/.MediaScannerService: pid=6663 uid=10011 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
09-11 01:01:18.652 W/MediaScanner(6663): Error opening directory '/storage/sdcard0/.android_secure/', skipping: Permission denied.
09-11 01:01:32.383 W/ActivityManager(2488): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
09-11 01:01:32.383 W/ActivityManager(2488): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 137392ms

kaustubhg123 said:
I am sorry to post it in wrong section. I did not know where to post it.
Click to expand...
Click to collapse
Well, Q&A section would be great, general would also be OK. Basically anything BUT development section...

Try to update your recovery then format your sdcard.

The problem is in the media scanner: it stops when it finds a non standard picture or mp3.
Try to format your sd and copy just one picture and one mp3 to see if it works.
But for this problem I have returned to ICS
sent from my C=64 using Tapatalk64

yerazero said:
The problem is in the media scanner: it stops when it finds a non standard picture or mp3.
Try to format your sd and copy just one picture and one mp3 to see if it works.
But for this problem I have returned to ICS
sent from my C=64 using Tapatalk64
Click to expand...
Click to collapse
I am also thinking to switch to CM9, but this isn't the solution, is it? I want JB and even stock Google ROM is problematic. However, I will now try to remove everything wipe my phone clean, everything and then try installing JB again... Sad.

kaustubhg123 said:
I am also thinking to switch to CM9, but this isn't the solution, is it? I want JB and even stock Google ROM is problematic. However, I will now try to remove everything wipe my phone clean, everything and then try installing JB again... Sad.
Click to expand...
Click to collapse
I totally agree with you, this is not a solution but at the moment there are excellent ICS ROMS so I can still live without JB
sent from my C=64 using Tapatalk64

I also experienced this problem on my Nexus S, yesterday I just flashed it with the newest release of XenonHD and the problems still persist. Only PowerAmp can play the mp3 files. So, nobody including Google themself cannot solve this problem? I just experienced this when JB came out. Gingerbread and ICS never had this problems.

Posting this to Q & A forums. Sorry to disturb you developers.

Walkman app

Hello, I am having serious issue with the walkman app (both stock and the updated version). It frequently crashes as soon as I press the icon or if I turn on the screen with the widget. After a random number of attempts (3 - ~20) it will eventrually open. I have tried many things like removing widget, clearing cache & data in app & media storage and removing all my songs. I even unmounted my 64G sd (just in case). I am having a gps program with weird .wav filenames (e.g !sound.wav) but I have added a .nomedia to avoid indexing.
I have even tried to change the max processes limit in developer menu as suggested in an older thread for an older device.
All suggestions welcome (exept factory reset please).

I would just flash or replace a new firmware with flashtool.

After lots of debugging (voodoo, praying etc) it appears that there was a conflict with the svox tts packages. I personally had installed the greek language.
So far, the crashes are gone.
UPDATE: unfortunatelly this was not the issue, crashes are back. Help please?

Here are some logcat logs.
I am using 64G sdxc minisd. Crashes happen even with no songs at all.
I/ActivityManager( 896): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.sonyericsson.music/.MusicActivity} from pid 1619
I/ActivityManager( 896): Start proc com.sonyericsson.music for activity com.sonyericsson.music/.MusicActivity: pid=16731 uid=10062 gids={50062, 1015, 1023, 3002, 3003, 1028}
E/AndroidRuntime(16731): FATAL EXCEPTION: Thread-874
E/AndroidRuntime(16731): java.lang.RuntimeException: Package manager has died
E/AndroidRuntime(16731): at android.app.ApplicationPackageManager.queryContentProviders(ApplicationPackageManager.java:590)
E/AndroidRuntime(16731): at com.sonyericsson.music.cl.e(PluginManager.java:305)
E/AndroidRuntime(16731): at com.sonyericsson.music.cl.b(PluginManager.java:184)
E/AndroidRuntime(16731): at com.sonyericsson.music.cl.<init>(PluginManager.java:81)
E/AndroidRuntime(16731): at com.sonyericsson.music.cl.<init>(PluginManager.java:46)
E/AndroidRuntime(16731): at com.sonyericsson.music.cm.run(PluginManager.java:104)
E/AndroidRuntime(16731): at java.lang.Thread.run(Thread.java:856)
E/AndroidRuntime(16731): Caused by: android.os.TransactionTooLargeException
E/AndroidRuntime(16731): at android.os.BinderProxy.transact(Native Method)
E/AndroidRuntime(16731): at android.content.pm.IPackageManager$Stub$Proxy.queryContentProviders(IPackageManager.java:2302)
E/AndroidRuntime(16731): at android.app.ApplicationPackageManager.queryContentProviders(ApplicationPackageManager.java:588)
E/AndroidRuntime(16731): ... 6 more
W/ActivityManager( 896): Force finishing activity com.sonyericsson.music/.MusicActivity
I/ActivityManager( 896): Start proc com.sonyericsson.android.bootinfo:remote for service com.sonyericsson.android.bootinfo/.MiscTaService: pid=16767 uid=1000 gids={41000, 3003, 1015, 1028, 3002, 3001, 3$
I/ActivityManager( 896): Start proc com.sonymobile.social.services for service com.sonyericsson.facebook.proxylogin/.AccountAuthenticatorService: pid=16775 uid=10050 gids={50050, 3003, 1028}
I/ActivityManager( 896): Start proc com.sonymobile.playanywhere for broadcast com.sonymobile.playanywhere/.PlayAnywhereReceiver: pid=16800 uid=1000 gids={41000, 3003, 1015, 1028, 3002, 3001, 3007}

An apk call a function not located in it's source code

I am doing some reverse engineering on an gapephone app from the play store. When I run it in debug mode I get those lines from logcat :
Code:
02-11 19:56:08.857: I/ActivityManager(773): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.ankama.dofustouch/.MainActivity (has extras)} from uid 10039 on display 0
02-11 19:56:09.057: I/Xposed(12567): Inspeckage_Error com.android.okhttp.OkHttpClient#open(java.net.URI)#exact
02-11 19:56:09.113: I/Xposed(12567): Inspeckage_Error java.lang.ClassNotFoundException: org.apache.http.conn.ssl.HttpsURLConnection
02-11 19:56:09.114: I/Xposed(12567): Inspeckage_Error java.lang.ClassNotFoundException: okhttp3.CertificatePinner
I'm confused because when I look to the source code I can't find any lines invoking okhttp. I wonder if it's possible to come from it's '.so' libraries.
all suggestions are welcome

yes you can invoke any class from native because class or method name is needed to be add in String parameter

Raiffeisen banking app

Apart from magisk I have also installed xposed framework. All banking apps are running but, the Raiffeisen app. I'm actually even not sure if it has to do with root. The app crashes immediately after it gets started.
Some suggestions?

I tried right now with Magisk Manager 20.4 (20400) and Raiffeisen app (Romania) and the Raiffeisen app works if you Hide Magisk Manager ( în Magisk manager Settings).
That means Raiffeisen Apps are searching for Magisk Manager. I think.
LE: Smart Mobile works. RaiPay doesn't Work.

xposed will always allow root to be detected.

Arak0n said:
xposed will always allow root to be detected.
Click to expand...
Click to collapse
Yes, but I installed many banking app which does not accept root. They all work as long I keep them in the magisk hide list.

XtraWater said:
Yes, but I installed many banking app which does not accept root. They all work as long I keep them in the magisk hide list.
Click to expand...
Click to collapse
That simply means that those other apps do not look for Xposed, while the app in question possibly does. Might also look for USB debuggin and/or Developer options being enabled, etc, etc...
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

XtraWater said:
All banking apps are running
Click to expand...
Click to collapse
& btw., not the best idea to use important data on a custom ROM.

I have the same problem with this raiffeisen app. Did you find any solutino for that?

Didgeridoohan said:
That simply means that those other apps do not look for Xposed, while the app in question possibly does. Might also look for USB debuggin and/or Developer options being enabled, etc, etc...
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
I can confirm the Raiffeisen banking app probably fails because of something else. There is no Xposed on my system, both safetyNet checks pass, Magisk Manager is also hidden. I have tried to activate MagiskHide to Phone-related apks as well since the app requests call management permissions, but it didn't help. I've also chmodded /proc/net/unix to 000. I tried disabling USB debugging and developer mode altogether.
What's interesting is that I think the app looks for the native camera app on my Mi A1 which was not present initially, but then I've created a Magisk module which placed the original camera apk at the correct location which did not help either. Decompiling the source revealed that it uses Vasco's technology for authentication which is also used by com.EquitasDigipass and interestingly enough it looks like it tries to do something with its resources too.
Code:
06-27 13:44:39.848 3219 3338 I ActivityManager: Start proc 17693:com.guidance.android.apps.raiffeisen.banklet/u0a192 for activity com.guidance.android.apps.raiffeisen.banklet/.ui.InitActivity
06-27 13:44:39.860 17693 17693 E ffeisen.bankle: Not starting debugger since process cannot load the jdwp agent.
06-27 13:44:39.866 1955 2382 I Magisk : proc_monitor: [com.guidance.android.apps.raiffeisen.banklet] PID=[17693] UID=[10192]
06-27 13:44:39.905 17693 17693 I ffeisen.bankle: The ClassLoaderContext is a special shared library.
06-27 13:44:40.305 17693 17693 D FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
06-27 13:44:40.306 17693 17693 D FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
06-27 13:44:40.306 17693 17693 I FirebaseInitProvider: FirebaseApp initialization successful
06-27 13:44:40.373 17693 17717 I FA : App measurement is starting up, version: 15300
06-27 13:44:40.373 17693 17717 I FA : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
06-27 13:44:40.374 17693 17717 I FA : To enable faster debug mode event logging run:
06-27 13:44:40.374 17693 17717 I FA : adb shell setprop debug.firebase.analytics.app com.guidance.android.apps.raiffeisen.banklet
06-27 13:44:40.376 17693 17693 W : type=1400 audit(0.0:1832): avc: denied { read } for name="/" dev="rootfs" ino=1 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0
06-27 13:44:40.513 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.alibaba.aliexpresshd-YKwyZRC-LJzYtvxBjpz3wQ==/base.apk' is compressed.
06-27 13:44:40.524 17693 17693 D OpenGLRenderer: Skia GL Pipeline
06-27 13:44:40.581 17693 17727 I Adreno : QUALCOMM build : 2df12b3, I07da2d9908
06-27 13:44:40.581 17693 17727 I Adreno : Build Date : 10/04/18
06-27 13:44:40.581 17693 17727 I Adreno : OpenGL ES Shader Compiler Version: EV031.25.03.01
06-27 13:44:40.581 17693 17727 I Adreno : Local Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Remote Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Remote Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Reconstruct Branch :
06-27 13:44:40.581 17693 17727 I Adreno : Build Config : S L 6.0.7 AArch32
06-27 13:44:40.581 17693 17727 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8953.so from current namespace instead of sphal namespace.
06-27 13:44:40.602 17693 17727 I Adreno : PFP: 0x005ff087, ME: 0x005ff063
06-27 13:44:40.608 17693 17727 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
06-27 13:44:40.608 17693 17727 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
06-27 13:44:40.610 17693 17727 I OpenGLRenderer: Initialized EGL, version 1.4
06-27 13:44:40.610 17693 17727 D OpenGLRenderer: Swap behavior 2
06-27 13:44:40.628 17693 17727 D vndksupport: Loading /vendor/lib/hw/[email protected] from current namespace instead of sphal namespace.
06-27 13:44:40.628 17693 17727 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8953.so from current namespace instead of sphal namespace.
06-27 13:44:40.792 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.matteljv.uno-lwQ-HHADZe0GUWmTYstAvw==/base.apk' is compressed.
06-27 13:44:40.833 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.instagram.android-KGDMA_EyAMkGiZ0sDc7ZTA==/base.apk' is compressed.
06-27 13:44:41.191 17693 17722 W ziparchive: Unable to open '/system/priv-app/MiuiCamera/MiuiCamera.apk': No such file or directory
06-27 13:44:41.191 17693 17722 E ffeisen.bankle: Failed to open APK '/system/priv-app/MiuiCamera/MiuiCamera.apk' I/O error
06-27 13:44:41.192 17693 17722 E ResourcesManager: failed to add asset path /system/priv-app/MiuiCamera/MiuiCamera.apk
06-27 13:44:41.192 17693 17722 W PackageManager: Failure retrieving resources for com.android.camera
06-27 13:44:41.408 17693 17722 W ffeisen.bankle: resources.arsc in APK '/data/app/com.EquitasDigipass-hveat1DdrahqrzU15PUnjg==/base.apk' is compressed.
06-27 13:44:41.526 17693 17693 W : type=1400 audit(0.0:2011): avc: denied { read } for name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:selinuxfs:s0 tclass=file permissive=0
06-27 13:44:41.578 17693 17717 W ffeisen.bankle: Long monitor contention with owner firebase-iid-executor (17721) at long com.android.org.conscrypt.NativeCrypto.RSA_generate_key_ex(int, byte[])(NativeCrypto.java:-2) waiters=0 in com.google.firebase.iid.aa com.google.firebase.iid.z.a(java.lang.String, java.lang.String, java.lang.String) for 1.181s
06-27 13:44:41.615 17693 17717 I FA : Tag Manager is not found and thus will not be used
06-27 13:44:45.480 17693 17693 I ffeisen.bankle: System.exit called, status: 0
06-27 13:44:45.480 17693 17693 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
06-27 13:44:45.545 3219 4238 I ActivityManager: Process com.guidance.android.apps.raiffeisen.banklet (pid 17693) has died: fore TOP
06-27 13:44:45.546 3219 3340 W libprocessgroup: kill(-17693, 9) failed: No such process
06-27 13:44:45.549 2426 2426 I Zygote : Process 17693 exited cleanly (0)
06-27 13:44:45.552 3219 3340 W libprocessgroup: kill(-17693, 9) failed: No such process
06-27 13:44:45.552 3219 3340 I libprocessgroup: Successfully killed process cgroup uid 10192 pid 17693 in 6ms
06-27 13:44:45.558 3219 3393 W ActivityManager: setHasOverlayUi called on unknown pid: 17693

hi guys,
So basically I came here to find a solution for this same problem, I have installed just the Magisk app, and try to hide myRaiffeisen app the root permission and the Magisk app itself and so far for me has no succeed, but after updated to magisk 201.1 (20100) version I give it a try and after clear cache and app data of the bank app at last it going o work,
so if this problem still persist the new version should able to handle the situation
cheers

svi_system said:
hi guys,
So basically I came here to find a solution for this same problem, I have installed just the Magisk app, and try to hide myRaiffeisen app the root permission and the Magisk app itself and so far for me has no succeed, but after updated to magisk 201.1 (20100) version I give it a try and after clear cache and app data of the bank app at last it going o work,
so if this problem still persist the new version should able to handle the situation
cheers
Click to expand...
Click to collapse
It's not working to me even after updating magisk...

danny3458 said:
It's not working to me even after updating magisk...
Click to expand...
Click to collapse
So if I understand you correctly, on your phone has installed magisk with 201.1 or newer version and in the magisk manager you also marked the raiffeisen app to hide root capabilities from it?
I used this method several times on different devices with success, so I hope you able to achieve it as well

I just flashed the newest LineageOS 17.1 build onto my Pixel 3. The Austrian version of the Raiffesein App "Mein Elba" immediately forwarded me to a website where they made some security claims regarding custom roms.
Fortunately installing Magisk has solved these issues immediately. No additional work had been required.
I'm running LineageOS 17.1 (build from the 5th of march by razorloves together with magisk 20.3.
When I run the SafenetCheck in the Magisk Manager it shows "basicIntegrity: true, ctsProfile: false".
Best Regards,
Michael

::Michael:: said:
I just flashed the newest LineageOS 17.1 build onto my Pixel 3. The Austrian version of the Raiffesein App "Mein Elba" immediately forwarded me to a website where they made some security claims regarding custom roms.
Fortunately installing Magisk has solved these issues immediately. No additional work had been required.
I'm running LineageOS 17.1 (build from the 5th of march by razorloves together with magisk 20.3.
When I run the SafenetCheck in the Magisk Manager it shows "basicIntegrity: true, ctsProfile: false".
Best Regards,
Michael
Click to expand...
Click to collapse
From Mr. Magisk himself. https://mobile.twitter.com/topjohnwu/status/1237656703929180160?s=19

Do you block Google Play Wakelocks/Analytics (@MeggaMortY) ? This is crashing the Sixt app for example. I cannot block them in xXx rom.

I have never rotted my Galaxy S8 before and it still shows "rooted device detected" I also tried to disable OEM unlock and even the whole developer mode but it still shows the same message.
Sent from my SM-G950F using Tapatalk

<deleted>

badmania98 said:
I tried right now with Magisk Manager 20.4 (20400) and Raiffeisen app (Romania) and the Raiffeisen app works if you Hide Magisk Manager ( în Magisk manager Settings).
That means Raiffeisen Apps are searching for Magisk Manager. I think.
LE: Smart Mobile works. RaiPay doesn't Work.
Click to expand...
Click to collapse
life saver

Database Develop

welcome