Comments (16)
bpasquet
commented on June 12, 2024
2
I'm in the same case, LG NEXUS 5 rooted, personnally I can put the phone in diag mode :
getprop sys.usb.config --> diag,adb
But I haven't any repository /dev/diag on my phone and the program return me :
Could not find /dev/diag, does your phone have a Qualcomm chip?
from qcsuper.
p1-mmr
commented on June 12, 2024
Hello, thanks for reporting. I think that it may be the same issue as in #5, and I may have fixed the issue in 9f419d8. Can you pull the latest commits and confirm?
from qcsuper.
EvgeniaPatsoni
commented on June 12, 2024
Yes after pulling the latest changes Wireshark does indeed open!
Unfortunately though, once it opens it displays a Message: No packets captured
Do you have any idea if this has to do with the previous issue or if there is something wrong with my device?
from qcsuper.
p1-mmr
commented on June 12, 2024
If Wireshark displays this error immediately, then this means that QCSuper immediately stopped sending packets to Wireshark (most likely it exited for some reason).
Is any output displayed by QCSuper in the terminal at the time where Wireshark shows an error? If yes, can you share it?
Also, can you tell whether it works better by using --pcap-dump /tmp/output_pcap.pcap instead of --wireshark-live (this should write a capture to the disk)?
from qcsuper.
EvgeniaPatsoni
commented on June 12, 2024
Both commands (wireshark and pcap) display the same output in the terminal:
open: No such file or directory
The connection to the adb bridge was closed, or preempted by another QCSuper instance
Below is the wireshark message
from qcsuper.
p1-mmr
commented on June 12, 2024
Thank you for your feedback.
In order to help troubleshooting the issue, can you:
- Pull the latest modifications (I have enriched debugging output in f2a3482)
- Run the regular capturing command, adding the
-v(verbose) flag:./qcsuper.py --adb --wireshark-live -v - Paste the obtained output
Thank you!
from qcsuper.
EvgeniaPatsoni
commented on June 12, 2024
After pulling changes and running command with -v, this is the output in the console:
[>] Running adb command: /usr/bin/adb exec-out id
[<] Obtained result for running "/usr/bin/adb exec-out id": b'uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0\n'
[>] Running adb command: /usr/bin/adb exec-out "test -w /dev/diag; echo DIAG_NOT_WRITEABLE=$?; test -e /dev/diag; echo DIAG_NOT_EXISTS=$?; test -r /dev; echo DEV_NOT_READABLE=$?; su -c id"
[<] Obtained result for running "/usr/bin/adb exec-out "test -w /dev/diag; echo DIAG_NOT_WRITEABLE=$?; test -e /dev/diag; echo DIAG_NOT_EXISTS=$?; test -r /dev; echo DEV_NOT_READABLE=$?; su -c id"": b'DIAG_NOT_WRITEABLE=1\nDIAG_NOT_EXISTS=1\nDEV_NOT_READABLE=1\nuid=0(root) gid=0(root) context=u:r:init:s0\n'
[>] Running adb command: /usr/bin/adb exec-out "su -c \"test -e /dev/diag; echo DIAG_NOT_EXISTS=$?\""
[<] Obtained result for running "/usr/bin/adb exec-out "su -c \"test -e /dev/diag; echo DIAG_NOT_EXISTS=$?\""": b'DIAG_NOT_EXISTS=0\n'
[>] Running adb command: /usr/bin/adb push /home/evgenia/qcsuper/inputs/adb_bridge/adb_bridge /data/local/tmp
[<] Obtained result for running "/usr/bin/adb push /home/evgenia/qcsuper/inputs/adb_bridge/adb_bridge /data/local/tmp": b'[100%] /data/local/tmp/adb_bridge\n/home/evgenia/qcsuper/inputs/adb_bridge/adb_bridge: 1 file pushed. 0.2 MB/s (11608 bytes in 0.066s)\n'
[>] Running adb command: /usr/bin/adb exec-out "su -c \"killall -q adb_bridge; chmod 755 /data/local/tmp/adb_bridge\""
[<] Obtained result for running "/usr/bin/adb exec-out "su -c \"killall -q adb_bridge; chmod 755 /data/local/tmp/adb_bridge\""": b'tmp-mksh: killall: not found\n'
[>] Running adb command: /usr/bin/adb forward tcp:43555 tcp:43555
WARNING: linker: /data/local/tmp/adb_bridge: unused DT entry: type 0x6ffffffe arg 0x5b0
WARNING: linker: /data/local/tmp/adb_bridge: unused DT entry: type 0x6fffffff arg 0x1
open: No such file or directory
[>] Sending request DIAG_LOG_CONFIG_F of length 7: b'\x00\x00\x00\x00\x00\x00\x00'
The connection to the adb bridge was closed, or preempted by another QCSuper instance
from qcsuper.
p1-mmr
commented on June 12, 2024
Ok, a few suggestions of things to check:
- It would be interesting to have the output of these two commands:
adb shell su -c "ls -l /dev"andadb shell su -c "stat /dev/diag" - Some posts online seem to indicate that there is known trouble to communicate with /dev/diag on Nexus 5, but that installing an alternative kernel, called Franco kernel, solves the issue: https://lists.srlabs.de/pipermail/gsmmap/2015-September/001338.html
- The official website is https://kernels.franco-lnx.net/ (I advise to back up your device if you do this manipulation)
- Some posts suggest that disabling SELinux may help with accessing Diag on Nexus 5 (https://forum.xda-developers.com/google-nexus-5/help/dev-enable-diagnostic-mode-t2535478) but this seems to mostly require to install another kernel foremost
- To check if any log was related to QCSuper was emitted from SELinux, you may run
adb shell su -c "dmesg 2>&1 | grep adb_bridge"
- To check if any log was related to QCSuper was emitted from SELinux, you may run
from qcsuper.
EvgeniaPatsoni
commented on June 12, 2024
Ok so I tried both of the options. First I flashed ElementalX kernel (Franco kernel showed errors upon installation) and then I disabled SELinux. I also reinstalled the phone drivers on my pc so that it would be properly recognized as a diagnostics port. But still no dev/diag directory.
However, I found that a diag folder exist in the /d directory instead of /dev. I am not sure if this is the same as the one needed.
Below is the adb shell su -c "ls -l /dev" output:
-r--r--r-- root root 131072 2019-07-15 11:28 __properties__
crw-rw-r-- system radio 10, 51 1973-07-18 22:07 alarm
crw-rw---- adb adb 10, 60 1973-07-18 22:07 android_adb
crw------- root root 10, 62 1973-07-18 22:07 android_mbim
crw------- root root 10, 55 1973-07-18 22:07 android_rndis_qc
crw------- root root 250, 26 1973-07-18 22:07 apr
crw------- root root 250, 19 1973-07-18 22:07 apr_apps2
crw-rw-rw- root root 10, 47 1973-07-18 22:07 ashmem
crw-rw---- nfc nfc 10, 63 1973-07-18 22:07 bcm2079x
crw-rw-rw- root root 10, 48 1973-07-18 22:07 binder
drwxr-xr-x root root 1973-07-18 22:07 block
crw------- root root 10, 57 1973-07-18 22:07 ccid_bulk
crw------- root root 10, 58 1973-07-18 22:07 ccid_ctrl
crw------- root root 5, 1 1973-07-18 22:07 console
crw------- root root 10, 41 1973-07-18 22:07 cpu_dma_latency
drwxr-xr-x system system 1973-07-18 22:07 cpuctl
drwxr-xr-x system system 1973-07-18 22:07 cpuset
crw------- root root 10, 236 1973-07-18 22:07 device-mapper
crw------- root root 10, 81 1973-07-18 22:07 dsp_debug
crw------- root root 10, 50 1973-07-18 22:07 epm_adc
crw------- root root 235, 12 1973-07-18 22:07 erandom
crw------- root root 235, 11 1973-07-18 22:07 frandom
drwxrwx--- root system 2019-07-15 11:28 fscklogs
crw-rw-rw- root root 1, 7 1973-07-18 22:07 full
crw------- root root 10, 229 1973-07-18 22:07 fuse
drwxr-xr-x root root 1973-07-18 22:07 graphics
crw------- root root 240, 0 2019-07-15 11:41 hidg0
crw------- root root 240, 1 2019-07-15 11:41 hidg1
cr--r----- root system 10, 183 1973-07-18 22:07 hw_random
crw------- root root 89, 0 1973-07-18 22:07 i2c-0
crw------- root root 89, 2 1973-07-18 22:07 i2c-2
crw------- root root 89, 84 1973-07-18 22:07 i2c-84
drwxr-xr-x root root 1973-07-18 22:07 input
crw-rw-r-- system system 10, 95 1973-07-18 22:07 ion
crw-rw---- system camera 239, 0 1973-07-18 22:07 jpeg0
crw-rw---- system camera 238, 0 1973-07-18 22:07 jpeg1
crw-rw---- system camera 237, 0 1973-07-18 22:07 jpeg2
crw------- root root 10, 52 1973-07-18 22:07 keychord
crw-rw-rw- system system 244, 0 2019-07-15 11:47 kgsl-3d0
crw------- root root 1, 11 1973-07-18 22:07 kmsg
crw------- root root 10, 59 1973-07-18 22:07 laf
crw------- root root 10, 237 1973-07-18 22:07 loop-control
crw-rw---- system camera 251, 0 1973-07-18 22:07 media0
crw-rw---- system camera 251, 1 1973-07-18 22:07 media1
crw-rw---- system camera 251, 2 1973-07-18 22:07 media2
drwx------ root system 1973-07-18 22:07 memcg
crw------- root root 10, 74 1973-07-18 22:07 msm_aac
crw------- root root 10, 80 1973-07-18 22:07 msm_aac_in
crw-rw---- system audio 10, 46 1973-07-18 22:07 msm_acdb
crw------- root root 10, 71 1973-07-18 22:07 msm_amrnb
crw------- root root 10, 77 1973-07-18 22:07 msm_amrnb_in
crw------- root root 10, 70 1973-07-18 22:07 msm_amrwb
crw------- root root 10, 66 1973-07-18 22:07 msm_amrwb_in
crw------- root root 10, 69 1973-07-18 22:07 msm_amrwbplus
crw------- root root 10, 68 1973-07-18 22:07 msm_evrc
crw------- root root 10, 78 1973-07-18 22:07 msm_evrc_in
crw-rw---- system audio 10, 72 1973-07-18 22:07 msm_mp3
crw------- root root 10, 73 1973-07-18 22:07 msm_multi_aac
crw------- root root 10, 67 1973-07-18 22:07 msm_qcelp
crw------- root root 10, 79 1973-07-18 22:07 msm_qcelp_in
crw-rw---- system audio 10, 45 1973-07-18 22:07 msm_rtac
crw------- root root 253, 0 1973-07-18 22:07 msm_sps
crw------- root root 254, 0 1973-07-18 22:07 msm_thermal_query
crw------- root root 10, 76 1973-07-18 22:07 msm_wma
crw------- root root 10, 75 1973-07-18 22:07 msm_wmapro
crw-rw---- root mtp 10, 56 1973-07-18 22:07 mtp_usb
crw------- root root 10, 40 1973-07-18 22:07 network_latency
crw------- root root 10, 39 1973-07-18 22:07 network_throughput
crw------- root root 10, 82 1973-07-18 22:07 nmea
crw-rw-rw- root root 1, 3 1973-07-18 22:07 null
crw-rw---- radio vpn 108, 0 1973-07-18 22:07 ppp
crw-rw-rw- root root 5, 2 2019-07-15 11:41 ptmx
drwxr-xr-x root root 1970-01-01 02:00 pts
crw-r----- radio radio 10, 85 1973-07-18 22:07 qmi0
crw-r----- radio radio 10, 84 1973-07-18 22:07 qmi1
crw-r----- radio radio 10, 83 1973-07-18 22:07 qmi2
crw-rw---- system drmrpc 243, 0 1973-07-18 22:07 qseecom
crw------- root root 10, 93 1973-07-18 22:07 ramdump_adsp
crw------- root root 10, 44 1973-07-18 22:07 ramdump_audio-ocmem
crw------- root root 10, 90 1973-07-18 22:07 ramdump_modem
crw------- root root 10, 42 1973-07-18 22:07 ramdump_smem
crw------- root root 10, 89 1973-07-18 22:07 ramdump_smem-modem
crw------- root root 10, 88 1973-07-18 22:07 ramdump_venus
crw-rw-rw- root root 1, 8 1973-07-18 22:07 random
crw------- root root 10, 94 1973-07-18 22:07 rfkill
crw------- root root 10, 53 1973-07-18 22:07 rmnet_ctrl
crw-r----- radio radio 10, 61 1973-07-18 22:07 rmnet_mux_ctrl
crw-rw---- system system 252, 0 1973-07-18 22:07 rtc0
crw------- root root 249, 0 1973-07-18 22:07 sensors
crw------- root root 250, 8 1973-07-18 22:07 smd22
crw-r----- radio radio 250, 22 1973-07-18 22:07 smd_cxm_qmi
crw------- root root 250, 25 1973-07-18 22:07 smd_data_0
crw------- root root 250, 24 1973-07-18 22:07 smd_logging_0
crw------- root root 250, 27 1973-07-18 22:07 smd_pkt_loopback
crw------- root root 250, 21 1973-07-18 22:07 smd_sns_adsp
crw------- root root 250, 18 1973-07-18 22:07 smd_sns_dsps
crw------- root root 250, 23 1973-07-18 22:07 smd_test_framework
crw------- root root 250, 9 1973-07-18 22:07 smdcnt_rev0
crw------- root root 250, 10 1973-07-18 22:07 smdcnt_rev1
crw------- root root 250, 11 1973-07-18 22:07 smdcnt_rev2
crw------- root root 250, 12 1973-07-18 22:07 smdcnt_rev3
crw------- root root 250, 13 1973-07-18 22:07 smdcnt_rev4
crw------- root root 250, 14 1973-07-18 22:07 smdcnt_rev5
crw------- root root 250, 15 1973-07-18 22:07 smdcnt_rev6
crw------- root root 250, 16 1973-07-18 22:07 smdcnt_rev7
crw------- root root 250, 17 1973-07-18 22:07 smdcnt_rev8
crw-r----- radio radio 250, 0 1973-07-18 22:07 smdcntl0
crw-r----- radio radio 250, 1 1973-07-18 22:07 smdcntl1
crw-r----- radio radio 250, 2 1973-07-18 22:07 smdcntl2
crw-r----- radio radio 250, 3 1973-07-18 22:07 smdcntl3
crw-r----- radio radio 250, 4 1973-07-18 22:07 smdcntl4
crw-r----- radio radio 250, 5 1973-07-18 22:07 smdcntl5
crw-r----- radio radio 250, 6 1973-07-18 22:07 smdcntl6
crw-r----- radio radio 250, 7 1973-07-18 22:07 smdcntl7
crw------- root root 250, 20 1973-07-18 22:07 smdcntl8
crw------- root root 10, 86 1973-07-18 22:07 smem_log
drwxr-xr-x root root 1973-07-18 22:07 snd
drwxr-xr-x root root 2019-07-15 11:41 socket
crw------- root root 10, 92 1973-07-18 22:07 subsys_adsp
crw------- root root 10, 91 1973-07-18 22:07 subsys_modem
crw------- root root 10, 87 1973-07-18 22:07 subsys_venus
crw------- root root 10, 64 1973-07-18 22:07 tgt
crw-rw-rw- root root 5, 0 1973-07-18 22:07 tty
crw-rw---- root system 4, 0 1973-07-18 22:07 tty0
crw------- root root 4, 1 1973-07-18 22:07 tty1
crw------- root root 4, 10 1973-07-18 22:07 tty10
crw------- root root 4, 11 1973-07-18 22:07 tty11
crw------- root root 4, 12 1973-07-18 22:07 tty12
crw------- root root 4, 13 1973-07-18 22:07 tty13
crw------- root root 4, 14 1973-07-18 22:07 tty14
crw------- root root 4, 15 1973-07-18 22:07 tty15
crw------- root root 4, 16 1973-07-18 22:07 tty16
crw------- root root 4, 17 1973-07-18 22:07 tty17
crw------- root root 4, 18 1973-07-18 22:07 tty18
crw------- root root 4, 19 1973-07-18 22:07 tty19
crw------- root root 4, 2 1973-07-18 22:07 tty2
crw------- root root 4, 20 1973-07-18 22:07 tty20
crw------- root root 4, 21 1973-07-18 22:07 tty21
crw------- root root 4, 22 1973-07-18 22:07 tty22
crw------- root root 4, 23 1973-07-18 22:07 tty23
crw------- root root 4, 24 1973-07-18 22:07 tty24
crw------- root root 4, 25 1973-07-18 22:07 tty25
crw------- root root 4, 26 1973-07-18 22:07 tty26
crw------- root root 4, 27 1973-07-18 22:07 tty27
crw------- root root 4, 28 1973-07-18 22:07 tty28
crw------- root root 4, 29 1973-07-18 22:07 tty29
crw------- root root 4, 3 1973-07-18 22:07 tty3
crw------- root root 4, 30 1973-07-18 22:07 tty30
crw------- root root 4, 31 1973-07-18 22:07 tty31
crw------- root root 4, 32 1973-07-18 22:07 tty32
crw------- root root 4, 33 1973-07-18 22:07 tty33
crw------- root root 4, 34 1973-07-18 22:07 tty34
crw------- root root 4, 35 1973-07-18 22:07 tty35
crw------- root root 4, 36 1973-07-18 22:07 tty36
crw------- root root 4, 37 1973-07-18 22:07 tty37
crw------- root root 4, 38 1973-07-18 22:07 tty38
crw------- root root 4, 39 1973-07-18 22:07 tty39
crw------- root root 4, 4 1973-07-18 22:07 tty4
crw------- root root 4, 40 1973-07-18 22:07 tty40
crw------- root root 4, 41 1973-07-18 22:07 tty41
crw------- root root 4, 42 1973-07-18 22:07 tty42
crw------- root root 4, 43 1973-07-18 22:07 tty43
crw------- root root 4, 44 1973-07-18 22:07 tty44
crw------- root root 4, 45 1973-07-18 22:07 tty45
crw------- root root 4, 46 1973-07-18 22:07 tty46
crw------- root root 4, 47 1973-07-18 22:07 tty47
crw------- root root 4, 48 1973-07-18 22:07 tty48
crw------- root root 4, 49 1973-07-18 22:07 tty49
crw------- root root 4, 5 1973-07-18 22:07 tty5
crw------- root root 4, 50 1973-07-18 22:07 tty50
crw------- root root 4, 51 1973-07-18 22:07 tty51
crw------- root root 4, 52 1973-07-18 22:07 tty52
crw------- root root 4, 53 1973-07-18 22:07 tty53
crw------- root root 4, 54 1973-07-18 22:07 tty54
crw------- root root 4, 55 1973-07-18 22:07 tty55
crw------- root root 4, 56 1973-07-18 22:07 tty56
crw------- root root 4, 57 1973-07-18 22:07 tty57
crw------- root root 4, 58 1973-07-18 22:07 tty58
crw------- root root 4, 59 1973-07-18 22:07 tty59
crw------- root root 4, 6 1973-07-18 22:07 tty6
crw------- root root 4, 60 1973-07-18 22:07 tty60
crw------- root root 4, 61 1973-07-18 22:07 tty61
crw------- root root 4, 62 1973-07-18 22:07 tty62
crw------- root root 4, 63 1973-07-18 22:07 tty63
crw------- root root 4, 7 1973-07-18 22:07 tty7
crw------- root root 4, 8 1973-07-18 22:07 tty8
crw------- root root 4, 9 1973-07-18 22:07 tty9
crw-rw---- bluetooth net_bt_stack 247, 99 1973-07-18 22:07 ttyHS99
crw------- root root 246, 0 1973-07-18 22:07 ttyHSL0
crw-rw---- system vpn 10, 200 1973-07-18 22:07 tun
crw-rw---- system net_bt_stack 10, 49 1973-07-18 22:07 uhid
crw-rw---- system net_bt_stack 10, 223 1973-07-18 22:07 uinput
crw------- root root 241, 0 1973-07-18 22:07 uio0
crw------- root root 241, 1 1973-07-18 22:07 uio1
crw------- root root 241, 2 1973-07-18 22:07 uio2
crw-rw-rw- root root 1, 9 1973-07-18 22:07 urandom
crw-rw---- root usb 10, 54 1973-07-18 22:07 usb_accessory
crw------- root root 10, 65 1973-07-18 22:07 usf1
crw-rw---- system camera 81, 5 1973-07-18 22:07 v4l-subdev0
crw-rw---- system camera 81, 6 1973-07-18 22:07 v4l-subdev1
crw-rw---- system camera 81, 15 1973-07-18 22:07 v4l-subdev10
crw-rw---- system camera 81, 17 1973-07-18 22:07 v4l-subdev11
crw-rw---- system camera 81, 19 1973-07-18 22:07 v4l-subdev12
crw-rw---- system camera 81, 20 1973-07-18 22:07 v4l-subdev13
crw-rw---- system camera 81, 21 1973-07-18 22:07 v4l-subdev14
crw-rw---- system camera 81, 22 1973-07-18 22:07 v4l-subdev15
crw-rw---- system camera 81, 23 1973-07-18 22:07 v4l-subdev16
crw-rw---- system camera 81, 24 1973-07-18 22:07 v4l-subdev17
crw-rw---- system camera 81, 7 1973-07-18 22:07 v4l-subdev2
crw-rw---- system camera 81, 8 1973-07-18 22:07 v4l-subdev3
crw-rw---- system camera 81, 9 1973-07-18 22:07 v4l-subdev4
crw-rw---- system camera 81, 10 1973-07-18 22:07 v4l-subdev5
crw-rw---- system camera 81, 11 1973-07-18 22:07 v4l-subdev6
crw-rw---- system camera 81, 12 1973-07-18 22:07 v4l-subdev7
crw-rw---- system camera 81, 13 1973-07-18 22:07 v4l-subdev8
crw-rw---- system camera 81, 14 1973-07-18 22:07 v4l-subdev9
crw------- root root 7, 0 1973-07-18 22:07 vcs
crw------- root root 7, 1 1973-07-18 22:07 vcs1
crw------- root root 7, 128 1973-07-18 22:07 vcsa
crw------- root root 7, 129 1973-07-18 22:07 vcsa1
drwxr-xr-x root root 1973-07-18 22:07 video
crw-rw---- system camera 81, 4 1973-07-18 22:07 video0
crw-rw---- system camera 81, 16 1973-07-18 22:07 video1
crw-rw---- system camera 81, 18 1973-07-18 22:07 video2
crw-rw---- system camera 81, 0 1973-07-18 22:07 video32
crw-rw---- system camera 81, 1 1973-07-18 22:07 video33
crw-rw---- system camera 81, 2 1973-07-18 22:07 video34
crw-rw---- system camera 81, 3 1973-07-18 22:07 video35
crw-r--r-- root root 10, 43 1973-07-18 22:07 xt_qtaguid
crw-rw-rw- root root 1, 5 1973-07-18 22:07 zero
The adb shell su -c "ls -l /d/diag" output:
-r--r--r-- root root 0 1970-01-01 02:00 status
-r--r--r-- root root 0 1970-01-01 02:00 table
-r--r--r-- root root 0 1970-01-01 02:00 work_pending
And the adb shell su -c "stat /d/diag" output:
File: `/d/diag'
Size: 0 Blocks: 0 IO Blocks: 4096 directory
Device: 5h Inode: 108 Links: 2
Access: (755/drwxr-xr-x) Uid: (0/ root) Gid: (0/ root)
Access: 2019-07-15 11:28:51.036999980
Modify: 1970-01-01 02:00:00.550000002
Change: 1970-01-01 02:00:00.550000002
from qcsuper.
p1-mmr
commented on June 12, 2024
Hello @bpasquet ,
personnally I can put the phone in diag mode :
getprop sys.usb.config --> diag,adb
When doing so, is there a /dev/tty* Diag device you can communicate with exposed on your PC?
In other to check this, you may try the procedure described in the "Using QCSuper with an USB modem" section of the README:
If you don't know which devices under
/devexpose the Diag port, you may have to try multiple of these. You can try to auto-detect it by stopping the ModemManager daemon (sudo systemctl stop ModemManager), and using the following command:sudo ModemManager --debug 2>&1 | grep -i 'port is QCDM-capable'then Ctrl-C.
These commands being to execute on your PC, and not on your Android phone.
Regards,
from qcsuper.
bpasquet
commented on June 12, 2024
Hello @p1-mmr and thank you for the fast answer.
I have /dev/ttyACM0 on my PC when I plug my device
from qcsuper.
p1-mmr
commented on June 12, 2024
Ok, can you run QCSuper with the command sudo ./qcsuper.py --usb-modem /dev/ttyACM0 --wireshark-live (specifying /dev/ttyACM0 or another sibling device that may be the Diag device) in this case?
from qcsuper.
bpasquet
commented on June 12, 2024
I get this return in verbose mode :
sudo ./qcsuper.py --usb-modem /dev/ttyACM0 --wireshark-live -v :
[>] Sending request DIAG_LOG_CONFIG_F of length 7: b'\x00\x00\x00\x00\x00\x00\x00' [>] Sending request DIAG_LOG_CONFIG_F of length 7: b'\x00\x00\x00\x00\x00\x00\x00' [>] Sending request DIAG_LOG_CONFIG_F of length 7: b'\x00\x00\x00\x00\x00\x00\x00' [>] Sending request DIAG_LOG_CONFIG_F of length 7: b'\x00\x00\x00\x00\x00\x00\x00' Error: Diag request DIAG_LOG_CONFIG_F with payload b'\x00\x00\x00\x00\x00\x00\x00' timed out
from qcsuper.
bpasquet
commented on June 12, 2024
@p1-mmr
I have installed SnoopSnitch on the mobile to try to make a pcap. This app have created de /dev/diag repository.
Now, when I run the command :
sudo ./qcsuper.py --adb --wireshark-live -v
wireshark is not opened and log look's like this :
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux exec-out id
[<] Obtained result for running "/tmp/qcsuper/inputs/external/adb/adb_linux exec-out id": b"adb server version (41) doesn't match this client (39); killing...\n* daemon started successfully\nuid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0\n"
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux exec-out "test -w /dev/diag; echo DIAG_NOT_WRITEABLE=$?; test -e /dev/diag; echo DIAG_NOT_EXISTS=$?; test -r /dev; echo DEV_NOT_READABLE=$?; su -c id"
[<] Obtained result for running "/tmp/qcsuper/inputs/external/adb/adb_linux exec-out "test -w /dev/diag; echo DIAG_NOT_WRITEABLE=$?; test -e /dev/diag; echo DIAG_NOT_EXISTS=$?; test -r /dev; echo DEV_NOT_READABLE=$?; su -c id"": b'DIAG_NOT_WRITEABLE=1\nDIAG_NOT_EXISTS=0\nDEV_NOT_READABLE=0\nuid=0(root) gid=0(root) groups=0(root) context=u:r:init:s0\n'
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux exec-out "su -c "test -e /dev/diag; echo DIAG_NOT_EXISTS=$?""
[<] Obtained result for running "/tmp/qcsuper/inputs/external/adb/adb_linux exec-out "su -c "test -e /dev/diag; echo DIAG_NOT_EXISTS=$?""": b'DIAG_NOT_EXISTS=0\n'
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux push /tmp/qcsuper/inputs/adb_bridge/adb_bridge /data/local/tmp
[<] Obtained result for running "/tmp/qcsuper/inputs/external/adb/adb_linux push /tmp/qcsuper/inputs/adb_bridge/adb_bridge /data/local/tmp": b'[100%] /data/local/tmp/adb_bridge\n/tmp/qcsuper/inputs/adb_bridge/adb_bridge: 1 file pushed. 5.6 MB/s (11608 bytes in 0.002s)\n'
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux exec-out "su -c "killall -q adb_bridge; chmod 755 /data/local/tmp/adb_bridge""
[>] Running adb command: /tmp/qcsuper/inputs/external/adb/adb_linux forward tcp:43555 tcp:4355
Any idea?
from qcsuper.
bpasquet
commented on June 12, 2024
When I do :
sudo ModemManager --debug 2>&1 | grep -i 'capable'
I see that is AT-capable instead of QCDM-capable
from qcsuper.
hunterra
commented on June 12, 2024
Managed to get network dump from LG Nexus 5. Steps:
- Flash Cataclysm firmware. I used Cataclysm-Jun_20_2015-HAMMERHEAD-Lollipop-5.1.1_r3_Stable.zip
- Install SnoopSnitch apk, it should be F-Droid version. Took it from 4pda.to
2.0.9 F-Droid - Launch SnoopSnitch, grant root permissions. Application writes /dev/diag file. Stop SnoopSnitch application
- Run QCSuper: python3 qcsuper.py --adb --wireshark-live
from qcsuper.
Related Issues (20)
- No NAS present in 5G QCDM (Qualcomm Diag) protocol packets HOT 1
- old Motorola worked
- Snapdragon 8 gen 3 PCI Express HOT 1
- Confirmation QCSuper working on Pinephone Pro
- How to make it work on Pixel 4 XL rooted and Diag port enabled?
- Impossible to start 4G LTE usb qualcom modem (huawei)
- Reporting MC7455 is working HOT 1
- ERROR @ adb.py:424
- I am trying to connect this QCSuper tool with ue samsung s22. HOT 4
- Huawei E1552 works with QCSuper
- Nokia6 (TA-1021) working successfully
- Not working on Oneplus Nord (avicii) PixeExperience 13+
- Update for Android 13 & 14 HOT 3
- Qcuper dose not work on G620s rooted phone
- Wireshark Not Capturing Packets
- Logging only lasts a few seconds with Samsung S21 HOT 1
- Samsung Galaxy S5 working successfully
- No module named 'src.modules' HOT 1
- regarding snapdragon 8 gen 3
- Support alternate file system with Qualcomm modem modules
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from qcsuper.