Ubports Recovery unintended system.img flashing
-
@advocatux Yes, I see them in adb. Do you know if I only need to copy the "data" folder in order to save all data such as sms, dekko2 settings, signal data, photos...
-
@karstong I prefer to save the whole /home because is easier to cherry-pick whatever I need later to reinstall it.
You should save at least
.local/share/evolution/and the content in the main folders (Documents, Downloads, Music, Pictures, and Videos) but, again, is better to save /home than need something later that is already lost.Edit to add
.local/share/history-service/history.sqliteto save the sms -
@advocatux There actually is no home directory. What I see is the following:
~ # ls
cache init.rc
charger init.wcnss.wifi.sh
data init_bt.sh
default.prop mnt
dev proc
etc res
file_contexts root
fstab.qcom sbin
init sdcard
init.class_main.sh sideload
init.mdm.sh storage
init.qcom.class_core.sh sys
init.qcom.early_boot.sh system
init.qcom.factory.sh tmp
init.qcom.modem_links.sh twrp.fstab
init.qcom.ssr.sh ueventd.qcom.rc
init.qcom.syspart_fixup.sh ueventd.rc
init.qcom.usb.shThe documents, downloads etc. is in data/user-data/phablet...
I do not find: .local/share/evolution
-
@karstong When I try to copy a folder an error occurs "skipping special file 'SingletonSocket' and it dos not continue or do something else...
-
@karstong the /home for "your" user is
/home/phablet/To list the hidden files (those starting with a dot) too you need the command
ls -laor if you're using the filemanager, unlock it, and click "show hidden files". -
@karstong you can delete that file (SingletonSocket) and try again.
-
@advocatux I don't find this file. Maybe it is hidden. Obviously I can copy any file but not directories. Do you have an idea?
-
@karstong do you have UTmedia installed? then is probably in
.local/share/utmedia.nfsprodriver/UTmedia/SingletonSocket -
@advocatux ./local/share does not exist
-
@karstong how are you trying to find it?
-
@advocatux With "ls -la" I get the following screen print:
~ # ls -la
drwxr-xr-x 17 root root 0 Jan 1 00:56 .
drwxr-xr-x 17 root root 0 Jan 1 00:56 ..
drwxrwx--- 4 system cache 4096 Jan 12 1970 cache
lrwxrwxrwx 1 root root 13 Jan 1 00:00 charger -> /sbin/healthd
drwxrwx--x 36 system system 4096 Jan 2 1970 data
-rw-r--r-- 1 root root 5822 Jan 1 00:00 default.prop
drwxr-xr-x 12 root root 15480 Jan 1 00:56 dev
drwxr-xr-x 3 root root 0 Jan 1 00:56 etc
-rw-r--r-- 1 root root 10882 Jan 1 00:00 file_contexts
-rw-r----- 1 root root 1204 Jan 1 00:00 fstab.qcom
-rwxr-x--- 1 root root 422804 Jan 1 00:00 init
-rwxr-x--- 1 root root 2696 Jan 1 00:00 init.class_main.sh
-rwxr-x--- 1 root root 1702 Jan 1 00:00 init.mdm.sh
-rwxr-x--- 1 root root 7064 Jan 1 00:00 init.qcom.class_core.sh
-rwxr-x--- 1 root root 6734 Jan 1 00:00 init.qcom.early_boot.sh
-rwxr-x--- 1 root root 11380 Jan 1 00:00 init.qcom.factory.sh
-rwxr-x--- 1 root root 4022 Jan 1 00:00 init.qcom.modem_links.sh
-rwxr-x--- 1 root root 4561 Jan 1 00:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 2962 Jan 1 00:00 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 7718 Jan 1 00:00 init.qcom.usb.sh
-rwxr-x--- 1 root root 4199 Jan 1 00:00 init.rc
-rwxr-x--- 1 root root 218 Jan 1 00:00 init.wcnss.wifi.sh
-rwxr-x--- 1 root root 1611 Jan 1 00:00 init_bt.sh
drwxrwxr-x 5 root system 0 Jan 1 00:56 mnt
dr-xr-xr-x 169 root root 0 Jan 1 00:00 proc
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 20 2017 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 1 00:56 sdcard
drwxr-xr-x 2 root root 0 Jan 1 00:56 sideload
d---r-x--- 2 root sdcard_r 40 Jan 1 00:56 storage
dr-xr-xr-x 12 root root 0 Jan 1 00:56 sys
drwxr-xr-x 15 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 80 Jan 1 00:56 tmp
-rw-r--r-- 1 root root 840 Jan 1 00:00 twrp.fstab
-rw-r--r-- 1 root root 9098 Jan 1 00:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7515 Jan 1 00:00 ueventd.rc
~ #In this list there is no ".local". The content of "data/local" is the following:
/data/local # ls -la
drwxr-x--x 3 root root 4096 Jan 1 1970 .
drwxrwx--x 36 system system 4096 Jan 2 1970 ..
drwxrwx--x 2 shell shell 4096 Jan 1 1970 tmp
/data/local # cd local
/sbin/sh: cd: can't cd to local
/data/local # ls -la
drwxr-x--x 3 root root 4096 Jan 1 1970 .
drwxrwx--x 36 system system 4096 Jan 2 1970 ..
drwxrwx--x 2 shell shell 4096 Jan 1 1970 tmp
/data/local # -
@karstong it seems you're running the commands as root (I don't know why).
To list the content of "your" user's home the command is
ls -la /home/phablet/ -
@advocatux This command brings:
~ # ls -la /home/phablet/
ls: /home/phablet/: No such file or directory
~ # -
@karstong where are you running that command?
-
@advocatux In adb shell from my ubuntu desktop maschine with the phone connected via an USB cable.
-
@karstong if you exit adb shell, back to your terminal in Ubuntu, and type
adb pull /home/phablet/ /home/your_user/directory_you_want_to_save_to/What happens?Obviously change that parameters for yours.
-
@advocatux It gives me the same error:
~$ adb pull /home/phablet/ /home/huelguat/test
remote object '/home/phablet/' does not exist -
@karstong I hope you're doing something wrong because if really "/home/phablet/" doesn't exists, you have lost all the data in that device.
I'm assuming you're running adb properly, so I'm out of ideas for now.
-
@advocatux I hope too that I did not lose all my data. Anyway, thanks for your help!!!
-
@karstong you're welcome and I hope all your data is still in your device, somewhere!
