W dniu 23.08.2012 00:41, Ron Munitz pisze:
Hi, Do you have ro.secure somewhere in your "getprop" ?
No, I've checked that, I also checked the privilege drop code path so I'm sure I'm not taking it.
A hint: -tests builds run adbd as shell (or quickly drop so I could not notice), -eng builds keep them as root.
If ro.secure==1 you'll be defaulted to the shell user - so that's what you need to change (try build.prop)
build.prop is identical in both builds
Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Thanks ZK
On 23 August 2012 00:54, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Just run "adb root" instead of "adb shell" on your computer.
The former is supposed to give you a root shell, the latter gives you a shell as some user who may or may not be root (depending on the build type).
ttyl bero
W dniu 23.08.2012 13:18, Bernhard Rosenkränzer pisze:
On 23 August 2012 00:54, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Just run "adb root" instead of "adb shell" on your computer.
The former is supposed to give you a root shell, the latter gives you a shell as some user who may or may not be root (depending on the build type).
Thanks for the hint Bero!
I've actually solved it with that patch I've proposed, my build was wrong (partial) so I could not see the side effects of the fix.
Thanks ZK
On Thu, Aug 23, 2012 at 1:18 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On 23 August 2012 00:54, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Just run "adb root" instead of "adb shell" on your computer.
The former is supposed to give you a root shell, the latter gives you a shell as some user who may or may not be root (depending on the build type).
Can you give background what's the approach android takes here? e.g. when do they give you root and when do you get a "unprivileged" shell and why is that?
Also, does it mean that a tests build is rather a production builds with test and we would like to have an eng+tests target?
Debug capabilities depend on your build type, or more precisely some system properties which it defines, and root is not meant for production so it is a debug capability. E.g. you will never have root access to any purchased device...
As per your test builds, unless you are doing some security penetration tests I would keep the root. From my experience non rooted androids tend to make life difficult when testing bring ups, but I don't really know your cases so that's just a thought. On Aug 23, 2012 2:51 PM, "Alexander Sack" asac@linaro.org wrote:
On Thu, Aug 23, 2012 at 1:18 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
On 23 August 2012 00:54, Zygmunt Krynicki zygmunt.krynicki@linaro.org
wrote:
Does "adb root" work for you?
Where should I run it? I never had to do that with -eng builds.
Just run "adb root" instead of "adb shell" on your computer.
The former is supposed to give you a root shell, the latter gives you a shell as some user who may or may not be root (depending on the build type).
Can you give background what's the approach android takes here? e.g. when do they give you root and when do you get a "unprivileged" shell and why is that?
Also, does it mean that a tests build is rather a production builds with test and we would like to have an eng+tests target?
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
Alexander Sack -
Bernhard Rosenkränzer -
Ron Munitz -
Zygmunt Krynicki