First of all there are some prerequisites. I’ll describe a way assuming you have a windows PC/laptop to do the steps.
First of all you need to install some drivers and tools. The easiest way is to install the “15s ADB installer and driver” from https://forum.xda-developers.com/showthread.php?t=2588979
Then the developer options on the phone must be enabled. In the developer options then “USB debugging” and root access for ADB need to be enabled.
After those prerequisites are done, the actual steps are the following
- connect the FP2 via USB cable to the PC
- on the phone enable USB data transfer mode (MTP) instead of “charge only”
- that should prompt you to confirm that you want to allow access from the PC
- mark the check box to remember the decision and tap OK
- on the PC, open a command prompt
- in the command prompt type
adb root
and once that completes without erroradb logcat > logcat.txt
- this will log things that happen on the phone to a file on your PC
- now shut down the phone (without torch)
- in your case you expect this to reboot instead of actually shutting down
- at some point the command prompt will lose connection to the phone and stop saving the log to file
- after the phone is rebooted, unlock it and enable data transfer mode again
- in the command prompt, type the following commands one after the other
adb root
adb shell dmesg > dmesg.txt
adb pull /proc/last_kmsg
- now you can disable the USB debugging in the developer options of the phone again
That should give you three files: logcat.txt
, dmesg.txt
and last_kmsg
. Those might help finding out the root cause.
But just to make sure: I’m no Android developer, so I won’t be able to find and fix the problem myself. It might be necessary to create a new entry in the Fairphone bug tracker and hope they find the cause.