IodéOS installation failed on a Oneplus 9Pro

[Actarien]

I tried to install IodéOS 7.5 on my new phone, a Oneplus 9Pro, but I failed badly

I’ve followed instructions from https://gitlab.iode.tech/ota/ota and downloaded and checked iode-7.5-20260506-lemonadep-fastboot.zip from https://gitlab.iode.tech/ota/release/-/tree/master/lemonadep

I’ve done well first steps : OEM unlocking, adb reboot bootloader, fastboot flashing unlocking, I’ve accepted unlocking, and then I run ./flash-all.sh from my Linux laptop : the script start working well, with a lot of actions ending with OKAY, but at some time, one operation failed, and the phone rebooted . It was with these traces :

extracting super_empty.img (0 MB) to disk… took 0.000s
Sending ‘super’ (5 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.010s]
Resizing ‘odm_a’ OKAY [ 0.005s]
Resizing ‘product_a’ OKAY [ 0.005s]
Resizing ‘system_a’ OKAY [ 0.004s]
Resizing ‘system_ext_a’ OKAY [ 0.004s]
Resizing ‘vendor_a’ OKAY [ 0.004s]
Resizing ‘vendor_dlkm_a’ OKAY [ 0.004s]
extracting super_empty.img (0 MB) to RAM…
extracting odm.img (607 MB) to disk… took 2.523s
archive does not contain ‘odm.sig’
Resizing ‘odm_a’ OKAY [ 0.005s]
Invalid sparse file format at header magic
Sending sparse ‘odm_a’ 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >

I got a strange screen like this :

I tried to go back to fastboot mode, it works, the script started again, but with all actions failing, and ended, rebooting phone on this same page with lot of text…

I’ve collected script-all.sh ’s output in a log file :

flashing.log.txt (12,4 Ko)

I still can go to fastboot mode using Power+VolUp+VolDown, but the normal boot go to the state like the previous picture : what should I do to recover this ? Should I try to restart ./flash-all.sh again [from the beginning] ?

Any help would be very appreciated !

[vanMacG]

I don’t have this device, but in your log, it often says Flashing is not allowed for Critical Partitions.
So you probably have 2 options:

• Wait for someone with a lemonadep
• Try to unlook with fastboot oem unlock instead of fastboot flashing unlock. This is the way LOS instructs in their wiki + oneplus instructs in their docs here. OEM unlock often unlocked critical partitions as well.

PS: You wrote

fastboot flashing unlocking

I guess this is a typo, and you used fastboot flashing unlock? Otherwise you shouldn’t get something on your phone to unlock.

[rik]

@Actarien in addition, maybe sudo is required? I feel like I have seen your issue but can’t quite recall what was behind it… Alternatively, you can try our graphical installer but certainly the script should work?

[Actarien]

@vanMacG : Yes it was a typo, the ’fastboot flashing unlock’ command run well

@rik I’m don’t think sudo is required, as first commands using fastboot worked…

I’ve found a post with another person having trouble installing iodéOS on a lemonadep : Initial state before installing iodé and fastboot issues - #13 by slomo

I tried to put my phone in fastboot mode and type each command of flash-all.sh script one after another, and the problem comes when doing :

fastboot --skip-reboot update iode-7.5-20260506-lemonadep-img.zip

Although the –skip-reboot option was set, the phone reboots during the process :

extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_system.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta_system.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_system’ (4 KB) OKAY [ 0.002s]
Writing ‘vbmeta_system’ OKAY [ 0.001s]
extracting super_empty.img (0 MB) to RAM…
extracting vbmeta_vendor.img (0 MB) to disk… took 0.000s
archive does not contain ‘vbmeta_vendor.sig’
extracting super_empty.img (0 MB) to RAM…
Sending ‘vbmeta_vendor’ (4 KB) OKAY [ 0.002s]
Writing ‘vbmeta_vendor’ OKAY [ 0.001s]
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >

And the phone restart on another menu (that I don’t recognize) :

and I don’t know what to do next …

I don’t understand why fastboot says “Rebooting into fastboot” whereas the –skip-reboot option was given ?!?