[RECOVERY] Ouya CWM Recovery

[billouetaudrey]

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

Need usb keyboard

Envoyé depuis mon Galaxy Nexus avec Tapatalk 4

 

[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?

So can anyone answer any of my questions/queries about this pink recovery issue?

 

[HT123]

So can anyone answer any of my questions/queries about this pink recovery issue?

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

 

[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?

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

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?

 

[Hal9k+1]

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?

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.

 

[zondajag]

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.

Is that something professorpoptart could help with at all? Who compiled this CWM? was it the original poster?

 

[Hal9k+1]

Is that something professorpoptart could help with at all? Who compiled this CWM? was it the original poster?

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!

 

[zondajag]

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!

Um any way of getting instructions on how to safely implement your new updated version of the CWM recovery?

 

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

 

[Re-Mi]

Hi all im having the following problem:

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

 

[TadeoNYC]

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

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.

Sent from my Nexus 7 using Tapatalk 4

 

[domagoj_zg]

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.

Sent from my Nexus 7 using Tapatalk 4

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?

 

[zondajag]

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?

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.

 

[Ipse_Tase]

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.

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.

 

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

 

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

Sent from my SCH-I535 using Tapatalk

 

[Ipse_Tase]

I think its just guessing wildly. Either you have drivers or you don't (for Windows 7 for instance).

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

 

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

Duh, finally.

Rooted it with this method: http://forum.xda-developers.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.

 

[soulman79]

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.

 

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