ubuntu-phone team mailing list archive

[ioc <scdnewson@xxxxxxxxxxx>]

This could indicate, as assumed earlier, that your install isn't 
completing correctly, so, prior to install adb shell and df to view 
mounts, if no mounts, mount -a, if not /data, mount /data

Also, open up your root-stock-install in gedit and remove adb reboot at 
the bottom of the file, this way once install has completed it won't 
reboot and you can check if the system.img was installed correctly, so 
after install you should see a system.img inside /data and /cache/system 
should show as loop mounted, which in turn be populated.  For 
clarification, the rootfs is pushed to where the rootstock-touch-install 
tells it to go, then it is unpacked to wherever the 
rootstock-touch-install tells it to unpack to (which should be  
/cache/system loop mounted as /data/system.img) then your device 
specific system.img is pushed inside that into 
/cache/system/var/lib/lxc/android

All the Best

On 11/08/16 21:40, ujwal satish m wrote:
> Hello,
>
> I have been using ppa:phablet-team/tools repository to build set of 
> images for nexus 4.
> I observed the following things in recovery mode:
>
> 1. /data  directory contains just media directory in my build; but the 
> preinstalled vivid build recovery has many sub directories
>
> 2./data/system.img is missing in my build.
>
> How to debug this ?