I moved your post here. Please have a look at the marked solution.
The magnifying glass at the top right of the page is a search function 
.
I tried the search but was unable to find this thread ;/
I upgraded twrp and after that, I was able to upgrade opengapps too. Thanks! I’ll wait for a bit so the CPU can cool off, and see if that problem is also resolved now.
Alternatively you can connect your phone to a computer via USB, start TWRP, activate “ADB Sideload” in TWRP and then install your ZIP file by using adb sideload on the computer.
1 Like
I’ve also successfully updated OpenGApps after figuring out how to update TWRP. I’m sure these things are made as straightforward as is reasonable but since I find I only need it once or twice a year I can never remember how to do it and any notes I make are often superceded by the time I need to look. Lots of internet searching and reading again… Otherwise no problems.
I also had a very hot phone, quickly discharging, by the end of the whole updating process. But once everything was done, I rebooted and it seems to be “normal” again. Mind you, I have a 3-year-old battery which seems to be getting rather tired.
Thanks, but the abd webpage seems only to have .exe files and I am not using Windows. I am using Linux. Do you know if the solution you proposed can be implemented in Linux? I see no linux download links on the adb website.
Ok, second try …
‘For many Linux derivates you can find small packages for the ADB without the need for installing the whole SDK. For example, for most Debian distros you will find the packages “android-tools-adb” & and “android-tools-fastboot”.’
If in doubt, an internet search for the name of your Linux distribution + “adb” should help.
1 Like
Thanks for the advice. I tried enabling the Sideload from TWRP, but after a long time loading, it says it failed. The last message was “Starting ADB sideload feature”. I have adb command working on linux, but I was never able to connect to the device.
Trying:
$ adb shell
Gave me this:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
And trying
$ adb devices
Gives me:
List of devices attached
1baf6ee unauthorized
Following advice from here and I managed to get the device recognized:
adb devices
List of devices attached
1baf6ee device
I tried to activate adb sideload from twrp again but, again, it gets stuck on the “Starting ADB Sideload feature…” message until it says it failed. After it fails, the outout for adb -devices is:
adb devices
List of devices attached
1baf6ee recovery
So, it changes from “device” to “recovery”.
And I don’t seem able to use adb at all:
adb shell ls
error: exec ‘/system/bin/sh’ failed: No such file or directory
I didn’t do much with ADB Sideload up until now, but I think after this message you are supposed to just ‘adb sideload’ your ZIP from the computer side … which you didn’t … which is why it fails after some time.
Just my reasoning, could be wrong, I can’t check just now.
I think ADB Sideload doesn’t enable the whole ADB command set, that’s only available when the OS is booted.
I finally managed to sideload the opengapps zip file into the phone, but the “zip verification failed” message appeared. I tried with two different zip files that I just downloaded. I am using TWRP 3.1. I should be able to make it work, right?
I had downloaded that before, started the phone with TWRP, clicked on install and found the .img file of the 3.2 version. Everything proceeded without any error messages, but when I reboot and I start TWRP again, it still says it’s version 3.1.
I am flashing the image to recovery and not to boot. Is that OK?
Hi all,
I had the same trouble with installing opengapps after updating to the latest Fairphone Open OS (Android 7.1.), so I followed the advice above and installed the latest version of TWRP 3.2.3-0
Since then, my FP2 will boot showing only the TWRP screen, I cannot figure out how to get to the normal phone function. Any help greatly appreciated. Thanks, Yves
Sounds like you installed TWRP into the boot partition, but it needs to go into the recovery partition.
If so, here’s another case … solution in the end was to wipe the phone (deleting all data) and install from scratch …
… many thanks, yes, you are right: after installing it to the recovery partition with no effect (i do not have an additional sd card in my fp2) i installed it to boot. seems like that was a mistake 
I am trying to manually install Fairphone Open OS (https://support.fairphone.com/hc/en-us/articles/207914363), I hope this will work
… the procedure described under (https://support.fairphone.com/hc/en-us/articles/207914363) did seem to work in itself. However, my FP2 has now been trying to boot for about an hour or (Fairphone Logo on the screen, and blue circles pulsating from left to right). Surely, that can’t be it? Many thanks for any help …
Which binary image did you use?
Hi, I used the binary linked in the link below, that being [Binary image] Fairphone OS 18.04.1 (Android 6.0)
Does that clarify things? Many thanks …
You started out from Fairphone Open OS, right? If that is that case, data on your data partition may be incompatible with the Fairphone Regular OS system image (which you appear to have used). Switching between the two normally requires wiping the data partition for this reason. In your case, I’d suggest first trying whether the binary image for Fairphone Open OS (Android 6 18.04 or Android 7 18.10) does give you a booting system.
1 Like
Fantastic advice, many thanks, I used the Fairphone Open OS binary for Android 7 and now get a bootable system. Pheew … 
One bug immediately gets my attention: on pressing the power button and selecting “shut down” the phone restarts. Nevermind.
Next mission: install the latest OpenGapps. I am following the procedure described here (https://twrp.me/fairphone/fairphone2.html), with no effect: the version of TWRP stays 3.1.1.0 and is not updated to 3.2.3.
Any ideas on that would also be greatly appreciated …