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!
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.
My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.
jwhite0514 said:
My son is trying to get his kindle fire back up and running. With not much success. He was reinstalling the software and must have wiped the device clean as now he cannot get back into recovery mode. When installing FFFF it says that there is no exec directory. He ordered a factory cable adapter from black hat under the impression that this would force the device into fastboot thus recovery. When he attached the adapter all that happened was that it went back to the kindle fire logo and is now showing offline status unknown. Before at least it was showing online. Are we mistaken that it should go to recovery (blue and white) kindle logo. We are a little tired of messing with it and are thinking of calling it quits. Any suggestions would be much appreciated. We have turned off and on, installed drivers, and switched cables to no avail.
Click to expand...
Click to collapse
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.
Thanks for the reply. I looked at the logo this morning and it came up brightly lit with no change so I am assuming it is in fastboot mode. That being said the device, in device manager it comes up as unknown usb device. Before it would come up as kindle and I would install the drivers and it would come up as an android phone adb composite. I went into device manager and tried to update the driver manually and windows tells me that the correct driver is being used for this device. I did unplug the adapter and go back with a regular data cable and that made no difference. Do you need to force it to use a different driver. I am trying to use the drivers that came with the KFU I downloaded.
soupmagnet said:
You almost got it right. The error you received means the shell is no longer accessible and therefore unable to send necessary shell commands, like those used to change bootmodes. In order to fix the problem, a factory cable is needed to access fastboot, which gives you an alternative method of changing bootmodes (to access recovery) or flashing partition images (i.e. installing recovery) by use of fastboot commands. But the factory cable does not actually boot the device into recovery on it's own though.
Here's where it get's a little tricky though. Unless you know what to look for, it's difficult to know whether the device is actually in fastboot because the only thing that will be displayed on the screen is the Kindle Fire logo. You'll know if the device is in fastboot because the Kindle Fire logo will stay brightly lit, indefinitely. If the Kindle Fire logo flashes and/or gets slightly dimmed, then you'll know the factory cable you have is defective. With that being said, however, just because the device boots into fastboot mode, doesn't necessarily mean the computer will communicate with it. For that, you need working drivers.
Long story, short...you need to confirm whether the device is actually in fastboot before you can go any further.
Click to expand...
Click to collapse
Kindle drivers are notoriously touchy. Try uninstalling/reinstalling them a couple of times. I predict they will suddenly start working and you can proceed with installing custom recovery/rom.
Sent from my GT-p511x
Thanks for the respone, I have installed and uninstalled to where if I here the computer connect and disconnect one more time I might throw it against the wall. Are there specific steps that I need to take other than ordinary to unintall/install the drivers correctly or maybe drivers that are more sccuessful than others.
Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?
jwhite0514 said:
Ok, after sifting through a number of threads. I read where adb and fastboot are mutually exclusive and adb will not see a device that is in fastboot mode. Is that correct? And when you install the drivers with KFU does that contain the fastboot drivers? Or should you download SDK platforms tools which contains both? And then run fastboot commands to flash a recovery? If so, is there a good tutorial for someone that does not follow directions well?
Click to expand...
Click to collapse
Yes, adb and fastboot are mutually exclusive but the same drivers should work for each. You can try the drivers located HERE, or read the topic on understanding driver installation located HERE.
Of you are still unsuccessful in communicating with the device in fastboot while using fastboot commands, you may have to restore it with Firekit using the "shorting trick".
OK, here is an update. I was able to get the device into recovery and TWRP. Not sure what I did differently other than maybe standing on one foot, facing south and staring at the stars, but it worked. When all of this started it was right after my son updated the software to 6.3.2 via wifi, maybe something went wrong. So last night I was able to flash 6.3.1 back to the device and was told that it was done succesfully. Using adb I can see the device in recovery and the shell lsiting is ~ # ←[6n which I guess is good as it said there was no shell before. So now my question is could it possibly be a corrupt bootloader on the device as well as it was hung at the fire logo. If so, do I need to reinstall the stock bootloader and if so where do you find it or does it come with the software flash?
I have succesfully got the update file on the kindle, did all the wipes selected install and now seems to be hung at veryfing filesystem and partitions sizes. Can someone tell me how long a flash should take or is something wrong? Since I have never done this before I have no idea.
Hello, excuse my bad English, but I need emergency.
I have a KFHD by certain situation is in a loop recovery system. As you know, this loop is that the device can not boot and will only return to the menu.
I managed to do a "factory cable", but this is where the problem comes: Apparently the factory cable works well, then send my device to "fastboot mode", but my PC does not dectecta well. I mean, my PC only detects it as "unknown device". I installed the same driver offered here, and I've also installed the USB ADB drivers from SDK, but my device still does not appear to work. So I come to you, hoping you can help me, obviously I can not run any programs to my KFHD restabilizar if the PC detects me. Actually this process should be easy, since it is only a matter of using the "KFHD SRT," but before I solve the problem on the drivers.
Oh and by the way, as data when my KFHD is connected to the PC in "fastboot" mode, a constant sound is heard, that sound you hear when Windows detects a device, but repeatedly. Also, when I go to "device manager" is flashing continuously when connected my KFHD. The device I can find the part that says "Generic USB Hub", but it is listed as unknown, and I can not access it to manually assign the controller. I hope this can help as a reference, I am very desperate because I thought the factory wire going to solve everything easy. Also connected the regular cable when it's in fastboot mode, but it does not detect it.
Thanks if you are paying attention to this, and expect a response. Nice day :crying:
OK so to make this clear you can get into recovery still or are you stuck in fastboot now? If you can get into recovery it is a lot easier to fix as you just have to push a ROM onto the device assuming we can get the drivers to install. Or did you mean stock recovery?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so to make this clear you can get into recovery still or are you stuck in fastboot now? If you can get into recovery it is a lot easier to fix as you just have to push a ROM onto the device assuming we can get the drivers to install. Or did you mean stock recovery?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering and for your time.
I commented . my KFHD is has the red triangle, and constantly sends me to " kindle fire recovery system " where options appear : reboot your kindle , reset to factory defaults . Neither of these options is used correctly because it always ends up making a loop to the menu. But still , you can enter this mode every time I turn off the computer, and I can also come to whenever fasboot mode with the cable. I guess it 's a good sign .
The downside is that my PC does not detect my KFHD in any way. But reality itself but only detects an unknown device in fastboot mode . But does not detect it well, and the message appears continuously me usb device not recognized .
Already tried all usb desisntalando drivers and re- install and got the same result. Now I tried to do the same with two other PCs, and continues with the same. I do not know what could be . I clarify that I built my own "cable factory" , I have reviewed in several places and it seems that I did well, ootherwise you could not put in Fastboot mode.
There's a possibility that your fastboot cable may have shorted out the USB port... If it keeps saying something like USB device not recognized that's bad. If it can't be detected in fastboot as a Tate,otter,or jem device then I would think about getting amazon to give you a free replacement.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
This KF7HD is NOT rooted and never has been. A week or so after they pushed out the last OTA update, the Kindle will only boot to the Kindle Fire colored logo screen. I never turned on debbuging before this boot stuck issue occrued. Once again, ADB was NOT TURNED on and I'm unable to boot the kindle to turn it on. I do have the USB drivers installed, SDK, ADB and all that jazz installed.
With normal USB cable plugged in and Kindle stuck on it's logo screen, the computer see's the Kindle as a Portable Devices "MTP USB Device". With a purchased fastboot cable plugged in, the computer see's the Kindle as a Portable Devices "soho-pvt-prod-07" when it boots into FastBoot mode. Computer is Win7 64bit Professional.
I'm just looking to get this thing restored back to factory so the wife will get off my back! So...am I screwed because debugging was never turned on or does that not matter when using FastBoot.
Thanks for the help. I've been reading and working on getting this fixed for the last three nights.
Thanks,
Dan
Debugging is only for ADB, not fastboot. Try downloading the stock bootloader (may not be required), boot, recovery, and system images and flash them to your Kindle Fire device using fastboot.
To do this, copy the stock images to your platform-tools folder where your fastboot.exe file is located. Now flash the images.
If you need the commands to flash them, just ask me! I'll be happy to help!
Hope I helped you,
Nick aka phiftyopz
Sent from my iPhone 4 using Tapatalk