Here is the wrong part of Documentation. Hope someone can fix this. (maybe that bug is also somewhere else in that documentation, please have a look)
Before install
How to Boot into bootloader mode
Press and hold the Volume Down button.
Release the Volume Down button as soon you boot into bootloader mode
Here is the info from the flash script itself, it mentions “Volume DOWN Button”, which does NOT enter fastboot mode. And removing battery while connecting to PC won’t work, only a “no battery” symbol is shown. Maybe my USB-3.X port is not providing sufficient power?
./flash_FP4_factory.sh
*** Fairphone 4 flashing script ***
INFO: The procedure will start soon. Please wait...
Note that this will detect and flash only on FP4 device.
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
INFO: One Fairphone 4 in fastboot mode found (serial number: XXX).
Sending 'bluetooth_a' (940 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
ERROR: Could not flash the bluetooth_a partition on device XXX.
ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)
ERROR: Aborting now (press Enter to terminate).
SO now I am a bit stuck. While my Fairfphone 4 is waiting in fastbootd menu, connected to th e USB-3.1 port of my laptop, the script only repoert with above error message. Whould I need to run it as root??? (using Debian linux).
I have a Fairphone 4 here and just tried it myself. Power + Volume DOWN definitely boots into fastboot/bootloader mode. It was always the DOWN button with all Fairphones.
Whe nI just run the script when that menu is shown, this is reported on my laptop:
FAILED (remote: ‘Flashing is not allowed in Lock State’)
I am sure to have (fetched unlock code from ff site etc.) done unlocking my phone inside stock OS.
You need to do that first from fastboot mode, which is the one that shows START, Restart Bootloader, Recovery Mode and Power Off (i.e. you need to stay on that screen during the unlock step)
adb devices
List of devices attached
XXX unauthorized
adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Ok if I reboot into Stock OS, ther is “usb debugginh is enabled” and when I enter sim-pin and unlock-pin and THEN do another try, that is different now:
adb devices
List of devices attached
285dc5d3 device
adb reboot bootloader
...
There on the phone now is in the “fastboot mode” (i think at least) som einfo, one says: DEVICE STATE - locked
So I have to unlock it. Try on console via faast boot … one moment please…
./flash_FP4_factory.sh
*** Fairphone 4 flashing script ***
INFO: The procedure will start soon. Please wait...
Note that this will detect and flash only on FP4 device.
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
INFO: One Fairphone 4 in fastboot mode found (serial number: xxx).
Sending 'bluetooth_a' (940 KB) OKAY [ 0.010s]
Writing 'bluetooth_a' OKAY [ 0.004s]
Finished. Total time: 0.021s
Sending 'bluetooth_b' (940 KB) OKAY [ 0.014s]
Writing 'bluetooth_b' OKAY [ 0.004s]
Finished. Total time: 0.025s
Sending 'devcfg_a' (42 KB) OKAY [ 0.002s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
ERROR: Could not flash the devcfg_a partition on device xxx.
ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)
ERROR: Aborting now (press Enter to terminate).
THERE same choices of items, but screen looks very different (font etc) from the vol-down booting into fastboot. Someone can explain me what the difference is?
adb and fastboot only recognize my mobile when that is fully bootet, sim pin entered and when I am not at 1st setup stage of e/os, adb devices shows no devices . I now have to setup to some point until the phone is serving USB again? (my guess is: I have to re-activate USB-Debugging?) * sorry when I am experimenting around without much understanding, which makes me feel miserable*
See. But why is “X-> recovery mode → fastboot mode” different from “X-> fastboot mode”?
former shown different screenlayout and font, and it allowed the installer script to perform, latter gave only installer-errors.
ADB (Android Debug Bridge) and Fastboot are 2 different things. They just usually come together in the same set of tools.
Accordingly, there’s an adb devices command and a fastboot devices command for device detection.
