I am not good with the tech but this instruction was pretty easy to follow. It all worked until the last command to install the new software version.
I tried with different iteration of the link from you, @Pilo11 and even copied the whole name of downloaded file and always the same message:
adb: failed to stat com.google.android.gms_22.02.21_(150408-428111784)-220221039_minAPI30(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk: No such file or directory
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…
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.
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.
Which operating system do you use (e.g. Windows, Mac, Linux, etc)?
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)).
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.
@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 !
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!