[Q] N00b hosed up pretty bad.... - Kindle Fire Q&A, Help & Troubleshooting

Total n00b here. I think I may have really messed up my Kindle fire.
I have searched high and low for a solution but unfortunately I fail to understand some jargon, so Im stuck. Some of you may shake your heads in disgust for being forced to associate yourself with someone of my idiocy and may say it serves me right. All the same, Im desperate for help here, so anything you can do to help me out would make me infinitely grateful.
I have been researching for weeks now on rooting my Kindle fire which I recieved as a birthday gift at the end of April so I could tap into its full potential. I was running the most recent firmware (6.3.1) and finally decided to downloaded the Kindle Fire Utility 0.9.6 to my PC and pull the trigger on Rooting it. I had some initial driver issues, but eventually got the KFU to show an ABD status of "Online" with a Boot Status of "4000". I had read in a few places that it was a good idea to make a recovery before doing anything else, so without giving it much thought I typed 3 (Install Latest TWRP Recovery) and hit enter. The KFU displayed the screen "waiting for device" and the KF went to the boot logo screen, which is where it has stayed ever since. It never occurred to me that I should first "ROOT" my kindle, and I dont know if this is directly responsible for my current situation or not.
Ive attempted to follow various suggested methods of recovery (power off Kindle, and powering it back on after restarting my computer and initiating Bootmode command 1 <4000>normal and command 3 <5001>recovery (in separate instances) and uninstalling/reinstalling drivers.) but now every error that can occur does. At this point Im ready to throw in the towel and Id be happy to just get my Kindle back to its factory settings but I dont know how I can do that.
I have come across various threads that appear to address just my problem by downloading the original Kindle firmware update from Amazon, renaming it "update.zip" and "flashing it to the sd card", but I have no idea what that means or how to do it. PLEASE HELP!!!!
(after my first misadventure there is now a "recovery" folder in the directory where I unzipped the KFU. Im inclined to think this might help, but I dont know how or what to do with it.)
Thanks in advance for anyone patient enough to respond to this.

Ok, so after further researching this problem, I have taken note that many users have successfully, installed a TWRP recovery without Rooting their Kindle Fire, (at least that is how I understand it). Evidently its not uncommon for a failure to occur during the process of any one of the optional commands given in the KFU, almost always causing this "boot logo error" or similar mishap.
That being said, I have attempted every other form of recovery mentioned on this and other forums, including Kindle Fire Unbrick Utility, with no success. The underlying problem being, that anything I am attempting to correct through the computer never reaches my Kindle. My PC acknowledges that there is something plugged into the USB port by sounding an alert tone, but it sounds different, like theres some kind of error, and the "USB error" icon appears on the right hand side of the "Start bar" (I normally use a Mac, so Im no hip to all the PC lingo) When I click it I get one of two messages no matter which port the device is plugged into: either the Kindle is labeled as an "Unknown Device" and that drivers could not be located, or that my device could perform "faster" if I moved it to a "high speed" USB port (all of the ports on my computer are listed under High Speed). When checking the device utilities folder, previously the driver was consistently called "Android ABD Interface" with a yellow error sign. Upon "updating driver" I would get the error code 10, "this device cannot start". Now however, no driver is displayed whatsoever for my Kindle, android or otherwise...
Ive read that in some cases, allowing the battery to completely drain then plugging in and booting it back up will cause a Kindle in this state to "default to its factory settings", so this will be my last ditch effort to salvage my Kindle before I resign myself to returning it to Amazon in hopes that it will still be covered under warranty. I guess Im just not cut out for this sneeky stuff. The retarded thing is, the only reason I wanted to Root my Kindle fire in the first place was to personalize the backgrounds...

what happened is your stuck in fastboot and your windows drivers are all buggered up. I can tell you what I would do?
---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------
unplug your kindle from your computer and use system restore to roll your computer back to when your drivers were good not to be confused with system recovery if your with me so far?
---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------
its very likey that adb will not detect your kindle it cannot while its in fastboot
But first try this shift plus right click on the tools folder in kindle fire utility select open command window here power your kindle off and enter the command
Fastboot getvar product (hit enter)
Plugg your kindle in it will power on in fastboot
If you get the response product: kindle then we can move on.

I think so, though I dont know how to perform a "system restore"... If it was a Mac id simply jump into the Time Machine and roll back the clock a few hours, but I dont even back up my PC cuz I use it for nothing but the occasional game and PC exclusive stuff like "this"...

if you get the response product: kindle
Type fastboot oem idme bootmode 4000 (hit enter)
fastboot reboot (hit enter)

The problem really isn't that you've done anything wrong. For some reason when the device switches from normal boot (4000) to fastboot (4002), Windows fails to recognize it as being in fastboot mode. The typical fix is to reinstall the drivers. Unfortunately, it isn't always as easy as it sounds. Sometimes it works and sometimes you'll end up bald from pulling your hair out over it, and I have yet to see a definitive solution to this problem. So, as of now, success is really just hit and miss.
There are, however a few tutorials to give you a decent foundation to work from.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
YouTube is likely to have a few thousand videos on the topic as well.
If all else fails, you can always set up a Linux LiveUSB and issue adb/fastboot commands from there, but I would consider that a last resort, unless you are already familiar with Linux.

yes and what soupmagnet said to

Ok Pooch, so while you telling me what I should be doing, I decided to be proactive and figured out how to perform a system restore and rolled my computer back to this morning before I started any of this messy business. Hopefully this will not complicate the process youve now begun directing me through...

just unistall the drivers that came up when you plugged your kindle in unplugg your kindle reinstall the drivers and maybe youll get lucky
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
the drivers could be a fight but hey its windows

Thepooch said:
just unistall the drivers that came up when you plugged your kindle in unplugg your kindle reinstall the drivers and maybe youll get lucky
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
the drivers could be a fight but hey its windows
Click to expand...
Click to collapse
Soooooo, I didnt get lucky...
To your point Soup Magnet, Ive probably watched most of the tutorials you mention on You Tube and read every forum thread on the subject within the past 6 hours... It sounds so simple! But im tired.
Ill try the command prompts you suggested earlier and see if I get any luck there, after that i'm done, at least for tonight.
Thanks for your help guys!

dont give up its fixable your just in the wrong bootmode

Thepooch said:
Fastboot getvar product (hit enter)
Plugg your kindle in it will power on in fastboot
Click to expand...
Click to collapse
..."< waiting for device >"
It was worth a shot. Thanks again.

was it powered off before you plugged it in after it said waiting for device?
---------- Post added at 11:41 PM ---------- Previous post was at 11:31 PM ----------
Then next time try
fastboot -i 0x1949 getvar product (hit enter plug in your powered off device)
fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)
fastboot -i 0x1949 reboot(hit enter)

Thepooch said:
was it powered off before you plugged it in after it said waiting for device?
Click to expand...
Click to collapse
Correct. I powered off the Kindle and disconnected it. Then I entered the command and hit enter and connected the powered off device. The Boot screen came back on, but that where it stays, and 15 min later its still "waiting for device".
Ill revisit this in the morning when my head is clearer. If you come up with any bright ideas in the mean time, Ill be happy to try them out!

indeed good luck rest should help xda isnt going anywhere
Sorry typo above is fixed

Thepooch said:
was it powered off before you plugged it in after it said waiting for device?
---------- Post added at 11:41 PM ---------- Previous post was at 11:31 PM ----------
Then next time try
fastboot -i 0x1949 getvar product (hit enter plug in your powered off device)
fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)
fastboot -i 0x1949 reboot(hit enter)
Click to expand...
Click to collapse
nope
nope
nope
I know all the commands are good, its just not communicating to the Kindle...
Figured Id give it one more go before I hit the sack. I know this is gonna keep me awake anyway...

http://forum.xda-developers.com/showthread.php?t=1660636

pugsley42 said:
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Looked promising and I almost got excited about it... until step 14, when after turning on the device after turning it off (while still plugged in)no new text was spit out in the utility and my Kindle refused to reboot...
What might be happening is that every time I plug in/ turn on from off while plugged it, windows attempts to install the driver software automatically, which may be causing the mix up at the device utility stage. Like Pugsley, after deleting the .android folder from my profile and uninstalling the ADB interface/driver, then running hardware change scan, my device is recognized as "kindle", but after turning off the device and turning it back on at the "waiting for device" screen, the device is automatically updated as Android ADB interface with errors again. Is there a way to temporarily block this auto-install? That might work...

josepho1997 said:
Plug it in and tell me what it says on your computer. If it says Kindle or Android Composite Device then you should be good. If it doesn't, do a hard reset and try again. Same thing happened to me and the KFU drivers wouldn't work for me, so I downloaded a new driver. I will post a new reply with he drivers. But first if you get Android Phone or something else under Android Composite device, then uninstall it. Then go to disk drives(i think that's what its called)
and find your kindle and uninstall. Then reopen device manager. Find Kindle with an ! and open it up. Now open of the Kindle Fire Drivers folder I gave you(unzip first) and click on install.bat
Click to expand...
Click to collapse
In Device Manager, when I plug in my Kindle it shows up as "kindle" in all lower case letters and the generic device icon has a yellow "!" attached to it. If I uninstall it an then "check for hardware changes" it just pops right back up.
Is "disk drives" separate from the Device Manager utility? I did a search for it at the start screen and came up with nothing... If you send me those drivers you were talking about Ill give that a try. Thanks.

Grrr! So I downloaded the driver.zip file you posted up (thank you) and double clicked the "install" file within the unzipped folder. It appears to have installed, but now every time I plug in the Kindle it goes to "unknown device", not showing up as "kindle" anymore, and no sign of "android" anything in the device manager. I haven't been doing anything differently, same USB port as before, etc. I did shut down my computer for a few hours and booted it back up just before downloading the zip file though. Must have started the whole cycle over again. I've got to go back through earlier posts and find out how I got past this issue.
I think I know what you're asking me to do, it will just take a little bit of patience on my part to get it going. Ill post my results when I do. Thanks again!

Related

!!!(Q) Help bricked kindle fire 6.3

okay so i was trying to root my kindle fire and i didnt get su any where so then i tryed to install cwm and now its stuck at the yellow triangle and it wont go into recovery and it also will not connect to adb i need hellp ASAP
Install drivers as ADB composite with the Android SDK and then use this to change the bootmode
The link you posted is not working due to the period in the URL at the end.
Do not afraid. I have got the same experience Let God bless the search button
http://forum.xda-developers.com/showthread.php?t=1568340
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Click to expand...
Click to collapse
My kindle got the 6.3 update -solved!!
This has got to be one of the fastest ways I have rooted 6.3 kindle update
i went on line here http://liliputing.com/2012/03/root-...ogle-play-store-with-kindle-fire-utility.html
downloaded the new kindle fire utility and ckick on Install permanent root with super user. got rooted in about 2 minutes with no trouble at all
thanks everyone for your help but i solved it what i was doing was unsing the kindle fire utility trying to instal latest firefirefire but it just sat there and so i just went into the utility and reinstaled the twrp and it booted normal!!
Bricked Kindle
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
ChrisKenison said:
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction.
Click to expand...
Click to collapse
If you get the yellow triangle logo to come up, then it's probably in fastboot mode. If you reboot it while it's connected to your computer and you get some device detection beeps from Windows, it's likely to be a driver issue. Look here...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You might want to read the first post in that thread too.
Watch carefully as the device boots up and you get the yellow triangle logo. If that boot logo comes up and stays there, it's in fastboot. If the boot logo comes up, the screens blacks out, and then the boot logo comes back up (dimmer) then it's either trying to get into recovery or booting into the OS and failing.
I would try setting the bootmode to normal in KFU and when it says "<waiting for device>" reboot the Kindle Fire. Since you have FFF, the fastboot program on your computer will wait for the Kindle Fire's FFF bootloader to get into temporary fastboot and reset the bootmode when the KF is ready.
But, the computer won't even recognize there is a device connected to it
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
And because its not recognized in the device manger, kfu isn't picking it up
Sent from my Galaxy Nexus using xda premium
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
If you can't get the drivers working with the KFU distribution, you'll have a harder time with the SDK. They are the same drivers, but KFU has an updated, Kindle Fire specific .inf file for the driver and also installs the .ini file in the .android folder that you'll need. I don't know what you see in the device manager, but if you don't get one of the devices shown in the post I referred to earlier, I would try another Windows machine. You won't be able to do anything without getting it to detect your KF and load the proper drivers. If you are more adventurous, you could try pokey9000's Firekit (search for it) and try using linux to send it fastboot commands.
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
yea mine is stuck on the firefirefire boot screen
ChrisKenison said:
Yeah, that's my problem. I have tried 3 different windows machines (all windows 7) and, being the adventurous person i am I tried the Linux fix (removing back cover...) to no avail. All that did was make my kindle blink green. Not sure what that means either.
Click to expand...
Click to collapse
Well, if you can't get any of those scenarios to work out, maybe it's a hardware issue. It might be something as simple as a bad USB cable or something more serious within the KF itself. I've never had a problem with Windows or Linux not seeing the KF, so my hands on experience in this regard is limited... my KF has never been broken to that degree. I'm always curious to see what's going on with people's KF when they say nothing works, but my KF has never given me that opportunity.
ChrisKenison said:
I will have to try installing the drivers from the Android SDK... maybe that will turn up something. But, by installing the drivers from KFU, it doesn't work.
When I plug the device in, it beeps at me saying device is unrecognize and it couldn't install drivers because there was a malfunction. In the device manager (while that's happening) it shows up as an unrecognized usb device. Then, it goes away (the device doesn't stay in the device manager). Then, that whole thing happens again one more time. There isn't anything for me to update in the device manager... thoughts?
Click to expand...
Click to collapse
Sometimes in order to install the correct driver you need to delete the original from your computer because it will continue to attempt to revert to the default but beforehand try rebooting your computer and the kindle
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
mistaanime said:
yea mine is stuck on the firefirefire boot screen
Click to expand...
Click to collapse
Run the kf utility again install twrp and fff again

[SOLVED] Stuck at the KF logo

I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
Depending on which PC I use, and in what order it's plugged in, I get different results in the Device Manager (both Windows 7):
Home PC -
Hardware Ids = USB\UNKNOWN
Yes, I've tried loading drivers six ways from Sunday, and none worked.
Absolutely no solution involving ADB in any way will work until I can at least get Windows to recognize it correctly and load the proper drivers.
Work PC -
If I have the KF turned on when I plug it into my PC, I get the same result as on my home PC (though I don't think I tried plugging it in on my home PC while my KF was powered off).
If I have it turned off when I plug it in, my PC sees it as an "Android ADB Interface", with the correct hardware ids.
Even when it sees my KF correctly in Device Manager, I still can't get ADB to communicate with it.
I've tried FireKit on my Ubunutu 12.04 laptop, but it never sees my device, and gets stuck at the <waiting for device> message. I've tried countless driver iterations and many utilities, and none seem able to communicate with it while it's stuck at the logo.
Any help would be immeasurably appreciated!!
[UPDATE]
While my device was detected correctly in Device Manager (but still not able to communicate via ADB), I reloaded the drivers using the KF Utility. It is still detected as "Android ADB Interface" but with an error in Device Manager. The error is "This device cannot start. (Code10)". I uninstalled it, including drivers, and let Windows autodetect. It was identified as "kindle", so I ran the same driver package and it still sees it as "Android ADB Interface", but still with the error.
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
IT LIVES!!! While I was still getting the error code 10, I launched the KF utility one more time. ADB status was still offline. I went into the menu to modify boot mode, told it to boot in normal mode and it was stuck <waiting for device>. On a whim, I left it there and cycled power on my KF. It found the device, finished, rebooted, and it's good!!! The Device Manager is happy now too!!
The behavior was so odd between my work and home PC. I was seriously scared when it gave a bad device ids on my home PC. I think it was more a combination of several different things that helped, and I'll update my main post with all that I did to get it back (that I can remember). Hopefully it will help someone else.
This is an *amazing* community, and I can't thank everyone enough for the incredible work you all do and the true sense of selflessness exhibited here on the forums!
btw, How do I edit the subject to indicate it's solved?
^_^
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
jaetrix said:
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
Click to expand...
Click to collapse
Glad it could help someone! I was frustrated enough about it and couldn't find a single solution that fit my issue. I just had to combine some to get it to work for me.
Bump
Yes this saved two bricked kindles. Trial and error is sometimes the best means to solving a problem.
Sent from my GT-I900 using xda premium
This is happening alot here of recent thats why I bumped it to the top of the list
Thank you for this. Maybe a moderator will be kind enough to sticky this.
Sent from my Galaxy Nexus using Tapatalk 2
pugsley42 said:
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
[...]
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Pugsley42...you 'da man! I had the same story as you told above, including searching and following countless threads of instructions. Nothing worked until I found your instructions! Thank you, thank you, thank you!
Stuck at the KF logo
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
My first suggestion would be to read this:
http://forum.xda-developers.com/showpost.php?p=25884555
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
pugsley42 said:
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
Click to expand...
Click to collapse
Okay, I was attempting to load a ROM on it. It had been rooted already with no issues and then something happened during the installation of TWRP and spit out an error message of unable to load and then rebooted. That's where I am with the kindle fire boot screen.
As for the "Device Manager" It shows up as "Android Composite ADB Device" and with KFU it shows the following status:
ADB Status: Online
Boot Status: Unknown
At this point is when if I try to run Install Latest TWRP Recovery or FFFF or anything it just sits there and says "Waiting For Device"...
I've read though most of these posts and have tried several different suggestions with no luck so far. So I have actually read through here. :-/
Hope this helps at all.
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Stuck at the KF logo
pugsley42 said:
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Click to expand...
Click to collapse
Yeah, I've tried it using the KF Utility as well as using fastboot at the command line :-/
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Your explanation and guidance cut right to the solution for me. Thank you so much!
Thank you!!
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
cmgroden said:
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
Click to expand...
Click to collapse
I presume if any of this helped, you were able to get further than you have been. What state is it in now? What error(s) if any?
I seem to be having this same issue but I cannot get my pc to recoginze the kindle fire as anything. perhaps i did something wrong but i was following a video on youtube and though i was doing it exactly as it showed. First thing i did after I finally got the drivers loaded was start KFU and then chose to load TWRP. It started the process but when it hit the part about rebooting my device that's where it stopped. Since then i've been stuck at the white and yellow kindle fire logo. No matter what i do to try to reinstall the ADB drivers I cannot get my computer (win xp) to recognize the kindle. It shows as "unknown device" in device manager and when it's plugged in the little pop up says that the usb device has malfunctioned and windows doesn't recognize it. So am I totally dead? I'm assuming before i can do anything to recover it I need to get windows to recognize it with the ADB drivers.

[Q] Waiting for Device

So, Ive been searching for over 6 hours now and I really cant seem to root my kindle fire. I tried basically everything, and when things went wrong, I just deleted the files and started again. On my last try, I was able to fastboot it (at least I think so). When I ran KFU, ADB was online and Boot: 4002.
When I tried to root it always got stuck trying to find twrd.img. Then I tried option number 4, Installing Clockwork Recovery (because option number 3 was a dead end) and twrd.img was installed. But everytime something seemed to go right, the process wouldnt finish, it would just be <waiting for device>. I thought my problems would be over, so I tried to root it again. Now whenever I turn on the device, KFU is unable to locate my kindle, and it doenst appear on the device managing tab either. Even using the kindleunbrick.bat that worked for me the last times, it just gets stuck at <waiting for device>. ADB is offline and Boot: Unknown for now.
I really need to root my kindle because I dont live in America, so I dont have access to most stuff. I already changed the language when installing the driver, however, everytime I hooked my kindle up, a windows message would pop out saying that there was a problem with the driver, but when I went to device managing tab and tried to uptade the driver to "user\.android" it always came back as updated.
I am really noob at this, but I have read all the guides I found and something always went wrong. I hope someone can help me with this, please.
Thanks
Is your kindle turning on? If I could suggest you should put off anymore attempts to root your device till you know precisely what your doing and why. My biggest guess right now is your drivers are the greatest pitfall. You seriously don't want anything going wrong with them in the process of sending recoveries boot loaders or rooting you will end up with a really fancy paperweight. Privy to to attempting anymore you need to know that your drivers are functioning 100%.The fact that you pushed cwmr to your device after twrp should hurt a thing hopefully one should overwrite the other if all goes well . Since rooting is the primary goal go with that until you have verified root then recovery and bootloader can be done easily later with safer methods. Hold off awhile as long as your device will boot until you have found the knowledge and support to make it happen right. Start here http://forum.xda-developers.com/showthread.php?t=1552547 then go here http://forum.xda-developers.com/showthread.php?t=1638452 plan to use this method to root http://forum.xda-developers.com/showthread.php?t=1568340 ask a lot of questions don't be hasty or you will spend a lot of time trying to fix it instead of enjoying it.
As I said, I read all those guides already. I can use my kindle normally, but when I connect it to my computer, it is unrecognized. I tried every method I found to root, even though I just wanted to watch stuff and download a few games for my spare time(my intention was to watch stuff from premium features, but Im not really sure if root will allow me to do that from a foreign country*, so Im a little hesitant to extend premium).
I guess I wont try anything else for now because my main goal was reading, and this I can still do, but I am puzzled with the fact that I was unable to root it. Ill try to understand a bit more (hopefully with some tips). Thanks
*Geographical restrictions
OK well youve read the guides but in what you say it appears you are doing some of the wrong things why would you unbrick if your not bricked? Your drivers are your only issue as of this point but your methods are pushing you close to bricking your kindle. I would like to see you succeed in rooting your device and avoid bricking it.
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
When your around we can try to get your drivers working
It would be nice to know what os your running on your computer. If you are on windows 7 use system restore to roll your computer back to a date before you started messing with the drivers or anything. Once it completes plug your kindle into your computer check to see if you can access the SD card contents and if it appears as a kindle in your device manager. Important now if all is good unplug your kindle and run the .bat file that comes with kfu. Then plug your kindle in let windows install the driver. Open up kfu find the tools folder shift plus right click select open command window here. Then type adb devices if its followed by a string of numbers this shows your kindle connected via adb . At this point you should obtain some help from some of the pros here at xda at fastboot and adb commands to safely root your kindle. If you decline and still wish to use kfu then only select install permenant root. If at any point in this process it fails and you loose adb connection do not unplug your kindle run the driver file again then recheck device status with kfu I believe its option 0 to see if your back online again. Pay attention to the dialogue that takes place in the kfu window you see verbatim that says failed or permission denied then quit after that. One important thing is you need to allow installation from unknown sources in the kindle settings on the kindle under device or it won't push the required files anyway.Wait to install twrp and fff until later there are easier safer methods. If your kindle hangs for a long time at the kindle fire logo select boot mode normal in kfu before unplugging. If at anytime kfu states waiting for device do not unplug it rather power it completely off then power it back on while connected .
---------- Post added at 01:53 AM ---------- Previous post was at 01:32 AM ----------
Just a side note I have rooted 4 different times with kfu without a single failure or mishap including the ones you are experiencing. I'm inclined to feel that relates mostly to your computer and drivers which makes kfu an unsafe approach for you I'm not responsible If you brick it!!!
I unbricked my device before I even came here, I tried an youtube tutorial and then it got stuck on the kindle fire logo, but after I unbricked it, it was fine. I know that something is going wrong, but Im following step-by-step the guides (at least I think so). As I said, everything was going correctly, ADB was online, Boot:4002, but when I tried to root it would be on an endless search for the file twrp.img, and after I succesfully downloaded it (I guess), my computer is unable to find my Kindle.
I run Windows 7, but it isnt properly activated (my room mate threw out the serial code), I dont know if this would interfeer in any way. When I conect the kindle, it appears to be in USB mode and says that I can transfer files, but my computer wont even find it. Ill try to restore my computer now and then Ill come back.
I know that doing this is my responsibility, but not being able to download apps is pretty annoying, so I have to keep trying.
If you can get adb status online then, why don't you install TWRP manually? Or use the "smirkit"?
Once you get recovery installed, you're set.
Also, be sure to "disconnect" from USB storage mode before trying to use adb commands or they won't work.
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Shift+right click your KFU "tools" folder and select "Open command window here"
From there, enter:
Code:
adb devices
If the output is something like:
Code:
List of devices connected
123456789ABCDEF
then you can install TWRP
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
If the output is:
Code:
List of devices connected
(null)
then you need to reinstall your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Thank everyone that helped me, I managed it!
Actually I was doing everything right, but I guess the problem was my computer, because when my girlfriend came over I tried connecting it to her netbook and it recognized my kindle. I just downloaded the kfu, installed drivers, reconected kindle and let it update, ran KFU and selected option 2. All done now
I have no idea why this didnt work before, but at least now I can really enjoy my kindle.
Thanks again!
saybhausd said:
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Click to expand...
Click to collapse
Not system recovery bud system restore two different things go to accessories system tools system restore choose a date chose to restore to that point. System recovery is way way different. Glad you got it going

[Q] Problems with FFF & KFU. Device not recognized

Hello-
Quick background. I have a Kindle Fire with the CM9-Reloaded ROM installed. All was going well for a few weeks until my Kindle stopped connecting to the internet. I figured it was just a bug and wanted to reinstall the ROM or choose a different one.
I have FFF v1.4 (with the blue logo) installed. When I get to the screen that allows me to choose "Normal Boot", "Recovery", or "Reset Boot Mode" I choose the "Recovery" to go into TWRP; however, this doesn't happen. It puts me back into a loop to the same screen to choose again. I can do this over and over again and I'm still not able to get into recovery to get to TWRP.
I decided to see if I could use the Kindle Fire Utility to get to TWPR that way. Before everyone asks, my drivers are all updated and functioning properly. I uninstalled and reinstalled just to double check. When the Kindle is plugged in, I can go to the device manager and see my Kindle there. The problem is that KFU says I'm offline and I can get to any of the menus. When I plug in my Kindle I do get the little "bong" that tells me my computer recognized it.
Also, went to my laptop and downloaded the KFU and installed everything. Same result as with my desktop.
What else can I try? I have a factory cable, but I really don't know much about how to use it. I simply followed step by step instructions to root this when I originally got it. Any suggestions? I'd really just like to put this Kindle back to stock, re-root, and try it all over again to eliminate any potential issues in the future. Thanks in advance for your help.
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
same boat
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Dasanko said:
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
Click to expand...
Click to collapse
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
jeffjoleen said:
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
Click to expand...
Click to collapse
By it not working, do you mean that it reboots normally?
"fastboot getvar product" to get the KF to stick with fastboot mode when it's loading the bootloader.
"fastboot flash recovery twrp.img" very important to double check the file hash to make sure it's not corrupt.
"fastboot reboot" only in case it doesn't automatically reboot on its own.
EDIT: Keep in mind fastboot mode uses a different set of drivers, so you may have to install those as well (included in KFU, along the ADB ones).
---------- Post added at 06:57 PM ---------- Previous post was at 06:49 PM ----------
Justugh said:
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Click to expand...
Click to collapse
Please don't hijack other people's threads, start your own here on Q&A. Otherwise, handling with two completely different issues in the same place gets awfully confusing. Also, read this: http://forum.xda-developers.com/showthread.php?t=1552547

Fire Hd 8.9 can't enable ADB

I bought a kindle fire from craigslist that turned out to be a demo unit.. I've unsuccessfully tried for the past hour to enable ADB, all the guides require enabling debugging, but I can't access settings since it's in demo mode.
Is there any other way to enable ADB or get into fastboot? I'm going crazy..
Sent from my SCH-I605 using Tapatalk 2
Haloman800 said:
I bought a kindle fire from craigslist that turned out to be a demo unit.. I've unsuccessfully tried for the past hour to enable ADB, all the guides require enabling debugging, but I can't access settings since it's in demo mode.
Is there any other way to enable ADB or get into fastboot? I'm going crazy..
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
You won't be able to enable adb use fastboot and this tool to replace the demo system http://forum.xda-developers.com/showthread.php?t=2011126 .
---------- Post added at 05:08 PM ---------- Previous post was at 05:01 PM ----------
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and reboot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Thepooch said:
You won't be able to enable adb use fastboot and this tool to replace the demo system http://forum.xda-developers.com/showthread.php?t=2011126 .
---------- Post added at 05:08 PM ---------- Previous post was at 05:01 PM ----------
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and reboot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Click to expand...
Click to collapse
I did everything you said, I got "Waiting for device" in cmd and all but when I plugged in my KF (while it was turned off) and tapped power it booted straight into Demo again, what should I do?
edit: Is there a certain driver I need to install? I got the one here http://forum.xda-developers.com/showthread.php?t=1890413 and it installed, but when I plug in my kindle it shows up under Devices & Printers as a Portable Media Player (model Kindle), and under Kindle it says "Connected as Media Device", is this normal?
Unread your private messages.
I got it to work by following your steps, I also had to manually install the driver with the guide here: http://www.jayceooi.com/2011/12/29/how-to-install-kindle-fire-adb-usb-driver-video/
Gonna type out the process in case anyone comes here from a search engine later:
I installed the driver, followed your steps for opening CMD/running command "fastboot -i 0x1949 getvar product", then I held down the power button until the device shut off (around 20 secs), plugged in cable, tapped power button, and it showed the device (Jem-PVT-Prod-04) was recognized, but disconnected. I did the same thing again (20 sec power off, turn back on) and I was able to enter fastboot. From there I followed the link you posted (system.img recover tool) wiped all data then chose option 3 (which rooted the device and installed a launcher)..
All is well so far! Thanks again!!
Way to make a demo a real tablet :highfive: .
Hey guys,
Sorry to necro an old thread here but I cant seem to get this to work
I bought a demo tablet too and I have followed this guide installed the linked driver and as soon as I try step one nothing
I run Fastboot in CMD use the command fastboot -i 0x1949 getvar product CMD tells me waiting for device and with the kindle turned on I connect the USB lead and nothing it just sits so Im at a loss and have been trying to make this work for months im pulling my hair out with it
If anyone can help I would be extremely grateful..
When the fastboot driver isn't installed the command won't work' and its a pain to install it in the timeframe it gives you, best suggestions are this:
1. try kindle fire first aid's driver installer
2. Do this from and Ubuntu 13.10 live CD/USB after installing fastboot from Ubuntu software center.
Personally I use Ubuntu Linux and I would say its much more preferable because there's no mess with drivers on the kindle, it automatically loads the module required so all you have to do is run the command from a terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
When the fastboot driver isn't installed the command won't work' and its a pain to install it in the timeframe it gives you, best suggestions are this:
1. try kindle fire first aid's driver installer
2. Do this from and Ubuntu 13.10 live CD/USB after installing fastboot from Ubuntu software center.
Personally I use Ubuntu Linux and I would say its much more preferable because there's no mess with drivers on the kindle, it automatically loads the module required so all you have to do is run the command from a terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi stunts and thankyou for the reply!
I have downloaded the kindle fire HD First aid program from this thread
http://forum.xda-developers.com/showthread.php?t=2096888
the first aid program is linked as https://xerocomm.app.box.com/kffa-100 within the above thread
It was posted by user prokennexusa is this the first aid program you talk about?
If so there is a folder within the rar file designated Drivers im assuming that these are the drivers you speak of but there is no installer
I can manualy install them ofcourse but do I have to remove the drivers I downloaded and installed previously
(The drivers Haloman800 mentions in this thread)
Ive tried to manualy install different drivers over the top of ABD drivers before and windows always says the drivers I have are up to date and doesent change them
Ilikenoodles said:
Hi stunts and thankyou for the reply!
I have downloaded the kindle fire HD First aid program from this thread
http://forum.xda-developers.com/showthread.php?t=2096888
the first aid program is linked as https://xerocomm.app.box.com/kffa-100 within the above thread
It was posted by user prokennexusa is this the first aid program you talk about?
If so there is a folder within the rar file designated Drivers im assuming that these are the drivers you speak of but there is no installer
I can manualy install them ofcourse but do I have to remove the drivers I downloaded and installed previously
(The drivers Haloman800 mentions in this thread)
Ive tried to manualy install different drivers over the top of ABD drivers before and windows always says the drivers I have are up to date and doesent change them
Click to expand...
Click to collapse
If you wanna take the easy way out use the linux method, i have to say this is the easiest imo. The drivers in my signature work too, i thought the kffa had a driver installer but i guess not? So either screw with windows and try to remove previous drivers or go with linux, choice is yours,
stunts513 said:
If you wanna take the easy way out use the linux method, i have to say this is the easiest imo. The drivers in my signature work too, i thought the kffa had a driver installer but i guess not? So either screw with windows and try to remove previous drivers or go with linux, choice is yours,
Click to expand...
Click to collapse
Ill try screwing with windows to remove them drivers first
Havent got a multiboot system setup so hopefully it will be less of a mess about than setting up linex and multiboot etc..
Ill post back with results
---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------
stunts513 said:
If you wanna take the easy way out use the linux method, i have to say this is the easiest imo. The drivers in my signature work too, i thought the kffa had a driver installer but i guess not? So either screw with windows and try to remove previous drivers or go with linux, choice is yours,
Click to expand...
Click to collapse
Oops just found the installer Within KFFA
So I ran it and it said completed successfully
I then used "fastboot -i 0x1949 getvar product" It said waiting for device so I powered on the kindle (its in demo mode) my pc detected the kindle installed it as a kindle and gave me the auto play options again but the Fastboot window remained unchanged
How will I know when I actually have the correct drivers installed will the kindle install as "kindle portable media player" or something else?
Once again I do appreciate you giving your time to help me.
Ilikenoodles said:
Ill try screwing with windows to remove them drivers first
Havent got a multiboot system setup so hopefully it will be less of a mess about than setting up linex and multiboot etc..
Ill post back with results
---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------
Oops just found the installer Within KFFA
So I ran it and it said completed successfully
I then used "fastboot -i 0x1949 getvar product" It said waiting for device so I powered on the kindle (its in demo mode) my pc detected the kindle installed it as a kindle and gave me the auto play options again but the Fastboot window remained unchanged
How will I know when I actually have the correct drivers installed will the kindle install as "kindle portable media player" or something else?
Once again I do appreciate you giving your time to help me.
Click to expand...
Click to collapse
If you plug it into your pc when the kindle is off, your pc should detect it in fastboot and that command waiting to be run should put it into fastboot, if it doesnt its because the driver isnt installing for the jem device that should be breifly appearing.

Categories

Resources