OnePlus 8T A15 from e/OS 3.2 A14

Community Forum
1

Is an update to e/OS A15 possible from e/OS Android 14 3.2-a14-20251025540136-community-kebab. Some devices require stockrom

phone
phone427Ă—374 173 KB

2

/e/ build’s metadata says e-3.2-a15-20251023539369-community-kebab.zip
is based on OnePlus8T:14/UKQ1.230924.001/R.1a46c89-1_1 firmware
payload-dumper-go says it only include :

piero@HP-p6-2038fr:~/Téléchargements/bidoulles/extract builds content$ ./payload-dumper-go -l e-3.2-a15-20251023539369-community-kebab.zip
Please wait while extracting payload.bin from the archive.
payload.bin: /tmp/payload_759027616.bin
Payload Version: 2
Payload Manifest Length: 99712
Payload Manifest Signature Length: 267
Found partitions:
boot (101 MB), dtbo (25 MB), odm (87 MB), product (587 MB), recovery (101 MB), system (1.6 GB), system_ext (554 MB), vbmeta (8.2 kB), vbmeta_system (4.1 kB), vendor (542 MB)

.

Lineage says
first upgrade firmware without touching /data
then upgrade custom OS (by locale update or recovery sideloading)

Update firmware on

OnePlus 8T

kebab

warning

Warning: These instructions are NOT for carrier branded variants.

  1. Download the latest Android 13/14 full stock ROM update from Oxygen Updater
  2. Extract stock ROM using payload-dumper-go
  3. Boot up LineageOS recovery
  4. Go to “Advanced” → “Enable ADB”
  5. Check your DDR type using the following command: adb -d shell getprop ro.boot.ddr_type, or in case getprop returns an empty value, use: adb -d shell cat /proc/devinfo/ddr_type instead
  6. Go to “Advanced” → “Enter fastboot”

7.warning*

8.Warning:* The “Enter fastboot” option may not be present on older LineageOS recovery builds and it cannot be substituted with “Reboot to bootloader”.

  1. Execute following commands:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
  1. Flash correct XBL files

11.warning*

12.Warning:* Flashing wrong XBL files will brick your phone.

  • For DDR type 0 (DDR4):
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
  • For DDR type 1 (DDR5):
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img

.

in conclusion, Dirty upgrade is not recommended for this device,
BUT you can try it anyway ( no risk, no fun ! )

1 Like
3

I suppose the short answer is no :thinking:. I am not so experienced with this kind of stuff. I have to do pretty difficult things to upgrade within e/OS from 3.2 a14 (latest) to 3.2 a15 with the risk of bricking my device…?

4

But what if I accept loss of all data? Can I upgrade from e/OS 14 to e/OS 15?

5

Hi @davidvanwijk refer to my post Feedback for v3.2 - #14 by radprec .

It is possible to do a dirty upgrade without data loss. I know an example is not a rule, but it points out the possibility.

6

All the way you need to reach android 14 that is the final firmware version for this device

The way proposed by Lineage look easier than have to restart from scratch :
reflashing the all firmware, unlocking the bootmoader again, reflashing a custom recovery an finally reflashing /e/.

[HOWTO] Upgrade my /e/OS to major Android version without loosing /data