At first sight this would indicate that you are not correctly in Bootloader. This screen has
big Green START at top of screen
Fastboot highlighted in Red
Locked / Unlocked highlighted in Red
(Over the years users who start from fastbootd can get into complex positions.)
Tip Once you arrive at the described screen there is no need to touch another button on the phone before sending commands from the PC.
Boot modes simplified
In case it helps to vizualise things
A simple Android phone has three basic modes in which it runs.
Normal phone
Recovery. With /e/OS installed, the Recovery appears as the colourful e-Recovery.
Fastboot mode. I think of this as a communication channel which effectively allows you to adjust the underlying “whole system” while the rest of the software is more or less inactive.
(Both fastbootd and recovery adjust the phone while it is “live”.)
OK, I am on the screen you described and obtain the response :
6023457b fastboot
After that I taped
./fastboot flashing get_unlock_ability
and obtained
(bootloader) get_unlock_ability: 0
OKAY [ 0.000s]
Finished. Total time: 0.000s
OK so the 0 response indicates not ready to unlock. I think I will let @AnotherElk follow up, but one two more questions, on your Bootloader (green START) screen do you have Locked highlighted in Red at the foot of that screen.
When you told us that you never saw an opportunity to apply the Fairphone unlock code … is it a possibility that you had not started from the point described this morning?
Starting from this point does an opportunity to apply the Fairphone code appear?
Since the beginning I think that I must first unlock the OEM before to unlock the boot.
But, because I cannot run the system, I have no access to the setting menu an developer options. How to solve this ?
In Post #13 I was somewhat hesitant but I do feel that “natural justice” would suggest that Fairphone (as the people who took your money) should fix this.
My knowledge of Fairphone is what I read rather than hands on experience but where you are now seems beyond what could be reasonably expected of a normal user.
The code to unlock the boot is described in the Fairphone documentation and I could obtain this code from their internet site (it’s the only concrete thing I can obtain from them), but I never acceded to a screen or a command line where I could insert this code. I suppose it is necessary before to unlock OEM.
I am totally conscious that it would be the duty Fairphone to solve this problem, but I never obtain a concrete response to my requests, it look like they were all dead. An international action in justice would be logic but complicated and probably expensive. So I have no solution.
My feeling is that if you were to “brute force” reinstall /e/OS there is a rather high chance that the phone would need reimaging at a cost of €52 (last mentioned price on this forum).
I believe Fairphone should do whatever it takes to reimage the phone at their expense. I feel you should tell them the story very briefly of what you tried here and that you are not prepared to take the risk of going further; you would rather return to phone to them for reimaging at their expense.
No lawyer is required to make this very reasonable case, the phone is not fit for purpose as is.
We have heard above that Fairphone have struggled with support.
You should probably follow up any active ticket number you have, allow 7 days and repeat but with cc to a new case.
For what it’s worth: my understanding and experience is that with /e/OS installed (which I think is how your phone came), you don’t need to enter a code from Fairphone’s generator page to enable unlocking the bootloader, despite what the Fairphone support site says (and indeed the /e/OS install instructions).
My belief is based on (a) this forum post, (b) my own experience – when I tapped “OEM unlocking” in the developer options of my /e/OS install, I was prompted for my own regular phone PIN, but not for any other code. After this, fastboot flashing get_unlock_ability says 1. (I haven’t gone any further yet, because I’m waiting for a new /e/OS release, so I’ve not personally verified that the bootloader is unlockable.)
(I think this doesn’t directly help you, because I don’t think you get as far as booting any OS. But I guess it’s helpful to know that it’s not inherently necessary to have somewhere to insert a code from the Fairphone site. I don’t know anything about the underpinnings here or why it’s OS-dependent.)
I had already told the problem to Fairphone, I made several revivals but only responses since the beginning of may are to look at the “Fairphone knowledge base” and to have patience. I cannot send the in the Netherlands without a return voucher. I have not enough trust in Fairphone to send my device without appropriate documents. So shall have a last try with a repairman and if he doesn’t reach, I threw the phone.
Hi,
A miracle ! This was totally unexpected : I received yesterday an email from fairphone that said that they take account of my problem and today, I received a return voucher. It was very time, one week later I should have thrown away the phone. I expect now only two things : that the repair will no require so much time, and that they will not refuse the warranty because of my interventions on the device. I hope that it will now at last follow the normal repair process.
Once thank you to everybody who help me
@aibd
In my experience with support, quite often if i left my phone alone for a few or more hours, they (support) would be helping and fixing in the background, once they had accepted the incident report, and not always giving feedback.