I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Resolver1 said:
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Click to expand...
Click to collapse
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
Hmm that did help. I should make a noob friendly guide because all of these guides are so vague when it comes to fastboot.
fast boot commands not functioning, adb works fine
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
lgweaver said:
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
Click to expand...
Click to collapse
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
onemeila said:
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
Click to expand...
Click to collapse
Found those steps. but that driver was already installed and said it was functioning. I risked it and attempted the root and install of jellybean without the fastboot command showing devices. apparently it works. my Kindle fire 2 is running cyanogen mod without issue now.
thanks for the response.
Related
Hi, I recently bought a factory cable because my Kindle is bricked. I'm stuck at the kindle fire logo with no adb shell and fastboot says "waiting for device". I got in this situation by doing a wipe from twrp and then flashing the stock recovery (dumb, I know).
Anyway, with a regular cable I can do basic adb commands (adb reboot, etc).
With the factory cable my kindle isn't showing up under adb devices. Windows recognizes it and it shows up in the device manager. I've already re-installed the drivers and everything.
Here's an outline of what happens when I plug in the factory cable. This is starting with the kindle off.
Kindle turns on and goes tot he kindle fire logo and freezes. The power button is green with the factory cable. I noticed that with the normal cable it's orange. I'm not sure if this has any relevance at all.
Anyway, I'm wondering what I can do to get my kindle to show up in adb while using the factory cable.
If you need more info from me let me know and I'll add it.
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
soupmagnet said:
A factory cable puts the device in fastboot mode, therefore will only accept fastboot commands.
Click to expand...
Click to collapse
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
WhatTheFiber said:
I'm not sure if I'm missing something, but fastboot commands aren't working either. It's not showing up under fastboot devices and fastboot flash recovery hangs at "waiting for device".
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
The second post is about device drivers and what to look for in the device manager when your device is in fastboot mode.
It's also possible that you aren't including the vendor ID in your fastboot command. That's covered in the third post.
Click to expand...
Click to collapse
Thank you so much! I was able to flash twrp by using fastboot -i 0x1949. Now I've just got to choose a new rom to flash .
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
So, I know not supposed to post questions that are lame, but I can't seem to figure this out. I will state my specs/situation:
I am stuck on the first step of installing FFF on my first Kindle Fire 1st gen.
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
The kindle fire is in fastboot mode (I'm pretty sure, at least).
It is stuck on the stock Kindle fire boot-up logo.
install_Drivers was run successfully after enabling unsigned driver installs.
Run.bat was executed
selected Option 5 first, to install FFF
FFF was downloaded by KFU, the Fire rebooted and then got stuck.
As it rebooted, I had forgotten to automatically have my Fire connect to the Virtual Machine, so VMWare prompted my with what system I wanted the fire connected to. I'm not sure if that delay has something to do with the stall and failure of KFU to install FFF or get out of fastboot.
KFU doesn't recognize the Kindle ("waiting for device" message; ADB: Offline; Boot Status:Unknown).
In my "other devices" on Windows Device Manager I see "Base System Device" and "Unknown Device"
My questions are:
1. How do I go about getting it out of fastboot mode even though KFU can't see the device.
2. What was I doing wrong in the first place?
Before you tell me:
I have read through the Guide
I have read through and searched much of the KFU dev thread
I have searched the forums, without a clear solution.
Thank you very much for your help!!!
escoloader said:
2. What was I doing wrong in the first place?
Click to expand...
Click to collapse
This:
I am on a Macbook Pro Retina 15" mid-2012 (USB3.0/2.0 mix ports only)
I am using KFU on a Win8 64-bit Virtual Machine (VMWare latest version)
Click to expand...
Click to collapse
Use breakdroid instead
Sent from my Amazon Kindle Fire HD using Tapatalk 2
soupmagnet said:
This:
Use breakdroid instead
Click to expand...
Click to collapse
How do I get it back to normal booting first?
Thanks for your help!
escoloader said:
How do I get it back to normal booting first?
Thanks for your help!
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thank you for the help, but could you please explain how I use that code, step by step if possible?
Thanks a lot
EDIT: I guess I should specify, I do NOT have a fastboot factory cable. Do I need one?
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Thepooch said:
Okay since you can use windows on a vm start there. Shift+right click on the tools folder inside KFU select open command window here, plug in the kindle, type the first command hit enter, type the second command hit enter if all goes well it should reboot normally. Same concept on a mac whatever directory adb and fastboot are in open a terminal, same commands same method. Good luck
Edit: in fact you can just copy paste my commands then you know you got it right. Dunno about the cable yet see if the commands work.
Click to expand...
Click to collapse
Did the first one, but still says "waiting for device" and nothing is happening. :/ (EDIT: for clarity's sake, nothing happening means its still stuck on the kindle fire white/orange stock boot logo)
btw, thank you for your help.
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
soupmagnet said:
Hold the power button to turn the device off. Enter the command, and turn the device on when you see "waiting for device".
Click to expand...
Click to collapse
still says "waiting for device" in the terminal.
also, windows still comes up with "usb unrecognized" message at the bottom right of my screen.
What's next?
Thanks for joining to help, soupmagnet
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Thepooch said:
Okay rerun the driver.bat packaged with kfu then plug the device in see if it comes up in device manager.
Click to expand...
Click to collapse
Still doesn't show up. (It also occasionally crashes my mac system when I plug the kindle in now :/ )
If I get a factory cable, will that likely solve this easily?
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Thepooch said:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Code:
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Thepooch said:
Well I'm not a Mac person but it's far better with drivers than Windows ever will be maybe google how to setup and and fastboot on a Mac and go from there. Download install breakdroid that should be accompanied with the drivers.
Click to expand...
Click to collapse
Got it! Using Breakdroid, I was able to capture the Kindle as it powered on. I believe my main problem was that there was a significant enough delay in connecting the Kindle via USB to the Windows Virtual Machine, that the ADB couldn't access it in time to capture it. Or whatever.
Solution: I used BreakDroid on my Mac. Turned the kindle off, then back on while Breakdroid was waiting for my device to perform Step 1 on Breakdroid's Kindle Tools. Then it immediately captured the Kindle when I powered it on. Went through the steps on Breakdroid, and it's working with bootloader and recovery
Works great! Have all my stuff back. And...it's rooted
THANKS FOR ALL YOUR HELP, GUYS!
EDIT: Now how do I install Google Play?
Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!
Maximus300 said:
Firstly, if there is already a thread about this that I've missed, I'd be appreciative if you'd send me in the right direction to get information.
Anyway, my Kindle Fire HD, rooted CM 10.1, will no longer boot past the orange Kindle Fire Splash screen. I've tried using fastboot commands and all of the button configurations in any and all attempts to get a response from my device, but it remains on that screen with no looping or any kind of change. When plugged in (or turned on while plugged in) it's registered in Device Manager as the usual "Jem-PVT-Prod-04" when drivers aren't installed, and then disappears from the Manager within five seconds. I can't install the ADB drivers because it vanishes, so I cannot communicate with the device from my computer; therefore I cannot fastboot (as far as I can see) and have no possible way to recover it.
Is my last hope a fastboot cable, or is there something that I have missed this whole time? Thanks for any and all help!
Click to expand...
Click to collapse
Thats a kindle fire hd 8.9" model, fastboot cables don't work on them. A easy way to fix this is to boot a ubuntu live cd and install the fastboot command from the repos and run it. Latest ubuntu is 14.04 lts and i haven't checked the package names yet, but if it has the same name as on 13.10 then these instructions should work. Boot a ubuntu live usb/cd and open the settings and look for something like software updates and check off all the download form internet boxes. Hit reload if it asks, and if it asks ignore the first command in the next part of the instructions.
Now open a terminal and run these commands:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
fastboot -i 0x1949 getvar product
Now that it says waiting for device, plug the kindle in while its off and you should be in fastboot mode. From there you can reflash it from windows with kffa or srt, or just do it manually while in ubuntu.
So I used the Linux command to put my Kindle in fastboot mode, but now it says it cannot connect with MTP device, so I still cannot flash any type of recovery. Even though it is in fastboot mode, and the drivers are installed, ADB is still not working on Windows.... and I'm not sure how to do it manually on Linux...
MTP is irrelevant with fastboot, as is adb, you don't use adb commands with fastboot, you use fastboot commands. You can use kffa or SRT to restore it from windows once it is in fastboot, or restore it manually in Linux using SRT's images. You probably will have to use SRT, I have heard a report that kffa's downloads for the images are offline again, though I'm not positive on that.
Sent from my Amazon Tate using Tapatalk
I've installed ADB/Fastboot/USB Drivers from http://forum.xda-developers.com/showthread.php?t=2588979 (tried both 1.3 and 1.4.2 versions.
Booted my SW3 into Fastboot (whitescreen, with fastboot written on it) - attached to the PC, Device shows up as SAMSUNG Android Phone > Android ADB Interface
Ran CMD as an Administrator.
Typed, adb reboot bootloader.... Error: device '<null>' not found.
Typed adb devices... not listed.
Okay, so using a driver stripper (and windows program uninstaller), removed all Samsung phone USB drivers, KIES and existing ADB drivers. Re-ran the top tool to re-install everything. Repeated process, still showing up as SAMSUNG Android Phone > Android ADB Interface. Still not detected.
No idea at all what's going on here. I've tried cleaning the drivers multiple times. Other USB ports (2.0 & 3.0). Tried manually updating the driver to Google Inc. driver variants (9.0-11.0)
Really appreciate any help here.
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
woschirmer said:
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
Click to expand...
Click to collapse
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Sideburnt said:
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Click to expand...
Click to collapse
Okay progress, I see what you mean now adb reboot bootloader doesn't work. But fastboot reboot bootloader does. This is allowing me to move through the necessary TWRP and img steps. Thanks.