Develop Bugs

[Q] Is the yellow triangle a stock screen?

Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU? Amazon said they would send a replacement, but I'm wondering if I'll have issues if they see it's been rooted...
Update 6.3.1 has left me on this screen, and as of yet I have not been able to get around it. The computer will only recognize it for about 5 seconds when it is plugged in, but then the LED on the KF goes Orange and it disconnects.
I'm looking at getting the factory cable.
Unfortunantly when I ran the KFU I did not install any other recovery options other than rooting the device. (Crossing over from the jailbreaking on the iPhones, you could get the device is recovery without any big deal and I assumed it was the same with the KF...oops)

Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
While in recovery, look for an option to mount your sdcard.
When it is mounted, it will show up on your computer as an external drive.
From your computer, transfer the "Flash.zip" from this link: http://forum.xda-developers.com/showthread.php?p=25598837 ...to your sdcard.
Then use recovery to flash "Flash.zip" and reboot.
When it reboots, hold the power button until it turns orange again and use the selections at the bottom to change your bootmode. To scroll through the selections hold the power button for a second and release. When you have the right option selected, leave it alone for a few moments and it will select automatically. You may need to reboot.

Avidmtbiker said:
Is the yellow triangle ('press power for recovery options') a stock KF screen, or is the something that's been added by the KFU?
Click to expand...
Click to collapse
This is not the stock boot loader screen, it is an older version of FireFireFire.

soupmagnet said:
Turn your Kindle off.
Turn your Kindle on.
As soon as you see the yellow triangle, hold the power button until it turns orange. This will boot your device into recovery.
Click to expand...
Click to collapse
I've done this...
But there's no response from the KF, the screen doesn't change. The LED does go Orange, but it would anyway - even without pressing the button.
The computer is unable to recognize it at this point.
As of now it seems only to turn on whenever the USB cable is plugged in, I'm guessing the battery is dead.
Any more suggestions? I'm leary of sending it back in with modded software, I imagine they're smart enough to check that...

Ah, so you don't even have recovery installed. I guess I should have seen that in the OP...I'm such a noob <hangs head in shame>
OK the first thing you need to do is educate yourself a little bit about the Kindle Fire, the different bootmodes, and the difference between adb and fastboot:
http://forum.xda-developers.com/showthread.php?p=23747567
Then you need make sure your drivers are in good working order:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
When you have a good foundation to work from, we'll get recovery installed and continue to fix any other problems you need help with.

KF stuck at Kindle Fire white/blue logo; tried a few ways including Linux

Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
​- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
​- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
​- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
​- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
​- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.

A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.

Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.

ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.

Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...

Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.

I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.

Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544

ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.

your welcome I`m quite pleased its fixed myself

same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)

I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help

hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs

[Q] Kindle fiire rooting fail

SO recently i tried to root my kindle using one of the guides unfortunately i somehow messed up during it or something, but the problem i have now is whenever i turn my kindle on it has the yellow triangle with a fire logo in it and at the bottom it says "press power button for recovery". Simple enough only the second problem is i do not have TWRP or anything like that so pressing the power button literally does nothing. Unfortunately as well when i plug it into the USB it will identify that something is connected but it won't install it to the pc because it cant find some hardware or something. So i cant get it to start up or connect it to the pc and am desperately looking for a solution. Thanks to anyone who can help.

First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.

jma9454 said:
First off. Do you have a first gen kindle fire?
6.3.x or 10.x.x?
If you have a first gen,
Download this.
http://forum.xda-developers.com/showthread.php?t=2192818
Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer.
Does KFU find the device? If so, good. You will be taken to the main screen at that point I think.
Choose to install recovery (TWRP).
That should be it. Post here if there's any problems.
Sent from my muffin-ated Kindle Fire with Tapatalk HD.
Just because I am a Senior Member doesn't mean anything.
I do not count myself any higher than anybody else.
Click to expand...
Click to collapse
Attached is a picture of what my kindle screen looks like. I tried resetting it, plugging it into the computer, etc. but this screen never changes. Also on my pc it doesn't recognize it as a kindle, it recognizes it as an unknown device. So I can't put any files onto my kindle at the moment because my PC keeps telling my me driver is not working or something. I attached files showing what my pc says as well. Also I apologize for the bad quality of the pictures i don't own a very nice camera at all so I apologize in advanced for that. The last 3 are readable the 1st one is basically just a yellow triangle with a fire symbol in the middle and it says "press power button for recovery" but nothing happens when i press the power button, and the 2 photo is a little bit blurry but all it says is:
Unknown Device
Device Type: Universal Serial Bus controllers
Manufacturers: (Standard USB Host Controller)
Location: Port_#0009.Hub_#0002
Device Status:
Windows has stopped this device because it has reported problems. (Code 43)

The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.

soupmagnet said:
The "press power button for recovery" can be confusing if you don't know what's going on. That version of FireFireFire sits in fastboot mode for...I think...8 seconds before it will recognize the power button. You can repeatedly press the power button until the LED turns orange to see if that gets you into recovery. If not, you're probably looking at something like usbboot to replace your bootloader. You need to replace your bootloader anyway, but hopefully you'll be able to flash a new one in recovery instead.
Click to expand...
Click to collapse
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?

KindleFail said:
Repeatedly pressed the power button for about 30 seconds with the same result, green light still, and no screen change. So it looks like its this usbboot, how would i go about doing this in order to replace my bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1405052
http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit
Since you will need Linux anyway, you might as well download and install SoupKit. It comes with Firekit and will probably make your life easier in the long run.

What guide did you use exactly? I can see if we can update that guide to use the latest FFF because that is a very old alpha version that has had many issues with the yellow triangle in the past. I'm surprised its still floating around here.
Sent from my One V using xda app-developers app

Stuck at boot logo
Hey all,
I'm not sure if this is the correct place to post but I didn't want to make a new topic and this seems to be in the area of what is wrong with my kindle... I tried the new KFU v0.9.9 on my first gen KF running 6.3.2. I have rooted it before (not on 6.3.2), but unrooted and restored to factory settings because I thought I was going to sell it. However, the plans fell through and I am keeping it so I wanted to re-root and all that jazz....
My question is, how do I get it boot past the boot logo? I used the KFU, but firstly when it prompts it says:
'findstr' is not recognized as an internal or external command, operable program or batch file.
So none of the commands pop up, however they are still there... For example, i followed:
"Choose bootmode menu, and choose fastboot.
Hold down the power button for 10-20 seconds till it turns off.
Connect your kindle to your computer."
And I can get to fastboot, but it says there is no device connected to my computer. If you need more details on the problem I'll be glad to give them to you. Hopefully someone checks this thread again
Thanks

What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?

soupmagnet said:
What version of Windows do you have that doesn't have 'findstr'?
What do you see in your device manager while the device is plugged in?
Click to expand...
Click to collapse
I'm running a 64 bit version of Windows 7 professional.
There's nothing in the device manager when I plug it in.

Softbrick after formatting system... Fixed

So not paying attention I formatted system and didn't flash new ROM before rebooting. Now I can't get into recovery, even trying alt+sysrq+i, and turning on the system just shows a black screen. The Ouya is being detected as MTP device and no adb/fastboot functions work. Is there any hope in getting this one back in working order?

So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!

BUS DR1V3R said:
So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!
Click to expand...
Click to collapse
What if that exact timing doesn't work? I've been able to use that method before, but I think I've fully bricked the system.

trevorftard said:
What if that exact timing doesn't work? I've been able to use that method before, but I think I've fully bricked the system.
Click to expand...
Click to collapse
What did you do to the system?

Exactly same prob here, but the keyboard trick doesn't work for me
I messed up after flashing CWM Recovery and perform a full wipe.
Any chance to get it back ?

ElMeteK said:
Exactly same prob here, but the keyboard trick doesn't work for me
I messed up after flashing CWM Recovery and perform a full wipe.
Any chance to get it back ?
Click to expand...
Click to collapse
Do you have ADB access? I might not be the best person to field these questions, but I'll give 'em a try.:good:

BUS DR1V3R said:
Do you have ADB access? I might not be the best person to field these questions, but I'll give 'em a try.:good:
Click to expand...
Click to collapse
Nop, no adb access.
Only showned as MTP device.

ElMeteK said:
Nop, no adb access.
Only showned as MTP device.
Click to expand...
Click to collapse
Ah, I looked high and low for answers for this all day yesterday and must have tried the keyboard trick at least 100 times before I found a timing that worked for me. My only advice would be to keep trying slightly different timings. You may have to use the alt+sysrq+i key combo more times than I did. Try doing it about 10 or 15 times. Just remember to hold the keys for a few seconds, release, and hold again.
My screen eventually flashed green and the system rebooted straight into recovery.

BUS DR1V3R said:
Ah, I looked high and low for answers for this all day yesterday and must have tried the keyboard trick at least 100 times before I found a timing that worked for me. My only advice would be to keep trying slightly different timings. You may have to use the alt+sysrq+i key combo more times than I did. Try doing it about 10 or 15 times. Just remember to hold the keys for a few seconds, release, and hold again.
My screen eventually flashed green and the system rebooted straight into recovery.
Click to expand...
Click to collapse
It's not working for me
I've tried for about an hour unsuccessfully (

ElMeteK said:
It's not working for me
I've tried for about an hour unsuccessfully (
Click to expand...
Click to collapse
Sorry, it worked for me but I was at it for at least 4 or 5 hours before I finally got it to work. All I can tell you is either keep trying or run out and get a new system. :fingers-crossed:
We need a hardware mod to add a recovery button to existing units. As soon as one is available I may offer a cheap service to install any mods needed. Until then we are reliant on a somewhat flakey keyboard shortcut.

BUS DR1V3R said:
So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!
Click to expand...
Click to collapse
rather then booting into recovery mine just goes to a black screen with OUYA and a red "!"
am i doing something wrong or do i just have to keep trying? or is it toast?

glitchhawk said:
rather then booting into recovery mine just goes to a black screen with OUYA and a red "!"
am i doing something wrong or do i just have to keep trying? or is it toast?
Click to expand...
Click to collapse
Try pressing the Home key on the keyboard. It may take multiple presses.

BUS DR1V3R said:
Try pressing the Home key on the keyboard. It may take multiple presses.
Click to expand...
Click to collapse
oh man thanks! first time i got into ! screen the menu opened. wow lol. WOOT!! there is still hope!!

glitchhawk said:
oh man thanks! first time i got into ! screen the menu opened. wow lol. WOOT!! there is still hope!!
Click to expand...
Click to collapse
Good stuff, glad you got it going!

I was able to get my Ouya into recovery mode one time after trying off and on for hours, but I had it plugged into my computer monitor and when I changed the monitor source back to DVI (my PC) to see which option in the recovery menu to choose and switched back, the HDMI source showed "no signal". I haven't been able to get it back to that screen since and I wasn't really paying attention to the timing (of course). It's odd to me that since I can see device in ADB while it's booted to black, but "adb reboot recovery" does nothing.
Can someone who has discovered the correct timing and can get into recovery consistently help with these questions? It might help with some other cues to know if you're doing it right rather than just "restart it over and over and try different timings".
1.) Does the power LED on the top of the Ouya stay on when it's in recovery mode?
Occasionally, my power LED will turn off but the device still says it's connected in ADB.​2.) If you have the Ouya plugged in via micro-usb when you turn it on, do you hear the USB connect sound?
I'm using Win 7 and depending on my timing I either DO or DO NOT hear the USB connect sound from my speakers as it's connecting as a ADB Composite Interface / MTP Device.​3.) Does your Ouya lose HDMI signal in the "boot to recovery" process?
I know not all TV's/monitors timeout at the same interval, but If I leave my Ouya alone it boots to a black screen, messing with the key combo sometimes make its turn blue and show "No Signal"​4.) If your USB keyboard has LED's on it to show when caps/num/scroll lock are pressed, do they illuminate when plugged into your Ouya?
I found some documentation on sysrq magic keys in the Android kernel docs, maybe one of the other key combos will have better results?
https://android.googlesource.com/kernel/common/+/experimental/android-3.8/Documentation/sysrq.txt

I finally stumbled upon the right key combo timing again through sheer dumb luck. I took my Ouya out of my office and back into the living room, connected it to my TV with a USB keyboard and gave it one last try before giving up - glad I tried one last time.
For anyone else that is having trouble still, here's some things that might help as well as answers to my questions from above. Some of it is just speculation, but maybe it'll help someone:
Timing: As SOON as I tapped the power button on the Ouya I immediately held down ALT on the keyboard and every few seconds also pressed SYSRQ+i (never letting go of ALT). I believe I did it a total of five times and I stopped as soon as I saw the LED on the top of the Ouya turn off. I didn't really hold down the keys and count a few seconds like I've heard others mention, I just tapped SYSRQ+i around five times while holding down ALT. Menu popped up after the power led turned back on.
Driver: Make sure you followed the guide from the Ouya docs and have the right version of the Google USB driver installed (here's the Windows guide https://devs.ouya.tv/developers/docs/setup#toc_61). When my Ouya was booting to black it was showing up as an Android ADB Interface and a MTP usb device that it couldn't find a driver for. The correct identification should be Android ADB Composite Interface
ADB Make sure you're running the lastest version of ADB (1.0.31 currently). When I ran adb devices on the black screen it would return my device serial number and the string "device" which refers to the state it was in (occasionally this value would "offline" when I'd tried a key-combo that failed to get into recovery mode).
Once I got recovery mode up and selected the adb sideload option adb devices would show my Ouya serial number and say that it was in the "host" state. When I tried the adb sideload otafirmwarefile.zip command, it would fail because adb sideload wasn't a valid command in the older version of adb I was running. Running the google SDK manager from the ADT bundle, removing/re-installing android platform tools and logging out / in to Windows fixed this for me next time I opened a command prompt. Now with the right ADB version running adb devices on my micro-usb connected PC showed my device serial number and "sideload" as it's state.
Answers to my previous questions:
1.) Does the power LED on the top of the Ouya stay on when it's in recovery mode?
Yes and No. The light turned on when I powered it on, after alt+sysrq+i presses the light TURNED OFF momentarily and then turned back on just as the recovery mode screen came up​
2.) If you have the Ouya plugged in via micro-usb when you turn it on, do you hear the USB connect sound?
Not sure, when I got into recovery mode I had my micro-usb cable disconnected. I reconnected it once I selected the second option in the recovery menu (adb sideload)​
3.) Does your Ouya lose HDMI signal in the "boot to recovery" process?
Yes, at least mine did. I had black screen at boot, then it went to "no signal" at the same time the LED at the top went out, then the screen came back on when the recovery mode screen came up​
4.) If your USB keyboard has LED's on it to show when caps/num/scroll lock are pressed, do they illuminate when plugged into your Ouya?
No, the LEDs on my USB keyboard never lit up, but the keyboard was working.​

Fire TV Stick 4k half dead open for suggestions

2 days ago I came back to my Fire TV Stick 4k only to find black screen with "loading..." letters in corner, and at that moment pressing home button did nothing, seemed that remote isn't working at first or device froze.
3 Hours before that I has using device, and only thing I did i power toggled it 3 times in few seconds using power button on remote (don't ask why it irrelevant now)
After I power toggled the device, and after "Fire TV" logo it stated that it can't find my remote. So i changed fresh batteries, tried to resync remote to device and all other stuff, but nothing helped. So I decided to try my remote on another device, and concluded that remote is perfectly fine and connects to other device without problems, and that it's nothing wrong with it.
At the same time it baffled me that device didn't load home screen after boot, just notification that it cant find remote and black screen after that.
Later I discovered that remote is in fact working (built in firmware restore functions and menu that is accessed by long pressing home button for few seconds).
So I decided to do factory reset by pressing key combination.
Factory reset menu came up, and after I pressed "OK" nothing happened, device didn't reboot.
Pressed key combo again, and let the timer for factory reset count down to zero.
When it came to '1' it froze.
Pressing key combo again factory reset menu would come again and do countdown from start.
I can also invoke menu accessed by pressing home button for few seconds, but what ever I choose from there it freezes, but if I press home button again it opens same menu again and move left-right and even enter "profiles", so it's not frozen, it just seems that it can't open any menu entry for some reason.
At he same time I can access it via wifi ADB and run ADB shell commands, so it is connected to wifi that has internet access.
I tried running "adb reboot recovery", device reboots, comes up with Fire tv logo and "no command" on screen.
It sits there for a minute and after it reboots and goes into normal boot.
I also tried "am start -n com.amazon.tv.launcher/.ui.SettingsActivity" folowing "am broadcast -a com.amazon.tv.intent.action.MASTER_CLEAR" but no avail.
it states "Broadcast completed: result=0" and that is it.
How do I factory restore / flash firmware, whatever ?
I will take any suggestion before tossing it into bin, because I think memory got corrupted somehow and device is processing and executing fine.
Edit 1 :
Safe mode method using USB keyboard on OTG cable doesn't work. Tried ctrl+alt+menu+prtscr+i several times, it invokes nothing.
Edit 2 :
Tried rooting using shorting to ground exploit, but it doesn't work since serial number of device is too high thus bootloader locked.
Edit 3:
I can see all the installed packages over ADB and uninstall ony of them normally.

Hi mate, try my solution up for the bootlooping firestick

Travel_Mate said:
Hi mate, try my solution up for the bootlooping firestick
Click to expand...
Click to collapse
Thank you for suggestion. The main question is how do I format USB stick to Android "internal memory" if I don't have Xiaomi 4K stick, like you mentioned in your original post ?
I have another working Fire Stick 4k, and have formatted USB stick using that device, but since Fire Stick 4k uses Fire OS 6, and possibility to format USB stick to "internal memory" is a feature of Fire OS 7, I don't think it will work.
At the moment I just formatted this stick using Fire OS 6, connected using OTG to malfunctioned stick, I can see Fire TV accessing it few times on boot (LED flashes), but after boot I don't see any activity. I will let it sit for a few hours.