long story short.
Rooted my kindle fire with kfu, flashed hashcode JB rom and gapps successfully. Father-in-Law says, hey that is cool do mine.
Rooted with kfu, flashed hashcode JB rom and gapps. When I reboot after flashing the roms, it gets stuck in the twirling triangles load screen for hours. When I restore the back-up (more on that issue in a second), it gets stuck on a static kindle fire boot.
Memory was nearly full so I only backed up boot and recovery with twrp. I can move between different bootmodes fine, and am sitting in twrp right now. I have connected USB to computer and kfu says it is online, but it is not showing up on my computer for me to simply download a new Rom onto device.
How can I either, get back to working stock OS, or flash a new (hopefully functioning rom)?
I scoured for hours and didn't find anything that fit my bill, I am admittedly a noob, your help would be appreciated and if I missed a forum dealing with this issue please post a link.
Backing up boot and recovery does very little if anything at all that's why those to items are not part of the default backup scheme. Your situation is not much different than about 96% of those who come to XDA for kindle help and is caused by a dirty flash so I'm very surprised it doesn't fit the bill of many others. Maybe my tutorial will help look at the bottom of my post on how to flash a ROM. http://forum.xda-developers.com/showthread.php?t=1923010
Edit: it doesn't help that the memory is so full as well.
Related
Hi all, I am completley new to all of this side of technology, and rooting my kindle fire seemed an easy task, and it probably is but i think i have well and truly messed it up and any help will make me a happy man again!!!
I carried out the procedure using the KFU, at first my device was not online, so i used the method described via device manager which worked fine, the device was online and i carried out the permanent root with super user, everything went fine, i then went on to install from the extras the google play bit.
This is where things have gone wrong i think, as now the kindle will turn on but it gets stuck on a screen with kindle fire written across it the fire bit is an orange colour, i can get it to boot into twrp screen via the recovery boot aswell.
But everytime i try to connect to the KFU its always say offline no matter what i do. Is there a way to start over agan????
Like i said im new to all of this and have read a few how to's and explanation threads but i get easily confused, lol!!!!
Cheers
You can try clearing the cache/dalvik cache using TWRP and rebooting, but that probably won't help. If you are prepared to lose all of your settings, installed apps, etc. do a factory reset in TWRP and reboot. It should complete the boot process then. Otherwise, you're looking at reflashing the stock software and starting over... in which case, I recommend you just flash modaco and be done with it.
Whatever the case may be, learning about how your device works will help you out in the long run...
http://forum.xda-developers.com/showthread.php?t=1552547
Go back to the Kindle fire utility and press option 1(bootmode) then normal boot (4000) no matter if it says offline it will still work m8.:good:
Give it a shot
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'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
Years ago my daughter loaded "perfectly android" rom on this tablet. Recently it no longer boots.
Model 3HT7G
Turning on, you get the Kindle Fire in orange, then screen flashes and you see Kindle Fire in Blue.
Then a strange strip of color down the left side.
Then it sits on a "perfectly android" screen and blanks the screen every few seconds.
It does this until you hard power it down.
Anyone know how to remove this custom ROM and put something modern on there? The "perfectly android" website exists still but most of it doesn't work.
I have a link in email from them where she bought the software back in 2016 the file was called "Perfectly-Android-CM12-HD89-Installer.exe"
The install notes mention TWRP but not the version and the filename suggests Cyanogen Mod does it not?
Thanks in advance for any assistance.
seems stuck in TWRP screen loop. the screen I see is just some custom TWRP logo screen from whatever my daughter installed years ago.
ADB nor fastboot seem to respond.
I do see the Kindle in device manager, I installed the SDK and ADB drivers.
Fastboot always just reports <<waiting on device>>
Tried two different USB cables
Any thoughts on how to un loop it?
Best guess is the recovery image is corrupt?
OK, after many attempts I finally got it in to fastboot boot mode, did the recovery steps in the threads on here and I'm back to a fully functioning stock 8.1.4 install (I think that is the image that it recovered to, I can check if it matters the exact stock version).
What is the latest stable modded ROM released for these gen tablets? I think it had CM12 on it before based on the file names.
denathor said:
OK, after many attempts I finally got it in to fastboot boot mode, did the recovery steps in the threads on here and I'm back to a fully functioning stock 8.1.4 install (I think that is the image that it recovered to, I can check if it matters the exact stock version).
What is the latest stable modded ROM released for these gen tablets? I think it had CM12 on it before based on the file names.
Click to expand...
Click to collapse
There isn't really a stable rom for the Jem 8.9. It's mostly nightlies available
Best I used was temasek 13.1 from android file host.
However most of the roms have bugs so I reverted to pre-rooted stock.
I then just Debloated the latest stick rom and installed nova launcher.
After that I binned it and bought a Samsung galaxy tab a 2016 as the Jem was painfully slow