Related
Hey,
I keep on getting the "USB Device not recognized" message on my rooted Kindle Fire HD with stock ROM 7.2.3.
Tried on several Windows 7&8 machines to no avail. The USB ports are checked and working with an external harddrive, mouse etc.
Does anyone have a clue? It actually seems to be an issue on the Kindle device itself and isn't reporting itself as an existing device?
I tried several things, like:
- Holding power button 20+ sec while the USB is connected.
- Reboot PC etc.
- ADB, verifying the drivers the 0x1949 etc.
Nothing helps. Please let me know if you know the solution!
Thanks
Sector!
sector123 said:
Hey,
I keep on getting the "USB Device not recognized" message on my rooted Kindle Fire HD with stock ROM 7.2.3.
Tried on several Windows 7&8 machines to no avail. The USB ports are checked and working with an external harddrive, mouse etc.
Does anyone have a clue? It actually seems to be an issue on the Kindle device itself and isn't reporting itself as an existing device?
I tried several things, like:
- Holding power button 20+ sec while the USB is connected.
- Reboot PC etc.
- ADB, verifying the drivers the 0x1949 etc.
Nothing helps. Please let me know if you know the solution!
Thanks
Sector!
Click to expand...
Click to collapse
Well, it seems like you forgot about one very important thing: the USB!
Use only the original cable that came with the Fire. Not anything else! There is a reason why the company gives a USB cable when you buy the device, you know.
Cable isn't the problem
gadgetroid said:
Well, it seems like you forgot about one very important thing: the USB!
Use only the original cable that came with the Fire. Not anything else! There is a reason why the company gives a USB cable when you buy the device, you know.
Click to expand...
Click to collapse
Unfortunately I already tried with the official cable. Same problem. Would a reset to factory defaults resolve this? And do I then keep my root access?
any luck with this?...i just got a Kindle Fire HD and am having the same problem...ADB drivers seem to be working fine, and the Kindle is rooted, but it does not show up at all in Windows Explorer, so i can't transfer anything to it
also, i've tried uninstalling & reinstalling the ADB drivers several times, but still nothing in Win Explorer...one thing i notice, even though i delete/uninstall all Kindle drivers i see in Device Manager, including "Hidden Devices", when i go to reinstall the drivers, i get a pop-up windows saying ADB drivers are already installed, and asking if i would still like to re-install the drives...how do i delete everything relating to the Kindle on my PC, so that i can do a completely fresh install of the drivers?
Nope still nothing.
phunzoid said:
any luck with this?...i just got a Kindle Fire HD and am having the same problem...ADB drivers seem to be working fine, and the Kindle is rooted, but it does not show up at all in Windows Explorer, so i can't transfer anything to it
also, i've tried uninstalling & reinstalling the ADB drivers several times, but still nothing in Win Explorer...one thing i notice, even though i delete/uninstall all Kindle drivers i see in Device Manager, including "Hidden Devices", when i go to reinstall the drivers, i get a pop-up windows saying ADB drivers are already installed, and asking if i would still like to re-install the drives...how do i delete everything relating to the Kindle on my PC, so that i can do a completely fresh install of the drivers?
Click to expand...
Click to collapse
Hmmm the ADB drivers aren't working for me, so you are one step closer! I still have the problem and am still considering a full reset, but afraid of bricking....
Both of you, download this file and install the drivers over the old ones, see if it helps: https://dl.dropbox.com/s/vprplelu9zx7s2o/kindle_fire_usb_driver.rar?dl=1
seokhun said:
Both of you, download this file and install the drivers over the old ones, see if it helps: https://dl.dropbox.com/s/vprplelu9zx7s2o/kindle_fire_usb_driver.rar?dl=1
Click to expand...
Click to collapse
Thanks
Doesn't work
Unfortunately it doesn't help. I am going for a hard reset soon.... Will report back here.
seokhun said:
Both of you, download this file and install the drivers over the old ones, see if it helps: https://dl.dropbox.com/s/vprplelu9zx7s2o/kindle_fire_usb_driver.rar?dl=1
Click to expand...
Click to collapse
didn't help...i even spent several hours doing a Win7 "Repair Install", thinking that would help...but disappointingly, after the repair, same issue....Win7 does not recognize it as a mass storage device, and doesn't show it in Win Explorer...i did install the ADB drivers, and do have ADB access, just nothing through Win Explorer :crying: .... on another computer also running Win7 x64, the Kindle shows up fine in WinExplorer
aaaaarggggghhhhh....:crying: i did a totally fresh install of Win7 x64 on a brand new hard drive...and this computer still won't recognize the Kindle as a mass storage device?!?!?....so i have to assume there is something wrong with the computer...but ADB works, and i was able to root the Kindle with this computer
Be sure ADB is enabled on the device itself if you have ever wiped the sdcard or have a custom ROM installed.
Sent from my Amazon Kindle Fire HD using xda app-developers app
i got the same problem, in my thread i also posted many screenshots but nobody still has found a solution....
i was never able to get one of my PCs to recognize the KFHD as a USB storage device, but at least ADB works...so i've decided to just wirelessly connect (w/ AirDroid, WiFi File Transfer,etc.) to the Kindle for file/media transfers...an even better solution than using a USB cable :victory:
on device manager what do you see?
(i solved my problem doing that http://forum.xda-developers.com/showthread.php?t=2167129&page=4)
My device still doesn't work
For me it still doesn't work. Didn't do a full reset, because I am too scared I will loose my Root access which will make my device completely useless...... Going to contact Amazon support.
bencio28 said:
on device manager what do you see?
(i solved my problem doing that http://forum.xda-developers.com/showthread.php?t=2167129&page=4)
Click to expand...
Click to collapse
I don't see ADB stuff.... ADB doesn't work anymore either....
I've noticed with other devices that I've rooted that windows is VERY tempermental when it comes to adb and windows recognizing any android device. If you have everything installed correctly, I have actually found sometimes simply disconecting your kindle from your computer and rebooting both and then reconnecting helps sometimes. Like I said windows is VERY tempermental. Worked for me more than once with my phone and my kindle.
from my Viped out one x
Two Kindles- One does and one doesn't
DroidIt! said:
I've noticed with other devices that I've rooted that windows is VERY tempermental when it comes to adb and windows recognizing any android device. If you have everything installed correctly, I have actually found sometimes simply disconecting your kindle from your computer and rebooting both and then reconnecting helps sometimes. Like I said windows is VERY tempermental. Worked for me more than once with my phone and my kindle.
from my Viped out one x
Click to expand...
Click to collapse
Funny thing is, I have two KFHD 7" both rooted. Windows sees one but not the other. Device manager shows Kindle Fire- Android ADB Interface on the one not showing up in Explorer and shows same plus Portable Device-Kindle Fire on working one.
Have been able to install 2nd boot loader on the working one and CM 10, but can't do anything else with the other. I have a fast boot cable and have restored it back and wiped several times to no avail.
One thing I noticed, The one that doesn't recognize in explorer only shows to have 12.9 GB space while other working one shows 27.9Gb space.
I have been successful with a KFHD 8.9, KF 7" 1st gen and KF2 and (1) KFHD 7" in rooting, 2nd boot loader and custom ROMs (along with many other Android devices), but not this one 7" HD.
This thing is driving me crazy.
Help Plz
EDIT: Okay going thru my notes I think that I have figured out what has caused this (still don't know how to fix). It seems that after the first root, wifi was on and it updated itself to 7.3.1. It is only after this, that I can't get ADB and flash boot loader or files to SD card. Using KFHD rescue tool and KFFirst aid I have flashed back to 7.2.3 with root (tried both) , but still can't get ADB. Fastboot with factory cable works fine though. With the kindle booted up on 7.2.3 rooted or 7.3.1 non root, Windows still doesn't see the device. Device manager shows ADB device but not the SD card part of the device. Is there any way to recover everything back to stock (non root) to start fresh?
Finally Fixed
Joem68 said:
Funny thing is, I have two KFHD 7" both rooted. Windows sees one but not the other. Device manager shows Kindle Fire- Android ADB Interface on the one not showing up in Explorer and shows same plus Portable Device-Kindle Fire on working one.
Have been able to install 2nd boot loader on the working one and CM 10, but can't do anything else with the other. I have a fast boot cable and have restored it back and wiped several times to no avail.
One thing I noticed, The one that doesn't recognize in explorer only shows to have 12.9 GB space while other working one shows 27.9Gb space.
I have been successful with a KFHD 8.9, KF 7" 1st gen and KF2 and (1) KFHD 7" in rooting, 2nd boot loader and custom ROMs (along with many other Android devices), but not this one 7" HD.
This thing is driving me crazy.
Help Plz
EDIT: Okay going thru my notes I think that I have figured out what has caused this (still don't know how to fix). It seems that after the first root, wifi was on and it updated itself to 7.3.1. It is only after this, that I can't get ADB and flash boot loader or files to SD card. Using KFHD rescue tool and KFFirst aid I have flashed back to 7.2.3 with root (tried both) , but still can't get ADB. Fastboot with factory cable works fine though. With the kindle booted up on 7.2.3 rooted or 7.3.1 non root, Windows still doesn't see the device. Device manager shows ADB device but not the SD card part of the device. Is there any way to recover everything back to stock (non root) to start fresh?
Click to expand...
Click to collapse
Problem solved:
Here is what I did to fix the problem.
If you haven't preformed this fix for windows, do this first. http://forum.xda-developers.com/showthread.php?p=36373627
First plug in device to computer and navigate to device manager. Then go to kindle fire and expand to show Android ADB Interface. Right click on it and select "Scan for Hardware changes". Let it run. If it finds nothing don't worry. Then right click again and select update driver. Navigate to locate drivers myself. If you have KFFirstAide or other utility locate to where the ADB drivers are in that file and select ok. It will go through the process and install the drivers. After doing this you should now be able to see the device through explorer and transfer files.
I now have 2nd bootloader and CM 10.1 (Hashcode) up and running great. Hope this helps.
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Crossvxm said:
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Click to expand...
Click to collapse
Many Android devices, once depleted of battery, will not boot properly until the battery is anywhere from 20% or above. Try letting it charge longer. To speed up the process, use a wall adapter from your other devices. it will pump more voltages. As you said, there aren't any mods I can see that would cause bootloops or bricks.
Try charging it for a good hour, not booted up. To make sure it has charge. Then try to turn it on. This is very weird though, first time I heard a Android device acting up like that.
Sent from my air conditioner unit running CyanogenMod
I left it charging from 5am to now and it hasn't charged a thing because when I disconnected it and tried to turn it on it turned off after 7 minutes of the Kindle Fire logo. I also noticed that the reflection animation on the logo moves faster than it usually does. It just stays there. I'm guessing my only option would be a factory cable of some sort. No matter how many 20 second power button thing I use, it just stays stuck on the logo, as if something had damaged the firmware somewhere, but how? I will try to charge it once more for a while and see.
EDIT : I made my own "factory cable" and got it to fastboot. Now what can I do to restore it???
Hopeless???
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Crossvxm said:
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
View attachment 2012991
View attachment 2012994
Click to expand...
Click to collapse
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
seokhun said:
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
Click to expand...
Click to collapse
I tried and the System Recovery Tool does not detect the device. It stays at "waiting for device"
One step forward and two steps back
Okay each time I advance, I am stuck with a new obstacle. I got ADB working (can use its commands) but my device isn't detected when I use the command "adb devices." As mentioned before, in Device Manager > Other Devices, Kindle appears as Tate-PVT-08, updating that "driver" is no use, and here I am Kindle-less once again. This is like a nightmare. Had I caused this issue by flashing a rom, or second bootloader, I'd probably give up and say "oh well I read the warnings, went along and I messed it up." But the case is that I did nothing to cause this, it only ran out of battery which happened once before and that time there were no issues starting up. I've searched left and right, high and low but cant find a way to now get this thing detected so I can see what I can do next. Can anyone please give me a list of what to do to get out of this Kindle Fire logo?
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
dugoy13 said:
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
http://translate.google.com/translate?hl=en&sl=ja&u=http://ameblo.jp/conpe/entry-11437514328.html&prev=/search%3Fq%3DTate-PVT-08%26biw%3D1366%26bih%3D673
Is there any specific place/thread with the drivers to the fastboot?
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Possibly Solved
Crossvxm said:
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
Is there any specific place/thread with the drivers to the fastboot?
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
An other option
Crossvxm said:
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
Click to expand...
Click to collapse
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
CVanB said:
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
Click to expand...
Click to collapse
It updated randomly from 7.3.1 to 7.4.1 on May 30th (aprox 5 days ago) that same day I rooted it after it erased my root with the same guide I used for 7.3.1 that was based on 7.4.1. It worked perfectly, but around that time I never let the battery die during those few days. In record, I've only let the battery die once before, this time makes it 2 times total. The cable I made is from a Samsung, I made it using instructions on making it for the Kindle Fire HD 7 specifically, although as I've heard, you may be right. But when I research that "device" (Tate-PVT-08) on google, the Kindle Fire pops up in search results, but none are really helpful. Example, the bottom of this thread I'm posting below, people have similar issues and the "Tate" thing:
http://forum.xda-developers.com/showthread.php?t=1930656
Same problem
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
dugoy13 said:
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari said:
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
Click to expand...
Click to collapse
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
DroidIt! said:
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
Click to expand...
Click to collapse
Yeah I tried that and even my own little invention. But I give up. I'm just scrapping the whole project. Its useless, I'll just have to get me a Nexus 7, I don't want to get stuck with another brick. Amazon is pretty ridiculous. Their system is unstable, their device is crap. I have read about problems like this on these things everywhere. Whether its the charging refusal, 0% battery, not starting up, not having Google Play, root headaches and nearly impossible restore scheme, these things are well worth their cheap price.
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
stunts513 said:
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for trying. But if you'd see what I did to the poor thing out of frustration you'd call me nuts. Its really not coming back now...
Hello everyone. Here's my story.
I got my Kindle, worked with it for a while, then successfully rooted it (my PC running on Windows XP stopped seeing it, but meh, that wasn't a problem at all). Then I wanted to try something new so I installed TWRP and used Cyanogen Mod and Paranoid Android (didn't really like the second one) so I decided to switch to Kinology.
I went to recovery mode, and then swiped whole system. >_< Like everything. And then I panicked and started making mistakes.
I didn't use adb sideload (silly me) but instructions from here http://forum.xda-developers.com/showthread.php?t=1951254. And one more mistake - I didn't downgrade.
So I got my Kindle in a pretty odd state - when switched on it showed me orange "Kindle Fire" logo which was blinking forever.
And my PC wouldn't recognise it anymore. It wouldn't see any Kindle device but something unknown. And it wouldn't see drivers I tried to re-install over and over again.
So I made another mistake - sent my Kindle back to the shop where I ordered it (not Amazon, an online shop here). They weren't able to do anything so I'm getting my bricked device back (soon, I hope).
So, here's what was the state of my device before I sent it back:
1) blinking orange "Kindle Fire" logo when switched on;
2) when plugged in PC with fastboot cable showing "Fastboot" logo on screen;
3) PC wouldn't recognise this device anyhow.
I'm a slowpoke, I know, I should have asked long ago, but late is still better than never.
I don't have my Kindle yet so I can't work on it for a while. But I will appreciate your advices.
Most terrifying question now is can it possibly be working again (techs from that shop said they could do nothing and it's so terribly bricked...)? Any OS would do just fine, really.
Thank you in advance.
ValeriaD said:
Hello everyone. Here's my story.
I got my Kindle, worked with it for a while, then successfully rooted it (my PC running on Windows XP stopped seeing it, but meh, that wasn't a problem at all). Then I wanted to try something new so I installed TWRP and used Cyanogen Mod and Paranoid Android (didn't really like the second one) so I decided to switch to Kinology.
I went to recovery mode, and then swiped whole system. >_< Like everything. And then I panicked and started making mistakes.
I didn't use adb sideload (silly me) but instructions from here http://forum.xda-developers.com/showthread.php?t=1951254. And one more mistake - I didn't downgrade.
So I got my Kindle in a pretty odd state - when switched on it showed me orange "Kindle Fire" logo which was blinking forever.
And my PC wouldn't recognise it anymore. It wouldn't see any Kindle device but something unknown. And it wouldn't see drivers I tried to re-install over and over again.
So I made another mistake - sent my Kindle back to the shop where I ordered it (not Amazon, an online shop here). They weren't able to do anything so I'm getting my bricked device back (soon, I hope).
So, here's what was the state of my device before I sent it back:
1) blinking orange "Kindle Fire" logo when switched on;
2) when plugged in PC with fastboot cable showing "Fastboot" logo on screen;
3) PC wouldn't recognise this device anyhow.
I'm a slowpoke, I know, I should have asked long ago, but late is still better than never.
I don't have my Kindle yet so I can't work on it for a while. But I will appreciate your advices.
Most terrifying question now is can it possibly be working again (techs from that shop said they could do nothing and it's so terribly bricked...)? Any OS would do just fine, really.
Thank you in advance.
Click to expand...
Click to collapse
You will be able to fix it once you have a fastboot cable, so tell me when you have gotten your kindle back.
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
itouchables said:
You will be able to fix it once you have a fastboot cable, so tell me when you have gotten your kindle back.
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
Yay, there's still hope :cyclops:
Okay, as soon as I get my Fire back I'll contact you. Thanks.
..
---------- Post added at 02:49 PM ---------- Previous post was at 02:41 PM ----------
itouchables said:
You will be able to fix it once you have a fastboot cable, so tell me when you have gotten your kindle back.
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
is a "fastboot" cable the same as the cable that came with my kfhd 7"?
if not what is the difference? and where can i get one?
JeremySwagS said:
..
---------- Post added at 02:49 PM ---------- Previous post was at 02:41 PM ----------
is a "fastboot" cable the same as the cable that came with my kfhd 7"?
if not what is the difference? and where can i get one?
Click to expand...
Click to collapse
Yes a fastboot cable is different, you can buy one from scorpion, or you can make your own.......
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
In the same position.
I had successfully rooted my Kindle Fire HD 7" via this http://forum.xda-developers.com/showthread.php?t=2351201
I was then going to install a mod via this method: http://forum.xda-developers.com/showthread.php?t=2271909
Was in one of the twrp screens when I was called away from the house. My wife let my neighbor and her pestilential 6 year old son into the house. Apparently, this little budding genius found my kindle and just randomly hit everything. How I didn't wind up in custody is beyond me.
When I got back to the house, I picked up a Kindle that would just cycle into twrp (orange logo/blue logo a few times and then twrp - nothing else). Windows no longer recognized the device. I got a Fastboot cable and used the KFHD Recovery Tool.
http://forum.xda-developers.com/showthread.php?t=1951254 which reported itself
I first started with option 4 - Erase cache and user data. I got "OKAY" messages on both steps. Followed by "GONE - Hope you made a backup!"
Then I went on to option 2 - Restore Factory Rooted with Super SU.apk, Apex Launcher and Play Store
Got message "Sending System 907264 kb"
OKAY *some number of seconds that the procedure took and WELCOME BACK!
I swapped the cable from the Factory cable to the normal Kindle Fire usb cable and selected option 6 Reboot normally.
Now I'm stuck in a normal straight orange Kindle Fire boot loop. Any ideas how to fix this? I've been up and down the forums and being a newb and, relatively speaking, an idiot - I've failed to find my way forward.
Try using kindle fire first aid this time around, I have a feeling it will work. Still need to use fastboot cable to get into fastboot but other than that it also has a restore stock system images feature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Try using kindle fire first aid this time around, I have a feeling it will work. Still need to use fastboot cable to get into fastboot but other than that it also has a restore stock system images feature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the help Stunts! I try using KFFirstAide and it gets to *Daemon started successfully* and then nothing. Any operation where KFFirstAide accesses the Kindle - it just goes to a blinking cursor. Nothing ever pops up on the Kindle itself - it just stays on the Fastboot screen.
I've tried both the repair function for the KF HD 7" and going in through diagnostics to attempt to repair.
If I use the factory cable, it goes straight to Fastboot. If I use a normal cable, I cannot enable any ADB functions as the device just continues to loop the orange Kindle Fire boot screen. I am unable when connected via the factory cable to regularly
The system can not find the file specified. The kindle is not responding to simple fastboot commands.
Product: Tate-PVT-08
Below that it says if you see output above this note then fastboot is enabled and you can safely proceed with a restore.
So, I reinstalled these drivers http://forum.xda-developers.com/showthread.php?t=2072359&nocache=1 - as it looks like drivers are the problem. Both before and after installation, on my device manager instead of Kindle Fire, it reads Samsung Phone and below that Android ADB Interface with a yellow triangle and comment "Device can not start" (Code 10).
So, if this Kindle were a murder scene, I'm guessing there'd be a big pool of blood somewhere around this driver issue (assuming I'm not about to be clunked on the head by some other issue and my dead body heaved into a closet to spill out onto my wife later).
I see Kindle Fire Utility has a fix for this, but some of the KFU posts have said it's for 1st gen only, so I'm a little far down the rabbit hole. Will keep reading and see if I can make some sense of this.
Sorry to be so dense, I feel like a Friday the 13th victim who refuses to die and just runs around the forest screaming with a rake jammed through my shoulder. I do realize it's poor form
Update: resolved the driver error via this post: http://forum.xda-developers.com/showthread.php?t=2306561&page=2
Now back into the KFFirstAide and let's see what happens. Results of KF First Aide are the same (although the driver on the device manager is back to reading Kindle Fire and ADB interface which is working properly)
GODS BE PRAISED!!!! Got back in via the KF HD SRT. Rolling along now. Thanks again Stunts. Really appreciate your time.
(Hilarious end note - along came an OTA update and wiped all my good work. Back to square one *Shakes fist at God*)
itouchables said:
You will be able to fix it once you have a fastboot cable, so tell me when you have gotten your kindle back.
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
Hello.
It's been a while but I got my Kindle and ready to work with it.
I'll try first aid after I charge it.
Just want to clarify few steps.
I have a "clear" recently re-installed Windows 7. What I did was installing drivers from here http://forum.xda-developers.com/showthread.php?t=2072359&nocache=1 then steps 1-9 from here http://forum.xda-developers.com/showthread.php?t=2096888.
Do I heed QemuRoot? Or it was wrong to do these steps before ever trying to find any adb devices?
My kindle doesn't show in the list of devices, it still blinks with orange "Kindle Fire" when connected to PC via data cable and shows "Fastboot" logo when connected via fastboot cable.
What should I do now?
How do I delete my post?
I mean this one, #10.
Wait so is your device showing up in the device manager with an error?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Wait so is your device showing up in the device manager with an error?
Click to expand...
Click to collapse
No, my device isn't showing up in the device manager at all.
And it is in fastboot? It should show up as a Tate device. Though if it is showing up but without errors but fastboot doesn't detect it I would reinstall the drivers, because I have a similar problem on windows 7. Once its in fastboot use the normal USB cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
And it is in fastboot? It should show up as a Tate device. Though if it is showing up but without errors but fastboot doesn't detect it I would reinstall the drivers, because I have a similar problem on windows 7. Once its in fastboot use the normal USB cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yup, first fastboot then normal cable.
My PC doesn't seem to see kindle at all. No new devices appear when plugged neither with fastboot nor data cable. Nada.
Um OK try expanding the USB devices section in the device manager and posting a screenshot, because I'm at a loss, unless you for some reason are plugged into a USB 3.0 port, but even then I thought it would at least show up. If you don't know how to take a screenshot offhand, just hit the print screen button on your keyboard, above or near the del, pg up and such keys, then open paint and hit paste, and save it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um OK try expanding the USB devices section in the device manager and posting a screenshot, because I'm at a loss, unless you for some reason are plugged into a USB 3.0 port, but even then I thought it would at least show up. If you don't know how to take a screenshot offhand, just hit the print screen button on your keyboard, above or near the del, pg up and such keys, then open paint and hit paste, and save it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
That's how it looks like.
I'm not sure I have any USB 3.0 ports. I tried to plug into 5 different ports - result was the same.
OK do me a favor, that one that says USB composite device, open its properties and goto details, and choose hardware id's from the drop down list and either screenshot it or just write em down for me.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK do me a favor, that one that says USB composite device, open its properties and goto details, and choose hardware id's from the drop down list and either screenshot it or just write em down for me.
Click to expand...
Click to collapse
There are two IDs.
USB\VID_0E8F&PID_0022&REV_0210
USB\VID_0E8F&PID_0022
Ah I was completely off, see I recently noticed the kindle installed as a composite device when I was in windows the other day, long story short I thought u might just need to reinstall then drivers, but that is not a kindle vendor Id that I can tell, sounds more likely to be USB speakers or something upon searching Google and getting random drivers that. Try plugging this into another computer, if it still doesn't show up it could be a hardware problem, might be as simple as resoldering some joints idk.
Edit: on another note, before trying to check for a bad connection on the kindles USB plug, try booting linux and seeing if it picks it up, usually an Ubuntu live CD will do the trick, hopefully its not a hardware problem.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ah I was completely off, see I recently noticed the kindle installed as a composite device when I was in windows the other day, long story short I thought u might just need to reinstall then drivers, but that is not a kindle vendor Id that I can tell, sounds more likely to be USB speakers or something upon searching Google and getting random drivers that. Try plugging this into another computer, if it still doesn't show up it could be a hardware problem, might be as simple as resoldering some joints idk.
Edit: on another note, before trying to check for a bad connection on the kindles USB plug, try booting linux and seeing if it picks it up, usually an Ubuntu live CD will do the trick, hopefully its not a hardware problem.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My netbook runs on Ubuntu 12.04 and doesn't see Kindle as well.
*My KFHD7 will not load passed the initial, "kindle fire" logo.
*While running KFFirstAide64 runme.bat, it reads, "The system cannot find the path specified" after I try the recovery.
*In Device Manager under other devices it states, "Soho-PVT-Prod-07"; My computer is communicating with the Kindle.
*I am using a factory (fastboot) cable and my tablet is in fastboot mode as of right now.
*Last updated version known: 11.2.3.2
Is there any other program or recovery option that I can use to restore my KFHD7 to it's factory conditions? How can I get the system to "find the path specified"?
Solution!
I don't know how I missed it but here it is.
http://forum.xda-developers.com/showthread.php?t=1951254
Additional Problems...
When I run the program to recover, it reads, "<waiting for device>".
*I am using "KFHD_SRTv1.3.5" SR Tool which was recommended to me.
*I've tried using different USB ports.
*Waiting for the device proves to be pointless.
*I have downloaded the ADB driver but installing it shows no improvements.
What can I do?
That is for the Kindle fire HD 2012 edition. If you flash it to your Kindle you will Brick it.
You need this program.
http://dl.kfsowi.com/tools/kindlesuite/KindleSuite.zip
Thanks for the reply
Red_81 said:
You need this program.
Click to expand...
Click to collapse
I have downloaded the program and tried to restore my device but I ran into the same problem, "waiting for device". I've installed the device drivers as well. I checked on one of the other programs my ADB status and it is not on. I don't believe I can turn it on without getting passed the initial bootlogo.
Do I need the ADB enabled in order for a full recovery? How can I get my device to be acknowledged by this program when my computer is reading that it's there?
EDIT:
I need to restore my kindle.
While in fastboot mode, the logo has 3D orange font that says "fastboot" with a black background. There is nothing else that shows up. Before I tried to root there was green font in I think the top left corner; looked like a cmd prompt was running something (if I recall correctly)..
if you are in fast boot and stuck waiting for device you are probably having a driver problem like I had. I used fastboot on Linux instead of Windows and solved my driver issue that way.
Sent from my SCH-I535 using XDA Premium 4 mobile app
muiriddin said:
I used fastboot on Linux instead of Windows and solved my driver issue that way.
Click to expand...
Click to collapse
Sorry for the late reply. I'll try out Linux OS and see what happens. I'll let ya'll know the news :fingers-crossed:
EDIT::
So my computer crashed trying to fix my kindle; hard drive malfunction of some sort. My friend put the hard drive into his computer and it erased his BIOS. We then put in an 80GB hard drive that we got for $10, re-installed windows and tried again. Hard drive crashed crashed again. Maybe when I tried to install the drivers they were installed onto my computer instead of the Kindle?
This is an on going process but I probably won't be posting again any time soon. Maybe when I actually start programming things will be a little more self explanatory.
Thanks for all your help. This is all for this thread.
My audio stopped working randomly, which it has been doing. I figured, "no problem, I can just get a factory reset."
I rooted my kindle and used Stunts' Wallpaper Fix, so when I factory reset the Stunts Wallpaper Fix and the Root were gone, but the notification bar went in and out. After hours of frustration, I decided I'd just download CM11 because I was getting tired of the way the notification bar going funky.
I followed all of the steps of the TWRP + 2nd Bootloader Thread but it was via another source, and I forgot to add the CM11 to the Kindle and wiped OS.
Now my Kindle Fire is stuck on the blue logo, it's not responding computer wise, I've probably downloaded the Android SDK, Google USB Driver, kindle ADB drivers and Fastboot drivers about 10 million times and my kindle can recognize fastboot, the computer will not.
Kinda stuck, don't know what to do, and I'm not trying to hardbrick this. Any ideas? :crying: I've been working on this for about 5 days now and my fastboot cable came in today (i had another for when i bricked it the first time, but it's lost.) so i tried working with it for about 3 hours but my frustration is getting the best of me and the Kindle's battery life is getting the best of it.
I fixed it! I fixed my baby~! About 5-6 days later and I finally got it to work!
I'm going to assume if you bricked your kindle that hard, then you should have had a Kindle Fire driver previously, this is necessary! Do not let this be a first time install!
Here's what I did!
I deleted my drivers for Kindle.
The first step is getting your Kindle recognized. Make sure you download the android SDK (you need ADB and Fastboot)
I found a good program for that, search up "15 second ADB installer" or something like that.
Once installed, remember where your driver is (or go to Start search and search up "Amazon.com.")
Plug in your fastboot cable (if you have one) or your normal cable.
Go to Device Manager (accessible in Start search) and look for Tate-VT-08 or something like that, it's under "Other Drivers" and it won't show up unless you've wiped out your drivers.
Right click it until you can update your driver, and then look for list of previous drivers. Look for "Kindle Fire" (it's there if you've plugged in your kindle before)
Click it
and you are now recognized fastboot wise! Go girl/boy!
Next, download KF SRT (Kindle fire system recovery tool) and do option 3 because I did both options 1 and 2 and it bootlooped mine so I had to start this process all over.
You're now at factory settings for 7.3.0. Wait until it naturally updates (it will) and you should be good to continue tinkering around.
Lesson learned: Always ALWAYS read the directions carefully, and don't get too ahead of yourself! :highfive: