Develop Bugs

Are su/sudo available in android, can root be performed without rom flash?

Hello guys, seem like I will be moving to this part of xda in a couple of weeks
I have several questions though, mostly regarding roms and rooting. I have used linux for sometime and from what I understand su/sudo/gksu/gksudo etc. are not available in android? I mean I cannot gain root access in the same way as on the desktop. And if I root the device it will not lose warranty, as I can unroot it later on similar to SPL/HardSPL in winmo. The other question is, I think I am going to be OK with the stock rom, as the desire is some pretty fast hardware, so can I root it without installing rooted rom, again as HardSPL in winmo. I will probably need the root access for some applications, like task manager, otherwise I will probably only use the phone, browser, mp3, social stuff, gps, email, videos like I did in the past.
I am sorry if these questions were asked before, I read the tutorials in the first post, however things are still not quite clear for me

You don't have to install a custom ROM if you use unrevoked for root, it just adds the superuser app to your current ROM. However it will flash the recovery, so it voids your warranty anyway. There is no way to avoid this.
No idea about su/sudo though, I know nothing about linux

Well,I kinda have the same questions...First off,there is the su command in Android which is equal to the sudo command in Ubuntu etc.To give an example,I was trying out the ezHero rom on my Hero the other day and jit was enabled with this process:in terminal emulator you type in su,and then it asks for superuser permissions(probably only available through root?) and then you type jit-on and some other things happen that don't really matter here.I believe I answered half your question.Now,if root can be achieved through terminal...I don't think so!It's above my head though...

Thanks guys, that cleared up a lot
About this recovery, I guess if I can unroot and flash "stock recovery" if there is such a thing, it will not be a problem, is this the case? If I can't maybe I should buy a used device instead of a new one.
About the su/sudo, I have used mostly Ubuntu, and in the users menu I usually had 2 users - admin and root, once I set up a root password. Then I used the admin user and if I needed root access for something I did it with su or sudo + <command>, requiring password, or if it was software launcher requiring root access with a path gksudo + <regular parameters/command> in the launcher properties. For example, as far as I know you cannot change attributes like readable/writeable or edit files which are not personally belonging to your user without root access . It is a really neat and simple feature on the desktop and I am puzzled as to why they removed it from the stock rom. I didn't include this in the original post so that it is not too confusing.
Anyway thanks guys, having been with winmo for the last few years, I will finally give android a go and see if it works for me

Yeah it is relatively easy to flash to complete stock ROM and recovery. There's a guide somewhere in the developer board.

Invisible Elf said:
You don't have to install a custom ROM if you use unrevoked for root, it just adds the superuser app to your current ROM. However it will flash the recovery, so it voids your warranty anyway. There is no way to avoid this.
Click to expand...
Click to collapse
No. Just no.
There's nothing in the warranty agreement to suggest that (there is a line that confirms that in the N1 agreement, though), and countless people have sent their rooted Desires back to HTC for repairs, and they've all been repaired. They just won't repair it if the ROM you flashed broke some hardware (ie overheated the LED and made it short-circuit).

Thanks guys, then I'll get a new device, great

[Q] Unroot EVO and still keep a custom rom?

Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
The image that is used in unrooting is a stock ROM. What I want to do is setup my phone - the way I want it with Mikfroyo - with all the tweaks etc and then "just do the unrooting part". If that makes any sense - I don't need any superuser permissions etc.
Long story short - can a phone be unrooted with a custom ROM instead of a stock ROM?

im pretty sure this is impossible dude, sorry, just leave it all rooted, whats the problem

I know you can't unroot and keep a custom ROM but I wonder if there is a way to hide the fact that you're rooted from the app. What kind of message pops up when you install it?
Sent from my PC36100 using XDA App

It just says that Good cannot run on a rooted phone and just locks the app - I have to call IT to get an unlock code using the device ID that is displayed in Good's pop-up message.

It has to be checking for something specific and I bet there is a way to fudge it but unfortunately that's outside my realm of understanding. I would ask one of the devs here about it.

What permissions does the App request when you install? It could just check for SuperUser

SSjon said:
What permissions does the App request when you install? If could just check for SuperUser
Click to expand...
Click to collapse
I which case you could either delete superuser or use it to block the app... perhaps?

I am sure its more complicated than that - if they are touting themselves as a replacement for blackberry security for iPhones and Android - I seriously doubt a simple fudging of the superuser permissions will deceive it. Also, I'd like to comply with my company's requirements for using an Android phone so I don't get into trouble.
So from what I understand - you cannot have a custom ROM on an unrooted phone. Thanks so much guys - I'll just have to learn to live with the bloated stockware and manual restores arghh......

It's not possible.... to unroot, you'd have to RUU, which returns the phone back to stock. And then, you'd have no way of flashing a custom rom unless you rooted again

ok this is one thing that I am starting to not understand here...
so many people when they answer - say "yes" it can be done or "no" it can not be done...
...ummm where is the why? It would be very informative to know such things or if someone has even tried said thing before.
like why can't you just run a ROM or other flash file from renaming the file and letting the stock loader do the flashing? ......answer: because the stock loader does a file signature check - see? that makes sense and answers the why. it also helps users to retain the information as well as understand it.
I would love to know why the OP can't just run the unrevoked s-on tool from here http://unrevoked.com/rootwiki/doku.php/public/forever#custom_splash (in the FAQ section) without removing his custom ROM and just make sure he doesn't use any apps that need the su access. sounds like it should work? has someone done this and found that it does not work? flashing back to s-on should just prevent flashing to any other ROM's I would think from everything I have read in this forum.
or once s-on is back does it also check the current ROM on the phone and would cause some issues? would be great information to know. because if the security only checks file signatures of flies to be flashed and not the current ROM it seems like the OP could do what he is wanting to.
well, just thought I would ask to see if I could gain some more understanding as to the mechanics of everything

It would be good to know if this works with Good for Enterprise. I am stuck on an SGS 2.1 with Telstra and want a non stock ROM but really need to use Good.

ushkand said:
Is this possible? I know most unroot the phone to take it in for service/exchange etc but my situation is different. I have to use Good for Enterprise to access my company's email and as you may know, Good does not allow rooted phones. So, I have no choice but to unroot my Evo.
Click to expand...
Click to collapse
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html

bkrodgers said:
I did not know that, and that SUCKS. My company's piloting Good now, and I was really looking forward to it. This just infuriates me. Mobile device makers are getting away with things that desktop/laptop makers never dreamed of trying. We shouldn't even NEED to "root" a phone. Imagine if you needed to hack your Windows machine in order to get the admin password and be able to install whatever you want. Now yes, I get that companies often do add those restrictions on their devices, and that they need to protect their data. Allowing access to company data on a personal device might make it a little more of a gray area, but it still blows. Good should be able to develop a system that can be secure, even if you have root access.
Here's a thread I just found. It sounds like you can just delete su and the superuser.apk. I think you can keep the custom rom, but you probably wouldn't be able to run anything that needs root, like Wireless Tether, Titanium Backup, or whatever. But you could probably have a flashable zip to re-add them when you need them. Or maybe one of the temp root methods would work. But it makes me furious that this is needed.
http://androidforums.com/droid-x-all-things-root/207397-good-enterprise.html
Click to expand...
Click to collapse
My thoughts exactly

Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
Thanks for the information. What is the ROM that you are using?

bkrodgers said:
Or maybe one of the temp root methods would work.
Click to expand...
Click to collapse
are there still temp root methods that work on the EVO?

I am using Mikfroyo 4.5.

Just came across this thread and was seeing if your GFE was still working? I have a DX and put a custom ROM and could not get it to work. I'm waiting for my new PIN and have removed SU to see if it works.

ushkand said:
Update- I was able to get Good running finally on a custom rom - However, I had to forgo my superuser capabilities. I just renamed both the Su and Superuser.apk and then was able to run Good without any issues. I can easily restore Superuser access by adb when I need to. The good thing is that with the recovery being there, I can still flash updates without needing superuser access.
Thank you all for your help.
Click to expand...
Click to collapse
I rooted my HTC Salsa to install apps2sd which is great, but what commands do i have to run and where to be able to rename su.apk ?
Thanks,
Mike

Difference between rooting and unlocking bootloader

I just want to know the difference
Sent from my Wildfire S using XDA

There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA

SanderTheNinja said:
There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading

with an unlocked bootloader, then you are able to root your phone and install custom roms and overclock and root stuff.
an unlocked bootloader is something you must do before having full access to your phone

scott_doyland said:
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading
Click to expand...
Click to collapse
I mean, you can only get root if you unlock your bootloader.
Sent from my Wildfire S using XDA

Root
Rooting a device is a method to gain full access to the operating system. With root you can do all the administrative stuff, write to locations normally restricted to the system and customize your device deeper.
Root enhances your privileges and you are able to change almost anything inside of your rom.
The rooting, however, affects ONLY your operating system (Android)
Unlocked Bootloader
In most devices, the Bootloader is the instance that calls the operating system (Android) and manages direct access to the device's partitions. Having an unlocked bootloader enables you to flash custom roms, custom kernels, recoveries and so on.
Bootloader and Rooting Teamplay
Often it is the case, and so, too in our devices, that a locked bootloader also locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader. Rooting needs write access to the system partition (for storing the superuser binary and the superuser app)
Without unlocked bootloader, only a temporary half-root can be achieved.

Thanks alot guys
Sent from my Wildfire S using XDA

How to unlock bootloader ,but the way that I can lock it again

prdonja said:
How to unlock bootloader ,but the way that I can lock it again
Click to expand...
Click to collapse
Do some research. There are hundreds of posts on this topic.

scott_doyland said:
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading
Click to expand...
Click to collapse
19 months after the question was asked, i just happened to be wanting to answer the same question for myself, so I searched and found this thread...
I am happy he asked the question, as it was the first answer I saw in google search... so maybe he could also have done a search 19 months ago, but his question was useful to me, and your response seemed rude and unnecessary. You never know who may benefit from a little generosity.
Mark.

scott_doyland said:
Do some research. There are hundreds of posts on this topic.
Click to expand...
Click to collapse
I know that you're not rude (even though you sounded so). You replied what was correct and appropriate.
But my research for the question in question (pun unintended) on google pointed me straight to this very thread.
So, it would be greater if someone had posted some more good links besides their rude looking remark (again, not rude, but just looking so).

theq86 said:
Root
Rooting a device is a method to gain full access to the operating system. With root you can do all the administrative stuff, write to locations normally restricted to the system and customize your device deeper.
Root enhances your privileges and you are able to change almost anything inside of your rom.
The rooting, however, affects ONLY your operating system (Android)
Unlocked Bootloader
In most devices, the Bootloader is the instance that calls the operating system (Android) and manages direct access to the device's partitions. Having an unlocked bootloader enables you to flash custom roms, custom kernels, recoveries and so on.
Bootloader and Rooting Teamplay
Often it is the case, and so, too in our devices, that a locked bootloader also locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader. Rooting needs write access to the system partition (for storing the superuser binary and the superuser app)
Without unlocked bootloader, only a temporary half-root can be achieved.
Click to expand...
Click to collapse
Thanks for this useful info

I agree. It is the autumn of 2014, and I've been reading webpages until my eyes are bleary. This is the 1st thread that actually explains how the two concepts relate rather than descending into buttonology. I think the OP's question hits the nail on the head (well, one of them at least) and he doesn't need to be treated in a demeaning manner.

Wow, 1 year after last post, I thanked he asked this question! Was thinking as same as u, loll
fredphoesh said:
19 months after the question was asked, i just happened to be wanting to answer the same question for myself, so I searched and found this thread...
I am happy he asked the question, as it was the first answer I saw in google search... so maybe he could also have done a search 19 months ago, but his question was useful to me, and your response seemed rude and unnecessary. You never know who may benefit from a little generosity.
Mark.
Click to expand...
Click to collapse

Root vs bootloader
If i have an unlocked bootloader can i install apps that require root. Will they still work even though im not rooted?

Deogracias said:
If i have an unlocked bootloader can i install apps that require root. Will they still work even though im not rooted?
Click to expand...
Click to collapse
I'm not an expert, but here's my understanding from months of reading up on this: Unlocking the bootloader lets you install a program known as Recovery, which is another program that lets you install operating systems, e.g., stock Android, CyanogenMod. Whether you have root or not is determined by settings made after the operating system is installed. So unlocking a bootloader is different from root. You can have either one without the other. However, I am also left with the impression that software that helps you unlock the bootloader also give you root (and perhaps vice-versa). This dual functionality is designed into the software, but they are separate things which don't have to both happen.
I just reviewed my answer and realized that it doesn't really address the quoted question very directly. Unfortunately, there is no "delete" function. So hopefully, it helps a bit. As further info, I unlocked bootloader, changed the Recovery, and replaced the native Android OS from Koodo with CyanogenMode. However, I did not root. Hopefully, someone else can chime in with further experience.

I've been wondering about this for years, as well. I don't feel confident doing things to my phone that I don't understand. I'm sure I'll never have a thorough understanding, as I'm not a programmer, but even a rough one would suffice. This is the same reason why I will only attempt certain operations on my car -- if I muck it up, I'm boned.
I rooted my phone (or maybe unlocked the bootloader?) a couple years ago, and never got around to doing anything else with it, because I couldn't figure out how to "do a recovery" (still don't know what that means, exactly). Or maybe I unlocked the bootloader, and never rooted it? I'm still confused. I see LOADS of folks who throw the terms around, whom I suspect, actually have no clue. I have a Verizon S4 MDK 4.2.2, and I just now finished the process -_- Better late than never? Now, I'm trying to decide if it's worth the headache, and possible risk, of installing custom ROMs, etc. Also, I know my phone is "SO old!!' and blah-blah-blah. At least if I screw things up now, I can get a new phone with a new contract, etc.
I really wish Verizon weren't such dirtbags about the locked bootloader thing.

No
SanderTheNinja said:
There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse

Heee is full difference between rooting and unlocking bootloader
Rooting - Administrative access to the entire file system including the ability to change system files such as installing system-wide ad-blocker by modifying the host file on your device, or uninstalling system apps, such as bloatware that comes pre-installed on your device. Without root, one can only see files in root directory instead of editing them. Some alps and mods only work with root.
Unlocking bootloader- To understand this term, one need to know the meaning of bootloader first. In simple terms, bootloader is like a person which checks many functions at the time of boot. It's on of the most important part and boots the first. Unlocking bootloader means asking that person to give us rights to do some modifications in our device like flashing custom recovery, rom etc.

prdonja said:
How to unlock bootloader ,but the way that I can lock it again
Click to expand...
Click to collapse
ADB

Is There A Way To Unroot Back to ICS

I know there must be a developer at work trying to make it happen but i need to go back to normal stock from the latest epic touch update w/o losing data thanx...

Rooting/unrooting with adb
The safe way is to know exactly what was modified in your system to root the device, and carefully undo the changes in the proper order. IMO, an app that roots a device *should* have unrooting capability as well because the developer of the app knows how the rooting process works, and how to undo the changes. Of course, the rooting process should be done in a way that allows it to be undone.
If you try to guess the process, and you don't know exactly what you are doing, you could brick your device, so be careful. I am not saying that as a disclaimer, but as an actual warning. Please take it seriously.
I had to root my tablet (also running ICS) manually through adb from my desktop Linux system. The method I followed was to install a custom su command in both /system/xbin and /bin, and then a Superuser app. It is not very complicated. I honestly don't know much about this yet, and just followed instructions that were posted at this site. The tablet was new, and I was ready to just re-install Android if things went wrong.
Does anyone know more about this? I tried to find more technical information on rooting, but was flooded with search results on what app to use, and other "user-level" information. I would like a full technical explanation if anyone has bothered posting such a thing. Do the apps all do the same operations? Is the procedure always the same for a given version of Android? And is there a corresponding method of unrooting, that works on all devices? If not, then why not?

jayts said:
The safe way is to know exactly what was modified in your system to root the device, and carefully undo the changes in the proper order. IMO, an app that roots a device *should* have unrooting capability as well because the developer of the app knows how the rooting process works, and how to undo the changes. Of course, the rooting process should be done in a way that allows it to be undone.
If you try to guess the process, and you don't know exactly what you are doing, you could brick your device, so be careful. I am not saying that as a disclaimer, but as an actual warning. Please take it seriously.
I had to root my tablet (also running ICS) manually through adb from my desktop Linux system. The method I followed was to install a custom su command in both /system/xbin and /bin, and then a Superuser app. It is not very complicated. I honestly don't know much about this yet, and just followed instructions that were posted at this site. The tablet was new, and I was ready to just re-install Android if things went wrong.
Does anyone know more about this? I tried to find more technical information on rooting, but was flooded with search results on what app to use, and other "user-level" information. I would like a full technical explanation if anyone has bothered posting such a thing. Do the apps all do the same operations? Is the procedure always the same for a given version of Android? And is there a corresponding method of unrooting, that works on all devices? If not, then why not?
Click to expand...
Click to collapse
I fully agree a 100%, but thanx to SFHUB the problem was solved...

pointed in right direction

could someone point me in the right direction on rootig my htc desire z . versio 2.3.3

camsurf said:
could someone point me in the right direction on rootig my htc desire z . versio 2.3.3
Click to expand...
Click to collapse
In regards to rooting and such, you don't have to go any further than checking out the Android Development sub-forum for whatever device you wish to gain root level access for. I suggest reading up on what exactly entails rooting your phone as well as what possible consequences could arise from doing so. Jumping into rooting your device without doing your fair share of research is how devices get bricked. Not trying to be a hard ass but that's the way it is.
Word of advice, asking questions for which there are easily found answers can be frowned upon by people here. I on the other hand am a nice guy ... therefore instead of ridiculing you I shall help you out and in return you may hand over your innocent soul for mine has been tarnished by the wonderful fellows of the Internets.:angel:
Onto the helping. CyanogenMod has created a wonderful wiki on how to go about rooting your device. Take note that you have Gingerbread on your device, therefore it will need to be downgraded to Froyo prior to rooting.
http://wiki.cyanogenmod.com/index.php?title=HTC_Vision

If you are looking for a complete guide starting from downgrading to rooting then you could download the pdf I made from the "minus" link in my signature.
Sent from my HTC Vision using xda premium

driving me crazy
Here's the deal I'm stuck at. When I download the Android spk and install the tools. Then when I try to put in the code in terminal to cover with my phone it responds adb path not found or does not exist. I added a path variable or whatever it said to do. I rooted two Sony phones already so I see don't think this should be to hard.
The other question I have is on my other rooted phones is it OK to factory reset and root again. I have a backup app. I wanna wipe my partners Sony and have a clean start.

camsurf said:
Here's the deal I'm stuck at. When I download the Android spk and install the tools. Then when I try to put in the code in terminal to cover with my phone it responds adb path not found or does not exist. I added a path variable or whatever it said to do. I rooted two Sony phones already so I see don't think this should be to hard.
The other question I have is on my other rooted phones is it OK to factory reset and root again. I have a backup app. I wanna wipe my partners Sony and have a clean start.
Click to expand...
Click to collapse
It's SDK btw (as in software development kit), start some place like this : http://wiki.cyanogenmod.com/index.php?title=HTC_Vision
Can't advise you on sony products.

camsurf said:
Here's the deal I'm stuck at. When I download the Android spk and install the tools. Then when I try to put in the code in terminal to cover with my phone it responds adb path not found or does not exist. I added a path variable or whatever it said to do. I rooted two Sony phones already so I see don't think this should be to hard.
The other question I have is on my other rooted phones is it OK to factory reset and root again. I have a backup app. I wanna wipe my partners Sony and have a clean start.
Click to expand...
Click to collapse
You didn't set the path properly and/or didn't reboot your computer; either fix that or just run the commands from within the directory ADB is located in.
As for your other devices, doing a factory reset from recovery will not lose root, all it does is take whatever ROM you have back to a clean start (no installed apps, no tweaks, no accounts, etc.)
Sent from my HTC Vision using xda app-developers app

OriginalGabriel said:
As for your other devices, doing a factory reset from recovery will not lose root, all it does is take whatever ROM you have back to a clean start (no installed apps, no tweaks, no accounts, etc.)
Click to expand...
Click to collapse
Depends on where you speak of "factory reset".
For example within the phone's OS, if you do a factory reset under system setting, then yes that would be true.
However 'factory reset' from say clockworkmod or 4EXT recovery means that it wipes the /system /data /cache etc partitions, and there would be no rom to boot into (something that can scare a new person if they have no clue that they need to flash a new rom back on, or restore nandroid backup)
The problem with a lot of those questions is that without clarification on where they are asking, can lead to undesirable results, so naturally people should read and re-read before doing anything.

ok thanks.
ok. so restart after installing sdk. do i need a andoid verson when i download those tools like it said, because i keep getting a password and usename request wheni get to the android version almost download . thanks for your help. thanks coming your way

camsurf said:
ok. so restart after installing sdk. do i need a andoid verson when i download those tools like it said, because i keep getting a password and usename request wheni get to the android version almost download . thanks for your help. thanks coming your way
Click to expand...
Click to collapse
All of this information should be explained in whatever guide you've been linked to, including the where you obtained the SDK from, also if you've rooted two other phones already this should be child's play for you.

camsurf said:
Here's the deal I'm stuck at. When I download the Android spk and install the tools. Then when I try to put in the code in terminal to cover with my phone it responds adb path not found or does not exist. I added a path variable or whatever it said to do. I rooted two Sony phones already so I see don't think this should be to hard.
The other question I have is on my other rooted phones is it OK to factory reset and root again. I have a backup app. I wanna wipe my partners Sony and have a clean start.
Click to expand...
Click to collapse
I didn't mess with adding the variable paths and just went to the location where the adb.exe file is located and ran it from there. For me I installed the Android SDK on the root of my C: drive so adb.exe is located at C:\android-sdk-windows\platform-tools. Therefore when I need to use adb I just go to that location through the command prompt and run adb from there.
As mentioned in the Cyanogenmod ADB guide, all you need to download and install using the Android SDK Manager are the Android SDK Tools, Android SDK Platform-tools, and Google USB Driver package.
As for your Sony devices, when you do a factory reset through Android or through recovery it will not unroot your phones. You will need to look for a guide in the forums for those Sony devices on ways to remove root and return the phones to stock.