Related
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
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!
Hello friends, I have a little doubt over here.
I was trying to root my Kindle Fire v6.3.1 to install Google Play and that kind of things by using the Kindle Fire Utility 0.9.6. I chose the Permanent Root with Superuser option and after it rebooted by using Fastboot, it stuck on the boot screen (the one that says kindle fire, the fire on yellow/golden letters).
I had installed the ADB drivers succesfully, as it was recognized by Windows; but I didn't install the TWRP tool. I have tried some things I read on this forum:
1. I powered it off, then opened the KFU, and chose Normal Bootmode. Then I plugged the KF and it turned on automatically. However, my pc didn't recognize the Kindle so KFU keeps waiting the device.
2. I tried turning it off, then on and pressing the power button 3 seconds to activate the recovery menu. It didn't appear.
Also, I'd like to remark that it doesn't turn off immediately. I have to press the power button a few times to do it, but it doesn't follow a pattern.
Thanks, and I'm sorry if something similar already existed. I've searched a lot and I can't find a solution.
PS: As English is not my native tongue, I might have made some mistakes.
seems to be the issue lately with kfu all it does when you select permanet root is get you stuck in fastboot. Did the kfu terminal show anything being pushed to your kindle? Also its very likely that twrp or fff didnt get installed if you did not select those options. Now its just a matter of getting it out of fastboot some info here may help http://forum.xda-developers.com/showthread.php?t=1705063
I'm sure I didn't install neither TWRP nor FFF. Regarding to KFU, all I can remember is that first it rebooted the Kindle in Fastboot Mode, then it downloaded some files I didn't have and then kept waiting for the device.
Now, when I connect the Kindle turned on, it appears as unknown device. When I try to update the drivers using ADB, still names it as 'unknown device'.
Thanks.
Adb won't see it in fastboot try some things in the link I posted there are other approaches here:
http://forum.xda-developers.com/showthread.php?t=1660636
---------- Post added at 06:37 PM ---------- Previous post was at 06:34 PM ----------
When you get tired of messing with windows stupid drivers http://forum.xda-developers.com/showthread.php?p=26491884
In Linux you will use sudo for your fast boot commands if you make a live USB setup
Thanks, I'll check 'em tomorrow!
THANKS, thanks man. I've managed to unbrick it by following the steps listed on this post: http://forum.xda-developers.com/showthread.php?t=1660636
Yayyyy!! Your welcome
Sent from my DROIDX using Tapatalk 2
Just be careful with it now
Sent from my DROIDX using Tapatalk 2
First, I'd like to thank the xda community for all of your help! This is the first time I've worked on an Android device. I started working on my niece's Kindle fire about 4 hours ago and everything I've read has been from this forum. She is leaving the country tomorrow morning and I would like for her to have her Kindle Fire working before she leave (which is why I'm turning to you guys). Here is what I know so far about the Kindle:
FFF v1.4a
TWRP v2.1.1
I've been using the following tools/utilities (Win 7 64):
Kindle Fire Utility 0.9.6
Kindle Fire Unbrick V1.0
From what she has told me, the Kindle fire was already rooted and had gedeRom installed (along with FFF and TWRP). She decided to change roms and was going to try Glazed. However, after following the instructions on how to prep the Kindle for the flash (wiping cache, dalvik cache, etc.), she wasn't able to mount the SD card on her kindle anymore.
My suspicion is she also wiped the SD card because there is nothing on it when I check through the TWRP file manager, but she won't admit it.
Now onto the issues. When booting into Normal Boot, FFF loads, tries to boot (obviously there is no ROM to boot to), so it will just simply loop back to the boot loader.
When I boot the kindle into the Bootloader, it will show up as ADB Android Interface in the Device Manager (from what I understand it is in fastboot here). The device ID matches that of this thread http://forum.xda-developers.com/showthread.php?t=1668159, I can also issue fastboot commands here. None of them seem to change anything.
If I choose to boot into recovery and load TWRP, the Kindle disappears from the Device Manager completely. I can't mount the SD Card, system, data, or cache. I cannot issue any commands from KFU, Unbrick, or command line.
So I've been trying to work from the FFF boot loader, since this is the only place my computer recognizes the Kindle. I've tried manually entering fastboot commands. While the fastboot commands seem to be responsive, upon reboot everything is the same. Using KFU achieves the same results. I've tried almost all the option in KFU, even tried Clockwork recovery (which installed, but I decided to go back to TWRP).
ADB commands do not work, I'm assuming this is because it is in fastboot mode. Any ADB command results in a 'device not found'.
It is always listed as ADB Android Interface in Device Manger, never as ADB Android Composite Interface on My PC .. which is where I think the problem lies, since I can't mount it. This is my nieve's Kindle, she originally rooted it and installed the drivers on her PC.
I've tried everything when installing/uninstalling the drivers. From the Android SDK, to the KFU drivers scrip, and a few driver downloads from different threads. When trying all different methods, I usually get a "Unknown Device". Eventually (I don't know how) it gets read again as ADB Android Interface and I'm back to square one.
Like I said, my knowledge and time is pretty limited. I'm sure this has been posted about 2 dozen times, but I simply cannot find a working solution for my problem. So if I missed an obvious step, or more info is needed, please let me know. I've read several threads, but after the 50th one I kind of just skim through them :angel:.
Thanks again in advance!
try the command fastboot devices see if you get a string of numbers
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
there is a likelyhood that if you dont get a response it still can be drivers or the state the device is in...
I get the following response:
0123456789ABCDEF fastboot
I used 3 Windows PCs, 2 Macs, and 3 different USB cables (2 purchased from Amazon and 1 from an S III) ...
After all that, I had ruled out the cables. However, my job recently sent me a new RAZR MAXX to replace my BlackBerry, and I saw it still sitting in the box. I decided to try it, why not? I've tried everything else .. and as soon as I plugged my Kindle in while it was in TWRP (nothing would happen with any other cable) .. the ADB Android Composite Interface driver started intalling! I decided to try it another computer I was using and I had the same results. Boy, was my face red. I literally wasted hours trying to solve my issue.
I don't know the technical differences between the cables I used previously and the one that came with my new RAZR MAXX (which I'll be messing with soon ) .. but that did the trick for me!
I'd like to thank Thepooch for reaching out and trying to assist me with this. This is a great community, and I will definately try to continue being active now that I have an Android device to tinker with!
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
ray8888888 said:
Hello, I have a stock Kindle HD 8.9 from best buy that seems to have seized up. It's not rooted, I was hoping I might be able to root it to bring it back to life.
When I turn on the kindle it stops at the kindle fire logo and looks like the logo is being lit up by a light streak that scrolls across the logo. This repeats until the battery dies.
When I plug the kindle the computer via USB, the computer makes a single noise that sounds like it is trying to find the device and then Windows attempts to find drivers. Windows then errors out and says the device driver cannot be found.
If I look in the device manager I do not see any Kindle devices. If I show hidden devices I can see JEM-PVT-Prod-04 in a faint gray color with a grey question mark next to it. Through downloading and installing USB drivers found on this site I was able at one time to get this to change to Android USB device. It never changed from the faint gray color. I uninstalled the drivers and restarted since updating the drivers did not seem to address the issue. I have seen mentions in many threads about yellow triangles but I have never seen that.
I believe read on the FAQ that if there is some indication of power or booting, then the device might be able to be recovered. I'm just not seeming to have any luck with getting it to respond to the PC.
The computer is Windows 7 64bit.
I read on amazon's developer site that ADB must be enabled on the kindle before rooting. Since the kindle will not boot, I can not confirm whether it is enabled or not. I presume this is a crucial step, but I felt I should double check with others who are more knowledgeable.
Thank you for any help that may be provided.
Click to expand...
Click to collapse
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
stunts513 said:
Ah good you are able to install the drivers, that's good, leave those installed, in your case you are not wanting adb access you are wanting fastboot access to fix it, that adb interface that briefly appears is actually fastboot, so with the drivers installed you will need a copy of a utility that comes with fastboot, i recommend kindle fire first aid, open a command prompt and cd to the directory where the fastboot program is, and with is and with the device off and unpluggedt run
Code:
fastboot -i 0x1949 getvar product
once the command prompt says "waiting for device", plug the kindle in, it should now go into fastboot mode and say fastboot on the screen. Now use kindle fire first aid to restore the kindle.
Click to expand...
Click to collapse
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
ray8888888 said:
Stunts, thank you for the help. I had thought in my reading that the fastboot command above was only used after the android device was visible in the device driver. It appears that the fastboot command "forces" the device to become visible, if I understand correctly. The device was listed in the device manger in full color rather than the faint gray that it was before.
I found the Kindle Fire First Aid and ran that, there was a helpful link in the FAQ. When I ran the First Aid, I choose the Kindle 8.9 and the first version as I do not know what version number was on the device to begin with. The First Aid ran through its procedures and the Kindle rebooted. I seem to have a working device now.
I can't remember where, but I thought I saw something In one thread about a patch that should be applied after rebuilding the Kindle but before connecting to the Internet with it.
Under About, it says I am on system version 8.1.2_user_1211420
Am I ok to continue with the device or should I be doing some cleanup/final fixing before using it normally?
Click to expand...
Click to collapse
it should be fine to use now, that's just stock rooted, you might wanna consider disabling ota's or flashing another rom onto it but its fine how it is.