im not sure where to go from here. I attempted to use the Kindle fire Utility to install "permanent root with superuser" on my stock KF. it seemed to be doing its thing until it rebooted and just hangs at the white and orange "kindle fire" logo now.
i have since been searching everywhere for a fix. When I stumbled across this thread (thank you) i made my own factory cable and reinstalled all the drivers and such (which seem to load fine when comparing them to the pics in the op anyway).
My problem is when i try to do anyting with adb or fastboot commands i just recieve a "waiting for device" message.
im pretty sure my factory cable works because my KF starts with it. with another usb cable i just reciceve a mesasage that the KF's battery is too low.
any help would be so much appreciated. thanks in advance!
All the factory cable does is put it in fastboot and your trying to get out of fastboot. Power the kindle off issue the command fastboot -i 0x1949 getvar product (hit enter) when it says waiting for device plug it in powered off with a regular cable not the factory one it should then power on if you get the response product: kindle the type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter) it should say "okay" then type fastboot -i 0x1949 reboot (hit enter) it will say "rebooting" then it will boot in normal mode. Good luck
Edit: also if plug in via usb possibly get that battery some juice if it will not charge your looking at this http://forum.xda-developers.com/showthread.php?t=1430038 to send a bootloader that will charge under low battery conditions
I was waiting for a mod to move this question out to its own thread before I replied. It looks like they didn't get around to it until early this morning.
KFU appears to have a habit of leaving devices in fastboot mode. This usually happens because the device drivers have not been installed or they are not loading properly. You should look into that first.
This guide...
http://forum.xda-developers.com/showthread.php?t=1668159
will tell you if you are actually in fastboot mode.
This guide...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
will tell you if the device drivers are installed and loading properly.
I've also been told that there are some problems with fastboot and USB 3.0 ports. If you are using a newer machine with USB 3.0 ports, try moving the cable to a USB 2.0 port and see if that helps you.
What kinfauns is saying about 3.0 vs. 2.0 is indeed correct once fastboot is initiated the 3.0 usb port literaly stonewalls further communication to and from the device only a 2.0 usb port will work.
Related
I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
jdswain said:
I've tried looking through lots of other threads, but I can't find a problem similar to this.
I tried to root my kindle fire using these instructions:
http://forum.xda-developers.com/showthread.php?t=1568340
It all worked until I got to the
fastboot -i 0x1949 flash recovery <name of recovery image here>
step, which appeared to hang. I was doing this on a mac, so I thought that was the problem. It was late so I went to bed. In the morning I tried to boot my Kindle Fire, but now I can't access it at all.
Without the USB cable plugged in it won't boot at all. With the USB cable connected the yellow logo comes up for a few seconds, disappears and continues in that loop. Pressing and holding the power button does not change anything.
I can't get the Mac to recognise a USB device when it is plugged in. I tried linux (under VMWare) and lsusb reported nothing either.
Does anyone know what I can do to get the KF back to a state where I can at least communicate with it?
Click to expand...
Click to collapse
I think you have a dead battery....
http://forum.xda-developers.com/showthread.php?t=1623244
FWIW, I've noticed a number of Mac fastboot problems being posted here lately. I tried this for myself to see what was going on. Although it will respond to 'fastboot devices' and 'fastboot getvar product' commands, it stalls while trying to send the image to the KF. I've tried several different copies of fastboot and they all do the exact same thing for me. No "fastboot flash" or "fastboot boot" commands will get past the sending stage.
VMWare might also have issues with fastboot as I've heard some rumblings about that as well. I'm a Parallels Desktop user and I've never really encountered any problems along these lines in my Windows or Linux VMs.
I think your next best bet is to build a Ubuntu Live USB system on a thumb drive and try using that on your Mac.
I've been speaking with kinfauns about this fastboot/Mac problem that's come up recently. I've been using Mac since I rooted my Kindle Fire and I've never had a problem with it in regards to adb or fastboot.
Have you installed any OSX software updates lately?
Howdy all,
I have a 1st Gen Kindle Fire that I apparently have corrupted. I pushed TWRP onto the device prior to rooting it and rebooting, and the device is stuck at the orange "kindlefire" logo. I've tried the KUU but the device is not detected by adb or fastboot. I've unloaded and reloaded the drivers to no avail. The device is detected as an "Android ADB Interface" which i'm not sure if that's the proper device name or not. I've tried not only the amazon provided kindle drivers, but the google drivers from the platform sdk and some of the other drivers from the forums here. In all cases, I'm unable to query the device via "adb devices" or "fastboot devices."
My last hope was to buy a fastboot cable to try to force the unit into fastboot mode, however it doesn't appear to be doing anything. The device boots and continues to stay in the kindlefire logo.
I checked the cable with a multimeter and I am indeed getting +5 on pins 1 and 4, so I can confirm the cable is a fastboot cable.
At this point, I'm pretty much out of ideas. Does anyone have another way of getting into fastboot mode? Is there a way to do it via an internal circuit short or pin jumpering?
Dirty Pete said:
Howdy all,
I have a 1st Gen Kindle Fire that I apparently have corrupted. I pushed TWRP onto the device prior to rooting it and rebooting, and the device is stuck at the orange "kindlefire" logo. I've tried the KUU but the device is not detected by adb or fastboot. I've unloaded and reloaded the drivers to no avail. The device is detected as an "Android ADB Interface" which i'm not sure if that's the proper device name or not. I've tried not only the amazon provided kindle drivers, but the google drivers from the platform sdk and some of the other drivers from the forums here. In all cases, I'm unable to query the device via "adb devices" or "fastboot devices."
My last hope was to buy a fastboot cable to try to force the unit into fastboot mode, however it doesn't appear to be doing anything. The device boots and continues to stay in the kindlefire logo.
I checked the cable with a multimeter and I am indeed getting +5 on pins 1 and 4, so I can confirm the cable is a fastboot cable.
At this point, I'm pretty much out of ideas. Does anyone have another way of getting into fastboot mode? Is there a way to do it via an internal circuit short or pin jumpering?
Click to expand...
Click to collapse
So, I'm an idiot -- when I was running fastboot I was not specifying "-i 0x1949" in my arguments, which apparently was necessary to make fastboot find the device. I've now done that and have unbricked the unit successfully.
To reiterate, when using fastboot on a kindle fire, be sure to have -i 0x1949 so fastboot can find the unit properly.
I have searched and read a bunch and have not stumbled upon my situation.
Hopefully someone can shed some light on my use of a factory cable.
Bought a cable from SkOrPn - great guy and very helpful. We thought maybe the problem was the cable so he sent out another. TO BE CLEAR, ISSUE IS NOT WITH SkOrPn's CABLE. Both cables yield the same results.
So, here's the deal:
I have 2 KFs that where bone stock. I used KFU to root, install TWRP and FFF 1.5 Bootloader. All worked fine and I subsequently installed CM11. So all is good.
Now when I try to use the Factory Cable as instructed
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Click to expand...
Click to collapse
But when I plug the Fcable into the fire it immediately powers on and boots normally, skipping fastboot mode. This happens with or without plugging the other end into the PC.
So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires.
Luckly I am fully rooted with FFF 1.5 and CM11, so I really dont need to use the factory cable. But I would like to figure this out BEFORE I need it!
micl9 said:
...So SkOrPn suggested I try plugging into the PC 1st and then the fire. This does boot to fastboot mode. So now I unplug the Fcable and using a "normal" cable plug the fire back into my PC. Now I get an error message saying that the USB device cannot be installed and of course KFU/ADB/fastboot does not recognize my device. So I am (or appear to be) in fastboot mode, but can't communicate with my fire. Keep in mind I have KFU working, so I know drivers are installed.
Any thoughts?
And the above is the same for BOTH fires...
Click to expand...
Click to collapse
Just because you can run kfu, and you got your kindles rooted, that doesn't necessarily mean your drivers are installed properly.
I would uninstall and reinstall your drivers just to check.
Also, when you plug in your kindle in fastboot mode, does you're computer list it as a fastboot device? (Command Prompt, cd to folder with KFU tools are and adb.exe and fastboot.exe are, then type fastboot devices; a string of characters is good, while nothing is bad)
If that doesn't work, can you use kfu to reboot your kindles into fastboot?
Sent from my Nexus 7 using Tapatalk
I tried uninstalling and re-installing drivers - might try a fresh computer
When connected in fastboot mode devices command comes back with nothing.
I will try using KFU to put the kindle into fastboot when I get home tonight.
Update:
OK so KFU can put it into fastboot - witch matches behavior using cable, so now I know that works.
And my PC does not recognize the kindle in fastboot mode. Tried UN-installing and re-installing drivers with no luck. As this has been my "hackers" laptop for quite a while there is no telling what driver ghosts remain.
Will give it a shot on another PC.
Still kinda odd that my Kindles require a different factory cable procedure to get into fastboot mode.
Post once you try it on a fresh PC.
Sent from my Nexus 7 using Tapatalk
Ok most issues are resolved
KFU
Apparently while in fastboot mode KFU will report status unknown, but using bootmode menu to change back to Normal works.
Also using adb devices in fastboot mode returns nothing, using fastboot getvar product returns kindle!
For these 2 I should have read more - sorry
USB reporting device cannot be installed after having device in fastboot mode via factory cable.
OK this one I got some bad info that said the factory cable is not used for flashing - only for getting device into fastboot mode.
What I was doing wrong - using Fcable to get into fastboot and then swapping the Fcable out for a std USB cable - this results in the device cannot be installed error and kindle not being seen by fastboot commands.
What I should do - using Fcable to get into fastboot mode AND using it for the data communication as well (ie DONT unplug the Fcable!).
Last (and still open) issue
Why my devices don't use the normal factory cable process (plug into Kindle and then PC) - but only works by plugging PC end 1st and then Kindle.
but I am not sure this matters anymore.
jma9454 thanks for chiming in!
Hi all,
I got a refurb 8.9 HD for basically free, so I want to flash the best current ROM onto it (which it looks like is CM11 at the moment). I'm having a bit of trouble getting the device into fastboot mode:
What I've accomplished so far:
Have adb and fastboot working in the command prompt
Installed the amazon usb drivers, kindle shows as Android Composite ADB Interface in device manager
Device is recognized by adb devices (shows serial number + "device")
Turned "Enable ADB" to ON in security settings
However, when I unplug the kindle, execute the "fastboot -i 0x1949 getvar product" command, I do get the <waiting for device> message, but when I plug in the turned-off Kindle, I get two quick chimes, then a second later the "device disconnected" sound, then the kindle boots as normally, and nothing happens in the command prompt.
It may be worth noting that when I first connected the Kindle (after installing drivers) I didn't get the "Enable USB Debugging" pop-up that two guides mentioned. Thoughts?
You must be doing it in the wrong order
1. turn of your kindle
2. connect your wire
3. open cmd and type fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
4. now turn on your device it should go into fastboot
Did you get it to work? And are you running 8.5.1? Because that's what I'm running and I'm having the same problem. I've seen solutions all over the place for 8.4, nothing for 8.5. Amazon seems to have a real lockdown on it.
Hi Guys!
Picked up a refurb Kindle Fire HD 8.9 on Woot the other day and want to stick CM 12.1 on it. I'm no programmer but I've successfully followed directions to root and install CM on about a dozen devices over the years but this one has me stumped.
I'm running Windows 10 and have apparently successfully installed the Amazon USB driver. When the tablet is plugged in Device Manager shows "Fire Devices > Android Composite ADB Interface" and it reports "working properly." I made sure to install the driver with Windows driver signing OFF. I can do a command prompt "ADB devices" and I get back a single device which corresponds to the device Serial Number (when I disconnect the tablet, I get nothing). So it seems ADB can find the tablet. The tablet has "Enable ADB" set to ON. I have done nothing else with the tablet, no registration, nothing, it's direct from factory and seems to be working fine. Current system version is 8.4.3_user_4308820, I have not updated it from what it came with.
So everything looks good until I try to run fastboot. I punch in "fastboot -i 0x1949 getvar product" and get "waiting for device". I reboot the tablet and it just simply reboots like normal and brings up the lock screen. I can't get Fastboot to show. I've done a simple shut down/reboot, I've held the power button down for like 20 seconds and forced power off. I've also tried plugging into different USB ports and different USB cables. Still nothing, just "waiting for device".
Can anyone offer suggestions to get to Fastboot? Many thanks in advance!
Are you generating your command prompt in the folder where fastboot.exe (and ideally also adb.exe) is located? If not, do so. When you get the "waiting for device" prompt with fastboot, are you then plugging in your powered OFF Kindle? This is one way that fastboot operates in our Kindles. There is also the modified factory cable that will automatically reboot the Kindle into fastboot mode (see the following video: www (dot) youtube (dot) com/watch?v=FFoAvnf7YUQ). Alternatively, you can try using ADB to reboot the device into fastboot as shown in the video. Good luck!