So i rooted my kindlefire previously and i believe that it was a success. But after messing with certain programs i believe i moved an incorrect folder to a wrong location causing my fire to (at the time what i thought) brick. My kindle after sitting on my desk for 6 months thinking it was bricked i touched the button and it turned on a booted up. First thing i did was Restore factory settings. Is my kindle still rooted even after factory setting restore? When i download the Fire kindle utility and run the superuser.apk it runs and says i dont have the lastest TWRP installed and it will manually install it for me. It goes through the running process and then it tells me Opps. Error while trying to run. Error found in recovery twrp. How do i go about getting past this error?
Keith
That's a kfu issue that need to be fixed hang tight till its confirmed resolved
At some point i had my kindle fire rooted with a jelly bean rom, with twrp recovery installed. I wanted to get rid of my fire, so i decided it was time to go back to the stock rom. In my infinite wisdom, I ended up wiping my factory backup by mistake. I went onto the kindle update site and downloaded the latest official version 6.3 bin file. I then renamed the .bin to .zip and updated it through twrp. When my kindle restarted, the factory OS came up, except I started getting android.acore errors along with another calendar process error. If that wasn't bad enough, it now randomly reboots whenever it feels like it. Luckily I can still usb mount it to my pc and can copy files back and forth. I tried using the kindle fire utility to root it again and install twrp, but no luck. Any ideas? Thanks in advance.
Factory reset it.
I was recently trying to get my kindle back to stock from cm10. I have a decent amount of experience with it all, but I wouldn't say that I'm an advanced user. What I did wrong was install the stock zip from twrp without wiping the system first, face-palm. It flashed just fine in recovery, and boots the stock os all the way up, however immediately after it loads I get errors for several processes and apps stopping unexpectedly. I can force close the error and do a bit before the next one comes up but after a bunch it just instantly reboots. I can get the factory restore in the settings just barely started but it reboots before I can do anything. Since I couldn't get that I went back to the KFU to try to get twrp and fff back on, but have not been successful. It detects the kindle as online in normal boot mode. I have an android adb device showing up in device manager, and I have uninstalled the drivers and reinstalled them several times. KFU won't let me get the kindle into fastboot and when I tried to install twrp it utterly failed saying it couldn't find a bunch of directories that it needed. I have come back from some pretty bad bricks before, but this one has me vexed. Any help would be appreciated.
Try installing twrp and firefirefire manually
Sent from my Amazon Kindle Fire using xda app-developers app
Okay, I was able to get twrp and fff installed using soupkit, but now it errors out when I try to install the update .zip file. I always used twrp below version 2.5 but now that is what I have. Any ideas?
Try flashing modded stock http://forum.xda-developers.com/showthread.php?t=2211872
Sent from my Amazon Kindle Fire using xda app-developers app
Went on a gut feeling and installed the older version of twrp that I always used and the update.zip instantly installed. Thanks for the suggestion of doing a manual install, I probably wouldn't have found soupkit and Linux definitely saved the day. Now I can sell it without guilt, so this is farewell. I haven't posted much but this community has been extremely helpful and allowed me to have loads of enjoyment from my Kindle so thank you much.
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Hmm, off flashing from fastboot should typically work, since you were attempting to flash cm 10.2 I have to ask something because I am slightly uncertain of this myself, but did you ever get twrp running at one point before all this happened, and second if so did you ever wipe any of the partitions or try to flash the ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Unfortunately no. I was never able to get into TWRP as the blue logo has never appeared. Directly after my first attempt at this I rebooted and got the red screen or wall of fire. I "fixed" that by reflashing stock boot, bootloader, recovery, and system image partitions to 8.1.4. Yet instead of a working device I now have either a boot loop or a fixed orange logo. I have gotten the device into stock recovery once (haven't been able to reproduce this result) but it shutdown while the process was underway(About half way??). I have also gotten the device to boot into a animated logo that then proceeded to a data corruption screen, but before I could even read the entire message the device shut off and began another set of boot loops. It looked like a amazon stock os prompt screen. Before this even began I had a normal Kindle fire that I had rooted. I forget what software version it was on before all of this unfortunately.
Sounds like the system image is slightly corrupted or something if the os had that kind of error about data corruption but you said the md5's march so that is weird. You try reflashing the boot partition again since reflashing system didn't work? This is frustrating, mainly because with out adb access from a decent recovery I have no Linux commands to work with, if worst comes to worst I think there's a way to reform at the system partition from fastboot but I wouldn't go for that just yet, I don't know the command offhand but if you did the wrong one I think there's a way it would clear all data on all partitions which would be very very bad. I'll ask hashcode what he thinks cause this is weird.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I have tried flashing all partitions before. Will try again soon. Also, I have another piece of information as well even if it isn't relevant. I originally bricked my Kindle at first, flashed the wrong bootloader. So I bought a for-parts Kindle (Same model) that had a busted screen and took out its motherboard and placed it into my device. Then I rooted the stock os on the new MB and the rest of the story is already in this thread. It still charges and fastboots but nothing other than a static orange boot screen so far. Thank you for helping me out on this; really hope that this can be fixed.
Thinkwithportals said:
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Click to expand...
Click to collapse
"I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick."
I have the same problem but when I try fastboot mode the computer wont even find the device
Alrighty, well. I woke up this morning and decided to re download all of the system, boot, and recovery image files. I flashed them to the device and it again boot-looped for about an hour. I set it up next to me and started reading through the forums for repair via soldering eMMC to SD card reader. I look down and what is starting back at me? A fully working Kindle waiting in initial setup for input... Yet within about a minute it is back into the old boot looping game again. Hardware problem? A short maybe???
possibly or maybe it has a bad emmc chip.
Sent from my LG-P769 using xda app-developers app
Hm, well I think I might just give up on this MB then. I am considering looking into my hard-bricked motherboard and using Kurohyou's pin-out. Even if my soldering skills are a bit rusty.
Thank you anyway for your help. I will report my progress in the other thread from here on out.
Careful not to melt the contact pads, I just ruined one of my Xbox 360 controllers today unsoldering a trigger, cheap parts.... Long story short controller falls in dogs water bowl, circuit board goes in rice, rice gets stuck under a trigger, I ruin controller unsoldering trigger... Least I have 4 more. But anyways yea careful, I suggest at least an st7 tip and not to let it get to hot, read someone else managed to melt a contact on a kf2 I think it was.
Sent from my Amazon Kindle Fire HD using Tapatalk
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.