New owner Avicii

Hello dear reader,

I’ve just received a second hand OnePlus Nord model AC2003.

Before messing out downloading a firmware update on the phone, I unticked the automatic install while the downloading has already started and it resulted in a firmware upgrade ready to install, but let’s hurry up to wait before proceeding !

So first, as i’m new to this brand and model, lets get some reading and basic testing :

If it wasn’t difficult to find out how to power on the device, powering it off was a bit more tricky !
I’ve ended with the long vol up button then power button. Let me know if there is a more straight way to do this.

Then I try to boot in recovery. I followed the guide to learn how to do this on this device and it worked, but there isn’t any useful info here.
After that, I tried to boot in fastboot mode, again, OK.

But I then read this :

Product_name : lito

and I think to myself, what have I bought ?

After further reading the internets, I realize it was a reference to the chip, shared with Billie model (OnePlus Nord N10 5G).

Can anyone confirm ?

For now, I’ve charged the phone up to 100% and it rest 24 hours to check ether the battery leak or not.

To be continued

Reserved for further explanations

in case you are not aware,

adb shell getprop

give many informations about the device an the android build…

1 Like

I did briefly check this previously, you are quoting product name but all installs are fundamental to device codename which you can check. Some further links in this guarded reply. Unable to install /e/OS on OnePlus Nord - #6 by aibd.

1 Like

lito is the unique product name quoted as TARGET_BOARD_PLATFORM and TARGET_BOOTLOADER_BOARD_NAME in https://github.com/LineageOS/android_device_oneplus_avicii/BoardConfig.mk`

Hello :slight_smile:

Thank you for those answer.
Indeed, it seems that all is normal, as your research tend to the same conclusion as me. And also with a visual exemple in the post pointed by aibd.

I will confirm with adb shell getprop once the 24 hours rest is over.

[DEVICE_PROVISIONED]: [1]
...
[config.disable_rtt]: [true]
...
[dev.bootcomplete]: [1]
...
[gsm.version.baseband]: [Q_V1_P14,Q_V1_P14]
[gsm.version.ril-impl]: [Qualcomm RIL 1.0]
... 
[init.svc.adbd]: [running]
...
[init.svc.bootanim]: [stopped]
[init.svc.boringssl_self_test32]: [stopped]
[init.svc.boringssl_self_test32_vendor]: [stopped]
[init.svc.boringssl_self_test64]: [stopped]
[init.svc.boringssl_self_test64_vendor]: [stopped]
[init.svc.boringssl_self_test_apex32]: [stopped]
[init.svc.boringssl_self_test_apex64]: [stopped]
...
[ro.boot.platform_name]: [SM7250]
...
[ro.boot.product.vendor.sku]: [lito]
[ro.boot.project_codename]: [avicii]
...
[ro.boot.vbmeta.device_state]: [locked]
...
[ro.boot.vbmeta.invalidate_on_error]: [yes]
[ro.boot.vbmeta.size]: [15424]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.veritymode]: [enforcing]
...
[ro.bootimage.build.fingerprint]: [OnePlus/Nord_EEA/Nord:12/RKQ1.211119.001/Q.GDPR.202312281624:user/release-keys]
[ro.bootimage.build.version.incremental]: [Q.GDPR.202312281624]
...
[ro.build.characteristics]: [nosdcard]
...
[ro.build.description]: [Nord_EEA-user 12 RKQ1.211119.001 Q.GDPR.202312281624 release-keys]
...
[ro.build.display.full_id]: [AC2003GDPR_11_F.23_2023122819090000]
[ro.build.display.id]: [AC2003_11_F.23]
[ro.build.display.ota]: [AC2003_11_F.23]
...
[ro.build.flavor]: [qssi-user]
[ro.build.hardware.version]: [11]
...
[ro.build.product]: [Nord_EEA]
...
[ro.build.user]: [root]
...
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.oplusrom]: [V12.1]
[ro.build.version.ota]: [AC2003_11.F.23_2230_202312281909]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [12]
[ro.build.version.release_or_codename]: [12]
[ro.build.version.sdk]: [31]
[ro.build.version.security_patch]: [2023-12-05]
[ro.build.version.svn]: [41]
...
[ro.crypto.state]: [encrypted]
...
[ro.facebook.partnerid]: [oneplus:3fc3fc1d-77f7-419a-82b4-8c4a1db849b6]
[ro.frp.pst]: [/dev/block/bootdevice/by-name/frp]
[ro.gfx.driver.1]: [com.qualcomm.qti.gpudrivers.lito.api30]
[ro.hardware]: [qcom]
[ro.hardware.egl]: [adreno]
[ro.hardware.keystore_desede]: [true]
[ro.hardware.vulkan]: [adreno]
...
[vold.storage.prepared]: [1]

[config.disable_rtt]: [true] : Cet appareil ne prends pas de congés (french pun)

[init.svc.boringssl_self_test : These self test are Sooo boring !

[ro.boot.product.vendor.sku]: [lito]
[ro.boot.project_codename]: [avicii] This what we where looking for

Woh, have you read this, it look like bad news for me !

why it is currently now stuck to /e/OS android 14 based…

Do you mean the chance to have an upgrade to further android majors within the e/OS ecosystem are very low for Avicii ?

If so, there will however be security update until e/OS abandon A14 …

And inbetween, there could be someone becomming a maintainer for this LOS repo …
It’s beautifull to dream \o/

yes,
also if murena sold it in the past, they may give effort to upgrade it as long as the kernel allow it.

1 Like

so now do you have A14 on your phone and you are able to put eOS based on a14??

just asking as i wasn’t able to do that… but i’ve been able to put A12 and then put eOS based on A12…

@pablohc86
in your case (/e/OS a12 already installed), you should be abble to simply upgrade /e/OS
(that include the “latest but not higher to /e/” OnePlus firmware parts)
download e-3.1.1-a14-20250828521479-official-avicii.zip (that is designed for update or install from recovery)
( not "IMG-e-3.1.1-a14-20250828521479-official-avicii.zip, that is designed for easy new install )
following [HOWTO] Upgrade my /e/OS to major Android version without loosing /data

.

listing partitions included in the /e/OS-a14 update file show modem and so on…

piero@HP-p6-2038fr:~/Téléchargements$ ./payload-dumper-go -l e-3.1.1-a14-20250828521479-official-avicii.zip
Please wait while extracting payload.bin from the archive.
payload.bin: /tmp/payload_878966459.bin
Payload Version: 2
Payload Manifest Length: 109712
Payload Manifest Signature Length: 267
Found partitions:
abl (225 kB), aop (197 kB), bluetooth (242 kB), boot (101 MB), devcfg (49 kB), dsp (67 MB), dtbo (25 MB), featenabler (90 kB), hyp (414 kB), imagefv (537 kB), keymaster (242 kB), logo (344 kB), modem (179 MB), odm (26 MB), product (614 MB), qupfw (57 kB), recovery (101 MB), storsec (20 kB), system (1.7 GB), system_ext (545 MB), tz (3.1 MB), uefisecapp (127 kB), vbmeta (8.2 kB), vbmeta_system (4.1 kB), vendor (552 MB), xbl (3.5 MB), xbl_config (82 kB)

1 Like

Hello, I don’t have enough time to experiment for the moment, I hope to be able to do so soon.