Tasker is not asking for root. Have SuperSU installed and phone is rooted (Nexus5, 4.4.2, stock, rooted)

6,775 views
Skip to first unread message

Adheesh Bhagat

unread,
Mar 26, 2014, 3:10:02 AM3/26/14
to tas...@googlegroups.com
Hello!

Loving tasker, recommend it everywhere i go ;) (Thanks, Pent!) 

I've been trying to enable root access on it though, but tasker neither asks for root permission, and any root action that it tries is denied by superSU. (Tasker has been denied superuser for an interactive ...) Tasker also does not show up on SuperSU's list of apps. 

I read that tasker works closer with superuser, however superuser hasn't been updated in a long time and from what I understand, on newer devices, SuperSU is a better option. (i'm running a nexus 5 4.4.2, stock, rooted, xposed, gravitybox)

(Yes, I've read the previous posts about this and haven't been able to get it working, hence I ask again) 

In the FAQ's, I found this:
**********

Tasker requires two things before root functionality is enabled:

  1. the su program must be in your path
  2. one of the following must be found:
    • a superuser package
    • the word modversion somewhere in the file /system/build.prop

If root is not being detected on your device but you are sure that root can be used by Tasker, you can therefore probably fix that by adding a line like:

# modversion this line enables Tasker root support

to the top of the file /system/build.prop.

**************

I have edited build.prop to include the line mentioned above, but am still unable to use root. What does the first condition mean? How do I include it 'in my path'? Can someone guide me? 

Is there something else I should be doing? 

Any help is much appreciated. 


Pent

unread,
Mar 26, 2014, 4:04:58 AM3/26/14
to tas...@googlegroups.com

I've been trying to enable root access on it though, but tasker neither asks for root permission, and any root action that it tries is denied by superSU.

If you get the 'denied' message, then Tasker has tried a root action and SuperSU has denied it. Nothing Tasker can do about that.
There is no explicit 'ask for root' protocol, apps try to run root stuff, then superSU should ask you whether to grant.

Pent

Adheesh Bhagat

unread,
Mar 26, 2014, 4:25:03 AM3/26/14
to tas...@googlegroups.com
Oh wow. I finally managed to make it work.

For the others who may have similar problems, heres what I did.

1) Have tasker, superSU installed.
2) edit build.prop file to include "# modversion this line enables Tasker root support" as the first line (without the "")
3) restart phone
4) launch tasker and create a task to delete any random file, and check 'use root'.
5) run the task. SuperSU should now ask whether to give tasker root access! 
6) .....
7) Profit. 

Sean M

unread,
Feb 26, 2018, 11:41:27 PM2/26/18
to Tasker
A late reply but thanks. Just had this problem and your solution worked for me.

Christian Weiss

unread,
Apr 14, 2018, 2:03:06 AM4/14/18
to Tasker
Same here. Until now, I used the direct-purchase version and root was available. But now I changed to the play store version (beta) - tasker suddenly claims my device is not rooted.

Christian Weiss

unread,
Apr 14, 2018, 2:04:00 AM4/14/18
to Tasker
Did not work for me.

Stipe

unread,
Apr 14, 2018, 10:10:21 AM4/14/18
to Tasker
Neither for me, still getting: "Error: your device doesn't appear to be rooted".

tboooe

unread,
Apr 15, 2018, 10:17:25 AM4/15/18
to Tasker
Same here. I use Run Shell command to turn on and off gps. This used to work fine but it seems one of the beta versions broke this functionality. Please fix. I am rooted on Mate 9.

João Dias

unread,
Apr 16, 2018, 8:56:38 AM4/16/18
to tas...@googlegroups.com
What version of the beta is everyone using here? Thanks!

On Sun, Apr 15, 2018 at 3:17 PM, tboooe <tbo...@gmail.com> wrote:
Same here.  I use Run Shell command to turn on and off gps.  This used to work fine but it seems one of the beta versions broke this functionality.  Please fix.  I am rooted on Mate 9.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

tboooe

unread,
Apr 16, 2018, 9:27:57 AM4/16/18
to Tasker


On Monday, April 16, 2018 at 5:56:38 AM UTC-7, joaomgcd wrote:
What version of the beta is everyone using here? Thanks!
On Sun, Apr 15, 2018 at 3:17 PM, tboooe <tbo...@gmail.com> wrote:
Same here.  I use Run Shell command to turn on and off gps.  This used to work fine but it seems one of the beta versions broke this functionality.  Please fix.  I am rooted on Mate 9.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

João Dias

unread,
Apr 16, 2018, 9:42:59 AM4/16/18
to tas...@googlegroups.com
Thanks, I'll try changing something for the next version and see if that works.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

Stipe

unread,
Apr 16, 2018, 9:57:41 AM4/16/18
to Tasker
I'm currently running 5.1.6b.bf too on Android 5.1.1.

Dne ponedeljek, 16. april 2018 14.56.38 UTC+2 je oseba joaomgcd napisala:
What version of the beta is everyone using here? Thanks!
On Sun, Apr 15, 2018 at 3:17 PM, tboooe <tbo...@gmail.com> wrote:
Same here.  I use Run Shell command to turn on and off gps.  This used to work fine but it seems one of the beta versions broke this functionality.  Please fix.  I am rooted on Mate 9.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

Andrew L

unread,
Aug 24, 2019, 2:58:50 AM8/24/19
to Tasker
This solution worked for me. Thank you. I have Kingo root, but didn’t run into any issues. I realize this is a zombie thread, but it helped me out and it’s nice to have confirmation of a working solution.
Reply all
Reply to author
Forward
0 new messages