Results 1 to 9 of 9

Thread: Help needed with Nethunter external bluetooth adapter

  1. #1
    Join Date
    2016-Nov
    Posts
    17

    Help needed with Nethunter external bluetooth adapter (and dbus)

    My new bt adapter has just arrived and it works with laptop but I would like to equip OTG on my OnePlus One - the Sena UD100-G03. Tried everything I could find online related to bluetooth.
    Re-flashed latest Kali nightly (2017.11-18-1618), with latest kernel on CM13.1.2.
    Linux version 3.4.112-cyanogenmod-g8fbc62e (root@nhbuild-box) (gcc version 4.7 (GCC) ) #3 SMP PREEMPT Fri Aug 12 19:57:27 CDT 2016
    Updated with apt-get update, dist-upgrade but still not getting it. Has the bluetooth package, bluez, blueman.

    with dbus running, bluetooth service/bluetoothd does not want to start. Seems like a permission issue to use the "external bt accessing" module for me. Couldn't find any solution for weeks now, hope there is a chance to get it working.
    Everything else is working like HID, wlan injection, etc.

    Code:
    [FAIL] bluetooth is not running ... failed!
    root@kali:~# bluetoothd -n
    bluetoothd[30492]: Bluetooth daemon 5.49
    bluetoothd[30492]: Failed to access management interface
    bluetoothd[30492]: Adapter handling initialization failed
    Also a strange thing that dbus struggles to start since the last few updates (not sure when). Takes about 3mins to start and seems like not doing it's job properly.

    Managed to see a dbus-monitor:
    Code:
    root@kali:/# dbus-monitor --system
    signal time=1532327145.748679 sender=org.freedesktop.DBus -> destination=:1.0 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
       string ":1.0"
    signal time=1532327145.754697 sender=org.freedesktop.DBus -> destination=:1.0 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
       string ":1.0"
    method call time=1532327345.837790 sender=:1.1 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
    method return time=1532327345.837857 sender=org.freedesktop.DBus -> destination=:1.1 serial=1 reply_serial=1
       string ":1.1"
    signal time=1532327345.837901 sender=org.freedesktop.DBus -> destination=(null destination) serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
       string ":1.1"
       string ""
       string ":1.1"
    signal time=1532327345.837962 sender=org.freedesktop.DBus -> destination=:1.1 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
       string ":1.1"
    method call time=1532327345.838793 sender=:1.1 -> destination=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RequestName
       string "org.bluez"
       uint32 4
    signal time=1532327345.838852 sender=org.freedesktop.DBus -> destination=(null destination) serial=6 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
       string "org.bluez"
       string ""
       string ":1.1"
    signal time=1532327345.838910 sender=org.freedesktop.DBus -> destination=:1.1 serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
       string "org.bluez"
    method return time=1532327345.838947 sender=org.freedesktop.DBus -> destination=:1.1 serial=4 reply_serial=2
       uint32 1
    method call time=1532327345.839649 sender=:1.1 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
       string "type='signal',interface='org.freedesktop.DBus.Local',member='Disconnected'"
    method return time=1532327345.839698 sender=org.freedesktop.DBus -> destination=:1.1 serial=5 reply_serial=3
    signal time=1532327345.841698 sender=org.freedesktop.DBus -> destination=:1.1 serial=7 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
       string "org.bluez"
    signal time=1532327345.841757 sender=org.freedesktop.DBus -> destination=(null destination) serial=8 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
       string "org.bluez"
       string ":1.1"
       string ""
    signal time=1532327345.841820 sender=org.freedesktop.DBus -> destination=:1.1 serial=9 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
       string ":1.1"
    signal time=1532327345.841859 sender=org.freedesktop.DBus -> destination=(null destination) serial=10 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
       string ":1.1"
       string ":1.1"
       string ""
    When started it manually, the bluetooth service starts too but still not getting any info from dbus. You can see that in the next reply. I guess bt service starts because there is a not completely started dbus service, so doesn't make any difference.

    I tried many configs for avahi-dbus.conf to let everything through, but whenever I reload and start again, it is still slow, and bluetooth is not working.

    Thanks for reading!
    Last edited by yesimxev; 2018-07-23 at 08:13. Reason: Update about dbus

  2. #2
    Join Date
    2016-Dec
    Location
    Canada
    Posts
    196
    service bluetooth start

  3. #3
    Join Date
    2016-Nov
    Posts
    17
    Quote Originally Posted by bigbiz View Post
    service bluetooth start
    Might not be obvious, I did that and doesn't work, except when I get the dbus service reloaded, then the bluetooth service starts. Still doesn't get bluetooth communication though, nor info in the rfkill list.

    Code:
    root@kali:~# service bluetooth start
    [ ok ] Starting bluetooth: bluetoothd.
    root@kali:~# service bluetooth status
    [FAIL] bluetooth is not running ... failed!
    root@kali:~# service dbus force-reload
    [....] Reloading system message bus config...    
    Failed to open connection to "system" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    root@kali:~# service dbus status
    [ ok ] dbus is running.
    root@kali:~# service bluetooth start
    [ ok ] Starting bluetooth: bluetoothd.
    root@kali:~# service bluetooth status
    [ ok ] bluetooth is running.
    root@kali:~# hciconfig -a
    root@kali:~# hciconfig hci0 up
    Can't get device info: No such device
    root@kali:~# service bluetooth status
    [ ok ] bluetooth is running.
    root@kali:~# hciconfig hci0 up
    Can't get device info: No such device
    root@kali:~# rfkill list
    0: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no

  4. #4
    Join Date
    2016-Nov
    Posts
    17
    After researching and changing programs, settings for countless hours, I finally thought okay, let's build a kernel from scratch for it. I have enabled btusb, and rfcomm (NOT as a module, as OnePlusOne doesn't load modules! And now I can see my bluetooth adapter. Dbus and bluetooth service doesn't even need to be run for it. Bluetooth service still can't run btw.

    Scanning, inquiring, sdptool works.

    But the most needed part of it doesn't work: RFCOMM
    I have enbaled in the kernel, so for me now it seems to be an rfcomm driver issue.

    Even after creating it's folder manually
    Code:
    mkdir -p /dev/bluetooth/rfcomm
    mknod -m 666 /dev/bluetooth/rfcomm/0 c 216 0
    bluesnarfer gets the device name, then gives me timeout error:
    Code:
    device name: *********
    bluesnarfer: open /dev/bluetooth/rfcomm/0, Connection timed out
    bluesnarfer: bt_rfcomm_config failed
    bluesnarfer: unable to create rfcomm connection
    bluesnarfer: release rfcomm ok
    l2ping gives me the same error, less explained
    Code:
    Can't connect: Connection timed out
    I have tried almost all possible non-rfcomm related things:
    Re installed:
    CM13.0 + nethunter nightly / my own build from nethunter-fs builder, with many other, and my own kernel
    CM13.1 + nethunter nightly / my own build from nethunter-fs builder, with many other, and my own kernel
    LineageOS 14.1 + nethunter nightly / my own build from nethunter-installer with kernels from the web
    LineageOS 15.1 + nethunter nightly / my own build from nethunter-installer with kernel from the web (yes there is one available a few days ago!)

    Also I am looking for the LineageOS 15.1 Nethunter kernel sources (or the solution for the original problem ), so I can try to build a new one with btusb and rfcomm enabled (as the above one doesn't have it)

    @jcadduono @binkybear - you might be able to help me with kernels

    Thanks for reading!
    Last edited by yesimxev; 2018-09-14 at 13:58. Reason: Story changed

  5. #5
    Join Date
    2016-Nov
    Posts
    17
    Installing bluez-4.7 from bluez.org makes the bluetooth service running. And 4.5 makes l2ping and rfcomm working. Although very unstable, it starts and l2ping works. Will try to check the difference in the services as rfcomm does not work without bt service. Even 4.99 from old.kali.org does not work in terms of service. Dbus actually works after creating a new kalifs. Will do a bit of research then close this issue but I have to return to life now. Maybe >4.5 bluez is not compatilbe with 3.4.11x kernels

  6. #6
    Join Date
    2016-Nov
    Posts
    17
    In the meantime, it seems that the only possible way to get the bluetooth service running and working at all, by install bluez-4.5 without deleting the latest one installed..? Everything works, except bluesnarfer (which was not updated since published, any way of running it reboots the phone after few mins).

    For those who need btusb enabled Oneplus One (bacon) kernel (also enabled CANBus)
    https://androidfilehost.com/?fid=1322778262904029166

    Also for those who suffers from laggy DBUS too, I have built latest Kalifs:
    Generic NetHunter armhf full with su
    https://www.androidfilehost.com/?fid...32744536983523
    Generic NetHunter armhf full without su
    https://www.androidfilehost.com/?fid...32744536983520
    Last edited by yesimxev; 3 Weeks Ago at 20:10.

  7. #7
    Join Date
    2016-Dec
    Location
    Canada
    Posts
    196

  8. #8
    Join Date
    2016-Nov
    Posts
    17
    Tried and nice. However, does not help bluetooth service to work. So anything that needs rfcomm, which needs btservice, fails with timeout

  9. #9
    Join Date
    2016-Nov
    Posts
    17
    Quote Originally Posted by bigbiz View Post
    Tried and nice. However, does not help bluetooth service to work. So anything that needs rfcomm, which needs btservice, fails with timeout

Similar Threads

  1. Airmon-ng on nethunter does not detect external wifi adapter
    By mordax in forum NetHunter General Questions
    Replies: 8
    Last Post: 2018-07-21, 02:01
  2. Compatible Bluetooth adapter for Kali Nethunter
    By Bugs78 in forum NetHunter General Questions
    Replies: 0
    Last Post: 2017-03-09, 17:40
  3. External Bluetooth issue
    By pattap in forum NetHunter General Questions
    Replies: 0
    Last Post: 2017-02-22, 22:01

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •