yashsingh1/xdaforums huggingface dataset:
[Ouya Android Development] mybook4:
Probably not the issue, but wanted to rule it out anyway. What's the md5 hash of the .img. I got c6b37906f280b16cd200503c3cde6dfb
[Ouya Android Development] professorpoptart:
got it working, edited my previous post... basically tried a third, lol
[Ouya Android Development] mybook4:
Crazy driver / edid issues maybe? Who knows. I'm glad you got it working though.
[Ouya Android Development] FrostyWolf:
I was also unable to get video after running fastboot unless I had the HDMI plugged in prior to issuing the command.
[Ouya Android Development] mybook4:
Ohhhhhh. I keep HDMI plugged in the entire time. Maybe that's the issue. Professorpoptarts, we're you plugged into HDMI at all times?
[Ouya Android Development] professorpoptart:
When it wasnt working yes, had everything connected, then powered up, then fastbooted. Even tried unplugging and plughing back in the hdmi a few times to try and get it to come on. However since I got it working I have not gad the issue (knock on wood)
[Ouya Android Development] No4g4Me:
is there a custom kernel up for this device yet? I havent seen one. :(
[Ouya Android Development] sonofskywalker3:
Kernel source was released 4 days ago, it may take some time.

However, I'm currently working on porting Cyanogenmod 10 from source, professorpoptart is working on porting an aosp rom from the HTC One X+, and I'm probably going to release a "Custom ROM" tonight that's just an easy flash to add a bunch of extra functionality. So no kernels yet, but Roms should start popping up soon.
[Ouya Android Development] FrostyF7:
I love you all!
[Ouya Android Development] slack04:
Hooray! I'm taking my ouya off craigslist! I was beginning to think nobody was going to develop for this box! I can't wait to start sending donations! (soon, life is expensive these days....).
[Ouya Android Development] Kaos2K:
Try another TV
[Ouya Android Development] emulation:
Is it possible to port another version of recovery (tactil maybe)? i think so that is the problem....
[Ouya Android Development] lartomar2002:
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!
[Ouya Android Development] afrome:
the recovery has some how been removed from my Ouya how can i reinstall it if i do not have a recovery?
[Ouya Android Development] emulation:
I tried with another TV and works :) thanks for the advice :) I installed CWM and a rom. Everything looks correct :)
[Ouya Android Development] sagarpruthi:
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.
[Ouya Android Development] Petesky:
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
[Ouya Android Development] FatalIll:
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?
[Ouya Android Development] CheeseMcGee:
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://xdaforums.com/showthread.php?p=44635711
[Ouya Android Development] marlon.jose:
Please keep going

.....
[Ouya Android Development] ph1nn:
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.
[Ouya Android Development] zanzee:
Make sure wireless ADB is off.
[Ouya Android Development] ph1nn:
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
[Ouya Android Development] BlissfulBeast:
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.
[Ouya Android Development] ph1nn:
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.
[Ouya Android Development] Klindworth:
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://xdaforums.com/showthread.php?t=2266629&page=1 found it in the zip of the OTA
[Ouya Android Development] lartomar2002:
What does CM10.1 os offer that stock os does not? Just curious?
[Ouya Android Development] Klindworth:
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
[Ouya Android Development] zondajag:
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?
[Ouya Android Development] deathblade:
How do you navigate? If it requires extra devices such as USB keyboard or something how do you uninstall?
[Ouya Android Development] billouetaudrey:
Need usb keyboard

Envoyé depuis mon Galaxy Nexus avec Tapatalk 4
[Ouya Android Development] zondajag:
So can anyone answer any of my questions/queries about this pink recovery issue?
[Ouya Android Development] HT123:
Pink recovery is a driver/ TV issue. The Ouya is not the only device that has the problem. here is a snippet from another site concerning the issue.

One has to remember that DVI/HDMI is capable of carrying two types of Colourspaces: RGB and YPrPb. Unless modified, the PC will always output RGB.I bet your HDTV is incomptiable with RGB Colourspace (ie. it's designed for video Colourspace, YPrPb).
[Ouya Android Development] zondajag:
The odd thing is the TV supports it fine. Its just when it goes through the HDMI switch I have the recovery goes all pink and squashed whereas Android boots in fine. Its definitely something to do with the recovery partition displaying images in a different way. Different drivers perhaps?
[Ouya Android Development] Hal9k+1:
CWM opens the framebuffer device directly, so I don't believe it's tapping in to an Android graphics library. The issue looks to be a race condition as I see it, because my outcome with this monitor is based on whether it's in sleep mode. I've decided to attempt compilation of the Recovery executable as part of my project on the General forum. Once I get through that, then I'll try a couple of workaround ideas: add delay(s) in key areas of the graphics initialization, and/or shut down the first graphics initialization (priming the pump) and bring it back up a moment later.
[Ouya Android Development] zondajag:
Is that something professorpoptart could help with at all? Who compiled this CWM? was it the original poster?
[Ouya Android Development] Hal9k+1:
Kulve set me straight on this -- no change to the CWM application should be needed -- only the kernel. Please try out the updated Recovery image on my Ouya General forum ([Recovery] [ROM Booting] ...) to see if your pink screen goes away as well. Thanks!
[Ouya Android Development] zondajag:
Um any way of getting instructions on how to safely implement your new updated version of the CWM recovery?
[Ouya Android Development] Beukhof1:
Hi all im having the following problem:

Adding Ouya USB Vendor ID for adb
The network path was not found.
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

.
.
Pushing recovery img to the internal sdcard
error: device not found
.
.
Pushing script to /data/local/tmp
error: device not found
.
.
Running script to flash CWM Recovery
error: device not found
error: device not found
.
.
Rebooting into CWM Recovery
error: device not found
.
.
You should be at CWM recovery now! Press enter to finish
Press any key to continue . . .
[Ouya Android Development] Re-Mi:
Jup me too... i had similar things with my first one but my second one seems to be "bricked" this way.

But i'm not giving up hope, as long as my laptop sees the ouya (this time it's max 10 seconds) i think there is still a chance to recover it.

But if anyone got a solution it would be great
[Ouya Android Development] TadeoNYC:
You don't have the correct drivers. Install the Nexus Root toolkit http://www.wugfresh.com and use the driver install utilities to clean up your computer and install new ones.
[Ouya Android Development] domagoj_zg:
Ok, someone should really address this: it doesn't work. I tried all combination of drivers,reinstalls etc.. Did anybody really solve problem Beukhof1 and others have?
[Ouya Android Development] zondajag:
I had a similar problem when I tried. You need to be more creative. Perhaps have a look at device manager and see what the device might have been mistaken as. I know for me I had to force install one of the bundled drivers manually but as to which one I cant be exactly sure right now.
[Ouya Android Development] Ipse_Tase:
If you're running Windoze, force it to get the driver from $HOME$/OneClickOuyaRecovery\Windows.

It does take a few attempts to get adb working, unlike other Android devices I fiddled with.

If everything else fails, you can install the whole Android SDK and take it from there. This script shortcut did it from me after 3-4 attempts. Just make sure you have the right paths and permissions to create subfolders. Open the bat script to see what MIGHT go wrong.
[Ouya Android Development] domagoj_zg:
I think its just guessing wildly. Either you have drivers or you don't (for Windows 7 for instance). SDK is totally irrelevant. All people claiming to do it after latest firmware update came to it somewhat foggy. Cannot remember where they found drivers, pressing buttons 4-5 times, installing some software... Bah. If someone really knows what drivers work that's the only important thing. Recovery script works if backdoor isn't patched in firmware and i think it isn't.
[Ouya Android Development] TadeoNYC:
I first rooted my OUYA in May when it was a total crapshoot and got it up and working with Samsung adb drivers. The toolkit from Wugfresh is as thorough as it gets. You may need to use the utility app to strip out all related drivers and then install new ones, being sure to manually select the proper one at every step. You need MTP drivers for it to be seen as a media player, and then separate adb and fastboot drivers for an adb composite device. It should be listed twice in device manager.
[Ouya Android Development] Ipse_Tase:
You missed the part where I was mentioning what folder I had to point Windoze to install drivers from - and it worked afterwards.

So "you don't" if they don't get installed...or else "you do" :)

Let's face it: the Ouya community is infinitely small compared to other Android devices - you will never find the 4000 pages threads from the Nexus 4 forum. Therefore the tools are bit rudimentary and I for one am grateful that people even spend time to cook a ROM or CWM. I would not have bought the device otherwise.

There seems to be a lukewarm sentiment towards the product, so I'm not too hopeful the situation will improve. Too bad, it works fine for my needs (XBMC/Netflix/YouTube).
[Ouya Android Development] domagoj_zg:
I got fresh W7 install this time BTW and no success. Ouya is installed as two functions in device manager, tried restarting .bat 10 times, no effect, still "device not found" message.:mad:

Duh, finally.

Rooted it with this method: http://xdaforums.com/showthread.php?t=2387507

and then installed recovery with this: http://ouyaforum.com/showthread.php?5159-OUYA-One-Click-CWM-Recovery

Thanks everybody for effort none the less.
[Ouya Android Development] :
I get "error: closed" when i try to adb push. Any suggestions?

Even when trying the autoatic script i get this:

[/URL][/IMG]

I should say that i can sideload things just fine.
[Ouya Android Development] csosbee:
According to that screenshot, your OUYA is in sideload mode when you are trying to adb push to it. The image should show a serial number and "device" in order for you to be able to adb push. Hope that gives a hint as to what's going on.
[Ouya Android Development] :
Thx for answer!

My ouya is bricked it only comes to the ouya"!" screen, and the only option to even get the computer to recognize the ouya is "sideload through ADB" option after bringing upp the menu through the alt+sysreq+i hack. and trying to sideload the latest ota firmware just lets me adb it over and after scanning the file it says cancelled. any thoughts?
[Ouya Android Development] nchantmnt:
Try Adb reboot bootloader and flash cwm.

Gesendet von meinem HTC One X+ mit Tapatalk
[Ouya Android Development] cronikman84:
i also have the same problem, My OUYA is also bricked after messing with the build.prop yesterday and all i get is a black scree when i start the OUYA, nothing boots or loads, if i do the alt+sysreq+i combination it gets me to the "stock OUYA recovery" where i can scroll down to "sideload through ADB" to get my pc to recognize the OUYA and when i enter the command "adb devices" it shows my device# xxxxxxxxx Host:(, and i don't know what to do here, i feel like a noob right now:o...

.........................................................................................Edit.................................................................................................................

Never Mind, i got the OUYA un-bricked and it's runing again... thank god :) i was able to get the sideload to work and and update installed, when i was adb'ing my pc saw my console but as a HOST not as SIDELOAD, so once i got my PC to see my OUYA as SIDELOAD and not HOST the sideloaded update went threw and installed no problem...
[Ouya Android Development] cronikman84:
he can't "Adb reboot bootloader and flash cwm"...his console is soft bricked and even if he runs the command it won't work at all and it will give him and error, it won't take the command cause he can only command a sideload if you get what i mean?...
[Ouya Android Development] tangcla:
Is 6.0.3.2 the latest recovery available for the Ouya?
[Ouya Android Development] makavelitha:
I need help!

CWM Recovery is not working for my Ouya, i've tried it with the "OneClickOuyaRecovery" package via Windows 7 x64 and i've also tried installing it from the Mod Collection App, but all what i get is the "OUYA "!"" Screen.

But my Ouya isn't bricked, after a reboot my Ouya works like before, but without CWM...
[Ouya Android Development] realhuh:
.. that indicate cwm is not install .. my sugestion .. install mod collection with proper step .. and install cwm from there .. that should do .. cheers
[Ouya Android Development] makavelitha:
thx for your answer, but i've already done this and it still doesn't work...

I've copied the "OneClickOuyaRecovery.zip" file to "sdcard/download" and installed CWM Recovery from the latest Mod Collection 5.1, after the installation my Ouya reboots and shows me the "OUYA "!"" screen.

And when i reboot my ouya, it works like before, but still without CWM...

btw, i've installed the Mod Collection weeks ago with the One Click Ouya Root Files!
[Ouya Android Development] cronikman84:
Do you have a keyboard connected to the OUYA before trying to get into CWM?
[Ouya Android Development] adfurgerson:
I use this app to get into recovery.

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
[Ouya Android Development] makavelitha:
Ok, thanks, problem solved!

The Problem was my Mele F10 Pro Air Mouse, i thought i can use it as a keyboard, but as it seems, it is not recognized as a proper keyboard..

Now i've connected a Logitech K400 and now CWM works!

Thanks for your help ppl :)
[Ouya Android Development] dom2570:
I think I may have bricked my OUYA. When I turn the device on all I get is an endless "Unforunately, OUYA Framework has stopped." I have tried ./adb reboot, but apparently I have lost the ability to establish a connection with the OUYA. Any ideas?
[Ouya Android Development] realhuh:
.. if you manage to get into CWM .. you can flash stock rom .. or factory reset from ouya recovery .. tutorial in here

.. good luck .. :D
[Ouya Android Development] cronikman84:
where you trying to install something, like a mod?
[Ouya Android Development] dom2570:
I had been messing around with a few different mods. I wanted to go back to stock and think I accidentally dirty flashed the stock rom.
[Ouya Android Development] Haxxa:
Thank You worked great on my new Ouya :)
[Ouya Android Development] Ticiano:
Hi guys. I'm just trying to be safe before start modifying this thing, because the things here are a little more risky than with other devices I use. I'd just like to know how to revert completely back to stock after going through CWM and CM tests, just in case. With my nexus devices all I have to do is to flash a stock firmware via fastbook and any changes made by customizations will be reverted. Is it possible to do something like this with this device?
[Ouya Android Development] Eyedoctor2:
External SD Card Nandroid

Is there any way to use CWM at present to make a nandroid on an external sd card? My Ouya is too full to backup to the internal card.

Thanks!
[Ouya Android Development] mrdegriz:
Hi All, I get the below when trying this

Remounting system partition to prevent etc etc

Unknown option -- o

followed by a bunch of unknown id

Any ideas? Cant believe Ive fallen at the 1st hurdle :/
[Ouya Android Development] stolenphot0:
Getting:

Forbidden

You don't have permission to access /ouya/OneClickOuyaRecovery.zip on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Any ideas?
[Ouya Android Development] ninjabadger:
Same here
[Ouya Android Development] D3LTA:
Mirror
[Ouya Android Development] quepaso:
I just got a brand new ouya, and its got the newest update installed (the os doesn't boot without forcing you to go online + make account). Since i'm on the newest firmware, i cannot get the ouya to talk via adb at all, even just doing a adb devices does not work. I disabled driver signing, the ouya has no exclamation mark, and i have ADB device listed under device manager. Running windows 8.1, tried usb 2.0 and 3.0 ports, nothing.

Did the ouya people do something for adb to stop working properly? And does this still work on the newest firmware? Thanks.
[Ouya Android Development] Prack:
Mine is also on the new firmware. I am able to get adb to work and it pushes recovery but never boots to it. The device will reboot but it reboots to the stock recovery, not the custom one. I've spent about 15 hours on this and have tried many ways over and over but I can't get it to work. I think those of us who waited are screwed.
[Ouya Android Development] quepaso:
Ive tried everything possible and i cannot get the ouya to show up under adb devices. It just refuses to work. I followed all instructions and have been trying for a few days now, and everything is setup perfectly, i removed all other devices and installed the usb driver from this package cleanly, it shows up under Android Composite ADB Interface, it just refuses to work, nothing shows up under adb devices. I really want to start messing with this thing, but not till i get a recovery on there to make sure i have a fallback in case i mess something up. Can anyone help? Running windows 8.1.
[Ouya Android Development] cronikman84:
[MENTION=3279537]Prack[/MENTION]...Theres a easier way to flash cwm recovery than this method, this method didnt work for my OUYA neither , it would not flash the custom recovery, here is the link to the tool that i used and it worked perfect, you may need to run it twice since sometimes it won't flash on the first try but it does on the second or 3rd time, when you run it at first is going to give you a warning/error about not being able to install the driver, just ignore the error, http://ouyaforum.com/showthread.php?5159-OUYA-One-Click-CWM-Recovery