FP4 bricked upon 5.5 beta tester update

also when trying Iode 5.5
but only since I flashed LineageOS recovery.

I tap in YES when iám asked for installing although signature verification failed

1 Like

Tried on Windows 11, same error, and always at 47%…

I thought about switching to the other A/B parition to recover iodé at the state before updating, but here’s the output:

> fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s

> fastboot set_active a
Setting current slot to 'a'                        FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed

So with a locked bootloader, impossible to change from a partition to another one…

but what happens, if i change to slot a and try to sideload Iode 5.5?
Will i still have my data? what if i change the slot again to b? is this slot empty?

i still have an open bootlader and i´m able to change the slot to a. then i have a bootloop.
but i´m able to boot into recovery…

so may i try to install iode 5.5 or will this erase all my data in slot b???

TBH I don’t know enough of how it works to give you any advice, and I don’t want you to lose your data.
The fact was that I remembered that Android relied on two A/B partitions in order to have a “backup” one in the case an OTA update is not working. AFAIK, when you install an OTA it’s pushed into the partition you’re not using. And when you reboot, it reboots on the partition with the update and the other one still has the older vesion of your ROM.
But I think data is stored in another place than these A/B partitions… but I’m not sure about that.

I also tried to unlock my bootloader, it doesn’t seems like it’s blocked. If I can gain access to iodé again without losing my data it would be awesome, but if necessary I could unlock the bootloader (and wipe all data).

thanks for your ideas and input.
maybe for me it is the last option before reinstalling the whole system…

but not today. for today it´s enough :wink: maybe tomorrow i´ll give it an other try…

I Tried switching to slot a. But ended up in bootloop.

May I sideload iode 5.5 to this slot or is it risky? I don’t want to brick my phone and hope not to loose my data…

Not sure if it helps, just telling you what I did…

The method proposed by Vince ran like a charm in my case:

In Win10 I started Windows Powershell
I connected FP4 with a cable to my PC

PS C:\Users\Roland> adb devices
List of devices attached
108d628b        sideload

PS C:\Users\Roland> adb sideload C:\Users\Roland\Downloads\iode-5.5-20240913-FP4-ota.zip
Total xfer: 1.00x
PS C:\Users\Roland>

Reboot went okay immediately. No data loss

That’s what I did, but not working for me… :man_shrugging:

That’s also what I did, and I had the errors I mentioned.
Thank you anyway for your help :wink:

:warning: using this method you will lose all data

I was desperate and wanted my FP4 back alive (my backup phone is not great at all), so I tried

> fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1

With a get_unlock_ability: 1, I can unlock my bootloader, so that’s what I did:

> fastboot flashing unlock
OKAY [  0.035s]
> fastboot flashing unlock_critical
OKAY [  0.037s]

Between those 2 commands, I let the phone wipe the data, and when it rebooted I immediately pressed “volume down” to go back into the bootloader.
After that, I did

fastboot reboot recovery

And in the bootloader, I flashed the latest OTA:

> adb sideload .\iode-5.5-20240913-FP4-ota.zip
serving: '.\iode-5.5-20240913-FP4-ota.zip'  (~94%)    adb: failed to read command: No error

At 94%, the transfer stopped itself and the recovery told me I needed to reboot in order to install additional packages. That’s what I did, and then I did again a sideload. But the recovery kept telling me I need to reboot at 94%.
So I decided to boot into iodé, and it now works. I lost all my data but it works.

I should’ve tried to sideload only doing “Wipe data” in the recovery before unlocking my bootloader, to see if it would’ve worked, but it’s now too late. So now idk if sideloading the OTA is blocked due to problems in the data partition, or if it’s due to the bootloader that is locked.

My bootloader was not unlocked

As for the prevention of data losses, I use

for backing up my phone data.

The problem of this is that you can’t backup the data of the apps, or maybe not all the apps.
Also, you have a built-in backup system into iodéOS, in case you didn’t know. You can find it in the advanced settings, I think (I’m currently with FPOS for testing purposes so I can’t tell you the exact path…

Interesting. I did not know that. I found it in Settings\System…

True, MyPhoneExplorer is good for back-up and synchronizing data, contacts, calendar, pictures, messages, …

Directly from phone to PC or laptop. Without cloud service.

I am not interested in using computers other than my own for backups.

So perhaps the iode built-in backup option is not good for me

But i think seedvault is a local backup. For example to store at sd-card…

For nextcloud, too

i think i have to setup my fp4 again.
i tried to check my oem status and got this result:

C:\platform-tools>fastboot getvar oem
getvar:oem FAILED (remote: ‘GetVar Variable Not found’)
Finished. Total time: 0.012s

Hi @f.limi, what is this command useful for?