udf with --custom-tarball that is too big: cannot pass bootsplash on reboot
Bug #1582325 reported by
Kyle Nitzsche
This bug report is a duplicate of:
Bug #1568889: OTA and u-d-f fail if image is too big for the system partition.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
Critical
|
Unassigned | ||
system-image (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Summary: I am installing my own customized tarball to cooler with udf using --customized-
Rebooting from recovery menu leaves device stuck in bootsplash.
We don't want this to happen on a channel.
Details to follow.
To post a comment you must log in.
To reproduce:
== I flashed my cooler using the SP_FLASH tool according to instructions here: https:/ /wiki.canonical .com/UES/ CE/Projects/ Avila/FlashTool
== Using device GUI, I enabled dev mode, set power > lock when idle > Never, and installed the latest system update which left me with:
phablet@ ubuntu- phablet: ~$ system-image-cli -i touch/stable/ bq-aquaris- pd.en -38-10- vivid
current build number: 3
device name: cooler
channel: ubuntu-
last update: 2016-05-16 15:18:01
version version: 3
version ubuntu: 20160408.1
version tag: OTA-10.1
version device: 20160330.0
version custom: 20160330-
== adb reboot-bootloader, fastboot boot recovery-cooler.img and rm /cache/recovery*
== install customized tarball like this: touch/stable/ bq-aquaris- pd.en \ puritine_ custom. tar.xz \
$ adb reboot-bootloade
$ fastboot boot recovery-cooler.img
$ ubuntu-device-flash touch \
--channel ubuntu-
--recovery-image recovery-cooler.img \
--device cooler \
--custom-tarball 0-7-13-
--run-script skip-sig.sh
WHERE: puritine_ custom. tar.xz puritine_ custom. tar.xz image/skip- gpg-verificatio n image-upgrader /cache/ recovery/ ubuntu_ command
$ ls -l 0-7-13-
-rw-rw-r-- 1 knitzsche knitzsche 558581464 May 13 16:50 0-7-13-
AND:
$ cat skip-sig.sh
#!/bin/bash
adb shell touch /etc/system-
adb shell /sbin/system-
THIS ^ WORKED FINE
== Switched to rc-propposed as follows:
$ adb reboot-bootloader touch/rc- proposed/ bq-aquaris- pd.en \
$ ubuntu-device-flash touch \
--channel ubuntu-
--recovery-image recovery-cooler.img \
--device cooler \
--bootstrap
4. complete oobe
5. enable dev mode, lock when idle = Never and rm ~/.customized
== install customized tarball again
last_log.1 last_log.3 log
/cache/recovery # ls -a
. last_install last_log last_log.2 last_log.4
.. last_kmsg last_log.1 last_log.3 log
(hmm, I expected to see tarballs here...)
# cd cache/recovery/
# rm /*
$ adb reboot-bootloader touch/rc- proposed/ bq-aquaris- pd.en \ puritine_ custom. tar.xz \ touch/rc- proposed/ bq-aquaris- pd.en channel and server https:/ /system- image.ubuntu. com to device cooler /.cache/ ubuntuimages/ ubuntu- touch/rc- proposed/ bq-aquaris- pd.en/cooler/ version- 51.tar. xz to device /gendarmarie/ flash/0- 7-13-puritine_ custom. tar.xz to device /.cache/ ubuntuimages/ gpg/image- master. tar.xz to device /.cache/ ubuntuimages/ gpg/image- signing. tar.xz to device /.cache/ ubuntuimages/ ubuntu- touch/rc- proposed/ bq-aquaris- pd.en/cooler/ version- 51.tar. xz to device /.cache/ ubuntuimages/ pool/device- e94e1b09f402d05 326f5ead27efbe. ..
$ fastboot boot recovery-cooler.img
downloading 'boot.img'...
OKAY [ 0.372s]
booting...
OKAY [ 0.068s]
finished. total time: 0.439s
$ ubuntu-device-flash touch \
> --channel ubuntu-
> --recovery-image recovery-cooler.img \
> --device cooler \
> --custom-tarball 0-7-13-
> --run-script skip-sig.sh
2016/05/16 12:43:21 Device is |cooler|
2016/05/16 12:43:21 Flashing version 51 from ubuntu-
2016/05/16 12:43:22 Start pushing /home/knitzsche
2016/05/16 12:43:22 Start pushing /home/knitzsche
2016/05/16 12:43:22 Start pushing /home/knitzsche
2016/05/16 12:43:22 Start pushing /home/knitzsche
2016/05/16 12:43:24 Done pushing /home/knitzsche
2016/05/16 12:43:24 Start pushing /home/knitzsche