Related
my computer won't recognize the kindle fire in adb. I have the kf rooted. have firefirefire installed. after firefirefire was installed is when I lost adb. I have tried reinstalling the drivers numerous times to no avail. Any suggestions?
I have deleted all previous sdk, usb drivers or anything android related from computer to start from scatch. I did a factory reset on the kf. I currently have KFU v0.9.3 setup from instructions i followed on a youtube video titled (How to Root - Kindle Fire 6.2.2 BurritoRoot3) by Nat3Mil. sorry I would post a link but apparently I can't until I have 8 posts.
kf v6.2.2
win7
thanks
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line
Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
b63 said:
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
and check "adb_usb.ini" in the ".android" folder in your personal folder
it should include 0x1949 - i use to add 0x18d1 also in a new line
Click to expand...
Click to collapse
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
vwpower44 said:
Sound like your Fire is in Fastboot. This happened to me last week. If you are able to load the drivers in manually, then you should be able to use the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
load the drivers manually and it acts like everything is good but adb still won't recognize the kindle under adb devices
zachjen said:
I have followed those steps in the link before and did it again but no difference. I don't have the adb_usb.ini file or the .android folder. only "Kindle ADB" and "kfu" folders both on the root of the c drive.
Click to expand...
Click to collapse
without the .android folder in your personal folder and the correct adb_usb.ini adb will never work !
create the .android folder and copy the file from c:\kfu\drivers\kindle to the .android folder
Thank you a million times! All is well again.
I had that folder and usb file before when it couldn't be recognized and forgot to put them back I guess.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I can't get this to work.
I've been trying to root/install jb on my kindle fire hd I bought today. I downlaoded the android sdk, installed the proper pacakges. Ran cmd and did "adb devices" no devices found. Enabled ADB on kindle fire, no devices found still. I've now downloaded the kfu and copied the file over just like you said (as well as installed the driver) and still to no avail.
I'm running Win7 64bit.
Any ideas?!?
You might be able to root the hd but the 1st gen. methods will not work and you will not be installing jelly bean at this point it`s not even possible. The hd forum can be found here http://forum.xda-developers.com/forumdisplay.php?f=1782
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode
He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).
gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.
i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....
My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.
Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.
Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?
adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2
nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?
veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit
I installed something not even sure what it was on my rooted kindle 8.9 to upgrade to android 4.3. I after the installation on the kindle i pressed flash and the kindle shut off. Now it does not work, it turns and the kindle fire logo comes up (not the blue) after that i can see that the kindle stays on but in a blank screen. when I plug into the computer the logo comes on and the computer makes four sounds and but then it shows the devise as disconnected. can anyone help, also I thought of buying the factory cables but some threads say that they are not meant for the 8.9 should I purchase these?
No need to purchase it for the 8.9" model from what I know, if the device shows up in the device manager for a moment as a jem device then install the drivers in my signature and get a copy of the fastboot command and run "fastboot -i 0x1949 getvar product" with the kindle off and unplugged, then plug it in, it should power on and go into fastboot mode. From there you should be able to reflash it to a working state.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
No need to purchase it for the 8.9" model from what I know, if the device shows up in the device manager for a moment as a jem device then install the drivers in my signature and get a copy of the fastboot command and run "fastboot -i 0x1949 getvar product" with the kindle off and unplugged, then plug it in, it should power on and go into fastboot mode. From there you should be able to reflash it to a working state.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
IS there a tutorial that you know of that i could use, I'm not sure what you mean by "get a copy of the fastboot command and run "fastboot -i 0x1949 getvar product"
Thanks again for your help
I just realized I'm reply I g to you in 2 threads at once... *facepalm*
Fastboot comes with certain apps here like kffa or kindle fire system restore utility. I usually advise getting it from one of those rather than downloading the bulky android SDK to get it. Once you have one of those utilities, just CD into the directory of the command in a command prompt, and run that command I mentioned.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I just realized I'm reply I g to you in 2 threads at once... *facepalm*
Fastboot comes with certain apps here like kffa or kindle fire system restore utility. I usually advise getting it from one of those rather than downloading the bulky android SDK to get it. Once you have one of those utilities, just CD into the directory of the command in a command prompt, and run that command I mentioned.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
every time I open either program it gives me different options with numbers, when i paste the command the window closes, can you advise on what I'm doing wrong
Um that description is a bit confusing, if you are opening a command prompt and cd-ing into the right directory, and running the command from there, it shouldn't close the command prompt.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um that description is a bit confusing, if you are opening a command prompt and cd-ing into the right directory, and running the command from there, it shouldn't close the command prompt.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
HI thanks for working with me, got this back in the terminal: "-i was unexpected at this time" also an update on the kindle it now when turn on it turns off and back on into its logo and then it reboots
also when i dont get the above error i get "fastboot is not recognized as internal or external command operable program or batch file.
By the way the rebooting is countinious
What exactly are you typing into the command prompt, including stuff from before you type the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jay_3 said:
also when i dont get the above error i get "fastboot is not recognized as internal or external command operable program or batch file.
By the way the rebooting is countinious
Click to expand...
Click to collapse
When you open a command prompt in Windows, or any operating system for that matter, it opens and runs commands (logically) from within a directory. A command is nothing more than a program that accepts arguments which are passed to it (i. e. "fastboot" is the command, and "0x1949 getvar product" is the argument passed to it) When a command is ececuted from the command prompt, the shell searches it's current directory for the command (program) in question. If it doesn't find the command (program) within that directory, it searches the directories saved in the PATH environment variable. Any time you get "blah, blah is not recognized as internal or external command operable program or batch file" in Windows, that is why. To fix this, you can add the directory which contains those commands to your PATH environment variable, include the path to the command (program) in the command being executed, or even more simply, open a command prompt in the directory from which the command (program) is found.
This is basic knowledge that is fundamental for doing anything from the command prompt. You should already have the basic knowledge to not only navigate through your directories from the command prompt but also be able to identify what basic error messages like the one previously mentioned means. A simple Google search of the error you received would have easily given you hundreds of thousands of results explaining what the problem is and what to do to solve it.
stunts513 said:
No need to purchase it for the 8.9" model from what I know, if the device shows up in the device manager for a moment as a jem device then install the drivers in my signature and get a copy of the fastboot command and run "fastboot -i 0x1949 getvar product" with the kindle off and unplugged, then plug it in, it should power on and go into fastboot mode. From there you should be able to reflash it to a working state.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Had the exact same problem as him and couldn't find any info anywhere. This helped me fix it instantly
Thanks for the info!