Unable to flash FP6

Installation Help
1

Hi there,

I wanted to try out Iode on my FP6 and fully expected something to go wrong. However, I did not expect it to go wrong this early on…

I sucessfully unlocked my bootloader (both unlock and unlock_critical went smoothely), but when executing the flash_all.sh script, there’s not a single command which executes successfully (okay, the avb erasure and reboot works :smiley: ):

❯ ./flash-all.sh
Setting current slot to 'a'                        FAILED (remote: 'unknown command')
fastboot: error: Command failed
Erasing 'avb_custom_key'                           OKAY [  0.012s]
Finished. Total time: 0.020s
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB)                    FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
FAILED (remote: 'GetVar Variable Not found')
fastboot: error: Command failed
FAILED (remote: 'GetVar Variable Not found')
fastboot: error: Command failed
Warning: skip copying frp image avb footer (frp partition size: 0, frp image size: 524288).
Sending 'frp' (512 KB)                             FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying abl image avb footer (abl partition size: 0, abl image size: 245560).
Sending 'abl' (239 KB)                             FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying aop_config image avb footer (aop_config partition size: 0, aop_config image size: 20328).
Sending 'aop_config' (19 KB)                       FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying aop image avb footer (aop partition size: 0, aop image size: 318528).
Sending 'aop' (311 KB)                             FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying bluetooth image avb footer (bluetooth partition size: 0, bluetooth image size: 831488).
Sending 'bluetooth' (812 KB)                       FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Sending 'cpucp_dtb' (11 KB)                        FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying cpucp image avb footer (cpucp partition size: 0, cpucp image size: 203936).
Sending 'cpucp' (199 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying devcfg image avb footer (devcfg partition size: 0, devcfg image size: 49000).
Sending 'devcfg' (47 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying dsp image avb footer (dsp partition size: 0, dsp image size: 67108864).
Sending 'dsp' (65536 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying featenabler image avb footer (featenabler partition size: 0, featenabler image size: 105440).
Sending 'featenabler' (102 KB)                     FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying hyp image avb footer (hyp partition size: 0, hyp image size: 1682304).
Sending 'hyp' (1642 KB)                            FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying imagefv image avb footer (imagefv partition size: 0, imagefv image size: 53048).
Sending 'imagefv' (51 KB)                          FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying keymaster image avb footer (keymaster partition size: 0, keymaster image size: 441312).
Sending 'keymaster' (430 KB)                       FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying multiimgoem image avb footer (multiimgoem partition size: 0, multiimgoem image size: 12088).
Sending 'multiimgoem' (11 KB)                      FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying qupfw image avb footer (qupfw partition size: 0, qupfw image size: 60576).
Sending 'qupfw' (59 KB)                            FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying shrm image avb footer (shrm partition size: 0, shrm image size: 51952).
Sending 'shrm' (50 KB)                             FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying tz image avb footer (tz partition size: 0, tz image size: 4027040).
Sending 'tz' (3932 KB)                             FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying uefi image avb footer (uefi partition size: 0, uefi image size: 2903864).
Sending 'uefi' (2835 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying uefisecapp image avb footer (uefisecapp partition size: 0, uefisecapp image size: 196696).
Sending 'uefisecapp' (192 KB)                      FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying xbl_config image avb footer (xbl_config partition size: 0, xbl_config image size: 307336).
Sending 'xbl_config' (300 KB)                      FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying xbl image avb footer (xbl partition size: 0, xbl image size: 1166160).
Sending 'xbl' (1138 KB)                            FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying xbl_ramdump image avb footer (xbl_ramdump partition size: 0, xbl_ramdump image size: 860056).
Sending 'xbl_ramdump' (839 KB)                     FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 100663296).
Sending 'boot' (98304 KB)                          FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying dtbo image avb footer (dtbo partition size: 0, dtbo image size: 31457280).
Sending 'dtbo' (30720 KB)                          FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying init_boot image avb footer (init_boot partition size: 0, init_boot image size: 8388608).
Sending 'init_boot' (8192 KB)                      FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying pvmfw image avb footer (pvmfw partition size: 0, pvmfw image size: 913408).
Sending 'pvmfw' (892 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 104857600).
Sending 'recovery' (102400 KB)                     FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying vendor_boot image avb footer (vendor_boot partition size: 0, vendor_boot image size: 100663296).
Sending 'vendor_boot' (98304 KB)                   FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying vbmeta image avb footer (vbmeta partition size: 0, vbmeta image size: 65536).
Sending 'vbmeta' (64 KB)                           FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying vbmeta_system image avb footer (vbmeta_system partition size: 0, vbmeta_system image size: 65536).
Sending 'vbmeta_system' (64 KB)                    FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Warning: skip copying super image avb footer due to sparse image.
Sending 'super' (23026 KB)                         FAILED (remote: ' Invalid argument size')
fastboot: error: Command failed
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.050s

Of course, the device reports normally with `fastboot devices` and is booted into bootloader / fastboot mode (not recovery). Somehow, it seems that the device is certain that there is no such thing as a slot (as you can see in the output above).

I am not quite sure how to proceed from here. I downloaded https://gitlab.iode.tech/ota/release/-/raw/master/FP6/iode-7.5-20260506-FP6-fastboot.zip this zip as instructed by the guide ota / ota · GitLab

Thank you in advance for any help!

CodeSalat

2

Okay so I ran some getvar commands in the bootloader until the device prompted me to press a button in order to shut it down. I then ran the install script again during startup into bootloader and it went through this time.

It took a solid hour with intermediate restarts for the device to boot afterwards, but it seems like it works for now! :smiley:

1 Like
3

OK this is strange but happy to see it seems to have worked in the end? Maybe fastboot just needed a reboot :slight_smile: ?

4

So I feel like I need to update this thread because there was some debugging required to get it working:

First off, I think the device telling me to press a button in order to shut it down (which happened after running a multitude of commands in fastboot) was fastbootd crashing. It almost felt like killing PID 1: the text was way too small to be intentionally user-facing and also the message IMO doesn’t make a lot of sense after running a `getvar all`.

Also, the device sadly did not work as intended: I thought everything worked fine until I woke up to an alarm that only vibrated. I played some music and realized audio wasn’t working at all. I then tried restarting only to be met with the bootup stuck at the Iode logo for way too long just like at first boot.

Despite me “successfully” flashing the device twice at that point and being hit with the same issue every time I do, I downloaded the `-ota` file for Iode on the FP6, went into the lineage recovery and side loaded it via adb. Rebooted and the device started in less than a minute and fully functional.

There have been some reports about fastboot being a little picky on the FP6, so I am going to assume that this is probably on them and not Iode. The way fastbootd responded to my commands was flakey at best.

More info: between the two successful fastboot flashes (which both resulted in a broken OS), I changed: USB cable, host, fastboot version and USB version. After the first flash, I did not wait long enough during boot for anything to happen and tried re-flashing after staring at the logo for half an hour.

Maybe someone can do something with that information :smiley:

CodeSalat

1 Like
Back from de dead -> the next episode of my journey to install iodeOS on FP6