Page 14 of 20 FirstFirst ... 41213141516 ... LastLast
Results 131 to 140 of 197

Thread: [New Tutorial For BT3 ONLY]One bluetooth post to rule them all!

  1. #131
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    9

    Default

    @akamagic
    The executable as I remember is important for the default file or else there are pairing problems.
    To be sure make them executable.

    Can anyone confirm this?

    @ASTRAPI:

    You cannot pair a sniffer.
    You cannot sniff without the firmware. The first post describes how to change the hardware but not how to upgrade the firmware which if you have done it whatsoever you should be able to be in RAW mode as I see.

    @ColForbin

    You are more than right. In fact I stated in previous post that I managed to be harsh without having this intention. I got in this subject by reading the posts of DrGreen and he is more than helpful as you say.

    I know by my own experience that the lack of time makes difficult to update and share information promptly and 100% correctly. And obviously this is the case here.

    Although it is summer I will try to contribute more in this subject or else... from September.
    I bet DrGreen will produce smthg in the meantime. Or else someone else or even me will catch him up.

    In any case... the forum needs contribution and I hope it will be shared.

  2. #132
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    14

    Default

    @DARTIS

    I don't believe it is necessary to make them executable as for me it works either way, but guess it wouldn't hurt

    @jrm7262

    Its really up to you since you could still scan phones and use simple attacks such as bluebugger and bluesnarfer (depending on the phone) with one unmodified dongle. But of course it would be better to have two dongles. One as a sniffer (in raw mode) and the other unmodified (for scanning and such) as being able to sniff is where the exploits really begin.

    ps: The DBT-120 is what i use as my sniffer and i have another cheap dongle for scanning and pairing

  3. #133
    Very good friend of the forum drgr33n's Avatar
    Join Date
    Jan 2010
    Location
    Dark side of the moon ...
    Posts
    699

    Default

    aggtrfrad / sws2007

    Can you sen me all the info in a PM please with all the output messages from bccmd etc.

    akamagic

    Once a dongle has been modified it cannot perform scan tasks ETC because the source code you are using do not contain the right op codes and haven't been coded in Not yet

    johnjohnsp1

    dbt-122 has a broadcom chipset and doesn't work

    daleapearson

    Yes you are on the right path, I have alot to catch up on so if you are stuck, post back and I will help out more.

    ASTRAPI

    Again once a dongle has been modified it cannot perform scan tasks ETC because the source code you are using do not contain the right op codes and haven't been coded in.

    DARTIS

    Harsh words man ! There are a hundred ways to skin a cat !!!!!!!! For EG:

    Quote Originally Posted by DARTIS
    For example:
    mknod –m 666 /dev/rfcomm1 c 216 1
    mknod –m 666 /dev/rfcomm2 c 216 2
    mknod –m 666 /dev/rfcomm3 c 216 3

    sdptool add --channel=1 DUN
    sdptool add --channel=2 OPUSH
    sdptool add --channel=3 FTP

    rfcomm bind 1 [….MAC] 3
    rfcomm bind 2 [….MAC] 6
    rfcomm bind 3 [….MAC] 7


    Afterwards you connect/bind with rfcomm the device 1 with the respective channel of the phone which has the same service..this shows some luck of knowledge.
    Why not use mknod ?

    Blue|Smash v2.0 was a mix up that I'm looking into. It IS 100% functional! If I've missed anybody or anything out post again as I'm back for a while now As for the people asking for the frontline firmware can I just point out that is is illegal to obtain a copy without buying it ! I am not prepared to offer any assistance in getting a copy.

  4. #134
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    12

    Default Which version of firmware ?

    Hi All,

    When upgrading the firmware of the usb bluetooth dongle (in my case D-Link DBT 120), does it matter which version to upgrade with?

    I read through a lot of posts and versions are mentioned from 47 to 52.
    (There was one comment that version 5 bricks the dongle).

    Any advice appreciated, I'd like not to brick the dongle on my first attempt, just because I used the wrong version of the firmware.


    Kindest regards

    James

  5. #135
    Just burned his ISO
    Join Date
    Jun 2008
    Posts
    9

    Default

    @Dr_GrEeN:

    God...sorry. I know I was but it was an explosion of thoughts not really deserving to be used all together against you.

    Why not use mknod ?
    hmmm...sorry cannot understand.
    I just state a more straightforward technique for rfcomm bindings

    I hope Bluesmash 2.0 will get fully functional because the DB and pygame commands are buggy.

    All the other are functional as they seem but cannot work due to the link with the above mentioned bugs.

    @jrm7262:

    Use only airsnifferdev47bc2.dfu
    or 47 if you prefer.

  6. #136
    Junior Member aggtrfrad's Avatar
    Join Date
    Apr 2008
    Posts
    74

    Default a7eng

    -a7eng eb502 uses bluecore2-ext chip. not bluecore4. Frontline has written a couple of firmware files for different devices including bluecore2/3/4 chips. Frontline firmware files look like that: Airsnifferdev??bc?.dfu
    first two ? is version of the firmware, third ? is chipset version it is intended for.
    That means airsnifferdev57bc4 won't work (not even load) to a a7eng-eb502 dongle using bluecore2. airsnifferdev??bc2 uploads to the dongle successfully, BUT the dongle fails verification tests, and never comes back to normal state, it stays in dfu mode (devid is ffff and it only accepts dfu commands, not bccmd commands, and its not an hci device anymore).

    -When downloading the original firmware from your a7eng-eb502 dongle to your pc, something goes wrong and the firmware file is corrupted. not sure why but it is. That means that if you upload the wrong firmware to your dongle, it's not coming back by re-uploading your back up, it's corrupted.
    I have tried several versions of firmware for csr, to bring my dongle back from dfu mode, but none worked.

    -bccmd works perfect for this dongle, but with no new firmware, nothing done.

    -The only way to bring this dongle back from dfu more, is to upload the factory firmware, that is the only one it will ever accept (i hope i'm wrong cause i spent 80$ after reading it can be a sniffer). This file is not available to the public, I got it after begging a developer from a7eng for help, and sending all my order information to him.

    p.s. I have tried airsnifferdev46/47bc2. If you have older or newer versions (for bc2 always) pls pm me. Maybe we are lucky. Also, if anyone's into dfu protocol, pls pm me. I read that there are some security keys between firmware files and csr chipsets, maybe that's the reason the dongle only accepts the factory firmware.
    Here's a bccmd pslist output, for the record...
    Code:
    0x0001 - Bluetooth address (8 bytes)
    0x001e - Radio power table (40 bytes)
    0x0021 - Default transmit power (2 bytes)
    0x002d - Maximum transmit power when peer has no RSSI (2 bytes)
    0x015e - DFU encryption VM application public key MSB (64 bytes)
    0x015f - DFU encryption VM application public key LSB (64 bytes)
    0x0160 - DFU encryption VM application M dash (2 bytes)
    0x0161 - DFU encryption VM application public key R2N MSB (64 bytes)
    0x0162 - DFU encryption VM application public key R2N LSB (64 bytes)
    0x01be - UART Baud rate (2 bytes)
    0x01c2 - UART configuration when under VM control (2 bytes)
    0x01f6 - Crystal frequency trim (2 bytes)
    0x01f9 - Host interface (2 bytes)
    0x01fc - Enable host query task? (2 bytes)
    0x0209 - TX and RX PIO control (2 bytes)
    0x0259 - Module serial number (4 bytes)
    0x025a - Module design ID (2 bytes)
    0x025c - Module security code (16 bytes)
    0x0267 - Module manufactuer data 9 (16 bytes)
    0x02b4 - User configuration data 42 (32 bytes)
    0x02c2 - USB product string (56 bytes)
    0x02c3 - USB serial number string (40 bytes)
    0x03cc - HCI traffic routed internally (2 bytes)
    0x03cd - Initial device bootmode (2 bytes)
    0x04b0 - Unknown (10 bytes)
    0x04b8 - Unknown (2 bytes)
    0x04b9 - Unknown (2 bytes)
    0x04ba - Unknown (2 bytes)
    0x04bb - Unknown (2 bytes)
    0x04bc - Unknown (2 bytes)
    0x6001 - Unknown (128 bytes)
    -Google is watching you

    -June 1, 2001, Microsoft CEO Steve Ballmer: "Linux is a cancer that attaches itself in an intellectual property sense to everything it touches."

  7. #137
    Senior Member BigMac's Avatar
    Join Date
    Jan 2008
    Posts
    213

    Default

    Dr_Green i wanted to ask you if you tried carwhisperer yet?

    I installed it the other night and tested it with my usb dongle but i dont have a bluetooth phone or head set... I tested the tools out and it seems vary simple...

  8. #138
    Good friend of the forums williamc's Avatar
    Join Date
    Feb 2010
    Location
    Chico CA
    Posts
    285

    Default

    Trying out your findings. Here's what I've found and where I'm stuck:

    I have three Bluetooth adaptors. One is internal to the laptop (hci0), one is my Dlink sniffer (hci1), and one is my Linksys BT100 (hci2).
    Code:
     hci0:   Type: USB
            BD Address: 00:1E:37:5A:F4:5B ACL MTU: 310:10 SCO MTU: 64:8
            UP RUNNING PSCAN
            RX bytes:24562 acl:113 sco:0 events:656 errors:0
            TX bytes:8863 acl:119 sco:0 commands:289 errors:0
    
    hci1:   Type: USB
            BD Address: 00:17:9A:2B:86:11 ACL MTU: 0:0 SCO MTU: 0:0
            UP RUNNING RAW
            RX bytes:186 acl:0 sco:0 events:0 errors:0
            TX bytes:129 acl:0 sco:0 commands:18 errors:0
    
    hci2:   Type: USB
            BD Address: 00:18:F8:89:8F:34 ACL MTU: 377:10 SCO MTU: 64:8
            UP RUNNING PSCAN
            RX bytes:21417 acl:89 sco:0 events:482 errors:0
            TX bytes:7920 acl:95 sco:0 commands:244 errors:0
    I followed your original posts to configure the devices. Now, I'm working on your video for sniffing with Bluesmash. I get to this point and appear to have an error:
    Code:
     Enter device name eg hci0.....:  hci1
    Use Timer ? y/n:  y
    Use Filter ? y/n:  n
    Ignore packet type? y/n:  n
    Ignore zero length packets? y/n:  y
    Own pin? y/n:  y
    Scanning for devices.......
    Blue|Smash found 00:1C:43:81:27:BC - SGH-A707
    Enter the Master's MAC....:00:1E:37:5A:F4:5B
    Enter the Slaves's MAC....:00:1C:43:81:27:BC
    csr_sniffer: hci_send_req(): Connection timed out
    csr_sniffer: hci_send_req(): Connection timed out
    Launching Sniffer :p
    hcidump's log will be stored in 00:1E:37:5A:F4:5B@00:1C:43:81:27:BC.cap
    Continuing on, I get errors:
    Code:
     bt ~ # attest 00:1C:43:81:27:BC 3
    Connecting to 00:1C:43:81:27:BC on channel 3
    Can't connect: Permission denied (13)
    Log file is empty too. Any ideas? Thanks!

    William

  9. #139
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    3

    Default

    Can someone explain to me why i get "Cannot open '/dev/rfcomm0': Connection refused" message at the end?


    bt ~ # hciconfig hci0 up
    bt ~ # hciconfig -a
    hci0: Type: USB
    BD Address: AA:AA:AA:AA:AA:AA ACL MTU: 678:8 SCO MTU: 48:10
    UP RUNNING
    RX bytes:85 acl:0 sco:0 events:9 errors:0
    TX bytes:33 acl:0 sco:0 commands:9 errors:0
    Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy:
    Link mode: SLAVE ACCEPT
    Name: 'ISSCBTA'
    Class: 0x000000
    Service Classes: Unspecified
    Device Class: Miscellaneous,
    HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP Subver: 0x1fe
    Manufacturer: Integrated System Solution Corp. (57)

    bt ~ # hcitool scan hci0
    Scanning ...
    00:11:22:33:44:55 K750i
    bt ~ # sdptool browse 00:11:22:33:44:55
    Browsing 00:11:22:33:44:55 ...
    Service Description: Sony Ericsson K750
    Service RecHandle: 0x10000
    Service Class ID List:
    "PnP Information" (0x1200)

    Service Name: Dial-up Networking
    Service RecHandle: 0x10001
    Service Class ID List:
    "Dialup Networking" (0x1103)
    "Generic Networking" (0x1201)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 1
    Profile Descriptor List:
    "Dialup Networking" (0x1103)
    Version: 0x0100

    Service Name: Serial Port
    Service RecHandle: 0x10002
    Service Class ID List:
    "Serial Port" (0x1101)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 2

    Service Name: HF Voice Gateway
    Service RecHandle: 0x10003
    Service Class ID List:
    "Handfree Audio Gateway" (0x111f)
    "Generic Audio" (0x1203)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 3
    Profile Descriptor List:
    "Handsfree" (0x111e)
    Version: 0x0101

    Service Name: HS Voice Gateway
    Service RecHandle: 0x10004
    Service Class ID List:
    "Headset Audio Gateway" (0x1112)
    "Generic Audio" (0x1203)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 4
    Profile Descriptor List:
    "Headset" (0x1108)
    Version: 0x0100

    Service Name: OBEX Object Push
    Service RecHandle: 0x10005
    Service Class ID List:
    "OBEX Object Push" (0x1105)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 5
    "OBEX" (0x0008)
    Profile Descriptor List:
    "OBEX Object Push" (0x1105)
    Version: 0x0100

    Service Name: OBEX File Transfer
    Service RecHandle: 0x10006
    Service Class ID List:
    "OBEX File Transfer" (0x1106)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 6
    "OBEX" (0x0008)
    Profile Descriptor List:
    "OBEX File Transfer" (0x1106)
    Version: 0x0100

    Service Name: OBEX SyncML Client
    Service RecHandle: 0x10007
    Service Class ID List:
    UUID 128: 00000002-0000-1000-8000-0002ee000002
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 7
    "OBEX" (0x0008)

    Service Name: OBEX IrMC Sync Server
    Service RecHandle: 0x10008
    Service Class ID List:
    "IrMC Sync" (0x1104)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 8
    "OBEX" (0x0008)
    Profile Descriptor List:
    "IrMC Sync" (0x1104)
    Version: 0x0100

    Service Name: Mouse & Keyboard
    Service Description: Remote Control
    Service Provider: Sony Ericsson
    Service RecHandle: 0x10009
    Service Class ID List:
    "Human Interface Device" (0x1124)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    PSM: 17
    "HIDP" (0x0011)
    Language Base Attr List:
    code_ISO639: 0x656e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Human Interface Device" (0x1124)
    Version: 0x0100

    bt ~ # bash /etc/rc.d/rc.bluetooth restart
    Stopping Bluetooth subsystem: pand dund rfcomm hidd sdpd hcid.
    Starting Bluetooth subsystem: hcid passkeys.
    bt ~ # mknod -m 666 /dev/rfcomm0 c 216 1
    bt ~ # mknod -m 666 /dev/rfcomm1 c 216 6
    bt ~ # mknod -m 666 /dev/rfcomm2 c 216 5
    bt ~ # sdptool add --channel=1 DUN
    bt ~ # sdptool add --channel=6 FTP
    bt ~ # sdptool add --channel=5 OPUSH
    bt ~ # hcitool scan hci0
    Scanning ...
    00:11:22:33:44:55 K750i
    bt ~ # bluebugger -m as -a 00:11:22:33:44:55 phonebook

    bluebugger 0.1 ( MaJoMu | w ww.codito.de )
    -----------------------------------------

    Target Device: '00:11:22:33:44:55'
    Target Name: 'K750i'

    Cannot open '/dev/rfcomm0': Connection refused


    I have changed the /etc/bluetooth/hcid.conf with that:

    #
    # HCI daemon configuration file.
    #

    # HCId options
    options {
    # Automatically initialize new devices
    autoinit yes;

    # Security Manager mode
    # none - Security manager disabled
    # auto - Use local PIN for incoming connections
    # user - Always ask user for a PIN
    #
    security auto;

    # Pairing mode
    # none - Pairing disabled
    # multi - Allow pairing with already paired devices
    # once - Pair once and deny successive attempts
    pairing multi;

    # Default PIN code for incoming connections
    passkey "1234";
    }

    # Default settings for HCI devices
    device {
    # Local device name
    # %d - device id
    # %h - host name
    name "device1";

    # Local device class
    class 0x000000;

    # Default packet type
    #pkt_type DH1,DM1,HV1;

    # Inquiry and Page scan
    iscan enable; pscan enable;

    # Default link mode
    # none - no specific policy
    # accept - always accept incoming connections
    # master - become master on incoming connections,
    # deny role switch on outgoing connections
    lm accept,master;

    # Default link policy
    # none - no specific policy
    # rswitch - allow role switch
    # hold - allow hold mode
    # sniff - allow sniff mode
    # park - allow park mode
    lp rswitch,hold,sniff,park;
    auth enable;
    encrypt enable;
    }

  10. #140
    Junior Member
    Join Date
    Feb 2008
    Posts
    33

    Unhappy hi

    hi i was trying to do bluetooth hack my own phone but when i get to this part that you put in etc/bluetooth/hcid.conf it said permetion denied can you tell me why


    bt ~ # hciconfig hci0 up
    bt ~ # hciconfig -a
    hci0: Type: USB
    BD Address: 00:1C:26:E1:FB:60 ACL MTU: 1017:8 SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:3610 acl:11 sco:0 events:72 errors:0
    TX bytes:558 acl:7 sco:0 commands:29 errors:0
    Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF PARK
    Link mode: SLAVE ACCEPT
    Name: 'backtrack (0)'
    Class: 0x84010c
    Service Classes: Rendering, Information
    Device Class: Computer, Laptop
    HCI Ver: 2.0 (0x3) HCI Rev: 0x213b LMP Ver: 2.0 (0x3) LMP Subver: 0x41d3
    Manufacturer: Broadcom Corporation (15)

    bt ~ # hcitool scan hci0
    Scanning ...
    00:1B:EE:39:E6:2E Trixiesmom
    00:1E:E2:30:72:F9 John. Is awesome.
    00:1F:00:B4:0C:39 Mahabad jino
    bt ~ # sdptool browse 00:1F:00:B4:0C:39
    Browsing 00:1F:00:B4:0C:39 ...
    Service Name: AVRCP Target
    Service Description: Audio Video Remote Control
    Service Provider: Symbian Software Ltd.
    Service RecHandle: 0x10000
    Service Class ID List:
    "AV Remote Target" (0x110c)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    PSM: 23
    "AVCTP" (0x0017)
    uint16: 0x100
    Profile Descriptor List:
    "AV Remote" (0x110e)
    Version: 0x0100

    Service RecHandle: 0x10001
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 1

    Service Name: Dial-Up Networking
    Service RecHandle: 0x10002
    Service Class ID List:
    "Dialup Networking" (0x1103)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 2
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Dialup Networking" (0x1103)
    Version: 0x0100

    Service Name: OBEX Object Push
    Service RecHandle: 0x10003
    Service Class ID List:
    "OBEX Object Push" (0x1105)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 9
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "OBEX Object Push" (0x1105)
    Version: 0x0100

    Service Name: Imaging
    Service RecHandle: 0x10005
    Service Class ID List:
    "Imaging Responder" (0x111b)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 15
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Imaging" (0x111a)
    Version: 0x0100

    Service Name: Audio Source
    Service RecHandle: 0x10007
    Service Class ID List:
    "Audio Source" (0x110a)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    PSM: 25
    "AVDTP" (0x0019)
    uint16: 0x100
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Advanced Audio" (0x110d)
    Version: 0x0100

    Service Name: Hands-Free Audio Gateway
    Service RecHandle: 0x10008
    Service Class ID List:
    "Handfree Audio Gateway" (0x111f)
    "Generic Audio" (0x1203)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 3
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Handsfree" (0x111e)
    Version: 0x0105

    Service Name: Headset Audio Gateway
    Service RecHandle: 0x10009
    Service Class ID List:
    "Headset Audio Gateway" (0x1112)
    "Generic Audio" (0x1203)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 4
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "Headset" (0x1108)
    Version: 0x0100

    Service Name: SyncMLClient
    Service RecHandle: 0x1000b
    Service Class ID List:
    UUID 128: 00000002-0000-1000-8000-0002ee000002
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 10
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "" (0x00000002-0000-1000-8000-0002ee000002)
    Version: 0x0100

    Service Name: OBEX File Transfer
    Service RecHandle: 0x1000c
    Service Class ID List:
    "OBEX File Transfer" (0x1106)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 11
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "OBEX File Transfer" (0x1106)
    Version: 0x0100

    Service Name: Nokia OBEX PC Suite Services
    Service RecHandle: 0x1000d
    Service Class ID List:
    UUID 128: 00005005-0000-1000-8000-0002ee000001
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 12
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "" (0x00005005-0000-1000-8000-0002ee000001)
    Version: 0x0100

    Service Name: SyncML DM Client
    Service RecHandle: 0x1000e
    Service Class ID List:
    UUID 128: 00000004-0000-1000-8000-0002ee000002
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 13
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "" (0x00000004-0000-1000-8000-0002ee000002)
    Version: 0x0100

    Service Name: Nokia SyncML Server
    Service RecHandle: 0x10010
    Service Class ID List:
    UUID 128: 00005601-0000-1000-8000-0002ee000001
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 14
    "OBEX" (0x0008)
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "" (0x00005601-0000-1000-8000-0002ee000001)
    Version: 0x0100

    Service Name: SIM Access
    Service RecHandle: 0x10011
    Service Class ID List:
    "SIM Access" (0x112d)
    "Generic Telephony" (0x1204)
    Protocol Descriptor List:
    "L2CAP" (0x0100)
    "RFCOMM" (0x0003)
    Channel: 8
    Language Base Attr List:
    code_ISO639: 0x454e
    encoding: 0x6a
    base_offset: 0x100
    Profile Descriptor List:
    "SIM Access" (0x112d)
    Version: 0x0101

    bt ~ # /etc/bluetooth/hcid.conf
    -bash: /etc/bluetooth/hcid.conf: Permission denied

Page 14 of 20 FirstFirst ... 41213141516 ... LastLast

Posting Permissions

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