ChannelsToFlash
9064
Comment:
|
9330
Update to arale device tarball testing
|
Deletions are marked like this. | Additions are marked like this. |
Line 86: | Line 86: |
With arale currently the device tarball stops the install of the rest of the system, so you first need to Flash the system normally to get the latest custom and ubuntu systems on, see | With arale currently the device tarball stops the install of the rest of the system, so you first need to Flash the system normally to get the latest custom and ubuntu systems on, see [[https://wiki.ubuntu.com/QATeam/ChannelsToFlash#Image_Testing_Channels|Image Testing Channels]] for more info, Then run the bit below. |
Line 91: | Line 91: |
/!\ To confirm the tarball is installed correctly cat /android/cache/device-build and it should match the image you installed. |
Flashing Devices
Contents
This is to confirm the command line you should use to freshly wipe your devices ready for testing different sections of the image.
You will need to install phablet-tools package on the version of ubuntu you are running.
sudo apt install phablet-tools
Flashing the Current Release
Image Testing Channels
These channels are used for silo and regression testing
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/bq-aquaris.en --recovery-image recovery.img
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/meizu.en --recovery-image recovery-arale.img
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus 4 and Nexus 7 (Mako and Flo):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/ubuntu
Nexus device need no recovery image as adb is not disabled by default in the recovery image.
Testing Custom Tarballs
These channels are used to flash pending custom tarballs for testing for approval.
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/bq-aquaris.en-proposed --recovery-image recovery.img
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/meizu.en-proposed --recovery-image recovery-arale.img
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus devices have a custom tarball but it is automatically added to the ubuntu tarball
Testing Device Tarballs
First download the required tarball. This will be linked to in email and via The CI Spreadsheet
You will then need to create a disable-gpg.sh script with the following lines.
#!/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
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/bq-aquaris.en --recovery-image recovery.img --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
With arale currently the device tarball stops the install of the rest of the system, so you first need to Flash the system normally to get the latest custom and ubuntu systems on, see Image Testing Channels for more info, Then run the bit below.
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/meizu.en --recovery-image recovery-arale.img --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
To confirm the tarball is installed correctly cat /android/cache/device-build and it should match the image you installed.
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus 4 and Nexus 7 (Mako and Flo):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-proposed/ubuntu --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
Nexus device need no recovery image as adb is not disabled by default in the recovery image.
Flashing the Next Release
Image Testing Channels
These channels are used for silo and regression testing
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/bq-aquaris.en --recovery-image recovery.img
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/meizu.en --recovery-image recovery-arale.img
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus 4 and Nexus 7 (Mako and Flo):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/ubuntu
Nexus device need no recovery image as adb is not disabled by default in the recovery image.
Testing Custom Tarballs
These channels are used to flash pending custom tarballs for testing for approval.
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/bq-aquaris.en-proposed --recovery-image recovery.img
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/meizu.en-proposed --recovery-image recovery-arale.img
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus devices have a custom tarball but it is automatically added to the ubuntu tarball
Testing Device Tarballs
First download the required tarball. This will be linked to in email and via The CI Spreadsheet
You will then need to create a disable-gpg.sh script with the following lines.
#!/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
BQ Aquaris e4.5 (Krillin):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/bq-aquaris.en --recovery-image recovery.img --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
BQ recovery.img is located at http://people.canonical.com/~jhm/barajas/recovery.img
Meizu MX4 (Arale):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/meizu.en --recovery-image recovery-arale.img --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
Meizu recovery-arale.img is the renamed recovery.img located at http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
Nexus 4 and Nexus 7 (Mako and Flo):
First enable developer mode on the device this is located in system-settings→About Phone→Developer Mode
adb reboot bootloader ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/ubuntu --device-tarball <path to device-tarball.tar.xz> --run-script ~/disable-gpg.sh
Nexus device need no recovery image as adb is not disabled by default in the recovery image.
QATeam/ChannelsToFlash (last edited 2016-05-04 08:16:05 by localhost)