ubuntu-device-flash silently does not flash

Bug #1360543 reported by Zoltan Balogh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
android (Ubuntu)
Confirmed
High
Sergio Schvezov
goget-ubuntu-touch (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My mako device has the rev203 flashed.

I do this ->

adb -s ${SERIALNUMBER} reboot-bootloader
ubuntu-device-flash --serial=${SERIALNUMBER} --channel=ubuntu-touch/utopic-proposed --wipe --bootstrap
adb -s ${SERIALNUMBER} wait-for-device
phablet-config -s ${SERIALNUMBER} welcome-wizard --disable
phablet-config -s ${SERIALNUMBER} edges-intro --disable

The flashing process gives this output -> http://pastebin.ubuntu.com/8116521/

After the flash, the device is still on the rev203.

A consider this as a critical security issue, as this method is used when the release candidate packages are validated before landing them.

The device I am using is flashed 10+ times a day.

What I need here are the following:

1) when the flashing is not successful then the tool should return with failure. Probably a simple post processing test tool to validate the flashing.

2) A tool or a written guide to factory reset/clean up the device. I have cleaned up the chaches in Recovery mode, used the UI "Factory reset" without result.

Revision history for this message
Zoltan Balogh (bzoltan) wrote :
Revision history for this message
Zoltan Balogh (bzoltan) wrote :

Checking the recovery logs there was a bogus directory structure (?) under the /userdata/user-data/phablet/.cache/com.ubuntu.gallery/ what messed up the flashing.

Removing that directory made the flashing work.

Still the falsher should not just fail silently.

Zoltan Balogh (bzoltan)
information type: Private Security → Public Security
information type: Public Security → Public
Changed in goget-ubuntu-touch (Ubuntu):
status: New → Confirmed
Changed in android (Ubuntu):
status: New → Confirmed
assignee: nobody → Sergio Schvezov (sergiusens)
importance: Undecided → High
tags: added: rtm14
tags: removed: rtm14
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

It seems rm can't read that deep into filenames while in recovery and bails on "format data". This isn't a problem in properly partitioned devices as the partition is actually formatted instead of rm'ed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.