Develop Bugs

[Q] manually reinstall the OTA update.zip?

Here's my situation and why I ask, everything was up and running fine. Side loaded some apps and had wireless adb working. I got the OTA update the other day and it wiped out some system side loaded apks. So I got everything back the way I want it (same as the first time...), still working fine. Then wanted to get wireless adb woking again so just push an edited copy of build.prop I had from before the update. Since then I cannot get any video output and the control will not pair (all lights just blink a few times). tried power cycling a few times, different hdmi cable, ect...nothing. The good news is that I can still connect with adb over usb. Since this issue started when I pushed the old build.prop I tried pushing the correct build.prop but still no luck.
Is there any way to manually re-run the OTA update? maybe push it to a directory and reboot? press and hold power for 30 sec?... Or any other ideas?

So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...

Here's my best instructions on how to fly blind on this, good luck...
1. unplug the console
2. plug it in and turn it on, the light will come on. make sure adb works
3. adb reboot recovery. the light should flash
4. adb will not work at this point, you have to put it in sideload mode first. on a usb keyboard press the "home" key, wait 2 seconds, press the down key, then press enter.
5. if you have a plug in sound you should hear it now, and "adb devices" should return the device id and say "sideload" beside it.
6. type "adb sideload <ota.zip path>" and hit enter.
7. wait plenty long. like a really long time just to make sure. like 10 minutes at least, even though it should only take 2.
8. Once it's had enough time to complete the flash, you can pull the power plug, plug it back in and power on.
again, good luck.

professorpoptart said:
So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...
Click to expand...
Click to collapse
Check out this thread on the ouya dev forums that says how to boot into recovery . I think you just have to hold down print screen as ouya starts but not sure
forums(dot)ouya(dot)tv/discussion/1380/recovery-mode
Also the reason why skywalkers method night not work is because ouya changes the default key layout ("Generic.kl" in /system/usr/keylayout/) to map the home button on keyboards to "move_home" which navigates to the top of a page rather than the android home function. In order to fix this, you can pull the kl file using adb and edit it and put it back or copy the kl from another android device. The android command is "HOME" for most devices but might be "HOME ALT" for ouya because they changed it to work with a double press of the button.
I hope this helps sorry for the weird link I never post on xda and don't have permission to post links...

Thanks for the extra info, i just posted what worked for me

after looking at post at http://forums.ouya.tv/discussion/1380/recovery-mode it sounds like the device might already be in recovery mode. they described it as sometimes having the red triangle but most of the time a just black screen. Sounds like mine, at first I would get no inuput on the tv, now I'm not getting no input on the tv, just a blank black screen. I tried just hitting home to see if a menu would come up but it didn't. tried the sysrc+i for a minute and then home again... just a black screen still. O well were would the fun be if it just worked! lol. I will have to play with it more after work. thanks for the tips,
*should the num lock led work? I used an old dell usb keyboard but num and caps lock leds didn't work, so not sure if the board was working at all...

It Works!
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!

Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.

professorpoptart said:
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!
Click to expand...
Click to collapse
Sick. I'm glad that worked for you.. another tip if you want to use a keyboard with your ouya more often. on ouya the "HOME" function also opens the menu (they did this so that they could have one button do both(tap/double tap)) if you want the actual "HOME" function, you need to remap to kl to "HOME ALT".

sonofskywalker3 said:
Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.
Click to expand...
Click to collapse
Sure hit me up when you're ready. I've been following the other CWM thread...

Thanks for the information I used a few days ago to reinstall OTA because i had problems with android drivers.

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

[Q] How do I force Ouya into Recovery? No ADB Access

How can I force my Ouya into Recovery? I have no ADB access.
I have this problem here...
http://forum.xda-developers.com/showpost.php?p=43989508&postcount=145
I tried the sysrq key combination but it just locks the ouya up.

That is one of the main drawbacks of ouya - you just can't.
If you bricked it it stays bricked, at least to the moment when ouya releases sbk.
Even if they release firmware update with recovery you have no way of applying it so nvflash seems to be the only option for you.
Sorry about your ouya. You can of course try contacting support and ask for help, but as you said sysrq is not working so it might be difficult.
Sent from my iPad using Tapatalk - now Free

i wonder if it is possible to connect your device as usb-storage-device.
maybe you are able to push the ota to your device and make it update on first boot. but i guess we're unable to push a file via mtp into /cache where the update.zip is supposed to be found
you don't have any possibility to get into settings e.g.?
i still refuse to believe that threre is simply no way of fixing it you it hangs on updater.
atm i'm at work for at least 6 hours from now on but as soon as i get home i will try to "softbrick" my ouya (keeping safe recovery as backup) and try to get to the point where you are. from there on it's trial and error for me
i'll tell you if i find some way to get to recovery or fixing this problem without using sysrq

What do you mean it locks it up?
I have had it take a few tries to get it to work. I also had to hit the home key to get the menu to show up.
One way that seems to work often is powering up cold (after pulling the power) with the USB kb plugged in and hitting the alt sys-req I as the first ouya boot animation starts to come on the screen.

HT123 said:
I also had to hit the home key to get the menu to show up.
Click to expand...
Click to collapse
VERY important to remember, VERY easy to forget.

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

Have I bricked my FTV 4K stick beyond repair?

Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks

you need a usb keyboard and then you need to press a combination shown on youtube: , Don't be afraid it is very hard to do it but i can confirm it works 100% for sure!! The timing for holding the key press is all that matters to be successfully...
Try different timings if it's not working on the first run but you need then to hold the buttons for very long time until your fingers feel dead....
..im not sure if adb is working in "safe mode" you need to test that. If yes - you could use "adb reboot recovery".
2. you need to reflash Magisk in core mode.

Aq
dougie175 said:
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
Click to expand...
Click to collapse
You haven't killed your stick, install fastboot drivers and app.
Connect your stick to your pc via usb.
Enter
Code:
fastboot devices
when you see black screen with amazon logo, it should be inside fastboot mode
(If somehow you flashed update to boot.img as written in the guide)
If you see the stick in fastboot mode,
Pull twrp from kamakiri.zip
Place it in fastboot folder
Enter
Code:
fastboot flash boot boot.img
(boot.img or whatever the name of your twrp image)
Code:
fastboot reboot recovery
It should work, if not you can use shorting method again.

Thanks very much both, I will have a play around this evening when I get home from work and the kids are in bed, hopefully with the info above I can get back to recovery again.

Thanks for the help gents, in the end I had to do the shorting method to get the stick to do anything. It took about 6 attempts before kamakiri script even registered it as anything being plugged in, it just kept saying wait for boot.
Once it realised the stick was present and shorted I was away though, I have ended up having to factory reset and wipe everything so will need to start again with it but I am just pleased I don’t need to shell out again for a new stick.
Thanks again for your help