Hi
My adb doesn't work.I do the following:
*downloaded android-sdk-windows.zip and extracted to E:\
*Edited my PATH variables:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;E:\android-sdk-windows\tools
*restart my pc
*connected my phone in usb debugging mode.
*ind cmd typed cd: e:\android-sdk-windows\tools
*then "adb devices"
Says "adb devices" not recognized as internal of external command.
What i do wrong? Please help me!
1. Linux(easy)
2. Mac(easy)
3. Windows(medium)
________________________________________________________
1. Linux
You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot linux binary
http://www.mediafire.com/?ldlovlzi9mx3pbh
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it?
Copy this file to /etc/udev/rules.d
EDIT:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Easy?
______________________________________________________________
2. Mac
I don't have Mac, but it should be like for linux:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot Mac binary:
http://www.mediafire.com/?kjozh1q5dyyqhn3
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
(I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it? Easy?
______________________________________________________________
3. Windows
1. Download SDK
http://developer.android.com/sdk/index.html
2. Download Google USB Drivers from SDK Manager
3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
(Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
5. Open CMD from Start>Run and type:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
6. Reboot
==========================================================
7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
10. Choose to view all devices and click Have Disk
11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
13. Once the drivers have been installed, you should be able to use ADB with your device
14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB
That's it, if you have some complaints, post them.
Bye!!!
EDIT: Changed android_winusb.inf file due error in it.
EDIT2:Changed android_winusb.inf file due error in it again.
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
shut the cmd say something ? because when i write the command and push enter its just jump to another line and says nothing ???
No. You can go to that file("%USERPROFILE%\.android\adb_usb.ini") and manualy add 0x955 to it.
Sorry!
I cannot connect to this link:http://www.mediafire.com/?kjozh1q5dyyqhn3
Please do me a favor, send fastboot as an attachment to this mail address:
[email protected]
I'll try because I'm not at home, I went to my grand parents and I have really slow internet.
Hello guys I have a problem, the step 5. Open CMD from Start> Run and type:
echo 0x955>> "% USERPROFILE% \. Android \ adb_usb.ini"
I run this step but I open a txt file that says this:
Android # USB Vendor ID 3RD PARTY LIST - DO NOT EDIT.
# USE 'adb Android update' TO GENERATE.
USB Vendor ID # 1 FOR LINE.
0x955
I now do not understand where I write echo 0x955?
/documents_and_settings/[your user name]/.Android(hidden file)/adb_usb.ini
Sent from my Xoom using Tapatalk
Nice guide. Think you forgot the udev rule for Linux:
Create a file called /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
Without that Linux won't give you write permission to the device.
Ok, I'll add.
Sent from my IDEOS S7 Slim using XDA App
So when I want to use fastboot, I install the Android Bootloader Interface driver? Not the ADB interface driver?
Needless to say I haven't got fastboot working yet but ADB works. One other thing: If I manage to install a firmware and do a wipe and everything works; can it be that I would experiance better performance if I as well managed to to a full wipe with fastboot? I mean, can it flush things that CWM can't? I'm using the latest cyanogenmod (test version) from DerArtem, but I am a bit interested in trying the latest progress of honeycomb...
I have problems with interfaces. On one computer is ADB interface and on other is something else but I prefer linux for doing any job that's connected with android. In theory wiping should be same with fastboot and recovery but, again, I prefer fastboot because it's JUST erase all on data/cache/system partition and recovery might don't have support for other partition types as well as other problems, but I don't say that it can be different.
Thanks. I hope I continue to have a functioning cwm. If it breaks I will have to install Linux
ı do everything but when ı wrote adb devices nothing
Linux or Windows?
Jon2555 said:
Linux or Windows?
Click to expand...
Click to collapse
windows 7 x64
When the tablet is open in USB Debugging mode I can see my device adb devices list but when ı restart my tablet fastboot mode ı can't find
The best slow to install Linux via VM. It complicated on windows, it's different from computer to computer.
Sent from my IDEOS S7 Slim using XDA App
do i type this exactly with all the " ???
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
????????????????/
HELP PLEASE
No
Sent from my IDEOS S7 Slim using XDA App
When i tipe the echo 0x955 line
It keeps on saying that system cannot find the path specified
can someone please help?
even when i open comand prompt and type adb it says adb is not recognised as an internal or external.........
Hello,
I just find out why I cannot use adb... AS100 have different VID/PID, so the usb driver just won't install in Windows.
Code:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01
I've edited android_winusb.inf and repacked a toolkit that should work for both AS100 and folio.
The file size is (slightly) larger than 8MB,so I uploaded it to mediafire:
http://www.mediafire.com/?44gzifauee07u9j
Including adb usb driver, fastboot and adb command.
---
Use fastboot:
boot your toshiba AS100/folio
when you see toshiba logo, press power 3 times and vol+ 1 time to enter fastboot mode.
you should see "Starting Fastboot USB download protocol..." on screen.
connect tablet to PC with USB.
install usb driver in Windows.
open cmd console in Windows
cd to where you put the tools folder, e.g. cd D:\toshiba\folio-toolkit\tools
run "fastboot devices" (without quotes)
if you see "? fastboot" in console, the tablet is connected and you can use fastboot to flash images.
(run "fastboot help" to see a list of usable commands)
---
Use adb:
boot your toshiba AS100/folio into android.
make sure usb debug option is checked.
connect tablet to PC with USB.
install usb driver in Windows.
open cmd console in Windows.
cd to where you put the tools folder, e.g. cd D:\toshiba\folio-toolkit\tools
run "adb start-server" (without quotes)
run "adb devices"
you should see the following in Console:
Code:
List of devices attached
0123456789ABCDEF device
(run "adb help" to see a list of usable commands)
---
Adb troubleshooting:
If you see "0123456789ABCDEF offline" when you run adb devices, try the following:
Code:
adb kill-server
adb start-server
If it still not works, try reboot the tablet again when connected with USB.
---
About AS100: basically it's as same as folio 100, with 1GB on board RAM.
totally lost
Sorry guys, Im totally lost, trying to fastboot my folio and was gonna install a fresh rom. I need thorough instuctions. Not all of us are wizkids, for example, its not enough for me to just write "do this" or "do that", i need to know HOW to do things, like my name says, Im a noobie
Come on you guys, help the clueless ppl
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Same Thing
Hi mjamsek,
I have exactly the same experience as you. I cannot enter the fastboot mode since unlocking/rooting my tf201. Did you solve the problem. ANY help is greatly appreciated!
mjamsek said:
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Click to expand...
Click to collapse
I'm having this exact issue except I used Kingo to root instead of Motochopper. I also tried all of the above to fix it, nothing yet.
@mjamsek
Hey it is not going to fix your issue but, you cant run adb commands in fastboot....
So it should look more like this.....
Code:
fastboot reboot-bootloader
What is your bootloader version ?
Maybe try this as long as you are on a bootloader that ends in 2.17 or 2.18
type this
Code:
fastboot erase recovery
then reboot bootloader
then flash a CWM recovery
then reboot-bootloader
then flash TWRP....
Try that and tell me where it gets you...
Thx Josh
I have a similar issue, I will try your cmd lj50036
Exactly the same issue there...
Device rooted and unlocked. Recovery flashed ( CMW), but unable to entered on....
Good evening!
Today I was a little bored, so I created simple ADB & Fastboot command line procesor.
I'm not really sure that this application is practical.
Description
You don't need to type "adb" or "fastboot" everytime. If CLP shows "ADB >> ", then type command you want to run, for example "shell ls /data/app".
I have no time for descripting this app, just use it and check out.
Works only with Windows.
SourceForge project page: sourceforge.net/projects/adbfastbootclp/