QCSuper
QCSuper copied to clipboard
P1sec
On Pixel 3, get "The connection to the adb bridge was closed, or preempted by another QCSuper instance"
When I run with a rooted Pixel 3 attached (running AOSP master), I get:
./qcsuper.py --adb --pcap-dump outputfile
43555
ioctl: Invalid argument
The connection to the adb bridge was closed, or preempted by another QCSuper instance
When I run strace /data/local/tmp/adb_bridge on the device, here's the last lines:
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xeb8d1000 prctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, 0xeb8d1000, 4096, "atexit handlers") = 0 mprotect(0xeb8d1000, 4096, PROT_READ) = 0 munmap(0xeb776000, 409600) = 0 prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) openat(AT_FDCWD, "/dev/properties/u:object_r:vendor_socket_hook_prop:s0", O_RDONLY|O_LARGEFILE|O_NOFOLLOW|O_CLOEXEC) = 3 fstat64(3, 0xffef2e40) = 0 mmap2(NULL, 131072, PROT_READ, MAP_SHARED, 3, 0) = 0xeb7ba000 close(3) = 0 prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) futex(0xeb2d6080, FUTEX_WAKE_PRIVATE, 2147483647) = 0 mprotect(0xeb8e1000, 409600, PROT_READ) = 0 mprotect(0xeb9c1000, 409600, PROT_READ) = 0 mprotect(0xeb83e000, 409600, PROT_READ) = 0 mprotect(0xeb7da000, 409600, PROT_READ) = 0 mprotect(0xeb8d1000, 4096, PROT_READ|PROT_WRITE) = 0 mprotect(0xeb8d1000, 4096, PROT_READ) = 0 mmap2(NULL, 10498048, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0xea584000 mmap2(0xea585000, 10489856, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xea585000 prctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, 0xea585000, 10489856, "scudo:secondary") = 0 openat(AT_FDCWD, "/dev/diag", O_RDWR|O_LARGEFILE) = 3 ioctl(3, _IOC(_IOC_NONE, 0, 0x20, 0), 0xb439f08c) = 1 ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0x2) = -1 EFAULT (Bad address) ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0xb4395520) = -1 EINVAL (Invalid argument) ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0xb439552c) = -1 EINVAL (Invalid argument) ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0xffef47c0) = -1 EINVAL (Invalid argument) ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0x2) = -1 EFAULT (Bad address) ioctl(3, _IOC(_IOC_NONE, 0, 0x7, 0), 0xffef47c0) = -1 EINVAL (Invalid argument) write(2, "ioctl: Invalid argument\n", 24ioctl: Invalid argument ) = 24 mprotect(0xeb8d1000, 4096, PROT_READ|PROT_WRITE) = 0 mprotect(0xeb8d1000, 4096, PROT_READ) = 0 mprotect(0xeb8d1000, 4096, PROT_READ|PROT_WRITE) = 0 mprotect(0xeb8d1000, 4096, PROT_READ) = 0 exit_group(1) = ? +++ exited with 1 +++
I'm at this commit:
commit 4a9fa934e9a564c09b5fddfe2b36a42b02e750c9 (HEAD -> master, origin/master, origin/HEAD)
Merge: ff44913 0ce0e27
Author: Marin <[email protected]>
Date: Wed Dec 18 19:38:45 2019 +0100
Merge branch 'master' of https://github.com/P1sec/QCSuper
hello!, did you have any luck with this issue? I am actually experiencing mostly the same thing...
Hello! Well I did go through, I updated Android to 7.0 (using normal OP3 system upgrade, nothing fancy) and rooted the device again... From then everything went smooth,
It works great! Cheers
On Wed, Sep 9, 2020, 8:42 PM James Moore [email protected] wrote:
No, and ended up not pursuing it at all. Good luck!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/P1sec/QCSuper/issues/43#issuecomment-689881371, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJHKDJU5RHCS3CTQHDYBDHDSFAHH3ANCNFSM4OIYHXPQ .