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?
Related
Guys,
Details: Using Windows 7 64 bits, on a notebook.
Here is the full history of my brand new brick... call me stupid.
Second day with my Kindle Fire, I tryed to root my kindle fire.
Downloaded the KFU 0.9.5, instaled the drivers.
But the KFU wasn't workig... I only was getting the ADB offline status and the "waiting for device" message.
When I realized that the drivers I had were from my Motorola Milestone.
Next step: Uninstall the wrong drivers, and reinstall the new ones.
Only with this i could get the device to work with KFU.
Open the Run application at KFU folder.
Choosed option 2: Install Permanent Root with Superuser.
All worked fine until i get the message "with great powers come great responsabilityies" press any key to continue...
[EDIT: Tried to install Gapps extras... I don't remember if Kindle was dead before this or after]
The Kindle rebooted, got to the screen with the "kindle" word, and died.
Since that I'm getting no power on, no led lights, no response when connected to usb... nothing.
What should I do?
Go to Motorola Tech Support (here in my city) and try to use a factory cable?
or
I can only put my hopes on USB Boot Mode?
Guys, thanks in advance and sorry for my english, I certainly made some msitakes.
Or I can try Firekit?
That's strange, installing the wrong device drivers on your computer shouldn't affect your Kindle.
What it really sounds like is your battery died in the process of installing the FFF bootloader. How was your battery before you started? Have you tried holding the power button for 20 seconds for a hard shutdown?
As far as I know, the only thing that will cause power on issues is a broken bootloader. In which case, USB boot with firekit is your only option.
I guess I had at least 50% o battery charge, or more... I can't remember...
If I push the power button now, the Kindle will get warm, as if it was in use. And if I hold for 20s, will shut down...
I don't even started to install de fire fire fire bootloader, I installed the permanent root with super user and then went to install GApps. I guess my kindle was shutdown before Gapps install.
What should I do? Test the factory cable first?
When you say that I have to use Firekit, you are saying that I have to open my Kindle?
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
EDIT:
Reading the FIREKIT Topic, this post: http://forum.xda-developers.com/showpost.php?p=25814062&postcount=26
My issue is kind of different from his... I'm guessing I'll have to open my Kindle anyway... Started yesterday, but I was messing with the case, gonna find some proper tools
VMs will not work. You have to create a bootable Linux LiveUSB thumb drive.
DuendePaladino said:
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
Click to expand...
Click to collapse
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
kinfauns said:
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
Click to expand...
Click to collapse
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
soupmagnet said:
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
Click to expand...
Click to collapse
I guess it might depend on the VM, but I disagree with the generalization that VMs are too slow and have issues with USB.
The only thing I've seen is that Oracle's VirtualBox USB implementation breaks adb. I've never tried VMWare, but Parallels Desktop for both my Ubuntu and Windows setups work perfectly. Never had an issue.
DuendePaladino said:
What should I do? Test the factory cable first?
Click to expand...
Click to collapse
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
aarons510 said:
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
Click to expand...
Click to collapse
Without a working bootloader, a factory cable is useless.
soupmagnet said:
Without a working bootloader, a factory cable is useless.
Click to expand...
Click to collapse
All the scene leads to this... USB Boot.
About the USB stick, I was making some confusion about it.
But, I´ll gonna make one stick right now.
Guys,
I made the usb stick... just figuring how to open the kindle fire, without ruining the case.
But I guess today I'll made the short trick.
Question: I'll keep the 6.3 stock room that i tried to root? Or I'll have to download another ROM?
Is there any know issues about firekit compatibility with ubuntu 12.04?
Like this here? http://forum.xda-developers.com/showpost.php?p=25918331&postcount=10
I WON!!!!
I'M BEOWULF!!!!
Serious now...
Firekit method, with short trick... keep trying... until you find the right spot for the shor... and will work
EDIT:
THANK YOU GUYS!!!
I wouldnt be that happy without your help and your knowledge... You're the real Beowulf!
Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.
Does KFU recognize it? If it does you are good to go.
Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.
http://forum.xda-developers.com/showthread.php?t=1644970
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!
Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.
Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon
Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.
nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?
Alright folks, I would like to start off with a little introduction:
I'm extremely new to the rooting scene, i've been jailbreaking iphones and ipods since day one. That being said, I probably should have spent more time researching this technique before I went through with it.
Fast forward to today:
I tried rooting my device awhile back, wasn't a 100% successful and I really didn't have the time to work it out. I did have FFF installed and the next window (which i'm not exactly sure what it's called, which allowed me to boot in various moods and such)
Earlier today I got stuck in a boot loop, where my kindle would turn off as soon as i restarted it, and after i selected normal boot mode. I decided it would be a good idea to try a different boot option, so i tried the FF boot, which completely ruined my day.
My current situation is as follows:
I'm currently stuck on the first FFF screen (yellow triangle, with the green light on), i can do nothing else from that screen except hard (cold) reboots. When i plug my kindle in (Mac, windows 7, windows XP), the device is not recognized and i get zero response. I've tried a decent amount of suggestions on this forum, including Kindle fire unbrick (Which can somehow see that there adb is installed, but the bootmode is unknown)
Help out of this current situation would be wonderful. I'm really in a jam here.
Sounds like you are stuck in fastboot and you might have a dead battery too.
You should read this...
http://forum.xda-developers.com/showthread.php?t=1552547
1st post for background information, 2nd post for making sure your device drivers are loading/working, and the 3rd post for fastboot and adb commands. You'll probably need to use fastboot to change the bootmode back to normal.
This one...
http://forum.xda-developers.com/showthread.php?t=1623244
address dead battery problems. You might be affect this by this one as well.
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
B4CKlash said:
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
Click to expand...
Click to collapse
What do you mean by recovery screen? Because your first post said FFF and that's your bootloader. If the yellow triangle boot logo comes up and that's all that the display does (doesn't go black and redisplay the boot logo), then it's in fastboot mode. Windows should give you an indication that it's connecting with a series of 2 connection beeps (low->high tone) without a following set of disconnect beeps (high->low tone). The device manager will show something new in the list (this is covered in post #2 in the first URL I pasted for you).
Yes, you need to get something to get recognized by your computer then you need to install the proper drivers for it. Look at post #2 again, and see if you can figure out what device is appearing in the list and get the drivers loaded for it. If you get absolutely nothing, there's something wrong with the bootloader, your USB cable, USB port, or computer in general and it's a bigger problem.
If nothing happens on your computer, find another one and hook it up there. You might also look at this...
http://forum.xda-developers.com/showthread.php?t=1430038
and see if Linux can help you.
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
B4CKlash said:
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
Click to expand...
Click to collapse
Windows will be the only one that of the three that will beep at you. There's a better chance of you getting something done with Linux, but it's starting to sound like a bootloader problem to me. There's another user with a similar problem to yours and he's basically where you are now. Both of you might have to open up the case and get it to USB boot mode where you can upload a bootloader to it through USB. Try Firekit and see if it gets anywhere.
After toying with jailbreaking/modifying iPhones, taking a Unix/Linux course at a local community college, experimenting with different linux operating systems, and stalking these forums for about the last month, I figured I would purchase myself a "Bricked" Kindle Fire and have at it for funsies. Well, I bit off more than I could chew. I'm stuck as much as the Kindle Fire is at what I think is the boot screeen for the FireFireFire Bootloader. It powers on and loads the Kindle Fire blue logo with a v1.4a in the top corner. Then, selects and deselects "normal boot" "recovery" "reset boot mode" on it's own without ever picking one! I'm not sure what the prior owner did to this thing but I'm assuming they at least attempted to root it. I've tried SoupKit, KFU, Kindle Fire Unbrick Utility, and tried adding the google USB driver for the thing in Windows 8. The worst part of it is that it's not recognized in either Ubuntu (terminal - tried lsusb) or Windows 8. Any help, suggestions, or even comments telling me that I'm dumb for doing this would be much appreciated. Thank you!
Your saying it runs through the bootmenu selections on its own? That`s a new one for me. Have you tried to select one? To get the Driver installed on windows 8 you must disable driver signature verification then install the driver.
It doesn't respond to me trying to select any of the options. It just cycles through each one from top to bottom. Last night I went through the steps to disable driver signatures (posted here: http://forum.xda-developers.com/showthread.php?p=34626361) I was successful in installing the drivers but the computer still does not recognize the device. I was also able to download/extract the Android SDK to my computer. I ran ADB and it showed the driver was installed. I believe ADB should recognize the device?
There are two methods on that page which one did you use? The one in post #8 will work but I just simply hold shift then click restart then follow the rest of the instructions to disable it. If its in fastboot adb will not recognize it but I bet your shell is corrupted as well when you select recovery it should go there unless your recovery is broken.
I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.
When you plug it to the pc or the wall charger? To the pc isn't that strange could be the cable itself, to the wall might raise an eyebrow to early to tell. Im gonna send you a pm.
CH1215 said:
I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.
Click to expand...
Click to collapse
It looks like you need to replace the bootloader...probably via usbboot.
Arrrgh The dreaded broken bootloader time to work a little firekit.
I did try a few of pokey9000's firekit options in SoupKit but to no avail. I am a bit confused as to where I need to place my metal object to "short the point" as I couldn't find any threads with pictures. I will continue to reasearch/apply usbboot and return to you with my findings. I really appreciate the help both of you have given me.
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 this is the test point there is a small metal frame surrounding it . Start the script when it says waiting for omap44xx contact the test point and just as you lean whatever you are using to short against the small metal frame and plug in the usb at the same moment. Keep it shorted till the script runs through 4 stages. The script you need to run is the usb fix parts install fff and twrp. It is best to brace the kindle against something so it does not slip as your trying to perform this maneuver. Caution not to contact anything but the test point and the metal frame to prevent permanent hardware damage.
I used a modified safety pin, used the correct option in firekit, and followed your directions, but it didn't seem to do anything. I can tell that the prior owner(s) had tried this before as the area I am to place the pin looks a bit scratched. On another note, I had to boot my windows partition to get something off of there late last night and I left the device plugged in. Surprisingly, this morning the device was showing up in the system tray as "kindle." I was curious and looked at the properties and it's showing the drivers are working and that it's an "Android phone." I don't know if this is a good indication of anything or not.
When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.
Thepooch said:
When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.
Click to expand...
Click to collapse
"Android Phone" expanded in Device Manager shows "Android Phone ADB Interface." When I try the command you suggested it says, "error: device not found."
I know this has been covered thoroughly in this forum multiple times, and I have really tried to read as many threads as possible before asking.
I rooted my device months ago and finally got a Nexus 7 and want to give my KF to my kids but wanted it stock first. I must have done something in TWRP that removed my bootloader.
I have tried the unbrick tool, I ordered a factory cable from Skorpn (awesome work btw) and by using KFU, my PC can finally see my Kindle.
The problem I'm having is that none of the commands are working and it looks like the bootloader is either bad or completely gone.
It used to turn on and the logo stayed bright. After I used the factory cable it now turns on, blinks, and goes dim.
All the drivers loaded correctly and KFU see's it online.
When I try to reinstall TWRP through KFU it downloads, but is stuck at waiting for device.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2433 KB/s (510876 bytes in 0.205s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
After reading further, I think I formatted too much and wiped the SD card partition. It doesn't seem like there is a bootloader at all.
Did I miss something in all the reading?
Thanks.
So after doing even further reading I found
http://forum.xda-developers.com/showthread.php?t=1638452
I connected the factory cable and the logo is now staying brightly lit, so I assume it's in FB Mode.
I downloaded TWRP based on the link and FFF, but now I don't know what to do with them.
I went to ADB's site and installed SDK, but I'm not sure how to get the cmd portion to sideload TWRP and then FFF.
I'm doing my best to following along in the instructions and went to the ADB site and installed SDK.
I saved it to my C drive but when I try to do the following, along with "adb devices,
c:\Android\android-sdk-windows>
I get:
'adb' is not recognized as an internal or external command,
operable program or batch file.
Update:
NVM, I had it in the wrong directory.
Once I got that figured out, I did an "adb devices" and no devices came back. Of course I have the factory cable connected and I'm not sure if that matters.
Update:
Ok, now I used a standard USB and it sees my device, but now the logo went back to going dim after reboot.
So it looks like my problem is fairly common, however forum searches don't seem to be helping.
It looks like I wiped too much in TWRP.
Now that I finally figured out ADB, I'm confused about the factory cable.
When it's connected ADB does not see my device but the logo is lit bright yellow. When I use a standard cable ADB sees the device but the turns on and goes dim but the logo is still there.
I've downloaded the ZIP files for TWP and FFF, but I can't seem to figure out how to side load them no matter what I do.
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Copcheck said:
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Click to expand...
Click to collapse
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
leroy329 said:
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
Click to expand...
Click to collapse
No luck with adding persistence.
I get everything to to boot in Linux, followed all the instructions, but Soupkit still does not see my Kindle.
I've tried my factory cable and a regular cable. No luck
Some has changed though because now my Kindle logo light is solid bright whereas before it would blink and dim.
Good luck to you!
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Copcheck said:
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Click to expand...
Click to collapse
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
When I unplugged the factory cable from the PC and the KF, I could have done 1 of 2 things. Powercycle the KF and hold the power button down to get into TWRP or use a regular USB to side load a ROM and then load it.
Good luck to you, I hope you get it figured out.
Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
If you're getting the Kindle Fire orange and white, you haven't installed the new bootloader. Rerun KFU with the Kindle in Fastboot (using Cable) and select install FireFireFire. This will give you the bootloader to reboot to recovery.
Edit: You might as well reinstall TWRP while you're at it, just to be safe.