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

Hello:

Just to check before I reactivate Play Store updates: when did the issue appear on your side? :innocent:

Thanks in advance for your answer!

the same would happen again eventually, but initially the new battery would have power right? I just need it to work for long enough to try following these instructions or doing a factory reset, then presumably it will charge again?

I know someone with a fairphone but they live on the other end of the country…

1 Like

This solution
adb shell
pm uninstall -k --user 0 com.qualcomm.location

published by Yasen_Tomov works for me!

The only question is now, do I need to reeinstall the package later?

3 Likes

Just to check - when you try to turn it on, do you press and hold the power button for a few seconds? Turning it on needs more than a tap of the button; holding it down for 2-3 seconds seems to do the trick.

A̶l̶s̶o̶,̶ ̶i̶f̶ ̶y̶o̶u̶r̶ ̶p̶h̶o̶n̶e̶’̶s̶ ̶p̶l̶u̶g̶g̶e̶d̶ ̶i̶n̶t̶o̶ ̶t̶h̶e̶ ̶c̶h̶a̶r̶g̶e̶r̶,̶ ̶e̶v̶e̶n̶ ̶i̶f̶ ̶t̶h̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶’̶s̶ ̶f̶l̶a̶t̶,̶ ̶y̶o̶u̶ ̶s̶h̶o̶u̶l̶d̶ ̶s̶t̶i̶l̶l̶ ̶b̶e̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶t̶u̶r̶n̶ ̶i̶t̶ ̶o̶n̶ ̶a̶s̶ ̶t̶h̶e̶ ̶p̶o̶w̶e̶r̶ ̶c̶a̶n̶ ̶c̶o̶m̶e̶ ̶t̶h̶r̶o̶u̶g̶h̶ ̶t̶h̶e̶ ̶c̶a̶b̶l̶e̶ ̶(̶s̶o̶m̶e̶t̶i̶m̶e̶s̶ ̶y̶o̶u̶ ̶c̶a̶n̶ ̶r̶e̶m̶o̶v̶e̶ ̶t̶h̶e̶ ̶b̶a̶t̶t̶e̶r̶y̶ ̶a̶n̶d̶ ̶r̶u̶n̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶j̶u̶s̶t̶ ̶o̶f̶f̶ ̶t̶h̶e̶ ̶c̶a̶b̶l̶e̶ ̶/̶ ̶t̶h̶a̶t̶ ̶w̶o̶r̶k̶s̶ ̶b̶e̶t̶t̶e̶r̶ ̶a̶s̶ ̶s̶o̶m̶e̶ ̶p̶h̶o̶n̶e̶s̶ ̶w̶i̶l̶l̶ ̶a̶u̶t̶o̶-̶s̶h̶u̶t̶d̶o̶w̶n̶ ̶i̶f̶ ̶o̶n̶ ̶l̶o̶w̶ ̶b̶a̶t̶t̶e̶r̶y̶,̶ ̶e̶v̶e̶n̶ ̶i̶f̶ ̶c̶h̶a̶r̶g̶i̶n̶g̶…̶ ̶I̶ ̶c̶a̶n̶’̶t̶ ̶r̶e̶c̶a̶l̶l̶ ̶t̶h̶e̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶s̶ ̶o̶f̶ ̶h̶o̶w̶ ̶F̶P̶ ̶h̶a̶n̶d̶l̶e̶s̶ ̶t̶h̶i̶s̶.̶)̶ (redacted per yvmuel’s comment)

One other thing to check is your charge cable’s OK - i.e. if you have another USB-C powered device plug that into your charger to check it receives a charge - sometimes a cable gets twisted, which breaks the metal wiring resulting in temporarmental connections.

Hope some of those ideas help.

2 Likes

No when the battery is really completely empty the phone will not start when plugged in.

Also this does not work with the FP3

@Ellen_Lees it seems you are hit by different issues, for the charging issue I think its better to follow up in one of the many topics around this
https://forum.fairphone.com/search?context=topic&context_id=90386&q=FP3%20not%20charging%20order%3Alatest&skip_context=true

4 Likes

Which operating system do you use (e.g. Windows, Mac, Linux, etc)?

  1. When putting the filename you need to provide the full path to that file. If the file’s in the same directory as you’re console session then just the filename is sufficient (as paths are relative). e.g. Say you’re on Windows and the APK file’s in your user account’s download folder you can change your console’s working directory to be that folder by running pushd %userprofile%\downloads (if using cmd) or pushd "$($env:userprofile)\downloads" (if using PowerShell); then reference the file by name; or you can use the absolute path (e.g. adb install -d "com.google.android.gms_22.02.21_(150408-428111784)-220221039_minAPI30(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk" (cmd) / .\adb install -d "$($env:userprofile)\downloads\com.google.android.gms_22.02.21_(150408-428111784)-220221039_minAPI30(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk" (PowerShell)).

  2. Somtimes character escaping can be an issue. That is; the system needs to know which letters are part of a command vs which are part of a filename, as some characters have a special meaning. On Windows you can resolve this with the above filename by putting the name in double quotes. On other systems you may have to “escape” some of the chararacters (e.g. by putting another character, such as a backslash before them); this can be seen in Pilo11’s original post where he’s escaped the brackets; i.e. adb install -d com.google.android.gms_22.02.21_\(150408-428111784\)-220221039_minAPI30\(arm64-v8a,armeabi-v7a\)\(480dpi\)_apkmirror.com.apk.

Note also: where you can run adb on may follow the same rules (this depends on other factors, like if the path with the adb executable file in is in a special directory)… For simplicity it’s probably simplest to put the downloaded apk file into the same directory as your adb executable and use that folder as your working directory.

Hope that’s some help.

1 Like

@malwes : the last command is to tell adb to install the APK package on your phone.

The com.google.something_apkmirror.com.apk in the command is actually a file path.

For the adb command to work on my Fedora GNU/Linux I needed to execute it in the folder where the apk file was stored, for example I typed cd ~/Downloads/ to move my terminal in the Downloads folder in my home.

I suppose it works the same on Windows. I have no Windows accessible to test but you might try to type something like chdir C:\Users\yourWindowsUserName\Downloads (or maybe just chdir Downloads) if your file is located inside the default Downloads folder for example, and then executing the adb command from here should work.

Hope that helps, you clearly have done the most difficult !

Edit : the previous answer by @JohnLBevan is probably more accurate than mine :sweat_smile:.

1 Like

Haha, thanks - maybe more accurate for Windows, but definitely you’re best for Linux :wink:

1 Like

Thanks both - charging cable is fine, and I’ve tried holding the button down. Looks like the battery is just completely flat, which presumably has happened because of the reboot loop thing, given that it has never had this issue before. I’ll look elsewhere for solutions for charging the battery again!

1 Like

I found some more advice here: Dictionary Entry: Kickstart - hope that helps.

OK when plugged in do you get a red LED?

Jetzt, da ich es endlich geschafft habe, so weit zu kommen, erhalte ich die Nachricht “Deinstallation von Google Play-Dienste fehlgeschlagen” und es fängt wieder von vorne an. Woran kann das liegen?

Solution 3 worked like a charm and was quick to implement. Thanks!

1 Like

Haben Sie “Find My Device” / “Finde mein Handy” aktiviert? Sie müssen diese Funktion deaktivieren, bevor Sie Google Play-Dienste deinstallieren können.

1 Like

Tout d’abord, un grand merci pour cette aide précieuse !

Personnellement, je suis encore bloqué : après avoir activé le débogade USB (partie 1), et téléchargé ADB, je n’arrive pas à valider la commande “cd FolderLocation” : le message que je reçois est alors “Le chemin d’accès spécifié est introuvable.”

Quelqu’un aurait-il une explication ?
Merci d’avance,

L’union fait la force…alors que dire de la solidarité !

Mathieu

Quel système d’exploitation utilisez-vous (par exemple, Windows, MacOS, Linux, etc.) ?

Remarque : lorsque vous tapez cd FolderLocation, vous ne devez pas taper FolderLocation mais plutôt le chemin dans lequel votre fichier adb.exe peut être trouvé ; par exemple. cd %UserProfile%\Downloads

Genau soweit bin ich auch gekommen …
Ich kann dir nur empfehlen die Lösung von Yasen_Tomov zu nutzen.

Ich hatte das gleiche Problem und bin nur mit der Lösung (leider nur über adb) zum Erfolg gekommen.

I can confirm that Solution 3 as proposed by @Yasen_Tomov has worked in my case. Thank you for the support.

1 Like

Oui, il faut bouger le dossier en gardant la touche Command appuyee. Sinon ca ne marche pas!

Correction : although in the first days it worked fine I now have the same issue again, therefore it is not the Smart Launcher that causes the problem