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

Help Fairphone 3
438

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