Develop Bugs

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.​

[SOLVED] Think I bricked...

I started off slow, I had my OUYA fully updated, I used the OneClick Recovery, went fine. Then I threw the "RootMyOUYA" apk on it, all went fine. I decided to put Xposed Framework on it, fine, Mod Collection, fine.
I did a Factory Reset just to get a clean slate, I loaded the OUYA back up and logged into my account. I went back into recovery, wiped Cache & Dalvik, flashed StockPlus. It was SUPER delayed and laggy trying to navigate menus. I tried doing a Factory Reset but it did nothing. I went back into recovery and did a data/factory reset, cache, dalvik wipe and now...
I get the OUYA splash screen, background, and then black screen. Nothing. How do I fix this?
If it helps at all, its still recognized under ADB.
EDIT:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse

Now no longer recognized under ADB... Any ideas?

If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4

nchantmnt said:
If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4
Click to expand...
Click to collapse
Yeah I wound up figuring it out. My derpderp-self forgot to put USB Debugging back on after I got everything set up. All is good now! :good:

I did something worng! Help!

I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!

apazrjon said:
I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!
Click to expand...
Click to collapse
i recommend a factory reset

If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.

Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!

apazrjon said:
Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
I would use command "adb shell pm list packages -f" that way you can see what apps are installed on the Fire TV and exact package name.....
Next uninstall with "adb uninstall com.amazon.app.name" (no directory or .apk specification needed)
I was playing with some Xposed mods yesterday and locked the fire TV up as well, uninstalling mod fixed it. (Xposed Additions Module)

apazrjon said:
I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.

roustabout said:
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.
Click to expand...
Click to collapse
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.

reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?

apazrjon said:
reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?
Click to expand...
Click to collapse
Did you already uninstall all Xposed modules and the Xposed framework ?

trying that next. It seems that adb will only work right after I reboot for some reason. Going to try again right now.

Just went ahead and got a $10 usb keyboard from walmart. Still couldn't get the home button to work for getting my into recovery. Then i decided to press shift + home and it worked. I don't know if it was the key combo or just good timing with the home button. Who knows. Back to factory now! Time to rebuild. Everything was set up perfect! Just couldn't leave well enough alone, lol! Thanks for all the help. My adb would only work for one time at a time and wouldn't uninstal anything. Cheers!

deleted content ..
sorry ., didn't notice I would have been duplicating what others already posted ....

rbox said:
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.
Click to expand...
Click to collapse
Sorry, meant "only command flag in ADB you might try before going for a full restore"
I thought the OPs core problem was that xposed was telling his system to use a nonexistent app as the launcher, and he wasn't able to get the app back in even for long enough to uninstall Xposed, reboot, and then uninstall XBMC.

Smithy71 said:
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
I've got a gray screen and can't get rid of it. I'm rooted and have elmerohueso's Launcher installed. All has been working perfect until the other night when I got a "low memory" pop up with a request to uninstall some apps. After that, the screen grayed and that was that. I've gotten to the“Update was not successful” screen but cannot get the menu to show up. I'm using a usb keyboard and have tried home, shift + home, and every other combo I can think of but the menu will not show up.
Anyone have another suggestion?

When you are on the update unsuccessful screen, press alt + sys rq + i to reboot back to the update screen again and then press home to bring up recovery menu. That's what I did on my keyboard

Smithy71 said:
If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
how to connect usb keyboard same time usb power? fire tv have no usb port

roy0175 said:
how to connect usb keyboard same time usb power? fire tv have no usb port
Click to expand...
Click to collapse
OTG Y Cable! It's an OTG cable that can also deliver power to the FireTV while you are using it with a mouse, keyboard, etc...

Bricked Fire TV (Gen 2 - V7.6.1.4)

Hi - I was installing some external memory, a 16gb Sandisk USB memory stick. The fire cube recognised it straight away & I proceeded to format it as ‘internal storage’. I got a msg to say that the format was complete. The TV screen then flashed & the next thing the fire cube re-booted & all I have is an Android Recovery screen. I’ve tried the mute + the volume down for 60 secs. None of the keys on the remote are doing anything nor are any of the buttons on the fire cube.
Can anybody help or is this bricked due to the software version?

All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.

Finnzz said:
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Click to expand...
Click to collapse
Hi - Yes, I’ve tried the mute & volume down button on the cube & held down for 60+ seconds. Nothing happened. It does seem to know when a key is pressed because if I press the right hand button with a circle on it, the ‘try again’ turns green. I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…

Clubcard said:
if I press the right hand button with a circle on it, the ‘try again’ turns green.
Click to expand...
Click to collapse
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Clubcard said:
I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Click to expand...
Click to collapse
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.

Functioner said:
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Click to expand...
Click to collapse
Hi - It’s unplugged as all the cube is doing is flashing blue all the time. When I apply power, I get the FireTv logo & then the Android recovery screen comes up. The cube doesn’t do anything. When the ‘try again‘ hightlights green, nothing I do will make it reboot. I’ve pressed every button on the remote & all the buttons on the cube.
The USB on the back is a micro USB & all I have is a USB keyboard which is why I had to connect it via the OTG I had. I’ve attached a photo. I do have a different OTG cable which has a micro USB input for a power supply. I’ve tried that & the keyboard has power but I still can’t select the factory reset..

I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.

Functioner said:
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
[/QUOTE
It’s very good of you to do that but it’s rather extreme. What if you brick yours?
Click to expand...
Click to collapse

My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.

Functioner said:
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Click to expand...
Click to collapse
Hi - Have you managed to sort anything out yet?

tengo el mismo caso lograste resolverlo?

Clubcard said:
Hi - Have you managed to sort anything out yet?
Click to expand...
Click to collapse
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.

Functioner said:
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Click to expand...
Click to collapse
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..

Clubcard said:
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Click to expand...
Click to collapse
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.

Functioner said:
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Click to expand...
Click to collapse
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..

Clubcard said:
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Click to expand...
Click to collapse
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?

Pro-me3us said:
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Click to expand...
Click to collapse
Hi - Will check that out later when I finish work. Thanks..

Clubcard said:
Hi - Will check that out later when I finish work. Thanks..
Click to expand...
Click to collapse
Hi - When I re-read your Instructions I couldn’t figure out how to do what you advised. Anyway I made what must have been my 10th phone call to Amazon. It went from them offering me 15% discount, then 20% & then 30%. I said no to all & finally after a lot of polite badgering, they have allowed to me buy a new one & I have an email from Amazon stating that I will get a full refund when my cube is delivered tomorrow

Clubcard said:
they have allowed to me buy a new one
Click to expand...
Click to collapse
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.

Pro-me3us said:
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Click to expand...
Click to collapse
Hi - Yes, it’s a 3rd Gen I’m getting. I had the downloader app & had kodi & few other apps on my 2nd Gen. Will this 3rd Gen not allow me to have any of these 3rd party apps on?

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.