Thanks again for taking the time.
I am using Git Bash.
So my equivalent returns this:
$ /c/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys/fastboot.exe
fastboot: usage: no command
Just to confirm so we don’t go off wrong … as I don’t know Windows well enough … please can you connect your Fastboot enabled FP5 and paste all lines as if:
cd /path/to/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys/
fastboot devices
OR
fastboot --help
Hmm
cd /c/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys/
fastboot devices
bash: fastboot: command not found
Sorry it should be
./fastboot devices
and / or what happens with
./fastboot.exe --help
OK yes, that makes sense. So :
/c/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys
$ ./fastboot devices
1f070822 fastboot
That is the serial number of my FP5, but
$ cd /c/IMG-e-2.5-t-20241108446629-official-FP5/
$ chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh
**** Fairphone 5 flashing script ****
INFO: The procedure will start soon. Please wait…
Note that this will detect and flash only on Fairphone 5 device.
INFO: You are using MinGW on Windows
INFO: Looking for connected device(s)…
INFO: One Fairphone 5 in fastboot mode found (serial number: 1f070822).
Info: Your phone is in regular bootloader mode.
Error: Your phone is still locked.
Did you execute ‘fastboot flashing unlock’?
Error: Your phone is not ready for flashing yet (see above), aborting…
So please can we look at what variation of
fastboot --version
might exist on this machine.
They are :
/c/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys
$ ./fastboot --version
fastboot version 33.0.3-8952118
Installed as C:\IMG-e-2.5-t-20241108446629-official-FP5\bin-msys\fastboot.exe
and
/c/platform-tools
$ ./fastboot --version
fastboot version 35.0.2-12147458
Installed as C:\platform-tools\fastboot.exe
So I copied the newer version into the bin-msys just to see what would happen but I get the same error.
Edit in light of your added:
I think all this really tells us is that you can lock and unlock your FP5 on this machine with fastboot version 35.0.2-12147458 but the script is failing to run with fastboot version 33.0.3-8952118
So (another edit) the following suggestion may not be so attractive … hmmm
Am I right to say that platform-tools is not system installed on this machine?
Are you drawn to the suggestion to
… and the aim would be to provide fastboot form /c/platform-tools …
Edit for clarity perhaps as Adding adb path to the environment variables.
Aside to the “recommended script way” and the “traditional fastboot way” here we can considere an “alternative recovery way” that can be flashing the recovery.img from the “IMG-e.zip” file on both slots, then boot to recovery and install the e-2.5-t-20241108446629-official-FP5.zip
I replaced the older fastboot.exe in bin-msys with the newer version from platform-tools which made no difference.
When you ask if platform-tools is installed on this machine, the answer is that Platform Tools was downloaded and unzipped as per the instructions. I can run it from either c/platform-tools or from c/ IMG-e-2.5-t-20241108446629-official-FP5/bin-msys by navigating to either directory and prefacing the fastboot command with ./
Is there some other way of installing fastboot?
When I refer to “system installed” it involves “Adding adb (and fastboot) path to the environment variables” as the link in my last post.
I don’t think that fastboot is the problem, but the script.
OK, I added an environment variable in the system (windows) and…
That fixed it. I thought I was going nuts there for a moment.
I just want to say thanks for your patience in going through this with me - I might have got there in the end but I might also have give up by now.
I will add a comment here Flashing script wrongfully claims the phone is still locked so the next user maybe gets there a bit quicker.
Have a good day !
1 Like
Hi there folks,
I’ve had the same issues as nickd here had and add to that that I needed to be root on the terminal in order for things to fly. I’ve also temporarily added the PATH entry within the “root” shell.
Finally I’ve also faced an error while flashing the device:
Setting current slot to 'a' FAILED (remote: 'Unable to set slot')
fastboot: error: Command failed
This was due because within that attempt I’ve seated/booted the phone within the fastbootd menu – I rebooted to the bootloader menu and attempted the flashing again and all went fine…
I’m currently not so at ease with “re-locking” my phone although I’ve made sure the updates where below the ones flashed… it was, still really do not wanna brick that board…
Cheers,
o.
EDIT: all fine, locked again… fear not, think and do wisely =)
bobby@70h:~/Desktop/FP5/platform-tools$ sudo ./fastboot flashing lock_critical
OKAY [ 0.027s]
Finished. Total time: 0.028s
bobby@70h:~/Desktop/FP5/platform-tools$ sudo ./fastboot flashing lock
OKAY [ 0.027s]
Finished. Total time: 0.027s