Installation questions for an ONEPLUS 12 waffle

/e/OS Devices OnePlus
1

Hello all,
I am trying to install /e/ OS e-3.4-a15-20260115569564-community-waffle on my new device.
It runs for the moment Oxygen OS Android 15.
But in the installation instructions is written:

  • Before following these instructions please ensure that the device is on the latest Android 16 firmware.

But I am wondering if it is good to upgrade to Stock Android 16 before installing /e/OS Android 15… wouldn’t this trigger anti-rollback functions or so? Or can I just go ahead and install /e/OS Android 15 on my actual Oxygen OS Android 15?
Thanks for your enlightenments.

2

have a look into the .ZIP /META-INF/com/google/android/updater-script, you will find the reference of the stock version on witch /e/ is based.

3

Merci beaucoup. But I didn’t really understand it. I guess it’s Android 15, but not sure. Can you take a look, please?

/META-INF/com/google/android/metadata:

details below

ota-property-files=payload_metadata.bin:4951:211212,payload.bin:4951:2808119488,payload_properties.txt:2808124497:156,apex_info.pb:2552:1248,care_map.pb:3847:1057,metadata:69:710,metadata.pb:847:1657
ota-required-cache=0
ota-streaming-property-files=payload.bin:4951:2808119488,payload_properties.txt:2808124497:156,apex_info.pb:2552:1248,care_map.pb:3847:1057,metadata:69:710,metadata.pb:847:1657
ota-type=AB
post-build=OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
post-build-incremental=1768510978
post-sdk-level=35
post-security-patch-level=2026-01-01
post-timestamp=1768510978
pre-device=OP5929L1,OP595DL1

care_map.pb:

details below

‹
odm
2,0,609822ro.odm.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
“
product
2,0,185301ro.product.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
‘
system
2,0,387158ero.system.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
™

system_dlkm2,0,2457 ro.system_dlkm.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
™

system_ext
2,0,134441ro.system_ext.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
‘
vendor
2,0,252741ero.vendor.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys
š

vendor_dlkm 2,0,30364 ro.vendor_dlkm.build.fingerprint"^OnePlus/CPH2581EEA/OP595DL1:15/AP3A.240617.008/U.R4T3.cfc6a2_1337040_1337041:user/release-keys

Is there any useful information? Does the “15” which appears several times indicate that it is based on Android 15, where as no “16” appears?

Thanks!

4

/META-INF/com/google/android/metadata
is not
/META-INF/com/google/android/updater-script

but both refer to 15/AP3A.240617.008/ that is an android 15 version

5

So I could install /e/OS Android 15 on Oxygen OS Android 15?

6

i think so, but i don’t want afirm that

1 Like
7

Ok, so I am trying to install /e/OS Android 15 on it. But the Oneplus 12 device doesn’t respond to the fastboot commands. When I type ´fastboot devices´ it shows the number, but ´fastboot flashing unlock´ give an error. How can I proceed from here?

Here is the error:

FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
8

check bootloader status by running :

fastboot oem device-info

fastboot flashing get_unlock_ability
9

It gives me the same error:

fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed

But I am searching for about two hours xda and everywhere else. It seems that the OxygenOS Android 15 firmware which ends with .863 has a fastboot problem and cannot be unlocked :enraged_face:

10

I’m also curious if installing /e/OS over Oxygen 16 as indicated in the installation documentation will trigger anti-rollback measures.

11

The advice is specific

  • The required version is Android 16 , which may be lower than the /e/OS version you are about to install - this is not an error! If there are multiple updates of that version (e.g. security updates), make sure to use the latest!
  • If you need to upgrade or downgrade your device, please search online for guides. We are unable to provide specific instructions here and on our support platforms.

Rollback is complex and the hazards differ by manufacturer and device. When /e/OS a16 arrives perhaps one would avoid this “leap of faith”.

1 Like
12

I didn’t want to test that… But with Oxygen OS 15 you can’t unlock the bootloader, see my post above. It seems that Oneplus broke that when they tried to fix a security flaw for SMS.

Well, /e/ OS is on Android 15 for the moment. So installing it overtop an Android 16 Stock is contrary to every installation instruction, wether on LOS or e.foundation…

So my solution was: upgrading to OxygenOS Android 16, then installing LOS 23 (Android 16) - and waiting for /e/OS Android 16 to come out :sweat_smile:

2 Likes
13

Good idea. I updated to OOS 16 and despise the UI. I was debating installing vanilla YAAP, but they seem to be having issues with A16. In the end, I think installing /e/OS would be preferable for privacy.

It’s fine to install /e/OS over LOS instead of over OOS once /e/OS reaches A16?

14

I think so, since it’s based on LOS.

1 Like
15

Just noticed that A16 is released for OnePlus 12. Curious if anyone has tried flashing e/OS/ A16 over latest Lineage A16 builds. If so, how did it go? Thinking of trying to do that soon.

16

I just flashed the latest e/OS/ A16 over latest Lineage OS 23 but am getting the error “Screen lock was already changed. Please choose a different lock method…” when I try to set a PIN. Another thread indicated it could be because I didn’t log out of Google accounts before installing e/OS/. I tried factory resetting e/OS/, but that didn’t resolve the issue. Any fixes for this would be greatly appreciated!

17

If this was the case it would trigger Factory Reset Protection, forum threads on the subject have hashtag frp. The install page should tell that Google account, all passwords and PINs must be removed before reinstall /e/OS same applies for Lineage install.

The fix is to return to return to Stock android if this is where the account preexisted [1], ensure to fully make contact with the Google account, remove the account and all passwords and PINs then reinstall /e/OS.

[1] As you installed over Lineage do you know for sure the account was created in that environment with Gapps or earlier Stock? The answer would determine where to remove the account.

2 Likes
18

Thanks for the reply!

Is FRP unique to e/OS/ or inherited from Lineage OS? Asking because I didn’t have this issue on Lineage, so if it’s also an issue with Lineage then I must’ve signed out on Stock before installing Lineage since I had PIN + Fingerprint enabled on Lineage.

So the first thing I’ll try is reinstalling Lineage, logging into my Google accounts, removing them, and then reinstalling e/OS/ to see if I can then enable PIN + Fingerprint. Make sense as a first strategy?

1 Like
19

This from Install LineageOS on waffle | LineageOS Wiki

  1. Remove all Google accounts from your device to avoid “Factory reset protection”

FRP initially “belongs” to Google and the component is stored in a partition untouched by AOSP install.

Readers affected will be interested to hear how it works out for you.

1 Like
20

Just clean flashed Lineage 23 and am still getting the same error, so it looks like I need to flash Oxygen OS A16 and see if that fixes it.

I’d usually use MSM tool for that, but don’t think that’s a viable option with the ARB fiasco. Can anyone help me get back to Oxygen?