Develop Bugs

root and recover help please

hey guys, i bought the fire for my wife for valentines day, immediately rooted it to get rid of that terrible kindle launcher and stuff, well, I've got a transformer prime and galaxy nexus, so after a couple months of her playing with my ics awesomeness she now wants to come over the good side, only t hing is, for the life of me i can't rememeber what i did as far as recover goes on this fire. I've read to hold the power button until it turns orange, but it won't do that for me. So how do i get into recovery with the kindle fire?

With your Kindle Fire off, hit the power button (and release it), and wait for the FireFireFire logo (triangular) to appear. Then, hit the power button until it turns from green to orange/red, and let go. You will then go into recovery.

first off, thank you very much for your reply.
When i pushed the power button (with the kindle off) it just went to a black screen with the word "kindle" in white and the word "fire" in orange. stayed there for about a minute or two then booted up. never a yellow triange.....any ideas?

vballrkc said:
When i pushed the power button (with the kindle off) it just went to a black screen with the word "kindle" in white and the word "fire" in orange. stayed there for about a minute or two then booted up. never a yellow triange.....any ideas?
Click to expand...
Click to collapse
Oops! Looks like you lost FireFireFire somewhere along the way. Probably because of the recent Kindle update, which also would have unrooted you, unfortunately. You will need to re-root (which will reload the FireFireFire boot loader).
The Kindle Fire Utility can root a 6.3 (OS) Kindle Fire. Not sure how you rooted last time. If you did not use KFU, the old procedure you used may not work any longer.

Ah. Ok. I was unaware you get iota updates after rooting. Thanks ill just start all over.

[Q] Kindle Fire keeps restarting and freezing on yellow triangle

I apologize, I posted this in the General Info section by mistake. I don't know how to delete that post, but wanted to post correctly here.
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?

[Q] Help Dealing with Unresponsive Screen/Buttons (Probable Water Damage)

On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.

install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do

My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2

ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)

bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2

[Q] Stock KF stuck in boot loop - Win7 PC doesn't recognize KF

After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.

hiltoncp said:
After searching and reading many threads and trying several "fixes", I think my last resort is this post (at least before I try Firekit or similar). I hope I didn't miss the one thread that has my answer.
Background:
Using Win7 64 bit
KF 1st gen (I believe)
Completely stock
Using Amazon KF HD charger and USB cable Amazon supplied when similar issue happened with our other KF (that new charger fixed that one)
Symptoms:
While plugged into the charger the green light will appear and a few seconds later we'll get the "KINDLE FIRE" logo on screen, sometimes it's animated and sometimes not. Sometimes the logo appears for about 5 seconds and other times about 30 seconds. When the logo appears the screen back-light first starts out low and then after a second or so it will brighten until the logo disappears and the KF appears to turn off, at least until some seconds later the green power light will come on and the process starts all over and keeps repeating. On occasion during the cyclic boot process I have seen the slide lock screen which was unresponsive and once I saw the screen with the KF device name, time, WiFi status, batt level (and no I didn't notice), etc. Lately I haven't seen either of those screens again, just the logo or nothing.
I've downloaded the Android SDK and installed the drivers but when I plug the KF into any of my USB ports the KF is not recognized. So if I can't get the PC to recognize the KF I can't go any further with trying to restore to factory default using TWRP or similar.
So my question is does anyone have something else I/we can try before moving on to Firekit? Thanks to all for your time and attention. BTW Amazon offered to sell me a new KFHD for $129 but I just don't have that in my budget right now so your help is much appreciated.
Click to expand...
Click to collapse
You need a factory cable

KF Factory Cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.

hiltoncp said:
I appreciate the quick reply. So my follow-up is to say I'm using the USB cable that came with the Amazon charger they sent when having problems with our other KF. Is that not a "factory" cable? If not, do you have any idea if this one would work: ebay.com/itm/like/271275399661?lpid=82 ??? Or do I need to spend $17 on this one: amazon.com/Factory-Amazon-Kindle-Motorola-Tablets/dp/B00BPDH4G4 ???
Thanks again.
Click to expand...
Click to collapse
Yes 'factory' as in the one they use at OEM to install software.
Build Your own factory Cable is also an option if you can solder tiny things.

kindle fire black screen, botom led off

HI,
I just try to root my Kindle Fire 2nd gen using Kindle Fire Utiity 0.9.6 and all goes fine until stack on screen wait... and I wait for 15 min with black screen, green led. I decide probably stupid thing, disconnect from cable and try to restart it but its not restarting. Now it have black screen, no led its working, not charging (was fully charge before I start) not responsive at all. I try to hold reset for 15s, 30s, 60s and nothing not switch on. Did I permanently bricked?

Probably, as kindle fire utility is only for first gen
Sent from my DROIDX using XDA Free mobile app

see attached

Thanks. I found this in different forum and was sure it is for 2gen my fault, should came here first I open it, disconnect for few hours battery, reconnect and still dead. Nothing can be done to rescue?