Ok, I got a fairphone 6 without the e/os, wanted to switch to that and used the webinstaller on windows 11 after updating my phone. That worked pretty ok until after the very last step and the phone is now stuck in “FastBoot Mode” regardless of which option i select. holding down the power button doesn’t shut it down either just repeatedly tries to boot and then gets back to fastboot.
The device state is listed as unlocked and i didn’t see any pop ups or messages. I did get a “muerna” screen when it first started to boot back up tho. My phone doesn’t seem show up in the device manager under “other devices”. i installed all the optional driver thingies that looked phone related already.
After looking here for a bit i saw a post with a similar problem to mine and the person was advised to download platformtools and open the terminal in there to run “./fastboot oem device-info” and “./fastboot flashing get_unlock_ability“. I did that but whenever i try to run the commands it just wants to open a file in the text editor. If i do let it open in the text editor everything looks entirely scrambled. I also tried to update the terminal but it stil only wants to create a file.
is there anything i can even do from here?
i’m really bad at tech so please use as easy terminology and steps as you can, i’m rly sorry for the inconvenience ;-;
However the above guide does aim to be a “Safe guide” and it is not wise to proceed when you have fastboot errors. The reason for caution is that one can brick a Fairphone with lack of understanding.
Rather than persevere with uncertainty perhaps spend some time researching other eosinstaller threads.
my biggest problem is that the phone won’t boot at all anymore it just shows the fastboot menue and every one of these guides require you to be able to boot
i think i’m just gonna try to contact support instead, thank you for trying to help me tho
Good luck, but please bear in mind complex forum posts do not get answered necessarily even same day.
I get that … both boot methods, System and Recovery fail. This will happen in the case of fastboot flashing errors; the phone is not bricked as long as we have working fastboot.
However (now of all times) you really want reliable fastboot.
It is a usage issue, so not specified as an “on device error”; a good sign for the device itself being OK
It is a fastboot problem where a “correct command” is seen as unknown.
It is possible that the original fail and this error is due to USB problems. Consider the whole USB chain. It has been reported that certain USB will not carry fastboot commands or complex fastboot commands. You will need a good quality (full capacity) data cable, so not a thin, skinny cable.
Avoid USB hubs including any USB hub that might be hidden in the PC / laptop.
Avoid a USB-C to USB-C cable as it may be provisioned through a hidden hub.
For predictably good results check (if necessary with a manual) that you are connecting to a USB-2 port soldered to the motherboard.
I am not sure this is true, but a booting phone is always a good place to start.
We can rescue a phone from working Fastboot mode with a Fastboot ROM. This is the method of the guide.
We don’t know the background before eosinstaller, we don’t know what errors occurred and we don’t know if the phone was compromised even before eosinstaller.
You are asking only about one very specific fastboot “error message”.
To support you to run a Fastboot “recovery” we have to know we are free of fastboot errors otherwise any hidden obstacle remains unknown to anyone in a position to help.
