Is rooting simply copying of SU to android OS?
I've been playing around w/ rooted phones then realize this question, is it simply copying SU binaries to android OS? looking for opening in OS where it can allow copying to system directories?
Related
Hey all,
I want to root my HTC magic but keep the stock firmware on it (mostly just to do wifi tethering). I've gotten as far as getting a su binary on the phone which claims to allow all apps to su (from http://android-dls.com/wiki/index.php?title=Magic_Root_Access ), and i can get root when i adb shell into the phone. However, android-wifi-tether still claims that it's "unable to start tethering", which i put down to needing some sort of bridge between the java apps and the su binary? Something that pops up for example, that dialogue in cyanogen about whether or not you want to grant root?
Any ideas?
hi, is it conceivably possible to root a fone with something like connect-bot. since it's local command-line shell has access to the directory tree above /mnt/sdcard , couldnt someone download the files needed for the root to the fone via the web browser and copy them to the correct locations with something like connect bot ?
i am new to android so i am wondering if there is a hole in my theory ?
thanks,
Depends on the phone really. Some need to flash files you normally can't while OS is still up. Some, perhaps?
There are root deployment applications which can be ran on some phones
Sent from my Verizon Supersonic using XDA App
thanks, i wonder if there is a roster of files that need to be updated/ replaced for rooting a 'samsung galaxy s2 epic 4g touch by sprint' (i hate that name).
the reason why i ask is because since android has a perfectly capable linux command-line and file browser then there is no need for windows. (i managed to install heimdall on fedora but i have a suspicion that the apb just runs the commands as if it was run directly on the fone).
Most of the phones need to connect into PC usb port... unfortunatelly
The way of rooting depends on which android version you are using. Some exploits allow applications to get root privilege; others, like psneuter(2.1) or zergRush(2.3.3) work restarting the ADBd with root privileges by making it believe it's running on a test(rooted) phone.
On the first case, I remember an application called "Universal Androot", which I used to root my first Android phone, SE Xperia X10 mini, when using Android 1.6. That app exploited some security error on the system, and gained root itself, so I rooted my phone without need of a computer. Also, for 2.3 API Level 9, I think GingerBreak has an android app which does the same.
For the second type(the most common), it's necessary to use a computer, as the only way to get the root privilege once exploited is via the ADB console "adb shell". The other processes will remain running with their original privileges.
^ thx for the explanation. kinda' like you cant upgrade the kernal of a running system.
hmm that would be nice if someone sort this out..
Like Z4?
HTC Thunderbolt running MIUI
sort of, but more related to android security: exploits like psneuter & zergRush attack ADBd to make it run as root. other exploits, like gingerbreak, give root privileges to the application which run the exploit(somehow equivalent to running "su" on the terminal)
Sent from my MK16i using XDA App
There are some ssh-servers for android, but I haven't found one, which includes a rsync-binary. Since the phone isn't rooted at the moment, I cannot copy a rsync-binary in the path of the ssh-server, what I normally do with a rooted phone. Any ideas how to use rsync with a linux-pc and an Android device without root?
Do you sync "Servers Ultimate (Pro)" could do the job? It looks a little bit "overkill" for me.
Hi there,
I am a newbie in Android development. I was wondering if there is any generic way to temporarily root any android devices? Or does rooting depends upon manufacturer\Android version? I was able to root(via zergRush exploit) a Samsung handset which runs on Android 2.2, however it failed on other devices running on different version of Android. I am working on Windows 7 32 bit machine.
Please suggest.
I yout have compatible phone, you can use Farmaroot, it's one click apk, no need to use computer or cable.
see http://forum.xda-developers.com/showthread.php?t=2130276
According to the links given, it seems that the exploits(rooting) are processor\manufacturer dependent. I am into forensics, so installation of apk on the devices is not an option. Is there any published list of exploits for various Android devices? Please suggest.
You can root any device because you can upload and execute a blob but it's only possible to do this in /data/local/tmp folder. You can upload the exploit and make it executable and then let it crack android. Then you can upload su and install it permanently. Most likely the system is read-only so need elevated privilege.
hi all, i know this is a developers' community but it's also a unique source of information on related matters so inevitably here i am (an end user)
system:
pc: windows 7 x64 pro os
phone: samsung gts-5300 (galaxy pocket), android os (gingerbread xxlj4), ('rooted' following these instructions)
question:
is there a way to be able to manipulate files in the phone through usb cable with a windows program (like a file manager)?
or at least can it be done using console commands?
note that by 'files' i mean android os files too
the issues:
'rooting' that phone does not actually grant root access to the system files but merely grants access to the su app and a glimpse of the system files
so yes we say it's 'rooted' but you can't actually pull any system file to a windows folder for example bcz you don't have the permissions required
i have installed numerous applications, on the pc and the phone, android sdk, android commander, qtadb, droid explorer, adb insecure, rom manager so i suppose that if someone gives me a set of steps i could hopefully quickly reply the problem that comes up on each step (obviously i don't think there is a quick solution to this, i know im an optimist...)
as far as i can understand, adb insecure should be the solution to this problem for similar devices where 'rooting' is not actually rooting, but im having the already mentioned and i suppose resolved issue of it causing the usb debugging mode to go off, and the problem is noone in the related thread actually mentions how that problem is overcome
thnx for your time