🇬🇧 🇫🇷 No FP OS on updater app for back to Android

C’est ce que j’ai fait mais il dit qu’il connait pas la commande ‘adb’

Edit : Du coup j’ai passé la partie de test et je suis arrivé jusqu’au moment ou je doit taper adb sideload FP2-gms76-1.13.0-ota_from_open.zip. Sauf qu’il connait pas adb du coup

1 Like

Okay, j’ai essayé en installant “Minimal ADB and Fastboot”. Maintenant il reconnait la commande mais il dit ça :
loading : 'sideload FP2-gms76-1.13.0-ota_from_open.zip'
* cannot read : 'sideload FP2-gms76-1.13.0-ota_from_open.zip'

Est-ce qu’ADB reconnaît ton téléphone si tu tapes adb devices ? Si oui, c’est juste que j’ai oublié de spécifier (honte à moi) qu’il faut te déplacer jusqu’au répertoire où tu as téléchargé le dossier ZIP pour revenir à Fairphone OS (avec GMS) avant de taper adb sideload FP2-gms76-1.13.0-ota_from_open.zip.

Si c’est dans le répertoire Téléchargements, il faut te déplacer jusqu’à lui avec la commande cd. Elle fonctionne ainsi : admetttons que tu te situes dans C:\\ et que tu veux aller dans 'Mes Documents'. C’est mieux de tout d’abord vérifier que 'Mes Documents' se situe bien dans C:\\ (toujours dans cmd) :

  • Tape dir pour afficher la liste des dossiers qui se trouvent dans C:\\

Vu que le terminal est un programme qui s’affiche en plus de ton interface graphique, tu peux ouvrir l’explorateur de fichiers en parallèle pour savoir où tu veux aller. Pour changer de répertoire et naviguer dans tes dossier avec le terminal, tu dois taper la commande cd. Pour aller dans Mes Documents depuis C:\\, tu tapes la commande suivante (en admettant que Mes Documents est bien un des sous-dossiers [et pas un sous-sous dossier] de C:\\) :

  • cd 'Mes Documents'

Il te faut mettre le nom du dossier Mes Documents entre guillemets (simples ou doubles) pour que le terminal interprète cela comme une suite de caractères et pas deux noms de dossiers ou de fichiers différents. Pour retourner en arrière, tu tapes :

  • cd..

Pour aller plus loin que juste un dossier après C:\\, tu tapes :

  • cd mon_dossier\mon_sous_dossier\, etc.

Référence des commandes Windows : https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ntcmds.mspx?mfr=true
Instructions pour la commande cd (en anglais) : http://www.pcstats.com/articleview.cfm?articleid=1723&page=3
Un petit manuel très pratique (semble-t-il), en anglais : http://www.pcstats.com/articleview.cfm?articleID=1723
Une correspondance avec les commandes UNIX/Linux : https://doc.ubuntu-fr.org/tutoriel/console_commandes_de_base

A mon avis, pour les commandes Windows, c’est mieux te de référer à @Stefan que moi, parce que je suis sous Linux et je ne peux que deviner. Ou alors, de faire quelques recherches en ligne !
@Stefan : I’m sorry if I’m bothering you, but I think it’s better for @Corentin and @Conatus to ask you for Windows commands, because I’m not a Windows user and expert at all…

Unfortunately I don’t understand French very well / it’s very hard for me to understand what you were talking about above. Besides, I’m not the author of the ADB-Windows-driver-wiki, I just created the post. The author is @josuttis. :slight_smile:

Also, you could simply apply the FP2-gms76-1.13.0-ota_from_open.zip in TWRP (see #dic:recoverymode for instructions how to get there) if I’m not mistaken. :wink:


Our problem - with @Conatus - is the cmd doesn’t unterstand the command adb sideload FP2-gms76-1.13.0-ota_from_open.zip.

He say that :

loading : 'sideload FP2-gms76-1.13.0-ota_from_open.zip'
* cannot read : 'sideload FP2-gms76-1.13.0-ota_from_open.zip'

Do you know what it could be ?

Oh sorry, my bad… :pensive: @Corentin and @Conatus are trying to return to FP OS with GMS. They did try with method 1, but it didn’t work. So I told them to try method 2 ! But for Windows commands, I have to guess or the make researches, as I don’t know the Windows Command Prompt at all (I am on Linux).

As you seem to be a Windows user and to know cmd, I thought you could help them to navigate through the files with this tool.

@Corentin : you need to navigate to the folder in which the ZIP file is located, for example “Downloads”, and then type the command. Did you download the drivers for your Windows installation ? There you see that you’ve got two links to follow depending on your installation : https://forum.fairphone.com/t/pencil2-adb-on-the-fairphone-2-windows-driver/11529/15

1 Like

No problem! :slight_smile:

Wouldn’t TWRP be able to apply the update?

Normally yes, because I used it for Lineage OS :slight_smile: But I’m not really sure, as there is “ota” in the filename… Nevertheless, it is a ZIP file and it should work with TWRP. I’m doubting too much :wink:

I think that OTA simply means that you don’t get separate *.img files, but a ready to flash *.zip.

Oddly enough, the official guide recommends this method. I’m not sure whether it does a wipe of user data, which would mean you’d need an SD card or this sideload approach.

Edit: I read over the big red warning box (see below) - data is wiped, which would take out the update file that you’re trying to apply, unless you have it on a SD-card. As not everybody will have one, sideload is recommended.

:warning: Warning:
If you switch to Fairphone OS, all your data (including apps, messages and pictures) will be erased. Make sure to backup first!

Are you sure the word sideload is actually in the error messages?
If the word sideload isn’t in the error, then adb is just saying it doesn’t know the file you’re pointing to. Two ways to fix it: copy it (FP2-gms76-1.13.0-ota_from_open.zip) into the folder where you’re running adb (probably the easiest option), or modify the command to have the full path for the file name (for example adb sideload 'C:\Downloads\FP2-gms76-1.13.0-ota_from_open.zip')

For the console to find a programme, it needs to be installed and in a place where the console knows to check for programmes. The console will always check the folder in which you are currently working, so it is perhaps easiest to:

  • navigate to the folder where you installed adb
  • copy FP2-gms76-1.13.0-ota_from_open.zip into the folder
  • hold shift and right click on some empty space in the window (not on a file), select open terminal here (or your language equivalent).
  • continue as before
1 Like

I don’t think you need the full Android SDK. I’m not familiar with the universal adb driver, so it may install adb somewhere, but based on this topic (step 2), it doesn’t. The guide in that topic recommends minimal adb.

I do think that the file gets cached by TWRP if you try to install it. I expect TWRP to be smarter than erasing a file that it is supposed to install.

@conatus Note that adb devices says “unauthorized”. You need to unlock your phone.

Probably this helps:

You may need to start the phone normally (so not in TWRP) and authorise access from there (and then restart into TWRP to continue).

I’d hope so. I’m still wondering whether a manual download of the ota file, and then opening that with the updater app wouldn’t also work. Presumably the way the updater works (and TWRP should as well) is to copy the update file into the cache partition.

1 Like

It’s running now ! Thank you so much !

But now, something is wrong. It start, with the Fairphone and the Android logos, next it make the animation with the “start a mouvement”, next again it say “Loading” and next it optimise apps. But now ti’s blocked here …

And I try to wipe factory settings / data but it do the same. Now I’m just waiting if it can unblock of “Loading”.

That can take up to half an hour (30 mins). Just leave it there. (Google Apps need a lot of optimizing because they invade your system very deeply.)

Now, it’s blocking on “Android is starting … starting apps.”

If it doesn’t fix itself, see if there are options in recovery mode to wipe Dalvik cache and normal cache, then reboot. Or perform a factory reset.
I’m not as familiar with the FP2 side as I am with the computer side of working with adb etc, so I’m not sure whether there are any other tricks.

I tried it. And it’s the same again.

Does it reboot itself, or does it just stay on the screen forever?

It just stay on “starting apps”