OnePlus 8T (kebab): upgrade from /e/OS 4.0 A14 to 4.0 A16 – should the new recovery.img be flashed first?

[davidvanwijk]

Hi,

I’m currently running:

Device: OnePlus 8T (kebab)
Current ROM: /e/OS 4.0 Android 14 community
Target ROM: /e/OS 4.0 Android 16 community

The current download page provides only:

• e-4.0-a16-20260610633937-community-kebab.zip
• recovery-e-4.0-a16-20260610633937-community-kebab.img

However, the installation guide still says to unzip a recovery ZIP and flash:

• dtbo.img
• vbmeta.img

Those files are no longer provided.

Since this is NOT a first installation from OxygenOS but an upgrade from an existing /e/OS installation, what is the correct procedure?

1. Keep the existing /e/OS recovery (4.0 A14), factory reset and use:
   Apply Update → ADB sideload

or

2. Flash the new recovery.img first, then sideload the ROM?

If option 2 is correct, what is the exact fastboot command for kebab?

Thanks!

[piero]

You already have the custom dtbo.img and vbmeta.img flashed on your device because you already did the /e/OS install in the past.

So from my point if vue,

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

you can have a go upgrading simply choosing local update from the device → settings → system updater → 3dot menu → local update

This will first replace the current recovery, then install the /e/ build…

@piero

In order to be sure it is really possible in your case, you must answer those 4 questions :

[davidvanwijk]

Current build:
4.0-a14-20260611634539-community-kebab

Trying to sideload:
e-4.0-a16-20260610633937-community-kebab.zip

Recovery says:

Update package is older than the current build,
expected a newer than the timestamp 1781188147
but package has timestamp 1781090923
and downgrade not allowed.

Is the published A16 build older than the latest A14 build, or should the downgrade protection be bypassed?

[aibd]

@davidvanwijk

Is the published A16 build older than the latest A14 build,

Yes,

4.0-a14-20260611634539-community-kebab
4.0-a16-20260610633937-community-kebab.zip

a14-2026-06-11-634539

a16-2026-06-10-633937

[piero]

You may try to first flash the new recovery using fastboot…

[davidvanwijk]

Thanks. Before I do that:

Thanks! I checked question 3 and the ZIP indeed contains payload.bin.

However, using ADB sideload from recovery results in:

Update package is older than the current build.
Expected timestamp 1781188147
Package timestamp 1781090923
Downgrade not allowed.

My current build is:

4.0-a14-20260611634539-community-kebab

while the available A16 build is:

4.0-a16-20260610633937-community-kebab

Should I:

• ignore the timestamp warning (Yes)?

• use Local Update instead?

• or wait for a newer A16 build?

[piero]

@davidvanwijk

use Local Update instead?

The recommended way before all.

@davidvanwijk

ignore the timestamp warning (Yes)?

If the device propose to install anyway, you may try choosing yes.

@davidvanwijk

or wait for a newer A16 build?

For sure it will work.

[davidvanwijk]

sorry and thanks. I posted a new question before reading your answer …. Stupid, sorry

[davidvanwijk]

I tried Local Update.

The ZIP is imported successfully.

After confirming installation, nothing happens.

The updater simply returns to this screen.

Recovery sideload still reports:

Package is older than current build.
Downgrade not allowed.

Is this expected with the current A16 community build?

[davidvanwijk]

Local Update also refuses to install the current A16 build. It imports correctly, but after choosing Install it returns to the updater and eventually reports that the package cannot be installed. I’ll wait for the upcoming 4.1 A16 build and try again. Thanks for your help!