Is it possible to port another version of recovery (tactil maybe)? i think so that is the problem....
I just rooted my Ouya using WondrrEkin's "RootMyOuya" here on xda/ouya/development and it installed superuser. I then install busybox. Do I stll need to use adb to install CWM? The reason I ask is my pc is in a different room than by TV, there is about 40 feet seperating them. Wish I had a laptop!
Last edited:
the recovery has some how been removed from my Ouya how can i reinstall it if i do not have a recovery?
I tried with another TV and works 
thanks for the advice I installed CWM and a rom. Everything looks correct
thanks for the advice I installed CWM and a rom. Everything looks correct I am trying to use the one click style method on a mac osX 10.8.4. My OUYA is rooted with SU installed, the mac and OUYA are on the same network. Let me know what all do i need? and what am i doing wrong? i keep getting /adb no such file or directory found when i run the /InstallOuyaCWMRecovery.sh in terminal. Thanks a lot.
I was having a lot of bother getting anything done using win xp but after getting a hold of a win7 machine I got this installed no bother
but I'm puzzled , the reason I installed it was to make a backup of my ouya before flashing a custom rom but I dont see that option on the menu
but I'm puzzled , the reason I installed it was to make a backup of my ouya before flashing a custom rom but I dont see that option on the menu
May have been answered before, but do you have to do this every time you want to get into recovery or does this install recovery and give you a way to boot into it?
I'm stumped :crying: I used the automatic method to install CWM, and it worked fine. The problem is when I boot into recovery and press home, the only options I see are Reboot System, Add update from ADB, Wipe data/factory reset, wipe cache partition. What did I do wrong, and how do I fix it? I've been through all the threads for about 2 hours now and haven't found an answer. I would try to manually install, but I get no video, and it doesn't recognize the fastboot drivers. I've tried everything on that end too and haven't come up with anything.
Thanks for any help you can give!
**UPDATE** - I finally stumbled upon a fix for my problem. For anyone else getting the (!) when you boot into recovery, and have limited options, follow the steps in this thread exactly and you will be up and running in no time. http://forum.xda-developers.com/showthread.php?p=44635711
Thanks for any help you can give!
**UPDATE** - I finally stumbled upon a fix for my problem. For anyone else getting the (!) when you boot into recovery, and have limited options, follow the steps in this thread exactly and you will be up and running in no time. http://forum.xda-developers.com/showthread.php?p=44635711
Last edited:
I got another OUYA for a friend and this script no longer works. Not sure if it's with the newest firmware or what. I just keep getting "device not found".
My OUYA shows up in windows system properties but I cannot connect to it with the program or adb/fastboot
Please help. None of the drivers install either. Is this something they broke in the system update? Root however still works fine.
My OUYA shows up in windows system properties but I cannot connect to it with the program or adb/fastboot
Please help. None of the drivers install either. Is this something they broke in the system update? Root however still works fine.
Last edited:
How do I turn off wireless ADB? I searched but couldn't find an answer. I tried "adb connect ipaddress" but then it just says:
>adb connect 192.168.1.29
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.29:5555
I installed fine on the latest version of Ouya with my laptop OS Windows 8 Pro 64 bit.
I bought the Ouya from a guy on ebay and he tried to root it but couldn't figure it out but after hours and hours or trial and error I figured it out.
First, make sure you download the latest Andrown SDK installed:
1. http://developer.android.com/sdk/index.html#download > Developer Tools > Download > Click checkbox > select 32 or 64 bit.
Note: Make sure you install all of the extras and for best results I would install every package.
Note: For Windows 8 you need to disable driver signing. Google it, it's easy.
2. Make sure on your Ouya that you have USB DEBUGGING check off and turned ON.
3. You should at this point have a device in Device Manager under Portable Devices called Ouya with no exclamation point and also under USB Composite Devices you should see another deivce with an exclamation point. The one with the exclamation point is the one you want to manually install the drivers to.
4. I can't remember which package but one of these worked for me. Just search XDA for either:
1. OUYA the Wiz Recovery 1.0 - NOTE: This is the only one that worked for installing recovery.
https://www.dropbox.com/s/ovxni3vrifdb77d/OUYA_TheWiz_Recovery_1.0 (1).zip
2. OneClickOuyaRecovery
3. Ouya Safe Recovery Installer
4. Ouya Toolbox 1.1.2
Hopefully this helps, let me know if you have any questions. Thanks.
Last edited:
THIS was it! In Device Manager I was trying to install the drivers over: Portable Devices > OUYA Console, and I needed to install the driver over: Android Phone > Android Composite ADB Interface.
It actually never had an exclamation point that's how I missed it, but I installed the driver over it anyway and it worked. Thank you! :good:
edit: I don't even have the Android SDK installed, I never bothered with all that. I placed into USB debugging like any other Android device, replaced the driver per your instructions and ADB/OuyaToolbox/etc all work flawlessly.
Last edited:
Can anyone provide a stock boot.img ?? CWM worked great and i flashed cm10.1 to it but i've forgotten to save the boot.img.
Edit: http://forum.xda-developers.com/showthread.php?t=2266629&page=1 found it in the zip of the OTA
Edit: http://forum.xda-developers.com/showthread.php?t=2266629&page=1 found it in the zip of the OTA
Last edited:
What does CM10.1 os offer that stock os does not? Just curious?
in the beginning it was easier to get the playstore working and such things as a console with su.
new problem: i can't flash the right boot.img. i think this is because the device isn't recognized right by my system and i don't know why. the only thing i get running is cwm and the only device adb it's listing is "015d483b6307fa1a recovery". after "adb reboot bootloader" i get a unknown device which i can't install the drivers from cwm recovery to. somewhere else i've read "adb reboot recovery" should solve this problem but it doesn't. any suggestions?
as long as i get into adb a plane ouya backup would be nice (i got none) or another running backup without your userdata
new problem: i can't flash the right boot.img. i think this is because the device isn't recognized right by my system and i don't know why. the only thing i get running is cwm and the only device adb it's listing is "015d483b6307fa1a recovery". after "adb reboot bootloader" i get a unknown device which i can't install the drivers from cwm recovery to. somewhere else i've read "adb reboot recovery" should solve this problem but it doesn't. any suggestions?
as long as i get into adb a plane ouya backup would be nice (i got none) or another running backup without your userdata
Last edited:
found something that might be of use to those who are getting issues with the cwm recovery being pink. It would appear that cwm recovery mode isnt entirely compatible with certain types of hdmi components. I have a hdmi switch that I use to connect the ouya as well as other devices.
It seems that booting into The OS works absolutely fine through the hdmi switch. It even switches to the device when it starts up.
However the picture becomes squashed to half of its width and magenta coloured when I reboot to recovery while its connected to the tv via the hdmi switch.
I don't believe the hardware would be this choosey. It has to be something about the display drivers for CWM not being compatible with certain hdmi devices. Can anyone investigate this further?
It seems that booting into The OS works absolutely fine through the hdmi switch. It even switches to the device when it starts up.
However the picture becomes squashed to half of its width and magenta coloured when I reboot to recovery while its connected to the tv via the hdmi switch.
I don't believe the hardware would be this choosey. It has to be something about the display drivers for CWM not being compatible with certain hdmi devices. Can anyone investigate this further?
How do you navigate? If it requires extra devices such as USB keyboard or something how do you uninstall?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone