Rename the .ext4.win000 and .ext4.win001 files to .tar and you could then extract the content with any archive manager.
Regular FP OS doesn’t include TWRP, but the original Android recovery, which is just for flashing updates and probably, wiping the phone, nothing more. You can flash TWRP again with fastboot. I recommend using the official TWRP project itself port, which support encryption, unlike FP Open’s one.
We all agree. Fairphone has not even removed the update. We are now a month after the bug report and they haven’t done anything yet. I don’t think they care at all at this point.
As this affected your work and obligations, made you loss data, time and patience, Fairphone Open is officialy supported and under warranty, and we have pretty good legal coverage here in Europe, I suggest you to fill a Support ticket asking for responsibilities and consider taking legal actions (though a consumer’s rights defense NGO) if you lost sensible or important data.
After more than a year with a Fairphone 2, justifying Fairphone mistakes (because we know launching a startup is hard) and taking part in the community, I’m no longer a Fairphone supporter but just a merely community friend. This is just inadmissible and undefensible, and I’m not angry now but truly sad.
Unfortunately, my feelings come close to Roboe’s. Currently, I do not have too much time to play around fixing my phone and am dependent on a working phone on which I can be reached. I’m still dealing with quite a few issues (GPS, battery life, random reboots, random screen freezes…), making every day usage quite challenging. I still believe in Fairphone and love what they’re all about, but some things are highly irritating. @Douwe this is a very serious bug, how come there’s no statement or at least official acknowledgement, yet? Is something happening? And why has this update not been removed or put on hold, yet? At the very least I’d expect an official warning so others make a full backup before upgrading!
I wrote my whole failed upgrade story in the other thread (e.g. failed last attempt) and it feels like Fairphone hasn’t even noticed there’s an issue. No I did not file a support ticket, I had my hopes up that the reports on backtracker were sufficient for something to happen…
Hey @leVin42, I just saw that yeah. Somehow I missed that notification. Sorry about that. I guess ‘tagging’ me in a topic is not the best way to reach me. PM’s work better most of the time.
I understand your part (and your job, I think), but the bug report —tagged as critical— has been overlooked for a month and a half in the official bugtracker.
It highly worries me that Teemu, the only Fairphone staff that replied to the bug report, has renamed it incorrectly today, and the update hasn’t been retired.
So far we were not able to find the reason for this to break.
It seems connected the installation of some 3rd party system modifications and the team is not able to support and test for these kind of modifications.
In what sense do you think the bug was renamed incorrectly?
I have the bug and I did not install any 3rd party system modifications. I just enabled root access (for CatLog to see if I can find out why I get random reboots) and installed some regular apps (through F-Droid or apks downloaded from Google Store). I don’t have any (Open) Google Apps installed.
Clear. Thank you for explaining.
We’ve tried several times here to reproduce the bug and did not succeed, so it is difficult for us to find out what is happening.
Today we will release the July update for Open. We have not changed anything in regards to this bug (as we wouldn’t know what to change). But we’d be happy to hear if you still experience this issue when updating to 17.07.
I’ll try upgrading directly to 17.07. and if that fails I’m pretty much out of ideas, as I already tried to completely unmodify my phone. I will try to go back to the regular OS, upgrade and then install Open OS again. I just hope that it works eventually!
Thanks for your effort and constantly providing updates!
How can i completely wipe the phone and do a clean install? I thought flashing the image with fastboot would be enough but it seams the /data partition is still there?
Sorry, @Douwe, but I can’t see how marking the bug report as “Rejected” solves anything at all. Ignoring the fact that its new name doesn’t truly descript the issue.
After a month and a half, I don’t have the Open 5.1 backup anymore to try the new Open 6 update —because of the bug I switched to Lineage OS— so I’m afraid I can’t help with the bug.
I did not mantioned yet, I just needed to delete the app AdBlockPlus, I were able to do it in safe mode and the freezing and reloop found an end…
But that takes me two days in front of two Displays.
But I still got, like some others, the problem with stuttering when playing audiofiles since the update… That means in fact I can not hear music with the phone…very sad for me.
since I had some time today, I thought I’d finally try my luck with the newest Marshmallow FP Open version.
Of course (of course!) I got stuck in boot loops. Luckily I made extensive backups beforehand, but I’m a little unsure how to go on and after several hours of searching the forum, I’m giving up on finding the answer without asking…
Here’s the current situation:
I have both a Titanium Backup Pro backup and a TWRP backup
I factory reset my phone and installed 17.07, OpenGapps and Xposed via TWRP, all of which seems to have worked (I think, unsure on how to check for Xposed).
Now I’d like to get my apps and data back. I first tried to install TiBa, but while the Play Store lets me install it, I cannot open it thereafter (it doesn’t show up anywhere on the home screen or in the list of all apps, but does show up as installed in the Play Store. But when I click on Open in the Play Store, it just opens the Play Store page for TiBa, not the app. The only other option is uninstall. Un- and reinstalling it doesn’t change anything).
So then I figured I’d go the TWRP route, but am also uncertain what I should restore - all partitions (Boot, System, Cache, Data)? Or does one of these include the old Android 5.1, which I don’t actually want back and if so, which one should I uncheck?
On the off chance that someone has a better solution for how to get my apps and data back, I’m open for it. Worst case I guess I’ll go back to 5.1, but since I’ve managed to get 6 installed now, it would be nice to keep going…
