Flashing stuck: can't open /cache/recovery/ubuntu_command

[Cris Dywan]

I'm doing this on a Samsung Galaxy:

phablet-flash ubuntu-system --channel devel-proposed

It stops and doesn't continue in the recovery screen with:

CWM-based Recovery v6.0.2.8
E: Can't open /cache/recovery/ubuntu_command
Checking for autodeply.zip
autodeploy.zip not found.

See attached averbatim console output from phablet-flash.

[Stuart Langridge (sil)]

Note that I had the same experience, but I waited a while and it turned out that the terminal was still sending things to the phone: after a few minutes the terminal pushed a few more things, then said "restarting device..." and then the phone (a Nexus 4) rebooted. It was quite disconcerting to see the error message on the phone screen, though: I'd got as far as half-typing a question about it into IRC before it became clear that it was still working.

[Cris Dywan (kalikiana)]

I gave it a second and a third try, the last one seems to have succeeded - to be fair I didn't stare at the screen non-stop, but if I see an error message and nothing happening for 10min I assume it's stuck. That didn't appear to happen the third time I tried.

[lilix (alixlebosse)]

I have flash my phone with the official tutorial on the web site ubuntu.com bug I have this same error.

[Sergio Schvezov (sergiusens)]

This is sort of confusing, from the log it seems everything went fine. I am however removing the prints from recovery as they seem to be confusing people.

[Sergio Schvezov (sergiusens)]

Ok, I need more info, is this precise, quantal, raring, saucy or trusty? Given that it wasn't logged with ubuntu_bug I'm thinking it's neither saucy nor trusty.

If you
adb reboot recovery

and run
adb devices

what do you see?
can you adb shell from recovery?

if this is true, then this bug is a android-tools-adb bug and a missing udev rule.

[Sergio Schvezov (sergiusens)]

Those messages have been removed from the recovery screen so users don't get confused by it.