It has been an awful while since I have posted on a forum, let alone start a thread; Yet, after the "ordeal" I just endured it seemed as though I ought to share what had happened with hope that it may help someone in the future. I apologize if all this is in the wrong sub/sub/sub-forum or anything like that, kindly let me know and I will do my best to rectify my mistake.
So I got a Kindle Fire HD 7" today and the first and most painfully apparent aspect of the device which I noticed was that Amazon decided to viking-rape android; I don't care what anyone says, what they did- well, it's awful. Not being too much of a stranger to rooting, user ROMs, and the like, it seemed only natural for me to try and pursue something similar with this device. So, I do the research, settle on a first ROM to try and hope it's a keeper, gain root, get TWRP working and would you believe it: I forgot my ROM.
Well, I assumed that the Kindle HD would just send me back to the AmazonOS or whatever they call it- but it didn't. It simply kept oscillating from the white/orange kindle logo to the white/blue. I started to get a bit worried, but it's been quite a while in Android (in almost any software/OS, really) when getting bricked means getting BRICKED. So I did some more research. Simple solution worked for me to get me back into recovery:
If your Kindle Fire HD 7" is continuously booting ("bootloop") after installing TWRP
Try holding down the "volume up" section of the volume toggle when the white/orange kindle logo appears, just like you did when you first installed TWRP, for at least three seconds. There's no vibration and nothing changes, really- it seemed like it would bootloop for 10 minutes again, but instead this time after about maybe one minute I was back into TWRP.
At this point, the plan was to ADB my ROM and GAPPS to the Kindle. Unfortunately, for whatever reason the Kindle Drivers that had served me so well, until this point in time, ceased to form a connection between the two devices. This happened at 3pm- it is now 9:20pm (as of this sentence) and I finally got it to work. I will spare you descriptions of all the things that were tried which did NOT work. Needless to say, I did in fact try a significant number of "solutions," and yet; only one thing (or a combination of things culminating with this one thing, in which case maybe i SHOULD try and list everything else I tried... but I can't remember it all so nevermind, anyways...) wound up working then and now:
If Your Kindle Fire HD 7" is not being recognized by your PC
First download these drivers from XDA user stunts513.
Then connect your kindle to the PC. Navigate to "Device Manager." The most simple way would be to type "Device Manager" into the search box located in the Windows Start Menu. If you don't see "Kindle" (it may be under "Other devices") then this solution will not work for you, and you might have an issue with your hardware (perhaps either the Kindle, the PC, or the USB cable.) If you see "Kindle" it will most probably have a yellow triangle on it; if so- lets continue.
That file you downloaded a moment ago is designed to be a component of ADB (this thread is not the place to explain ADB, how to install it or use it; if you are asking those questions at this point I urge you to turn to the XDA search bars and 'ole Googly before proceeding.) Next, regardless of if it actually "does" anything or not, I moved the "usb_driver" folder to the appropriate ADB sub-directory ("c:\Android\sdk\extras\google" in my case, perhaps not in yours, but really i don't think this aspect matters much, anyways.)
Returning to the Device Manager: At this point you may right-click on the "Kindle" listing with the yellow triangle. Having messed around with various drivers I thought it would be a good idea to click on "uninstall." After that I unplugged the Kindle and plugged it back in. It came back up in the list with a yellow triangle. At this point I highlighted and clicked on "Properties." Then selected the option that states either "Update Driver" or "Install Driver," can't remember really. A new window opens and asks if you want Windows to search for a Driver, or if you want to. Say you want to manually designate a driver. This should launch a file browser and now you can navigate to where you placed the "usb_driver" folder earlier. I went as far as "c:\Android\sdk\extras" before checking the "search sub-directories also" check box. Windows foudn the driver, installed it and HOLY MOTHER OF GOD I GOT MY ADB BACK.
At that point I pushed my stuff to the Kindle, flashed it and went merrily along. Hopefully this helps someone- if not, my bad; I still love you all. Except for Jim. **** Jim. He knows what he did.
BAI GAIS!
wrong forum my friend...
http://forum.xda-developers.com/forumdisplay.php?f=1784
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?
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.
ladies and gentlemen. i start this thread after months of being at my witt's end with my first generation kindle fire.
upon recieving my fire last december as a christmas gift from my father in law i coundn't wait to jump at the chance to root it and see what she can REALLY do. burritoroot at the time was the tool of choice to do it, and so i climbed about the band wagon. When the fire's software updated automatically it locked me out of root access (auto update was not a welcome surprise for an avid jailbreaker) i reluctantly picked myself out of the silicone mudd that the laughing folks at amazon had thrown me in while stealing my lunch money and wiped the sweat from my brow and returned to google to get myself back where i belonged, rooted, and easily enough, burrito root2 had dropped just in time to let me dance about with glee in the wonderful world of roothood once again until of course another update.
my bloodthirst for rooting had begun to wain as the new update left all me favorite tweaks still available even without having to get my hands dirty with root access. (google play and my custom skin with the eye candy of ice cream sandwich remained leaving me satisfied)
a few months went by and a stood mild mannered not willing to delve deeper into system files until the filthy root lust reared its ugly head again. this time flaunting a new shiny toy in front of my keen childlike eyes. Free. In-App. Purchases. I smoothly popped open my laptop in hopes to find burrito root three to give me that hot fix i needed. much to my dismay the rules had changed. doing this job would require a whole new batch of tricks. so i took the bait and downloaded KFU .0.9.6 and grabbed my usb cord in hopes that in a few minutes i'd be back balls deep in the 6.3.1 system files of my kindle fire. but of course this would not be the case. after installing the proper drivers to make device manager say what it is supposed to say, KFU wouldnt even notice my kindle was online on my windows 7 64 bit laptop. running as admin yielded different results, as it said adb was online but when asked to do anything it said it couldnt find the hard drive in question. nor the specified path. whats more it behaved the same way without the kindle even connected.
i went to bed to watch netflix on the device and decided to try again the next day. this time with my windows 7 64 bit desktop computer that i had used to root the item before (as well as a motorola backflip that i used for work at the time, but that is another tale.) i downloaded another copy of KFU .0.9.6, decompressed its files and placed it in drive C like a good boy. plugged the usb cord in and crossed my fingers. without a doubt things were working differently. not necessarily smoothly. but differently. kfu was reading the fire and so i chose option 2. the screen went black.
and i waited. and waited. my impatience got the better of me and i decided to start over thinking that things had frozen and become unresponsive. only to find my kindle would only boot to the unfainting orange and white kindle fire screen. frustrated i read as many forum support pages as my brain would allow. for weeks i did this until i found myself getting to frustrated knowing i'd have to finally resort to the inevitable. buying a factory cable.
so when i had some free cash on paypal i went to ebay and found one fro a chinese seller for 8 bucks shipped. eagerly i waited for a week until final arrival. i plugged it in just waiting for all my troubles to just vanish. nothing. i cant find it doing much of anything different. kfu is of course finding adb offline, and windows device manager is calling the device the same thing but stating the obvious (this device doesnt seem to start up properly) on a whim today i plugged it into my laptop. similar story. for about three minutes or so while it just sat rebooting itself every 10 seconds or so before i did more than plug the thing in. that changed when i hooked it up to a charger though. i'll keep you posted though.
my question though is where exactly am i going wrong? is the factory cable supposed to do something different right away? maybe i shouldve bought a factory cable from here to debunk that theory... i will of course appreciate any help i can get with this. luckily my wife's kindle still works so we arent completely tabletless. but being in maintenance by trade i know that $200 is a little steep for a masonry brick.
any wise guides apreciated.
-HJD
Part of it sounds like a flat battery but I think you caught that. The main problem I think you have on top of the battery thing is a broken shell which is exactly what a factory cable is for. I found a couple small things with the approach to using a factory cable that can help. First start with the device off plug to the device end then the pc side, it should boot static at the logo if it kicks into fastboot then recovery and bootloader can be sent to the device rooting stock is obsolete, simply do a full wipe when in recovery minus external storage/sdcard and flash a rom. About the very worst thing you can do is unplug the kindle in middle of a bootloader flash despite your thorough post I can't tell you if thats the case. The second way that helps get it into fastboot I have found is merely going through the paces shift+right click on the tools folder in kfu, select open command window here execute
Code:
fastboot -i 0x1949 getvar product
then plug the kindle in with your cable if the terminal throws product: kindle your are indeed in fastboot at least its been effective for me at that point you can use kfu to send fff and twrp. Mount your sdcard in twrp, transfer rom.zip and gapps zip, then unmount and unplug, wipe and flash away.
If your having trouble with drivers or the situation is worse like as in a broken bootloader then you will need Soupkit to rescue your device http://forum.xda-developers.com/showthread.php?t=1850038.
If the kindle is still at the orange and white KindleFire screen here's what you can try which has worked for me and a couple others at this point:
Plug in the kindle to the computer via a normal usb and turn it on (it should be at the KindleFire boot screen)
Boot up KFU, it probably won't see the device, but this is FINE!!!
Select the option to install TWRP, it should push it to it.
when the Kindle reboots it should be in recovery mode, if not try using KFU to boot it into Recovery mode.
If you get this far use KFU to download the latest amazon update. Find this update.zip and in recovery mount the kindle and move the update.zip to the root of the sdcard. Then try to install the zip and it should put you back to stock which then you can try rooting it again or you can leave it alone lol. You might run into an issue in recovery flashing the zip, if you do here's what you can do to fix that:
unmount data, system, cache BUT leave sdcard mounted
do a factory restore, wipe dalvik cache and cache
fix the permissions in twrp
then attempted to flash the update.zip
Now if you weren't able to get it into recovery or if TWRP failed instead use KFU to try and install FireFireFire. Again, KFU will most liekly NOT see your device, this is FINE, go ahead and try it. Remember use the normal usb cable for this. If you get FireFireFire installed then you can go ahead and try recovery TWRP at that point which then follow the steps I posted above. Hope this helps!
Do a full wipe before flashing.
looks like we got it guys! thank you so much. as for now it back to factory with the inclusion of fff and twrp. couldnt be happier at this point.:good::good::good:
So after reading about a dozen or so threads, all of the FAQ's, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Got a brand new Kindle Fire HD 7" for Christmas, obviously couldn't leave it alone. I have rooted about a dozen models of Android phone, and jailbroken multiple iPhones, so I know the trials and tribulations of this process...
So I attempt to root my KF using the Bin4ry and Qemu method. I have a AWFUL time getting the drivers to properly recognise my KF. I end up finding another person's issue such as mine, and go through the LONG way of downloading the adt bundle, and installing all of the google software and drivers that way. EUREKA! Drivers work, KF recognised by my machine. First shot with Bin4ry after the driver mishap, works fine. Takes 2 attempts with the second step with the Qemu method, but again, I get there. after the first time booting up, I factory reset the Kindle. Still have SU on the apps list. Cool! Now what?
I boot the machine and shut it down about 5 times just to check stability, and hard shutdown (power button for 20+ seconds) twice. Every time all is ok, and SU is still there.
Now time to play. I again go through reading a couple threads on changing the launcher, and decide to go with the Nova launcher for now. I download it from the Play store, yet can't seem to find it on my KF. I for some god awful reason decide "well I saw it a couple threads ago, that someone had an issue with the launcher change the name of launcher.apk to launcher.apk1 and then it worked" so obviously I go and do that. Enter the final time I would boot my KF.
Upon reboot, I get the stock/standard "kindle fire" screen with no animation at full brightness. It then goes black for a split second, and comes back with the "kindle fire" screen, but now with the animated "shiny streak" that goes across the logo. I left it there multiple times for a half hour +, no change.
So I don't freak out yet, cause it turned on, and I find it can't be all that bad. So I check for it in device manager...nothing. Check My Computer just to see if its recognised for memory storage...nothing. I run the Bin4ry script again, just to see...nothing. Run Qemu just to be thorough...nothing. Restart my computer, repeat ALL above steps...nothing. Still never see's the KF, also never makes a tone at me when I plug the kindle into the cable. Change USB ports, repeat all, nothing. Back all of the drivers out, and reinstall all of them. Restart. Nothing. Download kindle unbrick utility, that still doesn't see the KF. No adb shell commands ever let me even see that it is seen somehow my my computer.
So now I am stuck. It still seems to me to be a driver issue, but I seriously cannot see how that is possible. I guess while waiting for a response from one of the guru's here, I will repeat my process of backing all of the previous drivers out and reinstalling them. There is NO other software on the kindle except for the Nova launcher and whatever the Bin4ry and Qemu methods install on it.
Sorry for the long post, but I figured it would be better than leaving you guys to ask more questions, though I'm sure you will anyways.
Thanks for any help, sorry to be that guy!
Jordan
See, I already remembered something, mine is running 7.2.3 when it was unpackaged, and all of this has been done with the factory cable.
Probably have better luck on the HD thread
Sent from my GT-N7000000000 using Tapastalker 2
I dont know if it's possible but since you can install an apk via adb
Code:
adb install launcher.apk
maybe you can
Code:
adb uninstall launcher.apk1
my guess is when you changed the file extention it cause the problem it doesn't recognize the apk1 extention thus causing a corruption. The second gen devices are very unstable when trying to modify one false step results in a permanent brick. Shift+right click inside the folder where you extracted quem root tool select open command window here try the uninstall code if that doesn`t work run bin4ry to open the shell and try again.
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."