Bricked my Ouya?

[Evil.Sonic]

If anyone can give advice it would be appreciated.

So I bought an Ouya from a friend that had CM11 on it and still some of their apps ect

I plugged it in, I noticed the screen over cast but the device was working, I went into CM11 and did a factory wipe (for a fresh start)

CM11 booted back up, but the controller wasnt working anymore. Took me a while to access the menus with the keyboard but I got the controller working.

I got fed up with the screen issue and the hassle and thought it was CM11s problem so I wanted to see what stock ouya was like

I alt + print scrn + i and flashed stock Ouya

now all I see when turning on the Ouya is the Orange Ouya logo, and alt + print scrn + i does NOT longer take me into recovery.

What can I do here? Thanks in advance.

 

[jerryfath]

Can you turn on the ouya, then plug in a usb cable and test whether your pc sees the ouya? If so, you should be able to use a tool like ouya toolbox to flash cwm, then boot into recovery. I would highly recommend installing the latest boot menu, so you don't have to time the alt-ps-i in the future.

 

[Evil.Sonic]

jerry, thanks for your reply

My pc recognizes the ouya but I haven't been able to get the drivers properly installed

I've tried win xp, win 7 and 8

it loads as a mtp device. I've got android sdk installed but that's as far as I've got

 

[Evil.Sonic]

well it's been a few days and I can't figure it out

when I plug the ouya into my pc it tries to install drivers for "MTP device"

it fails. tried diff ports. sdk installed. windows 7 and windows xp. no luck

anyone know what I can do? I can't get the Google usb drivers to install at all

 

[jerryfath]

Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids

The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.

Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers

 

[Evil.Sonic]

Can you check the USB ID of the ouya when it's connected to your PC? Under linux you can do a simple lsusb, but under Windows, I think you'll need to install a little utility to list all of the devices on the USB bus.
Edit: You can get the ID in Windows using the Device Manager. Under the Details tab Hardware Ids

The Ouya vendor id is 2836. The device ID will be different depending on what state the Ouya is in. That might give us a clue as to what's happening.

Edit2: There are a number of threads out there about adding the Ouya hardware ID to android-sdk\extras\google\usb_driver\android_winusb.inf in order to get the Ouya to be recognized by the Google drivers

Hi jerry, Ive tried editing the google usb driver inf file but no luck. theres a 2nd inf file in most steps but I dont have the other android folder.

here is the device instance ID in windows xp

USB\VID_2836&PID_0012\015D8CA2FD2BF006

the steps ive done are.

download android sdk
install google usb driver

download google usb driver stand alone
edit inf file

try to detect drivers - fail

 

[jerryfath]

When you say "try to detect drivers - fail" what are you actually doing?

If you haven't already, you should go into Device Manager, right click on the ouya, select the driver tab, choose update driver, choose have disk, then navigate to the folder with the usb driver .inf that you've edited.

When you do that, it should either install the driver or tell you no driver was found for the device.

 

[brandogg]

I'm sure you tried lots of times and I apologize if this is no help, but I just kept banging on alt + prn scrn on mine until it finally went into recovery and a factory reset fixed it. I would imagine that's all that yours needs...just need to find a way to kick it into recovery.
Edit - I did have to install the newest Google driver from the Android SDK Manager as well, and did not need to modify like you used to need to do IIRC.