I've looked around the forums and I am not finding instructions on how to unbrick a Kindle Fire that has ClockworkMod installed. I installed ClockworkMod and installed a late ICS build with kernel 3.0 and the Fire is stuck in an infinite boot loop with the Kindle Fire/Android mascot logo.
I can get into ClockworkMod but re-flashing with the CM9 that I have doesn't do anything to fix it.
I know that if I were able to put the stock Kindle firmware on that /sdcard volume I can fix this but how do I do this with ClockworkMod?
I've tried all the unbricking utils (even the Java front-end) and they act like they're fixing things but they all make no changes.
I do have the correct drivers and can send adb commands to fastboot, normal boot, recovery boot, so I'm pretty sure I'm just missing how to unbrick a Kindle that is using ClockworkMod.
Thanks in advance.
aegrotatio said:
I've looked around the forums and I am not finding instructions on how to unbrick a Kindle Fire that has ClockworkMod installed. I installed ClockworkMod and installed a late ICS build with kernel 3.0 and the Fire is stuck in an infinite boot loop with the Kindle Fire/Android mascot logo.
I can get into ClockworkMod but re-flashing with the CM9 that I have doesn't do anything to fix it.
I know that if I were able to put the stock Kindle firmware on that /sdcard volume I can fix this but how do I do this with ClockworkMod?
I've tried all the unbricking utils (even the Java front-end) and they act like they're fixing things but they all make no changes.
I do have the correct drivers and can send adb commands to fastboot, normal boot, recovery boot, so I'm pretty sure I'm just missing how to unbrick a Kindle that is using ClockworkMod.
Thanks in advance.
Click to expand...
Click to collapse
When you say "infinite bootloop" do you mean the device turns on, shows the boot logo, then reboots?
If so... http://forum.xda-developers.com/showthread.php?p=25400963
Also CWM will not work with the latest versions of ICS, you need to flash TWRP.
I recommend people copy both the Kindle standard image as well as the customized image to the /sdcard volume. That way if you're stuck with a bricked Kindle at least you can re-install the original Kindle image and get back to where you were before.
I ordered a factory cable to get it to boot into factory recovery mode, which I know works in all cases.
In the meantime I'm going to attempt to try the steps in that post.
After that I'll try to mount the original Kindle system image from a USB drive (using the USB boot feature of CWM) and then try to install it from there and then go back to TWRP or FireFireFire.
I've successfully used FireFireFire before, but using CWM bricked my Kindle hard. I'll update this thread when it's working again.
Thanks for the info.
Okay, I successfully unbricked it.
It wasn't so much a hard brick or a soft brick but more of a firm bricking.
I went into CWM and told it to mount the USB volume. The 5 gigabyte drive appeared on my computer and I formatted it.
I took the Amazon stock update and changed its file extension to zip.
I then copied it from the computer to the mounted volume.
I chose the zip for installation and then installed it from CWM.
After shutting down and rebooting a few times it worked.
I didn't even have to do any ADB tricks. This is because I had a working CWM boot image.
Now it's off to more hacking!!
I am having the same problem... how did you get into clockwork? it doesnt stay on long enough for me to connect it to the KFU
I did the same thing. You'll need to go into CWM and mount it as usb storage and then it will show up on your desktop as a disk drive. Format it from there to wipe out the crap that's hanging it up and then reinstall either your rom or stock amazon rom.
HaNNibalHector said:
I am having the same problem... how did you get into clockwork? it doesnt stay on long enough for me to connect it to the KFU
Click to expand...
Click to collapse
I am int he same boat. How did you or can I get into Clockwork
I'm not very knowledgeable about CWM but I do have an idea. Try turning off kindle by holding down power button, plug kindle in to computer and turn it on. Open KFU, if it says that adb is online, then you have your fix. Just set the boot mode to recovery and you should boot right in to cwm.
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1623244
luishawk said:
I tought it was a driver issue cause whenever i tell my kindle to reboot into fastboot I can give the commands to reboot into normal again, but I cant seem to see it using fastboot devices, there are somethings I need to check before doing the push fbmode cause I dont quite get it yet, actually my plan is to get it back to stock somehow and then start from there.
Click to expand...
Click to collapse
You are in fastboot mode.
The following will cover the fastboot commands you need...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
You will use those fastboot commands to install TWRP and then use TWRP to install FFF.
Follow the instructions on installing these components described here...
http://forum.xda-developers.com/showthread.php?t=1638452
You will use TWRP to revert back to the stock software.
kinfauns said:
You are in fastboot mode.
The following will cover the fastboot commands you need...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
You will use those fastboot commands to install TWRP and then use TWRP to install FFF.
Follow the instructions on installing these components described here...
http://forum.xda-developers.com/showthread.php?t=1638452
You will use TWRP to revert back to the stock software.
Click to expand...
Click to collapse
Ok, I've managed to install the drivers in the kf utility,
When i use this command "fastboot -i 0x1949 getvar product" I get the reply "kindle" so I assume my kindle is booting in fastboot mode as you said, so it must mean I'm still on the stock bootloader if I'm not wrong ,
So, I think what I should do is either flash a stock rom or flash a new bootloader and new recovery using both of this commands, correct?
fastboot -i 0x1949 flash bootloader c:\kfu\restore\u-boot.bin
fastboot -i 0x1949 flash recovery c:\kfu\restore\recovery.img
If i want to flash it back to stock should i should use:
fastboot -i 0x1949 flashall c:\kfu\restore\update-kindle-6.3.1_D01E_4107720.bin correct?
I ask cause I wanna be sure, dont wanna mess up even further, I must get now bootloaders and recoveries in .bin and .img extensions right?
I don't think that last one will work. I believe I tried it that way before and it didn't work.
You can flash the bootloader and recovery the way you have it there. Normally, I would suggest you get into recovery first and flash your bootloader there, but I think you said your /sdcard won't mount, so this will be preferable in your case.
While you are at it, flash TWRP 2.1.1 and FFF 1.4a. FFF 1.4a is distributed as a zip file. DO NOT FLASH THE ZIP FILE. I cannot stress that enough. Download the FFF zip file, check the md5 sum and make sure it matches what's on the OP. Then, you must unzip it and dig out the .bin file in there. I think it's in the cache folder if I remember correctly. Once you have both of those in place, you should be able to get your /sdcard partition fixed.... hopefully.
EDIT: I think I confused you with another guy... I think you should flash TWRP, boot into that and then flash FFF. Look at this page...
http://forum.xda-developers.com/showthread.php?t=1638452
Under the "Installing a recovery and custom bootloader" section are the exact commands in the order you need to do them. As it shows in the section, TWRP uses the zip file to flash the bootloader, you don't need to unzip it if you are going to do it that way.
kinfauns said:
I don't think that last one will work. I believe I tried it that way before and it didn't work.
You can flash the bootloader and recovery the way you have it there. Normally, I would suggest you get into recovery first and flash your bootloader there, but I think you said your /sdcard won't mount, so this will be preferable in your case.
While you are at it, flash TWRP 2.1.1 and FFF 1.4a. FFF 1.4a is distributed as a zip file. DO NOT FLASH THE ZIP FILE. I cannot stress that enough. Download the FFF zip file, check the md5 sum and make sure it matches what's on the OP. Then, you must unzip it and dig out the .bin file in there. I think it's in the cache folder if I remember correctly. Once you have both of those in place, you should be able to get your /sdcard partition fixed.... hopefully.
EDIT: I think I confused you with another guy... I think you should flash TWRP, boot into that and then flash FFF. Look at this page...
http://forum.xda-developers.com/showthread.php?t=1638452
Under the "Installing a recovery and custom bootloader" section are the exact commands in the order you need to do them. As it shows in the section, TWRP uses the zip file to flash the bootloader, you don't need to unzip it if you are going to do it that way.
Click to expand...
Click to collapse
Awesome!! brother you are full of win! it worked, I'm out of the boot logo loop, now I'm gonna flash the recovery
well, I've managed to messed up again, now its in some kinda of a twrp boot loop, everytime I reboot It goes back into twrp, I cant seem to go back into fastboot, I must investigate further.
luishawk said:
well, I've managed to messed up again, now its in some kinda of a twrp boot loop, everytime I reboot It goes back into twrp, I cant seem to go back into fastboot, I must investigate further.
Click to expand...
Click to collapse
If you installed TWRP 2.1.1 and you are using "Reboot -> System" to restart your device, the device should boot into the system. If it looks like it's booting properly, but it still comes back to recovery, something is wrong with your system software or more likely your storage partitions. This is often the case when some partitions are not available and the system software wants them fixed. It will boot into recovery, so it can be fixed, and the recovery restarts the device again in normal mode. However, you've replaced that stock recovery with TWRP and that's where it sits because TWRP isn't designed to automatically fix anything and it doesn't restart on its own.
Boot into TWRP, and get parted's partition table information...
Code:
adb shell parted /dev/block/mmcblk0 print
... and paste it here.
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
kinfauns said:
If you installed TWRP 2.1.1 and you are using "Reboot -> System" to restart your device, the device should boot into the system. If it looks like it's booting properly, but it still comes back to recovery, something is wrong with your system software or more likely your storage partitions. This is often the case when some partitions are not available and the system software wants them fixed. It will boot into recovery, so it can be fixed, and the recovery restarts the device again in normal mode. However, you've replaced that stock recovery with TWRP and that's where it sits because TWRP isn't designed to automatically fix anything and it doesn't restart on its own.
Boot into TWRP, and get parted's partition table information...
Code:
adb shell parted /dev/block/mmcblk0 print
... and paste it here.
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
Click to expand...
Click to collapse
Brother, my kindle is alive again! everythink works, thank you!
kinfauns said:
Alternatively, you can download the Kindle Fire software update from Amazon, change the suffix to .zip, extract the contents of the zip file, get the recovery.img out of it, flash it in fastboot, and restart. That might fix whatever problem is causing the reboots into recovery. Make sure you have the FFF bootloader installed before you do that so you can flash TWRP back again if that doesn't help.
Click to expand...
Click to collapse
This worked for me as well. Thanks!
My kindle only reboots by itself after it goes into sleep mode. if it is powered on, it does not reboot.
When in sleep mode, it reboots by itself and ends up in the TWRP screen.
bigric_tx said:
flash it in fastboot
Click to expand...
Click to collapse
Could someone please provide me with a step by step guide as to how to execute this part?
stanusj said:
My kindle only reboots by itself after it goes into sleep mode. if it is powered on, it does not reboot.
When in sleep mode, it reboots by itself and ends up in the TWRP screen.
Could someone please provide me with a step by step guide as to how to execute this part?
Click to expand...
Click to collapse
Guessing Kindle is trying to install update, but fails because you replaced stock recovery with TWRP.
Watch my [Video] Installing update-kindle-prerooted.6.3.3.v1.zip in TWRP
just download my update-kindle-prerooted.6.3.3.v1.zip and install in TWRP,
[2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
Yesterday was my first time rooting a Kindle Fire, and the root process went very smoothly when I followed this guide which uses saferoot: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
While I made use of this guide for flashing FFF and TWRP: http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
After successfully rooting it, I wanted to try the OtterX ROM/TWRP/Bootloader, since I read the comments and saw it would be good to try it out. After flashing the bootloader (otterx-u-boot_v2.05), the kindle kept rebooting showing the logo and the option to 'press power to enter boot menu'. I thought this was normal so I didn't mind it. (During this time, I could still enter recovery.) I proceeded to Step 2 which was flashing TWRP for OtterX (I downloaded zip-otterx-twrp-2.8.2.0-recovery.zip and installed it using the previous TWRP I flashed: openrecovery-twrp-2.2.2.1-blaze.img).
I wasn't able to remember what I did next, but I know I was already having issues. I was getting anxious and sleepy at the same time, I remember exploring the boot menu and foolishly/stupidly tried the EMMC Corruption Fix, without even trying to research about it beforehand, so now I'm stuck at the "fastboot mode" screen (I've attached a photo of the screen). Whenever I turn on the device, it shows the kindle fire logo and the option to enter boot menu. If I let it be for a while, it goes into the "fastboot mode" screen, the same thing happens when I try to choose "continue boot" or "recovery boot". Windows doesn't recognize it anymore whenever I try to connect it too (I'm using Windows 8.1 by the way.)
Please help, I've tried reading about how I could restore the kindle to the state it used to be after I rooted it, but no luck, I couldn't find anyone encountering the same problem as me since I think I'm the only one stupid enough to apply that EMMC corruption fix without knowing or reading what it actually does. Thanks in advance to anyone who could help.
Try
Download adb/fastboot files, if you have not yet.
Power off Kindle
In command prompt
Run command to flash recovery
Power on kindle
See [Video] Flashing TWRP in OtterX bootloader
THANK YOU SO MUCH for your reply. I tried it as soon as I woke up. I found out that the problem was the driver, I reinstalled it and flashed the recovery using the fastboot command.
Sent from my C5502 using XDA Free mobile app
Hi
given this is my first thread here, please redirect me, if my search-fu did not lead me to the correct post.
I'm trying to install a custom ROM on my 5T but after successful flashing it is simply displaying the boot animation of Lineage and nothing else happens and no connection with ADB is possible at that time. Steps I did (following this guide):
updated to stock OxygenOS (A5010_43_180223), reboot, ...
enable dev options
enable USB debugging, advanced reboot, OEM unlock
reboot into bootloader
fastboot oem unlock
enable dev options, USB debugging, advanced reboot, OEM unlock again
reboot into bootloader
fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.73-op5_op5t.img (also tried twrp-3.2.1-0-universal-codeworkx-dumpling.img and twrp-3.2.1-2-dumpling.img)
boot into recovery
swipe to allow system changes (no change detected when not doing this)
adb push lineage-15.1-20180402-microG-dumpling.zip /sdcard/ (also tried older images or standard lineage build)
install this via TWRP
when done, wipe cache/dalvik
reboot system
boot animation for a very, very long time (longest waiting time > 45 minutes)
Initially, I had magisk v16 also thrown into the mix, but to reduce complexity I don't at the moment.
Interestingly, once I'm at this stage and the boot fails (also not on second or third try after force-reboot), I cannot get stock (OnePlus5TOxygen_43_OTA_030_all_1802230142_ebdb8bfbc359405a.zip ) to boot anymore, it also is stuck in boot animation. The only way to get back to working stock ROM found so far is flashing original recovery and firmware (sideloading) and locking of boot loader again.
Does this sound familiar to anyone, as I'm running out of ideas what I did wrong and where.
Thanks a lot in advance for any pointers!