Google sending out update RC30 to stop root access

[Crashdamage]

rynosaur wrote:

...I'd PAY MONEY to have a nice KDE or Gnome desktop.

KDE? Gnome?? Oh, noooo....something much simpler/lighter/faster/better. I can't stand either KDE or Gnome anyway.

But, WTH, why are we talking about this? I mean, I like Android. I think it's a kick-ass start for a killer Linux-based mobile OS. Let's work on that and not waste time and effort on stuff like Debian-on-G1.

[ickyfehmleh]

I don't think many of us could have successfully pulled off the Debian jailbreak as it was written. Hell, i had a hard time doing a GUI install of Ubuntu with a dual-boot Vista install.
...

Besides, if a DEVELOPER is SMART they'll write a Linux distro custom-compiled for the G1 that isn't risky for average dullards like me, and I'd PAY MONEY to have a nice KDE or Gnome desktop. HINT HINT!

First you say that you had a hard time performing a GUI installation of Ubuntu, then you go on to say that you want a custom Linux distribution FOR YOUR CELL PHONE. Perhaps you yourself are in need if a 'hint hint': Google didn't pour money into the development of the Android APIs so people could wipe out all of their hard work and opt instead for a Linux installation. Yes, Google leveraged Linux's availability on such devices, but Android is much more than Just Another Linux Installation.

[Oh.Diva]

The AnyCut trick did not work on mine. Still stuck on RC19

[refused9150]

the anycut trick did not work on mine. Still stuck on rc19

rc29!!! =)

[soldair]

hey all. I am really confused by some posts by a few members speaking about this as a "security hole".

in order for this to become a security problem you would have to turn on telnetd and forget to turn it off.

Because telnetd does not auto start a simple reboot would be enough for even a lazy person to "re-secure" their phone.

Google wasted time stopping people from using their own device with no security gain.

There is no gain from either the providers or Google by locking users out of the filesystem.

[smoger]

hey all. I am really confused by some posts by a few members speaking about this as a "security hole".

in order for this to become a security problem you would have to turn on telnetd and forget to turn it off.

Because telnetd does not auto start a simple reboot would be enough for even a lazy person to "re-secure" their phone.

Google wasted time stopping people from using their own device with no security gain.

There is no gain from either the providers or Google by locking users out of the filesystem.

..except for the fact that *everything* you type goes through to the shell....

[bugmenot1]

hmm...well following a walkthrough i found somewhere on the "internet machine":

• Yes i've taken my stock RC30 g1 and downgraded to RC29 taking advantage of the root shell bug to create a root shell just for meee

• Yes i then upgraded to a modified RC30 which closed all the security holes in RC29, keeping of course root shell just for meeeeee

• Yes i'm now using a custom theme and now use a custom boot screen for my g1 (pretty kool!)

• Yes i have all my apps and app cache stored on my sdcard, and umm like over 50 apps with over 60 meg of system memory left on my phone

• Yes imagine all of the possibilities my g1 can realize because of the BRILLIANT g1 Hax0rs out there (Special thanks to you sirs!!)

• root access (IMO) to the G1 should only be for power users or those who have the ballz to take a chance (and risk bricking their $400 phone!) to accomplish something pretty rare and kool...period! not in the hands of an "average" lamer stupid r-tard; and to all you wussies who dont wanna root your phone, posting here and preaching the gospel to the rest of us about how it's not right to root your phone, remember your driving a le-mans, I'm driving a GTO baby Yeahhh, they look the same, but its wats under da hood dat counts, ya dig?? ROFL...

• And remember if your G1 is NOT rooted, well then My g1 can kick your G1s a## any-day-of-the-week!

Bye bye now!

[ickyfehmleh]

Thank you for resurrecting a two-month old thread.