Related
A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.
soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.
soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.
Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?
Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.
soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....
I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.
That will work. Download Ubuntu 10.4
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...
PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks
Hi all,
Thanks in advance for any help.
I am trying to help someone root their Kindle Fire.
I have already done my own and it worked 100% first time without issues!
They have downloaded the KFU etc and tried to run the install drivers and then the run.bat which starts up the KFU, but after trying to root it the following comes up :
Attached pic.
Might it be worthwhile following the ADB advice from here? Is that the issue? And then try again? :
jayceooi how-to-install-kindle-fire-adb-usb-driver
Thanks again.
Could be a few things Generally speaking most issues are driver related make sure it appears under android phone as "Android composite adb interface" if not reinstall the driver. The use of a 3.0 usb port can prevent fastboot and render the device unseen by the computer and stuck in fastboot with no recourse to correct the situation other than creating a live sub with soupkit and or using another pc. Lastly there are cables that do not do fastboot or adb but will charge and transfer data. So check the driver, try another sub port, try another cable, try another pc. Good rule of thumb anyway. Make sure the kindle is first gen. a well.
So trying to figure out the ADB driver issue.
Followed my own link above and part of it says to look under Devices/Printers and the Kindle should show there.
Only thing is, it's showing as a Google Nexus!!!!
Say what????? I'm soooo confused.
Any ideas?
Look in device manager bud. Right click on computer and select manage then select device manager look for Android phone and expand that then check how the driver is stated.
Under Device Manager :
It says the following under Disk Drives -
Amazon File - CD Gadget USB Device.
No Android Phone or any expansion option showing.
Also the following pathway that is referred to doesn't exist :
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver folder.
Thanks for your patient help, thePooch.
Is this kindle running system version 6.3.1? As well I sent you a pm unread your private messages.
Thanks mate for the offer.
All sorted now! Changeover of cable and laptop seemed to do the trick.
No idea why, but we're not arguing with a good result!
Cheers.
Very good! I did mention cable in my first post so you can see now it is possible. :highfive:
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Try putting it into fastboot again and use these drivers for the device that comes up and see if it will install them:
http://forum.xda-developers.com/showthread.php?p=44446906
Ha, for a minute I thought I saw my name at the end of this post... For the sake of privacy I don't really intend on giving my name out openly to explain why, but if you look at my skype profile it would make sense.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
kasek said:
STRIKE!
It worked!
Had to reboot windows in order to deactivate the enforcement of driver signatures (your usb driver failed with "The hash for the file is not present in the specified catalog file"), but it finally boots into fastboot and back.
If you could spare a few seconds to explain why your driver files work and others don't? (too old?)
And what's this fuzz about driver signatures?
Anyway, thank you so much!
Click to expand...
Click to collapse
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yeah, you're right about Windows 8, it's really a pain in the a**.
I'm gonna switch to Ubuntu once they'll publish my beloved shooters (CoD, Battlefield, ...) on Linux. Fortunately, I'm using Linux since my college time ('94) so I guess the only one having problems will be my wife
stunts513 said:
I am not sure why the ones you already had didn't work with fastboot. Those drivers were just a compilation of device vendors id and product id's off of various kindles i have had to help with or deal with myself. As to the other part i will say this, I find windows 8 to be a total pain. The problems u were having is thanks to Microsoft deciding to enable that driver signature enforcement, see once I modify the drivers it kinda unsigns them so that's why you had issues. I don't know why they enabled that feature on windows 8, it was on vista too if I remember correctly, and then on 7 it was gone and it just gave u a warning while trying to install. I got sick of windows myself and stick to Linux unless I'm gaming. Driver problems are a lot easier because it comes with tons of drivers, never has to install the device, it just initializes automatically, unless under a few rare occasions u have to compile the drivers that it doesn't have. Yay Linux!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
confirm rooted in ver 8.4.6
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Zukii said:
Could you give me a course link about rooting KFHD8.9 on Ver8.4.6 ?Thank you~
Click to expand...
Click to collapse
Shure.
This one worked perfectly for me:
http://forum.xda-developers.com/showthread.php?t=2337634
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
kasek said:
I'm pretty frustrated because I've spent more than 4 hours trying to boot into fastboot, googling, searching XDA, ...
- OS: Windows 8
- Kindle Fire HD 8.9, Software 8.4.6, rooted, ADB activated in the security settings
- Amazon ADB drivers installed, device manager says "Kindle Fire" -> "Android Composite ADB Interface"
- when trying to boot into fastboot with "fastboot -i 0x1949 getvar product", I'm stuck at waiting for device. Device manager blinks ("Jem-PVT-Prod-04") and the Kindle boots up normally
- when using KFFirstAide64 I can boot into fastboot, device manager says "Jem-PVT-Prod-04" with a yellow triangle (obviously no driver)
- when trying to send any fastboot commands to the Kindle, (like fastboot devices), nothing happens
- pressing and holding the power button shuts the Kindle down, powers on normally
Please help!
I need to get rid of this Kindle ROM. Tried it for a day but this crap really hurts once you're used to CM-ROMs
Cheers,
Carsten
Click to expand...
Click to collapse
I'm like you (8.4.6) somehow I getinto fastboot quite succesfully, I dont know if this is your problem, you seems to try to "fastboot" before you poweroff your device.
don_ernesto said:
hi guys, i'm stuck in the very same point as the OP and i am getting the "hash for the file is not present......" error when installing the pointed drivers,
how do i install them?
Click to expand...
Click to collapse
Maybe this link could be helpful:
http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
This was exactly what I did.
Good luck!
Hey guys so nobody kill me if this one seems obvious. At this point I just need help figuring this little issue out and I have kinda hit a dead end on solutions. I've been out of the modding game for quite some time now and have finally got back around to getting into ROMs again.
So I have my OnePlus 9 Pro (North America/ International Version) purchased right from there website. I decided I wanted to start off by unlocking the bootloader and rooting the phone. Basic stuff. I get ADB up and running on my laptop, all of my drivers I can possible install are installed, I check and see if the device lists under adb devices. It does. I boot my device into fastboot. I go to list devices to make sure its still connected aaannndd nothing... No matter what USB sloth I plug it into on the laptop nothing. I heard the device connect sound but nothing happens and the device never lists. So I go to the Device Manager on Windows 10 and I see that it is infact recognizing that an " Android" is connected. After a few seconds of "setting it up" I am met with a lovely reassuring message in the "other devices" list that "Device Driver is Unavailable." Thats it. No options to search online, no options to manually install something. Just no solution its just unavailable.
So at this point I'm not really sure what to do next. Its probably a very simple issue to correct but the driver installation error stuff always confused the hell out of me so If any of you fellow phone loving artists would be willing to help me out I'd greatly appreciate it!
I prefer using Linux because there isn't this problem, but my most recent experience with this on Windows, I had to have phone plugged in, go to Windows settings menu, go to system updates, and check for optional updates. The proper driver was there for me and likely will be for you too
If the device drivers install ok but you have problems detecting device in fastboot, you have to manually update driver:
While device is plugged in and in fastboot, go to device manager > click on your device in the list > update driver > choose from list > oneplus drivers. There should be 3 options
adb interface
Fastboot
Android composite driver (or something like that)
Install the fastboot one. Hope this helps
Guys thank you for the help! I checked under optional updates and all of the drivers i needed were listed as needing an update! Really appreciate the quick responses! Finally I can have some fun with this phone now! Thanks again guys!