[WIP] AOSP tegra 3 port

professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 28, 2013 at 3:21 AM
The purpose of this thread is to work on porting an 4.1.2 AOSP rom for a tegra 3 device over to the OUYA. This is my first attempt at a port, so any warnings/advice moving forward is more then welcome! This thread will be used until we have a tested working build at which time I will post a [ROM] thread for it with clean instructions/documentation. Any builds posted here are to be assumed not working and could potentially brick your device...

I'm using RC-OUYA-1.0.264-r1_ota.zip as base rom
http://forum.xda-developers.com/showthread.php?t=2266629

I switched port rom to liquid smooth 4.1.2 for the TF700 (HTCdemon suggested closer hardware)
http://forum.xda-developers.com/showthread.php?t=1979464

I'm also working on a port rom with the stable tf700t CM10.0 build
http://get.cm/?device=tf700t

For my development environment I am using h311sdr0id's h311s|KITCHEN (ubuntu)
this has the kernel tools needed to pack/unpack boot.img as well as dsixda's android kitchen 0.221
http://forum.xda-developers.com/showthread.php?t=2152398

What I'm working on...
http://forum.xda-developers.com/showthread.php?t=1598713

The basic pieces needed;
A jb(4.1.2) rom made for the device (the OTA zip)
A jb(4.1.2) rom that I want to port (the AOSP zip)
if going from different manufacturer must have same processor (both tegra 3)

Ramdisk wise:
I have merged the AOSP tf700 boot.blobs ramdisk with ouyas OTA ramdisk to make a custom boot.img that "should" boot the AOSP rom.
I have attached the working copy of the merged boot.img in a flash-able zip. This "should" allow the AOSP rom to talk to the kernel. Although it has been tested and is working on stock OTA installs this build is for R&D only!

Update:
With porting just the roms (/system) they all install fine, but get stuck on the boot animation.
With porting with the new boot.img they install, but get stuck on a blank screen before boot animation

Update:
I am also waiting for my bus pirate to come in (mid next week) so I can get console output while booting to see where its crashing at to point me in the right direction.
I got it in and working.. instruction and links on page 6
 

Attachments

Last edited:
  • Like
Reactions: CXENTE, camo_flage, genetic608 and 10 others
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 28, 2013 at 6:50 PM
I have not, thanks I will take a look. That also has a lot of 4.1.2 roms... I want to stay in android 4.1.2, I now that there were changes to the blue tooth stack in 4.2 that cause the wiimote pairings to break. Not sure if this would effect the ouya controller, but one less thing to worry about.

Sent from my SAMSUNG-SGH-I337 using xda app-developers app
 
  • Like
Reactions: genetic608
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 28, 2013 at 11:57 PM
CWM error status 6

So I see that status 6 has to do with parsing the updater script. Usually from if you edit the file in wordpad or something. I'm on ubuntu 12.04 andI edited in gedit and am getting this. I even took a look in vim and it looks good to me. Any other clues on what status 6 might mean? Here is a copy of the build I'm try to flash if anyone wants to take a look. I will keep digging online.

!!Warning!! This file may blow up your ouya, I wouldn't flash if I were you... not that you could.... status 6....


Deleted the file... didn't work anyway...
 
Last edited:
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 29, 2013 at 12:26 AM
HTCdemon said:
Actually the Ouya is pretty much a TF700T without screen ( aka the Asus Transformer Pad Infinity )
Click to expand...
Well since I've been spinning my wheels here on this status 6, let me try and port a tf700 rom real quick. I don't expect it to work 100%, just looking for a successful flash and maybe boot!

edit:
well I must be doing something wrong, getting the same status 6 with this one too.
 
Last edited:
mybook4

mybook4

Senior Member
Apr 3, 2011
445
267
0
May 29, 2013 at 2:58 AM
I tried downloading the zip, but I get into some weird Authorize Download loop. Can you post just the updater-script to a pastebin? I ran into status 6 a couple times when I was making the CWM zip.

Sent from my Nexus 7 using xda premium
 
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 29, 2013 at 3:08 AM
mybook4 said:
I tried downloading the zip, but I get into some weird Authorize Download loop. Can you post just the updater-script to a pastebin? I ran into status 6 a couple times when I was making the CWM zip.

Sent from my Nexus 7 using xda premium
Click to expand...
http://pastebin.com/CgmYJVQY

I think it has something to do with mounting system.

Im using dsixda's android kitchen to build and sign.

edit:
I get this when building, which I think is causing the issue but I dont see it in the script.
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("MTD", "system", "/system"); "0 /system/

edit:
I see that theres an option in the kitchen for "Check update-script" it found some errors with the fonts. Pushing the zip now to try the new build.
nope same thing status 6.
 
Last edited:
  • Like
Reactions: mybook4
mybook4

mybook4

Senior Member
Apr 3, 2011
445
267
0
May 29, 2013 at 3:36 AM
When I mounted /system, I did it with

run_program("/sbin/mount","/system");
Click to expand...
I unmounted it with:

run_program("/sbin/umount","/system");
Click to expand...

These worked for me. I believe this works because the recovery.fstab defines /system. You could try replacing the mount lines with the lines above.

There's more going on in the script, so it could be something else.



Sent from my Nexus 7 using xda premium
 
Last edited:
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 29, 2013 at 3:54 AM
from what I understand it runs line for line until it errors, and since my /system is never formatted I would say the error is probably that line.

edit:
While writing this I took a look in the actual zip rather then the working directory and the kitchen is changing the file!

this is whats in the updater-script after I build the rom.
format("MTD", "system");
mount("MTD", "system", "/system"); "0 /system/
package_extract_dir("system", "/system");
...
...

edit:
looks like one of the default setting in the kitchen says something about update script. When I choose this I only have an "update_script" and no "updater_script"... well its built, giving it a try...

CWM gives a message about the update_script not being supported and to switch to updater_script (which was what I was trying to use)... so there has got to be a setting/option I'm not seeing...

edit:
looks like I have to add the mount point to the edify_defs folder so the kitchen can build for the ouya...
http://forum.xda-developers.com/showthread.php?t=633246

edit:
ok, now the kitchen says;
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system"); "0 /system/

looks good, pushing zip now...

And!... status 6...

at least the updater_script looks correct now;
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system"); "0 /system/
package_extract_dir("system", "/system");
...
...

edit:
since this has yet to format system, I can always do that manually in CWM. I'm removing the format and seeing if just mount works.
 
Last edited:
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 29, 2013 at 5:04 AM
So i'm sitting here right now looking at a liquidsmooth boot animation!

I let it sit for 10 minutes or so, looks like its stuck.

Once it get stuck in the boot loop you have to do the Alt+SysRq+i trick to get back into recovery.

so I went into recovery tried the zip, saw that it mounted and took off, so it did have something to do with format. after it finished I went to mounts menu option in CWM and formatted system cache and data manually and reran the install. reboot and I got the logo I was looking for. So still work to do to get it actull get into the system but a good step forward.

Here is a copy of the liquidsmooth 4.1.2 ouya port [link to original rom in first post] if anyone wants to take a look. The only changes I made to the rom are listed in the first post.
!!WARNING - this build will loop on boot animation, no real reason to flash right now!!
[removed link since it didn't work...]
let me know if this link doesn't work...

So, the to do list:
1. How to get past the boot animation loop (not sure if adb will work at that point... wifi for sure doesnt).
2. Need to work on the updater script to find the working format syntax.
3. Sleep!
 
Last edited:
  • Like
Reactions: milkdudxp
sonofskywalker3

sonofskywalker3

Senior Member
Jan 22, 2009
812
460
0
May 29, 2013 at 10:06 PM
Well I'm on the same page as you, only not as far down... I followed mybook4's advice on mounting /system, removed the format line and replaced it with:

delete_recursive("/system");

to wipe the system partition, and got my build of CM10 to flash! YAY!!

Nothing... No splash, no bootanimation, no nothing. Adb devices returns:

???????????? No Permissions

So I had to do the same thing, alt+sys req+i, reflash stock firmware. I think it has to do with some missing proprietary files, I used the tf700t proprietary-files.txt but it's not quite good enough I think. I'm trying to find a good tutorial to tell me what exactly I need to extract from the Ouya, the CM porting guide is quite vague...

In other news, did anyone else get an OTA update today? If so I guess I'll be starting over on the OuyaPlus ROM. It's just as well. all the Ouya stuff stopped working after I deodexed it. Universal deodexer my shiny metal... well you know.
 
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 30, 2013 at 12:05 AM
One thing I wanted to try was to clear cache and dalvik after it gets stuck. Had that issue a few years back on some old roms. When I booted back up I did not get the boot animation, just a blank screen. So i wonder if something is getting stuck on a "start-up" script.

while at the blank screen or boot animation I cannot adb (usb or wifi via build.prop) to get a logcat going to see what shes stuck on. its in MTP mode while booting...

Also got rid of the init.d stuff just to see what happens.

... still formatting system, data, cache and dalvik on every try.

edit:
no change. Does anyone have any advise on debugging boot up? maybe a verbos boot mode? or logging that can point me at something other than "stuck on boot animation"?
 
Last edited:
professorpoptart

professorpoptart

Senior Member
Jul 7, 2010
165
110
0
May 30, 2013 at 4:23 AM
just for the hell of it I grabbed the stable TF700t CM10.0 build from http://get.cm/?device=tf700t tried a quick port of that with the same results. I get a really cool CM boot logo to look at though!

edit:
so at least I know its not that specific rom...

I've been following this tut for the porting process
http://forum.xda-developers.com/showthread.php?t=1908008

I think I'm going to try and leave the tf700 system alone and only change the device name in build.prop and edit the updater_script and see what happens.
pushing zip...

every time I flash a zip its like scratching a lottery ticket! come on...!! lol

looks cool!...
 
Last edited:
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone