Android Version:-2.3.5
Kernel Ver:-2.6.35.7-I9100XWKJ1-CL647431 [email protected] #2
Doesnt have SU or recovery so i dont think it is but the ROOT portion of the Kernel version is throwing me here.
Does anyone know?
TheBlueRaja said:
Android Version:-2.3.5
Kernel Ver:-2.6.35.7-I9100XWKJ1-CL647431 [email protected] #2
Doesnt have SU or recovery so i dont think it is but the ROOT portion of the Kernel version is throwing me here.
Does anyone know?
Click to expand...
Click to collapse
Install the SuperSU app or the SUperUser app from the Android Play Store/ else, install any app that requires root.
once you run the app the app will request for root permissions, if it works, then you have root. if not, you will need to root the phone.
the ROOT portion in the kernel is almost usually there.. even if the kernel is not rooted.
Thanks for the quick reply, it doesnt look like it is, SU complains and adaway doesnt install.
Samsung actually compile their kernels as root (!). The root part of the kernel name is just the username it was compiled under.
Sent from my GT-I9100 using XDA
maybe install voltagecontrol via playstore and look if u can change ur voltages and if the programs ask u to grant root rights, if not then its unrooted!
Just read the FAQS and GUIDES
Install CWM and root kernel.
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
The Reverend is right on the money (Sorry Rev, out of thanks. Will hit you up tomorrow).
That '[email protected]' thing is in every kernel under settings/about phone, and as the Rev said is simply the name of the user account/machine that the kernel was compiled on.
It has nothing whatsoever to do with root.
Related
Alright, so I now have a new Samsung Galaxy S2 from Bell (GT-I9100M) and I want to play around with it. However, I'm pretty anal about getting the phone back to it's original state, just in case I'd like to.
I want to be able to backup everything from the phone in its current state so that I can restore it.
I'm currently getting the source for android and I'll be compiling zergrush from source in order to gain root access to the phone.
1st: Can this be undone?
2nd: Once you root your phone, does everything run as root? (that would be aweful)
3rd: Is root + Rom Manager + Titanium Backup all I really need to install custom roms easily? Or am I going to have to use Heimdall and such (I'm on Linux so no Odin for me unless I pop up a VM).
Correct my assumptions if I'm wrong:
It seems like zergrush exploits a bug that will give /data/local/tmp/sh uid of root. Is that how root access works? just a copy of the shell with root uid in that path. So if I delete this file, it unroots my phone?
If I zergrush my phone, gain access, use titanium backup to backup everything to the SD card or on my PC then I can use rom manager to get cyanogenmod and flash it straight through the phone's app. In case I want to revert to my good old stock rom and everything unrooted, I use rom manager to reflash the backup I made and then how do I revert what was done by zergrush?
Cheers!
Lewis
Is anyone familiar with what I'm asking?
as far i know zergrush was till 2.3.4 doesnt wored on 2.3.5 and 2.3.6 so not sure if it works on ICS.
try to search if the stock firmware is available for your phone model, unless you doesnt care for that in that case i assume ur phone is just a i9100 so you can flash a stock rom later using odin
now to gain root simplest method is http://forum.xda-developers.com/showthread.php?t=1103399
My phone is running 2.3.3 so zergrush should work.
As for the stock firmware, I'd want to extract it from my phone so that I get the exact same version when I revert.
the CF root method isn't suitable for me because I can't backup my kernel before flashing this.
I also can't use Odin as I am running linux. I can use a VM or Heimdall but it seems like zergrush is the best method for my situation. I already have the android sdk installed. My current issue is compiling zergrush from source... my environment doesn't seem to be completely setup correctly.
Why are you compiling it yourself? You can get a binary from the source, http://forum.xda-developers.com/showthread.php?t=1296916
There was a similar request a while back for what you're trying to accomplish, see http://forum.xda-developers.com/showthread.php?t=1409484
I compiled from source cause I like to know exactly what I'm running on the phone . Not such an issue when it's in user-space but when it comes to granting root access to anything...
Which is why I'm asking about what happens after rooting the phone. I suppose any app will have root access unrestricted... How does Cyanogenmod works for that? Can I explicitly grand root to applications, like on a linux desktop where you put your password when an app needs root.
So, can I undo zergrush's root by just deleting /data/local/tmp/sh ? (or just the setuid?)
ldiamond2 said:
I compiled from source cause I like to know exactly what I'm running on the phone .
Click to expand...
Click to collapse
So you've presumably peer-reviewed their code prior to compiling?
ldiamond2 said:
I suppose any app will have root access unrestricted... How does Cyanogenmod works for that? Can I explicitly grand root to applications, like on a linux desktop where you put your password when an app needs root.
Click to expand...
Click to collapse
There are currently two choices for managing root requests, SuperSU, and Superuser.
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
https://play.google.com/store/apps/details?id=com.noshufou.android.su
AFAIK, neither of which publish their code publicly - so considering your earlier point, you won't be wanting them on your phone either.
oinkylicious said:
So you've presumably peer-reviewed their code prior to compiling?
Click to expand...
Click to collapse
Yep for sure.
oinkylicious said:
There are currently two choices for managing root requests, SuperSU, and Superuser.
Click to expand...
Click to collapse
At least having a single app that I can't see the code is safer than a bunch of them... I'll give it a shot.
But doesn't cyanogen mod offer superuser access management?
Found the source code for superuser
https://github.com/ChainsDD/Superuser
So there are two populair methods of rooting the galaxy s3:
- The Samsung galaxy s3 toolkit
- Chainfire's CF-ROOT
My questions are as follows:
What are the technical differences between the two rooting methods?
Do the methods have any drawbacks? (cf-root for example is incompatible with rommanager)
disclaimer:
I am not interested in what you think is the best method, I want to know the technical differences between the two methods used.
I know that the toolkit itself is not a rooting method, it does however include 4 different methods you can use, I am referring to those.
The toolkit uses cfroot I think. Not sure if it's as up to date as the latest cfroot via Odin. They both work well enough. There is no other method I know of. And I haven't had any drawbacks.
That's all I can say really
Sent from my GT-I9300 using xda premium
Also The toolkit uses Odin too. It has other options and clear instructions. Drivers. Modems etc so this would be the best option for an casual user.
Latest cfroot via Odin is probably your best option if u know what your doing
But it's up to you mate, it doesn't really need analyzing so deeply...
Sent from my GT-I9300 using xda premium
slking1989 said:
But it's up to you mate, it doesn't really need analyzing so deeply...
Click to expand...
Click to collapse
Well it is personal but I like to know or at least have a general idea of what I am doing to my phone. So yes it does
Tnx for the reply
Anyone else who can give me some more insight?
Unfortunately I don't have an answer for you, but I also am interested in the answer to your question..
I think certain methods of rooting use SuperSU (is this the CF one?) and then another method uses Superuser. I think both install busybox (that seems to be the same?)
In my experience, using the Superuser.apk app was faster than SuperSU..
I don't even have the Busybox app installed (but I am sure my phone has busybox, so this also confuses me??)
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
gee2012 said:
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
Click to expand...
Click to collapse
Yes go with the CFroot if u just want to root ur phone.
Sent from my GT-I9300 using Tapatalk 2
'K, I'll bite. I'm not going to give an overall recommendation - at the end of day, they both install an APK and put a new binary in /system/xbin.
Note: I used CF-Root to root my phone. When I talk about how the the toolkit does what it does, I'm basing my words on this image. I've seen the things in that image before, even though I haven't used the toolkit. This also means that my toolkit observations may not be entirely accurate but it's a batch script, anyway; you can just read through it and find out how it works. I'm also primarily a Windows user, but I used to use GNU/Linux quite a bit to write programs for a phone that I once had.
Rooting is, when broken down, the installation of a "su" binary installed to /system/xbin, that is owned by root and carries the setuid flag. This flag is important as the Linux kernel will then run the process whenever it's invoked as the person who owns it, root. This process can then, in turn, start other programs and they inherit the user ID (something like this - I'm taking my time reading TLPI...) so they are then running as root. There's also a "manager" app (Superuser or SuperSU) that will be installed; this app is talked to by the su binary (through the Android Binder AFAIK, though Superuser's source is available so if you really wanted to find out you could read that) to see, for example, if the program that is invoking "su" is allowed to do so. CF-Root installs the SuperSU apk to /system/app, which means that it survives factory resets. The toolkit, from a quick look at the Superuser ZIP in its folder and its batch file, also installs the Superuser apk to /system/app. When sideloading apps or installing from the Google Play Store, they usually get installed to /data/app.
Not all "su" implementations for Android need a manager app, I've seen implementations where su does not place restrictions on who is allowed to run it; uid=0 for everyone without discrimination! (Yes, that also includes you, Super Smilies Pack 3000 with boob smilies) Thankfully, neither the toolkit nor CF-Root do this. I lie a little. Superuser's su binary will automatically reject any request to become root if the Superuser.apk is not installed but SuperSU's su binary will automatically accept all requests to become root if the SuperSU apk is not installed. Personally, I prefer SuperSU's behaviour as there have been too many times with my old phones where I'd have to sign into Google Play after wiping /data just to install the Superuser APK when all I wanted was to run a simple command.
ext* filesystems along with other *NIX filesystems have the concept of file permissions, a concept shared by other *NIX filesystems. In order to actually place this su binary owned by root into a folder owned by root, you need to be root. (Actually, the folder is also owned by the shell group so a user which is a member of that group could do it too, but they wouldn't be able to set the all-important setuid flag as they're not the user root [perhaps a member of group root could do it but I don't know]) Usually, exploits in other programs running/can run as root or in the kernel are searched for so that you can temporarily root in order to install the su binary correctly. The GSIII (with the exception of Verizon's) has an unlocked bootloader, though, so programmers don't need to search for any of these: it's able to flash unofficial, unsigned recoveries and kernels.
CF-Root does this:
* it flashes a new CWM-based recovery in the recovery partition of the phone. If you've seen the stock Android recovery, you'll know that it just can't match the features of CWM. The important thing about CWM is that it runs as root, just like the stock recovery, but it also lets you place any file anywhere on the phone without requiring that the the ZIP file containing the files are not signed with a Samsung private key. Remember what I said about file permissions?
* there's also a param.bin file. I don't know anything about this file, but I suspect it's flashed to get the phone to boot up into recovery mode the next time it's started so that CWM runs before anything else
* it also flashes the cache partition (I'm not sure whether it overwrites or appends as I don't know how [and probably never will] know how ODIN works with two ZIP files: SuperSU, which contains the su binary, the SuperSU apk and a script that is run by CWM to set the required permissions on the su binary among other things, and the CWM app which lets you tell the recovery what actions you want it to perform in Android without having to navigate through the awkward interface of CWM itself. While I don't know how to do this myself, CWM recovery can be told to automatically run commands from an external source. I'm not talking about random websites on the Internet, but (I think) through files that have to be placed somewhere by root. This is what apps like the CWM app and ROM Manager do. This is also what CF-Root does to tell the recovery that the next time it's booted that it should install both the CWM ZIP and SuperSU ZIP. That's it in the case of CF-Root: you now have a phone with the two files required for root access, and a CWM recovery and an app to control it.
The toolkit:
(I only talk about the "insecure boot" options as I imagine the recovery option does something similar to the above and do remember that I haven't used the toolkit to root my phone so some assumptions are made. I also assume you know what ADB is as I won't be explaining it)
* it gets you to flash a kernel image with a patched adbd that runs as root, so adb on your computer, in turn, is able to place files anywhere on the phone's /. File permissions make it so you can't just place adbd in its expected place (/sbin) as any user and /sbin is also mounted on a ramdisk part of the flashable kernel image so it would be replaced on the next reboot, anyway.
* When the phone is running again with the new kernel, it then tells adb (now running as root) to push the Superuser APK and the su binary into their rightful place and sets the correct permisions on the su binary so that it runs as root
* if you've told it to install busybox, busybox is pushed and a bunch of symlinks for all the applets that BusyBox supports are set up
CF-Root installs, naturally, Chainfire's SuperSu whereas the toolkit installs Superuser. I much prefer SuperSU (and I bought a pro license for Superuser long before I did for SuperSu). Superuser's interface is much better than SuperSU's and it's also open-source but I find that SuperSU works much quicker for me (Root Explorer actually popped up a message on my sister's freshly-flashed Xperia Arc S saying that Superuser can be slow if Superuser hasn't granted it root access quick enough - I've never encountered that on my Huawei U8800pro with SuperSU which has pretty much the same specs as the Xperia) and it can also log the commands an app is running as root if you're suspicious of an application.
You'll notice that ADB still runs as a normal user with CF-Root. You can use Chainfire's adbd Insecure app which will replace /sbin/adbd everytime the phone is started with his patched adbd which always runs as root, or you can just flash one of the many kernels available that already include a patched /sbin/adbd.
CF-Root also does not install BusyBox. You can grab one of the installers from the Play Store but what I do personally is kang a CM9 nightly build for the I9300 and take the META-INF folder and the /system/xbin/busybox binary and strip out most of the lines in the update-script leaving only the lines that mount, extract and create the symlinks for busybox and place the result in a new ZIP which is then flashed with CWM.
Your "cf-root for example is incompatible with rommanager" gripe is easily solved - just flash another recovery. CF-Root just packages a CWM Recovery, an app to control CWM and SuperSU. CF-Root itself is not a resident component, but the recovery and SuperSU etc. are, if that makes sense.
qwerty12 said:
A long story with a lot of interesting and valuable information
Click to expand...
Click to collapse
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
The only advantage i can see to using toolkit is it will get updated quicker and it has loads of other options. If you just want to Root and flash a Rom cf root is way to go
Sent from my GT-I9300 using xda app-developers app
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
Click to expand...
Click to collapse
Glad it helped
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Yeah, HTC's locked bootloaders and the S-ON/S-OFF rubbish is one of the reasons I decided to skip the One X and go for the Galaxy S3.
creesch said:
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Its fair to say that unlike many people on this forum you did your research. Searched.. and asked a valid question. Whereas the majority of people just ask questions without being bothered to figure it out themselves. So thanks. Over analyzing? Maybe a little... but its better than flashing any old thing like many other have done and continue to do. Big thanks to qwerty who has filled me in on some useful info also.
Sent from my GT-I9300 using xda premium
You should have thanked him tho maaan
Sent from my GT-I9300 using xda premium
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
slaphead20 said:
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Alright well since it was only the touch aspect that made me consider it i'll leave it just like it is
Hey guys
Hey guys i have the internationa galaxy s3 running 4.1.2, i haven't done anything to my phone yet and im about to root it is the boot loader unlcoked and if not how do i unlock it :good:, could someone please help me:crying::crying: and give me clear instructions and links please :fingers-crossed: thanks you so much,
BTw i know this is the wrong thread but i cant find the right one, thanks alot guys
regards nick
Hi to the community...
I need root acces for my new POV_TAB-p1325 !
All my attemps to get root failed!
this tablet use RKBatchTool.exe when usb connected to load *.img firmware updates! (for exemple: TAB-P1325_V1.0_20140503.img,which is the latest firmware update)
maybe the solution could be creating an unsecured *.img including recovery mode, superuser etc ?!
could anyone help to make such *.img file ?
best regards
alansan2013
the tab-p1325 tablet run under JB 4.1.1
pov root check
Hi, sorry but did you check if you already had root access before trying with tools? Recently most of these are Chinese clones and come with root privileges out of the box.
vsanto88 said:
Hi, sorry but did you check if you already had root access before trying with tools? Recently most of these are Chinese clones and come with root privileges out of the box.
Click to expand...
Click to collapse
Hi,
I'm sure it's not rooted because when I run titaniumbackup, it says that it have no root access !
regards
alansan2013 said:
Hi,
I'm sure it's not rooted because when I run titaniumbackup, it says that it have no root access !
regards
Click to expand...
Click to collapse
Just exhausting all possibilities here so bear wit me. . Try installing super Su or other Su binaries from the play store. Install a root checker app from the play store as well and then try it.
vsanto88 said:
Just exhausting all possibilities here so bear wit me. . Try installing super Su or other Su binaries from the play store. Install a root checker app from the play store as well and then try it.
Click to expand...
Click to collapse
all done, but no pre-root !
Hi.
I know this is a realy old topic, but still on position 1 @ googlesearch for "POV_TAB-P1325 root".
My POV_TAB-P1325 is now rooted. Maybe it works with other Devices which have a "RK30 Device" driver in the Windows Device Manager.
Here is the link:
www(dot)slatedroid(dot)com(slash)topic(slash)88850-rooting-rk3188-tablets(slash)
Happy rooting
P.S. Remove (dot) and (slash) with the real signs in the link cause of "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Hi guys, this is my first thread on xda btw
you see my j320az (cricket)
Baseband version: J320AZTUS3AQG1
Android version: 6.0.1
device status: custom
Security enhancements for android: permissive
I tired rooting my device using an img.tar file that set selinux to permissive and tried to root with no success but now when I try apps to root my deivce like kingoroot,
it says that I'm already rooted, but when I used multiple root checkers from the play store, most of them say I do not have root
But then when I used a Super SU app from the playstore (Just search up "SuperSU" without quotes and it should come up as the top one that has a green icon with the hashtag sign) says that my su binary is occupied, but when I try to fix , it says I have to use a custom recovery to flash the latest version of an su binary update .img.tar file and it gives a file for the j7elte
link to that: bit.ly/2qz6lqb
unfortunately I don't know of any custom recoveries for my device, can anyone help me out? I would really appreciate
I can try and give more info as needed, feel free to contact me, just tell me some ways you can communicate with me
Hi,
I need to root a Zebra TC56 to install some other apps that require rooted Android. There is very little information in the way of rooting the Zebra TC56. I 'm pretty set on using Chainfire's superSU, but I cannot find any information on whether it will work on this hardware. Does anyone know if the superSU works on this device with Android 6? If not, is there another Root Tool that will work.
Any advice appreciated.
THANK YOU!
VK
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
jwoegerbauer said:
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
Click to expand...
Click to collapse
BusyBox installed fine.
SuperSU will not install all the way. When I select to root, it says root not detected and then, "How to Root", which launches my browser to a site that no longer exists.
Now what?
Thank You!
edit: Still stuck at this point. I read about TWRP, KingoRoot and some other random apps. I cannot brick this touch computer; it is $1600; that would be a very expensive brick. :crying:
So, I have no idea if I am right, but maybe I need to open the terminal emulator and "su" install the SuperSU apk. But I have no idea and I don't want to experiment. Hopefully, someone can help me.
@vidarr_kerr
Don't confuse things:
SU is the super user who unrestrictedly can perform any operation on Android OS. As soon as SU got installed Android is rooted! Again: BusyBox you successfully installed contains the su applet.
SuperSU is merely a root-manager app: it maintains a database where is stored what app can act as super user. SuperSU app doesn't grant super user rights.
BTW:
TWRP has nothing to do with rooting device's Android, as this is also true with Magisk.
The device is still not rooted after the "BusyBox Installer (No Root)", from your link, was installed.
I installed BusyBox, I followed the directions to then copy a command, then open a terminal, paste the command in and hit enter, then nothing happened. SuperSU was not installed with it.
So, as you told me, I then installed the latest SuperSU APK from your link. It says it installed, but when I run it, it says root not detected and then has a link named, "How to Root", which launches my browser to a site that no longer exists.
I followed what you said. Where did I go wrong?
Thank You!
You didn't get it. Sorry to say this.
jwoegerbauer said:
You didn't get it. Sorry to say this.
Click to expand...
Click to collapse
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
(That should have tipped me off right away you had no clue, but I thought maybe you knew something.
So, you gave me the links for both of those files and it doesn't work.
I don't think you have any idea what you are doing; and shouldn't be explaining things you do not understand.
The "no root" BusyBox, does not include SuperSU.
If it did, why did you give me the link for the separate SuperSU file?
All the "no root" BB did was install a terminal emulator (with no su abilities).
The SuperSU didn't install, because the Android is NOT rooted.
If the Android WAS rooted, SuperSU would run and allow me to grant su privilges to the apps that require it to work.
You basically just wasted my time.
I would have just said "thank you" and moved on, but you are rude.
You don't know what you are talking about either.
Hopefully, this will help others, to not do what you say to do.
vidarr_kerr said:
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
Click to expand...
Click to collapse
You're right: BusyBox (No Root) doesn't come with SU-binary. Wasn't aware of this. I misinterpreted APK's title. Pitty.
ERRARE HUMANUM EST ( To err is human ).
Installing BusyBox containing SU-binary requires your device's bootloader got unlocked before, because Android's /system partition gets modified. Hence manage to unlock device's bootloader as 1st thing of all things. Good luck.
DL BusyBox latest: https://github.com/meefik/busybox/releases/download/1.31.1/busybox-1.31.1-46.apk
My last 2 cents here: SuperSU and SU binary are totally different things.