So I got my FP6 with pre-installed /e/os and managed to brick it almost instantly by trying to move over my fotos using some adb commands (wanted to keep the date/time stamps).
Contacted fairphone, sent it in and they fixed it in no time.
Got it back, works as intended, except for the ID-Austria app stating an open bootloader. It gives you the option to continue “at your own risk” and seems to work ok (did not register yet, but got through the first steps ok). See also this thead: Bootloader FP6 - Austria ID not working
I would like to check the state of the bootloader, but am a bit cautious now.
OEM unlock is disabled
USB debugging is enabled adb devices shows the phone’s serial
Does the greyed out OEM unlock toggle state a locked bootloader?
Can I boot into bootloader/fastboot with OEM unlock disabled? Or will it just boot into /e/os? Or get bricked again?
Can I then fastboot devices with no risk of damage?
If it turns out to be unlocked and I decided to lock it, I am aware of the consequences and risks of locking the bootloader at this point (data will be wiped and android rollback prevention might strike if build number is lower than previous flash).
Sorry for the noob questions, but better safe than sorry (again).
PS: I did flash /e/os successfully on a FP4 three years ago, so I am ok with adb and fastboot. It’s just not something I do on a regular basis. I’m a user mostly.
Does the greyed out OEM unlock toggle state a locked bootloader?
I’m fuzzy on this myself, but from experience, once you unlocked with the OEM key it will be greyed out / inactive
Can I boot into bootloader/fastboot with OEM unlock disabled? Or will it just boot into /e/os? Or get bricked again?
any stockphone can enter the bootloader. Just try adb reboot bootloader or use keycombos. Whatever you do there is at first just reading / introspection, it will not be bricked.
Can I then fastboot devices with no risk of damage?
is fastboot a verb? as said, you can look around with fastboot. When you do writing changes as “fastboot flash” then there’s risk unless you know 1. your highest patch level date when unlocking, that 2. your patch level date of what you flash is past that date before you relock.
Unless you do not relock, there is no risk from patchlevels even if flashing older ones. Those are the terms you want to search in the forum.
I got a bit adventurous and tried to toggle the OEM unlock switch. It is still possible to be activated, asking for the PIN code; I cancelled there and left it alone, as for now I want the phone to be locked.
I just realized, I was being confused and unprecise before: The text “OEM unlock” is not greyed out, only the slider is while not activated (left position), but that’s standard in android settings.
So the folks at the service center did a good job, the phone is as new.
The only thing, that’s weird is the ID-Austria app stating an open bootloader, but this is a different issue, which is addressed in the other thread linked above.
haven’t asked explicitly, so support sent it back with /e/OS again and locked - not stock Android?
The FP6 3.0.4 build was a cloaked userdebug build, that is what Apps can complain about (they want a non-debuggable, “user” build). Let’s see what’s in store for the FP6 with v3.1 / 3.1.1
I had bought the phone through fairphone webshop, so I turned there for support, stating that I wanted /e/OS back on the phone.
Support via email was not super fast, but responsive enough and friendly.
Once I had accepted the terms, Cordon electronics in France took over.
I got a shipping label and from that point on things went really quick and highly professional. Having in mind the bad reputation of fairphone’s customer support I was very pleasantly surprised.
I received a quotation (€ 52,- cc only), after payment the phone got fixed and sent on it’s way the same day.
