Hi,
need some help with fastboot.
Entering "./fastboot devices" gives no results.
Streak waits with white screen and displays FASTBOOT_MODE.
I did not install the SDK, but took the adb tool from the current SDK.
Entering "./adb devices" list one device - works!
I noticed that it is important to use the adb from the current SDK currently adb version 1.0.26 (an old adb version 1.0.25 did not work).
Streak with Stock Froyo
Linux / Ubuntu 10.04
Streak is recognized as (lsub): Bus 001 Device 011: ID 413c:b007 Dell Computer Corp.
Any idea? Are there different fastboot-binaries out there? All the ones I have found are 127435 bytes.
Thanks a lot
Arnd
I have exactly the same problem on ubuntu 10.04 with standard 2.2 Froyo.
adb devices shows the Streak but fastboot devices shows nothing. I have played with this for a while without success. I would love to have this working any help would be appreciated. I am using android-sdk-r07-linux_x86.tgz and fastboot 130.4 kb.
The streak is detected on USB and I can turn on and access USB storage.
Solved
Just found out, "./fastboot devices" simply does not work - unfortunate.
But try "sudo ./fastboot -i 0x413c reboot" - this will show "rebooting..." and actually reboot the device. Must be with sudo.
That means fastboot works.
I suppose, no need to install the SDK, no need to put any rules files into /etc/udev/rules.d
Arnd
Related
Why am I getting the following?
I'm trying to run the 32B Hero (pure black) ROM Runme.bat and it is erroring because it is seeing multiple devices?
C:\android\tools>adb devices
List of devices attached
XXXXXXXXXXX offline
XXXXXXXXXXX offline
XXXXXXXXXXX device
Click to expand...
Click to collapse
At least yours see's some devices..... Mine won't recognise anything!
Roy_Drage said:
At least yours see's some devices..... Mine won't recognise anything!
Click to expand...
Click to collapse
Be sure you have the lastest USB Driver found in SDK's folder installed..
Well if you are playing with the emulator, more devices will show up. To select a specific device you have to run it with -s SERIALNUMBER like:
Code:
adb -s 123ASDQW111 shell
dev kit USB driver is loaded.
Not aware that I am playing with the emulator? I'm not, at least I don't think I am?
easiest way to resolve this is to issue two commands in the command prompt
adb kill-server
adb devices
this should restart the adb service and only show one device, at least this worked for me when I had this problem, good luck
thanks man that helped alot!!!!!!!
I was going to reflash my rom and start all over!!!!!!
after installing rom bootloader loop
I finally was able to sideload a ROM after wipe out my OS, then installed a android revolution rom seems ok but when I restarted after showing a few seconds htc logo reboot and goes to recovery menu, what should I do? please help
i'm trying to create a gold card for my MyTouch 3G and i'm following the instructions from www.theunlockr.com
i am running Windows 7 RC1 64-bit and have installed the 64 bit usb driver from "android-sdk-windows-1.5_r3"
i executed the following step:
Type the following into the command dos prompt on the computer (the black screen with white letters that just opened) while the phone is connected through USB, hitting enter at the end of the line:
cd\
cd androidsdk\tools\
fastboot devices
i verified that it worked as it showed my serial number XXXXXXXXXXXX fastboot
proceeding ahead, i got to the step where i had to execute the following command:
cd\
cd\AndroidSDK\tools\
adb devices
it simply states "List of devices attached" and nothing more. i have verified that i checked USB debugging.
has anybody had similar issues?
i fixed the issue. d'oh!
i downloaded USBDeview and ran it as administrator. i uninstalled all htc android related drivers and unplugged the phone from the PC. then i plugged the phone back in via USB cable and windows detected & installed the drivers automatically.
afterwards, i ran the adb devices command again and it showed my device was attached.
tuffCookie said:
i'm trying to create a gold card for my MyTouch 3G and i'm following the instructions from www.theunlockr.com
i am running Windows 7 RC1 64-bit and have installed the 64 bit usb driver from "android-sdk-windows-1.5_r3"
i executed the following step:
Type the following into the command dos prompt on the computer (the black screen with white letters that just opened) while the phone is connected through USB, hitting enter at the end of the line:
cd\
cd androidsdk\tools\
fastboot devices
i verified that it worked as it showed my serial number XXXXXXXXXXXX fastboot
proceeding ahead, i got to the step where i had to execute the following command:
cd\
cd\AndroidSDK\tools\
adb devices
it simply states "List of devices attached" and nothing more. i have verified that i checked USB debugging.
has anybody had similar issues?
Click to expand...
Click to collapse
i am having the same issue with my HTC Dream
tuffCookie said:
i fixed the issue. d'oh!
i downloaded USBDeview and ran it as administrator. i uninstalled all htc android related drivers and unplugged the phone from the PC. then i plugged the phone back in via USB cable and windows detected & installed the drivers automatically.
afterwards, i ran the adb devices command again and it showed my device was attached.
Click to expand...
Click to collapse
This worked for me ... interesting how you have to Uninstall HTC drivers for an HTC device to work!
I am trying to access my phone through ADB to register w/o data. My device center and device manager both see the phone ("Android Phone" in DC, and "ADB Interface > HTC Dream" in DM). However, when I run ADB from the command line it cannot find my device. I have tried reinstalling drivers, killing and starting the ADB server, and even re-flashing my phone.
Note: When booting the phone from a fresh flash I DON'T have to enter "<enter>setprop persist.service.adb.enable 1<enter>" to initialize ADB. It is automatically seen as an ADB device, and after entering the command it is only seen as a storage device.
Thanks in advance.
(unlocking a Dream on Windows 7 x64)
Solved it by installing the drivers from here: http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
...
Is it recognized at all by your computer? If so have you tried the latest version of the toolkit?
Sounds like you have blanked the entire bootloader
WakeRider89 said:
Is it recognized at all by your computer? If so have you tried the latest version of the toolkit?
Sounds like you have blanked the entire bootloader
Click to expand...
Click to collapse
Run the following to determine if your computer can see your Nexus 10:
Code:
adb devices
fastboot devices
Both binaries are located in the platform-tools directory of your Android SDK. They will list any android devices that are connected. If your serial number shows up, then maybe it can be fixed.
If you are on Windows, check Device Manager (found in the Control Panel) for your Nexus 10. If you are on Linux (or possibly OSX), try running lsusb in a terminal.
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly