Closed jj0e closed 3 years ago
Try using the PID of the launched app as the -g flag.
Try using the PID of the launched app as the -g flag.
There is an issue as well when trying to get the PID via frida-ps -U
. If the app is opened, this command hangs as well. As soon as I close the app, the PID's are returned but the app is closed so it doesn't show obviously.
Also, update your local frida packages to the latest. pip3 install -U frida frida-tools.
Also, update your local frida packages to the latest. pip3 install -U frida frida-tools.
This worked, thank you so much!
works for me,thank you
Description
I'm patching a newly updated APK file via the
patchapk
command. The patch is successful, however when I open the app on my physical device, and typeobjection -d -g com.joe.app explore
, it saysand hangs forever. For some reason, it is unable to connect to the Frida server.
To Reproduce Steps to reproduce the behavior:
objection patchapk appName.apk
Similar issues
476, #469, #472
Expected behavior The app should be able to load. Using older patched APK files with older version of Frida are working fine.
Environment (please complete the following information):
Additional context
This is 100% a bug with the
patchapk
process. A little while back, maybe a couple months ago, I patched this app on version3.6.1
using thepatchapk
command. I still have this patched version and am able to run it smoothly. However, today when I try to patch the exact same version of the app, I run into this bug when trying to run it. I'm not familiar at all with Frida or objection internals, but it seems like it has something to do with the version it uses during the patching process:Based on what I'm reading it seems like there were quite a few changes with Frida 15+ that may be causing it? Is there a way for us to use a downgraded version in the meantime?