ubuntu-device-flash fails to flash image once it reboots into recovery mode

Bug #1427359 reported by Jim Hodapp on 2015-03-02
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
android-tools (Ubuntu)
Undecided
Unassigned

Bug Description

Running Ubuntu Trusty 14.04 and the latest packages from the android-tools PPA: https://launchpad.net/~phablet-team/+archive/ubuntu/tools

1. Try to flash a krillin device via: ubuntu-device-flash touch --channel=ubuntu-touch/ubuntu-rtm/14.09
2. Observe that at the time of this bug, RTM image 19 is downloaded and pushed to the phone successfully.
3. u-d-f reboots the phone into recovery mode and you see the Ubuntu logo spinning.
4. u-d-f complains that it failed to enter recovery after about 60 seconds.

See the log output for more details. [1]

[1] http://pastebin.ubuntu.com/10505648/

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in android-tools (Ubuntu):
status: New → Confirmed
Nephilim1973 (nephilim1973-e) wrote :

+1

Sturm Flut (sturmflut) wrote :

This happened to me today on Ubuntu 14.10 with a bq Aquaris E4.5. I ran "ubuntu-device-flash" without any parameters.

Rex Tsai (chihchun) wrote :

The problem is the u-d-f (ubuntu-device-flash) could get access to "adb shell" to deploy new images after it send "adb reboot recovery" to the device.

It's because the production recovery image does not enable adb shell for security reason. You have to pass a engineering version recovery to reflash with ubuntu-device-flash.

You could find the engineering recovery image at

http://people.canonical.com/~jhm/barajas/recovery-krillin.img
http://people.canonical.com/~alextu/tangxi/recovery/recovery.img

Changed in android-tools (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers