Closed 573 closed 2 years ago
I was at least able to overcome the issue of not being able to navigate the backup location anymore using the following:
adb shell pm enable com.android.documentsui
adb shell pm install-existing com.android.documentsui
Then I was able to export the database file to any location on the still broken (unwanted reboots) phone.
The file appears named (invalid) though, I guess due to it being stored in encrypted form ?
I was at least able to overcome the issue of not being able to navigate the backup location anymore using the following:
* enabled usb-debugging on the phone * installed adb on my computer * attached phone to computer and set mtp-mode (transfer data) on phone * [this site](https://forum.fairphone.com/t/how-to-get-rid-of-the-file-manager-preinstalled-app/72319/11) got me to: * `adb shell pm enable com.android.documentsui` * `adb shell pm install-existing com.android.documentsui`
Then I was able to export the database file to any location on the still broken (unwanted reboots) phone.
The file appears named (invalid) though, I guess due to it being stored in encrypted form ?
Reopened the (invalid)-named file and confirming it worked 🚀. Just have to reassign the original password for it yet while for the times of this operation set a very short one 😆
When I export the database I am presented with Android File manager which itself is broken due to a phone error.
Thus I just can't navigate to any location for the backup file.