Display an error message when applying a tarball fails

[Jean-Baptiste Lallement]

The option --custom-tarball doesn't work. The tarball is pushed correctly bug the custom bits are not installed.

This happened because gpg verification of the custom tarball failed. Create a script containing:

-----
#!/bin/bash
adb shell mkdir -p /etc/system-image
adb shell touch /etc/system-image/skip-gpg-verification
adb shell system-image-upgrader /cache/recovery/ubuntu_command
adb reboot
-----

and calling u-d-f touch with --run-script=<script> fixed the problem.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-device-flash 0.16-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 3 13:44:07 2015
InstallationDate: Installed on 2013-09-03 (545 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
SourcePackage: goget-ubuntu-touch
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Sergio Schvezov (sergiusens)]

On martes 3 de marzo de 2015 09h'46:18 ART, Jean-Baptiste Lallement wrote:
> Public bug reported:
>
> The option --custom-tarball doesn't work. The tarball is pushed
> correctly bug the custom bits are not installed.

If you use a recovery that checks for signed images it will fail most of
the time, can you make sure this is the case from the recovery logs?

[Jean-Baptiste Lallement (jibel)]

Could you tell me where are these logs?

[Jean-Baptiste Lallement (jibel)]

/android/cache/recovery/log after a fresh flash with custom.

[Dave Morley (davmor2)]

Sergio the recovery only unlocks adb access I don't think it handles gpg untrusted too is there no way the tool can handle that part?

[Dave Morley (davmor2)]

jibel sergio I have a script for that that I run for device tarballs I assume that can be run for custom too right?