I don’t understand why this requires a code rather than a toggle in developer settings like a Pixel. That doesn’t seem like openness and a commitment to treating users fairly since they could change their policy at any time.
I’ve read that it’s because fairphone has to pay a fee for each unlocked device, but it sounds a little weird so no idea if that’s real.
but, it can be worked around if you don’t want to get logged. the system just wants a 200 OK response from the server, I think through HTTP (not S), so you can set up an MITM proxy or custom DNS and web server to always give this response without using their website. that’s what I did too.
and the connection is actually HTTPS, but does not validate it against a globally trusted root certificate, so it can easily be served by a local server and a self signed cert
I’ve read that it’s because fairphone has to pay a fee for each unlocked device, but it sounds a little weird so no idea if that’s real.
The posts seem to suggest that Google is charging them a fee in that case, but that would be a little surprising given Pixels have a no-fuss unlock, and Google permits third parties to redistribute its proprietary add-ons to Android free of charge for installation by end users.
In any case, you’ve convinced me this probably isn’t Fairphone being evil, though some sort of public explanation would be nice.
I don’t understand why this requires a code rather than a toggle in developer settings like a Pixel. That doesn’t seem like openness and a commitment to treating users fairly since they could change their policy at any time.
I’ve read that it’s because fairphone has to pay a fee for each unlocked device, but it sounds a little weird so no idea if that’s real.
but, it can be worked around if you don’t want to get logged. the system just wants a 200 OK response from the server, I think through HTTP (not S), so you can set up an MITM proxy or custom DNS and web server to always give this response without using their website. that’s what I did too.
you can read more here: https://forum.fairphone.com/t/oem-unlock-input-verify-code/56231
edit: and also here: https://forum.fairphone.com/t/unlocking-bootloader-offline/95573
and the connection is actually HTTPS, but does not validate it against a globally trusted root certificate, so it can easily be served by a local server and a self signed cert
The posts seem to suggest that Google is charging them a fee in that case, but that would be a little surprising given Pixels have a no-fuss unlock, and Google permits third parties to redistribute its proprietary add-ons to Android free of charge for installation by end users.
In any case, you’ve convinced me this probably isn’t Fairphone being evil, though some sort of public explanation would be nice.