Develop Bugs

Recovery Mode?

Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?

with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec

Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk

Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered

Check this command
adb devices
does it even show up on the list?

Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.

https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem

Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.

Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
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
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again

darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm

Can no longer connect via ADB

I had it all set up correctly and it worked fine both by USB and TCPIP. At some point in the last day or two this stopped working. I've done a complete reinstall of the SDK on my desktop and followed the instructions here https://devs.ouya.tv/developers/docs/setup
When I do adb devices I just get nothing. adb connect xx.xx.xx.xx gives nothing as well.
When I try to run adb from a terminal emulator on the unit I can start or stop the server but any other adb command results in a 'device not found' message. This message is preceded by some two or three digit word but since my TV crops the image I cannot tell what it says. so it is something like '##r: device not found'
Does anyone have any idea on what I need to do to get ADB working again?

Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2

TadeoNYC said:
Look in your system settings and make sure the ouya is still being recognized. I haven't used adb since the recent updates, but perhaps something changed causing your computer to no longer see it or caused the drivers to fail.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
There aren't any drivers involved here yet. Nothing happens at all when I plug the system in. No devices are detected, correctly or otherwise.
I'm starting to think the micro usb port is just physically broken. I've tried multiple cables, restarting. Connecting other android devices to my desktop which work fine.

could be the port. I have a heck of a time plugging mine in sometimes. it's like the hole in the casing is just a bit bigger than the actual plug, and I have to fumble around for it. I mostly leave the microusb connected all the time now.

Oh!lol.
That happened to me as well. The micro usb port is deeper than normal. My Samsung plugs did not work,I was able to use one from my Kodak pocket video cam.
Sent from my SCH-I535 using Tapatalk 2

Ok, so I'm trying to just adb tcpip working now to bypass the usb issue. I installed an SSH server and I'm getting this
[email protected]:/ $ adb kill-server
[email protected]:/ $ adb tcpip 5555
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $

Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.

beowolfschaefer said:
Found this
setprop service.adb.tcp.port 5555
stop adbd
start adbd
no luck, still can't connect.
Click to expand...
Click to collapse
If you have wireless adb enabled the way to control it so it does not shut down the micro usb port debugging , find the wireless adb .Apk here on xda in the nook color general section and install it then you will beable to open the app and toggle it back and forth to get micro usb debugging back.

My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?

Broomfundel said:
My Ouya has done the same thing. Its not hardware but factory reset does not seem to do anything. I have tried several cables , 2 pcs and its the same story all across. MTP connection works fine. ADB , the Ouya thinks its in ADB but nothing is recognized by the pc. Not failed driver install. As soon as you turn debugging on, the Ouya effectively vanishes from the pc.
Alas I did not get as far as putting a file manager on so can not side load anything. Without ADB as well. Well i'm screwed. Not keen on trying to send it back as already got hit for an extra £16.64 by customs, and with the launch the teams are going to be swamped.
I'm convinced its a file permission issue of some sort. But no CWM, ADB , File Manager or Recovery that I have manged to find yet. Well for now at least im stumpped.
Any ideas?
Click to expand...
Click to collapse
Did you set up adb over wireless?

tcollum said:
Did you set up adb over wireless?
Click to expand...
Click to collapse
I had done but. But it stopped working some time after, and I have not managed to get it going since. Would it stop wired at the same time? Even so would it not have been reset by the factory reset?
Either way, Ill set it with an ethernet cable and see if the flaky wifi was why adb over wifi did not work.
I'm sure a workable solution will turn up. Just disappointed.
Ill report back.
Thanks
Update: Thanks for your help. I tried over wifi and no joy. But ethernet is working. So just got to sort out the flakey wifi now.
Thanks again.

Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta

For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!

HaYNigloo said:
For anyone who committed to wireless ADB method, and currently stuck without ADB access or su priveledge, the Play Store has a wireless ADB app called "ADB Wireless (no-root)" by Sherdle. Sideload this puppy and you'll be able to toggle the wireless/wired ADB connection!
Click to expand...
Click to collapse
It's also available through the f-droid app.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Some people report having better luck connecting Wi-Fi with the native android settings found in the manage area.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My wifi works great. unless i try to login to google.

Look here: https://devs.ouya.tv/developers/docs/setup
They changed the device ID, you need to do step 5-6.
More info here: http://www.ouya.tv/devnews.html

[Q] Factory Reset Narfed su

I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.

vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.

JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse

Hard boot the OUYA and laptop, adb via USB seems to work again.

So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta

no micro-usb connection after tcpip setup

I have a KS ouya. i have rooted it before, but the stupid auto updates got the best of me a couple times.
i've done it the same thing every time-
connect to micro-usb, turn it on, install the drivers, get adb working, set up the tcpip, install superuser, lucky patcher, etc.
this time though, after I set up the tcpip, it will NOT connect via usb again. windows xp no longer recognizes it.
no luck even after tcpip disconnect, adb usb.
any insight?

ArdDarvis said:
I have a KS ouya. i have rooted it before, but the stupid auto updates got the best of me a couple times.
i've done it the same thing every time-
connect to micro-usb, turn it on, install the drivers, get adb working, set up the tcpip, install superuser, lucky patcher, etc.
this time though, after I set up the tcpip, it will NOT connect via usb again. windows xp no longer recognizes it.
no luck even after tcpip disconnect, adb usb.
any insight?
Click to expand...
Click to collapse
You could try flashing a new rom or maybe a factory reset (amusing you are backed up).

i tried a couple things. I pulled the build.prop again and removed the tcpip entry, then pushed it back on. even after that I can still connect tcpip.
i also tried a factory reset. everything LOOKS factory, but i can still connect through tcpip and NOT through usb at all.
I have no idea wtf i'm going to do, but i'm going to figure it out and do it.

Install the app Wireless adb. It has resolved this issue for most people.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
Wireless adb.
Click to expand...
Click to collapse
thank you very very much. my problem was that I enabled wireless adb, then rooted. when it didn't connect via wire, I factory reset it. this unrooted it, but left me with only wireless adb. I can't do shell things through wireless adb.
SO, I found adbwireless by Sherdle, which is no-root. I haven't dedicated to using it, but it looks promising. I'll post updates. thank you again for your help. I kinda feel like Stevie Wonder in an obstacle course.

ArdDarvis said:
thank you very very much. my problem was that I enabled wireless adb, then rooted. when it didn't connect via wire, I factory reset it. this unrooted it, but left me with only wireless adb. I can't do shell things through wireless adb.
SO, I found adbwireless by Sherdle, which is no-root. I haven't dedicated to using it, but it looks promising. I'll post updates. thank you again for your help. I kinda feel like Stevie Wonder in an obstacle course.
Click to expand...
Click to collapse
I hope it works out. After seeing all of the headaches people have had with wireless adb the tuts should have a warning added.
Sent from my GT-P3113 using Tapatalk 4 Beta

well, no bueno.
its totally my fault, but i think the factory reset didn't touch the build.prop, but it DID unroot me. so now i'm stuck without root and only wireless adb.
when I wireless adb shell, su. it says I don't have permission. is this because I'm using wireless? I've used the su command to root the device, why no permission now?

Download the wireless adb apk onto your ouya , it can be found here on xda . Then open the wireless adb app on your Ouya and use the trackpad on the controller to toggle wireless adb on and off.

27scoob said:
Download the wireless adb apk onto your ouya , it can be found here on xda . Then open the wireless adb app on your Ouya and use the trackpad on the controller to toggle wireless adb on and off.
Click to expand...
Click to collapse
thank you for the help. i downloaded the apk, (its called adbWireless?) and installed it, but it says "kernel does not have all the necessary features for running this app. you need rooted phone". bummer.
I'm sure i sound like a complete newb; this is the first time i've ever joined a tech forum and had to write down what is happening. talking about it is easy, typing it is a little different.
i can pull the build.prop and at the bottom is the wireless code i put in. BUT, i can't push it back on because I need to change the permissions first. BUT to change permissions, i need su to work. to push su to /system/xbin, i need to change permissions.

I think I have the same problem :s
My computer don't recognize via USB, and I think is after enable tcpip ...( for wireless connection adb )
I update my ouya, lost my root and can't connect it ...
Do you find the solution ?
Thx
Edit : If I look the build.prop, I don't see the line for adb by tcp, so not sure it's my problem

Ok, i got it. and i feel great about it.
when setting up the drivers, we edited the android_winusb.inf to say
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
(that underlined part is the Hardware ID for the ouya in normal operation)
then we point the new hardware to the driver, then in terminal
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
and thats all well and good, but **** hits the fan sometimes.
and when it does, recovery mode is your friend.
if you lost wired adb due to enabling wireless adb then lost su, RECOVERY ENABLES WIRED ADB! so plug it in! it'll connect in recovery
2 ways-
1) "adb reboot recovery" (over wired or wireless connection), then use a USB keyboard and press the home key, and boom, theres recovery
2) plug in a USB keyboard, restart the ouya, when its booting up, push "Alt + PrntScrn + i" a lot, that'll eventually put you in recovery.
from recovery, we can sideload the most current OTA again via adb, BUT! the ouya changes hardware ID's when it is in recovery mode!
so, you have to go into the device manager, right click the device without the driver, go to details, then to hardware ID. you'll see that it is changed. so in the android_usb.inf, change it to say %CompositeAdbInterface% = USB_Install, USB\WHATEVER_HARDWARE_ID_IS (not REV)
once its changed, go into the device manager, right click the device, point it to the driver, then
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
and, there it is, wired adb capabilities in recovery so you can sideload in a OTA.
CWM recovery also changes the Hardware ID, so, after you do THAT, you gotta get the new hardware id again.
idk if its right, but it works- i just put the Hardware IDs for the different modes in the android_winusb.inf separated by commas. adb connects in ALL modes, which is WAY better than having to copy the IDs everytime and reload them.
hope it helps. i kinda feel like i know what i'm talking about a little, so, i'll try to help as much as i can.

billouetaudrey said:
I think I have the same problem :s
My computer don't recognize via USB, and I think is after enable tcpip ...( for wireless connection adb )
I update my ouya, lost my root and can't connect it ...
Do you find the solution ?
Thx
Edit : If I look the build.prop, I don't see the line for adb by tcp, so not sure it's my problem
Click to expand...
Click to collapse
yeah, it seems enabling tcpip disables wired connection.
idk about your build.prop, but i would suggest sideloading the most current OTA over in recovery. really thats all i can suggest. it overwrites the build.prop.
wireless adb seems to destroy all my dreams at once.

Constand rebooting to BootMenu

Hi Guys,
I have followed all steps to install bootmenu but when I restarted the FireTV, I was unable to boot kernal and it would reboot itself over and over. I can get into CWM v6.0.5.1.4a but I no longer have pre-root 51.1.4.0 on sdcard as I foolishly deleted it prior. Is there anyway I can flash back to pre-rooted 51.1.4.0 to start the process over?
Any help is much appreciated.

mozzer27 said:
Hi Guys,
I have followed all steps to install bootmenu but when I restarted the FireTV, I was unable to boot kernal and it would reboot itself over and over. I can get into CWM v6.0.5.1.4a but I no longer have pre-root 51.1.4.0 on sdcard as I foolishly deleted it prior. Is there anyway I can flash back to pre-rooted 51.1.4.0 to start the process over?
Any help is much appreciated.
Click to expand...
Click to collapse
once in recovery you can use ADB to push files to the FTV from your PC

I tried doing that but I am unable to connect through ADB. I tried adb connect (original firetv IP) and also adb connect (cwm IP address shown) but nothing.
Am I doing something wrong when trying to connect? Thank you for your response.

Can anyone please tell me my firetv isn't a complete loss?

mozzer27 said:
Can anyone please tell me my firetv isn't a complete loss?
Click to expand...
Click to collapse
Ive always done adb over network but im pretty sure you can connect a mac or pc to it via Usb.
You should be able to adb over network though. I assume you tried resetting your router and if your computer is wifi, i find toggling between 2.4 and 5ghz sometimes helps

KLit75 said:
Ive always done adb over network but im pretty sure you can connect a mac or pc to it via Usb.
You should be able to adb over network though. I assume you tried resetting your router and if your computer is wifi, i find toggling between 2.4 and 5ghz sometimes helps
Click to expand...
Click to collapse
I have been able to connect through ADB fine when I was in the FireTV OS now that I am in recovery through CWM I cannot connect. I have tried both the IP address of the FireTV and the one shown on CWM neither is working. I also do not see any information when typing adb devices in command prompt.
Have you connected to ADB through CWM recovery previously? I have tried a hard reset on the router and modem but still no luck. Although my router is capable of 2.4 and 5, my laptop is not. If I could just push the file through, I could start the process over but I seem to have hit a road block.

mozzer27 said:
I have been able to connect through ADB fine when I was in the FireTV OS now that I am in recovery through CWM I cannot connect. I have tried both the IP address of the FireTV and the one shown on CWM neither is working. I also do not see any information when typing adb devices in command prompt.
Have you connected to ADB through CWM recovery previously? I have tried a hard reset on the router and modem but still no luck. Although my router is capable of 2.4 and 5, my laptop is not. If I could just push the file through, I could start the process over but I seem to have hit a road block.
Click to expand...
Click to collapse
I'm more or less just throwing ideas you might've tried already...since we don't have a ton of development I don't use cwm for much. I know twrp has an adb sideload option that I've used. Also used the mount feature--I think to get zip files to the sdcard. Not sure if cwm has those options but pretty sure it does.
These aren't so much answers as they're things I'd try if in the same boat. Maybe explore that unless someone has a more concrete solution. Good luck.