when typing in;
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
in cmd all is fine untill i get to "fastboot oem boot" when it says "oem" is not recognised as an internal or external command, operable progam or batch file.
Does anyone have a solution?
Are you sure it's not complaining about 'fastboot' being not recognised?
Check if you have 'fastboot.exe' in your platform-tools folder (it might be in C:\android-sdk-windows\tools) If it is in tools, just drag it into platform-tools and try again.
-Nipqer
i cant thank you enough, ive been trying this for at least 5 hours and it was a simple copy and paste job
Related
I recently replaced the fastboot.exe in my SDK folder with one I downloaded from a file called tools.zip. After that, fastboot has not worked. I deleted my entire SDK folder and reinstalled everything. I also uninstalled my drivers and it is still not working.
When I type fastboot, I get the list of commands so I know it is in the right folder.
Any help?
blowe46 said:
When I type fastboot, I get the list of commands so I know it is in the right folder.
Any help?
Click to expand...
Click to collapse
Sounds like its working to me. Did you boot your phone into fastboot?
I just double checked, and realized the fastboot.exe is corrupted. It's bizarre because it's identical to a functioning copy of fastboot.exe
yes, I have the same Problem, everytime I tipe in " fastboot flash radio radio.img"
it says that fastboot could not be found...
(hmpf adb is working well)
Drillerkiller1337 said:
yes, I have the same Problem, everytime I tipe in " fastboot flash radio radio.img"
it says that fastboot could not be found...
(hmpf adb is working well)
Click to expand...
Click to collapse
This is a different problem to the OP, you've probably not used cd to get to the correct folder before issuing the command.
Command lines aren't for everyone. lol
figured it out thanks for all the help please delete......
my fear said:
ok i downloaded everything that this link tells me:
http://forum.xda-developers.com/showthread.php?t=532719
but when i put in
cd C:\android-sdk-windows\tools
it just stays in that folder i cant do anything past that. when i type adb shell it says 'adb' is not recognized as an internal or external command, operable program or batch file.
i just redid my computer from windows 7 32 bit to now i have 64 bit. am i missing something? when i had 32 bit i had it working but now nothing and i have all the same stuff as before. yes my phone has debugging checked.
any help is appreciated.
thanks,
Stephen.
Click to expand...
Click to collapse
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
rsfaze said:
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
Click to expand...
Click to collapse
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
my fear said:
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
Click to expand...
Click to collapse
That would be right.
I think you're trying to type adb -d shell for example instead of adb.exe -d shell. You would need to include the file extension as well when including commands to be done by ADB.
I followed the wiki.
ADB finds my device when cmd prompt
Adb devices.
It runs first part of the code.
But it then tells me fastboot is not a command.
I read a few other posts, but have found no answer to this problem.
Am guessing im missing something. Maybe someone could help me find out what?
Via HTC Desire Z
ADB and fastboot are in two folders of sdk. In command you need to direct to that folder. ADB is in "platform-tools" and fastboot in "tools"
Example, from my computer.
ADB - cd C:\android-sdk-windows\platform-tools
Fastboot - cd C:\android-sdk-windows\tools
From that you can use fastboot commands.
http://forum.xda-developers.com/showthread.php?t=1364416
I dowloaded SDK and os,and drivers,when i type fastboot -w,and other commands,cmd says that he doesn't know what to do with command.(I typed cd and path to fastboot.img...)
http://forum.xda-developers.com/showthread.php?t=927379
When i click on automatic boot it just shows for 1sec and then just dissipears.
My phone is in fastboot mod.
HELP ?
You have used the cd command to the path containing fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll?
What's the exact error message that comes up in cmd?
Just use this tool. There is nothing easier than this.
I was one of those sorry suckers that somehow got my Kindle Fire stuck in TWRP and I couldn't reset the bootmode to normal. ADB wouldn't recognize the Kindle while it was in TWRP no matter what I tried. Here's how I got it booting again.
1. Download Kindle Fire Utility here.
2. Unzip and open a command prompt in the "tools" folder inside of the unzipped kindle fire utility folder. Do this in Windows 7 by double clicking on the KFU folder and then doubleclick on the tools folder. Next find an empty space in the folder and hold down "shift" on your keyboard and then click your right mouse button. Select "Open command window here".
3. Type in this command and hit enter:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
When that properly executes it will say < waiting for device >
4. On the Kindle Fire inside of TWRP select Reboot -> System.
5. During the reboot process the fastboot command will execute and set you back to normal mode. Now type this in your command window on your computer and hit enter:
Code:
fastboot -i 0x1949 reboot
That ought to do it for ya.
*edit* Wish I could change the title somehow. I misspelled "recognize"
Thank you!!! it worked perfectly. I think this happened because once in the ICS rom I select to reboot into recovery using Room Manager and got stuck on it (bootmode 5001). Anyway this solved the problem in a blink!
You rock!!!! took me two days to find this post..... ugh
Kafluke said:
Wish I could change the title somehow. I misspelled "recognize"
Click to expand...
Click to collapse
LoL...just tell everyone you're British