On 09/08/2015 10:23 AM, Jamie Strandboge wrote:
On 09/08/2015 08:58 AM, Pete Woods wrote:
I'm running Vivid + Stable overlay PPA. For me, though, the really interesting
part is that even using the Android SDK tools manually is unreliable:
$ fastboot flash recovery ~/Downloads/recovery-arale.img
ERROR: usb_read failed with status e00002ed
ERROR: usb_read failed with status e000404f
sending 'recovery' (10672 KB)...
ERROR: usb_read failed with status e000404f
FAILED (status read failed (No such file or directory))
finished. total time: 0.000s
If I can't reliably push things using fastboot, that rules out anything specific
to Ubuntu on the device.
For me adb, phablet-shell, udf, etc all work fine on a Dell XPS 13 with Vivid
*if* I use the USB ports on the system. If I use the port replicator, adb
devices doesn't see the device (but the kernel does).
Oddly enough, my Arale can ONLY be seen if I connect it through a usb
hub, and a tiny 3 inch usb cable. Even then, I can only reliably access
it via fastboot. It flickers connections otherwise.
To workaround this, I hacked up the system image tools to download
images on the device and reboot and run them. Though I can't remember
what I did and like most things, didn't write it down. I hadn't needed
to flash for a month, so I forgot. Now I need to flash again, and I'm
stuck with a bootlooping phone so u-d-f seems like the only option.
The original image came care of Dave Morley's incessant attempts during
a long afternoon at a conference. He told me he didn't want to see the
phone again after that, but he somehow did manage to flash it. Thanks Dave!
I'm running Wily, but the device has always been this way. It's an early
device, but should have been after the hw defects.
nicholas
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
