Comment 19 for bug 1263811

Could the error be caused by having the TWRP custom recovery installed and
not CWM? though it seems others are still having issues even with CWM.
On Dec 28, 2013 8:20 AM, "Alexander Freynik" <email address hidden> wrote:

> @wolf-nir
>
> I've been using the SuperSU (Chainfire) app from his website first and
> am currently using the one installed by the Ubuntu installer script,
> which again is Chainfires SuperSU v1.86
>
> I've been trying to force "root" user and "system" user for the Ubuntu
> Dual Boot app (it is permanently accepted by SuperSU and other apps like
> TitaniumBackup are running well with it).
>
> Creating the /cache/system manually and/or copying the ubuntu-boot.img
> to the "files" folder as mentioned before still gives me the following
> output:
>
>
> [...]
> Loading keyring: archive-master.tar.xz
>
> /data/data/com.canonical.ubuntu.installer/files/ubuntu-boot.img is not a
> correct image.
>
> SU granted
> Starting image upgraded: Sat Dec 28 14:42:07 CET 2013
> Processing the command file
> Failed to unmount /cache/system with 22, Invalid argument
> rm
> /data/data/com.canonical.ubuntu.installer/files/uTemp/update_command.applying
> Creating SWAP device.
>
> Setting up swapspace version 1, size = 536866816 bytes
> UUID=[some uuid]
> Done upgrading: Sat Dec 28 14:42:41 CET 2013
>
> Missing update command
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1264570).
> https://bugs.launchpad.net/bugs/1263811
>
> Title:
> install fails just after download
>
> Status in Ubuntu Dual Boot Installer:
> Confirmed
>
> Bug description:
> Just after the download is complete, the app requests root access.
> After granting the root access I get the following messages:
>
> /data/data/com.canonical.ubuntu.installer/files/ubuntu-boot.img is not
> a correct image
>
> SU granted
> Starting image updater
> Processing the command file
> Can not access /cache/system - No such file or directory (2)
>
> Missing update command
> --
> After that, the only option is to choose the install channel again and
> restart the download process
> --
> Device: Nexus 4 rooted Android v4.4.2 with CWM
> No radio firmware modification
> Executed the install script with the 'UPDATE' option
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/humpolec/+bug/1263811/+subscriptions
>