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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1427359 Title: ubuntu-device-flash fails to flash image once it reboots into recovery mode Status in android-tools package in Ubuntu: Invalid 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/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1427359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
