Develop Bugs

[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] Wondering if the device is unfixable (That is it) (Provided specifics)

I just bought a used Kindle Fire (Model D01400). The guy had android on it but reinstalled the original software before selling it to me apparently. The original software worked when he gave it to me perfectly but i decided to restore the device to factory settings. When I did that it brought up the blue kindle fire startup screen with v 1.4 in the top corner and then loaded TWRP. There was an Install, backup, restore, wipe, mount, settings, advanced and reboot option. It says Team win recovery project (TWRP) V 2.2.2.1 at the top. I proceeded to choose the wipe option and wiped the cache, dalvid cache, factory reset, system and external storage. Then i rebooted it and it gave me that blue kindle fire screen and then nothing. If i press the power button I get one of three boot options. 2 of them bring me to the regular white and orange kindle fire screen that just sits there and does nothing. The other one brings me back to the TWRP screen.
The other pertinent piece of information is that when i try to connect it to the computer, I cannot access the device drive and see the contents. (I watched a video on how to fix the device to get it back to the original device software but I need to access the contents of the device) I followed the instructions provided in one of the beginners threads and installed the google sdk that allowed me to see the kindle on my device manager as an android phone but that it is. I cant do anything with the device in My Computer. It does not even show up in there as kindle.
I have been all over this website and read the beginners guide and short of installing linux to try soupkit and trying all the other fixes:
I just want to ask: Is this device bricked forever and unfixable or if I follow the guides that are on this forum can I get it to work like it did when it first came out of the box. (Just asking yes or no if this is fixable)
I just want to get this Kindle back to its normal state with its normal software. I just want to read books on this thing. Not use android.
Bonus Question: Knowing that I just want to get this back to how it works out of the box, is there a faster process than sifting through the beginner threads? (Just Yes or No) (If there is I will search harder to find it)
I am not asking for someone to hold my hand and do this for me. Just making an enquiry because there is tons of stuff to learn and do to try and fix this and I wonder if I am wasting my time.
(More specifics: I am using 64 bit version of windows vista, and have ubuntu installed as well, I have USB 2.0 ports, I have a factory Kindle USB cable from my older Kindle 3G)
I hope I covered everything.

And yes I realize now that I should have never done that factory reset when i first got it. It was working exactly how I wanted it to when i first got it. I am apparently not a smart man.

The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2

soupmagnet said:
The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Any advice on getting around the "connecting it to my pc thing" or is it alright if it shows up as an android phone in my device manager.

soupmagnet said:
The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Alright I have been learning about this and trying for hours and hours now. I have device manager reading the kindle fire as an android phone ADB interface but when i try to use KFU it does not show the kindle as being connected and when i even try to do anything, like installing TWRP again or something it does not read the device and says waiting for device. I have done everything in the beginners guide.
I think i am having so many issues because I inherited this device in the middle of its functionality and i never had to do the previous steps. I curse the guy who rooted this damnable device in the first place..

Alright i have made some progress and I got my hopes up way too much because i may not ever get a response to this but I am hoping. I followed thesee instructions because I already have all the prerequisites for this process done:
"Reverting to stock software
Required software:
Amazon Kindle Fire Software Update
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip"
I found this on http://forum.xda-developers.com/showthread.php?t=1638452
have the kfu and the software folder and the update put in that folder. I get the device into fastboot but when i type in
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
It returns back "error: device not found"
And that is when I cried for an hour. I have everything installed. TWRP i can now reasonably navigate everything. I have ADP thing in my device thing. Why wont this work!

adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip <------ that there is about the worst thing you could do go ahead wipe out your recovery your bootloader and brick your device. I think Soupmagnet recommended modaco that`s about the best place to start. The reason you cant push it might be drivers read up a little it won`t hurt ya. At any rate flashing stock is a mistake here is a nice big list of goodies to flash on that thing http://forum.xda-developers.com/showthread.php?t=1859851 . If your running Ubuntu? run this script on it and reboot http://forum.xda-developers.com/showthread.php?t=1850038 great little feature there that will help you adb push anything you want to that kindle not to mention return to stock safely which really isn`t needed if you flash modaco.

Ijustwanttoreadonthis said:
Any advice on getting around the "connecting it to my pc thing" or is it alright if it shows up as an android phone in my device manager.
Click to expand...
Click to collapse
In TWRP, you can use the Mount function to mount your sdcard as a USB device and transfer your ROM that way. I would highly suggest you install MoDaCo and try it out before you try to revert your device back to stock. In the meantime, you can educate yourself a little more about the device and how it works before you get yourself into trouble by not reverting properly.

I should have reported that I tried to put modaco on the device with the same process as thhis -> adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
And it still gave me an error saying it could not find the device. And i have been reading threads and trying stuff for hours now. The only problem is that because my device already has all this stuff set up the guides and threads all presuppose that the person knows what they are doing. If i would have just had a stock kindle and done all the steps to get to this point I would have already had all the practice and hands on training. I am going to try to get modaco onto my SD card trying every possible avenue before I post again. Again, my device manager is reading the kindle as Android phone -> Android ADP Interface and it does not show up in My computer as anything. That is what one of the tutorials said it had to do. I really hope this is correct and I am not trying in vain.

Ijustwanttoreadonthis said:
I should have reported that I tried to put modaco on the device with the same process as thhis -> adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
And it still gave me an error saying it could not find the device. And i have been reading threads and trying stuff for hours now. The only problem is that because my device already has all this stuff set up the guides and threads all presuppose that the person knows what they are doing. If i would have just had a stock kindle and done all the steps to get to this point I would have already had all the practice and hands on training. I am going to try to get modaco onto my SD card trying every possible avenue before I post again. Again, my device manager is reading the kindle as Android phone -> Android ADP Interface and it does not show up in My computer as anything. That is what one of the tutorials said it had to do. I really hope this is correct and I am not trying in vain.
Click to expand...
Click to collapse
Don't worry about using ADB at the moment. Boot into TWRP using the FireFireFire1.4a boot menu you described before, and select "Mount". Make sure there is an [X] on the last option and press the button at the top that says "Mount USB storage". Then check under "My Computer" in Windows to see if the sdcard was mounted. Then transfer your ROM as you would with a USB flash drive.

soupmagnet said:
Don't worry about using ADB at the moment. Boot into TWRP using the FireFireFire1.4a boot menu you described before, and select "Mount". Make sure there is an [X] on the last option and press the button at the top that says "Mount USB storage". Then check under "My Computer" in Windows to see if the sdcard was mounted. Then transfer your ROM as you would with a USB flash drive.
Click to expand...
Click to collapse
Short answer: Nothing appeared in My Computer
---------------------------
Long Answer: I tried every combination of processes that I found through the various troubleshooting methods.
I have 2 chords: A white Kindle chord I used for my old Kindle 3G and a blackberry USB chord that fits the same. I also tried every function with every chord with both Windows and Ubuntu just in case because I saw that in other threads where people were having issues that they were just not doing the proper process based upon the circumstances. I also tried all of these functions while the plugged in Kindle was reading as:
Other devices -> Kindle (Big K)
&
Android Composite ADB Interface
In my device manager. In all the cases I tried the best case scenario was a "removable disk" appeared in My Computer but it read "please insert a disk into Removable Drive" if i tried clicking on it. I also tried all of these functions with each of my 4 USB ports (all 2.0 ports) (which all work for any other device)
So I tried every port with every chord I have using every combination of processes I found in other threads to do what you advised and it did not show up. It took a while but I wanted to be concise because other people do not give enough background or try everything before coming back to the forum.
(Just for reference I tried the process outlined in "How can I verify the drivers are loading?" section in http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2 among other threads for troubleshooting advice and guides.
-------------
I will learn more about this ADB pushing process thing using CMD because the only glimmer of hope I have had in the past 2 days has been getting my computer to read the device when I used KFU. It worked one time and it was magical. Unless there is anything else I can try or if someone can confirm that this thing is completely broken beyond repair.

It's not broken it's just a little unhappy with you right now you may have a combination of things going on. Your drivers my be mistreating you and either you have an sdcard mounting issue or the drivers are affecting it. How ever it is I would be happy to help you sort through it. The only thing I ask is that you complete your thread afterward with a detailed description of what it took to fix it for the benefit of others in your situation. So pm me when your online and if I can I will assist you through it.
Just to let you know it may have been simulating mount in recovery as well funny thing those setting are useless when you want to get something done

Thepooch said:
It's not broken it's just a little unhappy with you right now you may have a combination of things going on. Your drivers my be mistreating you and either you have an sdcard mounting issue or the drivers are affecting it. How ever it is I would be happy to help you sort through it. The only thing I ask is that you complete your thread afterward with a detailed description of what it took to fix it for the benefit of others in your situation. So pm me when your online and if I can I will assist you through it.
Click to expand...
Click to collapse
There was a fairly simple solution that should be universal for most issues if you require pushing a file to your device.
Here is some background stuff that you should have before attempting to fix the problem I had and starting from scratch.
You will want this installed: http://developer.android.com/sdk/index.html
And the Kindle Fire Utility: http://forum.xda-developers.com/showthread.php?t=1399889
And in my case the Modaco ROM: http://www.modaco.com/topic/350682-14-jun-gr9-631-modaco-custom-rom-for-the-kindle-fire/
Unzip the Kindle Fire Utility into c:\kfu
Install the Android program
Create a folder titled Software in your c:\kfu and put the ZIP file that you downloaded from Modaco in the software folder
Make sure to go through the "How can I verify the drivers are loading?" section in http://forum.xda-developers.com/show...71&postcount=2
Plug your USB chord into the kindle first (while it is off) and then plug the chord into the USB port
It will bring up TWRP
Go into the options and make sure that you push Restore Defaults and ensure that any options with "simulate" in them are unchecked.
Open up cmd.exe and type in "cd c:\kfu\tools"
Go to the mount option in TWRP and mount the USB
type in ADB push and then drag the modaco file from the software folder onto the cmd window and it will show you and then type in \sdcard\
ADB push (the modaco file) \SDCARD\
It should take a few moments to transfer and it will say that it is done
Unmount and then unplug from the computer. Go to wipe and wipe everything other than external memory, then go to install and find the file you pushed onto the kindle in the file folders. Push on the file and it will ask you if you want to flash it, select yes.
After that is complete select reboot and it should automatically reboot and then go to the proper startup screen.
Special credit to Thepooch for providing all this information to me. I believe that should be everything.

Working in the directory that adb is in is important and this
Code:
adb push <exact file path> <exact file name> /sdcard/

[Q] Kindle Fire bricked, have factory cable but can't boot recovery, please help!

Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail

farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.

Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!

farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.

I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC

ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.

farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159

ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.

Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.

farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.

Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?

Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?

"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.

jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs

[Q] Not your average brick...

This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.

kyle8b16 said:
This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.
Click to expand...
Click to collapse
If you want to re-do the partitions and install the very latest bootloader and TWRP +ROM, you should install otterX (1st gen only!!). Follow the steps in this link and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=2671619

kyle8b16 said:
This post is coming after hours upon hours and days upon days of research, trial, and no success. Hopefully someone can help me out...
I was asked to work on a "bricked Kindle" due to a reputaion among friends and co-workers of being the "go to" guy for rooting, custom ROMs, and the like. I am familiar with adb, fastboot, etc, and have used them often. Even though I didn't know what had happened to this particular Kindle, I was confident I could fix it.
I got it and began investigating. It powered on and FFF 1.4a popped up, followed by the stock Kindle logo where it stayed. I rebooted and used FFF to boot to Recovery, which is TWRP 2.6.3.1. Further checking found that there is no ROM installed, only FFF and TWRP, nothing else. I thought "This will be easy!". Wrong...
I connected it to my Windows 7 PC and ... nothing. Didn't even show as anything being connected at all. Installed drivers, still no luck. ADB doesn't see it either. Tried using 'mount' in TWRP, nope. Then began my trip down the numerous fixit programs KFU, FireKit, ReKindle, etc. Not a thing. Linux doesn't see it either. Like it is not even connected. Even tried the USB Shorting Trick, still wont register on anything, as anything. Bought a Fasboot "Factory" Cable, still nothing. My only hope at this point is the terminal in TWRP. I have successfully run various commands in there, verified the different boot modes with idme. Found that it did change to Fastboot (4002) and back to Normal (4000) when asked. Attempted to use Parted for some investigation but it is difficult to use in that terminal. I did discover that several partitions are screwed up. How to fix them is beyond my expertise. My thought at the moment is to wipe the thing 100%, partitions and all, to see if I can then connect at least with FK or something to reformat and put FFF and TWRP back on (latest versions). Also when looking through the logs in the terminal, it listed failures with an OMAP clock file.
The original owner told me he knew it couldn't be fixed and told me to keep it. I think it is still possible to salvage it. Any ideas?
Thanks.
Click to expand...
Click to collapse
Even people think of me as a 'go to' guy. I love that respect
Sent from my A114 using XDA Free mobile app

Sounds like the USB port could be bad.
Sent from my PHOTON Q using XDA Premium 4 mobile app

Wish I could...
bflobills said:
If you want to re-do the partitions and install the very latest bootloader and TWRP +ROM, you should install otterX (1st gen only!!). Follow the steps in this link and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=2671619
Click to expand...
Click to collapse
I would like to give that a try but the problem is that I cant push anything to the device w/ adb at the moment. No computer, Linux or Windows, will recognize it at all (not even incorrectly). I thought initially that the usb port on the Kindle was bad but I can get it to react differently when it is plugged in vs not. For example, when the fastboot cable is connected it stops at the FFF boot screen as if it is in fastboot, but nothing recognizes it and fastboot doesn't work. When I connect to the computer with a regular cable it will turn the Kindle on and charge it, but no connection. I am still leaning toward it being some kind of software problem on the Kindle.

Return2Stock Tool
kyle8b16 said:
I would like to give that a try but the problem is that I cant push anything to the device w/ adb at the moment. No computer, Linux or Windows, will recognize it at all (not even incorrectly). I thought initially that the usb port on the Kindle was bad but I can get it to react differently when it is plugged in vs not. For example, when the fastboot cable is connected it stops at the FFF boot screen as if it is in fastboot, but nothing recognizes it and fastboot doesn't work. When I connect to the computer with a regular cable it will turn the Kindle on and charge it, but no connection. I am still leaning toward it being some kind of software problem on the Kindle.
Click to expand...
Click to collapse
Hi, Noob here but I faced a similar situation to you just last week. The ONLY thing that helped me is a tool known as Return2Stock by N2A. Since I am new, I cannot post outside links but I made a post on reddit in the kindle fire "hot" section titled Bricked Kindle Fire With No Access to TWRP (it's on the first page about halfway down. It describes what I had to do in order to get it working. But it did work! And I tried EVERYTHING. Good luck

Trying ti fix a bricked Kindle Fire HD 8.9 for a friend

Hey Guys,
OK, so I have spent about 5 hours scouring this forum and google and am in need of some help. I am trying to fix a kindle for someone and I really dont have much experience with Kindle at all but have rooted most of my android phones with no problem and flashed different roms etc... Well this thing seems a little hosed. When I turn it on, it shows the kindle splash screen then goes directly to the red screen. I wanted to use fastboot but device manager doesnt even show the device. When I power on the kindle, it will flash the jem device (Jem-PVT PROD-04) and then it goes right away so I dont really have any opportunity to install the drivers. WIth that being said, I cant use fastboot (just is stuck at waiting for device) or adbdriver.
My buddy attempted to root the kindle and was able to using yeymasterroot or something like that then proceeded to use fireflash and using freedom boot and twrp.
Has anyone gone through this and fixed it? How can I get fastboot to work (I tried installing the USB drivers and also installed the Android sdk). Is this thing just hosed and I should give up? I really dont want to and look at it as a challenge and was hoping maybe someone has had the same thing and figured it out? Oh, and I asked what version it was on before and he said 8.5.1.
Thanks in advance.

The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.

macman005 said:
The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.
Click to expand...
Click to collapse
Thank you.
Just an FYI for anyone that runs into the same issue. I absolutely tried every method I could find (I must have spent probably 15 hours or so researching) to use WIndows and finally gave up. I tried the most recent version of Ubunto live and this did not work as well. Soupkit would not install, I had to use Ubunto 12.04. Once I loaded this, I installed soupkit then tested fastboot and was good to go. Once in fastboot, I used the followink step by step wiki (follow every step to a T):
wiki.cyanogenmod.org/w/Install_CM_for_jem
Now, I have it working and it is fast and nice (albeit a bit heavy).
I hope this helps someone avoid wasting all of the time that I did for this but I am glad it is finally working. Next I will install Lollipop.

Trick how to fix this
maybe it is too late but it will help someone else probably if they face the same issue, first you will need to reboot windows with drivers signature disabled and then install these drivers who was made compatible with the jem model (the only one that worked for me) you can install them by just right clicking the .inf file after extracting the archive, or by going to the device manager and then make it show the hidden devices and you will see the Jem-PVT PROD-04 fadded in the devices list, you can right click on it and access to properties and from there you can install drivers via update (I guess you have the minimal windows knowledge to do this)...