ubuntu-phone team mailing list archive

[Jani Monoses <jani.monoses@xxxxxxxxxxxxx>]

Hi,

that system.img should be the one built from your CodeAurora tree and then
turned into a regular ext4 image on your build machine

$simg2img system.img new.img
$resize2fs -M new.img

In recovery mode
#mkdir a
#mount /data/system.img a

On the host
$adb push new.img /a/var/lib/lxc/android/system.img
$adb reboot

Jani




On Wed, Nov 6, 2013 at 9:40 AM, Dmitry Smirnov <divis1969@xxxxxxxxx> wrote:

> Hi,
>
> I'm trying to port ubuntu-touch to a 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)
> This causes device to be unrecognized ("unknown) and probably causes some
> other steps to fail.
>
> Also, /root is read-only for some reason and I also suspect this prevents
> the system to boot:
> + mkdir -p /root/android
> mkdir: can't create directory '/root/android': Read-only file system
>
> 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
>
>