Develop Bugs

[Q] PLEASE HELP!! Kindle Fire stuck at yellow triangle.

I tried to root my girlfriend's kindle today, and I did everything right, up until I had to install twrp with the kfu. She pulled the usb out before it could install, and now im stuck at the yellow triangle. Ive been able to get my computer to recognize it as "kindle" under device manager, but Im lost as to what to do next. Ive tried to update the drivers but it wont install. I REALLY WOULD APPRECIATE ANY HELP!!!

Try booting into recovery, if that doesn't work then try getting the kindle fire utility to get stock update.zip (#4 in run). If that doesn't work then I have no idea.
Sent from my Kindle Fire

Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device

King_Me said:
Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device
Click to expand...
Click to collapse
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.

I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*

King_Me said:
I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*
Click to expand...
Click to collapse
Lol well that's good.
Sent from my SGH-T989 with CM7

colorblind
BiteBlaze said:
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.
Click to expand...
Click to collapse
I'm there too but (gulp) colorblind, it might turn orange but I don't see it. I am stuck at triangle not being recognised by computer.

http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?

b63 said:
http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?
Click to expand...
Click to collapse
Hi, I have a similar (maybe the same) problem: my KF has blocked the yellow triangle.
This happened after that I tried for the second time to apply the "Install permanet root with superuser" from the Kindle Fire Utility 0.9.5.
The first time everything went fine except the subsequent installation of Extras returning error at the following lines:
tools\adb push apps\system\vending.apk /system/app
tools\adb push apps\system\GoogleCalendarSyncAdapter.apk /system/app
tools\adb push apps\system\GoogleContactsSyncAdapter.apk /system/app
The error was: permission denied.
So, I tought that somenting wen wrong in the previous installation and I tried again.
This time something went really wrong: the KF is in the state I told: yellow triangle.
I tried to turn off and on again but it is in the same state.
I tried to push the button waiting for the TWRP to get up, but nothing happened.
I tried to connect with PC, but the KF is not visible.
What can I do? Does somebody have any hint?
Thank you.

[Q] Did I brick my Galaxy Nexus?

Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?

I'm not too sure on this so I'd wait for someone for experienced to reply.
But I can say that it's very hard to brick a Galaxy Nexus. So have some hope.

How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.

Can you get into bootloader? Hold volume up+down and power on.
The android logo you recognised before with the '!' sign was 'Download mode'. If you can see anything on screen there should be no reason why you cant recover it. Don't worry your not bricked.

Same problem!!!
CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!

coprotsap said:
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!
Click to expand...
Click to collapse
Are you on stock? Have you unlocked the bootloader and rooted your device?

Yes to all
RTContent said:
Are you on stock? Have you unlocked the bootloader and rooted your device?
Click to expand...
Click to collapse
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!

coprotsap said:
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!
Click to expand...
Click to collapse
do you have clockworkmod recovery? restore a backup if u have one, or wipe data/factory reset, it will work for sure if it was only bootlooping

martonikaj said:
How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.
Click to expand...
Click to collapse
Thanks for the reply. If I hold the volume up, volume down, and power button with the battery in and with the USB unplugged I can feel a vibrate. When I plug the phone into my computer I don't see any fastboot devices. All the drivers are the same and I have tried several USB ports and cords.
If I remove the battery and connect the phone to my computer I hear constant USB connect/disconnect sounds and OMAP4440 constantly appears and disappears in the device manager. Still unable to detect the phone using fastboot or Odin.

What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk

RTContent said:
What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.

CuteFuzzyPuppy said:
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.
Click to expand...
Click to collapse
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk

RTContent said:
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Nothing at all.

any luck? I am having similar problems. Phone will not be recognized and I can't access the bootloader. Constant bootloops

i had a similar problem last saturday. Worked on fixing it until yesterday. It was a corrupted sd(from what I can tell) so I never was able to start up my phone again or flash anything to it. I am waiting on a warrenty replacement from samsung. At first I could get to fastboot ect but all flashing errored out. Pretty soon I could only get to a screen with a phone ......triange.....computer screen. Thats where I am at now. I even tried a usb jig to get it back to download mode (which works on lots of samsung devices to get them back from bricked to the oden screen) with no luck. I have seen a few posts saying it is confirmed to work on galaxy nexus, but I had no luck. no luck. On the bright side I was able to pull my droid 2 global out of bricked state yesterday which made me feel a bit better.

CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Flash thw phone again. Happend to me on symbian.. so I flashed it,, your phone is not bricked
Sent from my Gnex

my phone is similar with yours.So did you solve it?

[Q] Rooted Amazon Kindle Fire, now bricked and my computer(windows 7) cant find it

I rooted my KF about a month ago, and its been working fine since, then my friend told me to download firefirefire and NWRP from the kindle fire utility(which i used to root). In the process of downloading firefirefire, a boot symbol pops up with the kindle fire logo and an android bot over it. Its been stuck like that since, and my computer wont read the kindle when its plugged into the usb. Im also sort of a noob, so please help?

You admittedly said you're a noob so you should read this http://forum.xda-developers.com/showthread.php?t=1552547 . Your kindle isn't bricked. It's in fastboot mode. There are a few ways you can handle this situation. Search the forums as your situation is not unique and has been discussed all over these threads. If your still having problems and can't figure it out come back here for help.

The screen your looking at is the bootloader screen the problem is your still looking at it. This replaced the old fff boot loader the yellow triangle. If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
You can hold down the power button till it fully powers off ,then power it on when you see the screen your stuck at hold the power button again till it turns orange and twrp opens up if not read more to find out what to do next

AKbambi said:
I rooted my KF about a month ago, and its been working fine since, then my friend told me to download firefirefire and NWRP from the kindle fire utility(which i used to root). In the process of downloading firefirefire, a boot symbol pops up with the kindle fire logo and an android bot over it. Its been stuck like that since, and my computer wont read the kindle when its plugged into the usb. Im also sort of a noob, so please help?
Click to expand...
Click to collapse
If you get your kindle booting correctly I suggest you flash the new bootloader 1.4a by Hashcode. You can find that here http://forum.xda-developers.com/showthread.php?t=1632375 This new bootloader has some additional options, one which will allow you to tell the KF to boot normally if you were to find yourself in this situation again.

Thepooch said:
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on.
This did not work.. i dont have the yellow triangle, i have the kindle fire logo with a bot on top... again, im probably stupid for not knowing how to fix this, but what do i do now?
Click to expand...
Click to collapse

actually, nevermind.. i forgot to install the driver, and when i did, KF unbricking utility was very helpful and i got my kindle to work again.

AKbambi said:
Thepooch said:
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on.
This did not work.. i dont have the yellow triangle, i have the kindle fire logo with a bot on top... again, im probably stupid for not knowing how to fix this, but what do i do now?
Click to expand...
Click to collapse
The kindle fire screen with the android is the same as the yellow triangle glad you fixed it
Click to expand...
Click to collapse

[Help] Kindle fire powers off instantly

So I am trying to get my Kindle to stay on long enough to flash to stock, but when I turn it on it is at the yellow recovery symbol. When I use the "Boot into normal" Mode on KFU, it will turn on after about 10 seconds. But after the Kindle is on, about 5 seconds later it just powers off. It is fully charged. How could you fix this?

http://forum.xda-developers.com/showthread.php?t=1623244

I charged it all night and it still dies right away. Also I cannot put FFF or anything on it because it isn't detected in recovery, only when it turns on for the 5 seconds. How do you fix this?

Very likely it isn't charging use USB to charge maybe you'll get lucky sending anything to the device in this state is to dangerous

Thepooch said:
Very likely it isn't charging use USB to charge maybe you'll get lucky sending anything to the device in this state is to dangerous
Click to expand...
Click to collapse
So you're saying I should just plug it in for the night, then try booting it again? What should I do after I get it on?

Well you haven't got that far and there's no promise it will even work because of the bootloader your running if it doesn't work then your looking at something different to fix it

Thepooch said:
Well you haven't got that far and there's no promise it will even work because of the bootloader your running if it doesn't work then your looking at something different to fix it
Click to expand...
Click to collapse
I don't have a bootloader. I am just running everything normal, except it's rooted.

any progress? If you have a yellow triangle that is the bootloader just to clarify

Thepooch said:
any progress? If you have a yellow triangle that is the bootloader just to clarify
Click to expand...
Click to collapse
It is plugged in still, I will try it out now. Also thanks for clarifying that.

Did you hold the power button down for 20-30 sec? If its fully charged, then either you have to do a 20-30 sec hard reset or its stuck in fastboot mode. Well, actually, no, its not in fast boot mode if it turns off. So try the hard reset.

Rebooting to fastboot on CM10.1?

Having a small issue with my device, and I could do with getting in to fastboot to troubleshoot.
I have TWRP installed along with a nightly version of CM10.1, When I try ADB reboot bootloader The device reboots, flashes the first bootscreen for a second(Orange and White Kindle Fire) and then shuts itself down.
Any suggestions that don't involve getting a fastboot cable? I can make one if I have too, but I would rather try and find out why it wont work this way.

Nvmd

So, you don't see the blue Kindle Fire logo at all?

I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.

Jackering said:
I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.
Click to expand...
Click to collapse
Why don't you use the volume button to access recovery?
Hashcode said:
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and keep pressing until the logo turns BLUE. Wait a moment and you should enter recovery.
Click to expand...
Click to collapse

I can enter recovery fine, I want to get in to Fastboot to test something.

Jackering said:
I can enter recovery fine, I want to get in to Fastboot to test something.
Click to expand...
Click to collapse
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?

soupmagnet said:
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?
Click to expand...
Click to collapse
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.

Jackering said:
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.
Click to expand...
Click to collapse
Oh nevermind, I was wrong. Typically you would use 'idme' to change the bootmode then reboot, but 'idme' isn't included in our version of TWRP. I thought maybe it could be pushed to recovery then executed, but I keep getting a "Segmentation fault" error on this version when trying it on my end. I'm not sure what's causing that other than perhaps this version wasn't made with 'idme' in mind, but that's purely speculation on my part. If you had any other device than a Kindle Fire 2 you wouldn't have any problem accessing fastboot, but as it stands now, I think your only option (to get into fastboot) is to acquire a factory cable or install a different ROM.
But even with fastboot, that's still not addressing your original problem. The fastboot binary is really only useful for overwrite\ing partitions and changing the bootmode. Whatever your problem is, it will likely be fixed by installing a non-nightly version of CM10.1 (nightly = not so stable).
As for your device manager, later versions of TWRP have different hardware IDs than that of the stock OS. Just add the hardware ID to your 'android_winusb.inf' and reinstall it.

soupmagnet said:
Why don't you use the volume button to access recovery?
Click to expand...
Click to collapse
Btw- we don't have volume buttons. Drives me nuts
Sent from my SGH-I727 using Tapatalk 2