Hi,
this is my first post in this forum, so I hope to respect all the community guidelines.
After very good experiences with flashing a Nexus 5 with /e/, yesterday evening I tried to flash my Xperia XA2 following the steps on
https://doc.e.foundation/devices/pioneer/install
It did not went well so I hope to find some help or suggestions here.
In short
In the section “Pre-install instructions” the step “Sideload the copy-partitions-20210323_1922.zip”
did not work out well. After rebooting, the phone was stuck in a boot loop, but it was possible to recover to Android 9 via a menu on the phone. After restarting the procedure from “Temporarily Booting a custom recovery using fastboot” and rebooting the phone, the phone is stuck with “Your device is corrupted. It can’t be trusted and will not boot.”
Details
Setting:
- Sony Xperia XA2 (H3113)
- Android 9
- e-OS: e-0.20-q-20211216151800-dev-pioneer.zip
- Recovery-image: recovery-e-0.20-q-20211216151800-dev-pioneer.img
- pre-install-instructions: copy-partitions-20210323_1922.zip
Section: Unlocking the bootloader
user@host:~/Downloads/e-os$ sudo adb reboot bootloader
user@host:~/Downloads/e-os$ sudo fastboot devices
CABC12345C fastboot
user@host:~/Downloads/e-os$ sudo fastboot oem unlock 0xUNLOCK_CODE
...
OKAY [ 1.933s]
finished. total time: 1.933s
Section: Temporarily Booting a custom recovery using fastboot (1st run)
user@host:~/Downloads/e-os$ sudo adb reboot bootloader
user@host:~/Downloads/e-os$ sudo fastboot devices
CABC12345C fastboot
user@host:~/Downloads/e-os$ sudo fastboot flash boot recovery-e-0.20-q-20211216151800-dev-pioneer.img
target reported max download size of 536870912 bytes
sending 'boot_b' (23461 KB)...
OKAY [ 1.047s]
writing 'boot_b'...
OKAY [ 0.191s]
finished. total time: 1.238s
Please note: In the first run ‘boot_b’ was sent.
Section “Pre-Install instructions” (1st run)
The phone was still connected to the PC, but did not respond to any touch on the display or pressing any button, so I thought, that the commands
- On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
- On the host machine, sideload the package using: adb sideload copy-partitions-20210323_1922.zip
are kind of “either… or” and chose the second option, which led to:
user@host:~/Downloads/e-os$ sudo adb sideload copy-partitions-20210323_1922.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
The device did not react and so I disconnected the phone from the PC and tried a reboot. Afterwards, the phone was stuck in a boot-loop and after a couple of restarts, the option of a factory reset or “Try again” was presented on the smartphone’s screen. After factory reset, the Android Version 9 was still present. The bootloader was still unlocked.
Section: Temporarily Booting a custom recovery using fastboot (2nd run)
user@host:~/Downloads/e-os$ sudo adb reboot bootloader
user@host:~/Downloads/e-os$ sudo fastboot devices
CABC12345C fastboot
user@host:~/Downloads/e-os$ sudo fastboot flash boot recovery-e-0.20-q-20211216151800-dev-pioneer.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23461 KB)...
OKAY [ 0.929s]
writing 'boot_a'...
OKAY [ 0.190s]
finished. total time: 1.119s
Please note: In the second run ‘boot_a’ was sent.
Section “Pre-Install instructions” (2nd run)
Since in the first run I was not able to follow the Pre-install instructions I disconnected the phone form the PC to check whether in the recovery image the option “Apply Update” and “Apply form ADB”
- On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
- On the host machine, sideload the package using: adb sideload copy-partitions-20210323_1922.zip
Then a reboot did not work and the message “Your device is corrupted. It can’t be trusted and will not boot.” is displayed.
After reconnecting to the PC the device is not found
user@host:~/Downloads/e-os$ sudo fastboot devices
user@host:~/Downloads/e-os$
and the device does not respond to the volume down and power button.
Have I “hard-bricked” my phone or do you see any chance for recovery?
I am happy for any suggestions.