Hello. I have a Fairphone 2 and yesterday I tried updating from Fairphone OS 19.08.1 to Fairphone OS 19.11.2. I ended up on the Team Win Recovery Project with an “unable to find partition for path system” error.
Unfortunately I didn’t think of googling this error first, so in succession I tried the following:
Manually updating from my PC (Windows). This didn’t work as, prior to this, I’ve been having lots of issues with getting my PC to recognize my fairphone using a USB cable.
I downloaded the manual update to my SD card and tried to install from there using TWRP. I get the following error: "zip signature verification failed! Error installing zip file ‘/external_sd/fp2-gms-19.11.2-manual.zip’
At this point I successfully managed to create a backup of all my data to save to the SD card, so I tried doing a wipe (Data, Cache and Dalvik) in the hope it would do a factory reset on the phone. If the installation zip was on cache, as other topics on the forum suggest to try, it was wiped at this point.
Needless to say, this didn’t work either, and I still get the ‘Unable to find partition for path ‘/system’’ error.
Good news: I can access TWRP by pressing volume up and the power button at the same time.
The bad news are that I can’t do a manual installation from PC, as I noted on the original post. My PC simply refuses to recognize my phone, hasn’t done so for ages. I thought it was a bottom module issue for a while, but I replaced that module in July and the issue persisted.
I also can’t leave read only mode. I googled around, but it won’t let me uncheck the read-only option on Mount. I also know I didn’t install TWRP myself, so I’m not sure how to fix the read-only issue. It appears I’ve reached a stalemate - I can’t manually install from PC as my PC doesn’t recognize the device, and I can’t install from TWRP as I’m on read-only mode.
My location is Madrid, Spain. If indeed there is a #fairphoneangel around. Edit: just checked the Fairphone Angel topic and searched for Madrid. We’re out of angels in the area.
Sure, I didn’t think about telling you, I had understood even this combination didn’t work
Maybe the cable? Did you try another one?
Otherwise perhaps a problem with your fastboot? Did you try reinstalling the Android SDK Platform Tools, and trying again?
I suppose you don’t have access to another PC…
Do you mean tapping on it really just doesn’t do anything? Strange… I believe reinstalling TWRP would help, but you need a working PC for this.
Well… there was and is an angel in Madrid, but he paused the heaven, so indeed consider there isn’t any.
I tried with another cable, to the same results. I don’t have another PC available at the moment, but I will try with another PC and report back.
I have gotten in touch with Fairphone Support (if only so I could get a quote for how much the repair would cost), but it really does appear that they’re swamped with Fairphone 3 support requests. I have yet to get an answer from them.
Update: I’m on another PC, and have tried with 4 different cables.
There was a promising moment where the PC indicated an Android device had been connected to the PC, but I clicked away from that screen thinking I could now flash the Fairphone update. It was not to be, and I haven’t been able to get this new PC (and the several cables) to recognize the device again.
I downloaded the Android SDK Platform Tools, but it doesn’t list any device when I input the command fastboot devices. (It doesn’t seem that I have to do anything beyond run cmd as admin and type fastboot devices from platform-tools.)
I have no idea why my phone can’t be recognized by PCs… It’s been an ongoing issue and I ended up buying an OTG with a card reader so I could move data through the SD card. But obviously, that doesn’t work when TWRP is in read-only.
as the fastboot command does not find any devices on your system, you may also want to check these two things (if you haven’t already done so):
For the fastboot command to work, the device needs to be in “Bootloader” mode. This is the mode you described above (Fairphone logo, blue blinking LED). fastboot will not work, if you have already booted into the TeamWin Recovery. If you have booted into the recovery you can use the Menu of the Recovery-System to reboot the device into the bootloader.
I have never used fastboot on Windows , but I remember that in the past this required the user to install a special USB driver. I am not sure if this is still required, maybe some other users have experience with that. If you want to see how these installation looks for the Google devices, take a look at https://developer.android.com/studio/run/oem-usb
For me, fastboot always worked well in the past, so you might not be far off.
Hi all, I am experiencing the exact same problem. I have tried those several points that Aitziber tried without success before stumbling over this post. My phone won’t be recognized either by my laptop. I tried another PC as well. They all would run on Linux so I was wondering whether that could be the cause for the phone not getting recognized but it seems Aitziber tested on a Windows system too… (though I never even got that far to see anything recognized as Aitziber did) really stuck with this issue and my phone is out of order for 4 days now already - ever since I attempted to install the latest update. There must be a solution, it would be incredibly frustrating if an update was to essentially trash a phone.
I really feel this is the end of the rope since I tried to wipe pretty much everything, tried to install an OS by hand by putting it on a micro-sd card then copying it to the internal memory and tried installing it - but there I get the message: “zip signature verification failed”. Thanks for any hints on what to try further!
Thank you for the quick reply!! But unfortunately I had found that already in the forums… the checkboxes, both in the install menu as well as the general settings in TWRP, are unchecked. So in theory it shouldn’t perform a zip signature verification, yet that is the error message I get in TWRP. I have found that others have this problem too. I am trying to install a different TWRP version hoping that will fix the problem. If so I’ll report here of course.