ubuntu-phone team mailing list archive

[Tony Espy <espy@xxxxxxxxxxxxx>]

On 09/08/2015 11:26 AM, Alejandro J. Cura wrote:
> On Tue, Sep 8, 2015 at 12:08 PM, Tony Espy <espy@xxxxxxxxxxxxx> wrote:
> > Early in the development of arale I too got to the point where I couldn't
> > update at all. I managed to limp along by leveraging ssh and manually
> > pushing the files to the device via scp which was tedious to say the least.
>
> Do you have any tips/pointers on how to do this?

Here's the email I sent internally when this first started effecting 
me...  This should still work, however no guarantees.

---

For those of you that are stuck in the unable to update state, here's 
the process I used to manually update my arale via ssh:

1) Ensure that you have openssh-server installed, configured, and 
started ( outside the scope of this email ).

2) Run an ubuntu-device-flash with --download-only and --show-image to 
download and show the files that would be installed:

ubuntu-device-flash   --server https://system-image.startx.ro:10450 
--download-only --show-image --channel=ubuntu-touch/vivid-proposed 
--device m75

Ex.

espy@shrike:% ubuntu-device-flash   --server 
https://system-image.startx.ro:10450 --download-only --show-image 
--channel=ubuntu-touch/vivid-proposed --device m75
2015/03/21 13:28:21 Device is |m75|
Description: ubuntu=20150320,device=20150210,custom=20150320,version=143
Version: 143
Channel: ubuntu-touch/vivid-proposed
0 
http://system-image.ubuntu.com/pool/ubuntu-5a8dd3972e2d7bdad477a009ad3aebb027131a022b6fa68e1ef9a33bfcf5ddaa.tar.xz 
348851796 4ae8da125a1e8bdaabbccea9f005f033e46a9b527f0de24ea5ecbe2b1c462ab6
1 https://system-image.startx.ro:10450/pool/device_m75.tar.xz 27 
344c746e1a128ad808b435a8bfaabeafc9ee0aafd37263c0384e812689bef291
1 https://system-image.startx.ro:10450/pool/custom.tar.xz 32 
a453a731decc277bd0fd4e6df866014d8367511faee747f8ce694db9087a5393
3 
https://system-image.startx.ro:10450/ubuntu-touch/vivid-proposed/m75/version-143.tar.xz 
368 41fce290c71a59ed77c4acbc8c7ec1df268e9010b7702ad74e620b116c802ba6

3) Use scp to copy the files ( and associated sig files ) to the 
/cache/recovery on the device.  I I copied them all to /home/phablet 
first, then moved them to /cache/recovery as root.

4) Copy the image-master and image-signing tarballs and sig files to the 
device, and then to /cache/recovery.

5) Copy the file ubuntu_command ( see attached ) to /cache/recovery. I'm 
not sure it's 100% necessary, but I made sure it's executable by owner.

*NOTE* - this ubuntu_command is specific to an install of image #143. 
Please be aware that if you do this next week, you may get new image 
files, and thus will need to be *very* careful to fixup the 
ubuntu_command script before copying it.

6) Run 'sync' ( just to be safe; again might not be required )

7) Power down the device, and manually boot into recovery mode.

> Sounds like adding an option to ubuntu-device-flash so it uses ssh/scp
> to flash wirelessly would help a lot here.

+1; Can someone please open a bug for this?

/t



format system
load_keyring image-master.tar.xz image-master.tar.xz.asc
load_keyring image-signing.tar.xz image-signing.tar.xz.asc
mount system
update ubuntu-5a8dd3972e2d7bdad477a009ad3aebb027131a022b6fa68e1ef9a33bfcf5ddaa.tar.xz ubuntu-5a8dd3972e2d7bdad477a009ad3aebb027131a022b6fa68e1ef9a33bfcf5ddaa.tar.xz.asc
update device_m75.tar.xz device_m75.tar.xz.asc
update custom.tar.xz custom.tar.xz.asc
update version-143.tar.xz version-143.tar.xz.asc
unmount system