I tried /e/ os and would like to reflash the stock ROM to test something. Once the stock rom reflashed, I wanted to relock the bootloader to be back to a “factory phone”
So I ran first fastboot flashing lock_critical → factory reset, then the fp6 rebooted. I didn’t mention that the OEM unlock was not enabled at this moment … and then going back to fastboot to run fastboot flashing lock.
Unfortunately, the phone won’t boot: “corrupted ROM”, and the bootloader is now locked, and oem is lock too.
I’ve read some topics about how to unbrick fp3 / fp4:
not an expert, but for the EDL mode, one would need a device-specific file called firehose (?) that obviously doesn’t exist for FP6 since it’s very new and we need someone in the community to find/crack/extract/craft it first and distribute it.
Hi bro. I’m in the same situation. I reflashed the stock ROM from EOs. Everything was fine until, after booting the stock ROM, I tried to lock the boot, not realizing that the OEM unlock option was disabled in developer options.
For the records: which e/OS version was installed and which FPOS did you install?
Edit: I assume you guys ignored the caution part. Current SPL of FPOS is 5th May and e/OS seems to be already on 5th Jun. So I guess you installed on older SPL and thats causing the brick. https://doc.e.foundation/devices/FP6/install
edit: i succesfully installed /e/os but didn’t end up liking it. so i installed the official firmware again succesfully but bricked at the last re-locking step.
adp isn’t finding my fp6 and my fastboot reports the same as OP
the latest (and only) fp6 firmware was released june 25th, the latest Android security patch may 5th.well before the fp firmware so it shouldn’t trigger anything rollback protection, no?
From Fairphone’s “Manage the bootloader” page linked to above …
“If you install an OS with an older security patch level than your previous OS, Android’s roll-back protection might brick your device when locking the bootloader! Wait until you get a software update with the same or newer security patch level before locking the bootloader.”
(under “- IMPORTANT -”, standing out quite a bit)
If indeed Fairphone’s OS has an older patch level than the /e/OS build installed before reverting to Fairphone OS, than this would mean you exactly followed the instructions on how to brick your device.
the OS my fp6 shipped with had the same security patch as the latest /e/OS
so if the OS hosted on FP’s own website is older than what was pre-installed - yeah
For FPOS there is only one SPL version available so it def was not shipped with SPL 5th June. The OS version date is completely irrelevant, it does not say anything about the SPL date.
That’s exactly the problem if the patch level isn’t given for the download.
That’s why Murena try to give the patch level in their install instructions (I say they try because sometimes the page updates can lag behind the real patch level from the release notes, but that’s safer than not giving anything).
!