ok, i got all the fastboot stuff down, and installed everything, but on command prompt, i type in "fastboot devices", and nothing pops out!!!! also (if this helps any) in device manager (for windows xp) under adb interfaces it is listed as
"htc bootloader". isnt it suppose to be "htc dream"?
oh, and using sdk_r3 if that helps any
Related
Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
oceanisbleu said:
for about 4 days now I've been trying to get ADB to work on my phone following these instructions;
http://forum.xda-developers.com/showthread.php?t=858118&highlight=adb
I've tried everything and so far I can't get past "adb devices" when I do so I get the message "adb is not recognized as an internal or external command"
what exactly am I doing wrong and how do I fix it? I've installed JDK & downloaded the android SDK package, in device manager the phone is recognize as "Android ADB interface"
I'm ready to chuck this phone against the wall at this point
Click to expand...
Click to collapse
Double check your path...
"Now type cd\AndroidSDK\tools\"
My path is c:\android-sdk-windows\tools\
I've renamed the file to AndroidSDK & placed it directly in C:/ so for me it's C:/ AndroidSDK/tools/
doesn't work...
-I plug the phone in and it's recognized as "Android ADB Interface" in device manager
-I open easy tether on the phone then right click on the pc & click connect then it says connection established via Android ADB.....
-I open CMD
-I type cd\
-then cd\AndroidSDK\tools\
-then adb devices & this is where I want to break everything because I can never get past this part and all I see is 'adb' is not recognized as an internal or external command.......
I hate this phone lol & wish I had the money to get the evo so I can put this thing in the trash, I just want to setup firerat's and that's the main reason why I want to establish ADB, is there any way it can be done without ADB????
thanks for trying to help, I hope someone can still figure this out for me
If you downloaded the newest SDK, then the problem might be that you are looking for adb in the wrong directory. It is no longer located in \tools. It was moved to the \platform-tools directory
Sent from my HERO CDMA using xda premium
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
In the morning I'll give a more detailed instructions, but you need to add the platform-tools folder to your PATH.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
I have just added this exact directory to the end of my PATH
;C:\AndroidSDK\platform-tools\
rebooted, opened cmd, typed adb devices and still I get ADB is not a recognized command.
I went to HTC's site & downloaded the latest hero sync software (new version just came out 2 days ago) when I plugged my phone in it re-installed the drivers, tried it again and nothing!!
I did notice that after the HTC Sync installation in device manager the phone is no longer Android ADB Device, now it says MY HTC, did Sync ruin my ADB drivers?
Ok. So were you at with this???
Shoot me a pm if you still need assistance.
Edit: From reading your post I think your not changing the directory first.
So open up the cmd window. And type cd\ "then hit enter"
Thenn type.
cd\AndroidSDK\platform-tools\
And hit enter.
Then type. "adb devices" without the quotes. And see if that will show your serial number.
If that yeilds no results then try
cd\android\SDK\tools\
And hit enter.
Then type "adb devices" without the quotes. And hit enter and see if that will return your serial number.
Locked & Loaded
" Shooter on Deck"
Thanks guys for all the help you have provided, I have finally figured it out using this guide;
http://forum.xda-developers.com/showthread.php?t=532719
slightly different than the first guide I followed, instead of editing the PATH a new Environment Variable was created also a slightly different CMD code to get to ADB;
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
I hope this helps anyone else who might have the same issue.
Hello
I am trying to unlock my bootloader according to the instructions on htcdev.com, when I reach the stage where I have to execute the 'fastboot oem get_identifier_token' command I run into trouble, namely I see the following '...' and then the command hangs.
I have since established the device is visible to fastboot, when I run 'fastboot devices' I get the following, the output remains constant when I run the command with or without superuser privileges (I'm using Arch Linux).
Code:
HT338W902280 fastboot
As far as I can tell it seems my device is recognised by my laptop but that the commands being issued to it via fastboot aren't being received/executed, a conclusion further confirmed by the fact that when I run 'fastboot getvar all' the command hangs with no output being returned whatsoever.
I've tried running the commands as a normal user and as Su and in a couple of different terminals but the end results are identical. If anyone could suggest a solution or needs further information to help I'd be delighted to hear from you.
Thanks in advance!
Hey Guys any1 knows the fastboot commands for booting Device into recovery Mode and checking connected Devices?
Help would be nice, need to know
Thx Advanced
Function: Check connection and get basic information about devices connected to the computer.
"adb devices"
"fastboot devices" - This is essentially the same command as adb devices above. However, it works in the bootloader, which ADB does not.
Function: Reboot your phone into recovery mode.
"adb reboot recovery"
Obviously without the speech marks.
Someone please.help...
tott2003 said:
Someone please.help...
Click to expand...
Click to collapse
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use . before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with . in the beginning.
Click to expand...
Click to collapse
Cheers mate ?
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Click to expand...
Click to collapse
HOLY. ****ING. ****.
I have spent the past two days trying to figure this out. Not *one* other person on the internet, so much as I have seen, has mentioned using the side port. Seriously, you just made my day. Thank you so much! :good:
Created a new topic, disregard