Problem with root file access

70 views
Skip to first unread message

Vikesh Dhatterwal

unread,
Jan 8, 2017, 9:26:07 AM1/8/17
to Tasker
Recently, Tasker has been having problems accessing files and directories using root mode. When I try to copy a file, with the use root checked, it gives error that the given path is a dir not a file. But I can verify using Solid Explorer that it is a file indeed. However if I uncheck the root option, I get permission denied problem. It happened when I was trying the following:

1. Replace /system/media/bootanimation.zip with /sdcard/bootanimation.zip
2. Copying an APK file for any installed application. (/data/data/<package>-1/base.apk to /sdcard/Download/<package>.apk)

Earlier on Stock Marshmallow, it worked fine, but now it is having problems after I installed CM 14.1 (20161223-nightly-osprey). I am using Moto G 2015 (3rd Gen) India version.

Here is the message copied from the error:
##### Using root option checked:

19.37.19/FileUtil nrda: need request: /storage/emulated/0/bootanimation.zip: false
19.37.19/E checkSDPath: /storage/emulated/0/bootanimation.zip
19.37.19/E Copy File: checkSDPath: /storage/emulated/0/bootanimation.zip useDocFile: false
19.37.19/Shell runSync test -e '/storage/emulated/0/bootanimation.zip' root: true timeout: 3000
19.37.19/Shell have process
19.37.19/Shell write cmd: test -e '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process timeout timer 3000ms for: test -e '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process-thread ID 287
19.37.19/Shell joined with 287
19.37.19/Shell exit result: 0
19.37.19/Shell non-null timeout
19.37.19/Shell runSync test -f '/storage/emulated/0/bootanimation.zip' root: true timeout: 3000
19.37.19/Shell have process
19.37.19/Shell write cmd: test -f '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process timeout timer 3000ms for: test -f '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process-thread ID 289
19.37.19/Shell joined with 289
19.37.19/Shell exit result: 0
19.37.19/Shell non-null timeout
19.37.19/Shell runSync test -d '/storage/emulated/0/bootanimation.zip' root: true timeout: 3000
19.37.19/Shell have process
19.37.19/Shell write cmd: test -d '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process timeout timer 3000ms for: test -d '/storage/emulated/0/bootanimation.zip'
19.37.19/Shell start process-thread ID 291
19.37.19/Shell joined with 291
19.37.19/Shell exit result: 0
19.37.19/Shell non-null timeout
19.37.19/E Copy File: /storage/emulated/0/bootanimation.zip is a directory.
19.37.19/E Copy File: checkSDPath: /storage/emulated/0/bootanimation.zip ok false
19.37.19/E result: stop task (error)
19.37.19/E Error: 1
19.37.19/MacroEdit action finished exeID 1 action no 0 code 404 status: Err next 0

##### Using root option unchecked:
19.38.33/FileUtil needReqDocAccess: wudf: no write needed
19.38.33/FileUtil nrda: need request: /storage/emulated/0/bootanimation.zip: false
19.38.33/E checkSDPath: /storage/emulated/0/bootanimation.zip
19.38.33/FileUtil Copy File/checkSDPath: wudf: no write needed
19.38.33/E Copy File: checkSDPath: /storage/emulated/0/bootanimation.zip useDocFile: false
19.38.33/E Copy File: file not found: /storage/emulated/0/bootanimation.zip.
19.38.33/E Copy File: checkSDPath: /storage/emulated/0/bootanimation.zip ok false
19.38.33/E result: stop task (error)
19.38.33/E Error: 1
19.38.33/MacroEdit action finished exeID 1 action no 0 code 404 status: Err next 0

Please suggest an alternative approach to get this done.

Pent

unread,
Jan 9, 2017, 2:54:56 AM1/9/17
to Tasker
It's a bug in this particular action, fixed for next update
(in a few days I expect)

Pent
Reply all
Reply to author
Forward
0 new messages