How to install /e/OS with Linux Debian "Bullseye"on Fp4?It stopps on Fastboot!?

When I turn it on now, this message always comes up, and when I confirm with “Power” I end up in the new settings system, like in the picture here:https://commons.wikimedia.org/wiki/File:Unlocked_Android_Bootloader_Warning_Message.png…and then, after booting, the “Hello” start screen appears with a start button for language confirmation.

Thanks for the feedback – we both learn, I hope !

As I understood it, unlocking the bootloader initiates a Factory reset. If you still had wifi in action, what happened at that point seems less than a Factory reset.

No harm done … please follow on with the advice of @Ingo_FP_Angel.

1 Like

Blockzitat What mode was the phone in during those last two commands

root@debiano:~# adb reboot bootloader
error: no devices/emulators found
root@debiano:~# fastboot flashing unlock_critical
< waiting for any device >

I have to try that again! Is that possible in my current status?
to my last comment here:

Blockzitat
When I turn it on now, this message always comes up, and when I confirm with “Power” I end up in the new settings system, like in the picture here:https://commons.wikimedia.org/wiki/File:Unlocked_Android_Bootloader_Warning_Message.png …and then, after booting, the “Hello” start screen appears with a start button for language confirmation.

I’ve tried it again: first when it was switched off, pressed the “-” button, then connected, I was in fastboot, then these messages came up after I made entries:

root@debiano:~# adb reboot bootloader
error: no devices/emulators found
root@debiano:~# fastboot flashing unlock_critical
                                                   FAILED (remote: '    Device already : unlocked!')
fastboot: error: Command failed
root@debiano:~# 

Hey Ingo,

man sag das doch gleich, dass du aus Hamburg kommst und so wie ich deutsch sprichst! :wink:…man ey, das macht es doch bestimmt erstmal etwas einfacher…ich muss sonst immer mit dem Google-Umsetzter hin und herzwitschen…ok, ab jetzt in deutsch wa…(“ik bin än berliner”)…man quatscht in Brandenburg hier auch so…

Ich hab auf Englisch geantwortet, weils schon auf Englisch war und aibd m.E. kein Deutsch versteht und ich schon wusste, dass ich am Nachmittag (also jetzt gleich) erstmal keine Zeit mehr haben werde.

Daher jetzt nur ganz kurz: wenn das Phone im Fastboot-Modus ist, funktioniert nur fastboot und kein adb.
Im Recovery Mode und im normalen Systemmodus mit USB-Debugging an funktioniert nur adb und kein fastboot.

Das fastboot flashing unlock_critical hat zwar einen Fehlschlag vermeldet, aber “Device already : unlocked!” würde ich jetzt so interpretieren, dass Du einfach fortfahren kannst mit den Instruktionen.

Warum gibt es eigentlich 2 unterschiedliche Bootbildschirme?Ich hatte jetzt eben diesen hier:https://forum.fairphone.com/uploads/default/original/3X/b/b/bbc10f4dfe9058f224622931add8e02fce262488.jpeg
Und vorher den 2-farbigen, wenn ich die “-” Taste drücke und mit USB verbinde?Warum ist das so??Welchen soll ich nun nehmen?

Hi @DeepHouse – let’s try both languages !

At a simple level an Android phone has 3 modes in which to boot:

  • Normal
  • fastboot
  • Recovery

It is a feature of Fairphone (and other manufacturers) that one is given the convenience of a Bootloader screen – this gives the user flexibility. It is not the same as a bootable mode. As I understand @Ingo_FP_Angel’s text, I should be saying nothing new!

Your recent image is of Android Recovery.

I advise that you get full control and understanding of these 4 “states” by pressing the hardware buttons. You can then practice with

adb devices
fastboot devices

to know that you have reliable communication.


Hallo @DeepHouse - lassen Sie uns beide Sprachen ausprobieren!

Auf einer einfachen Ebene hat ein Android-Telefon 3 Modi, in denen es starten kann:

  • Normal
  • Fastboot
  • Recovery

Eine Besonderheit von Fairphone (und anderen Herstellern) ist die Möglichkeit, einen Bootloader-Bildschirm einzublenden - das gibt dem Benutzer Flexibilität. Es ist nicht dasselbe wie ein bootfähiger Modus. So wie ich den Text von @Ingo_FP_Angel verstehe, sollte ich nichts Neues sagen!

Ihr aktuelles Bild ist von Android Recovery.

Ich empfehle Ihnen, die volle Kontrolle und das Verständnis für diese 4 “Zustände” zu erlangen, indem Sie die Hardware-Tasten drücken. Sie können dann üben mit

adb devices
fastboot devices

üben, um zu wissen, dass Sie eine zuverlässige Kommunikation haben.

Übersetzt mit www.DeepL.com/Translator (kostenlose Version)

Hallo Ingo,

ich habe es geschafft!..mit gedrückter “-”-Taste verbunden und dann den Verlauf hier im Terminal(als root ging es nicht, warum auch immer…muss ich mal sehen woran das liegt?)…aber nun für die hier, die ähnliches Vorhaben,mir hätte das zuvor bestimmt geholfen.

andre@debiano:~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4$ su -
Passwort: 
root@debiano:~# ~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4
-bash: /root/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4: Datei oder Verzeichnis nicht gefunden
root@debiano:~# cd /home/andre/eOS_1.12.3-s
root@debiano:/home/andre/eOS_1.12.3-s# chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh
chmod: Zugriff auf 'flash_FP4_factory.sh' nicht möglich: Datei oder Verzeichnis nicht gefunden
root@debiano:/home/andre/eOS_1.12.3-s# chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh
chmod: Zugriff auf 'flash_FP4_factory.sh' nicht möglich: Datei oder Verzeichnis nicht gefunden
root@debiano:/home/andre/eOS_1.12.3-s# exit
Abgemeldet
andre@debiano:~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4$ chmod +x flash_FP4_factory.sh && ./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: xxxxxxxx).
Sending 'bluetooth_a' (940 KB)                     OKAY [  0.043s]
Writing 'bluetooth_a'                              OKAY [  0.014s]
Finished. Total time: 0.088s
Sending 'bluetooth_b' (940 KB)                     OKAY [  0.035s]
Writing 'bluetooth_b'                              OKAY [  0.005s]
Finished. Total time: 0.046s
Sending 'devcfg_a' (42 KB)                         OKAY [  0.009s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.024s
Sending 'devcfg_b' (42 KB)                         OKAY [  0.009s]
Writing 'devcfg_b'                                 OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.700s]
Writing 'dsp_a'                                    OKAY [  0.263s]
Finished. Total time: 1.979s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.655s]
Writing 'dsp_b'                                    OKAY [  0.221s]
Finished. Total time: 1.883s
Sending 'modem_a' (149596 KB)                      OKAY [  3.929s]
Writing 'modem_a'                                  OKAY [  0.783s]
Finished. Total time: 4.747s
Sending 'modem_b' (149596 KB)                      OKAY [  3.805s]
Writing 'modem_b'                                  OKAY [  0.740s]
Finished. Total time: 4.552s
Sending 'xbl_a' (3298 KB)                          OKAY [  0.099s]
Writing 'xbl_a'                                    OKAY [  0.172s]
Finished. Total time: 0.294s
Sending 'xbl_b' (3298 KB)                          OKAY [  0.098s]
Writing 'xbl_b'                                    OKAY [  0.157s]
Finished. Total time: 0.263s
Sending 'tz_a' (2944 KB)                           OKAY [  0.082s]
Writing 'tz_a'                                     OKAY [  0.013s]
Finished. Total time: 0.121s
Sending 'tz_b' (2944 KB)                           OKAY [  0.087s]
Writing 'tz_b'                                     OKAY [  0.012s]
Finished. Total time: 0.106s
Sending 'hyp_a' (399 KB)                           OKAY [  0.015s]
Writing 'hyp_a'                                    OKAY [  0.004s]
Finished. Total time: 0.039s
Sending 'hyp_b' (399 KB)                           OKAY [  0.016s]
Writing 'hyp_b'                                    OKAY [  0.005s]
Finished. Total time: 0.027s
Sending 'keymaster_a' (257 KB)                     OKAY [  0.016s]
Writing 'keymaster_a'                              OKAY [  0.003s]
Finished. Total time: 0.036s
Sending 'keymaster_b' (257 KB)                     OKAY [  0.017s]
Writing 'keymaster_b'                              OKAY [  0.002s]
Finished. Total time: 0.037s
Sending 'abl_a' (148 KB)                           OKAY [  0.010s]
Writing 'abl_a'                                    OKAY [  0.002s]
Finished. Total time: 0.027s
Sending 'abl_b' (148 KB)                           OKAY [  0.010s]
Writing 'abl_b'                                    OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'boot_a' (98304 KB)                        OKAY [  2.552s]
Writing 'boot_a'                                   OKAY [  0.539s]
Finished. Total time: 3.118s
Sending 'boot_b' (98304 KB)                        OKAY [  2.516s]
Writing 'boot_b'                                   OKAY [  0.438s]
Finished. Total time: 2.963s
Sending 'recovery_a' (98304 KB)                    OKAY [  2.590s]
Writing 'recovery_a'                               OKAY [  0.408s]
Finished. Total time: 3.019s
Sending 'recovery_b' (98304 KB)                    OKAY [  2.499s]
Writing 'recovery_b'                               OKAY [  0.545s]
Finished. Total time: 3.051s
Sending 'dtbo_a' (24576 KB)                        OKAY [  0.641s]
Writing 'dtbo_a'                                   OKAY [  0.090s]
Finished. Total time: 0.753s
Sending 'dtbo_b' (24576 KB)                        OKAY [  0.621s]
Writing 'dtbo_b'                                   OKAY [  0.081s]
Finished. Total time: 0.708s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.006s]
Writing 'vbmeta_system_a'                          OKAY [  0.001s]
Finished. Total time: 0.037s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.009s]
Writing 'vbmeta_system_b'                          OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'vbmeta_a' (8 KB)                          OKAY [  0.007s]
Writing 'vbmeta_a'                                 OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.010s]
Writing 'vbmeta_b'                                 OKAY [  0.001s]
Finished. Total time: 0.018s
Sending sparse 'super' 1/4 (745639 KB)             OKAY [ 19.799s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 2/4 (764651 KB)             OKAY [ 40.156s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 3/4 (751849 KB)             OKAY [ 21.683s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 4/4 (420416 KB)             OKAY [ 39.455s]
Writing 'super'                                    OKAY [  0.000s]
Finished. Total time: 123.437s
Sending 'aop_a' (174 KB)                           OKAY [  0.009s]
Writing 'aop_a'                                    OKAY [  0.002s]
Finished. Total time: 20.511s
Sending 'aop_b' (174 KB)                           OKAY [  0.007s]
Writing 'aop_b'                                    OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'featenabler_a' (84 KB)                    OKAY [  0.005s]
Writing 'featenabler_a'                            OKAY [  0.002s]
Finished. Total time: 0.026s
Sending 'featenabler_b' (84 KB)                    OKAY [  0.009s]
Writing 'featenabler_b'                            OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'imagefv_a' (524 KB)                       OKAY [  0.027s]
Writing 'imagefv_a'                                OKAY [  0.005s]
Finished. Total time: 0.050s
Sending 'imagefv_b' (524 KB)                       OKAY [  0.026s]
Writing 'imagefv_b'                                OKAY [  0.003s]
Finished. Total time: 0.035s
Sending 'multiimgoem_a' (13 KB)                    OKAY [  0.007s]
Writing 'multiimgoem_a'                            OKAY [  0.001s]
Finished. Total time: 0.016s
Sending 'multiimgoem_b' (13 KB)                    OKAY [  0.009s]
Writing 'multiimgoem_b'                            OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'qupfw_a' (53 KB)                          OKAY [  0.010s]
Writing 'qupfw_a'                                  OKAY [  0.002s]
Finished. Total time: 0.028s
Sending 'qupfw_b' (53 KB)                          OKAY [  0.009s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'uefisecapp_a' (121 KB)                    OKAY [  0.010s]
Writing 'uefisecapp_a'                             OKAY [  0.002s]
Finished. Total time: 0.028s
Sending 'uefisecapp_b' (121 KB)                    OKAY [  0.008s]
Writing 'uefisecapp_b'                             OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'xbl_config_a' (94 KB)                     OKAY [  0.008s]
Writing 'xbl_config_a'                             OKAY [  0.011s]
Finished. Total time: 0.027s
Sending 'xbl_config_b' (94 KB)                     OKAY [  0.009s]
Writing 'xbl_config_b'                             OKAY [  0.007s]
Finished. Total time: 0.024s
Sending 'core_nhlos_a' (111884 KB)                 OKAY [  3.329s]
Writing 'core_nhlos_a'                             OKAY [  0.699s]
Finished. Total time: 4.053s
Sending 'core_nhlos_b' (111884 KB)                 OKAY [  2.896s]
Writing 'core_nhlos_b'                             OKAY [  0.437s]
Finished. Total time: 3.341s
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata'                                 OKAY [  0.217s]
Finished. Total time: 0.222s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'metadata'                                 OKAY [  0.004s]
Finished. Total time: 0.009s
Setting current slot to 'a'                        OKAY [  0.033s]
Finished. Total time: 0.035s
-----------

INFO: Done. The device will reboot now.
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.050s

INFO: You can unplug the USB cable now.

andre@debiano:~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4$ fastboot flashing lock_critical
                                                   OKAY [  0.027s]
Finished. Total time: 0.027s
andre@debiano:~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4$ fastboot flashing lock
                                                   OKAY [  0.027s]
Finished. Total time: 0.027s
andre@debiano:~/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4$ 

Als root warst Du im falschen Verzeichnis (“/home/andre/eOS_1.12.3-s”), richtig gewesen wäre “/home/andre/eOS_1.12.3-s/IMG-e-1.12.3-s-20230616300623-dev-FP4”

1 Like

ok…bin jetzt übrigens übers Fp hier eingeloggt!..ey,das gefällt mir jetzt besser als die alte Aufmachung!Das kommt ja dem Iphone-Styl schon sehr nahe!..nun habe ich gerade ein problem mit telegramm: ich erhalte den aktivierungscode nicht!?Hmm habe schon gegoogelt,das Problem hatten schon viele…mal sehen ob ich auch hier einen threat zu finde!?..also ansonsten erstmal eine geile Sache das System!!!

This topic was automatically closed after 180 days. New replies are no longer allowed.