Related
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.
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
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.
Finally I've got to the point where a faulty usb stick bricked my Fire TV Gen 1.
Short story: wanted do downgrade to an older rb_firmware on my device. My device was rooted and on the latest rbox firmware (5.2.6.6). So downloaded a former rbox firmware and wiped in twrp recovery everything except the usb drive...after selecting the rbox firmware and installing it, it stopped and didn't get further then copying image...after a while the fire tv rebooted itself and tada a black screen with a white amazon logo appeard and nothing more.
What I've tried: using fastboot commands by wireing the fire tv with an A to A usb cable....did not work, maybe because I have an only partial unlocked bootloader and no full unlock.
Is there a hardware method (emmc flash) or am I good to go and throw my fire tv in the trash.
assyriska said:
Finally I've got to the point where a faulty usb stick bricked my Fire TV Gen 1.
Short story: wanted do downgrade to an older rb_firmware on my device. My device was rooted and on the latest rbox firmware (5.2.6.6). So downloaded a former rbox firmware and wiped in twrp recovery everything except the usb drive...after selecting the rbox firmware and installing it, it stopped and didn't get further then copying image...after a while the fire tv rebooted itself and tada a black screen with a white amazon logo appeard and nothing more.
What I've tried: using fastboot commands by wireing the fire tv with an A to A usb cable....did not work, maybe because I have an only partial unlocked bootloader and no full unlock.
I had same happen as I tried to root a Gen 1.
There is a article here on how you can get into the AFTV1 via keyboard strokes. From there you try to reset to default. I got to the menu from the keyboard but did not work for me. Maybe someone can point to where the article is here or search it. Good luck!!
Click to expand...
Click to collapse