Re: [android-building] LOOSE ROOT PERMISSIONS WITH MASTER BUILD

[Antonio Marín Cerezuela]

Hi,

I recently noticed something similar but didn't pay much attention to it.

Reloading adb with root permissions is working for now but not a normal su from within an adb shell.

So:

$ adb root && adb shell should give you a su prompt

BR,

Tony 

Antonio Marin

Research Dept
Swiss Mobility Solutions
Av. Locutor Vicente Hipólito 39, 2ª Planta
03540 Playa de San Juan - Alicante
Spain

www.swissmobilitysolutions.com


Este mensaje contiene información reservada y confidencial destinada exclusivamente al destinatario. Si usted no es el destinatario no está autorizado a copiar, reproducir o distribuir este mensaje ni su contenido. Si ha recibido este mensaje por error, le rogamos que nos lo notifique inmediatamente.

The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). It may contain privileged and confidential information. If you are not the intended recipient, please destroy this message and notify us immediately. Any disclosure, copying or distribution of this message is prohibited and may be unlawful.

On 11/05/2013, at 02:53, Maddoggin chillin <valoz...@gmail.com> wrote:

 So recently built for nexus 4 from master branch and everything built fine but when flashed the rom i lost root. i cannot update su binary and cannot use root explorer or anything that uses root perms. has anyone built from master branch lately and experienced this? is there a command or something im missing during buildin process? thanks for any help!!

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Paul Beeler]

I think root is not supported in aosp, but my guess is it's because of SELinux

[Paul Beeler]

You are correct.  I should of been more specific in that aosp does not support third party root app's like superuser.  Since the original poster stated using app's like root explorer that rely on superuser app.  Adb root access should work fine unless the target build is user.

[Antonio Marín Cerezuela]

On 13/05/2013, at 18:21, Paul Beeler <spar...@gmail.com> wrote:

You are correct.  I should of been more specific in that aosp does not support third party root app's like superuser.  Since the original poster stated using app's like root explorer that rely on superuser app.  Adb root access should work fine unless the target build is user.

Sorry,  I missed the part of third party root apps. AFAIK,  It's not possible to run any super user app on top of AOSP,  I have been playing a little with that and some apps claim to support the "legacy" su binary but I have not succeeded in running any of them but didn't went too far trying.

[Jean-Baptiste Queru]

The intended behavior remains unchanged, i.e. that only the shell user has root access, only on userdebug and eng builds. If that specific use case is not working, that's a bug.

As far as I can tell, this is not a build issue and might be best discussed on other mailing lists (platform, kernel, or security).

JBQ

On Thu, May 16, 2013 at 11:30 AM, David Hacker <davidha...@gmail.com> wrote:

It seems even if you remove the AOSP su in system/extra and build another su/superuser or flash any of the superuser zips all I can get is su in shell all other apps get denied no matter what I do.

--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private will likely get ignored or forwarded to a public forum with no further warning.