I marked this as solution ,so it will be visible better at the top, without removing the other possible workarounds
Hello yvmuell,
for me this is a workaround - not a solution.
Hopefully there is a final solution comming from Google/Fairphone within the next hours!
2 Likes
Hello:
So it seems that we can reactivate the Google Play Store if we have these settings on in the app?
In my case it could explain that I didn’t encounter the problem as the settings are put that way (I always prefer to manage updates myself 
).
On my side deactivating the Google Play Store has reactivated ads and has deleted premium functions in some of the paying apps I use 
(by the way I prefer that behavior than having a boot loop!).
Thanks in advance and I hope that the root cause will be fixed very soon.
It will be interesting to have a feedback post-mortem on this issue.
A special thought to users that don’t use the forum and are “basic users”…
Thats clearly stated in the post that it is a workaround, still its the current solution till a permanent fix
1 Like
Dear skilled forum members, thx to your help I managed to workaround and have used my FP now for 2 days -with fingers crossed. Impossible for me to try USB and other geek hard programming stuff, really too complicate for me, so I’m very happy that so far it seems to work without that. I did not disable GPStore because at the beginning of this story I happened to try the factory reset (before it was made clear here that it is useless). So I have to reinstall my app one at a time and carefully. (But I deactivated the auto-updates like mentioned in FP suggestions).
So big thanks to our helpful angels and others sharing their experience, which I follow daily since last week.
Well sorry for this long and maybe uninteresting but grateful intro, but actually I do have a question: As far as anybody knows, are only FP3 (and I think I saw one FP2) concerned by the bug?
Because I recently convinced my 80-yo mum to by a Fairphone, so she has been now for a few weeks the proud owner of a brand new FP4, as her first smartphone ever, and I really fear the moment where she call me to fix such an issue (I leave in a different country).
What do you think, should I try some preventive action?
3 Likes
I know how you feel. I needed approx. 10 times to do it. You can do it, too!
By sheer coincidence, I can shed some light on this problem: it’s related to the FP3-REL-8901.4.A.0017.3-gms-15368f27 and FP3-REL-8901.4.A.0016.6 -gms-f0c20986-user-fastbootimage.zip updates.
Since I have a rooted device, I need to manually update my FP3. Well, I forgot this for a while, and only today remembered that I should do it.
Well, guess what: After installing the 0017.3 update, I couldn’t load into android anymore, just like all of you. Then, I used the version prior to that, FP3-REL-8901.4.A.0016.6 -gms-f0c20986-user-fastbootimage.zip, and the problem still persisted.
Then, I reverted to the version that was last installed on my phone,FP3-REL-8901.4.A.0013.4-gms-c1b5afb7-user-fastbootimage, and guess what - it works again.
4 Likes
Sorry, I’ve only installed 69 Apps but it is not possible within 10 seconds to press more then the three dots within the Google Play Services … and I think, the deinstallation sould also run within the given 10 secs.
But I think if Fairphone knows already what’s the problem it should be solved in a short time together with Google.
Hi. I can happily concur with @Pilo11 . After downgrading Google Play Services and disabling Google Play Store, my phone has also been stable for 2 days. The workaround seems to work so far…
I found myself wondering why the 3 other non-Fairphone Android phones in our household were not affected by the boot loop, so I checked and they are all on version 22.43.12 of Google Play Services. The boot looping on my FP started when Google Play Services was updated to 22.44.16… So maybe the update got pushed to Fairphones too soon? Don’t know, but wanted to share this observation.
Thanks again to everybody in the forum who contributed to this workaround!
As you mention FP3-REL-…-versions, is this a clear answer to the question whether or not only FP3 devices are effected and FP4 nor FP2 are not?
Maybe someone else can answer that?
so far I havent seen any report for the FP4 or FP2, you might want to search the forum So currently it seems to be an isolated FP3 issue, for whatever reason
1 Like
Unfortunately, I abstained from the forum a few days and noticed that thread not until today morning. Fortunately, the faulty update was not installed on my FP3+ yet. So I instantly disabled Wi-Fi, disabled the Google Play Store and enabled USB debugging and told my mother to do that also on her FP3.
3 Likes
Hi all,
one question,
I disabled google play services, cleared the cache, deleted all the updates and made the two changes in the settings in the play store so there won’t be any updates for now.
Can I re - enable google play services (and stop the endless notifications)?
Thanks, Thomas
A (nearly off topic) question: I didn’t yet look at my ‘productive’ FP3 but fiddled around with adb and my FP2.
A dumpsys package com.google.android.gms|grep versionName gives two different entries:
versionName=22.26.15 (100300-461192076)
versionName=21.02.14 (120308-352619232)
Do you know what that versions stand for? I also dumped the whole output to a text file for better reading and searching, but I coundn’t explain what I saw. There is a “normal” package entry and a hidden system package.
As I know the first version is the currently installed version, the second ist oldest fallback version which is available on the phone by uninstalling all updates in the App Info menu. If you uninstall all updates U will get exactly this fallback version and both versions are going to be equal when you execute the command afterwards.
Yes you can enable the Google Play Services. BUT you need to DISABLE the Google Play Store before you do that 
2 Likes
I checked on my FP3 and the Google play services is on version 22.43.12 and no problem so you probably found the source.
1 Like
Place it between ’ ', skip the / before every ( or )
Thanks so much for the tips and hints. Not a great techi but managed to do it only to find my phone gone again this morning. I hadn’t uninstalled automatic up dates! Duh.
A few extra hints for non-techi wizkids:
- You need to hold down : Command when you drag the platform tools folder into your Terminal to make it work
- add ./ before the adb codes
- Add each line individually as they are all independent commands
Those were my few sticking points and then it worked. Thanks again so much to @Pilo11 , couldn’t have done it otherwise.
Let’s hope they sort the update out fast for those who are completely stuck!
1 Like
Thank you very much. It wasn’t easy to do it within 20 seconds, but now it works.
1 Like