Definitely don’t lock your bootloader in that case (as you are probably already know )!
Since my method of unlocking the OEM switch works, but for @cosmicget_unlock_ability was reset to 0 again afterwards , better not to tempt fate.as well, tread very carefully here.
The only safe path forward is to wait for the Calyx devs to release a new version based on the updated Fairphone stock images, which they confirmed they will.
Edit: Should have reread your post get_unlock_ability definitely shouldn’t have been reset to 0 again, so let’s hope this gets fixed with the next CalxyOS release. You might have to wipe your phone again then, though
I just reflashed a FP4 with the updated factory images and get_unlock_ability was reset to 0. That phone hasn’t been flashed to any custom ROM before (so not a Calyx problem this time) and get_unlock_ability was 1 before flashing.
So this is definitely not fixed…
Edit: I followed this process without locking the bootloader at the end and reflashed the whole OS again.
Same outcome, again.
Edit 2: Third time wasn’t the charm either. Tried a factory reset beforehand, tried fastboot flashing unlock again (doesn’t work on a unlocked phone), still changed that 1 to a 0 again
I think I messed up too… I did a quick flashing of CalyxOS (unlocked without critical). Then I recognized a much dimmer LED flash and wanted to get back to stock.
I did the download and startet the script which aborted because locked critical.
I unlocked critical and the installation went through. FPOS booted up, yeah!
And now for the messup. I got the message, that an unlocked phone isn’t secure. In my endles wisdom I locked critical and “nomal” again without toogling OEM unlock first in OS.
I then was presented the message that my system is corrupted. Now it just boots to fastboot mode and I cannot unlock the bootloader…
I’m kinda sad. I wasn’t able to send my FP4 back until now, I rarely got a response on Apr 22 that I was able to send it back if I wanted. I replied that I indeed wanted and did not receive an answer since. I mean I get they don’t have the capacity like tech giants but I was so hyped for my FP4 and now I kinda completely forgot about it since it is already in a package waited on being shipped to the repair center… They mention a support phone number on the support site but the only number I found was the one in the impressum here Impressum - Fairphone is that the correct one to call? Just to make sure they didn’t forget about my request?
I submitted my support ticket on friday night and did get an answer this afternoon. Currently I’m waiting for the shipping labels and instructions.
They acknowledged my situation:
Our Software team has identified the root cause of this issue. We now provide an updated package for manual installation which addresses this cause.
The problem is, this is the exact version that I was using. The checksum of the .zip-file I downloaded is identical to the the one in the article…
Perhabs somebody of you can tell me what I could’ve done wrong:
I installed calyxos several times because everytime that I locked flashing I got the Message that my device is corrupted. After that I unlocked it and installed it again.
I tried this several times until I just let it be open.
After reinstalling FPOS I did the same thing with the only difference, that i wasn’t able to unlock flashing again.
For the installation of calyx I unlocked only flashing.
After the first try of installing FPOS again the script failed because critical was locked, so I unlocked it and tried again. After installing and booting into the configuration wizard, I locked critical and flashing again. After doing that it prompted the message again that my device is corrupted and won’t boot.
As from my understanding the root cause is that. If you flash back the FPOS it does have a bug. That the Switch under Developer Options for “OEM Unlocking” is greyed out and turned off. So unlocking is not allowed. But you cannot turn it on as well. If you then go ahead and lock the bootloader you’re stuck in the loop. I still did not get an answer and everytime I call it says no agent is available right now… But nice that you received a response that fast!
BTW the german number there leads to nowhere, when I call there it just hangs up immediately. I tried to call the Netherlands one several times, where no agents where available unfortunately. Thanks a lot though
Yeah, I fell into this trap as well.
Trying to revert back to FpOS using FP4. Install Fairphone OS offline after attempting installing /e/os.
I’m have a feeling the issue was using a built image of /e/os that didn’t match the current security patch level
I updated the phone earlier today to “FP3V.A.116.20220414” (released April 25, 2022) before trying to flash “IMG-e-0.23-r-20220413178020”.
Trying to lock the bootloader as instructed gave me a corrupted OS message as mentioned throughout this post, but it didn’t reset my unlock ability to 0.
However, following Fairphones own guide FP4. Install Fairphone OS offline and locking the bootloader “corrupted” the OS and set my unlock to 0.
Can I somehow see what version is used in that “factory reset Fairphone OS” kit that you download through the link above? I have a gut feeling it’s not up to date to the current security patch level
It really is on me at the end of the day for attempting something I knew little about (after all, it’s on your own risk), but I think it would be a good idea to really emphasise the importance of finding out the correct versions in all relevant documents.
The documentation with important version numbers gets outdated pretty quickly, so next time I’ll make sure not to rely on those and try to double-check everything myself
Hoping to get this restored by sending it off to support like the people further up in the thread did, but if this happens often enough I think it should be in everyone’s interest to make these steps a bit more “fool-proof”.