Develop Bugs

[Q] HELP! Bricked Kindle Fire

I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym

caseym said:
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
Click to expand...
Click to collapse
I'm having exactly the same issue on my Kindle Fire. I just recently got it from a friend; it seemed to be bricked, but the friend stated that he had never tried modifying the stock OS. I was able to use KFU to install the most up-to-date version of TWRP, but not FFF; I wanted to get it to stock before doing any additional hacking. That version of TWRP booted without any issues.
As OP mentioned, the most up-to-date version of TWRP has issues with installing the current version of the Amazon software. So, I tried downloading a copy of TWRP 2.2.2.1 (attached) and used KFU to install it, by extracting recovery.img, renaming it to twrp.img, and dropping it in KFU's /recovery/ folder.
Since then, I've seen the same symptoms as OP. The Fire boots to the Kindle Fire bootscreen, with no animation. It's not detected at all by any computer I attach it to. Windows doesn't chime or show it in Device Manager and KFU and adb don't see it. I also tried setting up FireKit, but none of the tools in that package are able to see it.
I'm going to test to see if this persists after depleting the battery for a while. I do not have a fastboot cable to test with, but I'm open to opening the case if you guys think that'll help get it back up and running.

Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.

haikuginger said:
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
Click to expand...
Click to collapse
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym

caseym said:
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
Click to expand...
Click to collapse
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.

haikuginger said:
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
Click to expand...
Click to collapse
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym

caseym said:
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
Click to expand...
Click to collapse
I'm afraid I've got nothing for you at this point. Hopefully someone more knowledgeable than I can sound off.

[Q] need help with boot loop

Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??

according to FAQ 16 Frequently Asked Questions - Amazon Kindle Fire
If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse
yes you need a fastboot cable
or
there is a [UTILITY] Kindle Fire Unbrick Utility V1.1! that you can try

kfs325 said:
Please forgive my noob-ness. I've done some research but i can't figure out whats up with this device.
I have a Kindle Fire first gen that is stuck in a boot loop. I get the boot logo with "Kindle Fire" and a flicker effect but that is it. This is NOT my device i'm trying to fix it for a non-technical family member. I know they didn't try to root it or any of that. It just stopped working for them one day.
after installing / removing / reinstalling the drivers a million times i finally got the kindle fire utility to see the device as online. its seems like no matter what i do the device goes back to the boot loop and KFU gives me "waiting for device'. anyone have any ideas? do i need the factor cable to get this working again??
Click to expand...
Click to collapse
Not sure of the state of your Kindle Fire G1 (It's not rooted? Are you sure?), but this sounds similar to what I ran into trying to install CM11.
What version of TWRP do you have installed? If it's 2.2.2.1 and you're trying to install a ROM with KitKat (CM11) you can run into this. I did. When I installed TWRP 2.7.0.1 I could install CM11 just fine without the boot loop.
To install TWRP 2.7.0.1 I found that you could only do so by:
When you turn Kindle Fire on, hold down the power button to cycle through the options when you see the Kindle Fire logo. You want to land on the Recovery option.
Mount storage from TWRP 2.2.2.1 on a PC and copy CM10.x.x and related GApps to SDCARD
Factory reset then reinstall CM10.x.x (with Gapps for that version)
Install Flashify from the PlayStore
Download the latest TWRP for otter/Kindle Fire G1 (2.7.0.1)
Install it with Flashify
Download CM11 and related ZIPs (GApps kk, Change to Nexus 7, etc) to Downloads directory
Restart into TWRP recovery (should be 2.7.0.1 now), and factory reset/reinstall CM11 and related ZIPs from Downloads directory
Should be fine now.
I found that I could only do it this way because for some reason Kindle Fire Utility Kit and ADB couldn't work with my Kindle anymore with TWRP 2.2.2.1 (don't ask, I don't know why). This way works. Just make sure you have a copy of a version of a ROM and GApps on SDCARD at all times since mounting storage might not work anymore in TWRP (again, I'm not sure why). I tried it again and again, but I couldn't get it to work and it might be the same for you. Keep in mind this is for CM11. If you're using stock, then follow sd_shadow's advice.

[Q] Am I bricked now? -no boot-no recoveryTWRP

I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.

KoBRaQ said:
I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.
Click to expand...
Click to collapse
Did a little more research.Guess I should try a fastboot cable maybe?

connected for a split sec is all KFU needs to send reboot to fastboot mode command.
Did you try rebooting kindle few time while running KFU?

I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.

clifford25501 said:
I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.
Click to expand...
Click to collapse
which windows version 7, 8...?

I try on win xp and win7. First it was detected as OMAP4320 but after driver installing its detects only as TI BOARD. This happaeds after installing otter x bootloader and tpwr 2.7.0.0. I live it for a night because i couldnt install driver for otterx fastboot. When i check device on the morning it was in this state and do not power on.

screen stuck at black screen with amazon logo

hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.

azheng said:
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
Click to expand...
Click to collapse
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.

KLit75 said:
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
Click to expand...
Click to collapse
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?

azheng said:
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
Click to expand...
Click to collapse
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck

KLit75 said:
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
Click to expand...
Click to collapse
thanks for the help, i think recovery went bye bye along with the OS lol

Hi,
any update on this thread? I've been stuck also. I had safestrap. I supposed to flash a cleamsystempartion but I accidentally restart it without flashing new rom and now i am stuck in Fire Phone Logo. I still can access the stock recovery tho. Please help :crying::crying::crying:

try to flash your phone back to stock rom

any solution to this problem? I am stuck with same problem.

siddharth_bhal said:
any solution to this problem? I am stuck with same problem.
Click to expand...
Click to collapse
same problem here: can't start safe stripe and stuck at Amazon. tried to start the phone pressing volume up and power button, see if you can get into the build-in recovery. if it works, you can wipe the data and then use ADB sideload to flash in official rom (should be a bin file, i tried 4.6.1 version) and bring back your phone .

fire phone keep rebooting
my fire phone is keep rebooting with amazon logo up to 5 minutes and suddenly turned of i want to know the problem and how to fix it so please help me.

Have any of you guys tried the instructions in this thread: https://forum.xda-developers.com/fire-phone/general/reverting-fire-phone-to-stock-t3288890
I have bricked Fire phone quite a few times and everytime I followed his instructions and the lifehacker instructions that he linked to install adb and ADB sideloaded 4.6.6.1. without any problems.

My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently

Bahdtyga said:
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Click to expand...
Click to collapse
U need a new fire phone, talk with amazon from your country or region or the seller from where you got fire phone!

Help! Amazon Tate no OS or Recovery!

Hey, so I have two Kindle fire hd 7's and a couple years back I rooted both of them and hadn't used them in a few months. About a year ago I needed to use them because my primary device is not rooted. So I took them out and instantly got tons of Google error messages because they had not been updated in about 2 years so I went on my computer to reset and get the newest version of cm and somehow I ended up deleting twrp and cm 12 and now it will turn on but it's just the Kindle fire logo, so that's what happened to the first one. With the second one I tried to update cm and twrp. And it worked but then I think I tried to reboot to recovery from twrp and now my Kindle is stick in a twrp bootloop. I want o save these devices if possible. Is there a way to get twrp and cm back on the first one even though it's not recognized by my computer, or should I just toss it? And with the second one it is recognized by my computer I can also get it to fastboot mode. Is there anyway I can uninstall then reinstall twrp without the bootloop happening again? Any help is appreciated. Thanks