[Q] Kindle Firmware Corrupted? (Bricked...) - Kindle Fire Q&A, Help & Troubleshooting

Hi,
So I have Kindle Fire (1st gen) that used to be my brothers and it was locked or something so he installed 'TWRP' and 'FFF' but for some reason it wouldn't boot. It would turn on Ask for 'Normal boot, Recovery, Reset Boot Mode'. Only recovery worked, the rest got stuck on 'Kindle Fire. I Tried factory reset, erase all cache but nothing worked and at the time my computer didn't recognize it.
Eventual I managed to get it to work on 'Kindle Fire Utility' and re-installed 'TWRP' AND 'FFF'. On my kindle it said that I didn't have an OS. So I downloaded one and installed it with 'COTR' due to connection problems with 'TWRP'. During the installation it said 'signature verification failed' but I installed it anyway. Now when I boot there isn't any 'Normal boot, Recovery, Reset Boot Mode'. It starts up and says 'Kindle Fire then the screen gets brighter and after a sec it goes even lower than the first and just stays there.
Now it isn't recognized on the computer, I tried re-installing the drivers but it say it is already up to date.
I also followed a tutorial on youtube made by Skeelo764 and it is called "Fix Kindle Fire stuck in Recover TWRP and PC not finding"
But when I type 'adb shell'
it says this: exec '/system/bin/sh' failed: No such file or directory (2)
Any help is appreciated =)

Related

Kindle Fire is stuck on Kindle Fire Logo Screen

Alright so I used KFU to root my kindle to android market then I used TWRP to install CyanogenMod 7. Everything was fine tell I wanted to restore to stock. I downloaded the Kindle Fire 6.3 installed it then my kindle rebooted. After this happened, everytime it comes on dimly lit then goes to the brightest setting then goes back to dim brightness all while remaining on the standard kindle fire load screen. The letter animation stops shortly after it goes back to dim brightness. On my computer it no longer shows up under my computer but in device manager it is called a Amazon kindle under disk drives with 0 mb of space. On KFU I can get it to show up ADB online but status is Unkown. After I try to change boot mode (normal, fastboot, and recovery) or try and install any of it the kindle turns out comes back on for 4 to 6 seconds then shuts off comes back on and freezes. Also before changing boot mode any one I click it says is no longer on the device. I have also tryed KF unbrick with no help ether.
Does anyone know how to fix this pleas and think you.
mellowboombox said:
Alright so I used KFU to root my kindle to android market then I used TWRP to install CyanogenMod 7. Everything was fine tell I wanted to restore to stock. I downloaded the Kindle Fire 6.3 installed it then my kindle rebooted. After this happened, everytime it comes on dimly lit then goes to the brightest setting then goes back to dim brightness all while remaining on the standard kindle fire load screen. The letter animation stops shortly after it goes back to dim brightness. On my computer it no longer shows up under my computer but in device manager it is called a Amazon kindle under disk drives with 0 mb of space. On KFU I can get it to show up ADB online but status is Unkown. After I try to change boot mode (normal, fastboot, and recovery) or try and install any of it the kindle turns out comes back on for 4 to 6 seconds then shuts off comes back on and freezes. Also before changing boot mode any one I click it says is no longer on the device. I have also tryed KF unbrick with no help ether.
Does anyone know how to fix this pleas and think you.
Click to expand...
Click to collapse
One of two things has probably happened here. Either you did not use the factory reset to delete the /data partition prior to flashing the stock software or the system software is damaged or missing from the /system partition. If at all possible, you will have to try to put your KF into fastboot mode using adb. Unfortunately, the odds are against you and my guess is any "adb shell" command will fail. Temporary fastboot through the bootloader is also a non-starter because you have the stock bootloader installed. That leaves the factory cable or opening the back cover as your last two options. The details are spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
I suggest you get the factory cable, reflash TWRP, and try a factory reset. If that doesn't work, wipe the system partition as well, unmount all partitions and try flashing the stock software again.

[Q] Root Problem Can't Recover

Hi,
Believe me I have searched, read and tried most of the other posts relating to this problem but can't find anything that has been successful in solving my issue so I'm hoping someone can point me in the right direction:
I succesfully rooted my Kindle Fire and installed Jelly Bean, all working no errors. I could boot into TWRP (blue Kindle Logo instead of Orange with boot options at the bottom) and had actually tried a couple of different versions, it all worked well. Then I decided to reinstall the Kindle 6.3.1 again but I did something wrong in TWRP - not sure what the procedure should have been but I didn't Wipe Cache or erase when I should have done.
So now the Kindle boots to 6.3.1 with the Orange logo again (so it seems unrooted now) and when I get to the main screen I have 2 force close messages 'The Application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again'.And the same for process Acore. I can only hit force close and then the kindle shows the orange logo and I can swipe to log in and the same process happens and repeats.
I can connect to the KF with the cable the device shows in Device Manager as Android Composite ADB Interface and I can see various folders on the KF.
So I've tried re-rooting but can't get anywhere. The KF utility runs and says ADB status online Boot status:4000. If I run 3 to install (or reinstall) TWRP Recovery I get the activating Fastboot message and then
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
Unable to chmod /data/local/fbmode: No such file or directory
/data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
It goes no further.
I've tried a variety of different fixes from posts in this forum but nothing has been successful. If someone knows of a post where someone has succesfully solved a similar issue please point me to it, or if anyone can help or suggest howIi can get the KF either back to 6.3.1 or TWRP back or actually anything other than what I've got at present I'd be grateful.
I seem to have communication with the device so cable is working, device is working (sort of) so I can't beleive it's the end of the line for it.
Thanks in advance
Hi,
For the benefit of anyone else having this problem I solved it. I did a factory reset from within the device section of More+. You have to be quick and it may take an hour or so of clearing the Force Close messages and then trying to get to More - Device - Factory Reset as quick as you can before the loop goes round again, but I stuck with it and suddenly the thing rebooted and I was back in TWRP!!
Subsequently followed the correct procedure to return the KF to it's original state:
1.Connect USB cable to Kindle Fire.
2.Mount it as USB Mass Storage mode.
3.At PC, rename Kindle Fire Software Update bin file to update.zip.
4.Copy update.zip to Kindle Fire SDcard (root level).
5.Turn off USB Mass Storage mode.
6.Unplug USB cable.
7.Power off Kindle Fire.
8.Power on it.
9.Press power button until light turn orange.
10.TWRP 2.0 Recovery will be loaded then.
11.Select Wipe.
12.Select Cache then Wipe cache.
13.Select Dalvik Cache then Wipe dalvik-cache.
14.Select Factory Reset then Factory Reset.
15.Go back to Home.
16.Select Install this time.
17.Then select update.zip.
18.Select Flash after that.
19.After installed, select Reboot System.
20.That’s all.
I did enjoy the Android experience on the KF but really only want to use it as a browser and battery life was far worse on with Jelly Bean. Anyway I can always root it again sometime.

Kindle fire Bricked

I rooted my Kindle Fire HD 8.9 using Binary's rooting tool.
I went into the application named ROM-Toolbox, changed the font. It told me a reboot is required for the font to take effect.
I've used this application before and it worked fine. I rebooted and change my font. However the second time i got this.
It booted into an unusual screen."Kindle Fire system recovery. Your kindle does not seem to be bale to boot. Resetting your device to factory default may help you fix this issue. Volume up/down move to highlight; power button to select."
There are two more options. Reboot your kindle, or reset to factory default.
When i select either, i get a bootscreen loop. In which it booted the same two options.
When connected to a PC, the PC did not recognize the device in any shape or form. I've reinstalled the drivers.
When rebooting the Kindle, for a second the PC emits the sound that indicates that a device has been connected. In the system tray of my PC, it says "installing android adb interface" then it resumes to say device unplugged.
Please, much help is appreciated.

[Q] Bricked Kindle, bad. Please help me! Please! :(

Okay so I had TWRP and I was going to flash a different Rom. However I accidentally while not looking managed to wipe EVERYTHING, including my old Kindle OS (I reformatted it back to stock OS for some reason before I was going to flash another rom). I deleted everything, system, SD data, cache and delvec. Factory reset and whatever else was there, I didn't think it would do anything, there were no warnings. Now I believe my kindle is completely bricked for good and it makes me wanna cry
So far when I turn it on, it shows the original Kindle Fire screen and flashes to black quickly like it's rerunning the animation every 15 or so seconds. I'm afraid to keep it on and continue anything due to the battery last I saw was 30 person and the charging is already messing up on it.
If I could get it to connect to my computer I could reinstall TWRP and manae to flash it to whatever I want but when connecting it doesn't pick up and TWRP won't reconize it either. I've tried to use JDK or whatever it's called to ADB or something (you computer people get me!) and it gives me the error - exec '/system/bin/sh' failed. No such file or directory.
I'm not sure what I'm doing either, I've been watching a video on youtube and cannot get any farther in it due to this error.
Please, someone help me I'll worship you, I am completely lonesome without my Kindle
exec '/system/bin/sh' failed. No such file or directory
If you have FireFireFire installed (blue & white Kindle Fire logo) that error is not much of a problem. If it is not installed, however, you will need a factory cable.
Try to run Kindle Fire Utility 0.99 first and wait for KF reboot
ADB is also nightmare for me since my PC recently never recognizes my Fire in adb mode (always failed with KF tool .096 and 0.99). Therefore my TWRP version was stacked with 2.2.2.6 version for a long time, and the method to update it through the soft in Google Play store was also failed. However, I accidently find a good way to update TWRP to 2.6 versions by run KF tool and select Install TWRP. Then with the KF still connect to PC, I restart it and it take a seconds to install latest TWRP while my Fire still in boot status (blue Kindle Fire logo)
lifegap said:
ADB is also nightmare for me since my PC recently never recognizes my Fire in adb mode (always failed with KF tool .096 and 0.99). Therefore my TWRP version was stacked with 2.2.2.6 version for a long time, and the method to update it through the soft in Google Play store was also failed. However, I accidently find a good way to update TWRP to 2.6 versions by run KF tool and select Install TWRP. Then with the KF still connect to PC, I restart it and it take a seconds to install latest TWRP while my Fire still in boot status (blue Kindle Fire logo)
Click to expand...
Click to collapse
Okay! I ordered a cable off ebay and it just got here today, please tell me what to do I feel like you guys can help me unbrick it.

kindle fire gen 1 stuck in boot loop(?) after changing to ART from dalvik

I recently rooted and installed a custom rom on my 2011 (gen1) kindle fire.
I followed directions (https://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) to root.
Then I installed twrp latest version (older version did not accept my rom) https://twrp.me/amazon/amazonkindlefire.html
Then I installed the Infriction speed rom https://forum.xda-developers.com/showthread.php?t=2580232
I installed some apps... about 134 MB left in app install partition.
In developer settings I enabled ART, thinking, maybe this will make it faster...
Then it rebooted.
It was then stuck at a screen (not the android logo w/ words "kindle fire", but the bubbles screen of the os).
I decided, maybe I can fix with my pc.
Unplugged it - it then immediately shut off (loss of power??).
Then tried to use kindle unbrick utility, the various commands.
Now it is out of battery, but when I plug into PC or wall, it's in a boot loop, where it shows about 3 sec of the boot logo (android robot and words) and shuts off, before doing that again.
It is now undetectable by Kindle Fire Utility (just says "waiting" while the kfire reboots over and over), fastboot probably cannot detect either... (?) (worked one time but it just shut off again... and now doesn't work??), and can't boot into recovery.
Help.:crying:
So I'm assuming the partition ran out of storage?? but then what happened...
So I had a little luck trying to reset: ht tp s:// it stillworks.com/fix-kindle-fire-boot-loop-30462 .h tml
Then I got to the OS booting screen.
EDIT:
well that worked once... I tried to do adb reboot recovery after it got to OS boot screen (bubbles).
adb tells me:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Then it just fell into boot loop again. ?
So then I plug in, try again, it's just the boot loop. I'm going to try again after 30 min, but maybe need to do something different.
Cause of boot loop found
So it turns out it was just out of battery... I let it charge, did the reset thing, then was able to reboot into recovery.
\^o^/

Categories

Resources