Related
UPDATE: I added "solved" to the title since I am now unbricked. That said, I do hope someone will pop in and tell me how to run the shell scripts on a mac...
Click to expand...
Click to collapse
Hi there. I have spent several days searching xda forums, popping into the kindlefire irc channel, and searching google however have not yet figured this out, could use some help.
I have read: the Kindle Fire Beginners Guide, the Kindle Fire Unbrick thread, The Kindle Fire Utility thread (yup the whole thing), and more.
According to the Kindle Fire Beginner's Guide, only 1% of all brick situations are actually a brick, so I'm going to persevere and go ahead and ask for the help, because also according to the guide, if your fire can't be seen as a device then actually it's a brick. To quote: " unless something else was done to the device after the change in bootmode preventing access to adb or fastboot commands. Then it’s actually a brick at that point."
I can't be sure if anything else was done after the change in bootmode so I'll just explain how I got here and hopefully someone can help out.
I have a mac mini running Os x 10.6.8, and the Kindle Fire which was running stock version 6.2.2.
I used the kindlewater root method to install firefirefire and cwm recovery. Was able to boot into recovery by pressing on the power button for it to go orange and then load the recovery options.
Before doing anything at all (and in consultation with St3p_2 of this forum, one of the kindlewater developers), I decided to perform a backup in preparation for flashing a ROM.
so, I booted, went into recovery, navigated to "install a .zip" and chose "backup" at which point I got a message/nag/reminder that this was a permanent change, and I selected "ok". It did it's thing for a while, went into reboot, and I then had the firefirefire logo blinking in a very very slow loop.
It was recommended to me to perform a factory reset by holding the power button for 2 solid minutes, which should then have returned me to stock. Actually, the first time i did it for minutes I went from having a very slow blinking firefirefire to having a rather fast blinking firefirefire. Following a suggestion i then tried it with the kindlefire unplugged. This resulted in a plain black screen until the fire was plugged in again: no boot, no indication of response to use of the power button. Once plugged in, it has gone back to the rather fast blinking firefirefire logo.
I read through the Kindle Fire Utility thread, found the v0.9.2 version prepared for mac and linux, and downloaded it. Although I am not new to terminal, I am not familiar with what command language is necessary to perform the actions required by this tool. If I open the install_drivers.sh with terminal, i get this:
Reverie:~ apple$ /kindlefire/Kindle_Fire_Utility_MacLinux_0.9-1.2/install_drivers.sh ; exit;
This file will install the correct adb_usb.ini file for proper Kindle Fire detection.
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
so I tried running it in the console. I will spare you the output of the console as it appeared to be merely a printout of the actual code of the file and was quite long.
Trying to run the file runme.sh in terminal before running the install_drivers.sh in the console, I got error messages stating there is no such command, or no such file, depending on my command language.
After running the install_drivers.sh in the console, when I try to run runme.sh in terminal, i get this:
/kindlefire/runme.sh ; exit;
Reverie:~ apple$ /kindlefire/runme.sh ; exit;
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure adb is in your path
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue... --- STARTING ----
--- WAITING FOR DEVICE
Which I affirmed because all the requirements had indeed been set that way on the device before the bricking happened. After "starting" and "waiting for device" nothing happens even waiting indefinitely (more than half an hour) and then it never finds the device.
When I go into terminal and type: "adb devices" I get:
Last login: Sun Mar 18 17:08:38 on ttys001
Reverie:~ apple$ adb devices
List of devices attached
Reverie:~ apple$
This result is the same both before attempting to use the 0.9.2 mac utility and after.
I really am stuck at this point, as everything I find with instructions on how to "unbrick" does require that the machine recognize that your kindlefire is attached. Running any of the tools I find requires that basic bottom dollar, which I don't seem to have.
That said, the behavior of "nothing at all: blank screen" when unplugged, and the behavior of "blinking firefirefire logo" when plugged in would tend to indicate that at the very least the device knows it's plugged in and getting juice, and some process is happening when that's true.
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
sisterdelirious said:
Can someone help? Is my next step to purchase a factory cable, or do I have a software solution available to me that I just didn't find in this haystack of solutions?
Click to expand...
Click to collapse
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Wow... so simple...
b63 said:
nothing doing when unplugged seems like a dead battery
would try to charge it with the wall charger for some hours regardless if the orange light comes up - this can last a while
Click to expand...
Click to collapse
This was the deal. When plugged in with the usb cord it didn't seem to be giving it power and being powerless could not be recognized by the computer. Plugged it into the wall charger and Voila! was able to start up just fine, still rooted via the kindlewater method, capable of being booted normally or booted into CWM recovery. Awesome!
I also did a quick double-check, and now that it's powered-up, running a terminal and typing "adb devices" actually returns a list with the kindle (serial number?) on it.
furthermore i don't know which version of kfu for mac you'r using but zergrush is'nt working any more since stock rom 0.6.1
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I read through everything and the version of kfu that was modded for mac was 0.9.2 which I mentioned in my original post. Sounds like since I was on 6.2.2 that mac version is definitely not going to help me (both kfu out of date and stock version out of date on zergrush) if I were to want it for rooting purposes.
for rooting use kindlewater:
http://forum.xda-developers.com/showthread.php?t=1443071
Click to expand...
Click to collapse
that is the one i used. I was looking for a mac tool for post-root rescue methods...i had thought that the kfu mac version had valuable rescue/unbrick capabilities but at this point I don't remember.
as far as i know the commands need to be entered with a ./ in front ie: ./install_drivers.sh
Click to expand...
Click to collapse
[/QUOTE]
Thankfully, I don't need to try that. my kf got properly unbricked just by plugging it into the wall charger.
Great guide, it was the battery
kinfauns said:
Thanks for reading my guide. I hope it helped you a bit.
Mac OS X is also my primary OS and I take my hat off to you for even trying things this way. I took the easy way out from the very beginning and just used Parallels Desktop to build Windows and Linux virtual machines. If things ultimately don't work out, you might want to try going that route as well. I believe Parallels offers a demo version if you want to see it in action. Regardless, I don't think that matters quite yet, because I tend to agree with b63 here. I think the biggest problem you have right now is a dead battery.
Click to expand...
Click to collapse
Thank you for your guide. I thought it was extremely well written and very helpful. It definitely helped me relax a little stress-wise while looking for a solution.
That was it (dead battery). I did try meddling around a bit with virtualbox virtual machines: a windows 7 ultimate, and a linux box that I have that does not have internet access making doing anything realtime while reading suggestions just isnt easy/feasible right now. I found that the virtualbox vms did not have access to the usb devices (flash drives, external hard drives, ostensibly if it were visible to the computer the kindle) despite my installing some optional extension packs for that purpose. I didn't explore the vms further to linux or xp simply because of the time required to install and configure a vm. I also didn't rewire my home so net access went to the linux box for the same reason... ultimately both are possible but both more hassle than it seems to be worth before simply asking the question, can it be done on a mac?
I've never had a dead battery, so I can't comment directly, but take a look at this thread, starting at post #226...
http://forum.xda-developers.com/showthread.php?t=1392693&page=23
There some back and forth for a couple of pages, but that user describes symptoms that sound very much like what you are seeing right now. I think you should try the wall charger first. Plug it in, force the Kindle Fire to turn off and just try to let it charge overnight or something. If you cannot get your KF charged with the stock wall charger, you might want to buy a factory cable. From what I gather, that user reported that his Kindle Fire booted into fastboot mode by using the factory cable even with a (nearly) dead battery. He was then able to flash the stock software, which is able to handle the dead battery situation better than some alternative ROM and have it go through the charge cycle.
Click to expand...
Click to collapse
I'm just so glad this worked. Thank you for your help!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Similar issue
My KF is seeming to have a similar but distinctly different issue as the OP. Because I can turn on the KF without it being plugged in, I cannot imagine that it is a battery issue.
When I plug it in to a Windows machine, the FFF bootloader comes on, the KF seems to connect, be recognized, fail at driver installation (which I have done manually, with no success), and then disconnect. This prevents me from running any sort of commands.
When I connect to my Mac, I get the FFF bootloader and then no response whatsoever.
Trying to run commands from Terminal or the Command line or using KFU on my Windows machine all result in a "waiting for device" message.
Not sure what I should do from this point to get it back to accepting adb commands. I'm confident that once I do I'll be able to save it, but at this point I'm stuck.
Any ideas?
i live in australia, and got a kindle fire for my b'day, and wanted to access the features that arnt allowed outside the US. my first search i came across rooting it, and it seemed straight forward, the instructions, which was for kindle fire utility. i installed the drivers, then did run.bat, that worked and detected the kindle. then it said to go to bootmode menu, then install permanent root with superuser. it lasted about 2 seconds then it rebooted the kindle. thats it. unless i misread something. it looked exactly the same as before, i didnt know what to expect, but some hint that something had changed, so i figured it didnt work. then i saw the bootmode menu, and selected normal, and that just reset it, then chose fastboot, not knowing what it did. so i tried that. now my kindle isnt detected by the pc at all, it just says kindlefire on the screen, and the power light is orange.
most of the fixes i have come across all start with "we assume you have this or this installed on the kindle, and that it is detected in some way by the computer". but it isnt being detected at all. i saw the fireusb thing, with ubuntu, i attempted that, but it didnt seem to recognise the fk file, which was only 9mb, it was the only file the instructions said to take, and that its supposed to unpack to more tools to manage it and get it to register that the device is plugged in.
then the only thing else i could try was opening the back of it, and doing the shorting out thing, then plugging it in, but KFU didnt detect it and not sure what else to try. i am a complete noob at this i know, so i dont know where to go from here.
edit: turns out the kindle doesnt like being detected in 3.0 usb, or usb hubs. so if you are trying to get it to detect, use the ones in the back of the pc lol... soo much wasted time on this over such a simple thing, but im glad it was a simple mistake, and not a major problem. though now i have the issue of having small sratched and stuff on the side when i opened the case, but oh well, learn from my mistakes!
have you tryed holding the power button for like 20 seconds and completely powering it off then powering it back on? Chances are your stuck in fastboot many people lately have had this happen so your not alone. Some say to power it off have the kindle fire utility window open plug your kindle in it should power back on then recheck status. Look in device manager and see how it appears there windows is terrible with drivers when this happens it will try to install what it thinks best even if the device is unknown rendering adb useless until the driver is reinstalled correctly. Most the time this is not enough to set the bootmode back to normal because it cannot detect your device correctly. http://forum.xda-developers.com/showthread.php?t=1670405 this may help but its not the only thing that can be done. If some of the files actually did get pushed to your device such as fff the bootmode can be changed via the bootloader. Try the power down thing see what you get and post back.
---------- Post added at 01:03 AM ---------- Previous post was at 12:12 AM ----------
also look at this thread http://forum.xda-developers.com/showthread.php?t=1670300
Another thing simply just rooting your device does not change how it appears its not until you install twrp and fff that it changes there are simple ways to do that first we need to get your boot mode corrected and ensure you are rooted then the rest can get sorted out. Check how your device is listed in device manager first.
sorry for the delay. spent all day just trying to install ubuntu, then connecting to the internet wirelessly, seems to have a lot of issues. anyway, in the end i got it all set up, followed that guide, then ran firekit, but still not detected. in windows and ubuntu, when its plugged in by usb, nothing at all shows up in device manager, or lsusb. ive tried doing the short trick, then plugging it in, still doesnt get detected. and honestly i think when i thought i rooted it, i may have misclicked and instead of selecting instant permanent root or whatever that command was, i just did a normal boot, so im pretty sure i selected fastboot for a stock kindle. i know the usb cord works cause i use it for my phone.
adb devices doesnt detect it either. i got all the doesnloads from the link you posted, would they all be up to date? also the adb_usb.ini file, had to get online, but not sure if that matters.
In Linux, type
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
...and make sure you have the following:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Reboot to save any changes you've made and check "lsusb" again.
i added both those rules, one of which was already in there, but it still isnt being detected. typing lsusb, then up and enter repeatedly as i plug it in doesnt show any changes at all, its not being detected.
While unplugged, type
Code:
udevadm monitor --environment
Plug it back in and see if you get a result.
sadly not. tried plugging other things in, they all appeared, also my phone with the same cord. but nothing at all when i tried the kindle, with it powered off when plugging it in, and with the shorting out thing, nothing at all. i dont understand how booting in fastboot by accident, with a stock kindle, could make it not be detected at all, ive read people causing worse things getting it to at least be picked up. im pretty sure thats all i did, i cant think of how i could of done anything worse.
That's interesting...I'm having the same problem with mine but I was led to believe it was my VM causing the problem.
So, just to make sure...
Are you using a VM Linux install or USB or other?
Have you tried multiple usb ports?
Do you have FireFireFire installed and if so, what version are you using? (If you're not sure, what does your boot logo look like?)
What Linux distro/version are you using?
this is the first time ive ventured outside windows, so not sure what you mean by vm, but i installed ubuntu with a disc, to a second hard drive that i had in my comp.
and nope, dont have firefirefire installed, im pretty sure its just a stock kindle still, just stuck in fastboot by mistake, and not being detected by any usb port.
also, would a factory cable work? if its makes it boot differently, you would think it would? i really suck at making things, but http://forum.xda-developers.com/showpost.php?p=23049902&postcount=254 is selling them. sure it would probably take 2 -3 weeks, but if it works then thats better then not using it forever lol. and if i get it fixed before it even arrives, well, cant complain about that.
A factory cable will only help if you can get Linux to detect your device. Considering you can't get Linux to detect any USB event when plugging your Kindle in, it most likely points to a problem with your Linux install.
It would be very helpful to know what version of Ubuntu you are using.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
though there is a few updates in theupdate manager. but last time i installed them, it completely disabled my wireless adapter and ened up reinstalling ubuntu to get it to work again cause i couldnt figure out how to get it detected again. but redownloading it all now to see if its any different. i hope it is just a problem with the install, at least thats something i can work on.
at soupmagnets suggestion, i made a liveUSB, which i had tried to do earlier, but didnt succeed, where as now it does work, im pretty sure i have the drivers now installed, but not sure where to go from here, with it still not being detected at all.
haaa... im an idiot. just putting that out there. ok, so i got the kindle detected. turns out it was the usb ports. one was usb 3.0, and the others were in a hub, which apparently the kindle doesnt like. i got frustrated and plugged it into the back of the pc, and it is now unknown device in device manager. thinking i should go back into ubuntu, see if its also detected there, and go from there
oh yeah the usb is a problem and use 2.0 and go back to ubuntu you will see its detected in a couple hours Im gonna retest soups script for udev rules but I think you will have success now
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
in fact I think using 3.0 usb is quite dangerous
i didnt go back to ubuntu, i just used KFU again, and just tried doing normal boot. and it worked. its back up and working. ill try rooting it again now, being more careful this time, sorry for the waste of time, but thanks to soupmagnet for helping. now that its back to stock, i do stil lwant to root it, and now with ubuntu installed, what is the best noob friendly guide to use to just get the basic things up and running.
yayyy Im glad you got it goin check allow installation from unknown sources under device and install twrp first then fff bootloader no need to root flash a rom and gapps once your familiar all roms are rooted
You can select these options in kfu watch the dialogue on the screen you can see the files downloading and getting pushed to your kindle just make sure your connected to the net I suggest running one of the options without your device plugged in first do a reboot on your computer plug your kindle in check for adb online boot status normal and go for it
---------- Post added at 11:38 PM ---------- Previous post was at 11:23 PM ----------
or go this route http://forum.xda-developers.com/showthread.php?p=24129239
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!
So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
hi I am using the safe root method of root and trying to flash the FFF and TWRP , in this stib I am stuck in the fastboot mode I unplugged it and reconnect it help plz
Windows version?
How is it listed in Device Manager?
Error message?
I'm having the same problem and had posted a separate thread in the general forum, but coming here I see that I'm not the only one. I was following a guide here on how to saferoot, install FFF and TWRP on a 1st gen Kindle fire and after setting it for fastboot the first time my laptop could no longer see the device and it was stuck sitting at the non-animated "kindle fire" screen. I reset the device, uninstalled drivers and re-installed, rebooted my laptop, all to no avail, so I left it and went to bed. Little did I know that the device wasn't charging while at this screen and just left it plugged to my laptop and went to bed.
Now it seems the device is completely dead, or too dead to boot. The kindle fire screen will display for a couple seconds then the screen goes black, over and over. I used a high power charger(5v 2.2A) instead of the laptop USB port for over 12 hours and it's still just looping. Is there anything that can recover this thing?
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
g17jimmy said:
I
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Click to expand...
Click to collapse
That is what you wanted.
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
Click to expand...
Click to collapse
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
sd_shadow said:
That is what you wanted.
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
Click to expand...
Click to collapse
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
g17jimmy said:
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
Click to expand...
Click to collapse
It will not charge in Fastboot mode, best to flash the twrp and FFF, if it is a stable connection
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Edit: It will not charge in Fastboot mode
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
g17jimmy said:
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
Click to expand...
Click to collapse
not sure, but soupkit may only work on 32bit systems
sd_shadow said:
not sure, but soupkit may only work on 32bit systems
Click to expand...
Click to collapse
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
g17jimmy said:
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
Click to expand...
Click to collapse
tried different usb ports? usb 2.0?
sd_shadow said:
tried different usb ports? usb 2.0?
Click to expand...
Click to collapse
If I leave it hung on the kindle fire screen and plug it in to a different port Windows gives an error (screenshot attached.) If I turn it off (power button 15sec) and then plug it in it comes on and windows sees it properly as an android adb interface, but adb and fastboot still cannot see it.
I haven't looked into messing with it on my mac, I'll check that out, too.
The only live cd I had handy was an old version of Backtrack (BT5r3,) but it's 32bit and still adb and fb cannot see the device, even though the system sees it being plugged in and disconnected.
BTW- on the 64bit Centos 7 side of this system, I installed these packages to make Soupkit at least seem to work:
yum install gtk2.x86_64 gtk2.i686 libXtsc.x86_64 libXtsc.i686 ncurses-libs.i686
Something about the way the new CentOS works won't allow you to install the i686 libraries without including the x86_64 install at the same time.
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
g17jimmy said:
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
Click to expand...
Click to collapse
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
android tools
I like to have two terminals open. One with root permissions for fastboot commands and a normal terminal for adb. Some distros have a root terminal program, but if you don't, just sudo <gnome-terminal>,<xterm>, or whatever your favorite is.
Thanks to SD_Shadow for all his work. I don't know how he can keep track of all the possible screw ups one can perform rooting and flashing, and get to the bottom of things.
sd_shadow said:
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
Click to expand...
Click to collapse
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
g17jimmy said:
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
Click to expand...
Click to collapse
another pic
g17jimmy said:
another pic
Click to expand...
Click to collapse
Uncheck all in Mount options
, then try mounting storage
---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------
Also I don't recommend 2.8.x.x, suggest downgrading to 2.7.x.x
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
OK. I'll go back to 2.7.x and try again.
I tried to downgrade to 2.7.x, but it said "image too large for partition", but while trying to clear that up I seem to have accidentally fixed the sdcard mount. I wiped everything and rebuilt sdcard and now it allowed me to run the install of cm11. What causes the "image too large for partition error"?
Thanks.
Merry Christmas