I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
premo15 said:
I did some searching and wasn't able to find an answer to this question, so if it's already out there please point me in the right direction and forget this ever happened...
My main question is what exactly the purpose of su/root binaries are. I've done a lot of reading in all the threads dealing with gaining root access, unlocking the bootloader, turning off NAND security (S-OFF) etc. and I feel like I have a pretty good basic understanding of how it all works, but the piece that's still missing for me is how exactly root access is gained. From what I've gathered, it's not enough to just install SuperSU since that app still requires root access to do it's job. Are the su binaries the key to actually obtaining su permissions? A lot of the root methods (if not all) involve flashing Evo4GLTERoot.zip (or Evo4GLTERoot2.zip) and it seems like that's what's actually giving root access...so what's in it that makes it possible? I see some recovery images, adb libraries and a SuperSU zip file. Is the latter the root-giver? If so, how is it different than downloading and installing chainfire's SuperSU apk from the market? Also, when you run the app, there is an option to update su binaries...how does that fit into the equation? I've read about people losing root access after doing this on other phones, which seems counter intuitive, so I'm kinda confused about the purpose of it.
Sorry for the long line of questions...any answers are greatly appreciated. I'm a developer (albeit on Windows, but I do have some Linux experience), so please don't pull any punches when it comes to technical details. Thanks in advance...
Click to expand...
Click to collapse
the top right there is a search box.. type your question in there and im sure u will find your answer
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
evo401 said:
the top right there is a search box.. type your question in there and im sure u will find your answer
Click to expand...
Click to collapse
I have searched...extensively But I haven't been able to find any detailed information regarding my questions. Lots of general information about flashing su packages, etc. but I'm interested in how it works from a developer's perspective. I've read conversations between developers regarding su binaries but because they already have a mutual understanding of what they're discussing, it tends to be a little over my head.
Did the basic info site I provided help you understand
/
Rxpert said:
Did the basic info site I provided help you understand
/
Click to expand...
Click to collapse
Yes, it's a good start, thank you. One thing that's still throwing me though is that I've read some posts from people using one of the automated methods that say it completed partially (i.e. the bootloader was unlocked) but didn't actually root. When they attempted to install SuperSU manually, it complains about not having root access. Is that because they only have the apk and not the binaries? Do the binaries not get installed at the same time? Is that what flashing the Evo4GLTERoot.zip does?
Sent from my EVO LTE
Rxpert said:
Just be helpful
This may help explain things OP:
http://androidsu.com/superuser/
Let me know if thats what you were looking for
Click to expand...
Click to collapse
Ok, went back and re-read a bunch of stuff with the understanding I gained from that article and it's starting to make sense now. Just one last question: when you install a custom "rooted" ROM, I assume that means that it has the su binaries and apk baked in. If that's the case, then really all you would need to do to gain root access is unlock the bootloader, flash a custom recovery and flash the rooted ROM. Is that correct?
Thanks again...
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
michael.stollaire said:
This puts su binaries in place that allow for setting the correct permissions in the system directory for APKs and apps that require r00t privileges to execute, such as Titanium Backup, and so forth.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
PS, your procedure for unlock, etc. is 100%correct, BTW.
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
Click to expand...
Click to collapse
Alright, I get it now! Thanks guys!
Mike, I'm already at my thanks limit today so I'll hit you up tomorrow. Out of curiosity, my limit seems kinda low (8)...does that increase as you gain seniority?
Yes, I believe u get infinite thanks capability, as ur XDA stature increases, although not entirely sure, to be honest.
A written thx is more than enough for me, BTW, and happy to help. Feel free to PM me with other inquiries, if u feel this will hasten ur getting answers and/or mitigation of outstanding issues.
Rock on!
Sent From My S-OFFed, R00ted, 100% Tricked-Out HTC Evo 4G LTE via XDA Premium!
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Rxpert said:
8 is the max for normal members, but if you use the tapatalk app you have an unlimited amount of thanks to give from within the app
Click to expand...
Click to collapse
Ah, good to know, "thanks" for the info...
Sent from my EVO LTE
Related
I used to work with WM 5 & 6 phones, had plenty of them and enjoyed them all until I discovered the HTC Magic. What a giant leap forward!! Especially when using Google Apps as we do. I am however a bit reluctant to root the magic as it doesn’t seem like a walk in the park. I really miss being able to backup SMS messages and all the other apps that only run on rooted devices.
So my question is if the HERO is a rooted device or not.
Does anybody have an answer to this question? I’m so tempted to preorder one
the answer to the question should be probably yes seing how people have the system dump files. so its just a matter of time
In the meantime, you can back up SMS and MMS with GBackup from Market - backs up to Gmail automatically - can also back up call log and pics...
Dayzz
Apologies for my ignorance but what does rooting the phone mean? I've just come from using a Windows mobile phone - which I have been using since the original SPV!
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Ofcourse it's not 'rooted' when you unpack it from the box.
Eventually I'll guess the Hero will be rooted, but when and how... we'll just have to wait.
dipje said:
Ofcourse it's not 'rooted' when you unpack it from the box.
Click to expand...
Click to collapse
Easy son... He asked, I provided.
barryallott said:
Easy son... He asked, I provided.
Click to expand...
Click to collapse
wasn't ment to be offensive in any way ...
barryallott said:
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Click to expand...
Click to collapse
But as in Unix /Linux you use an ordinary login for normal day to operations and su to to use root. You have to consciously change your privelidges which is safer!!
Simon
Lots of useful info on allsorts, including rooting and other hacks here
http://forum.xda-developers.com/showthread.php?t=542452
Daisy xx
[GUIDE] Fre3vo / Fre3dom Official Thread (Discontinued)
#teamwin is proud to announce the Fre3vo tool for the HTC EVO 3D and Sensation!
What is Fre3vo: Fre3vo is a temp-root acquiring tool, allowing users access to a root shell on their HTC EVO 3D and Sensation devices.
What is Fre3dom: Fre3dom was the name of the tool being developed to enable S-OFF on the EVO 3D and Sensation. This has been abandon since AlphaRevX has announced on twitter that they've had the devices open for weeks now.
Fre3vo can be downloaded here: http://tinyw.in/1lJ
Prereqs:
1. You must be able to push files via adb to your device.
2. You must know what a shell is.
Instructions:
1. Download the fre3vo zip
2. Unzip the fre3vo binary
3. Push the binary via 'adb push fre3vo /data/local/tmp'
4. Change the permissions via 'adb shell chmod 777 /data/local/tmp/fre3vo'
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt. (Some may get more messages, but it seems the Sensation buffers the stderr more than the EVO 3D)
run 'adb shell' and you should have a '#' prompt instead of '%'.
This is temporary root. A reboot will clobber it. There are many threads with scripts for doing what the community has dubbed "perma-temp root", which lets you run all your root-based apps.
[Reserved for future details]
[More reserved for future use]
Want to thank you and your team for all the effort and contributions you've given to this community.
I have updated the FAQ with the contents of last nights "meeting".
I will update this post with results once testing beings.
Thanks Again!
adb?
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
http://pastebin.com/wiQc8Mid
steal25 said:
just curious- does the posted instructions/script have anything to do with the install process? And if so how do we get adb to work? I've had no luck so far running adb on the 3D.
Maybe getting adb to work on a non-rooted phone can be explained so we can prepare for this when it drops. Thanks in advanced for any help.
Click to expand...
Click to collapse
Here's a good thread regarding ADB. Sorry if you already know all that. I've gotten it to work, but every command results in the "adb server is out of date. killing......" message. In the end, the command goes through, but it has to restart the sever every single time.
FWIW, I didn't take any updates.
This thread is closed. When this rom is ready to go, then it can be re-opened, until then I don't see any actual development ongoing in here.
agrabren - PM me when your ready to post the rom.
Thread has been re-opened, sorry for the delay I am out of town
its all about getting su to stick
Rooting information added to the first thread. Please keep this thread on topic and without trolling, flaming. Any flaming or trolling may warrant a ban as we do not tolerate such things here at XDA.
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
yeah it does
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
Double confirm from me.
spunks3 said:
So im on original firmware and this worked great.. can anyone confirm this working with the latest OTA?
Click to expand...
Click to collapse
rooted here.. all updates applied.. confirmed..
Will we learn how the exploit was achieved, possibly post-perm-root?
installed it successfully but for some reason when i run su in terminal it does not give me root, and none of my root apps do not work am i doing something wrong or am i not understanding something?
Doward said:
Will we learn how the exploit was achieved, possibly post-perm-root?
Click to expand...
Click to collapse
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Thank you this worked for me on latest OTA.
DWhite456 said:
I imagine yes. You wont fight much info here in this forum (not sure why there isnt a whole lot of info here but there is other places). Team Win did say they will eventually tell HTC about the exploit. I am sure once they do that it will not be an issue to tell anyone else.
Click to expand...
Click to collapse
#teamwin only tells HTC about intentional exploits. non intentional they dont:
20:28 <@joshua_> agrabren, By the way, traditionally, unrevoked's policy is to report to vendors holes that appear to be 'intentional' (see skyagent), but to package and protect vulnerabilities like that the best we can.
20:29 <@agrabren> This was a non-intentional hole.
20:29 <@joshua_> Yeah. Traditionally, unrevoked just packs and protects that sort of thing until someone finally reverses them.
20:30 <@joshua_> We'd love to be able to do the responsible disclosure thing, but this is an arms race...
20:30 <@zule> htc created the arms race, we just fight fair
How do I update my path environment variable?
NEver mind found it here. Have to copy contents of 'Platform tools" to 'tools' folder.
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Androidious said:
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Click to expand...
Click to collapse
I have. No reply. Prob busy.
Sorry bout the post location.
Sent from my HTC PH39100 using xda premium
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
gtkansan said:
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Click to expand...
Click to collapse
xHausx said:
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
Click to expand...
Click to collapse
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
joeykrim said:
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
Click to expand...
Click to collapse
All apreciated. They did use a similar method, http://forum.xda-developers.com/showthread.php?t=1345620
[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows] to get stick temp root. Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board. I would think with the huge board level similarities between the raider/vivid and all the sensations that someone would have some experience to lend an idea or three ... Any help would be REALLY Apreciated! Thanks everyone.
Sent from my HTC PH39100 using xda premium
gtkansan said:
Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board.
Click to expand...
Click to collapse
android exploits take a lot of work to find/test/develop/release. bootloader exploits are generally more time/labor intensive to find/test/develop/release as bootloader code is closed source compared with android code that is open sourced. in addition, bootloaders can be very specific to only a few devices, where as android is running on many devices.
bootloaders have to be reversed engineered which is a skill set not many people have.
after all that negative news, perhaps somebody with the skill set will take the time to examine this device. perhaps a previous method will work or hasn't been patched!
after reading the thread linked above, seems everybody is on the right track. hope the extra information helps. good luck!
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
Just wondering, but with JCase's new moto X exploit being released, could this be used to root the HDX? From what I understand it should work on any android version that supports ASEC.
This may be a possibility... We'll have to wait and see...
Sent from my Nexus 4
S_transform said:
Just wondering, but with JCase's new moto X exploit being released, could this be used to root the HDX? From what I understand it should work on any android version that supports ASEC.
Click to expand...
Click to collapse
Jcase is a good dude. If anyone hasn't already, a polite & to the point PM should be sent to him asking just that. That is exactly what I did that led to the first root.
I personally am still rooted, I don't know exactly what I did differently than everyone else, besides installing safestrap a second time on the rom slot I use, but I have not blocked anything, not deleted or renamed any files, nothing, but updates come & the Kernel & BL fail to flash & it gets stuck in the Bootloader screen. I reboot, still have access to SS & am still rooted every time. Every single update has downloaded & tried to install & every single one has failed.
ASEC...
Hmmmm.... I will have to go through the KF HDX source, but if this exploit exists & it may very well considering it wasn't even fixed by Google until 4.4.2, the ASEC exploit should work just fine on the HDX.
Some interesting info here: http://blog.cassidiancybersecurity.com/post/2014/06/Android-4.4.3,-or-fixing-an-old-local-root
Basically the way ASEC exploit works, you can redirect a partition mount to ANYTHING, as long as it is an existing directory & there is an existing symbolic link to the directory. Interesting, even if it is a very old exploit, & very possibly something much easier to accomplish root with than some of the things I have played with, including SED...
---------- Post added at 03:13 PM ---------- Previous post was at 02:50 PM ----------
Hey, guys, I made the suggestion to contact jcase again a few days ago. PLEASE do NOT contact him regarding exploits right now. He is taking a break from this stuff & I hadn't bothered to check with him, or to check his current status.
If I feel like I am onto something, or if anyone else does, please let me know & I can get the idea or possible exploit to someone else. Jcase has done a lot for the XDA community, so give him his well deserved break.