I had been rooted, with TWRP recovery, and CM7, and Gapps. Wanted to go back to stock.
Brought up Kindle fire utility, downloaded stock update, transferred to fire via usb, used TWRP to flash stock update. Vola, back to stock kindle fire. Re-rooted with Kindle fire utility, and then my mistake, I flashed the CM7 Gapps into stock kindle. Got stuck on 'touch me android screen'. Went back into recover, wiped all, deleted all, and rebooted.
Now i'm stuck in the opening Kindle fire screen. I still have TWRP recover working, but ADB won't connect either in start up screen or recovery. Does your computer recognize that its connected when you turn it on? If it is showing the usual exclamation point next to the driver then you'll need to take the steps again to re-install the Google USB Driver. I know its a pain, but it works.
Download our Official Android App. (got close) until now. This kindle fire i believe is truly hard bricked. What happened was, I rooted it with the kindle fire utility, and when it rebooted it was stuck on the kindle fire logo screen. So i downloaded kindle unbrick utility to attempt to fix this and then it was in a bootloop. May 19, 2015 - This is what happened, I had a bricked kindle so i decided to fix it. While i was in the prcess of using kindle fire utilities v0.9.9. Suddenly while.
Then after that, make sure to open KFU just to make sure after reinstalling that the status shows that its rooted/adb rooted. After that open Command Prompt, cd to your adb spot. It should be somewhere like C: Program Files (x86) Android android-sdk platform-tools.
That's if your using Windows 7/Vista. If your running something like Ubuntu or Linux then I'm sure someone here is too and would post the file directory to it. After you open and get to the correct location in the file then copy the file line and go back into Command Prompt and do this: 1.
Cd C: Program Files (x86) Android android-sdk platform-tools 2.adb devices (just to make sure that your Kindle is really connected after redoing the drivers and that KFU wasn't screwing with you lol). If it shows something like 15DC01 then your good to go on to the next step. Type in adb shell 4. Once the adb shell gets connected then type in idme bootmode 4000. Then type reboot. After each of the command prompt lines that I have posted make sure that you push enter after each one. If you get stuck with an error somewhere in that process then comeback here and list what happened.
If it worked then your welcome ahead of time. Have a new kindle fire, tried to root and was successful then installed TWRP. Went to restore to factory defaults in Kindle launcher and somehow ERASED EVERYTHING!now when i boot up my kindle it goes to the TWRP screen and thats it.everything i try to do it either says cannot find device or something about 'exec '/system/bin/sh' failed: No such file or directory'.tried using kindleunbirckutility and now it just loads to the kindle fire screen. I can still get to TWRP by pressing power button til it turns orange.Really just want to restore it back to factory default.is this even possible?also forgot to back up in TWRP before doing all this.tried to find someone online that might could send me backup file they have, wasnt sure it that would work either?thanks for anykind of help from you guys. Have a new kindle fire, tried to root and was successful then installed TWRP. Went to restore to factory defaults in Kindle launcher and somehow ERASED EVERYTHING!now when i boot up my kindle it goes to the TWRP screen and thats it.everything i try to do it either says cannot find device or something about 'exec '/system/bin/sh' failed: No such file or directory'.tried using kindleunbirckutility and now it just loads to the kindle fire screen.
I can still get to TWRP by pressing power button til it turns orange.Really just want to restore it back to factory default.is this even possible?also forgot to back up in TWRP before doing all this.tried to find someone online that might could send me backup file they have, wasnt sure it that would work either?thanks for anykind of help from you guys. Click to expand.Ok, to start things off, you can't grab a stock backup file from anyone as it is their own personal device's programming and coding and info. So, if you do try it on your's you're more than like to ruin your kindle for good. The best thing to do is go into TWRP wipe everything and then do a System Restore. It'll put you back to factory settings, then go in and download the Google apps that I'm in the process as we speak to make it easy access for everyone knew to the Kindle Fire rooting scene and download them with the step-by-step instructions that I'll be posting in along with the link to download them. Hello Thank you to have accepted me like member.
I write from Italy My Kindle Fire it's stopped in the beginning on the logo after I istalling CM7. Now it's dead when I swith on it stopped on the logo and by KindleFireUtilityv0.9.3 and KindleUnbrickUtilityV1.1 the answer on every command is exec 'system/bin/sh' failed no such file or directory (2) The problem is thant the kindle cannot go to recovery and every command in adb have the same answer exec 'system/bin/sh' failed no such file or directory (2) Can you help me? My KF is bricked.
I was rooted using the KFU 0.9.6 and installed TWRP, Clockwork, Superuser, FireFireFire. I was in recovery tried to run an ICS.zip update. I did a backup, wipe cache, installed the zip update, wiped cache, rebooted, now the KF is stuck in a boot loop. ADB does not see the device neither does device manager.
I think I messed up applying the ICS update. I did not completely wipe the device, wipe the cache, then apply the ICS update. Kindle (white letters) fire (blue) and at the bottom says 'booting.' I can shut off and turn it back on but it goes back to the hung screen. It does let me select between Normal Boot, Recovery, and Reset Boot Mode.
None of the options do anything. Click to expand.Did this happen after the 6.3.1 update unrooted you or are you trying to root for the first time?
I have 2 KF that are rooted. When the 6.3.1 update came out, one got stuck at the boot screen and the other would still work. I ended up unrooting the one and going back to stock using guide. I then redownloaded KFU and reinstalled the drivers and it worked perfectly. This may have been the long way around but it worked for me. I was also using KFU 0.9.5 so you might give that one a shot as it should still be available in the KFU thread on XDA.
I also installed a CM9 rom on both devices so that I don't have to worry about OTAs anymore. Thx for your reply. This happened after the update unrooted me. I followed your suggestion and downloaded KFU 0.9.5 and in uninstalled and reinstalled the drivers. My computer recognizes the KF. Whenever I plug the KF to my usb (tried different slots) the computer beeps and recognizes the KF. I used KFU 0.9.5 and the ADB status: ONLINE.
However the boot status is UNKNOWN. I've made several attempts in bootmode activating all modes and I recieve THE SYSTEM CANNOT FIND THE DRIVE SPECIFIED 2460 KB/s exec 'system/bin/sh' failed no such file or directory (2). The kindle has been told to reboot. So, KFU 0.9.5 reboots the KF but thats the extent of where I'm at.
I'm still stuck at kindle fire logo. Thx for your reply. This happened after the update unrooted me.
I followed your suggestion and downloaded KFU 0.9.5 and in uninstalled and reinstalled the drivers. My computer recognizes the KF. Whenever I plug the KF to my usb (tried different slots) the computer beeps and recognizes the KF. I used KFU 0.9.5 and the ADB status: ONLINE.
However the boot status is UNKNOWN. I've made several attempts in bootmode activating all modes and I recieve THE SYSTEM CANNOT FIND THE DRIVE SPECIFIED 2460 KB/s exec 'system/bin/sh' failed no such file or directory (2). The kindle has been told to reboot. So, KFU 0.9.5 reboots the KF but thats the extent of where I'm at.
I'm still stuck at kindle fire logo. I'm pretty much stuck in the same boat. I had some issues and was able to get it back to a stock Amazon image. Then I tried the Kindle Fire Utility, and just attempting to do the option to grant root, it rebooted and now I'm stuck at the Kindle Fire logo. It doesn't have TWRP and no way that I know of to install it.
My PC will only recognize it as an unknown USB device. I've tried every driver trick I know of, and got limited success in adding a line in the winusb ini file to recognize 'usb unknown' as a Kindle Fire, but it won't fully initialize the driver. I dual boot with Win7 and Ubuntu 12.04, so tried the FireKit deal with the shorting trick, and it didn't make a difference. It would be stuck at the OMAP44xx or just waiting for device. I can't get ADB to see it under Win7 anymore either.
Ive rooted a few phones and tablets before and have never bricked a device (got close) until now. This kindle fire i believe is truly hard bricked. What happened was, I rooted it with the kindle fire utility, and when it rebooted it was stuck on the kindle fire logo screen.
I let it run flat over night, and the next day it was still stuck. So i downloaded kindle unbrick utility to attempt to fix this and then it was in a bootloop and it is now in a hard brick state. Power button is non responsive, unless charging, it will turn green then immediately to orange and stay that way. I like to think that nothing is unrecoverable, and im very determined to get this thing back up and running, even if it means taking the case off and flashing it with probes lol.
Ive been working on it for about a week now and I seem to have made things worse. So I'm hoping there's a genius out there that can help me bring life back into this thing. Lol it happens. Everyone makes mistakes. Just like people have told me, read read, and read some more.
Even when I think I know how to do something i'll look it up and read it from someone else. Dont tell Amazon what you did! If you tell them 'yea i was trying to root my kindle' they'll just laugh and say enjoy your paperweight.
Im not sure how you would go about getting it replaced because if they look at it first and determine it was because you bricked it, i dont think they would replace it? I just woke up and im confusing myself haha.