[ i would have done that for sure if the ‘updater’ would have told me that it’s an OS update, not just a regular one. (in my case it’s even worse: the phone started the update by itself via ghost touches.) sitting on a bench and keep telling that everything is fine to people passing by and struggle trough no fault of one’s own is not helping the fairphone communtiy at all. in my case it just drags me away personally…]
I apologize, that wasn’t my intention, and I understand your situation and the unfortunate part Fairphone played in it with deploying the upgrade this way.
I’m just a bit allergic to giving backups a seemingly negative touch with “(unfortunately) necessary” .
People don’t backup enough as is. And I for sure know I don’t.
actually i just wanted to encourage every lazy ass like me doing the effort to backup.
as a friend of mine, part of the international dance music scene just screwd his *book without any backup there. it’s not the first one in my surroundings. i’m just lazy with the phones man…newer the studio works.
It seems that your battery is deep discharged. Connect it with a charger and wait 30 mins.
If the LED is still flashing red, your battery is dead or your phone can’t charge it due to a damaged boot and/or system partition.
Turning on the phone with a connected charger results in reboots due to the drained battery.
Flashing the phone without inserted battery might help:
Press and hold volume down and power button, then connect the phone to your pc. The fairphone boot logo appears. Now, release both buttons.
Your phone is now in fastboot mode. If the phone still reboots, verify if both buttons were pressed while connecting the phone.
Install the previous 17.04.0 version as described in the wiki above.
Insert the battery and connect the phone to a charger (don’t turn it on). The LED will start flashing red, then flashing should stop and the battery loading animation shows up.
Your data should still be in place since the manual update package does not contain a data partition, and the flash.bat and flash.sh scripts do not contain wipe commands.
A backup shouldn’t be necessary*, but a recommended precautory measure. Android has a well-designed migration system to avoid troubles —far better from most desktop OSes, IMHO. I’m sure you say that in the best of intentions, but can be interpreted as blaming the user, which has no fault at all.
*= if you run FP Open as is, without Xposed or system-wide mods (microG and stuff)
Well, just to add my experience - quite the same as previously stated.
We have two FP2, both FPOpen and “rooted”, one with XPosed/XPrivacy one without.
When the Updater showed up “new version available” I did not imagine it would be the long awaited upgrade to Android 6 - so I did not take any precautions (backup apps / nandroid-backup).
Both phones were in a boot loop after the OTA-update. Sometimes I managed to enter the PINs, most of the time the phones did not accept any input.
Finally I decided to down- and upgrade the FPOpen as described further up. In Detail:
downloaded fp2-sibon-17.04.0-manual-userdebug.zip (Link somewhere up in this forum)
started the FP2 in Fastboot-Mode (Power-On + Vol-Down)
run the ./flash.sh in the unzipped folder
rebooted phone (Android 5.1, stuck in boot-loop, optimizing apps)
switched off by pulling out the battery
booted into Recovery (Power-On + Vol-Up)
in TWRP went to Advanced -> Sideload, on PC did adb sideload ...17.06.04...zip
rebooted
phone started normal with Android 6.0.1
My system settings were all there (including photos, SMS, contacs, call-log), but all application settings (including data) were gone.
I managed to recover the most important settings from old Titanium Backups and a nandroid-backup (I made after the first upgrade in TWRP).
The recovery of the two phones took me about 10 hrs.
I really appreciate the work the Fairphone-Team is doing, but an major upgrade has to be announced in some way - this one showed up like any other upgrade before.
And on top it seems like the bug was well-known before - this is not professional work.
I have problems taking screenshots. Seems, that it doenst depend on the app or the launcher where i try it. Everytime appears the message, that it isnt possible to make screenshots because the app or the company doesnt allow it.
I searched in the internet, but didnt find a solution.
I think it is a simple Android 6 thing, which i dont know until now.
Thank you for your attention and help.
Here you can see an “oldschool” screenshot.
Is the SD-card-writing-problem still existent on Android6? I told my cameraMX and OpenCamera to write to my SD-card. LeafPic shows me the fotos, but in the Windows-Explorer, all files have 0KB file size and I can’t open them.
Do I still have to change the platform.xml?
How do I get my pictures back???
Downgrading to 17.04.0 has not worked for me. The phone is trapped in a reboot loop - it does the “optimizing apps” thing, then it briefly flashes an error message that “unfortunately…” something, and it reboots and starts again.
I want to try upgrading back to 17.06.4, and then see if I can use TWRP to upgrade XPosed. Can someone point me to the manual-userdebug version of 17.06.4?
Get ‘adb’ (android developer bridge) on your computer. This depends on what operating system you use, but one way to do it is to install Android Studio.
Hooray! It’s back up and running! And I don’t seem to have lost any data.
This procedure actually resolves a long-running question I had. I have XPrivacy installed specifically to prevent apps slurping my address book. But the way I’ve installed updates before, the phone briefly boots without XPrivacy. I don’t know if, so I assume that, apps are briefly started in the background and do indeed slurp my address book before I have a chance to re-install Xposed.
Thanks, that did it. Indeed I had to boot directly into recovery after flashing TWRP via fastboot, otherwise it would have been overwritten by FPOOS. Now I can make backups of my encrypted data partition.
In conclusion the stock TWRP (3.0.2) has two major flaws for me:
Encrypted data partition cannot be mounted (which prevented me from flashing official TWRP directly from recovery).
Reboot and shutdown options don’t work, instead the phone freezes and has to be rebooted by holding down power for ten seconds.