$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
init
default.prop
logo.rle
init.trout.rc
data
system
sys
proc
init.goldfish.rc
init.rc
sbin
root
dev
$ ls /data/
ls /data/
opendir failed, Permission denied
$ chmod 777 /data/
chmod 777 /data/
Unable to chmod /data/: Operation not permitted
$
I want to change the permission settings for the /data dir, but it
won't let me....
This is ridiculous, I bought into what I thought was a completely open
platform only to find out that its not. Google/HTC/T-Mobile needs to
give us a way of loading our own build on the device or else any hope
google had of making android mainstream will fail.
On Oct 28, 8:24 pm, "Justin (Google Employee)" <j...@google.com>
wrote:
I have the same frustration. This is pretty bad. It is after all, my device. I wouldn't be happy if I got a computer from Dell and they told me I couldn't have admin access.
On Tue, Oct 28, 2008 at 6:00 PM, surferdude <datruesur...@gmail.com> wrote:
> This is ridiculous, I bought into what I thought was a completely open > platform only to find out that its not. Google/HTC/T-Mobile needs to > give us a way of loading our own build on the device or else any hope > google had of making android mainstream will fail. > On Oct 28, 8:24 pm, "Justin (Google Employee)" <j...@google.com> > wrote: > > You can't do this on a device. On devices root is disabled.
> > Cheers, > > Justin > > Android Team @ Google
> > On Oct 28, 4:42 pm, kooscar <osca...@gmail.com> wrote:
> This is ridiculous, I boughtintowhat I thought was a completely open
> platform only to find out that its not. Google/HTC/T-Mobile needs to
> give us a way of loading our own build on thedeviceor else any hope
> google had of making android mainstream will fail.
> On Oct 28, 8:24 pm, "Justin (Google Employee)" <j...@google.com>
> wrote:
> > You can't do this on adevice. On devices root is disabled.
> > Cheers,
> > Justin
> > Android Team @ Google
> > On Oct 28, 4:42 pm, kooscar <osca...@gmail.com> wrote:
However, based on your responses, is it safe to assume that Android
does not allow user manipulation of the file system and admin. related
behaviors aside from in/through application?
Practically speaking, something as simple as chmod 777 /data or ls /
data can only be done through an application?
Thank you,
Oscar
On Oct 29, 8:31 am, "Justin (Google Employee)" <j...@google.com>
wrote:
> > Google/HTC/T-Mobile needs to
> > give us a way of loading our own build on thedevice
> This already exists. Just run 'adb install <YOUR_APP.apk>'.
> Cheers,
> Justin
> Android Team @ Google
> On Oct 28, 6:00 pm, surferdude <datruesur...@gmail.com> wrote:
> > This is ridiculous, I boughtintowhat I thought was a completely open
> > platform only to find out that its not. Google/HTC/T-Mobile needs to
> > give us a way of loading our own build on thedeviceor else any hope
> > google had of making android mainstream will fail.
> > On Oct 28, 8:24 pm, "Justin (Google Employee)" <j...@google.com>
> > wrote:
> > > You can't do this on adevice. On devices root is disabled.
> > > Cheers,
> > > Justin
> > > Android Team @ Google
> > > On Oct 28, 4:42 pm, kooscar <osca...@gmail.com> wrote:
You misunderstood me. I want to take the source code from
source.android.com, build it and flash it on to my device, so I can
have superuser privileges instead of being restricted by Google/T-
Mobile. Telling your developers that root access is disabled and still
calling the platform open is unacceptable.
On Oct 29, 11:31 am, "Justin (Google Employee)" <j...@google.com>
wrote:
> > Google/HTC/T-Mobile needs to
> > give us a way of loading our own build on thedevice
> This already exists. Just run 'adb install <YOUR_APP.apk>'.
> Cheers,
> Justin
> Android Team @ Google
> On Oct 28, 6:00 pm, surferdude <datruesur...@gmail.com> wrote:
> > This is ridiculous, I boughtintowhat I thought was a completely open
> > platform only to find out that its not. Google/HTC/T-Mobile needs to
> > give us a way of loading our own build on thedeviceor else any hope
> > google had of making android mainstream will fail.
> > On Oct 28, 8:24 pm, "Justin (Google Employee)" <j...@google.com>
> > wrote:
> > > You can't do this on adevice. On devices root is disabled.
> > > Cheers,
> > > Justin
> > > Android Team @ Google
> > > On Oct 28, 4:42 pm, kooscar <osca...@gmail.com> wrote:
surferdude wrote: > I want to take the source code from > source.android.com, build it and flash it on to my device, so I can > have superuser privileges instead of being restricted by Google/T- > Mobile.
Whether the G1 accepts replacement firmware, and the process for doing them, is a hardware question. HTC has a decent track record in this regard, though I haven't seen a definitive statement one way or another on the G1.
> Telling your developers that root access is disabled and still
> calling the platform open is unacceptable.
By your definition, Linux is not an open platform.
It is eminently possible to take Linux and install it on a device that does not grant root access and is not designed to have its firmware replaced by end users.
Take, for example, the TiVo. Getting root access on a TiVo, where possible, is a royal pain, and replacing the TiVo software appears tor require physically dismantling the unit, AFAIK. Yet, TiVo runs Linux. Linux is open -- the TiVo is not. Similarly, Android is open -- the G1 may not be.
The Android "distro" that is installed by HTC on the G1 has root access locked down. It is eminently likely that mainstream Android "distros" on other devices distributed by major carriers will have root access locked down. This should not preclude other device makers from offering Android devices with root access, via their own patch to the Android source to lift that restriction.
So, rolling all the way back to your statement of what you want, the questions you'll need answers for are:
1. Which pieces of Android hardware will allow flashing of replacement firmware, and is the G1 one of them?
2. Where in the Android source is the no-root lockdown implemented and, if it's not configurable today as a build option, will the core Android team accept a patch that *does* make it a build-time configuration option, so those interested in root access can easily make firmware that offers it?
#1 will determine how you can do it at all on hardware; #2 will determine if this is perpetually a non-mainstream patch or if your wishes and OHA's wishes can be met simultaneously.
-- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.3 Published!
Since it's already known that there's an Over-the-air firmware update
available for the G1, it's obvious that the flash is reprogrammable.
If the question is whether there are other avenues, besides OTA, I
would expect that the source code should answer that...
On Oct 29, 11:32 am, Mark Murphy <mmur...@commonsware.com> wrote:
> surferdude wrote:
> So, rolling all the way back to your statement of what you want, the
> questions you'll need answers for are:
> 1. Which pieces of Android hardware will allow flashing of replacement
> firmware, and is the G1 one of them?
> #1 will determine how you can do it at all on hardware; #2 will
> determine if this is perpetually a non-mainstream patch or if your
> wishes and OHA's wishes can be met simultaneously.
On Thu, Oct 30, 2008 at 9:26 AM, hyc <h...@highlandsun.com> wrote:
> Since it's already known that there's an Over-the-air firmware update > available for the G1, it's obvious that the flash is reprogrammable. > If the question is whether there are other avenues, besides OTA, I > would expect that the source code should answer that...
> On Oct 29, 11:32 am, Mark Murphy <mmur...@commonsware.com> wrote: >> surferdude wrote:
>> So, rolling all the way back to your statement of what you want, the >> questions you'll need answers for are:
>> 1. Which pieces of Android hardware will allow flashing of replacement >> firmware, and is the G1 one of them?
>> #1 will determine how you can do it at all on hardware; #2 will >> determine if this is perpetually a non-mainstream patch or if your >> wishes and OHA's wishes can be met simultaneously.
> On Thu, Oct 30, 2008 at 9:26 AM, hyc <h...@highlandsun.com> wrote:
> > Since it's already known that there's an Over-the-air firmware update
> > available for the G1, it's obvious that the flash is reprogrammable.
> > If the question is whether there are other avenues, besides OTA, I
> > would expect that the source code should answer that...
> > On Oct 29, 11:32 am, Mark Murphy <mmur...@commonsware.com> wrote:
> >> surferdude wrote:
> >> So, rolling all the way back to your statement of what you want, the
> >> questions you'll need answers for are:
> >> 1. Which pieces of Android hardware will allow flashing of replacement
> >> firmware, and is the G1 one of them?
> >> #1 will determine how you can do it at all on hardware; #2 will
> >> determine if this is perpetually a non-mainstream patch or if your
> >> wishes and OHA's wishes can be met simultaneously.
The G1 is aimed at end users, not system developers. For user security
reasons the G1 will only accept properly signed system images. I'm not
sure, in this case, who 'owns' the key, whether it is the carrier or
the manufacturer, but one or both of them handle insuring system
images are signed.
Cheers,
Justin
Android Team @ Google
On Oct 31, 2:37 am, "Danny O'Brien" <dannyobr...@gmail.com> wrote:
> > On Thu, Oct 30, 2008 at 9:26 AM, hyc <h...@highlandsun.com> wrote:
> > > Since it's already known that there's an Over-the-air firmware update
> > > available for the G1, it's obvious that the flash is reprogrammable.
> > > If the question is whether there are other avenues, besides OTA, I
> > > would expect that the source code should answer that...
> > > On Oct 29, 11:32 am, Mark Murphy <mmur...@commonsware.com> wrote:
> > >> surferdude wrote:
> > >> So, rolling all the way back to your statement of what you want, the
> > >> questions you'll need answers for are:
> > >> 1. Which pieces of Android hardware will allow flashing of replacement
> > >> firmware, and is the G1 one of them?
> > >> #1 will determine how you can do it at all on hardware; #2 will
> > >> determine if this is perpetually a non-mainstream patch or if your
> > >> wishes and OHA's wishes can be met simultaneously.
|
