Develop Bugs

In Despair, desperate help needed!!!

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

[Q] Kindle will only boot to TWRP

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

[Q] Kindle Fire 1st gen Stuck at Boot Logo

Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.

jaredahuey said:
Hey Everyone,
I have been using these forums for the last year and a half and It has helped me a whole bunch to successfully root all of the android devices my family has. I have however ran into a problem with a 1st gen Kindle Fire. It is stuck at the orange and white kindle fire logo. So a little background, I have rooted this Kindle in the past and succeeded in flashing Cyanogenmod's jb. I changed it back to the old Kindle interface so that my sisters can use it for reading but they wanted to use it for games. I decided that I should just change it back to jb since I would have to go through the trouble of flashing google play. Now, here's when things go wrong.
I started by using KFU 0.9.6 since I was lazy and didn't want to go through my old method. I granted SU and also installed TWRP and FireFireFire. now, I found a rom by Cyanogenmod cm10.1.3otter and decided to flash it onto my device. Everything went fine but it wouldn't boot past the Cyanogenmod boot screen. So I put another rom on (cm10.1.2) and flashed that. It worked and i started using it under the assumption there was nothing wrong. I later discovered when entering the internet password that my keyboard was not working and nothing would allow it to work. I then decided that I would get the kindle rom back on and factory reset and wipe the device. When I flashed the Kindle rom and restarted it, It got stuck and would not boot past the Orange and white kindle fire logo. After 2 full charges and 48 hours, it is still stuck. I tried to check if the kindle showed up under ADB devices and it does but when I run adb shell(for one of the guides) it comes up with "no such file or directory." When I run KFU, adb is online but boot status is unknown. When I try to run any of the tools in KFU, waiting for device is shown and does not go away despite disconnecting and reconnecting/ power on and off.
I have been looking nonstop for the past two days without any help. I have tried to follow many of the guides online, but I never succeed. Can someone please help me solve this problem, I am completely stuck.
Click to expand...
Click to collapse
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.

Thepooch said:
You must enable adb on cm10 for one and the driver has to be modified for the pc to detect it due to pid and vid changes in cm10.
Click to expand...
Click to collapse
I am aware of that however, I cannot boot to cm10. If i could boot to cm10, I would know what to do but right now I am still stuck at the kindle fire logo.

[Q] Kindle Fire 8.9 Stuck on static boot screen.

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

[Q] kindle fire 2nd gen(?) /2nd bootloader/recovery

A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.

Lilybet said:
A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.
Click to expand...
Click to collapse
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.

stunts513 said:
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.
Click to expand...
Click to collapse
Thanks. Perhaps I made a mistake falshing recovery. Fixed now, TWRP works OK.
Now I am stuck with getting a working combination of ROM + GAPPS: Tried
1) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130813-signed.zip --- get "unfortunately com.android.phone stopped".
2) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130301-signed.zip --- get "unfortunately, android keyboard (AOSP) stopped" Clear data + clear cashe do not solve the problem.
3) cannot flash any cm-11 from download.cyanogenmod.org/?device=otter2&type=snapshot : get message set_metadata_recursive: some changes failed. E: Error executing updater binary in zip 'sdcard/cm-11*/ Error flashing zip 'cm-11-*'.

Something is telling me that TWRP v2.6.3.0 is not compatible with CM11 and Android KK. Is it correct?
Thus I need a working combination of CM10.? and JB GAPPS.

Tried this one early morning today: http://forum.xda-developers.com/showthread.php?t=2146030
Flashing was OK, but cannot boot afterwards: get a screen with rotating/flying triangles, nothing else.

Alright, the only combination with CM 10.2 that works at this moment for me is JB 4.3 with CM10.2/SGT7:
http://forum.xda-developers.com/showthread.php?t=2416561&nocache=1
The other threads seem to have links incompatible roms/gapps due to updates...