0

Actually in my application after an intent is sent I create a file called myfile.asc now i'm trying through ADB to pull that file but the issue is that by using 

adb pull /data/data/xx.xxx.xxx/files/myfile.asc

or

adb pull /data/data/xx.xxx.xxx/files/myfile.asc C:\Users\me\Desktop\files

it returns

"remote object does not exist"

The path is actually taken from the Android Studio device File Explorer by clicking on the file and copying the path.

gmetal
  • 2,908
  • 2
  • 11
  • 16
NiceToMytyuk
  • 3,644
  • 3
  • 39
  • 100

1 Answers1

1

You are trying to access the private folder file which is not accessible in non-rooted android device. For that you need to get the adb shell access then provide the permission to access that directory.

For this use case, I have created a library that can help you. It's open-sourced.

https://medium.com/@mohom.r/extracting-android-data-files-of-our-android-app-from-non-rooted-device-be9084ddbdc3

Mohammed Rampurawala
  • 3,033
  • 2
  • 22
  • 32
  • actually even by adding destination_path i get the same error.. – NiceToMytyuk Sep 11 '19 at 14:14
  • Because you are trying to access the file which resides in the private directory where we don't have access until and unless you are using a rooted device. For this case you can try using the library : https://medium.com/@mohom.r/extracting-android-data-files-of-our-android-app-from-non-rooted-device-be9084ddbdc3 – Mohammed Rampurawala Sep 11 '19 at 14:17
  • actually i can't use an external library as i'm writing a VB.NET programm that should work as a "syncronizer" and by sending some intent from ADB i create specific file and then i should pull that file.. If i will write the file in a external storage should i solve the problem? – NiceToMytyuk Sep 11 '19 at 14:33
  • 2
    Yes that would solve the problem. Writing the file to external storage. – Mohammed Rampurawala Sep 11 '19 at 14:37