[ROM] Unofficial CM10 Experimental (7/2/2013)

Search This thread

khanning88

Senior Member
Apr 10, 2010
55
267
USA
Unofficial Cyanogenmod 10 (Jellybean 4.1.2) for Ouya - Experimental



**MUST READ**

Until Ouya releases a proper method to force the device into a recovery state this is considered risky. If you're ever writing to the boot partition and the power goes out, or you flash a bad kernel, your Ouya could quickly become a shiny new brick.
Because of this, the flashable zip I posted does not contain the boot.img. The boot.img is a separate download which you should use fastboot to boot. I recommend using 'fastboot boot boot.img' until this issue is addressed. Of course this means that every time you reboot your device you will have to force it to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img' (very annoying).
You can use 'fastboot flash boot boot.img' if you want to write the boot.img permanently, but YOU'VE BEEN WARNED. I am in no way responsible for anything that happens to your device.
Right after you install, go into settings and enable adb and adb root access, THIS IS CRUCIAL. You could be locking yourself out if you don't. If you forgot to do this and you find yourself stuck in a bootloop read the section titled 'Stuck in a bootloop' below.


Tested working
Wifi
Bluetooth
Audio
HDMI
Google Play store (Use gapps-jb-20121011-signed.zip)
Ouya Controller
Ethernet (Have to use 'netcfg eth0 up', 'netcfg eth0 dhcp' commands since we have no settings menu)

Expect bugs and please report them. I have not tested this thoroughly.

Make sure you take a backup of your stock Ouya using CWM.

Downloads
cm-10-20130702-UNOFFICIAL-ouya_1_1.zip
0ff08b8c5aaa85e6d091e4e079cdc79c

20130702-boot.img
60b4c4d82dbe317cd14a5deda09b0831

Tips
Disable Battery Icon
- Go to Settings > System > Status Bar > Battery Status Style > Hidden

Disable extra notification drawer items
- Go to Settings > System > Notification drawer > uncheck Airplane mode and Orientation

Set governor to Performance
- Go to Settings > Performance > Processor > CPU governor > PERFORMANCE (check 'Set on boot' to keep changes on reboot)

Stuck in a bootloop
If you ever get in a situation where adb is disabled and you forgot to boot the proper boot.img you might get stuck in a bootloop.
The only option is to try the following to force the ouya to reboot into recovery.
- Power off the ouya.
- Plug in a usb keyboard that has a sysrq or printscreen key
- Power on the ouya, right after the boot animation starts press the sysrq/printscreen + alt + i keys and hold for a second
- Wait a second and press the key combo again, sysrq/printscreen + alt + i, hold for a second
- Repeat this until the device reboots (You should see the boot animation freeze after a few times, this means your getting close :silly:)
- You should end up back in CWM with adb working

Changelog
7/2/2013
- First release

Source
http://github.com/khanning - Device tree
http://github.com/ouya - Kernel source

Thank you

Cyanogenmod Team and all contributers
Everyone here that started the discussion before I got my ouya. Reading through the threads helped point me in the right direction.
 

Attachments

  • 20130702-boot.img
    5 MB · Views: 96
Last edited:

zanderman112

Senior Member
Oct 6, 2010
7,957
1,844
SouthEast USA
www.twitter.com
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
 

BenG321

Senior Member
Oct 28, 2012
87
21
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.

Same here. I'll wait for someone braver than me to jump in first. Water looks warm, though!

Sent from my SAMSUNG-SGH-I727
 

mybook4

Senior Member
Apr 3, 2011
445
267
Devs, I propose the following to get rid of the potential brick risk:

Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.

From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).

Definitely not straightforward, but should prevent bricks. Thoughts?

Sent from my Nexus 7 using xda premium
 

professorpoptart

Senior Member
Jul 7, 2010
166
110
let's reverse the role of SOS (recovery) and LNX (kernel).

It sounds almost to simple to work! lol
Really though, I see no reason why this would not work... even without hardware buttons, its just selecting "reboot recovery" from the cwm menu.

Might need a discussion around how this would effect the sysrq+i recovery... I believe we would be safe as (from what i can tell) it doesn't boot to the SOS mmcblk directly, it just go's to whatever "recovery" is.

I already have my second ouya on the way so I have no issues testing it out.
 

Asadullah

Senior Member
Aug 24, 2010
1,033
351
casselberry
I think it would be easiest for ouya corp to give us the boot loader source code and let us add I'll those features in ourselves
 
Last edited:

elmerohueso

Senior Member
Nov 29, 2010
568
224
Provo
This is awesome. Maybe you should add a link to this on the OUYA subreddit. Hopefully more exposure makes it more obvious to OUYA how much we need easy access to recovery.
And if more exposure means more noobs bricking their console, then they'll all be contacting OUYA to fix it (since it's not explicitly excluded from the warranty), and that might get them on the ball to release stuff faster.
 

DivinityCycle

Senior Member
Jul 29, 2010
484
265
Portland, OR
This should be fine. One of the things people may not know is that the Ouya is basically an "always on" device which is generally rarely shut down, so a cold boot is not a frequent thing. As a result, making a cold boot slightly less convenient isn't a real issue IMO, particularly as this will ONLY effect users who have opted to flash CWM and ROMs and stuff on their Ouya.
However, making such an extensive modification would mean we better be damn sure the OTA updates are prevented. I can easily imagine an OTA update coming along and breaking everything when it fails to properly update the device upon encountering the non-standard layout. Its one of those "that shouldn't happen" scenarios, but why chance it if we don't have to?
 

b00sted

Senior Member
Dec 24, 2009
1,278
863
Mount Morris NY
I am not too active on these parts anymore but wanted to post thank you for this and once they got proper recovery in place incase I bif my only media box I have for my tv I will give this a go!. ty again for all the work you have done.
 

HellRa1SeR

Senior Member
Dec 20, 2010
168
18
New Delhi
This is what eventually will be on my OUYA, probably a dual boot. The reason being that a lot of games on the play store nowadays have controller support. So I can have a huge catalog of games through there. Also, not to forget movies, music etc.

And whenever I wish to play OUYA exclusive games I could hop back on to the OUYA Rom.
Best of both worlds. :D

Great work devs.
 

zanderman112

Senior Member
Oct 6, 2010
7,957
1,844
SouthEast USA
www.twitter.com
So, if I were to install this, permanently, the instructions would be as follows?


Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?

Sent from my SPH-L710 using Tapatalk 2
 

jmhalder

Senior Member
Mar 26, 2008
357
55
illinois
Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?

The OP suggests that you don't do that quite yet, rather just boot into recovery, flash the zip, and use fastboot to boot the proper boot.img every time... This was you should always have the stock kernel installed on the /boot partition, and there are ways to get back to the recovery if you mess something up. So use 'fastboot boot boot.img' instead. If the kernel can't boot for some reason, currently you can use alt-sysrq-i to get back to recovery, if you mess up the boot partition, you can't, and you'll be completely bricked.
 

BUS DR1V3R

Senior Member
Sep 30, 2010
59
20
I hate to be the one to ask this, but could someone provide step-by-step instructions? I haven't had a reason to use ADB very much but I would very much like to enjoy my Play Store games that have already been purchased on my Ouya. Thanks in advance for anyone willing to take the time to explain this process a little better. :good:

Also, should we wipe anything?
 
Last edited:

toxicbubbles

Senior Member
Oct 13, 2011
65
24
i9100
Moto X Play
Good work man, oh so tempted but my kids use this for watching vids and so will keep my fingers crossed you find a way to make this more permanent. Keep up the good work

Sent from my GT-I9100 using xda premium
 

BUS DR1V3R

Senior Member
Sep 30, 2010
59
20
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.

Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
 
Last edited:

super jay

Senior Member
Jan 10, 2010
62
15
30
Buffalo, NY
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.

Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.

are you in fastboot?
 

BUS DR1V3R

Senior Member
Sep 30, 2010
59
20
are you in fastboot?

I am not entirely sure. The OP says to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img'. This is what I was trying to do, and I found that if I leave the spinning logo up long enough I can reboot bootloader, but when I try to fastboot the boot.img it just says <Waiting on device>.
 

Asadullah

Senior Member
Aug 24, 2010
1,033
351
casselberry
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.

Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.


I'm running it right now with really no issues. What I did was reboot to recovery did a factory reset then formatted system, data and cache. Then installed cm10 and then rebooted to bootloader and flashed the boot.img and did a reset. After that I made it into system and looked around all happy then did a reboot recovery and flashed gapps.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 47
    Unofficial Cyanogenmod 10 (Jellybean 4.1.2) for Ouya - Experimental



    **MUST READ**

    Until Ouya releases a proper method to force the device into a recovery state this is considered risky. If you're ever writing to the boot partition and the power goes out, or you flash a bad kernel, your Ouya could quickly become a shiny new brick.
    Because of this, the flashable zip I posted does not contain the boot.img. The boot.img is a separate download which you should use fastboot to boot. I recommend using 'fastboot boot boot.img' until this issue is addressed. Of course this means that every time you reboot your device you will have to force it to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img' (very annoying).
    You can use 'fastboot flash boot boot.img' if you want to write the boot.img permanently, but YOU'VE BEEN WARNED. I am in no way responsible for anything that happens to your device.
    Right after you install, go into settings and enable adb and adb root access, THIS IS CRUCIAL. You could be locking yourself out if you don't. If you forgot to do this and you find yourself stuck in a bootloop read the section titled 'Stuck in a bootloop' below.


    Tested working
    Wifi
    Bluetooth
    Audio
    HDMI
    Google Play store (Use gapps-jb-20121011-signed.zip)
    Ouya Controller
    Ethernet (Have to use 'netcfg eth0 up', 'netcfg eth0 dhcp' commands since we have no settings menu)

    Expect bugs and please report them. I have not tested this thoroughly.

    Make sure you take a backup of your stock Ouya using CWM.

    Downloads
    cm-10-20130702-UNOFFICIAL-ouya_1_1.zip
    0ff08b8c5aaa85e6d091e4e079cdc79c

    20130702-boot.img
    60b4c4d82dbe317cd14a5deda09b0831

    Tips
    Disable Battery Icon
    - Go to Settings > System > Status Bar > Battery Status Style > Hidden

    Disable extra notification drawer items
    - Go to Settings > System > Notification drawer > uncheck Airplane mode and Orientation

    Set governor to Performance
    - Go to Settings > Performance > Processor > CPU governor > PERFORMANCE (check 'Set on boot' to keep changes on reboot)

    Stuck in a bootloop
    If you ever get in a situation where adb is disabled and you forgot to boot the proper boot.img you might get stuck in a bootloop.
    The only option is to try the following to force the ouya to reboot into recovery.
    - Power off the ouya.
    - Plug in a usb keyboard that has a sysrq or printscreen key
    - Power on the ouya, right after the boot animation starts press the sysrq/printscreen + alt + i keys and hold for a second
    - Wait a second and press the key combo again, sysrq/printscreen + alt + i, hold for a second
    - Repeat this until the device reboots (You should see the boot animation freeze after a few times, this means your getting close :silly:)
    - You should end up back in CWM with adb working

    Changelog
    7/2/2013
    - First release

    Source
    http://github.com/khanning - Device tree
    http://github.com/ouya - Kernel source

    Thank you

    Cyanogenmod Team and all contributers
    Everyone here that started the discussion before I got my ouya. Reading through the threads helped point me in the right direction.
    8
    Why arent there any devs working on CM 10.2 for this? Lack of driver support?

    Haven't seen much in the way of new news on CM on the Ouya in about a month..unless its all on rootzwiki :p That's why I said that.Usually theres a dev or couple ofdevs commenting on what works and what doesnt and their views on the whole process but all that chatter seems to have died down

    Well since I just finished Safe Recovery for the OUYA, I figured I might go ahead and work up a working device tree for CM 10.2 in regards to the OUYA as well. I might just start a new thread once I get things rolling. :)
    5
    Devs, I propose the following to get rid of the potential brick risk:

    Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.

    From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).

    Definitely not straightforward, but should prevent bricks. Thoughts?

    Sent from my Nexus 7 using xda premium
    5
    is anyone still working on cm10.2 ?

    It's on my list. Just not at the top =)

    Sent from my HTC6435LVW using Tapatalk 4
    5
    I think this is a great idea that needs more attention:

    Devs, I propose the following to get rid of the potential brick risk:

    Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.

    From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).

    Definitely not straightforward, but should prevent bricks. Thoughts?

    But then I'm definitely biased, because I had the same idea:

    I agree with everyone it would be nice if we had a hardware means to boot into some kind of recovery or flashing mode to flash stock images.

    But I was trying to think if there is anything we can do if we don't get that... (guess that makes me a pessimist >_>)

    Let me preface this with don't try anything I'm describing here unless you know what you're doing, these are half-baked thoughts of someone who doesn't even have their OUYA yet:

    What if we could swap the boot and recovery partitions? (I haven't received my OUYA yet, so I'm not even aware of what partitions it has, so assuming it has them, and yeah, it wouldn't be quite that simple)

    Basically what I mean is when the device tries to boot normally, it would boot up a stable recovery rom. (ie the boot partition that normally has the kernel and then loads the rest of the rom instead just has a recovery rom)

    Then you have the recovery partition be what boots the full rom. That way you only chance bricking your device when you flash the boot partition, which if we can get a stable recovery rom that works for this, wouldn't be often. We would probably want to modify the recovery to have a 3 second/configurable timer where if you don't do anything it boots into the "recovery" partition which would boot up the full rom.

    Basically the boot partition becomes a new recovery rom which gets used like GRUB to boot into the "recovery" partition which boots up your actual rom, or maybe it could also boot from USB or netboot or whatever...

    Pretty much what we need is a solid bootloader, sound about right? Let me know if any of this makes sense/doable or if I'm entirely off base here! I don't know if I will have the time to try any of this when I do get my OUYA, but wanted to share some ideas, please proceed at your own risk!

    EDIT: Alternatively, the boot partition could be left stock and the recovery partition could be used as a bootloader to boot into USB or other options for loading roms without messing with the stock boot experience and risking bricking the device. ie in this configuration if you boot your device normally it would be stock, if you reboot into "recovery" it would load up a custom rom. Or instead of a custom rom, a custom recovery with bootloader capabilities.

    And I do plan to try this idea out eventually, but I've got some other ideas I intend to try out first.

    The first one I hope to have done by the end of this weekend (hopefully sooner though) is to reconfigure this experimental CM build to be usable without touching any of the internal storage space. I plan to have a modified boot.img that will load system/data/sdcard folders off a usb thumb drive. This method would be completely safe, though a little inconvenient because you would need to use adb to reboot the OUYA into bootloader mode so that you can then fastboot it to load the modified boot.img, but after that it could be disconnected and would be running using only external storage. You're essentially using a computer to jumpstart your OUYA into CM10, while leaving everything on the OUYA itself in pristine stock condition. Then I plan to try out arm versions of adb/fastboot so I can use my tablet or possibly phone (USB OTG) to jumpstart the OUYA instead of having to rely on my computer all the time.

    I think this will be an extremely safe way of using external ROMs until we can get some kind of special bootloader figured out.

    So if anyone is thinking about trying CM10, but leery of messing with their OUYA, just wait another week or so and I should have a safe, non-intrusive solution worked out!

    I welcome any input/thoughts on these ideas! And if anyone knows how to do the things I'm describing and wants to beat me to the punch, feel free and run with these ideas - I won't mind as long as you share your work and give me a little credit if any credit is due!

    ~Troop