Have you tried in Safe mode with either the power plugged in or not, or a USB connected to a PC ~ maybe ??
After a lot of tries (the time to do it being only around 10 seconds and having to wait that list of apps is available, then having to scroll to google) I succeeded disabling Google play services, Google play store (+emptying the cache), Google (+emptying the cache) but I’m still locked in this damn boot loop. Did I miss something (I precise: I can’t empty the cache of the google play services since I disable it as it is no longer present in the app list…)
Multiple attempts. Pretend it’s a game. 
3 Likes
Hey. Both “Disable” and “Force Stop” are greyed out on my phone. I tried to uninstall updates with the 3 dots in the top right but it doesn’t work (“Uninstall updates unsuccessful”). And so far I’m not fast enough (or my phone is too slow) to reach the “Clear Data” button under “Storage” before it restarts. Safe mode is even worse. Will try plugging in a cable…
1 Like
Hi,
I have a big problem with my Fairphone 3,
since yesterday, I’m not able to start the phone after some seconds it resets,
and shows me after a restart in the Recovery the option to restart or to set the phone to
factory reset.
Safe mode doesn’t fix that, I have not unlocked the phone,
and there is not enough time to enter the digits in the user menue…
What can I do to rescue the data on the phone???
Please, I need help…
I had the time to get the admin rights and to set the USB debugging,
but there are no files in the adb shell ???
only things with no permission for me …
That is the best working workaround!
I activated developer tools (and USB debugging).
Then I downgraded gms (Google mobile services) with ADB commands that’s much easier to do than the 5-10sec UI handling…
After USB debugging is enabled, U need to trust the connected computer (dialog at phone’s display), then download the fallback version (apk file) (f.e. APK Fallback version 22.02.21) and type the following commands:
adb shell am force-stop com.google.android.gms
adb shell pm clear com.google.android.gms
adb install -d com.google.android.gms_22.02.21_\(150408-428111784\)-220221039_minAPI30\(arm64-v8a,armeabi-v7a\)\(480dpi\)_apkmirror.com.apk
26 Likes
I did and finally managed to stop both Google Play and Google Services. However i now get notifications each half second to inform me that tons off things won’t work unless i turn Google Services back on. Managed to kill most notifications but can someone tell me if i need to downgrade to an older version of Google Services or is it better to just keep it off for now?
thanks, hope this works, now my phone is still on after minutes…
but was the problem??? a bad update ???
On a working phone there is a way: In settings go to Security & location > Device admin apps and disable any options that are run by “Google Play Services”, e.g. Find My Device or Screen lock service.
After that back in Apps & notifications > Google Play Services the Disableing option should no longer be greyed out.
However, on my FP3 I wasn’t able to go that way because during the 10-seconds-reboot-loop the changes made don’t seem to be saved… Too bad!
1 Like
No need, you can try, but no guarrarty it will work out fine.
Is it a good or bad sign that no updates from fairphone have been posted on this matter so far?
The miracle of the weekend 
1 Like
@Pilo11 YOU ARE A HERO!!!
Your adb tutorial helped me recover my FP3!
I had Developer Tools activated already, but not USB Debugging. But this was possible for within the 10-seconds-timespan.
After that I was able to reach out to the phone via USB and could install the earlier Google Play Services app. Excellent!!!
FP3 running now. I’ll back up everything now and then I’ll go for Lineage, I guess…
Edit: I disabled automatic updates (like @anon9989719 suggested) in Google Play Store > Settings > Network Preferences > Auto-update apps > Disable.
7 Likes
I really don’t know. The Google Play service cannot be solely responsible for this, otherwise many other smartphones from other manufacturers would also be affected. But it definitely has something to do with the update and version 22.44.16. I have a second Fairphone that still has version 22.43.xx installed, I installed 22.44.16 there and exactly the same problems occurred after a reboot.
6 Likes
@Pilo11 Thank you very much!
Your guide allowed me to downgrade Google Play Services and (so far) the phone seems to be stable again!
3 Likes
Isn’t there any way to switch off the whole possibility to reboot by itself altogether? It has no purpose (rebooting has of course, but just manually) and it makes finding solutions so painstaking!
1 Like
Framwork has to submit updates to Google. Google do over 2 million security checks and if they are sure it’s OK then Fairphone can release it.
Between Fairphone submissions to Google, google do updates without Fairphone approval so yes it is down to Google, though it may be because they missed an underlying issue in the Faiphone OS from a long time ago.
2 Likes
FP have confirmed that they’re working on this / treating it as a priority.
Beyond that, there won’t be much value to them commenting on this post (PR aside, perhaps) until they uncover the cause and have a fix. These issues can be complex to figure out; especially when the issue’s not reproducable (i.e. not all fairphones seem to be impacted at the same time; so it’s possible that they’ve not got a faulty phone to see the issue first hand on / try stuff out on… unless our theory on Google Play Services is correct and they’ve therefore been able to reproduce the conditions required for the issue to occur). If the issue’s caused by components from a third party it’s also harder for them to fix, as they can’t correct those components; so they then either need to set their code to pin the component to a version prior to the issue, or to work out a way around the issue from the outside.
I don’t know if their teams work weekends; but its likely that at least most staff (including any who’d cover comms) won’t, so I wouldn’t expect updates until Monday at the earliest… likely later if they haven’t uncovered anything worth communicating.
6 Likes
Downgrading Google Mobile Services according to your tutorial has also worked for me. Thank you so much @Pilo11
5 Likes
Thanks Pilo11: I followed your instructions and now I’ve my phone working again 
1 Like