Epic Android bug interprets your typing as system commands
By Chris Ziegler 
posted Nov 8th 2008 8:42PM
posted Nov 8th 2008 8:42PM
The philosophy goes something like this: the great thing about Linux is that it's secure, and the great thing about open-source software is that it's thoroughly and constantly vetted for robustness. So to that end, Android should be pretty rock solid, right? Perhaps, but the overwhelming enormity of this particular bug definitely gives us pause. It turns out that G1 firmware revisions RC29 and earlier literally interpret everything you type as command-line operations, so if you happen across a legit command, it's going to get executed -- with superuser permissions, no less. No, seriously. Just go to the messaging app, the browser, or anywhere else a text box is convenient, type "reboot," press the enter key, and watch magic happen. We've tested this on two G1s, both with RC29 firmware, and have gotten this to consistently work on one of the two, so your mileage may vary -- but either way, this needed to get patched on the double. Fortunately, Google's been quick about it, rolling a fix into the RC30 build that's being rapidly pushed to users as we speak, but man... how did that get through?
Bah ha ha ha ha ha! Just TOO FUNNY!
Guess AT&T and Sprint were right to say that Android needs some work before they will put it on their networks.
Sounds like a device issue rather than a network issue. Are you implying that somehow this bug could "infect", or be used to hack the network? Not trying to be snarky, but I'm curious as to how you might think that would work.
What? My comment didn't imply any possible infection of the network-- I was simply saying that maybe AT&T and Sprint were right not to commit to Android given this new issue. Both companies commented that they believe Android needs more development before they will bring it to their networks; and maybe they said that knowing that Android isn't very tested and could present a lot of issues in the future. These problems I am referring to are hand-set/device issues not network.
Hmm, tried on mine, RC29 and doesn't work. Might be kinda funny if it did. . .parlor trick. But no such luck.
WTF? That's some crazy shit. Terrible terrible.
Hmm, can someone see what 'rm -rf /' does?
I think that changes the color of the trackball, right? Can someone confirm that please?! ;)
Hey, I tried this and it bricked my phone!
jk :)
Just tried on mine, didn't work?
Epic? *eyeroll*
the bug worked on mine last night then i got my rc30 this mornign and the bug is fixed
still rc19 and no bug reboot. who at E made this?
-fsck the what!?
don't say yes to the RC30 upgrade if you use your GPS... they busted it!!!
Oh it did not. My GPS still works fine. Don't spread lies just because you are having issues.
http://androidcommunity.com/forums/f7/recent-updates-and-gps-functionality-6929/#post73126
It looks like I am not the only one that has screwed up GPS now. RC19 and RC29 both had working GPS on my phone. TC4-RC30 busted it.