Hello! I want to connect Kindle Fire and Raspberry Pi (ARM debian) via USB.
I build adb for ARM.
Code:
[email protected]:~$ sudo adb kill-server
[email protected]:~$ sudo adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF device
Now i want to get network Raspbery <-> Kindle.
I use gedeROM but I tried other ICS's roms.
I can't find usb tethering in menu, and apps from android market did not want to work.
How can i get network Raspbery <-> Kindle via USB?
What exactly are u trying to do.I don't understand
Sent from my Galaxy Nexus using xda app-developers app
Related
I have been following the same steps that works on my Samsung S4 but I cannot get it to wotk on Nexus 7 (2013). I have also tried various applications and non of them seem to work.
Android version: 4.4.4
Build: KTU84P
Code:
☁ / adb kill-server
☁ / adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
ViperZ28 said:
I have been following the same steps that works on my Samsung S4 but I cannot get it to wotk on Nexus 7 (2013). I have also tried various applications and non of them seem to work.
Android version: 4.4.4
Build: KTU84P
Code:
[emoji297] / adb kill-server
[emoji297] / adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Click to expand...
Click to collapse
Try a different cable .. Make sure that you accept the screen that says do you want to allow
Adb kill-server
Adb remount
Adb devices
Sent from my iPod touch using Tapatalk
jcbjoe said:
Try a different cable .. Make sure that you accept the screen that says do you want to allow
Adb kill-server
Adb remount
Adb devices
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I have tried several different cables, the exact same setup works on S4. I do not see the accept screen.
ViperZ28 said:
I have tried several different cables, the exact same setup works on S4. I do not see the accept screen.
Click to expand...
Click to collapse
Have you tried adb over wifi?
https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect
Sent from my SCH-I535 using XDA Free mobile app
jcbjoe said:
Have you tried adb over wifi?
https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I see in the logs
Code:
checking wireless status
changing status
adb connection max retries exceeded
adb connection max retries exceeded
I am going to go stock and see if the problem is in the rooted rom
ViperZ28 said:
Yes, I see in the logs
Code:
checking wireless status
changing status
adb connection max retries exceeded
adb connection max retries exceeded
I am going to go stock and see if the problem is in the rooted rom
Click to expand...
Click to collapse
I just flashed stock and it works fine, I will post to the custom rom thread about the issue.
Hello all. I'm trying to install xbmc to a fire tv stick. I have successfully done this with a fire tv. I don't know what's going on with the stick.
I can connect to the stick in the adbfire app and I can ping the stick via the command prompt.
I keep getting this error in the command prompt :
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
error : device not found
- waiting for device -
Any ideas?
Please help!
Thanks ahead of time!
deathcharge said:
Hello all. I'm trying to install xbmc to a fire tv stick. I have successfully done this with a fire tv. I don't know what's going on with the stick.
I can connect to the stick in the adbfire app and I can ping the stick via the command prompt.
I keep getting this error in the command prompt :
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
error : device not found
- waiting for device -
Any ideas?
Please help!
Thanks ahead of time!
Click to expand...
Click to collapse
Can you sideload other apps? It sounds like you don't have it configured right. Recheck your IP address.
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?
gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.
Hello
my android tv box is detected as android device by my pc, and it cause me problem with adb command
I've disabled usb debugging and close developpement settings but it still connected by adb via wifi
F:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
192.168.100.7:5555 device
Click to expand...
Click to collapse
can you help me please to resolve this problem please ?
Go to dev option and click on revoke.
Greetings,
I am attempting to run Tasker with AutoApps on my Note 10.
I get the following message when I run ADB from my MacBook.
adb: no devices/emulators found
I have USB Debugging enabled, and I installed Android File Transfer and also tested with Samsung Smart Switch. Both applications make successful connections with my Note 10, but I am confused as to why ADB does not detect my device. Any help is greatly appreciated.
I also ran...
/adb kill-server
./adb devices
and receive the following...
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
There is no device listed.
Any assistance would be greatly appreciated.
Did you try ./adb devices again after daemon had started?