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.
Related
When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.
stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>
Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.
Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?
Details:
OS: Windows 7 (32 bit)
Kindle Fire Version: 6.3.1 (stock, unrooted, only 2 days old)
What have I done so far:
1. Installed Android SDK with platform tools and USB driver
2. Modified usb_driver info file to include kindle hardware ID
3. Installed kindle driver after connecting with factory cable (can see 'Android ADB Interface' in the device manager)
4. ## Couldn't find the adb usb ini file in C:\Users\(User_name)\.android\
This is when I decided to try the KFU
5. Unplugged factory cable. Installed drivers using add_drivers batch file in KFU
6. Checked for adb usb ini file in C:\Users\(User_name)\.android\ - it was present with the new ID added
7. Plug cable -> Wait for device to be detected - > Start > Run > cmd
8. Navigate to the KFU tools folder with adb.
9. Tried all the various ways to see if the device is detected.
Code:
adb shell
adb kill-server
adb devices
Did not detect device at all (device not found error)
10. Unplug factory cable -> restart kindle -> repeat from step 5 till 9. Still nothing
11. Unplug factory cable -> restart computer -> restart kindle -> repeat from step 5 till 9
None of this has worked. I still can't get adb to detect my device. Am I missing something?
Thanks in advance for any help. Appreciate it.
x3_voodoo_3x said:
Details:
OS: Windows 7 (32 bit)
Kindle Fire Version: 6.3.1 (stock, unrooted, only 2 days old)
What have I done so far:
1. Installed Android SDK with platform tools and USB driver
2. Modified usb_driver info file to include kindle hardware ID
3. Installed kindle driver after connecting with factory cable (can see 'Android ADB Interface' in the device manager)
4. ## Couldn't find the adb usb ini file in C:\Users\(User_name)\.android\
This is when I decided to try the KFU
5. Unplugged factory cable. Installed drivers using add_drivers batch file in KFU
6. Checked for adb usb ini file in C:\Users\(User_name)\.android\ - it was present with the new ID added
7. Plug cable -> Wait for device to be detected - > Start > Run > cmd
8. Navigate to the KFU tools folder with adb.
9. Tried all the various ways to see if the device is detected.
Code:
adb shell
adb kill-server
adb devices
Did not detect device at all (device not found error)
10. Unplug factory cable -> restart kindle -> repeat from step 5 till 9. Still nothing
11. Unplug factory cable -> restart computer -> restart kindle -> repeat from step 5 till 9
None of this has worked. I still can't get adb to detect my device. Am I missing something?
Thanks in advance for any help. Appreciate it.
Click to expand...
Click to collapse
When you say factory cable do you mean the modified USB cable that makes the kindle boot into fastboot mode if that is the case adb will not see the device
Sent from my Galaxy Nexus using xda premium
ztkryan said:
When you say factory cable do you mean the modified USB cable that makes the kindle boot into fastboot mode if that is the case adb will not see the device
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You mean I should try it with a normal micro usb cable?
Sigh. I did not see this in any of the threads. Let me go try it first thing.
Thank you very much.
x3_voodoo_3x said:
You mean I should try it with a normal micro usb cable?
Sigh. I did not see this in any of the threads. Let me go try it first thing.
Thank you very much.
Click to expand...
Click to collapse
Factory cable enables fastboot mode... fastboot and adb are mutually exclusive.
Similar to "adb devices", you can try "fastboot getvar product" to see if the KF is found.
Do keep in mind fastboot mode changes the hardware ID and thus needs to have drivers installed for it as well, if you haven't already.
Dasanko said:
Factory cable enables fastboot mode... fastboot and adb are mutually exclusive.
Similar to "adb devices", you can try "fastboot getvar product" to see if the KF is found.
Do keep in mind fastboot mode changes the hardware ID and thus needs to have drivers installed for it as well, if you haven't already.
Click to expand...
Click to collapse
That didn't help either.
Tried with a normal cable. Neither fastboot nor adb nor the KFU would work although I have the drivers installed and have done everything else to root, as described in my first post.
My plan of action now is to try it on another computer. Fresh start with KFU alone.
Will update about how that goes. Have a bad feeling though.
x3_voodoo_3x said:
My plan of action now is to try it on another computer. Fresh start with KFU alone.
Click to expand...
Click to collapse
Run install_drivers.bat before you plug in the KF for the first time, should help.
Dasanko said:
Run install_drivers.bat before you plug in the KF for the first time, should help.
Click to expand...
Click to collapse
It worked in a new computer when I ran the install_drivers.bat file first.
Thanks all for helping. Appreciate it.
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)
I want to unlock and root my N7 LTE but adb and fastboot are not working, I enabled developer options and usb debugging, fastboot and adb work fine with my HTC One. I tried several cables.
My system: win8.1 64 bit (usb 2)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
SH34EW901467 device
edit: it also tried on a win7 64 bit, as ptp, mtp and none and it still doesn't show up
godutch said:
I want to unlock and root my N7 LTE but adb and fastboot are not working, I enabled developer options and usb debugging, fastboot and adb work fine with my HTC One. I tried several cables.
My system: win8.1 64 bit (usb 2)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
SH34EW901467 device
edit: it also tried on a win7 64 bit, as ptp, mtp and none and it still doesn't show up
Click to expand...
Click to collapse
found a solution, I googled for the device hardwareid and found the universal adb drivers, installed these and now adb and fastboot work
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Abrucci said:
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Click to expand...
Click to collapse
How does it show in Device manager?
sd_shadow said:
How does it show in Device manager?
Click to expand...
Click to collapse
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Abrucci said:
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Click to expand...
Click to collapse
Try a different usb cable