Related
I'm rooting a kindle, and some weird things happened while I was rooting it, problems with rooting on Windows 8, But now that I have TWRP and FIREFIREFIRE installed, it won't let me boot to system. It flashes on and off of the shiny kindle Fire screen, then boots to TWRP. KFU says it is in Boot STatus 0x5003. Any help?
Ichigo said:
You're in the recovery boot mode. Change it to normal boot mode using kfu.
a.k.a. Josepho1997
Merry Christmas
Click to expand...
Click to collapse
Hello, sorry to bump an old thread, but when I tried to boot into normal boot mode, it tells me "The system cannot find the file specified." I have been stuck in this TWRP recovery mode for so long. Even when I get into Normal Boot mode, how do I get JellyBean installed so it loads that ROM? I have the Jellybean ROM files on the Kindle, which I can access via TWRP, but don't know how to install. HELP!!!
Well, right now I did a factory reset of the Kindle and I was able to get the KF back to it's defaults. I copied the Jellybean .zip file and gapps Jellybean .zip file to the root of the KF. I booted into Recovery Mode and I was finally able to see both .zip files when I clicked on Install. I thought I could do the Permanent Root now that I did the factory reset, but once I ran it under KFU, it would go through the process to install TWRP and then boot the KF into TWRP, but it doesn't look like it completed the root. How do I complete it?
In the meantime, I had went into Recovery Mode, went to Install and currently loading Jellybean onto the KF. I'm currently stuck at Verifiying partition sizes and it's been sitting there for a few minutes. How long does it take before it's updated to JB?
System Only boots to TWRP and KFU will not see kindle
I have a Kindle Fire 1... Not the HD when I got it in Dec of 2011 I got some help to get TWRP and CM7 Installed on it, and it worked great until a couple of days ago and now there is no help in the kindle fire room anymore so I was wondering if there is someone out there who would be willing to help me to get this to work again either through teamviewer or a Chat of some type, Gtalk, IRC anything at this point to get this to work again.
I have tried everything from a Hard reset, and KFU will not see it and I even tried a unbricking tool and that cannot find it either. Please help me out.
Thanks
CloudStrrife said:
I have a Kindle Fire 1... Not the HD when I got it in Dec of 2011 I got some help to get TWRP and CM7 Installed on it, and it worked great until a couple of days ago and now there is no help in the kindle fire room anymore so I was wondering if there is someone out there who would be willing to help me to get this to work again either through teamviewer or a Chat of some type, Gtalk, IRC anything at this point to get this to work again.
I have tried everything from a Hard reset, and KFU will not see it and I even tried a unbricking tool and that cannot find it either. Please help me out.
Thanks
Click to expand...
Click to collapse
What exactly is going on...spare no detail...
Sent from my Nexus 7 using Tapatalk 2
Stuck booting into TWRP
Hello Forum Lords, I hope that I found the proper thread for my problem.
I was simply trying to install Cyanogemod 9 on my wifes replacement KF1 after the first KF1 suffered some sore of hardware malfunction and would no longer take a charge. Somehow, somewhere I went horribly wrong this time around. I got stuck at the KF1 logo and eventually I got it to boot, but only to recovery.
My predicament is this: My KF1 is stuck booting into TWRP. Device manager on Win Vista recognizes the KF1 as Android Composite ADB Interface. When I try to use the KFU to boot the device into Normal Mode it says "cannot find the drive specified".
At the KFU starting menu, it says ADB Status: Online, Boot Status: 0x5003.
My ultimate goal is to get this thing running Cyanogenmod again. I am painfully noob at all of this. Please speak as you would to an escaped chimp who will not let go of the keyboard and mouse.
Thank you, anybody
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.
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.
I'd like to preface this by saying I read the FAQ and did some searching here, but couldn't spot anything that sounded like my problem. I've half got an idea of what to do, but I'm quite confused and feel like some stuff needs clarifying. I apologize if this is more common than I realize, cause if it is I'm sure y'all are sick of answering questions like this.
---
I got a used Kindle Fire from a friend that came with CM10 on it. I wanted to use it for reading, but the Kindle android app was recently broken by Amazon so I reluctantly reverted it back to stock (I really liked having a tablet, but I've got a phone for that stuff and I needed an e-reader). The very next day they fixed the app so I decided I should load CM10 back onto the Kindle. Now, I flashed CM10 onto my phone last year and it was a painless process so I figured it'd be the same here. Somehow in the process I completely messed things up.
From stock FireOS, I used Kindle Fire Utility to flash TWRP on my Kindle, then from there installed CM10 again. What I didn't know, was that CM no longer comes with gApps preloaded. I had no clue, as when I flashed it onto my phone it had all the gApps on there. So I google it and find out I need to flash gApps on there. Here's the problem: I can't boot this thing into recovery. Somehow TWRP was lost in the process. I enabled developer options in the settings, then enabled the option to choose reboot into recovery in the power menu but when I choose it, it just reboots into CM10 again. I'm not sure how I'm supposed to revert back to stock or flash gApps in if I can't get to TWRP again.
It's clear this has gotten way over my head.
Summary:
* Have a kindle w/ fresh install of CM10 on it.
* No gApps and can't boot into recovery.
* I think TWRP might be gone somehow.
* I want to either return to stock or get TWRP back safely and gApps flashed on here.
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
themetalman said:
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
Click to expand...
Click to collapse
I can't seem to get KFU to recognize my plugged in Kindle. IIRC when I first used KFU, when it recognized the Kindle it displayed "ADB Status: Online" and "Boot Status: 4000". Now it's ADB Offline / Boot Unknown.
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
TheSMP said:
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
Click to expand...
Click to collapse
I have used the download and the bottom of this page to repair a bricked kindle fire.
Link: http://n2aos.com/
Then go back into kindle utility and reinstall TWRP and firefirefire.
You might also want to look at this site. He has great tutorial videos. Link: https://sites.google.com/site/tomsgt123/all-videos/kindle-fire
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