I guess because ADB and fastboot get distributed together they often get lumped together as simply ADB.
When we get into detail, the two are seperate entities working with different modes of the phone, and referring to fastboot as ADB then leads to confusion in troubleshooting.
I think we should assume fastboot doesn’t find the device.
Hello
Waiting for any device,… unauthorized,… I also had the messages/ errors and was also stuck in fastboot mode. Just wanted to “try” to explain how I solved it.
Good luck
Es ist ja bereits bekannt dass einige Apps nicht laufen. Osmand, Aegis, etc… Das ist auf die geringe jvm heapsize zurück zu führen.
Ein issue ist in Git eingekippt, bekannt und bereits gelöst. Kommt mit dem nächsten Update.
Workaround für die, die nicht zum Update warten können: im /e/ Forum eben berichtet und von mir bereits getestet. Funktioniert. Danach läuft Osmand, davor nicht.
Maybe @urs_lesse found at least a solution for some the tests. The Fairphone Checkup App (Originally for the FP2) fork available on F-Droid seem to work on other phones as well
In vanilla FPOS it’s called MMITest. It should show up under Settings → Apps if Show System is active (or check it with adb shell pm list packages mmi).
If it’s there you can trigger it with
$ adb shell am start-activity -n com.android.mmi/.MMITestMain
Edit: I checked the /e/ images, it’s not included.
I had same problem. I tried with diffferent cables, with no luck. I also try to force reinstall of the driver from the devices manager. No luck either.
I finally solved the problem with a simple “windows update”. But I had to go in “the optionnal updates” part. There I found updates waiting for Android.
Yep, that’s the most frequent issue on Windows
You have to install ADB & fastboot drivers in the Windows Update section “Optional updates”
I remember they detailed the procedure for FP3 afaik, but nothing for the FP4
For the last one, you can check only the ones that are related with ADB (Android Debug Bridge) and fastboot
However, I advise you to do all the updates, these are frequently drivers updates
All the given apps that are not up-to-date (that’s a /e/OS classic, but fortunately we can have them on F-droid, and uninstall the stock ones with root and Package Manager)
Discord is crashing VERY often, but still usable if you have the courage to force-close it every 5-10 minutes x) - No solution found
Aegis is literally not working, after the setup it crashes, and when re-opened it restarts the setup, and re-crash…
An alternative solution is andOTP (with no biometrics support ), but you have to:
export your 2FA codes in a plain text file (not Aegis .json file) before going to /e/OS (not very secure)
or have Aegis (and your 2FA codes) on another device and just scan all the QR codes with andOTP on your /e/OS FP4
(for any help, feel free to ask me )
Apart that, everything seems to work well for me, with Lawnchair 2 (got it from Aurora store, cause the stock launcher is horrible) and Magisk root (I’ll make a wiki on how to do it in a few days )
I’ve got everything in place now, but got stuck with the backup options. Found this thread stating that TWRP misses user data and this wiki and now I’m confused and would appreciate a hint into the right direction.
I can live with backing up my files manually, but would like to back up system settings and app settings to recover my FP4 to the state it is right now.
Is adb the way to go?