Error: Your device doesn't seem to be rooted.

[Tim Watkins]

I'm getting this message when I try to check the "Use Root" box in the
Kill App task. I was hoping to find a more reliable way to kill
Pandora. Anyway, I know I'm rooted, I'm able to use Super User,
Titanium Back-up and the like. I am still using the stock rom though.
I'm just wondering how Tasker checks to see if the phones rooted, or
if there is anything I can do to make Tasker know I'm rooted? Besides
installing a custom rom, because I'm not really sure how to do it. lol

[Pent]

I'm going to upload an update tomorrow, if it doesn't fix your problem
please get back to this thread.

Pent

[Tim W]

Your the man Pent, not only quick reply but everything seems to be
working great with this update. I can check the Use root box, and when
it come time for Tasker to kill Pandora I get a pop up that Taskers
been granted SU permission, and Pandora gets killed. Thanks for the
update and a great app.

[Pent]

> Your the man Pent, not only quick reply but everything seems to be
> working great with this update. I can check the Use root box, and when
> it come time for Tasker to kill Pandora I get a pop up that Taskers
> been granted SU permission, and Pandora gets killed. Thanks for the
> update and a great app.

Great.

Go easy on the Kill Apps BTW, the app doesn't get a chance to save
it's
data.

Pent

[ISO]

Hi Pent,

 

sorry for posting in an old post...

 

I'm having this issue too since I updated to ICS 4.0.3 XWLP8 and XWLP7 rooted kernel.

 

Now, in tasker I'm having this message. Your device doesn't seem to be rooted.

 

Is a tasker problem or it's a problem of my scenario? I have a Samsung Galaxy SII.

 

Regards!

[Pent]

The main issue I know with detecting root ATM is using SuperSU instead
of SuperUser (fixed next version).
Let me know if you still have the issue after next version.

Pent

[ISO]

Ok, thank you Pent,

 

I changed SuperSu for SuperUser and now everything works...

 

I will try with SuperSU when the new version is released.

 

Regards!

ISO

[TomL]

Have you tried rebooting phone?  If that doesn't work, have you tried clearing the data cache for the superuser app and then re-enabling each app for superuser permissions?  I find that helps sometimes when root access seems wonky.

Tom

On Friday, March 8, 2013 12:20:46 AM UTC-5, Eric Maycock wrote:

I know this is an old post  but I just installed the new clockworkmod superuser and I am getting the exact same error. Every other app that requests root is working just fine.

[Eric Maycock]

Yeah, I have tried rebooting, deleting cache for both apps, uninstalling and re installing both apps. Both are fresh installs now and my other apps have prompted for superuser access, but Tasker just gives me the error listed in this thread. It's almost like it doesn't even try.

[doc]

I have never been able to get "use root" to work in Tasker. I've given up trying and now use Secure Settings whenever I need a task to use root access. Its just a habit now.

[Eric Maycock]

It worked fine for me until I switched super user apps over to the new clockworkmod one. Strangely, every other root requiring app works fine with the new super user. 

On Fri, Mar 8, 2013 at 8:18 PM, doc <docsl...@gmail.com> wrote:

I have never been able to get "use root" to work in Tasker.  I've given up trying and now use Secure Settings whenever I need a task to use root access. Its just a habit now.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/GvWGQygW-7k/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Pent]

> I had the same problem and went looking for a solution, until it's fixed
> you can work around it by creating an empty file called:
>
> /system/app/Superuser.apk
>
> Tasker should have a more reliable check if su is able to be run as this is
> the first app I have found with issues with Koush's new superuser app.

Could you forward me the APK ?

The filesystem check for Superuser is actually a fallback, it's
supposed to
pick it up from the Superuser app listening for the relevant intent.

Thanks,

Pent

[Paul Marston]

I've attached the apk I found at /data/app/com.koushikdutta.superuser-1.apk

There doesn't seem to be a system app for it that I can see.

[Pent]

> I've attached the apk I found at /data/app/com.koushikdutta.superuser-1.apk

Thanks.

Doesn't declare that it listens for the su requests, annoyingly.

Pent

[Pent]

I've put a specific check in for that package, also qualifying is if
the superuser permission that it requires is known to the system.

Pent

[Eric Maycock]

Creating the Superuser.apk file in /system/apps worked for me. It didn't at first, but then I changed the file permissions to 644 and restarted Tasker. All is well now. :) Thanks!!

On Friday, March 8, 2013 11:43:27 AM UTC-7, Paul Marston wrote:

I had the same problem and went looking for a solution, until it's fixed you can work around it by creating an empty file called:

/system/app/Superuser.apk

Tasker should have a more reliable check if su is able to be run as this is the first app I have found with issues with Koush's new superuser app.