A post was merged into an existing topic: [Bug] 
Upgrade to FP Open 17.06.4 renders phone useless (freezes once booted and reboots itself)
My FP2 is rebooting too many times a day, often if I use it again after a few hours, switching on wlan or using the Gallery App from F-Droid. I can’t determine a system when it hangs up, and of course their is no error message. After the enforced reboot everything is working fine for a while.
Is it possible, that I made a mistake during my installation of 17.06.4?
Before I installed 17.06.4 I deinstalled XPrivacy. But I neither deinstalled Xposed nore Xposed Installer. Now their is a red message in Xposed Installer, telling me to install a newer version of Xposed, and the download of XPrivacy doesn’t work. I don’t know how to install a new version because my FP2 is encrypted and read that TWRP can’t handle this. I also can’t find a description how to deinstall Xposed on an encrypted phone.
Can anybody tell me
- if my problem will probably be solved if I uninstalled Xposed or which reasons come into consideration? (May be a hardware problem with the on/off-button? I’ve got the new slim case.)
- how I can uninstall Xposed on an encrypted phone? (Do I have to unencrypt it first?)
- how I can update Xposed on an encrypted phone?
afaik you must re-flash (with twrp) xposed framework (use the version matching your new android version if it is a new one) after flashing an update.
I dont know if some remains of an old xposed framework could break your system, but I don’t think so.
What’s encrypted is your data partition, not the system, so you should be able to flash in twrp.
Yesss!! Finally!! I managed to install 17.06.4 (OOS) directly over Android 5.
After using the updater app first which ended up in a bootloop, I did a factory reset in TWRP and installed from SD. Now everything works smooth.
The best news: my battery life is back to normal (around 28h with normal everyday usage vs 10h in Android 5) 
One question though: Since the update I don’t see the option “mount SD card” in the USB menu (when connecting to computer) anymore. Is this normal? Would be very disappointing if this feature would have been removed. And if yes, is there a Xposed module to fix that?
Cheers!
I want to follow your advice. May be you can give me an advice for one more obstacle: I’ve activated this SD card as internal storage feature. How can I copy the xposed-zip to a folder that I can reach with twrp?
you could install in TWRP when connected to your computer using adb commands
(adb install filename.zip) when the file is on your PC
You meant adb sideload <filename.zip>, and TWRP must be in Sideload mode, 
1 Like
Thank you, yes, got that mixed up with sideloading on my FireTv, there you use ‘adb install’"
Hello,
do you still got the Problem of the audio stuttering?
I have it a lot after the update and tried different audio player but they all stutter from time to time.
I thought about if it has something to do with the sd card, because it seems that there were a lot of changing since the update…
I didnt test to play files from the internal storage yet.
Ofcourse I would be happy to hear a solution… 
I can confirm the problem reoccurs after the last update.
I upgraded it, and lost all my contacts, half of the apps were removed and a few doesnt work anymore. i tried to install telegram with aptoide, doesnt work, with yalp store, doesnt work, downloaded the apk file, doesnt work.
it is just asking, do you want to install it? yes, then it says, couldnt install.
could anyone help me?
In TWRP (3.0.2-0) under Advanced I tried to activate ADB Sideload with following errors:
Updating partition details..
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux...
Unable o mount /data/media/TWRP/.twrps
MTP Enabled
Starting ADB sideoad
and nothing happens. And of course adb sideload xposed...zip leads to error: device not found.
The “/data” thingies are not spilled when Sideload option is enabled, but on TWRP boot. That means your data partition is encrypted and TWRP can’t mount it without the password, obviously. It doesn’t have anything to be with Sideload.
The rest means ADB sideload has been enabled fine on the device, so your problem seems to be with your machine. I bet huge amounts of money* that adb devices doesn’t list any device on your computer.
Which OS are you running and how did you install adb?
*= money which I don’t have, 
1 Like
That means your data partition is encrypted and TWRP can’t mount it without the password, obviously. It doesn’t have anything to be with Sideload.
Yes, exactly! That’s my problem (described above): How can I update Xposed on my encrypted phone?
The rest means ADB sideload has been enabled fine on the device, so your problem seems to be with your machine. I bet huge amounts of money* that adb devices doesn’t list any device on your computer. Which OS are you running and how did you install adb?
You won your (not existent) money: adb only lists my phone when I started FP Open, not in TWRP. I’m using Linux Mint with android-tools-adb for a long time, so I think that the problem is the encryption and not my computer.
Do I have to decrypt my data or is their a smoother way to update Xposed?
why not try newest TWRP?
I don’t know if it helps, but you might give it a shot.
2 Likes
If you have a SD Card, you can copy the xopsed framework there and install it from TWRP.
Yet, I would strongly recommend to flash the official TWRP port @Bergziege linked. This will give you ADB access in TWRP plus you can mount an encrypted /data partition.
1 Like
Thanks @AnotherElk for your hint.
I don’t know about any app on my phone causing a screen overlay error and I never saw the error message about that. I checked your links but I don’t use the mentioned apps.
The bug occurs at least quite often. I found a new work-around:
when the call comes in and I can’t drag the answering symbol I turn off the screen by pressing the power button and press it again so the screen turns on again: now I can drag the symbol to receive my call.
But that can’t be the solution. The hotline told me to check the drawing test (Maintenance/Checkup) but the display is completely responsive. And they told me that a complete reset (edit:) MIGHT help.
Anybody else with the same problem?
I didn’t find that issue in the bug-tracker. Does anybody know if that problem also occurs in default FP-OS?
There is an update to Fairphone Open 17.07.6 read here.
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.