I was gonna load my kindle fire hd with cm 11... The file got corrupted and now I can only go into twrp. I tried adb sideload but my computer doesn't recognize my device as a kindle fire hd, it just says unknown device. I then tried to change the driver and it kept failing. Can I fix it or is it a lost cause now?
Do you have cm11 zip in your internal storage? If not, reload the drivers in windows. Do you have a fb cable?
Related
Hi all,
Managed to get my device rooted thanks to the excellent information on the forum.
But I'm trying to mount my device to my Windows 7 64bit latop from which I did my root from as a USB drive to show in My Computer. I want to transfer some files onto it. But for some reason it is not detecting it as this. I've installed, uninstalled the Kindle Fire HD driver "Kindle Fire ADB Drivers". But still nothing?!
Many thanks for any help
First off I have tried everywhere to look for what could be wrong and then fix the issue that I am having with ADB recognizing my Kindle Fire HD, so I am sorry that I have to create yet another thread with this question/issue.
I, like many others, bricked my Kindle Fire HD 7''. I rebooted my Kindle and it was stuck at the Boot Screen just looping the same animation again and again. So I purchased one of SkOrPn's Factory Cables (shoutout) and it worked perfectly.
I plugged in my Kindle and it entered into Fastboot mode with no hassle. The drivers I previously installed to do the root were still on my computer and recognized my Kindle in my device manager, but for some reason ADB will not see it.
I have uninstalled the drivers and reinstalled them. They are of course the Kindle Fire ADB Drivers file. I have installed the correct Android SDK files and set up the environement, etc and followed a guide to connect my Kindle to ADB
I have done the appropriate edits to the adb_usb.ini file in the "C:\Users\[username]\.android" folder. By that I mean I added the "0x1949" line to the end of the file (both with a lowercase and uppercase 'X')
I have also edited the file 'android_winusb.inf' file by adding the appropriate lines to it then trying to update the driver with the usb_driver folder.
During this whole process I have also rebooted my computer and Kindle Fire HD (by unplugging it and holding down the power button) several times. And have tried to make sure and get the most recent files by doing an 'android update adb' and of course just downloading the most recent Android SDK
I tried to make this detailed so not as to leave out anything... again, I'm really sorry I have to even post about this, but I'm truly at a loss for what to do and I would appreciate any help possible..
+1 I have the same problem
Misterowl said:
+1 I have the same problem
Click to expand...
Click to collapse
I think I might have found a solution... I was going through some threads and saw the Kindle Fire Utility... Well I got it and even though it says ADB Status: Offline, and adb still doesn't recognize it no matter what I do, I was able to change it to different bootmodes! Though I accidentally put it in Recovery mode and had to figure out how to change it back to Normal/Fastboot.
Anyway, I figured since even though ADB didn't see my Kindle the Kindle Fire Utility did, which was great! Didn't help me fix my Kindle, but I then found the restore tool by onemeila and it too didn't see my Kindle, but I decided to try and Restore my Kindle anyways just to see what would happen. After waiting a while it restored my Kindle! I just unplugged the Factory Cable, held the power down for a few seconds, turned it back on and voila! It was completely restored and back to being rooted and unbricked! Let me know if this works for you...
I'll also post if I can find out if ADB can recognize my device yet because I realized that I did not have USB Debugging enabled...
Note: In the Kindle Fire Utility I enabled Read/Write mode for my Kindle and Set the bootmode to fastboot (it was already in fastboot due to the cable though)
Oh and on The KFHD System.img Restore Tool I chose the second option.. It was the only one that worked in restoring my Kindle and it's still not fully working
Hello,
I tried to copy files into the internal storage of my KFHD from Windows 7. The copy process failed. Since I am not able to access the storage anymore.
I read the dir, but I can not remove or create new files.
I booted into TWRP und tried to fix permissions. I got an error message.
Any idea?
Regards
I'm a bit confused what you did so lemme say a few things, mounting internal storage in twrp doesn't work on second gen kindles last I checked. If you flashed cm and can't view the internal storage from windows, its because you need to uninstall the kindle portable device in the device manager and then let it scan for devices again so it can install the drivers that work with cm. Does this answer your question or am I way off base?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I think my description was not sufficient.
After installation of CM10.1 everything worked just fine. The device showed up in Windows.
I tried to copy CM10.2 and gapps to the KFHD USB drive, while doing that an error occured.
Since I do not have write access to the KFHD /sdcard anymore neither under Windows nor under TWRP.
Ah that is weird, I'd go with just pushing the files over adb and see if then problem still exists after upgrading. I have a tutorial that covers it in the kindle general section under something like recovery boot loop after flashing twrp/2nd boot loader, need to put a link to that in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hi,
I will try to push the CM zip file and the gapps to the "sdcard" directory using ADB.
I will report back tonight.
I have a Kindle Fire HD 7" device model "tate" (yes I'm sure) that I rooted, installed TWRP, and Cyanogenmod. Recently, I decided to upgrade it. After having several difficulties, I mistakenly wiped the system and data partitions, leaving with a device that has no OS. This wouldn't be a problem save for the fact that my computer has seen some of my less tech savvy times where I wasn't careful with drivers. Regularly, I'd mount the internal SD Card via the recovery's fancy ui, then transfer whatever ROM image I wanted, installed it, and voila! My computer is aware that I have a Kindle plugged in to it. In the Device Manager, it's has named it several different things, usually a heading saying "Kindle Fire" with a sub-heading saying "Android ADB Composite Interface." (I believe that was it.) I've tried manually installing the Kindle drivers with the executable and removing the actual driver file from the executable to "select from list of drivers on my computer" to no avail. ADB detects my device as booted into recovery, but I can't mount the storage from the device. I have no external access to the internal memory to put any OS on the Kindle. I've tried every option in the Kindle Unbricking Tool and KFFA. Hopefully someone can point out an error on my behalf or perhaps a solution.
After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
taatoken said:
After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
Click to expand...
Click to collapse
Bump
Solution
Here you have it:
Install manually in the windows drivers list, Fire Device -Android composite ADB interface, over KFFOWI. Then install Stock Rom via ADB. Enjoy!
taatoken said:
After sending 13 hours working, search and hitting a brick wall, I decide to post. I have full installed all drivers for the my fire (5.1.4) in an attempt to downgrade it. Been to rootjunky and gotten the supertool. Downloaded the full Android Studio. Dow loaded the kindle fire usb driver and the kindle fire HD ADB driver. Downloaded QemuRoot, root_fire. All to no help. Mutilpe computer restarts. Wipe the device and cache. Still nothing. I have used the USB cord it came with and a high quality OEM cord. Still nothing. Been to computer management in an attempt to manually install the driver there. Still nothing. I am at my wits end. As it stands, the kindle when under Amazon system recovery <3e> is not connecting to my computer when I try to apply update from ADB. The message presented by my computer is "KFFOWI-----------------------X no driver found" Any suggestion, ANY WILL BE HELPFUL!
Thank you in advance
edit1: who knew this would be harder to root than the HTC evo 3d paper clip trick
Click to expand...
Click to collapse
I have the same problem, how do you install driver manually? On Windows I have only the update driver option and when I give him the location of adb USB driver. Windows tell me that there is no driver available for the device...
Any updates? I hit the exact same problem, tried everything online, still I cannot find a suitable driver for the "Kffowi" (with exclamation mark)..
Driver install
Go to device manager, right click on KFFOWI, click on update driver. Click Browse my computer. On the next screen, click the bottom option, "Let me pick from a list of device drivers on my computer".
Scroll down and click on Fire Devices
Look for "Android Composite ADB Interface" and select it, then hit next.
Driver will install, confirm that you want windows to use the driver, and bam. Done.
Problem solved
Running LineageOS 12.1-20181218-UNOFFICIAL-ford. amonet-ford-v1.4.1 installed on PC and rebooted. There isn't even the sound that a new USB-device is connected nor anything happening in the Windows device manager when pluggin in KFFOWI. Enable Android debugging is grayed out. How should I proceed, if I wan to upgrade to [ford,austin] Lineage-14.1 [17 JAN 2021]?
LineageOS 12.1-20181218-UNOFFICIAL-ford is working fine, but has become very slow.