It seems a few application detect that the phone is rooted with the presence of su. Can someone be root on a device, using one of the available exploit, without having to push and use 'su'?
You need SU to do anything in root. May want to read the what is root threads, they are really informative and even may surprise you with some info you hadn't come across yet
MoPhoACTV Initiative
Actually one can have root access with out the superuser.apk there's a thread on the g2x section about it, it's in the app and theme section. I reccomed that one fully understanding the implications of not having SU before they remove it though.
Sent from my LG-P999 using xda premium
Related
Any idea when a sub forum will be created for this device?
Sent from my HERO200
I was just searching for this as well.
I am interested in knowing this information as well. I am interested in buying the phone but I want to see if any developers plan on supporting it.
Ditto
Sent from my HERO200 using XDA App
In the meantime, I tried running `rageagainstthecage-arm5.bin` that seems to be common between a few phones- Droid2, Optimus S, probably others.
It runs but does not give root- the shell disconnects as normal but the phone will no longer show up as a device from 'adb device' or 'adb shell' until you reboot it.
Edit: z4root does work to root it. Install Superuser, run z4root, it will say it rooted while it didn't really work. Run it again and Superuser will ask for root perms. Permanent root function in z4root does not work.
I sure am hoping they create one. I tweeted them also about adding a Shift 4G sub forum but no one replied as of yet.
Yes please. I'm excited to see what kind of a developer community this phone gets.
Ditto, also. As the proud new owner of a Shift I turn to XDA to help me void my warranty
Sent from my PG06100
also interested in this ^_^
I agree.
Please create a Evo Shift 4G forum.
Thanks.
One of you pull system for me with adb.
Code:
adb pull /system /system
Zip the folder at C:/path-to-sdk/tools/ named system, and upload it and post it in this thread and I'll start working on some custom roms. Picking up this phone when I get the money from donations.
I will do it right now if no one has it up before I get done
http://www.digglesworth.net/evoshift/system.7z
There is the system dump from my phone. I hope this helps out.
Z4root wouldn't work for me. It just acts like its loading.
Sent from my Htc Evo Shift using XDA App
Z4root worked before but now it starts and then the phone restarts and runs really slowly until I do a battery pull.
Sent from my PG06100
I had that happen the last time I ran it (two nights ago?). I think this was after I told z4root to attempt to permanently root it. I haven't run it since and all has been fine.
Advocating this device....
Every time I try to .sh the ratc file I get permission denied. Have already chmod 0755 both root and ratc. Can we also throw a sh file in data/temp, chmod, then run it from there? Maybe?
Ill try it and try pushing busybox to temp when I get home
Sent from my SPH-D700 using XDA App
bubby323 said:
..... Picking up this phone...:
Click to expand...
Click to collapse
very good news to read
I've created three new threads in the XDA general section in an attempt to streamline all Evo Shift discussions.
Root and Development
Issues
General Discussion
Hello.
I am looking for some information on temporary rooting devices.
My current goal is to gain access to a root adb shell without actually modifying the device permanently. Be able to run a app with elevated privileges that will not modify the phone/tablet in any way and then exit and be back to stock with no changes to the device.
I have been looking at different oneclick root scripts and it seems across many different devices rageagainstthecage-arm5.bin is ran to gain root.
Does it do permanent changes at that point or does it just get access to a root shell to install busybox and su for permanent root after reboot?
If it is just used to gain a root shell, then my goal is to use this within a script to gain root access, run my app with elevated privileges and once finished, close out with no lasting effects to the device. So I will have to do the same process again if needing to run the app again.
If someone can comment on the process of gaining a root shell on android devices I would apprecaite it. I'm sure there is not a simple bin that can be ran on all 2.1 or newer devices but from the research I been doing tonight, seems it has been used on HTC's and Samsungs to gain root.
However if rageagainstthecage-arm5.bin does more than just hack itself root temporarly then that will not work for my issue.
If there is a different area in XDA Forums I should be asking this, please refer me there.
Greatly apprecaite all help on this.
MobileMedic
Just root it. Doesnt cause damage
Sent from my Nexus S using XDA App
Perm root would be the direct and simple answer to my needs. However it is not what we are looking for. I basically need to be able to remote control a device for the user and help them correct any issues they are having. There is no simple option for doing this as no one has written a "Log Me In" type app for android. And any that are written are for rooted phones. However, Mary-Jo and JimBob who call for help won't have rooted devices only stock. I am not allowed to root the devices because technically its voiding the warranty (even a flash back to stock would be just fine of a fix, but End Users are not that smart sometimes)
So having a Temp root option to be able to run remote control app is my only solution I can see at this time.
Any help would be greatly appreciated.
Hmmm. I root phones for customers as its my job. I understand a bit more where ur ciming from now.
sent from my boosted nexus S
Hello All,
I am trying to figure out some way to manually start an app as root. It seems that apps which "require" root privileges are coded to elevate to root using su. However, what I would like to do is manually start *any* app as root - even an app that does not "require" root privileges. For anyone familiar with Linux or Unix, this would be similar to running 'su -c /usr/bin/myapp' (or less so, but also similar to running 'sudo /usr/bin/myapp'). In Windows this would be like using 'runas /user:Administrator myapp.exe'. Specifically, what I would like to do is open my text editor as root, so I can modify my hosts file. I needed to change this today, but was not near a computer, and therefore I could not use ADB. I finally gave up trying to figure it out and simply used Vi from the terminal, which is fine when using ADB, but quite difficult when actually using the phone. I could not find many questions (or answers) about doing this, and the few posts I could find, I get the impression that those who replied did not fully understand what the OP was asking. If my question does not seem clear, please let me know and I will try to rephrase it. I very much appreciate any insight. Thank you.
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
ankur.co.in said:
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Rooting is opening the operating system to be alerted.
Sent from my Rooted Gameboy
Rooting allows you to run special applications like SuperUser, SetCPU. Allows you to flash custom kernels and ROMs like cyanogen mod. Also you free up memory that extra apps use.. In easy language, you get full access to everything..
Sent from my GT-I9300 using xda premium
If you want the most complete, hands-on way to control what your phone is capable of...it's best to root it. Rooting gives you access to manipulate your phone in a way that carriers try to keep you from doing.
Sent from my SGSIII running some "Goodness" 4.0 (Team Nocturnal) using xda app-developers app
Allow you to backup & access apps/info/data etc that no root phone cant.
ankur.co.in said:
I know how to root devices but whenever someone ask me what is rooting i am not able to explain it :-\ anyone got idea about how to explain rooting
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Rooting is the act of gaining superuser access(root permissions) to the root(main files) of the device's operating systems, letting apps run at kernel level. Rooting allows for overclocking, however, in Jelly Bean, root is not required to overclock. Overclocking is the most frequently used root application. Root also lets you change system files.
Here is rooting for all you noobs
Basically every linux system has an administrator capable of making changes to the computer and access all the files that make the system up. On Mobile phones however, this is locked down for security/warranty reasons etc.
This is a great start, we know that the admin (root) access is there, we are just locked down from using it. So the point of rooting is not to install Super User, it is to trick the system into giving us adb shell as root and therefore allowing us to mount the /system partition as Read/Write (instead of read only).
That is what allows us to change the value of ro.secure in the kernel, which sets the flag that allows us a root shell, instead of a regular (non-privileged) shell. Then we push the SU binary and SU app to the system, which gives us choice as to what apps are allowed su rights and what is not. In other words, we don't need the SU app to obtain root access. It is just for data protection.
It sounds so simple, but it is not. Since the /system partitions cannot be mounted as read/write by default, and ro.secure=1, we cannot have a root shell and therefore not able to change ro.secure=0. Therefore, it is secure.
In order to gain the root shell we have to find an exploit that will trick the system. We use an exploit (hack, vulnerability) to trick the android OS into giving us a root shell in adb. For example on of them (in simple terms is...)
1. We kill adbd ***(this is the parent) It spawns a shell (adb) based on its rights*** keep this in mind.
2. When it adbd starts up, it must run as root. When its done, it will set its id back to a non root user
3. The program (SuperOneClick for ex) races adbd by spawning a process that tries to change its id at the same time (slightly first).
4. Since we are busy changing the id of our fake process, the kernel wont be able to change adbd since it is busy and therefore adbd continues to run as root.
5. Now we can spawn a root shell, because the root rights are passed from adbd to the shell, which is now root.
6. Sucess! Now lets set everything up!
This has been answered about as well as it can. For future reference, please try searching before posting as extremely basic questions like this do not warrant creating a thread. Closed.
I own a ZTE Z933, this device doesn't appear to be rooted or anything by anyone yet, so I've been working on doing it myself.
I've noticed some devices get root by using an update.zip containing the SU binary.
My question is:
- Should this update.zip method work for any device that can do this in recovery?
- Is there any major risk? (like incompatible zips or SU bin's, or should i just be able to use the one from AndroidSU?)
The update.zip method seems very easy and seems like it should work for a lot of devices, but yet there's very little information on it, so it makes me believe that I'm missing something.
Any info on this would be appreciated!
Many devices rely on this method nowadays, previously it was possible via applications such as z4root.
This method will root any device that has a "custom recovery" installed. If it has a stock recovery it won't work as you can only install manufacture signed .zips and .dats
Well sometimes but rarely, risks don't really come when pushing a few binaries to /system/bin and the root app to /system/app however the original app will be outdated.
You will need to flash or install new updates bins and the app itself when it gets update.
Anything else please let me know.
http://www.xda-developers.com/users-beware-zte-root-backdoor-found
I just picked up this phone too.
Seems like root acess is simply password controled..
Maybe ztex1609523?
Anyone wanna jam that into an installer?
Sent from my ghost using XDA Free mobile app