when i try to connect to a bluetooth module through command line using " rfcomm connect 0 <address> 01 "
i get the error: " cant connect RFCOMM socket : connection failed"
i want to send serial data from pc.
Can anyone please help me with this.
Thanks,
Lavanya
Related
i have a chinese tablet and do not know its name
specs are
330 mb ram
allwinner a10 cortex a8 1.2 ghz
mali 400
android 2.3.4
kernel 2.6.36
it does not have slot for sim card
questions
1) it does not have default tethering option which is present under most android fones in wireless > tehering how to get this
2) i do not have wifi so need to reverse tether it
i think my tablet is rooted since i am able to install and use root explorer and also titanium backup says root access ok
and i followed this guide for reverse tethering
http://forum.xda-developers.com/showthread.php?t=1371345
it connected succesfullly all steps but still unable to load web pages. it says ok in log to all 9 steps . but in opera and firefox the web page does not load.
i wanted to post this in that thread but i cannot do that
please help
thanks
here are the logs for v 2.17
Connecting to device. This may take a few seconds
Step 1 : Check if a device is connected
adb.exe -s 20080411 devices
List of devices attached
20080411 device
Ok
Step 2 : Checking android package
Installed package version : 2.17
Current package version : 2.17
Ok
Step 3 : Check if usb port is available
Error : port not available
Step 4 : Prepare connection (Adb Forward)
Ok
Step 4 bis : Check again if usb port is available
Ok
Step 5 : Start android service
Ok
Step 6 : Ensure connection is closed before open it
Ok
Step 7 : Connect to android
Ok
Step 8 : Check android connection
Waiting for response. If nothing happens now, close the program and retry
Check connection 1 ok
Check connection 2 ok
Step 9 : Send init to android service
Ok
Step 10 : Send scripts
Ok
Step 11 : Start script1
Ok
Step 12 : Send port forwarding
Ok
Connection is done
CheckConnection : send done 2
UdpRelay : waiting on port 42004
-----------------script : Start before port-----
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -A INPUT -p icmp -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -A OUTPUT -p icmp -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -t nat -A INPUT -p icmp -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -t nat -A OUTPUT -p icmp -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -t nat -A TETHER -p icmp -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/iptables_armv5 -t nat -A TETHER -j LOG --log-uid --log-level debug --log-prefix "MYPREROUTING " --log-ip-options
iptables: No chain/target/match by that name.
Error running command :
/data/data/service.tracetool/app_bin/busybox19 ifconfig usb0 up
ifconfig: SIOCGIFFLAGS: No such device
Error running command :
/data/data/service.tracetool/app_bin/busybox19 ifconfig usb0 192.168.1.2 netmask 255.255.255.0
ifconfig: SIOCSIFADDR: No such device
Error running command :
/data/data/service.tracetool/app_bin/busybox19 route add default gateway 192.168.1.2
route: SIOCADDRT: Network is unreachable
--------- Script : start after opening ports
forward output to tether ok
Click to expand...
Click to collapse
please guys help me
at least tell me how to get the default usb tethering option in my tablet
please
Try EasyTether app. Available on market and computer needs drivers installed.
sent from xda premium on an Incredible S
easy tether app did not work for reverse tehering
my kernel does not support wired tether option . please tell how to add this feature into my kernel 2.6.36
rishabh63 said:
my kernel does not support wired tether option . please tell how to add this feature into my kernel 2.6.36
Click to expand...
Click to collapse
It's a kernel problem.
You have to search the web for kernel specific to your device.
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
I want to fix my bricked Nook (8g), in order to fix it I loaded cwm into a microsd card and my plan was getting adb to work while the Nook is in cwm recovery. The problem here is that my pc (Debian Wheezy) doesn't seem very happy with the tablet and I couldn't get it recognized.
Using Android SDK Manager I got the following in the usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
Click to expand...
Click to collapse
worth saying (probably), I also edited /etc/udev/rules.d/51-android.rules as follows:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_fastboot"
Click to expand...
Click to collapse
When I finished doing that and still didn't work, I looked up what happens when I plug the tablet into the usb port,
[ 9634.796053] usb 2-9: new full-speed USB device number 39 using ohci_hcd
[ 9634.980037] usb 2-9: device descriptor read/64, error -62
[ 9635.268035] usb 2-9: device descriptor read/64, error -62
[ 9635.548038] usb 2-9: new full-speed USB device number 40 using ohci_hcd
[ 9635.732041] usb 2-9: device descriptor read/64, error -62
[ 9636.020041] usb 2-9: device descriptor read/64, error -62
Click to expand...
Click to collapse
so this seems to be the error. Is it possible to fix it? I tried a few things I found (like killing the usb services and start them again) but you can tell it wasn't exactly successful. Is there anything I can try?
You might want to consider the unbrick method described at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/.
I'm having some trouble backing up the NVRAM partition on my new gemini. I downloaded the latest SP Tool build and modified the udev rules according to the wiki, however when I hit 'Read Back' in the tool and restart my gemini its boot hangs and I get the following output from SPFT:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1554179156.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_PROTOCOL_ERR
Disconnect!
BROM Exception! ( ERROR : STATUS_PROTOCOL_ERR (-1073676283) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../SP-Flash-Tool-src/Conn/Connection.cpp,131))
I haven't found this error code in any of the SPFT docs I've found; can anyone help?
Thanks!
dopaminejunky said:
I'm having some trouble backing up the NVRAM partition on my new gemini. I downloaded the latest SP Tool build and modified the udev rules according to the wiki, however when I hit 'Read Back' in the tool and restart my gemini its boot hangs and I get the following output from SPFT:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1554179156.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_PROTOCOL_ERR
Disconnect!
BROM Exception! ( ERROR : STATUS_PROTOCOL_ERR (-1073676283) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../SP-Flash-Tool-src/Conn/Connection.cpp,131))
I haven't found this error code in any of the SPFT docs I've found; can anyone help?
Thanks!
Click to expand...
Click to collapse
Hey, I get similar errors when trying to perform any action related to the preloader in Linux, Just described the issue here: https://www.oesf.org/forum/index.php?showtopic=35999
Also looking for a solution, and will follow this tread.
Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar