ubuntu-phone team mailing list archive

[Ivo Stoyanov <ivostoy@xxxxxxxxx>]

It's not that simple. What you see is only the first phase - initrd.
I am going thru the hoops for 2 weeks already.

See my thread about similar "learning pain" porting issues.

https://lists.launchpad.net/ubuntu-phone/msg05218.html



>________________________________
> From: Dmitry Smirnov <divis1969@xxxxxxxxx>
>To: ubuntu-phone@xxxxxxxxxxxxxxxxxxx 
>Sent: Tuesday, November 5, 2013 8:36 AM
>Subject: [Ubuntu-phone] Porting issues
> 
>
>
>Hi,
>
>
>I'm trying to port ubuntu-touch to some specific device but have issues with this.
>
>
>I've ported all the changes from phablet-saucy branch to my code base (non-CM, pure codeaurora).
>I decided to skip recovery procedures because I can build all the images (kernel, system, userdata, etc) and try to run the phone using just fastboot to flash the phone.
>
>
>The phone starts, initrd can run, but it fails to complete boot sequence: there is no /root/var/lib/lxc/android/system.img for ex. and I did not find who and when can generate it.
>I'm using pure phablet build for tilapia for comparison of the builds and also cannot find that /root/var/lib/lxc/android/system.img (even in recovery image)
>
>
>What I'm doing wrong?
>
>
>WBR,
>Dmitry
>-- 
>Mailing list: https://launchpad.net/~ubuntu-phone
>Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~ubuntu-phone
>More help   : https://help.launchpad.net/ListHelp
>
>
>