specials FTW!Hell I've been playing Super Mario on Supe Gnes since my last post game is addictive stuck on Star Road![]()
specials FTW!Hell I've been playing Super Mario on Supe Gnes since my last post game is addictive stuck on Star Road![]()
When android or recovery is running, adb is the method to control the device. When the bootloader is active you use fastboot. In other words, what you are seeing is correct. You are just at the bootloader. Now you can execute the fastboot command.Just curious when I do adb reboot bootloader, it disconnects and reconnects with a unknown device ( really a driver missing ) called "fastboot"
the ID's do not match the normal ID's and seem to be for nvidia fastboot... any suggestions on that front?
Star Road FTWHell I've been playing Super Mario on Supe Gnes since my last post game is addictive stuck on Star Road![]()
Strange...FYI, you know how I had issues getting video output booting the recovery.img... I have since hooked it up to all the displays that it would not work on, and it is now working flawlessly on all... so who knows what the heck that was all about.
Well then get off your butt and start developing something! =)Hell I've been playing Super Mario on Supe Gnes since my last post game is addictive stuck on Star Road![]()
I installed the OTA just to see what would happen. It downloaded, rebooted to cwm recovery, which asked me if I wanted to flash the untrusted zip. I said yes and it flashed successfully. After the flash I chose to reboot and it asked if I wanted to disable recovery flash. I chose yes again and it booted to the new version, and adb reboot recovery took me back to CWM. So fyi, CWM is smart enough to warn you and prevent itself from being disabled.When android or recovery is running, adb is the method to control the device. When the bootloader is active you use fastboot. In other words, what you are seeing is correct. You are just at the bootloader. Now you can execute the fastboot command.
P.S. There is a new Ouya "OTA". This will revert recovery back to stock if you receive it. I'll post a CWM zip version that won't cause the revert. Might as well throw in busybox, alternate su, and superuser. If you get the update, the worst case scenario is that you have to redo the the steps in the OP to get CWM recovery back.
Sent from my Nexus 7 using xda premium
Sweet! Why not start a [kernel WIP] thread.welp compiled the kernel ouya so nicely provided the source for recently... onwards to fixing some small scripts so that I can start building CM10 to work.
The main reason I asked this question is in the past 6 mos I have bought a Logitec wireless KB/Mouse combo to use with another device and a Asus BT KB/Mouse combo to use with the Ouya (if and when it arrives) if I tell my wife I now have to buy a usb KB well...., you can guess the restSo, you are saying that no bluetooth KB work or just the one you tried? Did it have it's owen receiver or did you try to pair with Ouya's bluetooth? I am very interested in this because I have a Asus bluetooth KB/Mouse with their own receiver that I was hoping to use with the Ouya.
My Logistic kb/mouse mk520 has its own receiver so hopefully that will work!I have a wireless keyboard/trackpad with it's own reciever. it's not bluetooth, but a proprietary wireless reciever, and it works just fine on the ouya in general, and in recovery. if yours is the same it should do fine, but if it's truly bluetooth it will not pair while in recovery most likely.
I need to clarify for myself and other noobs.Updated OP to add a One-Click-Style installation method. Linux, Mac OSX, and Windows 7 are supported. I tested on Ubuntu 12.04 LTS, Mac OSX 10.6, and Windows 7 64-bit.
O'Boy, now if only I had my Ouya. Oh well, I have waited this long so I can wait a little more. The development is moving along great.Updated OP to add a One-Click-Style installation method. Linux, Mac OSX, and Windows 7 are supported. I tested on Ubuntu 12.04 LTS, Mac OSX 10.6, and Windows 7 64-bit.