I am attempting to back up my /data folder and everytime i do /adb pull /data/ i get this
c:\android-sdk>adb pull /data/
pull: building file list...
0 files pulled. 0 files skipped.
What am I doing wrong?
Edit: seems that I got the pull data to work by doing it one by one, however when i go into /data/data and attempt a pull i get this
c:\data backup>adb pull /data/data/com.android.contacts
pull: building file list...
0 files pulled. 0 files skipped.
which is the same thing as before
Related
Everytime I use
Code:
adb pull /data/data/ C:\Android
it responds with
Code:
pull: building file list...
0 files pulled. 0 files skipped.
Pulling any other file works, but I can't seem to pull any file from /data/data/..
Is there a reason to this? or is it just me >_>?
its been over a year since i last used ADB and this is the first time using adb on the optimus 3d but i cannot seem to pull anything off of the phone.
this is the command im using on command line
adb pull /data/app app & adb pull /data/app-private app-private
but i just get this returned
pull: building file list...
0 files pulled. 0 files skipped.
pull: building file list...
0 files pulled. 0 files skipped.
now i can tell you that there are many apks inside that folder.
i cant even list what files are in that directory by using the 'ls' parameter
the only way i can actually view the files is if i
adb shell su
# cd data/app
ls
then it will list the files but i still cannot pull the files it just says data/app/filename.apk cannot find specified file
is this some kind of lock lg have put on or has the adb been updated and no longer allow you to do this?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Im guessing no one knows or has not bothered with adb themselves
i did like this
(rooted phone)
enter in adb shell
su
mkdir app1
cp /data/app/*.apk app1
exit from shell
then try adb pull /app1 app
and its working
to remove files and folder from app1 folder in adb shell
rm -r app1 (deletes app folder)
pls note rm -r will delete folders with files so dont delete wrong folder.
cheers didnt think about creating a different directory in an attempt to get round the system, cool will try this many thanks
A big mistake and big problem, I am still locked, I recently run rm -rf on a direcoty with was simlinked to /system/ and delete my ROM (I think):
Code:
adb pull /system/
pull: building file list...
0 files pulled. 0 files skipped.
Thats really weird, any chance to fix it?
LOL fixed it!! I put the zip with asus software to sdcard, name it EP201_768_SDUPDATE.zip, booted to RCK and the magic begins, it install it!!!!!
I'm trying to mount /data/data/ to /storage/sdcard0/data/test/ with the following via adb shell:
Code:
su
mkdir /storage/sdcard0/data/test
mount -o bind /data/data/ /storage/sdcard0/data/test/
When /storage/sdcard0/data/test/ is viewed within ES File Explorer or any other application, it appears empty. The file contents appear when listing the contents via adb shell. Why is this happening?
bump
Code:
su
mkdir /storage/sdcard[b]0[/b]/data/test
mount -o bind /data/data/ /storage/sdcard0/data/test/
Seems like the 0 was missing in the second line.
peachpuff said:
Seems like the 0 was missing in the second line.
Click to expand...
Click to collapse
Oops. That was a typo in the post. Folders still appear empty even with the 'missing' 0. Is there another cause?
ROM: LineageOS 18.1, Recovery: LineageOS 18.1 recovery
I messed up and put my build.prop in an invalid state. I got the default build.prop from the rom zip,rebooted the phone to recovery (lineageos 18.1 recovery), mounted the system partition on /mnt/system, and tried to write build.prop to default via adb shell and then cat >/mnt/system/system/build.prop and writing whatever stuff I want. However, even after remounting as rw, I get the following error message:
Code:
cat: xwrite: No space left on device
The same thing happens if I just edit on my PC and do adb push
Code:
$ adb push build.prop /mnt/system/system/build.prop
build.prop: 1 file pushed, 0 skipped. 89.9 MB/s (2662 bytes in 0.000s)
adb: error: failed to copy 'build.prop' to '/mnt/system/system/build.prop': remote write failed: No space left on device
Now what does this even mean?? There is 3.1M free space, as confirmed by df -h. I really searched I cannot find anything on this. Any help would be really appreciated!
---
I can confirm it is mounted as rw by checking this line in /proc/mounts
Code:
/dev/block/dm-0 /mnt/system ext4 rw,seclabel,relatime 0 0
adb remount also fails with
/system/bin/sh: remount: inaccessible or not found
I'm at my wit's end, any guidance here? I feel this should really not be this difficult! I just want to rewrite build.prop from adb/recovery!
---
It might have something to do with overlayfs, as seen here https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md. However adb remount merely says /system/bin/sh: remount: inaccessible or not found! How should I get this to work?
---
Finally: maybe I could just try to flash a zip containing only the build.prop via adb sideload? Will adb sideload wipe anything (e.g. system) or just overwrite the files which are present in the zip?
---
Just ended up flashing again. It worked without deleting apps or data