install fails just after download

I have a Gnex with AOSP 4.3 and I have exactly the same problem even if I manually create the directory /system/cache/ the installation halts after trying to create the swap file. With the message Missing update command

It's trying to uninstall after installation failure. So there is something else broken, can you scroll up to see the whole message?

My full dump is (GNex 4.3):

Starting download
Downloading: image-master.tar.xz
Downloading: image-master.tar.xz.asc
Downloading: image-signing.tar.xz
Downloading: image-signing.tar.xz.asc
Downloading: ubuntu-bfff41f10871b32**giant hex number**83c47.tar.xz
Downloading: ubuntu-bfff41f10871b32**giant hex number**83c47.tar.xz.asc
Downloading: device-888d392**giant hex number**b471a.tar.xz
Downloading: device-888d392**giant hex number**b471a.tar.xz.asc
Downloading: version-79.tar.xz
Downloading: version-79.tar.xz.asc
Generating update command
Download done in 1428 seconds
Extracting supporting files
Starting update script
SU granted
Starting image upgraded: Tue Dec 24 14:19:22 WET 2013
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: Tue Dec 24 14:19:23 WET 2013
Processing the command file
Can not access /cache/system - No such file or directory (2)

Missing update command

PS: Please add the ability to dump this messages to a file or the clipboard on next update please :)

Same problem as described above.

Nexus 4 rooted Android v4.4.2

Tried UPDATE and FULL (after unrooting) as well as multiple branches. Also reverted to 4.2 radio.

Same error on Galaxy Nexus

He attach of the error:

Exactly same problem here.
Nexus 4 rooted Android v4.4.2

Sorry to say me too. Old Nexus 7 with Android 4.4.2.

Google Nexus 4, Android version 4.4.2 KitKat (stock, rooted w/ SuperSU)

I choose to go with this option despite having SuperSU on the system although it states that "without SuperUser app installed" in https://wiki.ubuntu.com/Touch/DualBootInstallation#Can_I_uninstall_dual_boot.3F

./dualboot.sh FULL

.. I also ran this command to free up space:

adb shell "su sh rm -rf /cache/*"

Full dump: Screenshot (link to Dropbox)
https://www.dropbox.com/sh/hqir7rokiz2qclq/Qdlvb6FVdj

Photos are in order. Left to right.

I have the same problem.. N4 Stock ROM 4.4.2 rooted SuperSu installed.

I have the same problem. Nexus 4 Stock ROM 4.4.2 rooted, CWM & SuperSu installed.

It seems to me that the files can't be extracted to the correct directory because a lack of root access.

I managed to solve it by performing the following steps:

1. In the Ubuntu Dual-boot app deleting the downloaded files (options -> delete...)
2. Reboot the phone
3. Do NOT delete the /cache as the manual says.
4. Start the installation again and when prompted allow SU access.
PAY ATTENTION there might be a timeout on the approval. I allowed SU access for this app "forever" in order to avoid repeated questions.

ALSO - If it fails do it again. For me the second time worked (I must have missed the first SU prompt in the first installation)

Device: Galaxy Nexus with CM 10.2

@wolf-nir

I've tried all what you suggested before.
Installed multiple times with and without deleting the /cache (also rebooting inbetween) and different SuperSU settings and installations.

Unfortuanetly it doesn't seem to help.

@acminusm

If you get "Can not access /cache/system - No such file or directory (2)" you can try creating it manually, but the installation will probably fail somewhere else.

Which super-user app do you have?
By the way - open it and make sure that the Ubuntu installer has root privileges BEFORE you start the process again.

@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

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
>

Well yeah, I thought the same, so I also tried Stock and CWM. Sorry for not mentioning that.

Just flashed clockworkmod, fixed permissions, and got to the creating swap
devices, but failed after that. I think I'm going to restore to factory,
re-root, flash CM10 and try again.
On Dec 28, 2013 8:50 AM, "Alexander Freynik" <email address hidden> wrote:

> Well yeah, I thought the same, so I also tried Stock and CWM. Sorry for
> not mentioning that.
>
> --
> 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
>

I don't see any reason the recovery to be a part of it. The dual-boot script overrides the recovery partition with the Ubuntu's custom boot.

Flashing on CM 10.2 with their built-in SU app worked for me.

I will try that. Are you working with a Nexus 4?
On Dec 28, 2013 10:40 AM, "Nir Wolf" <email address hidden> wrote:

> I don't see any reason the recovery to be a part of it. The dual-boot
> script overrides the recovery partition with the Ubuntu's custom boot.
>
> Flashing on CM 10.2 with their built-in SU app worked for me.
>
> --
> 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
>

I can confirm, that installing latest stable CyanogenMod 10.2 from the link below and then installing the dualboot app via "./dualboot.sh UPDATE" works without problems.

 http://download.cyanogenmod.org/?device=mako&type=stable

At first it seems to be stuck at the "Google" bootlogo but it just takes a while to start up Ubuntu Touch.

I will try again with a freshly installed stock 4.4.2 in a bit.

Thank you, Alexander. I will attempt this tomorrow and report.
On Dec 28, 2013 9:05 PM, "Alexander Freynik" <email address hidden> wrote:

> I can confirm, that installing latest stable CyanogenMod 10.2 from the
> link below and then installing the dualboot app via "./dualboot.sh
> UPDATE" works without problems.
>
> http://download.cyanogenmod.org/?device=mako&type=stable
>
> At first it seems to be stuck at the "Google" bootlogo but it just takes
> a while to start up Ubuntu Touch.
>
> I will try again with a freshly installed stock 4.4.2 in a bit.
>
> --
> 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
>

I've flashed the occam-kot49h Nexus 4 v4.4.2 stock image via "./flash-all.sh" and then installed the dualboot app via "./dualboot.sh FULL" and now Ubuntu Touch installs as well.

My guess would be that either the deletion of the /cache contents or maybe choosing "yes" when there is the CWM false positive of not having supersu installed causes the problem. I can't think of anything else that I've done different this time besides having a clean system instead of a used one.

Maybe someone else can confirm this?

I used the app and modified recovery "multi ROM manager" with success. Maybe the devs and canonical can talk to the guy who developed this as it meets almost all of their goals as well. It boots both android and Ubuntu and allows access to the custom recovery.

I got mine working. Here's what I did on my unlocked Nexus 4.

Here are the steps I took:

1) Re-flash everything back to stock Android 4.4.2, KOT49H.

2) Enable USB debugging.

3) Download dualboot.sh and run ./dualboot.sh FULL

4) Open the Ubuntu Dual Boot app, download the Ubuntu image and let it do its thing.

5) Reboot to Ubuntu. Done.

*Note:
I did not install any recovery or SuperUser app after I re-flashed.

Everything feels great. I love the interface. It does get laggy and buggy at times but everything else is working (like calling, SMS, mobile data & camera) except WiFi. Navigating in it is quite natural to me except I find it quite hard to go "Back" to the previous intent/window, I have to swipe down from outside screen OR touch somewhere around the bottom area.

I can confirm that I got dual boot to work. I unrooted my Nexus 4 and reset
it to factory settings with Android 4.3. Ran the /.sh FULL without rooting
first. Let the installer install the CWM and Superuser app. Everything is
running fine now. Thank you all for your help.

On Sun, Dec 29, 2013 at 5:57 AM, Duane Adam <email address hidden> wrote:

> I got mine working. Here's what I did on my unlocked Nexus 4.
>
> Here are the steps I took:
>
> 1) Re-flash everything back to stock Android 4.4.2, KOT49H.
>
> 2) Enable USB debugging.
>
> 3) Download dualboot.sh and run ./dualboot.sh FULL
>
> 4) Open the Ubuntu Dual Boot app, download the Ubuntu image and let it
> do its thing.
>
> 5) Reboot to Ubuntu. Done.
>
> *Note:
> I did not install any recovery or SuperUser app after I re-flashed.
>
> Everything feels great. I love the interface. It does get laggy and
> buggy at times but everything else is working (like calling, SMS, mobile
> data & camera) except WiFi. Navigating in it is quite natural to me
> except I find it quite hard to go "Back" to the previous intent/window,
> I have to swipe down from outside screen OR touch somewhere around the
> bottom area.
>
> --
> 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
>

--
Cheerfully,

Andrew Brandt
Co-Owner/Lead Technician
All Star Computer Service
5073 S. Coulter
Suite 200
Amarillo, TX 79119
(806) 476-0100

*Important Warning:* All information contained in this email is property of
All Star Computer Service. This e-mail and any files transmitted with it
may contain PRIVILEGED or CONFIDENTIAL information, which is intended for
the use of the person to whom it is addressed. If the reader of this
email/attachments is not the intended recipient, employee, or agent
responsible to deliver it to the intended recipient, you are hereby
notified that any dissemination, distribution, reproduction, or copying of
this information is STRICTLY PROHIBITED. If you have received this e-mail
in error, please delete the related e-mail and all attachments and notify
the sender immediately.

I got it working by unrooting my nexus 4 (no need to do a reset factory apparently).

So my advice if your already rooted:
Go to the superuser app and hit "unroot" in the parameter section before installing dualboot.

Worked for me on nexus 4 with 4.4.2 stock.

The same worked for me.

- Use the 'Full unroot' button in SuperSU
- Reinstall SuperSU and the Ubuntu Installer
- Restart installation

On Nexus 4 with android 4.4.2

Same issue on Nexus 7 (2013) with Android 4.4.2 stock and TWRP recovery.

Verified in M9 build.