đŸ‡«đŸ‡· 🇬🇧 Telephone brickĂ© une solution?

Thank you very much for the help
I’ll get in touch with fairphone.

Hoping that this topic can be used by others so that they don’t make the same mistake.
and get fairphone to do something about it.

Merci beaucoup de l’aide
Je vais prendre contact avec fairphone

En esperant que ce topic puisse servir Ă  d’autre pour qu’il ne fasse pas la mĂȘme erreur
et que fairphone fasse quelque chose pour eviter cela

1 Like

I will take the time to test these orders I will make a post to give the results, I think tonight or at worst tomorrow.

Je vais prendre le temps de tester ces commandes je ferais un post pour donner les résultats, je pense ce soir ou au pire demain

1 Like

Tu n’as essayĂ© qu’une seule fois de flasher ? Si oui, tu peux peut-ĂȘtre passer Ă  l’autre slot en essayant plusieurs fois d’allumer ton tel (ça peut ĂȘtre 8 ou plus je crois). Et tu pourras avoir accĂšs au bootloader. Ensuite reviens ici :wink:

1 Like

hello
La commande

./edl.py --loader=sbl1.img printgpt

renvoie
Qualcomm Sahara / Firehose Client © B.Kerler 2018-2019
main - Using loader sbl1.img 

main - Waiting for the device
main - Device detected :slight_smile:
main - Mode detected: sahara
Device is in unknown state

et l’autre commande idem

I’m sorry to answer so late but I had to upgrade to python 3.7 and the debian stretch doesn’t like it so much, I don’t have an active X-org server anymore, but on this side I manage :slight_smile:
As you can see the Qualcomm is well detected but its status is unknown ???
the 2nd command sends me the same message
Now that I have the right python I can test other commands without any worries.

Je suis dĂ©solĂ© de rĂ©pondre si tard mais il a fallu que j’upgrade le systĂšme pour avoir python 3.7 la debian stretch ne l’apprĂ©cie pas trop je n’ai plus de serveur X-org actif, mais de ce cotĂ© la je me dĂ©brouille :slight_smile:
Comme tu peut le voir le Qualcomm est bien détecté mais sont état est inconnu ???
la 2eme commande me renvoie le mĂȘme message
Maintenant que le bon python je peut tester d’autre commande sans soucis

1 Like

J’ai essayĂ© de le dĂ©marrer un bon nombre de fois 10-12 d’affilĂ© en tenant le bouton power environ 10 sec et le bouton power + volume bas environ pareil 10-12 fois en les tentant 10 sec environ
Et il ne se passe rien
Merci de te pencher sur le problĂšme en tout cas

1 Like

Here is another tool for interacting with EDL/QDL mode:

1 Like

La commande
adb reboot edl
me renvoie
error no devices /emulators found

1 Like

You are already in EDL mode, that’s the point


Well, I’m glad, but what do I make of this?
I’m talking to my phone, it’s pretty good but I don’t know what to do with it.
excuse me for that it’s not against you I’m a little annoyed because I feel the solution can be close
I pray to the god stallman for a solution lol

bien je suis content mais j’en fait quoi de ça?
je dialogue avec mon tel c’est plutît bien mais je ne sais pas quoi en faire
excuse moi pour ça ce n’est pas contre toi je m’agace un peu car je sens la solution peut ĂȘtre proche
Je prie le dieu stallman pour avoir une solution lol
pour ceux qui ne sont pas au courant Richard Stallman est le crĂ©ateur de GNU d’oĂč son titre de Dieu :slight_smile:

1 Like

I am not exaclty sure, what is possible.
The first thing I’d try is sending it the sbl1.img as Image.
You can also try changing Mode to “Memory Debug” which may present the EMMC as a mass storage device to your system that would allow restoring sbl1 and aboot.

1 Like

uh how do I change the memory mode (adb, edl.py) or whatever I’m a bit lost with all this, also how do I get the image up?
I’m very happy for your help and I’m sorry to take up your time for me.
Thank you very much.

heu comment je fais pour changer le mode de mĂ©moire (adb, edl.py) ou autre je suis un peu perdu avec tout ça, aussi comment je fais pour remonter l’image
je suis trÚs content de ton aide et je suis désolé de prendre de ton temps pour moi
Merci beaucoup

1 Like

I was suggesting you try to use the second tool i linked to, which has a GUI.

1 Like

pressing power up and down while you turn on the phone, should enable EDL mode (black screen)

sahara and edl.py can load the sbl1.img, but I doubt that is enough in your sitution
you also need to restore aboot and tz and such

1 Like

It seems @basxto and I have a solution for you!

you need edl.py, which you already have.
Download unbrick.zip and extract in the directory where you have edl.py.
Take the battery out of the phone and put it back in.
Connect the phone, then run:

./edl.py wl unbrick --loader=unbrick/prog_emmc_firehose_8953_ddr.mbn && ./edl.py reset

After that you should be able to get back into fastboot.
From there you can use Fairphone_FP3_8901.2.A.0105.20191217_12171325_user_release-keys_dump.zip with @pigpig’s flasher script

7 Likes

@YakRap have you had a chance to try this?

1 Like

Hello everyone.
It took me a while to get back from upgrading my debian from stretch to buster.
I just launched the command and it’s wonderful when I turn on the tel it tells me FAIRPHONE mode unbricked edition
Now he needs to load up a little and I’ll take it from there.
many thanks to @basxto @pigpig @k4y0z and the ones I forget
if you can pass on the information to my German friend who has the same problem if he hasn’t already done so
Really a BIG THANK YOU to all those who took the trouble to look into the problem.
I’ll let you know what happens next

Translated with www.DeepL.com/Translator (free version)

Bonjour a tous
J’ai Ă©tĂ© un peu long a revenir du a l’upgrade de ma debian de stretch vers buster
Je viens de lancer la commande et c’est merveilleux quand j’allume le tel il me dis FAIRPHONE mode unbricked edition
là il faut qu’il charge un peu et je m’occupe de la suite
un grand merci a @basxto @pigpig @k4y0z et ceux que j’oublie
si vous pouvez transmettez l’information Ă  mon ami allemand qui a le mĂȘme problĂšme si ce n’est dĂ©jĂ  fait
Vraiment un GRAND MERCI Ă  tous ceux qui on pris la peine de se pencher sur le problĂšme
Je vous tiens au courant de la suite

5 Likes

Glad to hear, it worked out for you!

That was a little joke on our side, SCNR :rofl:

To get back your normal bootlogo head over here:

To everyone wondering, what he’s talking about:

5 Likes

I still have a problem with flash.sh and the command returns FAILED (remote Partition flashing is not allowed).
Maybe it’s because on this one in fastboot mode I have DEVICE STATE - locked

Pour la suite j’ai encore un problùme avec flash.sh la commande me renvoie FAILED (remote Partition flashing is not allowed)
C’est peut ĂȘtre du fait que sur le tel en mode fastboot j’ai DEVICE STATE - locked

Otherwise for the image I will keep it for a while in memory of my mistake and the people who helped me.

Sinon pour l’image je vais la garder quelque temps en souvenir de mon erreur et des gens qui mon aidĂ©

I did not think of that


Try the following command:
fastboot oem unlock

or if that doesn’t work try:
fastboot oem 8901_unlock

EDIT:
Did you have to unlock when you flashed the FP2 FPOOS?

1 Like

No when I flashed it I didn’t unlock anything the flashing is done without any question with FP2 OS
there he is doing the flash with lots of OKAY.
and
 he just finished with Slot b was successfully flashed.

Non quand je l’ai flashĂ© je n’ai rien dĂ©verrouiller le flashage c’est effectuĂ© sans posĂ© de question avec FP2 OS
lĂ  il en train de faire le flashage avec plein de OKAY
et 
 il vient de finir avec Slot b was successfully flashed

Unlock with fastboot oem 8901_unlock

1 Like