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?
Related
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there <waiting for device>. Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got <waiting for device>..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
nschiwy said:
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there . Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got ..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
Click to expand...
Click to collapse
First things, first...In Windows, if you are in fastboot and you get "waiting for device", it is a driver issue, plain and simple. In rare cases it could be a bad USB cable or port, but those are very unlikely considering what we see on a daily basis.
To understand the adb issue, you have to take a look at KFU's run.bat. To decide whether it is "connected" or not, it checks to see what state the device is in, i.e. in fastboot or booted normally or in recovery. To get the status (online/offline), it sends an "adb devices" command. If the command returns "List of devices attached -null-", the script will return a status of "offline". Either way, you are dealing with a driver issue.
I bought a couple of factory cables to test and share and found that if i just plugged it in an typed fastboot devices nothing would be returned no string nothing but if I powered it of and typed
Code:
fastboot -i 0x1949 getvar product
and then plugged it in it would power on and present product: kindle then fastboot devices would produce the string of numbers I was looking for. Dont know why it works this way but it does give it a shot...
nschiwy said:
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there <waiting for device>. Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got <waiting for device>..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
Click to expand...
Click to collapse
Try this it works fine for me so far. I'm facing the same problem as you ADB Offline,
1) Switch off your kindle.
2)start KFU (ensure it's the latest v. 0.9.6) on your desktop
3) Connect your factory cable to kindle first then to PC ( take note ADB status will still be Offline).
4) Kindle will boot by itself
5)when boot logo is on the kindle fire screen go to KFU press 5 (install latest firefirefire)
6)Installation firefirefire complete next press 3 install latest TWRP Recovery
7) Done. Now you can access to TWRP and flash your ROM
Thanks for all of the advice guys, in the end I wound up giving it to her with stock running so she can get used to it. Maybe sometime down the road I can help her with root and such. She is only 11, after all.
Rooting Problems
Lol I hope this doesn't affect me because I'm actually 12 With the same problem On My KF Ill try those BTW I jailbreaked a iTOUCH 4G With redsn0w and I un jailbreaked it Unsafe Way But GamePlayer Still Works
I was attempting to root my Kindle using the tools in this thread: http://forum.xda-developers.com/showthread.php?t=1399889
It failed at "Installing FFF... Waiting on Device". It seems like this is an issue with TWRP. Since that failed the kindle gets stuck on the Kindle Fire logo and can only be powered off with the 20 second button press.
I am not sure where to go from here, any help would be great, thanks
This same thing has happened to me SO many times. What's happening is your Kindle is stuck in fastboot mode. This is usually caused by a driver related issue. You probably didn't have installed all the correct drivers. Try doing this to get it back to normal bootmode:
First make sure the right drivers are installed. Run "install_drivers.bat"
Then before plugging in or turning on your Kindle run "run.bat" and choose "1 Bootmode Menu" and select "1 Normal <4000>"
It should now say "waiting for device". Make sure your Kindle is still off then plug it in. It should boot up on it's own. Then KFU will recognize it and switch it to normal bootmode.
Nihilian said:
This same thing has happened to me SO many times. What's happening is your Kindle is stuck in fastboot mode. This is usually caused by a driver related issue. You probably didn't have installed all the correct drivers. Try doing this to get it back to normal bootmode:
First make sure the right drivers are installed. Run "install_drivers.bat"
Then before plugging in or turning on your Kindle run "run.bat" and choose "1 Bootmode Menu" and select "1 Normal <4000>"
It should now say "waiting for device". Make sure your Kindle is still off then plug it in. It should boot up on it's own. Then KFU will recognize it and switch it to normal bootmode.
Click to expand...
Click to collapse
I did all of that and it still does not get past the splash screen. The kindle booted up on it's own, but KFU never went past <waiting for device> and the kindle never went past the splash screen.
Try researching into the Factory reset cable that Skorpion sells, that can help boot your kindle into fastboot mode and help unbrick it.
A factory cable would be no help here seeing as it's already in fastboot mode. You need to somehow get your Fire back to normal boot mode. To me it sounds like this is a driver related problem since KFU cannot find your device. Try looking into this. It has helped me in the past. You need to be running Ubuntu for this, but then you won't to deal with drivers.
Nihilian said:
A factory cable would be no help here seeing as it's already in fastboot mode. You need to somehow get your Fire back to normal boot mode. To me it sounds like this is a driver related problem since KFU cannot find your device. Try looking into this. It has helped me in the past. You need to be running Ubuntu for this, but then you won't to deal with drivers.
Click to expand...
Click to collapse
I have tried using that with Ubuntu as well, but the computer still never recognizes the Kindle. I ordered the cable in case it helps, it should be here after Christmas. I will try out some more options in Ubuntu in the time being.
The stock bootloader has (presumably) been modified from it's original state and packaged with the 6.3.1 update. I stumbled across this anomaly during my work on the SoupKit.
Typically, with working drivers, the stock bootloader would report that a device is connected when it receives the "fastboot devices" command. Now, it doesn't...even on Linux. Another thing I noticed, is that when a fastboot command is sent, it sits at "waiting for device", indefinitely, or until the device is restarted by use of the hard shutdown. When the device starts up again, fastboot will detect it and send the command. Unfortunately, this only works for one command at a time and the device needs to be restarted again.
This all depends on whether the drivers are in working order, of course.
Windows can be very finicky when it comes to Android drivers so the best bet is to use Linux so as to eliminate as many variables as possible. Try sending the command and restarting the device. If it doesn't work, you know it's a driver issue. You can keep trying to fix your drivers in Windows or bite the bullet and go the Linux route. If you do decide to go the Linux route, SoupKit can make your life considerably easier (just choose an option and follow the instructions).
"That's a special kind of stupid. The kind that makes me laugh."
I think its been once again modified a little more as of recent there was a tiny update that I believe will have some affect.
I have tried a few of the options in FireKit on a Ubuntu LiveUSB Stick.
Same problem as ever though. Nothing ever gets past < waiting for device >.
My process is: enter the prompt in Terminal and get to the < waiting for device > step. Plug in the powered off Kindle Fire. The KF boots up into the splash logo.
After a few minutes the screen and power LED starts to turn on and off but nothing else ever happens.
I got a factory reset cable, but it does not seem to do anything.
I have also tried soupkit and firekit, both on a Ubuntu live USB.
Is there anything else I should try?
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
.................FIGURED IT OUT!..............................
Much thanks to the pooch who spent hours helping me troubleshoot.
What we (he) did, as far as I remember, hopefully this can be of some service to someone else out there.
1) Figured out that trying all of this on a Virtual Machine is not a good idea!
2) I somehow broke the bootloader in my first attempt, so none of my computers were recognizing the KF.
3) Created a Pendrive to run Linux (ubuntu). Here Requires a USB drive formatted Fat16/Fat32/NTFS, minimum of 2 gb.
4) Once I got Linux running, installed SoupKit.
5) Went through a few tries of booting, rebooting, into recovery mode until the Kindle flickered back to life!
6) Followed prompts on SoupKit to install TWRP, updated TWRP, install FireFireFire, install Android 4.2.
Good luck, I am happy to answer any questions - though I am no means an expert now.
What I have tried...more info
More Information:
I am running Windows7 in a VirtualBox on an iMac.
I bricked the Kindle a few weeks ago, after messing with it then, I bought a factory fastboot cable. Still no dice.
I have tried all turning on and off computer, on and off Kindle with it disconnected, connected, going through the KFU 4 seconds after starting the Kindle. Letting the Kindle's battery die, recharging.
I have deleted .android folder, reinstalled drivers, re-downloaded KFU.
I have tried on a different computer (Windows XP) The Kindle is also not recognized there.
I have tried booting into Ubuntu (however in the directions there, it said the FireKit is for more "serious" issues than my soft brick.
I am sure there is some small detail I am missing, but I have not been able to find it - and I am not knowledgeable enough to properly diagnose the problem. Again thanks for any help.
kyleboyd said:
I am total noob. Just want to make that clear from the get go.
I hesitate to start a new thread, but I have been working on this forever, and have not made any progress.
I have a Kindle Fire that I would like to run android on - I started the process with the Kindle Fire Utility v 0.9.9. Something went wrong, and it is now stuck on the Kindle Fire start up logo. I also can no longer see it in the device manager, nor is it responsive to anything in the Utility. (ADB status: Offline Boot Status: Unknown). I am at a loss, does anyone have any ideas? Your help is appreciated!
Click to expand...
Click to collapse
Sometimes KFU will show as Unknown even though it's really fine. I had the same issue as you. Try switching boot mode to Normal and see if that fixes it, it worked for me.
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
hemmulde 1st
zastava750 said:
Read this (everything),especially third post.
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
kyleboyd said:
Thanks for the reply!
I tried that. When I type "fastboot getvar product" it says waiting for device or something similiar.
The advice applying to Device Manager don't get me anywhere, because my Kindle doesn't show up.
Any other ideas?
Click to expand...
Click to collapse
When using the stock bootloader (plain "kindle fire" boot logo), the fastboot command must always specify the custom vendor ID used by the Kindle Fire. For example, the commands above must be slightly altered to...
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 devices
and likewise, all of the following commands will need the "-i 0x1949" switch when using the stock bootloader. The FFF bootloader's vendor ID has been changed to one that is normally recognized by fastboot, so the "-i 0x1949" switch can be omitted.
Now onto some more useful fastboot commands...
Code:
fastboot oem idme bootmode 4000
fastboot oem idme bootmode 4002
fastboot oem idme bootmode 5001
Using one of these commands will change the bootmode to normal (4000), fastboot (4002) or recovery (5001). Then issuing...
Code:
fastboot reboot
will reboot the device into the respective bootmode.
I've tried that as well...
Just so I am totally clear, this is what I did in relation to those instructions:
Opened Command Prompt - set the directory to C:/kfu/tools
Typed "fastboot -i 0x1949 getvar product" (with out the quotations, obviously)
<waiting for devices>
I plugged Kindle in, it powers on and the frozen logo pops up.
I also tried "fastboot -i 0x1949 oem idme bootmode 4000" and "fastboot -i 0x1949 oem idme bootmode 4002"
According to the guide it often takes multiple tries, I have done it over and over again.
I have also tried different orders of code, plugging in Kindle, and powering on and off.
Am I doing something wrong? Is there a specific code for my Kindle? (Not -i 0x1949)
Thanks!
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1660636
Reinstall the driver then use kfu to reset the boot mode to normal.
Drivers?
I did try this: http://forum.xda-developers.com/show....php?t=1660636
When I get to the part about the Device Manager, I am stuck, as nothing shows up (I suspect something do with drivers)
Thepooch said:
Reinstall the driver then use kfu to reset the boot mode to normal.
Click to expand...
Click to collapse
By reinstall drivers do you mean clicking on "install_drivers" in the KFU folder? I have tried that.
Is there another method of uninstalling and installing drivers? Sorry if that is a dumb question!
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Still not working
Thepooch said:
If the devices is in fastboot which I believe it is it would show up as android adb interface, if it was attempting to boot to the system it would show up as android composite adb interface. If you are on xp or windows 8 this can be a bit of a tricky task. Android adb interface and android composite interface are two facets of the same driver. So yes I suggest rerunning the driver installation bat that is packaged with KFU. If perhaps you are on windows 8 you must disable driver signature verification and reinstall the driver. 3.0 usb ports have an issue with fastboot and can leave the device undetected.
Click to expand...
Click to collapse
Thanks for the quick reply.
So I am on a Win7 and/or a Windows XP. Currently on both systems, when I plug it into the computer, with the Device Manager open, nothing happens other than the Kindle turning itself on.
Before it froze up, I saw it in device manager as Android ADB interface, and before doing anything at all, saw it as the default Kindle Fire.
On the Win7 system, I have rerun the driver installation bat over and over and over again, with absolutely no results.
On the WinXP, I have tried it, and for the life of me can't get it to install (it says install failed (Unsigned)). I never connected the Kindle up to this computer before it froze up, so I wonder if that is somehow causing the problem (it is trying to update drivers that don't exist?)
Am I doing something wrong with this? Can I uninstall or delete drivers, and totally start over?
If you are using a WinXP you must install driver manually.
Drivers?
zastava750 said:
If you are using a WinXP you must install driver manually.
Click to expand...
Click to collapse
How do I do that, when the Kindle does not show up as being connected? All the guides I have found start off with accessing from the Device Manager. My Kindle does not show up in the Device Manager...
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Windows 7 - No Dice
Thepooch said:
okay well then you`re running xp use another computer getting the driver installed is hard even for the very skilled particularlly when the device is stuck in fastboot. Friend or relatives computer running windows 7 would be perfect. Otherwise it`s linux on a live usb booted on your xp machine.
Click to expand...
Click to collapse
Yeah so I have a Windows7. I have reinstalled the drivers (by clicking on the install_drivers.bat file in the KFU) over and over again, and I still do not get any recognition on the computer, or in the Device Manager when I plug in the Kindle.
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Thepooch said:
Try different usb port, make sure they are usb 2.0. Is the logo static or animated? It possible that you broke the bootloader. At some point I would be willing to look at some things for you via teamviewer. If it is not driver related I fear your next move is here http://forum.xda-developers.com/showthread.php?t=1430038. Keep it on charger or off till it can be dealt with.
Click to expand...
Click to collapse
Thanks! I would be willing to give it a shot (teamview I mean) if you are willing.
I tried the Firekit before I began this thread, but I kept getting stuck trying to run the tool after booting into ubuntu. Perhaps that is a different thread topic, but I am more than willing to put more work into figuring that out, if it could be the key to unlocking this stupid thing.
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Nixnaegie said:
I am having this exact same problem. Using Win XP i was able to get the ADB drivers loaded initially and used KFU to try to install TWRP. When it rebooted during that process it got stuck at the Kindle Fire logo. Since then I cannot get my computer to recognize the kindle. Like you, I feel like i've tried everything.
Click to expand...
Click to collapse
Glad to know I'm not alone - misery loves company! Solidarity my friend.
I wish I could tell you I'd solved it, but alas, I have not. I'm still working on it, I'll keep you updated if I have any breakthroughs!
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!
Help! I never post threads on these things because I can always find what I need somewhere. Alas, after working on this for days without sleep I admit I need help.
I have an 8.9 HD and had it rooted with TWRP 2.4.4 (I think, def. older one) and Cyanogenmod 10.X. I wanted to update to Cyanogenmod 11 but TWRP failed every time I tried to flash. I thought maybe I needed an updated TWRP to flash C11. I downloaded Flashify app to the Kindle and also the TWRP otter IMG file. After flashing the recovery, the app said to reboot so I did.
It booted up into the first kindle fire logo (orange) but went no further. Whenever I plugged the Kindle in, Windows makes the du-Duh sound like a USB device is connected but then immediately gives the Du-duh unplug sound. I read something about using the original Kindle cable to go straight to fastboot mode. I think I have it (is it white?) because I plugged it in and it is now in fastboot mode.
Windows is recognizing the unspecified device as Jem-PVT-x. I am in CMD but "ADB devices" shows an empty list and fastboot devices just goes back to the original line without showing/doing anything.
Can I fix this?! HOW?! Thank you SO MUCH for any help!
You have to either install the drivers in my signature in the brief moment it's detected or take the easy route and use a ubuntu live disk, either way you will be running" fastboot -i 0x1949 getvar product" and plugging the device in while it's off after that command has been run.