aibd, thanks foor the help. I finally managed to get 1 phone recognised by the MSM tool by pressing both the volume + and - and power buttons for mayby 20 seconds like Ytube21 suggested in this thread: https://xdaforums.com/t/how-to-reboot-to-qualcomm-edl-mode-without-adb.4469533/ that you found.
Now I have a working phone with adroid Nord OxygenOS 11.1.10.10.AC01BA on it. I will upgrade it to the latest android version and then try to install E os on it.
1 Like
Before somethuing goes wrong again, I have a question about the Android version. I have android 11 installed with build no 11.1.1.10.AC01BA (model is AC2003). I read in the E install guide (https://doc.e.foundation/devices/avicii/install) that I have to make shure that I upgrade to the latest version of Andoid 12 before starting the installation of E OS. But when I go to system updates in the device it says that the system is up to date. As I understand, it depends one Oneplus to enroll android 12 to my device and since I just managed to roll back to android 11, I suspect, that waiting for Oneplus can be a long wait.
Now when I follow the link in the installation guide to downloads for Avicii, I find Android Q, R and S. Am I correct in assuming that Android Q stands for Android 10, Android R for 11 and S for 12? And if so, is it safe to download the installation files for Android R for my device with 11.1.1.10.AC01BA on it and install them?
You are correct about Android versions e/OS + Android OS version names and numbers? - #3 by aibd
There is Oxygen Updater to help you update, discussed here https://community.oneplus.com/thread/1591794
And some more questions ;-). I do not understand this part of the installation guide:
Flashing additional partitions
Warning: This platform requires additional partitions to be flashed for recovery to work properly.The steps to flash the partitions are given below
Tip: In case the partition files are not available in the /e/OS recovery zip, users flashing the Android 13 or /e/OS T build, can try and download them from the LineageOS wiki install page specific to this device.
- First unzip the /e/OS Recovery file linked in the section marked
Downloads for avicii. The following files would show up in the location where you unzipped the contents of the eRecovery zip file
- dtbo.img
- vbmeta.img
- Next we manually reboot into bootloader or download mode
- With the device powered off
- hold Volume Up + Volume Down + Power.
- Flash the downloaded image files to your device by typing (replace
<...>with the actual filenames):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img
Am I correct in assuming that since I reverted to stock rom via de MSM tool, there are no partitions to be flashed? When I tried to install E OS on my own phone it went wrong because there appaerantly were 2 partitions, but after rolling bakc to stock rom via the MSM tool installation was a breeze and I did not flash different partitions. I think the above part was added to the guide later. Should I just ignore this part?
The instructions are a fit with improved packaging of the ROM which happened hand in hand with the introduction of Android 13 (T). These instructions were updated about August / September 2023.
Notice the different package resources on the more recent builds in the downloads page https://images.ecloud.global/dev/avicii/
No, the current /e/ ROM e-1.19.1-t-20240112373116-dev-avicii.zip + Recovery and boot img should be installed after correct preparation with correct dtbo.img and vbmeta.img
I read that thread before, but when I look in system updater it seemed to me it’s already working with Oxygen updater. I will look into it tomorrow.
Thanx for the help. Again.
OK, I updated to Andoid 12 with the help of the Andiod updater app.In the new Android version it is not very clear which version has been installed, but I found this in “About Device”: OxygenOS 12.1 AC2003_11_F.22. I hope that is the latest version. Unfortunately, I haven’t got the time to finish installing E OS because I’m giong on a holiday for two weeks, but afterwards I’ll be back to finish the project. Cheers.
Ok, I’m back and want to finish installing E… Now the devices I have have the latest security update for android 12 installed.
Downloaded the latest e-1.19.1-s-20240109372023-stable-avicii.zip file and extracted it. Then I flashed de dbto and vbmeta files with these commands:
fastboot flash dtbo dtbo-e-1.19.1-s-20240109372023-stable-avicii.img
fastboot flash vbmeta vbmeta-e-1.19.1-s-20240109372023-stable-avicii.img
That seemed to work:
C:\Platformtools\Oneplus\recovery-IMG-e-1.19.1-s-20240109372023-stable-avicii>fastboot flash dtbo dtbo-e-1.19.1-s-20240109372023-stable-avicii.img
Sending 'dtbo' (24576 KB) OKAY [ 0.555s]
Writing 'dtbo' OKAY [ 0.095s]
Finished. Total time: 0.670s
C:\Platformtools\Oneplus\recovery-IMG-e-1.19.1-s-20240109372023-stable-avicii>fastboot flash vbmeta vbmeta-e-1.19.1-s-20240109372023-stable-avicii.img
Sending 'vbmeta' (8 KB) OKAY [ 0.010s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.020s
Then I flashed the recovery file and that seemed to work as well:
C:\Platformtools\Oneplus\recovery-IMG-e-1.19.1-s-20240109372023-stable-avicii>fastboot flash recovery recovery-e-1.19.1-s-20240109372023-stable-avicii.img
Sending 'recovery' (98304 KB) OKAY [ 2.180s]
Writing 'recovery' OKAY [ 0.310s]
Finished. Total time: 2.508s
Started to get exited that it would work, but alas. I tried to reboot to recovery, but I could only reboot to bootloader.
If I walk through the menu to "power off" and choose that by clicking the power button the screen turns
black immediately, but I don't think it really powers off. When I use the power down and power off
combination it restarts to bootloader. When in bootloader mode I navigate to "recovery mode" and choose
that, I also return to bootlaoder mode.
The device is recognised in fastboot mode.
I wonder what went wrong this time? Did installing the recovery image fail? I got no failure notices. I hope
there is some quick fix to this, because I have spent so much time already unbricking the devices and I
was hoping installing E would work this time.Looks like the device was bricked again. Whatever I did, it only returned to bootloader mode. So I used the MSM tool to revert to stock again. I’m glad that works fluently ;-).
Since this is appearently not working, is it a good idea to try the older version of Android 11 that worked before? I found threads in different forums that experienced a lot of difficulties with Android 12. I read that Oneplus and Oppo merged and they tried to merge the Oneplus and Oppo versions of Android, which is problematic. So I have the urge to stay away from Android 12.
One possibility, where recovery failed to boot is that the data partition is still “contaminated” by stuff from a previous Android version.
Two things would help rule that out. Factory reset after running MSM tool and running fastboot -w (again wipes data) before or after flashing recovery image.
Are you reluctant to go with Android 13 (T) ?
You are probably aware of all the helpful links off https://wiki.lineageos.org/devices/avicii/. Note that these pages are updated for Lineage 20 (… 13 … T).
Edit the pages today are updated for Lineage 21.
You must reboot direcly to recovery
1 Like
On a Oneplus One I find the button press to leave fastboot mode is hold Volume Down + Power.
To boot to Recovery is also hold Volume Down + Power.
However to enter Recovery, I must release both buttons as the screen goes black, press both again and release both buttons as soon as the device vibrates.
1 Like
I tried the factory reset and running fastboot -w. When I ran the fastboot -w command, I got the following error:
C:\Platformtools>fastboot -w
Erasing ‘userdata’ OKAY [ 0.332s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Platformtools\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
I really don’t know what it means, but I tried installing the recovery anyway with the same result as before.
By the way, I do not have a simcard installed in the devices. I seem to vaguely remember there could be a problem with that. Could that have anything to do with it?
What is the output of fastboot --version ? [1]
I found the error message crop up twice on the forum.
- Fastboot: error: cannot generate image for userdata (SOLVED)
- Add a warning to /e/ install instructions to avoid fastboot -w failing?
I do use a SIM card when I install, but I am not aware of it being critical Edit, use of the SIM card to make connections on manufacturer OS is actually recommended on the LineageOS install page.
[1] Currently 34.0.5 (October 2023)
It was an old version:
C:\Platformtools\Oneplus\recovery-IMG-e-1.19>fastboot --version
fastboot version 33.0.3-8952118
Installed as C:\Platformtools\platform-tools\fastboot.exe
I updated the version and now fastboot -w seems to work although the phrase “Erase succesfull, but not automatically formatting. File system type raw not supported” may mean it didn’t work completely?
C:>fastboot -w
Erasing ‘userdata’ OKAY [ 0.836s]
F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 211321752 (103184 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
“”
[f2fs_init_sit_area: 638] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 672] Filling nat area at offset 0x00e00000
[f2fs_add_default_dentry_root:1255] Writing default dentry root, at offset 0x1c600
[f2fs_write_root_inode:1300] Writing root inode (hot node), offset 0x1c000
[f2fs_write_default_quota:1389] Writing quota data, at offset 0001c601, 0001c602
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1c001
[f2fs_write_default_quota:1389] Writing quota data, at offset 0001c603, 0001c604
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1c002
[f2fs_write_default_quota:1389] Writing quota data, at offset 0001c605, 0001c606
[f2fs_write_qf_inode:1438] Writing quota inode (hot node), offset 0x1c003
[f2fs_update_nat_default:1475] Writing nat root, at offset 0x00000e00
Info: Overprovision ratio = 0.450%
Info: Overprovision segments = 232 (GC reserved = 229)
[f2fs_write_check_point_pack: 854] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 942] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 956] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 968] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 979] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 987] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1007] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1028] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1047] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1080] Writing super block, at offset 0x00000000
Info: format successful
Sending ‘userdata’ (97 KB) OKAY [ 0.000s]
Writing ‘userdata’ OKAY [ 0.000s]
wipe task partition not found: cache
Erasing ‘metadata’ OKAY [ 0.000s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 7.112s
So I tried again to flash the recovery:
C:\Platformtools\Oneplus\recovery-IMG-e-1.19>fastboot flash dtbo dtbo-e-1.19.1-s-20240109372023-stable-avicii.img
Sending ‘dtbo’ (24576 KB) OKAY [ 0.592s]
Writing ‘dtbo’ OKAY [ 0.141s]
Finished. Total time: 0.765s
C:\Platformtools\Oneplus\recovery-IMG-e-1.19>fastboot flash vbmeta vbmeta-e-1.19.1-s-20240109372023-stable-avicii.img
Sending ‘vbmeta’ (8 KB) OKAY [ 0.016s]
Writing ‘vbmeta’ OKAY [ 0.000s]
Finished. Total time: 0.047s
C:\Platformtools\Oneplus\recovery-IMG-e-1.19>fastboot flash recovery recovery-e-1.19.1-s-20240109372023-stable-avicii.img
Sending ‘recovery’ (102400 KB) OKAY [ 2.267s]
Writing ‘recovery’ OKAY [ 0.536s]
Finished. Total time: 3.349s
Alas, the same result. Only fastboot mode. I can’t start recovery by holding the power and volume down buttons and releasing them as you described nor via the fastboot mode menu 
I’m very close to giving up.
An advantage of the Android T builds is that they are said to contain vendor blobs, this might well be a workaround to the uncertainties apparently found with the Android 12 firmware.
I ran payload-dumper-go on e-1.19.1-t-20240112373116-dev-avicii.zip.
I found even more partitions than I had expected
$ ./payload-dumper-go e-1.19.1-t-20240112373116-dev-avicii.zip
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 (66 MB),
product (499 MB),
qupfw (57 kB),
recovery (101 MB),
storsec (20 kB),
system (1.6 GB),
system_ext (395 MB),
tz (3.1 MB),
uefisecapp (127 kB),
vbmeta (8.2 kB),
vbmeta_system (4.1 kB),
vendor (877 MB),
xbl (3.5 MB),
xbl_config (82 kB)
I don’t quite understand what you mean by vendors blobs and why that could be a workaround, but I will try installing the T build. But do I have to upgrade the stock to Android 13 then first? I did not find an update to Android 13 for the European version (AC 2003) with Oxygen Updater. Only for the Indian version. I read somewere that it became available for the AC20023 but not how to get it.
Negative. From Post #59 (links from which I recommend careful study first) the Lineage install page includes
Warning: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Quoting Week 35, 2023 : Development and Testing Updates
/e/OS T builds
Status :Build and testing
Team is working on adding firmware along with the T builds. This will make it easier for users to flash the builds without having to flash the stock ROM first.
Vendor blobs refers to largely proprietary parts which we are used to seeing only in the manufacturer’s firmware, now seen in the T builds.
The output above from payload-dumper-go suggests that the /e/OS Android T ROM contains firmware parts not previously seen in /e/ ROMs.
1 Like
Finally there is progress. I tried to install recovery-IMG-e-1.19.1-t-20240112373116-dev-avicii.img and it worked. I now have a working recovery ;-).
Then I tried to sideload e-1.19.1-s-20240109372023-stable-avicii.zip and it seemed to work up to (~47%). then it paused as usual. But then I got the message: to install additional packages you need to reboot to recovery first. I could choose Yes or No. I choose no first, but then it just terminated the proces. Rebooted to recovery andtried again, this time choosing yes, but the same result. A picture of the screen with the message is attached.
Then I tried rebooting -although I was afraid that that would brick the device since the installation seemd not to be finished- and to my surprise the phone started up in E 
You can’t believe how happy I amm, that it finally worked. I hope that there will be no bugs in the E os, but at least it works. Now I will do the same with the second device.
BTW aibd, I can’t thank you enough for all your help and patience. It is really appreciated
2 Likes
I tried to install the T dev version of E on the second handy, that would only start up in bootloader mode by wipng the data first with Fastboot -W and then flashing the T dev version of the recovery and voila, that worked as well. I got the same message when sideloading the 1.19.1 -t- 20240112373116-dev-avicii.zip, but rebooting to E os worked as well.
So my advice to everyone who want to install E on a Oneplus Nord: FORGET ABOUT THE STABLE ANDROID S VERSION AND GO STRAIGHT TO THE DEV VERSION ANDROID S.
aibd again thnx a million for all the help and patience
1 Like