Hi,
I bricked my kindle after I accidentally used an app for a different Kindle. It boots up with the orange logo, then blue artifacts flash and it goes blank.
I purchased a Factory Cable from ScOrPn and it boots up into flashboot mode. At first, it installed the wrong driver entitled "adb interface device" or something. Adb wouldn't recognise it. I uninstalled the first driver, and I replaced it with a driver which had worked for me previously entitle "Adb composite interface device" <not exactly but it's the composite part that's important, I think. Anyway, I thought that would fix it but it doesn't. Adb doesn't recognise it so I can't unbrick it. Any help would be greatly appreciated.
Things that I have tried:
Installed composite interface driver
Kill-server
EDIT: Hi, after reading for several hours I installed KindleFireAide and it seems to be doing the job.
no adb recognition
Neither the standard cable works for kindle fire hd KFFA (kindle fire hd first aide) it does not find path since adb is not recognizing the unit and using homemade factory cable still does not recognize it . Unit starts system recovery and reboot but fail each time. KFFA path not found while running program. Any ideas?
Related
I'm having issues getting adb and fastboot to work with my kindle fire hd 7in. When I plug it into my computer with a factory cable, my kindle goes into the fastboot screen, but neither adb nor fastboot can find it. One possible reason for this is that my kindle appears in device manager as "Android ADB Interface", not "Android Composite ADB Interface". Everything I can find in many different forums says that it is supposed to appear as "Android Composite ADB Interface". Is this actually a problem? And if so, how can I fix this? I tried uninstalling and reinstalling the drivers multiple times, but it still doesn't connect with adb.
http://forum.xda-developers.com/showthread.php?t=2162986
Hi
I have 2 Kindle Fire HD 7 inch. The 16GB is rooted and can run ADB commands from the latest FirstAide. The other is a new 32GB (arrived today) and I am trying to root it.
In XPs admin tools/computer management, the Android Composite ADB Interface driver is shown. In Properties/general, the rooted device is shown as working normally, whereas the unrooted device is shown as "Currently, this hardware device is not connected to the computer. (Code 45)"
Obviously, trying to use FirstAide to root the new device won't work if ADB isn't working.
As the PC installation is the same, and even the same USB data is being used, there must be something different with the new device. I can't believe that the storage size plays a part so what should I look at? ADB is turned on in the new device (more/device/ADB).
I do have a factory cable but don't know how that can be used in this instance. The new device seems to work normally, and both device and PC have been rebooted/reset to no avail.
Can anyone help or does it look like the device is faulty?
edit: the new device was v7.2.2 but updated itself soon after to 7.2.3 which is the same as the rooted 16GB device
I just used the factory cable and reset the device which went into fastboot mode but didn't respond to any fastboot commands. Switching off and replacing the factory cable with standard data cable saw it boot normally (I thought the boot mode was persistent until reset?)
Maybe try a factory reset on the new one and then turn off wifi until you root it.
Sent from my KFTT using xda premium
If you connected the 32gb kindle before enabling adb at any point you'll want to UNINSTALL its drivers from device manager on your PC and upon reconnect your PC will install the adb version of these drivers assuming adb is enabled.
Let me know how this works for you.
Sent from my KFTT using xda app-developers app
Thanks for the replies. I'm a little confused.
Eventually, I uninstalled the drivers from the PC. I found I couldn't install the drivers using the new FirstAide, I got an error message, so I used the old FirstAide and the drivers installed no problem. From there I could get to root. :laugh:
However, now I find that the old device isn't seen by ADB whilst the new one is..... it's as if the drivers are device specific.
Can anyone explain this to me? In my mind, the drivers, once installed correctly should work for all devices. At the moment, I'm faced with uninstalling/reinstalling drivers whenever I want to swap devices.
victorlugo do you literally mean that if you charge up the device without enabling ADB then you won't be able to install the drivers? As it is, enabling ADB was one of the first things I did, as it was my intention to root it immediately and transfer data from the 16GB model using Titanium.
well, I now have 5 drivers installed covering the 2 devices:
2 x Android ADB Interface
2 x Android Composite ADB Interface
1 x Tate-PVT-08
anyone have any ideas why this might happen? Each device responds to ADB ok, but they use separate drivers
I'm trying to help a lady that works at my daughter's daycare with her Kindle Fire HD 7. The Kindle is stuck on the logo screen. I've read numerous threads here, to understand what I need to do to restore the kindle to factory settings. I'm having an issue however identifying the Kindle from my PC. I'm trying to attach the Kindle to a old Dell D610 latitude laptop that is running Windows XP SP 2. I've installed Andriod Studio and via the Andriod SDK Tools (SDK Manager application) I've installed ADB and FASTBOOT.
I started with the regular cable that comes with the Kindle. I powered the Kindle off, by pressing the power button for about 10 sec and then plugged it into my computer. The computer did not recognize the device, however, the screen does turn on and show the kindle fire logo in white and orange.
After reading through some threads, I purchased a fastboot cable. I then attached the kindle with the fastboot cable, but turning off the kindle and plugging it into the usb port. This time the kindle turned on, and then went into fastboot mode on the kindle screen. In device manager, the kindle shows up under "other devices" and it comes up as "Tate-PVT-08". When I go to my cmd prompt and try to type in "adb devices" I don't get any devices present. When I go type in "fastboot -i 0x1949 getvar product", I also do not get any devices.
here's the things i've tired:
1.) In the device manager I've tried to uninstall and reconnect the device. Same thing happens every time, I just get the device to reappear as Tate-PVT-08 and I'm not able to access it via fastboot or adb.
2.) I've tried to download the google usb drivers. When i try to navigate to them from the device manager for the Tate-PVT-08 device, it tells me their are no drivers for this item.
3.) I've tried to install the kindle drivers via the SDK Manager, however, windows still does not recognize the device or give me an option to select Kindle as the type of device I am connecting in the driver selection screen in the device manager.
So my question is, how can I jut get my kindle recognized by my PC so that I can go through a process to re-image the thing?
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
For full access please register an account on XDA.
Stand by
Good luck
I'm trying to help a lady that works at my daughter's daycare with her Kindle Fire HD 7. The Kindle is stuck on the logo screen. I've read numerous threads here to understand what I need to do to restore the kindle to factory settings. I'm having an issue however connecting to the Kindle from my PC. I'm trying to attach the Kindle to a old Dell D610 latitude laptop that is running Windows XP SP 2. I've installed Andriod Studio and via the Andriod SDK Tools (SDK Manager application) I've installed ADB and FASTBOOT.
I started with the regular cable that comes with the Kindle. I powered the Kindle off, by pressing the power button for about 10 sec and then plugged it into my computer. The computer did not recognize the device, however, the screen does turn on and show the kindle fire logo in white and orange when it is plugged in.
After reading through some threads, I purchased a fastboot cable. I then attached the kindle with the fastboot cable, by turning off the kindle and plugging it into the usb port. This time the kindle turned on, and then went into fastboot mode on the kindle screen. In device manager, the kindle shows up under "other devices" and it comes up as "Tate-PVT-08". When I go to my cmd prompt and try to type in "adb devices" I don't get any devices present, just a blank line. When I go type in "fastboot -i 0x1949 getvar product", I also do not get any devices and it says <waiting for device>.
here's the things i've tired:
1.) In the device manager I've tried to uninstall and reconnect the device. Same thing happens every time, I just get the device to reappear as Tate-PVT-08 and I'm not able to access it via fastboot or adb.
2.) I've tried to download the google usb drivers. When i try to navigate to them from the device manager for the Tate-PVT-08 device, it tells me their are no drivers for this item.
3.) I've tried to install the kindle drivers via the SDK Manager, however, windows still does not recognize the device or give me an option to select Kindle as the type of device I am connecting in the driver selection screen in the device manager.
So my question is, how can I jut get my kindle recognized by my PC so that I can go through a process to re-image it? Are there specific drivers i can install for the windows xp os for kindle?
Hello, I have an Kindle Fire HD 7 inch, which is in a boot-loop due to my failed experimentation with ROMs. I purchased a fastboot cable from amazon, and I can successfully boot in to fastboot mode. The problem lies when I try to access the device via fastboot.
When I first plugged the device in, running 'fastboot devices' returns no devices, so I installed the Google USB driver via the SDK Manager. Updating the driver, and rebooting the Kindle to fastboot mode was again unsuccessful. I tried this with 'Android ADB Interface' and 'Android Composite ADB Interface' So, after digging around on the Amazon website, I installed the Amazon Kindle Fire ADB Drivers, and tested both the included drivers, to no avail. Typing 'fastboot devices' returns an empty linespace, then the command exits.
I need to restore my Kindle to factory settings, as it will soon be my primary tablet device. Any help?
Thanks.