Issues with custom ROM and rollback to FPos with the manual install software

Hello, as a long time user of iode OS (on FP4, FP5) i wanted to install it on FP6, i made a mistake during the install and long story short, i’m stuck on the fastboot dialog (not the one with small blue letters but the one with black screen, white letters and you have to do vol+ or vol- to choose the thing you want to boot to.)

The thing is i can’t go to recovery it does not work. i can’t start the OS it does not work
I can detect the phone when i do "fastboot devices" but not much else

on the iodeOS forums someone told me to install FPos back and then reinstall iodeOS.
however, i can’t since i don’t know why the manual install software is almost every time i run it crashing and when it’s not it’s closing because it does not detect the fairphone.

Have you been there before ?

Thank’s for your help :slight_smile:

Also here is the link to the IodeOS topic : Fairphone 6 bootloader relocking gone wrong - Installation Help - iodé community

Welcome to the Community Forum.

Unfortunately I am afraid that your FP6 is “bricked” (and can only be made working again by Fairphone’s repair contractor Cordon in France). This happens when you are trying to install an operating system with older Android security patch level (SPL) than what is currently installed. I cannot say if your Iodé version had a more recent SPL than the Android OS you were trying to install, but the symptoms you describe sound like it.

If this is confirmed, you will need to contact support.fairphone.com and explain that your FP6 is bricked. From recent reports, it will cost around 50 € to get this resolved by Cordon. The device will need to be sent in for this.


EDIT: OK, going by your IodeOS topic, it seems a bit more unclear what has happened and what your options are. Your conversation partner there is probably more knowledgeable about this than I am.

1 Like

Thank you for your reply, i did not know about cordon it’s cool to know that even if it’s bricked there is a workaround somehow, i know i made a mistake so that’s my bad.

But i created this topic to talk about why the FPOS software does not work right, and maybe you know if there is logs of the app somewhere in the folder we download when we manual install ?

Thank’s again :slight_smile:

Tomorow i will read this topic, it might help alot :slight_smile:

So your bootloader is unlocked, correct? Fastboot devices is detecting the phone? Thus no its not a brick normally and could be fixed by yourself. So did you also try to reinstall Iode?

What PC OS do you use?

And to understand why its not working with the FPOS installer, more info would be helpful I guess…at which step does it crash etc.

1 Like

Hello i made a vidéo of the issue just so you see, i know i typed Yes instead of Y at the fairphone 6 discovery fail, but as we see at the end even Y does not work and it crash

icedrive.net/s/ubifh9Bf7D1Dj7TNDGGP9ZtCNWWZ

icedrive.net/s/6X6VVZWAw7fR6V5bbyRy4AB72ibX

Hello guys, i don’t know if you saw my last reply, but i posted a video of the issue i am experiencing with the manual installer

Also just so you know i opened a ticket at fairphone support :slight_smile:

Thank you !

from your link, i cannot read the video, nor download it

I didn’t want to allow download, but sorry, i don’t know why the preview is not working for you.
i’m allowing it now :slight_smile:

sorry again !

@yvmuell @piero-e
Here is the new link : https://icedrive.net/s/6X6VVZWAw7fR6V5bbyRy4AB72ibX

thank’s again :innocent:

preview still don’t work, but i was able to download and read the vidéo.

  1. seen the date, the script have been modified please re-download the original one to be sure.
  2. at some points some script expect the phone in fastbootd mode instead of fastboot, but i am personnaly not able to switch my FP3 to fastbootd only my Samsung

Ok so i downloaded the new script, i’m stuck at the same part.

Also i figured while searching for clues, that adb devices does not catch the device, but fastboot devices do !
And i wondered if there is a guide for fairphone OS like this : [Guide] Fairphone 4 stuck in Fastboot after /e/OS install — Full Fix

i tried fastboot GetVar current_slot and it does not work

tried to reboot in fastbootd :

fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

the device rebooted in fastboot mode but not in fastbootd it seems

Well i think i’ll get in touch with support at this point, i don’t understand how could i screw this that much …

Ok, i did reboot in fastbootd mode by typing fastboot reboot fastbootd :sweat_smile:
Now the Fairphone is stuck on the fairphone splash screen with a tiny line saying “Press any key to shutdown”

And what’s interesting is now the script does not work BUT it is not crashing anymore, I have a loop at the searching device part !

So it does not work but something happened :slight_smile:

1 Like

now launch the Fairphone script, until it stop,
but may have done some magic…
then, reboot to “normal” fastboot and retry with the Fairphone script,
and again if needed reboot to fastbootd… etc … etc …

.

not working on my FP3

In deed !

It worked for some couple seconds !!

And after it failed again :face_exhaling:

I tried what is mentionned at the end of the script, i removed the battery but the phone wont powerup without the battery when i push volume down and plug the usb-C

should i bother about this ?

Ok ! Progress !

I did try to go back and forth in fastboot then fastbootd Then BOOP !

It was working fine until Sending ‘vbmeta_b’ (12 KB) i don’t know why the phone kinda stopped listenning

INFO: One The Fairphone (Gen. 6) in fastboot mode found (serial number: xxxxxxxx).
INFO: The device is fully unlocked.
INFO: Proceeding to flash the device.
INFO: flashing partitions…
Sending ‘abl_a’ (239 KB) OKAY [ 0.007s]
Writing ‘abl_a’ OKAY [ 0.001s]
Finished. Total time: 0.022s
Sending ‘abl_b’ (239 KB) OKAY [ 0.006s]
Writing ‘abl_b’ OKAY [ 0.002s]
Finished. Total time: 0.021s
Sending ‘aop_a’ (311 KB) OKAY [ 0.008s]
Writing ‘aop_a’ OKAY [ 0.002s]
Finished. Total time: 0.023s
Sending ‘aop_b’ (311 KB) OKAY [ 0.008s]
Writing ‘aop_b’ OKAY [ 0.002s]
Finished. Total time: 0.025s
Sending ‘aop_config_a’ (19 KB) OKAY [ 0.002s]
Writing ‘aop_config_a’ OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending ‘aop_config_b’ (19 KB) OKAY [ 0.001s]
Writing ‘aop_config_b’ OKAY [ 0.002s]
Finished. Total time: 0.017s
Sending ‘bluetooth_a’ (812 KB) OKAY [ 0.020s]
Writing ‘bluetooth_a’ OKAY [ 0.002s]
Finished. Total time: 0.035s
Sending ‘bluetooth_b’ (812 KB) OKAY [ 0.020s]
Writing ‘bluetooth_b’ OKAY [ 0.002s]
Finished. Total time: 0.036s
Sending ‘cpucp_a’ (199 KB) OKAY [ 0.006s]
Writing ‘cpucp_a’ OKAY [ 0.001s]
Finished. Total time: 0.020s
Sending ‘cpucp_b’ (199 KB) OKAY [ 0.006s]
Writing ‘cpucp_b’ OKAY [ 0.003s]
Finished. Total time: 0.020s
Sending ‘cpucp_dtb_a’ (11 KB) OKAY [ 0.002s]
Writing ‘cpucp_dtb_a’ OKAY [ 0.000s]
Finished. Total time: 0.015s
Sending ‘cpucp_dtb_b’ (11 KB) OKAY [ 0.001s]
Writing ‘cpucp_dtb_b’ OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending ‘devcfg_a’ (47 KB) OKAY [ 0.002s]
Writing ‘devcfg_a’ OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending ‘devcfg_b’ (47 KB) OKAY [ 0.002s]
Writing ‘devcfg_b’ OKAY [ 0.001s]
Finished. Total time: 0.015s
Sending ‘dsp_a’ (65536 KB) OKAY [ 1.505s]
Writing ‘dsp_a’ OKAY [ 0.032s]
Finished. Total time: 1.550s
Sending ‘dsp_b’ (65536 KB) OKAY [ 1.506s]
Writing ‘dsp_b’ OKAY [ 0.032s]
Finished. Total time: 1.551s
Sending ‘featenabler_a’ (102 KB) OKAY [ 0.004s]
Writing ‘featenabler_a’ OKAY [ 0.001s]
Finished. Total time: 0.019s
Sending ‘featenabler_b’ (102 KB) OKAY [ 0.003s]
Writing ‘featenabler_b’ OKAY [ 0.002s]
Finished. Total time: 0.019s
Sending ‘hyp_a’ (1642 KB) OKAY [ 0.039s]
Writing ‘hyp_a’ OKAY [ 0.002s]
Finished. Total time: 0.054s
Sending ‘hyp_b’ (1642 KB) OKAY [ 0.038s]
Writing ‘hyp_b’ OKAY [ 0.002s]
Finished. Total time: 0.053s
Sending ‘imagefv_a’ (51 KB) OKAY [ 0.002s]
Writing ‘imagefv_a’ OKAY [ 0.002s]
Finished. Total time: 0.017s
Sending ‘imagefv_b’ (51 KB) OKAY [ 0.002s]
Writing ‘imagefv_b’ OKAY [ 0.002s]
Finished. Total time: 0.018s
Sending ‘keymaster_a’ (430 KB) OKAY [ 0.011s]
Writing ‘keymaster_a’ OKAY [ 0.003s]
Finished. Total time: 0.027s
Sending ‘keymaster_b’ (430 KB) OKAY [ 0.010s]
Writing ‘keymaster_b’ OKAY [ 0.006s]
Finished. Total time: 0.030s
Sending ‘logfs’ (16 KB) OKAY [ 0.003s]
Writing ‘logfs’ OKAY [ 0.005s]
Finished. Total time: 0.019s
Sending ‘modem_a’ (181100 KB) OKAY [ 4.179s]
Writing ‘modem_a’ OKAY [ 0.088s]
Finished. Total time: 4.280s
Sending ‘modem_b’ (181100 KB) OKAY [ 4.180s]
Writing ‘modem_b’ OKAY [ 0.088s]
Finished. Total time: 4.282s
Sending ‘multiimgoem_a’ (11 KB) OKAY [ 0.001s]
Writing ‘multiimgoem_a’ OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending ‘multiimgoem_b’ (11 KB) OKAY [ 0.001s]
Writing ‘multiimgoem_b’ OKAY [ 0.003s]
Finished. Total time: 0.020s
Sending ‘pvmfw_a’ (1024 KB) OKAY [ 0.024s]
Writing ‘pvmfw_a’ OKAY [ 0.001s]
Finished. Total time: 0.039s
Sending ‘pvmfw_b’ (1024 KB) OKAY [ 0.024s]
Writing ‘pvmfw_b’ OKAY [ 0.000s]
Finished. Total time: 0.039s
Sending ‘qupfw_a’ (59 KB) OKAY [ 0.003s]
Writing ‘qupfw_a’ OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending ‘qupfw_b’ (59 KB) OKAY [ 0.001s]
Writing ‘qupfw_b’ OKAY [ 0.002s]
Finished. Total time: 0.021s
Sending ‘shrm_a’ (50 KB) OKAY [ 0.002s]
Writing ‘shrm_a’ OKAY [ 0.001s]
Finished. Total time: 0.016s
Sending ‘shrm_b’ (50 KB) OKAY [ 0.002s]
Writing ‘shrm_b’ OKAY [ 0.001s]
Finished. Total time: 0.017s
Sending ‘storsec’ (32 KB) OKAY [ 0.001s]
Writing ‘storsec’ OKAY [ 0.001s]
Finished. Total time: 0.016s
Sending ‘study’ (3272 KB) OKAY [ 0.076s]
Writing ‘study’ OKAY [ 0.002s]
Finished. Total time: 0.091s
Sending ‘studybk_a’ (3272 KB) OKAY [ 0.076s]
Writing ‘studybk_a’ OKAY [ 0.003s]
Finished. Total time: 0.091s
Sending ‘studybk_b’ (3272 KB) OKAY [ 0.074s]
Writing ‘studybk_b’ OKAY [ 0.004s]
Finished. Total time: 0.092s
Sending ‘toolsfv’ (384 KB) OKAY [ 0.009s]
Writing ‘toolsfv’ OKAY [ 0.002s]
Finished. Total time: 0.024s
Sending ‘tz_a’ (3932 KB) OKAY [ 0.090s]
Writing ‘tz_a’ OKAY [ 0.003s]
Finished. Total time: 0.106s
Sending ‘tz_b’ (3932 KB) OKAY [ 0.091s]
Writing ‘tz_b’ OKAY [ 0.004s]
Finished. Total time: 0.107s
Sending ‘uefi_a’ (2835 KB) OKAY [ 0.065s]
Writing ‘uefi_a’ OKAY [ 0.003s]
Finished. Total time: 0.082s
Sending ‘uefi_b’ (2835 KB) OKAY [ 0.066s]
Writing ‘uefi_b’ OKAY [ 0.003s]
Finished. Total time: 0.082s
Sending ‘uefisecapp_a’ (192 KB) OKAY [ 0.005s]
Writing ‘uefisecapp_a’ OKAY [ 0.002s]
Finished. Total time: 0.024s
Sending ‘uefisecapp_b’ (192 KB) OKAY [ 0.005s]
Writing ‘uefisecapp_b’ OKAY [ 0.001s]
Finished. Total time: 0.020s
Sending ‘vm-bootsys_a’ (502200 KB) OKAY [ 11.539s]
Writing ‘vm-bootsys_a’ OKAY [ 0.249s]
Finished. Total time: 11.910s
Sending ‘vm-bootsys_b’ (502200 KB) OKAY [ 11.536s]
Writing ‘vm-bootsys_b’ OKAY [ 0.252s]
Finished. Total time: 11.907s
Sending ‘vm-persist’ (122284 KB) OKAY [ 2.808s]
Writing ‘vm-persist’ OKAY [ 0.070s]
Finished. Total time: 2.918s
Sending ‘xbl_a’ (1138 KB) OKAY [ 0.027s]
Writing ‘xbl_a’ OKAY [ 0.010s]
Finished. Total time: 0.050s
Sending ‘xbl_b’ (1138 KB) OKAY [ 0.027s]
Writing ‘xbl_b’ OKAY [ 0.009s]
Finished. Total time: 0.048s
Sending ‘xbl_config_a’ (300 KB) OKAY [ 0.008s]
Writing ‘xbl_config_a’ OKAY [ 0.008s]
Finished. Total time: 0.029s
Sending ‘xbl_config_b’ (300 KB) OKAY [ 0.008s]
Writing ‘xbl_config_b’ OKAY [ 0.010s]
Finished. Total time: 0.031s
Sending ‘xbl_ramdump_a’ (839 KB) OKAY [ 0.020s]
Writing ‘xbl_ramdump_a’ OKAY [ 0.004s]
Finished. Total time: 0.038s
Sending ‘xbl_ramdump_b’ (839 KB) OKAY [ 0.020s]
Writing ‘xbl_ramdump_b’ OKAY [ 0.005s]
Finished. Total time: 0.038s
Sending ‘boot_a’ (98304 KB) OKAY [ 2.259s]
Writing ‘boot_a’ OKAY [ 0.054s]
Finished. Total time: 2.325s
Sending ‘boot_b’ (98304 KB) OKAY [ 2.260s]
Writing ‘boot_b’ OKAY [ 0.051s]
Finished. Total time: 2.323s
Sending ‘dtbo_a’ (30720 KB) OKAY [ 0.705s]
Writing ‘dtbo_a’ OKAY [ 0.018s]
Finished. Total time: 0.736s
Sending ‘dtbo_b’ (30720 KB) OKAY [ 0.706s]
Writing ‘dtbo_b’ OKAY [ 0.015s]
Finished. Total time: 0.734s
Sending ‘init_boot_a’ (8192 KB) OKAY [ 0.188s]
Writing ‘init_boot_a’ OKAY [ 0.005s]
Finished. Total time: 0.206s
Sending ‘init_boot_b’ (8192 KB) OKAY [ 0.188s]
Writing ‘init_boot_b’ OKAY [ 0.005s]
Finished. Total time: 0.206s
Sending ‘recovery_a’ (102400 KB) OKAY [ 2.351s]
Writing ‘recovery_a’ OKAY [ 0.049s]
Finished. Total time: 2.416s
Sending ‘recovery_b’ (102400 KB) OKAY [ 2.352s]
Writing ‘recovery_b’ OKAY [ 0.052s]
Finished. Total time: 2.417s
Sending sparse ‘super’ 1/9 (722664 KB) OKAY [ 16.869s]
Writing ‘super’ OKAY [ 0.005s]
Sending sparse ‘super’ 2/9 (786364 KB) OKAY [ 18.357s]
Writing ‘super’ OKAY [ 0.011s]
Sending sparse ‘super’ 3/9 (786364 KB) OKAY [ 18.339s]
Writing ‘super’ OKAY [ 0.007s]
Sending sparse ‘super’ 4/9 (777024 KB) OKAY [ 18.118s]
Writing ‘super’ OKAY [ 0.008s]
Sending sparse ‘super’ 5/9 (786360 KB) OKAY [ 18.303s]
Writing ‘super’ OKAY [ 0.005s]
Sending sparse ‘super’ 6/9 (749596 KB) OKAY [ 17.459s]
Writing ‘super’ OKAY [ 0.009s]
Sending sparse ‘super’ 7/9 (772152 KB) OKAY [ 17.989s]
Writing ‘super’ OKAY [ 0.005s]
Sending sparse ‘super’ 8/9 (778496 KB) OKAY [ 18.118s]
Writing ‘super’ OKAY [ 0.007s]
Sending sparse ‘super’ 9/9 (97308 KB) OKAY [ 2.271s]
Writing ‘super’ OKAY [ 0.010s]
Finished. Total time: 151.227s
Sending ‘vbmeta_a’ (12 KB) OKAY [ 0.002s]
Writing ‘vbmeta_a’ OKAY [ 0.004s]
Finished. Total time: 0.030s
Sending ‘vbmeta_b’ (12 KB)

Okay SO i have found the pattern i should follow to get the files uploading on my phone :

  1. Boot flash_fp6_factory

  2. on a CMD aside do fastboot.exe reboot fastboot

  3. then do it again

  4. on the flash_fp6_factory window, type YES

  5. The phone land in the fairphone splash screen with a tiny line “ “Press any key to shutdown”

  6. Now the fairphone will not be able to be detected by the script ( you have a loop when typing Y)

  7. On the CMD screen type fastboot.exe reboot fastbootd, it will say < Waiting for device > because you are still on the splash screen on the FP6

  8. Now press a button on the FP6 and at the same time type Y on the Script screen

  9. The fairphone is now detected and the install begins !

I don’t know if it make sense but it worked for me :smiling_face_with_tear:
Thank you everyone, i really learn some things here !
As my phone is now on FPOS, i’ll get back to iodeOS forums !

Until next time i guess :rofl:

take care y’all

3 Likes

plot twist :
I managed to get myself in the exact same place, i don’t understand why it happened since this time i made sure oem unlock were toggled on the phone usb debugging etc …

I used FP6.QREL.15.151.0 (November Build) and on Iode OS i downloaded iode-7.1-20260116-FP6-fastboot.zip from one day ago, there may be an issue with the security patch ..

the SPL to take on consideration are

  • the one that was registred the last time you applied the unlock,
  • and the one installed when you apply the relock.

.

to bypass the FRP lock, you must install Stock OS (not sure, but maybe also LineageOS + Gapps) and use it to remove any Gogol account and screen lock or SIM lock or carrier lock
before installing any alternative android OS