OS update not working, and manual flash installation not working either

[Alessandro_Tavoni]

After updating on Tuesday (following the prompt from the updater), I get the "unable to find partition for path ‘\system’ " message and get the TWRP.
I have followed the threads and tried the manual installation, as per https://support.fairphone.com/hc/en-us/articles/207914363?flash_digest=6af4dd3e20db05f36402704baddfab402882c281#

But I get the “WARNING: No Fairphone 2 found” message always, even if I followed the steps and use a cable data.

Is my only option a TWRP factory reset? I guess that means choosing ‘wipw’ in the TWRP?
If I do that, besides losing the data, will the FP2 then boot with the functioning OS, or will I then need to do a manual installation, hoping the computer sees my phone?

Thanks for the help! I am travelling today back to Europe, so any quick feedback would be very much appreciated!

[AnotherElk]

@Alessandro_Tavoni

I have followed the threads and tried the manual installation

And have you tried to find and install the update in TWRP? …

Accidentally entered TWRP (Team Win Recovery Project) and no idea what to do

Had exactly the same issue, thanks for your solution. If someone have the same issue TWRP -> Install -> cache -> FP2 update zip file -> install

A little more detail in between …

@AnotherElk

“Install” in TWRP’s main menu, then navigate to /cache by tapping “(Up A Level)” and “cache”, and hope fp_update_gms_whatever.zip is still there to select.

---

@Alessandro_Tavoni

But I get the “WARNING: No Fairphone 2 found” message always, even if I followed the steps and use a cable data.

Please do steps 1 and 2 (ignore the other ones for now for this particular problem) in this guide here and see whether the manual installation finds your phone then …

Installing the Fairphone 2 from scratch in case of failure / Komplette Neuinstallation des Fairphone 2 im Fehlerfall

Updates could go wrong, upgrades could go wrong, own experiments could go wrong, any given thing could go wrong … and the Fairphone 2 doesn’t boot anymore, doesn’t update anymore, doesn’t do any given important thing anymore. Updates können schief gehen, Upgrades können schief gehen, eigene Experimente können schief gehen, irgendetwas anderes kann schief gehen … und das Fairphone 2 bootet nicht mehr, updatet sich nicht mehr, oder tut irgendetwas anderes wichtiges nicht mehr. If even a factory …

[Alessandro_Tavoni]

Thank you for the tips. Unfortunately neither worked. I tried to find the update in TWRP -> Install -> cache -> But there is nothing there.

And I installed the SDK platform and tried steps 1 and 2 but nothing happens (image below). Anything else left to try?

[AnotherElk]

@Alessandro_Tavoni

Anything else left to try?

If it’s not the cable, then this looks like driver trouble.
This here was done because MTP didn’t work when TWRP was booted, but it could serve as a generic driver repair …

@AnotherElk

To get MTP running again, I did the following …

• Disconnected the phone from the computer.
• In Control Panel - Programs and Features:
  Uninstalled everything with “MTP” or “ADB” in its name.
• Rebooted Windows.
• In Control Panel - Device Manager:
  Enabled View - Show hidden devices, and then uninstalled every possible ADB, MTP and smartphone device, hidden or not.
• Rebooted Windows.
• Connected the phone again with booted TWRP, Windows then needed a moment to set up MTP again automatically and prompted a success message afterwards.

Et voilà … Now the Fairphone 2 with “Internal Storage” and “Micro SD card” shows up again in Explorer as soon as TWRP is booted and the phone is connected via USB. I tried TWRP 3.2.3-0 and 3.3.1-0.

…

Turns out I deleted my working dic:adb and dic:fastboot commands with this endeavour (they were probably from Minimal ADB and Fastboot), so I did the following …

• Downloaded the current Android SDK Platform Tools, it’s better to use these anyway.
• Unzipped the ZIP file to C:\platform-tools (you can unzip it to wherever you like).
• Added this path to the Windows “PATH” environment variable, so adb and fastboot could be run from everywhere again without always having to prefix them with C:\platform-tools\ .