Okay we just removed the battery and reinserted it again but its still stuck in this fastboot mode. Some specs below the red fastboot mode line are being shown, the last line is the red device state locked.
with the volume keys I can select between:
restart bootloader (red)
recovery mode (red)
power off (white)
Thats all. Before I removed the battery I had already tried the normal START and restrat boot loader and power off.
All leading nowhere but again to this fastboot(?) state when turning it back on or rebooting it.
Any more hints?
With selecting start , it briefly vibrates and displays the fairphone and powered by android logos, and then back into this START page…
I now also tried the recovery mode selection, and it pretty much immediately briefly vibrates and then returns back to this start and selection page with specs info.
Is this phone now completely hosed? what the heck? how is this even possible???
If fastboot is still accessible, it is possible to reflash the OS to make it working again. However, I haven’t yet found an exact how-to for the FP3 for this. I’m hoping one of the experts reads this topic and can guide you further.
Is thi selection screen called “fastboot”?
This fastboot screen or whatever this is, currently shows:
bootloader version 8901.2.a.0105.20191217
baseband version mpss.ta.3.0.c1_00565_8953_gen_pack_1
serial number… (redacted)
internal storage size unknown
main memory size and vendor samsung
secure boot disabled
device state locked
You can try setting slot b active, if that doesn’t work either you’ll likely have to do the factory reset.
Get back into fastboot by shutting it down and holding “Volume Down” + “Power”, then fastboot --set-active=b
If it works now, just leave it.
Not sure how this happened, the idea of having two slots is that it should automatically switch back to the not updated slot, should the update go south.
Somehow in your case both slots got marked as unbootable and the retry count was 0.
Setting it active also resets the retry-count.
I’ve got the same problem here with a completly new phone, merely older than a week.
It turned off because of low battery before the last update could be done. Stuck in fastboot mode, same story as told before.
My fastboot.exe says as following:
I tried what you said k4y0z:
But either typing by hand and copying always gets me to this message:
I don’t think there should be one.
I can find references to that fastboot version going back >4 years. The slots system is more recent than that. If you still have issues try updating (official packages are Android SDK platform tools, i.e. you don’t need the full SDK.)
I also tried several combinations of “fastboot - -set-active=a / =b” and the only way working for me is with spaces in between.
Then I will get the response:
This message wont change for at least half an hour, is this normal?
Somehow I managed to set slot A active with no further change and am now struggling to set slot B active.
I also tried Android Multitools from this website which at least made my phone vibrate.
And thats as much as I know. Hopefully I am the only one having this issue!
Best wishes so far!
EDIT: I’m running on Thinkpad Windoof 10, version 1909 If this is of matter
My guess is your system is still using the old fastboot version. The new one(s) may be installed, but the older one may be taking precedence. (See also the comment about PATH above).
A hyphen followed by a space usually signals the end of the options to the programme. Chances are that you’re effectively running fastboot without any further command.
It means fastboot is waiting for a phone to be connected. If the phone is physically connected but fastboot cannot find it, then either the phone is not in fastboot mode or the drivers that are being used are not compatible.
Only one slot can be active at any time, as far as I’m aware (the android documentation suggests there can be more, but I don’t recall this for FP3). Apologies if this is stating the obvious and you just want to switch active slots, but this has caught out people before.
To fix the issues with fastboot, following the advice in the post above is a good idea.
Whether you need fastboot to fix this, I don’t know. If one of your slots does not boot because you switched off the device mid-update (at least, this is how I read one of your posts above), the other slot should at some point be tried automatically, as far as I know - but your mileage may vary.
Thanks Elk for this step by step instruction and thanks Johannes for further explanations, which I’m always eager to hear!
I followed your steps and am now able to run fastboot and adb directly from CMD. But there where some drivers left in the system32 directory which I did’nt want to delete before further asking.
Now I’m again able to find my phone
but the problem still remains, except:
and if I
It will return
remarkable is that the system will recognize a space between “–” and “set-active:a”
which i never tiped in.