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.
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.
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.
$ ./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.
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
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
