now click "show run pids " error.
not "finally we are free at last " line, my platform tools folder:
Python QT ADB Qt Super version
- Thread starter Storm Shadow
- Start date
not "finally we are free at last " line, my platform tools folder:
I have never seen this error myself.
one of the most important steps of configuring the app is these steps with the path
http://www.techbliss.org/threads/adb-qt-super-version.626/#post-2095
If you open cmd
and run "adb"
if adb is called try run "adb shell ps"
if it aint working in cmd there is something wrong with the path settings.
And yes the "finally we are free at last " is from another plugin i made.
https://github.com/techbliss/Free_the_Debuggers
one of the most important steps of configuring the app is these steps with the path
http://www.techbliss.org/threads/adb-qt-super-version.626/#post-2095
If you open cmd
and run "adb"
if adb is called try run "adb shell ps"
if it aint working in cmd there is something wrong with the path settings.
And yes the "finally we are free at last " is from another plugin i made.
https://github.com/techbliss/Free_the_Debuggers
Try install newest Android Studio http://developer.android.com/sdk/installing/index.html
find latest adb.exe and dll in the ...\android-sdk-path\platform-tools\adb.exe
samoray
New member
Thank you "storm shadow" for the help,
indeed I got rid of the annoying out of date thing, but more issues are showed up:
when I try to attach to a process with a PID number (the pid list is shown perfectly) I get this message: (Bogus or irresponsive remote server)
any more tips... thank again
indeed I got rid of the annoying out of date thing, but more issues are showed up:
when I try to attach to a process with a PID number (the pid list is shown perfectly) I get this message: (Bogus or irresponsive remote server)
any more tips... thank again
Yes
Use gdbserver x86_64 one from sdk insted of the one i provided
Use gdbserver x86_64 one from sdk insted of the one i provided
I can test in the weekend , also if i remember correct you cant use gdbserver on the newest targets.
samoray
New member
I think the problem is when I try to run gdbserver /or/ android_server on the target machine... it says (I could hardly read it on the terminal, I had to pause the terminal to read what it says); it says: "not executable: magic 7F45" is there anything that you can understand from this... 'magic number'?
and one more thing, can you please try to make your script pause for a few seconds after a click (for exemple: when I click 'restart adb as root' I wish it could pause for 2 sec so I can read the output, error or success).
any help would be appreciated
and one more thing, can you please try to make your script pause for a few seconds after a click (for exemple: when I click 'restart adb as root' I wish it could pause for 2 sec so I can read the output, error or success).
any help would be appreciated
then you properlly using the wrong gdbserver, using 64 on x86 or vica verca , or it simply aint an Elf file 7F45 is the header for Elf.
Have you tried attaching to other Pids and remember to run Ida as Admin thats very important.
samoray
New member
thanks for your replies, and many thanks following this topic.
I always run IDA as admin thats obvious, and yes I tried woith other pids without success.
my system is WIN 10 x64
IDA pro 6.6 (I use idaq.exe NOT the x64 one)
Genymotion virtual android system 5.0.0 API21 / and 4.4.4 API19 none of them connects to IDA.
Will you please show me which gdbserver/android_server should I use?
EDIT: I used gdbserver (android x86) from android ndk, I finally can attach to genymotion VM with success
many Thanks to you again
I always run IDA as admin thats obvious, and yes I tried woith other pids without success.
my system is WIN 10 x64
IDA pro 6.6 (I use idaq.exe NOT the x64 one)
Genymotion virtual android system 5.0.0 API21 / and 4.4.4 API19 none of them connects to IDA.
Will you please show me which gdbserver/android_server should I use?
EDIT: I used gdbserver (android x86) from android ndk, I finally can attach to genymotion VM with success
many Thanks to you again
Last edited: