Unfortunately, something went wrong and now my FP4 won’t boot FairphoneOS - after five loops (or three?) it booted up into Fastboot Mode and now won’t do sh*t.
Double trouble: DEVICE STATE is now “locked”.
How can I get this neat little thing going again? I already checked other threads but their solutions didn’t work for me and now I’m feeling quite dumbstruck.
Thanks in advance for any suggestions and best wishes,
the.k
as you locked your bootloader, did you used both commands:
fastboot flashing lock_critcal
fastboot flashing lock
?
That’s the funny part: My bootloader was unlocked when I ran “flash_fp4_factory.bat” to install the original fairOS from my win10. I didn’t OEM lock it afterwards as it never booted ^^ I suspect the installation script locked OEM on it’s own but didn’t read “flash_fp4_factory.command” yet.
are you able to boot in bootloader and unlock it again?
Nope, I’m not able to unlock it again. Please look at this:
c:>fastboot flashing unlock [waiting for execution...] FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Very interesting
There isn’t any code in flash_fp4_factory.command (flash_fp4_factory.bat just runs that script) that could (should) relock the bootloader.
Do you remember at what point the script failed or what the output was?
There isn’t any code in flash_fp4_factory.command (flash_fp4_factory.bat just runs that script) that could (should) relock the bootloader.
Good to know.
Do you remember at what point the script failed or what the output was?
The script didn’t look like it failed: I think I saw a “succesful” message but unfortunately there’s no “pause” command at the end of the script so I’m not sure. As my FP4 rebooted afterwards I felt confident.
Normally this happens when “OEM Unlock” ist not set in Developer Options
My feeling excactely! But I didn’t change the setting after using the “flash_fp4_factory.command” script as my FP4 ran into the boot loop. I’ve not seen the first setup wizard since.
As it is, I’m glad it boots into Fastboot Mode at all.
If your phone rebooted automatically, the script should have run without errors. The reboot get’s initiated last and errors during during checksum validation or flashing partitions will show you a prompt you have to interact with. So either the problem stems from one of the steps that don’t automatically throw an error, like wiping frp, misc, modemst1 / modemst2 or this maybe isn’t related to the installation procedure at all
Could you please link to the installation instructions you followed to get iode installed, perhaps there is something we are missing here?! A lot of these cases involve switching from some other custom ROM back to vanilla FPOS (not all of them though), there has to be an explanation buried somewhere…
Just to be clear, the bootloop started immediately after flashing, right? Did the actual bootprocess start at all (those dancing blue dots) or did it go straight back to fastboot every time?
Sadly, with a locked bootloader, fastboot isn’t all that useful…
Just to make sure we have tried all the options, can you reach recovery either through the option in fastboot or by running fastboot reboot recovery?
In any case, I suggest you contactsupport if you haven’t already, reviving a bricked phone isn’t something the community can do at this point.
After this my phone booted niceley into the original FairPhone Welkom screen. I powerd of the device re-enterd the Fastboot screen and locked the bootloader again.
After locking the bootloader my phone gave an error saying that the firmeware isn´t trusted and then the phone enterd the bootloop your decribing but now with the “Device state - locked” so all fastboot commands arn´t working anymore, including the unlock commands.
It looks to me like after the " fastboot flashing lock_critical" and " fastboot flashing lock" command it reset the android option “OEM unlock” to disable thereby disabeling the option to unlock it from fastboot.
I’ve followed the process a little bit more thoroughly and it seems that reinstalling FPOS resets “OEM unlock” to “disable”. Unfortunately you can’t reenable it then as the option is greyed out while bootloader is unlocked. And you can only enable the option when locking the bootloader. But you can’t lock the bootloader because then you run into the problem described in this topic…
That’s a normal behaviour
If the bootloader is unlocked, then this option is inactive, because it is only to allow you to unlock it, and it is still unlocked
On every ROM.
Yes, but on other ROMs it’s not a “devil circle” leading to a hard bricked device…
And before reinstalling FPOS it was AFIK greyed out but set to “OEM unlock enable” in my case.
yes, that’s really bad, but at the moment the cheapest one.
It’s only FP who can re-flash it.
with other manufacturers, the users are much worse off. there you are often left alone and a bricked device stays bricked.
