Stock fp3(+) (factory reset) boot loop (workarounds in first post)

Thanks so much - I have been experiencing the same issue since last night (early hours 12/11) on a FP3 and this worked. Involved connected through ADB, clicking notification to always trust the connected computer, and then on the next reboot ran the commands before unlocking the phone. Have now disabled Google Play updates and seems to be running fine for the time being.

1 Like

@Pilo11 how have you been able to copy files before unlocking? I fiddled around with ADB / shell commands for hours and I only received messages that either the path was not found, or I did not have the rights to access those disks / data…

Thank you so much for posting this. After many difficulties, I have managed to get to step two, but I get “cmd: Failure calling service package: Broken pipe (32)” as a response. Would you or someone else know what that means and what to do?

Fingers crossed :wink:

Hmm seems like your adb server is crashed (in an unexpected state): try to execute the following commands to restart it or restart your computer.

adb kill-server
adb start-server

It is not really necessary to execute “pm clear…”, the “adb install -d” command also clears cache and data because I did not used -r (ADB Syntax examples). But I thought it’s a nice addition to understand the steps.

2 Likes

Hi !!

I also experience this issue, until 12 november around 12:30 in France…
THANKS A LOT for all the tips here !! <3
Special thanks to Pilo11 :+1:t3:, Fairy3000, amoun & Elli_Thomas

But…
First two lines of commands : success :grinning:
But at the third line of command, failure response : [INSTALL_FAILED_VERSION_DOWNGRADE] :weary:

Do someone know what I did wrong and how to get it OK ?!
Thanks !!

1 Like

Are you sure that you did not miss the “-d” in the “adb install” command?
What does the following command output (need to be called on a linux or macos system or a terminal environment on Windows which supports grep)?

adb shell dumpsys package com.google.android.gms | grep versionName

on Windows powershell perhaps this:

adb shell dumpsys package com.google.android.gms | findstr -i versionName

My output:

versionName=22.02.21 (150408-428111784)
versionName=22.02.21 (150408-428111784)

It is important to install exactly that APK version (apk link).

3 Likes

I got it.
Thank you so much for the help!

Ooooops that’s it, I missed the -d :grimacing: :woman_facepalming:t3:

Everything’s OK now, THANK YOU Pilo11 !!! :superhero:t3:

I have another Fairphone3+ with Ubuntu which is also not affected … lol :wink:
many many thanks…

1 Like

Thank you for taking the trouble to provide these detailed steps. I had no chance without your guidance.

As a first time user of the sdk manager utility, I discovered:
The apk version needed to be downloaded to the Android\Sdk\platform-tools folder so the tool could find it.
In that folder, shift and right-click allowed me to start a ‘Power shell’ window to run the commands.
Adding '.' before the adb commands cleared one reported error.
Putting the apk name in single quotes cleared the other one.

When giving permission to use USB debug, I had to remember to tick “always” before pressing “allow”. It was still quite a game getting to those options in the permitted time before each reboot.
Kudos to you and the rest of the community for getting to this answer.
Nigel.

4 Likes

You can just drag & drop the apk behind the First Part of the command.

But workaround worked like a charm!

1 Like

Thank you all! With a combination of those two hints, I was able to uninstall the Google Play Services updates pretty easily without activating USB debugging, installing SDK, and all that.

Seems to be working for the time being. Automatic updates are disabled. I hope that prevents it from happening again.

5 Likes

I had EXACTLY same issue this evening FP3, UK, EE. Nothing special happened to my phone before this occurred. It came out of the blue

Solved it with Amoun’s tips- disabled Google play (phone was NOT happy about that… cue 1000 notifications about the world ending…), stripped Google Play of its updates, then switched off auto update for all. All is good again. For now!

1 Like

and tbh, if I can do it so can anyone

1 Like

As I read, your advice has been very helpful to everyone. My FP3+ reboots within 10 seconds. I managed to activate the developer mode in that time, but I can’t manage to reach the USB debugging button as well. Is there any trick? Thanks a lot…

Did you try this way to the workaround already?

2 Likes

Good morning,

i did the downgrade Yesterday on my wifes fp3plus. It worked for a few hours. This morning the boot loop is back… :frowning:

I also disabled automatic Updates in the Play Store App. Why is the Loop Back?

1 Like

These are some compiled answers from the thread

Retrieve data

From 90386/163

  • able to copy your files from your phone to your computer without unlocking it.
  • can also do the downgrade without any risk.

Two main workarounds

How to Revert the Google Mobile Services

  1. Enable Developer mode and USB Debuggings are both doable in under 10 secs.

    1. For Dev. Mode, follow this: 90386/161
    2. For USB-Debugging pics in link from here 90386/162
    • it’s fine if the FP restarts between these steps
    • these steps can be done without the SIM
  2. downgrade GMS (Google mobile services) with ADB

    • These can be done in in multiple reboot cycles
    1. Set up
      • install ADB
      • download the fallback version APK file (version 22.02.21)
        • see link in 90386/143
      • connect FP to computer with the above program and apk file
    2. Restart the FP, and
      • trust the computer (dialog on the phone)
      • check “ALWAYS ALLOW” from this computer
    3. (Need the SIM here) Restart the FP but DO NOT UNLOCK the phone
      • it should not restart until the phone is unlocked
    4. in a terminal on the computer, run the following when the FP logo (white on black) appears
      adb shell am force-stop com.google.android.gms  && adb shell pm clear com.google.android.gms
      
    5. If possible, run this as well, otherwise restart and run this
      adb install -d  'com.google.android.gms_22.02.21_(150408-428111784)-220221039_minAPI30(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk'
      
      • version 22.43.12 (150408-483592595) may or not work
      • problem already exists with version 22.43.56.
      • 22.45.14 (150408-487603456) also crashes. -
      • 22.02.21_150408-428111784 can work
  3. Disable Google Play Store Services and stop using/opening it until the issue is fixed.

    • From 90386/189

    • disable background data usage

      1. First open Play Store app info:
        Long press “Google Play Store” icon → little (i) sign

      2. Now disable background data:
        Press “Mobile data and WiFi” → Uncheck “Background data”

    • Do not open Google Play Store until the issue is fixed by Fairphone+Google.

      • Also, Deny any prompts for Google Play updates by other apps, unless you know the issue has been fixed.

Disable Google Play Services

  1. disable Google play
  2. strip Google Play of its updates,
  3. switch off auto update for all

must be done under 10 secs???

5 Likes

Which way did you choose to downgrade the phone?

Steps to read out the GMS version

Which current GMS version is installed on the phone?

I can run the first two commands and then the FP restarts.
What then? Can i install on the next reboot?

Did i miss something? I haven’t suspended, etc. Google Play Services