Stazi
January 23, 2025, 11:48pm
1
A few hours ago I think I bricked my Fairphone 5 by trying to install the /e/OS. I downloaded the latest 2.7 official IMG zip and used the guide and Git Bash to do the install but it always freezes at
Sending sparse 'super' 1/6 (762373 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
ERROR: Could not flash the super partition on device
I’ve tried changing cables and a lot of other things I’ve seen on the forum but nothing has worked. Right now I cannot load into any OS but I can reach the Recovery for /e/OS. My goal is to either finish the installation or somehow reinstall the original OS.
The bootloader is still unlocked
markum
January 24, 2025, 8:58am
2
I fear, you might have stumbled on the problem which bricked my device 10 months ago:
"The FP5 comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information"https://doc.e.foundation/devices/FP5/install
If this is the case, you have no choice than sending the FP5 in for repair. I am sure others will give you some commands to test, if you can get your device back running or if you have to send it in.
As the bootoloader is unlocked it should be possible to just reinstall FPOS. Anti rollback is only relevant when you lock the bootloader
You should be able to boot into fastboot? This means you could just reinstall FPOS
Stazi
January 24, 2025, 9:43am
5
I confirmed that the previous android patch was done in August in 2024 and the /e/OS version I was moving to was released January 11th 2025.
Stazi
January 24, 2025, 9:50am
6
When I tried to reinstall FPOS
@DESKTOP-CC3GG5H MINGW64 ~/Desktop/FP5-UT2H-factory/FP5-UT2H-factory
$ chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh
*** Fairphone 5 flashing script ***
INFO: The procedure will start soon. Please wait...
INFO: The package type is "user-factory"
INFO: You are using MinGW on Windows
INFO: Validating the integrity of the package.
This might take a while. Please wait...
INFO: Validation complete.
WARNING: Flashing this image wipes all user data and settings on the phone.
It will also remove the Google factory reset protection.
Are you sure you want to continue?
Type "Yes" (case sensitive) and press enter to continue: Yes
INFO: Looking for connected device(s)...
INFO: One Fairphone 5 in fastboot mode found (serial number: 95c652b6).
INFO: The device is fully unlocked.
INFO: Proceeding to flash the device.
INFO: flashing partitions...
Sending 'abl_a' (152 KB) OKAY [ 0.006s]
Writing 'abl_a' OKAY [ 0.002s]
Finished. Total time: 0.019s
Sending 'abl_b' (152 KB) OKAY [ 0.005s]
Writing 'abl_b' OKAY [ 0.001s]
Finished. Total time: 0.019s
Sending 'aop_a' (203 KB) OKAY [ 0.006s]
Writing 'aop_a' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'aop_b' (203 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.002s]
Finished. Total time: 0.021s
Sending 'apdp' (13 KB) OKAY [ 0.002s]
Writing 'apdp' OKAY [ 0.002s]
Finished. Total time: 0.022s
Sending 'bluetooth_a' (3388 KB) OKAY [ 0.073s]
Writing 'bluetooth_a' OKAY [ 0.009s]
Finished. Total time: 0.096s
Sending 'bluetooth_b' (3388 KB) OKAY [ 0.073s]
Writing 'bluetooth_b' OKAY [ 0.012s]
Finished. Total time: 0.099s
Sending 'cpucp_a' (182 KB) OKAY [ 0.006s]
Writing 'cpucp_a' OKAY [ 0.002s]
Finished. Total time: 0.019s
Sending 'cpucp_b' (182 KB) OKAY [ 0.006s]
Writing 'cpucp_b' OKAY [ 0.002s]
Finished. Total time: 0.020s
Sending 'ddr' (20 KB) OKAY [ 0.002s]
Writing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.014s
Sending 'devcfg_a' (52 KB) OKAY [ 0.003s]
Writing 'devcfg_a' OKAY [ 0.002s]
Finished. Total time: 0.023s
Sending 'devcfg_b' (52 KB) OKAY [ 0.003s]
Writing 'devcfg_b' OKAY [ 0.007s]
Finished. Total time: 0.029s
Sending 'dsp_a' (65536 KB) OKAY [ 1.393s]
Writing 'dsp_a' OKAY [ 0.136s]
Finished. Total time: 1.541s
Sending 'dsp_b' (65536 KB) OKAY [ 1.411s]
Writing 'dsp_b' OKAY [ 0.099s]
Finished. Total time: 1.523s
Sending 'featenabler_a' (84 KB) OKAY [ 0.004s]
Writing 'featenabler_a' OKAY [ 0.012s]
Finished. Total time: 0.028s
Sending 'featenabler_b' (84 KB) OKAY [ 0.004s]
Writing 'featenabler_b' OKAY [ 0.005s]
Finished. Total time: 0.022s
Sending 'hyp_a' (3601 KB) OKAY [ 0.078s]
Writing 'hyp_a' OKAY [ 0.012s]
Finished. Total time: 0.105s
Sending 'hyp_b' (3601 KB) OKAY [ 0.078s]
Writing 'hyp_b' OKAY [ 0.021s]
Finished. Total time: 0.112s
Sending 'imagefv_a' (64 KB) OKAY [ 0.003s]
Writing 'imagefv_a' OKAY [ 0.004s]
Finished. Total time: 0.019s
Sending 'imagefv_b' (64 KB) OKAY [ 0.003s]
Writing 'imagefv_b' OKAY [ 0.005s]
Finished. Total time: 0.020s
Sending 'keymaster_a' (261 KB) OKAY [ 0.008s]
Writing 'keymaster_a' OKAY [ 0.003s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (261 KB) OKAY [ 0.007s]
Writing 'keymaster_b' OKAY [ 0.009s]
Finished. Total time: 0.030s
Sending 'logfs' (16 KB) OKAY [ 0.002s]
Writing 'logfs' OKAY [ 0.001s]
Finished. Total time: 0.014s
Sending 'modem_a' (184796 KB) OKAY [ 4.000s]
Writing 'modem_a' OKAY [ 0.561s]
Finished. Total time: 4.593s
Sending 'modem_b' (184796 KB) OKAY [ 3.954s]
Writing 'modem_b' OKAY [ 0.619s]
Finished. Total time: 4.584s
Sending 'multiimgoem_a' (13 KB) OKAY [ 0.002s]
Writing 'multiimgoem_a' OKAY [ 0.002s]
Finished. Total time: 0.015s
Sending 'multiimgoem_b' (13 KB) OKAY [ 0.002s]
Writing 'multiimgoem_b' OKAY [ 0.002s]
Finished. Total time: 0.015s
Sending 'qupfw_a' (55 KB) OKAY [ 0.002s]
Writing 'qupfw_a' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'qupfw_b' (55 KB) OKAY [ 0.003s]
Writing 'qupfw_b' OKAY [ 0.012s]
Finished. Total time: 0.025s
Sending 'rtice' (261 KB) OKAY [ 0.013s]
Writing 'rtice' OKAY [ 0.007s]
Finished. Total time: 0.031s
Sending 'shrm_a' (44 KB) OKAY [ 0.002s]
Writing 'shrm_a' OKAY [ 0.011s]
Finished. Total time: 0.024s
Sending 'shrm_b' (44 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.011s]
Finished. Total time: 0.024s
Sending 'storsec' (20 KB) OKAY [ 0.002s]
Writing 'storsec' OKAY [ 0.002s]
Finished. Total time: 0.014s
Sending 'study' (240 KB) OKAY [ 0.007s]
Writing 'study' OKAY [ 0.001s]
Finished. Total time: 0.019s
Sending 'studybk_a' (240 KB) OKAY [ 0.006s]
Writing 'studybk_a' OKAY [ 0.002s]
Finished. Total time: 0.031s
Sending 'studybk_b' (240 KB) OKAY [ 0.006s]
Writing 'studybk_b' OKAY [ 0.002s]
Finished. Total time: 0.020s
Sending 'tz_a' (3713 KB) OKAY [ 0.080s]
Writing 'tz_a' OKAY [ 0.018s]
Finished. Total time: 0.109s
Sending 'tz_b' (3713 KB) OKAY [ 0.080s]
Writing 'tz_b' OKAY [ 0.023s]
Finished. Total time: 0.113s
Sending 'uefisecapp_a' (122 KB) OKAY [ 0.004s]
Writing 'uefisecapp_a' OKAY [ 0.005s]
Finished. Total time: 0.020s
Sending 'uefisecapp_b' (122 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.004s]
Finished. Total time: 0.019s
Sending 'xbl_a' (3602 KB) OKAY [ 0.078s]
Writing 'xbl_a' OKAY [ 0.015s]
Finished. Total time: 0.104s
Sending 'xbl_b' (3602 KB) OKAY [ 0.078s]
Writing 'xbl_b' OKAY [ 0.013s]
Finished. Total time: 0.102s
Sending 'xbl_config_a' (220 KB) OKAY [ 0.006s]
Writing 'xbl_config_a' OKAY [ 0.004s]
Finished. Total time: 0.023s
Sending 'xbl_config_b' (220 KB) OKAY [ 0.006s]
Writing 'xbl_config_b' OKAY [ 0.004s]
Finished. Total time: 0.029s
Sending 'boot_a' (98304 KB) OKAY [ 2.083s]
Writing 'boot_a' OKAY [ 0.318s]
Finished. Total time: 2.414s
Sending 'boot_b' (98304 KB) OKAY [ 2.084s]
Writing 'boot_b' OKAY [ 0.314s]
Finished. Total time: 2.412s
Sending 'dtbo_a' (24576 KB) OKAY [ 0.521s]
Writing 'dtbo_a' OKAY [ 0.120s]
Finished. Total time: 0.653s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.520s]
Writing 'dtbo_b' OKAY [ 0.141s]
Finished. Total time: 0.674s
Sending sparse 'super' 1/9 (726508 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
ERROR: Could not flash the super partition on device 95c652b6.
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).
the download still fails when it reaches the “Sending sparse ‘super’”
yvmuell
January 24, 2025, 10:05am
7
critical is unlocked as well?
Edit what PC system do you use?
Hi, I’m trying to get back to FairphoneOS after trying CalyxOS.
Unfortuantely I’m stack on the last step (flash script).
Everything in previous steps went well, except fastboot flashing unlock_critical, it returns
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
When I try to run shell script I get after a while:
Sending 'dtbo_b' (24576 KB) OKAY [ 0.843s]
Writing 'dtbo_b' OKAY [ 0.103s]
Finished. Total…
Stazi
January 24, 2025, 10:11am
8
I’m Currently using windows 10
yvmuell
January 24, 2025, 10:14am
9
And critical is unlocked?
Maybe its still a fastboot issue do you use official google adb/fastboot platform tools?
Edit and maybe its still a cable issue
That still sounds like the usual fastboot USB problems, have you tried every cable and port combination you have at your disposal? It can be quite hard to find the right combination sometimes.
I’m a bit more worried about those white lines on the bottom of your screen, is that just in the picture or are those always there?
Stazi
January 24, 2025, 10:27am
10
I did Unlock Critical, and i am using the platform tools linked in the official /e/OS installation guide in combination with Git Bash to make the installation.
Is there a fast boot command I can use to show you the Unlock status
FPbonn
January 24, 2025, 10:50am
11
$ fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Adb enabled: false
OKAY [ 0.069s]
Example from a FP3.
3 Likes
Stazi
January 24, 2025, 9:09pm
13
Here is what I have
\Desktop\platform-tools>fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.005s]
Finished. Total time: 0.005s
FPbonn
January 24, 2025, 9:45pm
14
For me it looks like a read error of the source file (sparse file format ).android tools version ?live system and flash your FP5 using the android tools of the linux distribution.
1 Like
Stazi
January 25, 2025, 12:49am
15
I installed Ubunto onto a flash and followed the install steps again on that OS System and everything went smoothly. I believe there’s some issue with my android tools on Windows.
When installed Ideos on my FP4 I also had problems until I updated the USB drivers on my Windows 10 notebook. With the updated USB drivers all went smoothly then.
felza
January 27, 2025, 3:52pm
18
Were you able to re-lock the bootloader too? Or did you leave it unlocked?