But you're using 13.10, and I'm still on 12.04 (on THIS particular laptop...some of my other computers are still on 9.04 and up
). They're not available for me, at least not without some tweaking, which I don't feel like doing right now.-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Forever Rootless?
- Thread starter jefboyardee
- Start date
). They're not available for me, at least not without some tweaking, which I don't feel like doing right now.
Joelgp83
Android Enthusiast
For the record, the download under "SDK Tools only" is more or less identical to the package in the ubuntu/debian repositories, with the exception that it is NOT in .deb format.
The ADT bundle, on the other hand, should be the whole development SDK.
jefboyardee
Extreme Android User
I’m trying to give rooting one more shot and you guys are like a bunch of surgeons cracking trade jokes as they congregate around a dying patient...
Bonne chance! 
I rooted my first android because I knew I'd keep it longer than official software updates would be available, so sooner or later I'd be using custom ROMs. Of course, since that meant I'd be rooting sooner or later, it inevitably became "sooner".
Yeah, the current one worked fine without root, but I felt insecure without the ability to take a nandroid, use Titanium to undo a retrograde app update, wipe the dalvik cache, etc. Plus with a custom ROM I have lots of little tweaks that aren't available by default, and the option of loading something completely different if that takes my fancy. As has been said, once you are used to having the options, it's hard to give them up.
That's also part of why I favour high-end devices: I want a decent dev community.
I rooted my first android because I knew I'd keep it longer than official software updates would be available, so sooner or later I'd be using custom ROMs. Of course, since that meant I'd be rooting sooner or later, it inevitably became "sooner".
Yeah, the current one worked fine without root, but I felt insecure without the ability to take a nandroid, use Titanium to undo a retrograde app update, wipe the dalvik cache, etc. Plus with a custom ROM I have lots of little tweaks that aren't available by default, and the option of loading something completely different if that takes my fancy. As has been said, once you are used to having the options, it's hard to give them up.
That's also part of why I favour high-end devices: I want a decent dev community.
There seems to be some confusion as to what rooting actually does, probably resulting from most guides asking people to follow steps without explaining the steps fully. Here is my understanding of the general process, please jump in and correct where appropriate, hehe (smiley for serious face, hiding some evil laughter).
1. An app wants to do something with root privileges, so it requests it from the OS via "su".
2. su normally checks the app's user (each app has its own user) against a list of users that are allowed to do this (sudoers). For a rooted phone, su is replaced by a customised version that asks "superuser" application.
3. superuser application as installed by the apk, checks against its own list of apps (users), if not granted it asks the human user with the UI.
So the only changes needed are to replace "su" binary, and install the matching "superuser.apk".
Replace su binary must be done with root privileges in the first place. To get these privileges, usually:
1. Connect to a PC with USB cable and use "adb" to login with a debug shell user (adb shell). Sometimes this is enough as the phone grants the debug user root access.
2. If the debug user does not have root privileges, one of several "root exploits" are tried to gain access.
Hopefully this is useful to someone to justify me trying to inflate my ego by looking knowledgeable!
1. An app wants to do something with root privileges, so it requests it from the OS via "su".
2. su normally checks the app's user (each app has its own user) against a list of users that are allowed to do this (sudoers). For a rooted phone, su is replaced by a customised version that asks "superuser" application.
3. superuser application as installed by the apk, checks against its own list of apps (users), if not granted it asks the human user with the UI.
So the only changes needed are to replace "su" binary, and install the matching "superuser.apk".
Replace su binary must be done with root privileges in the first place. To get these privileges, usually:
1. Connect to a PC with USB cable and use "adb" to login with a debug shell user (adb shell). Sometimes this is enough as the phone grants the debug user root access.
2. If the debug user does not have root privileges, one of several "root exploits" are tried to gain access.
Hopefully this is useful to someone to justify me trying to inflate my ego by looking knowledgeable!