Why did I make a new thread? Because people were complaining in the other one that it was going off topic. When we're finally rooted, hopefully this becomes the root help thread and the only root help thread. And the devs see this and get it out faster.
Each day more and more Android handsets are being sold, and that means users are faced with a major decision: To root, or not to root. Some of us will do it simply because we can, others will decide not to do it as they enjoy the phone as-is, but the majority of us will be on the fence about the whole idea of rooting.
Hopefully some of those questions can get answered and you’ll have a clearer picture of the process and some understanding to make the decision a bit easier. I’m sure this won’t answer every question you’ll have when considering whether or not to root your device, but hopefully this is a good start and a basis for further discussion.
What, exactly, is rooting?
Rooting your Android device involves adding in a small Linux application called “su”. It stands for SuperUser, and allows applications and commands to run with elevated permissions. Everything that runs code, whether it’s an application or the user, has a permission level set by the operating system. The root user is the boss and can do anything (good or bad) on the device. From simple things like clearing the cache from core applications, to more advanced things like wirelessly tethering a laptop or iPod touch through your phone, root can do it. The su program is a sort of gateway that lets applications or users act as root while doing tasks. If you’re the curious type (I know some of you are ) here’s a more in-depth review of root as used in a Linux system by the Linux Information Project . OK, so why would I want to root my phone?
Good question! Maybe you don’t. Everything in a Linux system is a file, or is treated as a file. Most of the files you will need to access or change are available to you without having elevated permissions. "Most" being the key term here. When you want to do things that affect or change the core software of your device -- like changing the theme or adding a nice piece of software from another device -- you'll have to do it as root. Dream and Magic users have been running Eclair on their phones for a good while now, and it’s because they have rooted their device. Rooting also gives you access to some handy software that you couldn’t use otherwise. Things like a complete system backup or ad blocking software require you to root your device. Don’t root your phone just for the sake of rooting your phone, but if you come across something you feel you could use or would like to have, then consider it. So it's like jailbreaking?
Pretty darn close. Jailbreaking an iPhone or iPod touch opens up things like using applications that aren’t manufacturer-approved or changing the look and feel of the device. Android already allows this to a large extent. The changes behind the scenes are the same way. A lot of what you can do with a jail broken iPhone you can already do with your Android phone, but to really unlock everything you’ll need to root it. The concept itself is identical. You’re allowing things that usually wouldn’t have root permission to have them. Is it dangerous? Will it break my phone? Will it void my warranty?
It can be, It might, and Yes. By not allowing access to the superuser account, the manufacturer and your carrier have basically protected you from doing things that change the system and make it unusable. All it takes is one wrong keystroke to turn your shiny new Android phone into a plastic and metal brick with no connection. Most times this is recoverable, but not always. You have to decide how capable you feel you are, and how well written the instructions you’ve found seem to be. Nobody will blame you if you decide against the risk, especially your cell carrier. All major carriers and manufacturers plainly state that altering or using unapproved software voids your warranty, and rooting falls into that category. While that seems a bit harsh, they need to be able to support the products they sell. For that to happen, they need to know exactly what’s running and what it’s doing.
Apps that run as root need a little further consideration. You need to have a level of trust in the person who wrote the app first and foremost. Does the developer have other software available? Do the user comments (for Market apps) have anything that raises a red flag? Do the requested permissions seem a little odd? These are all questions you need to think about before you allow something to run as root. For a further level of security, think about installing an application that warns you anytime something tries to run as root. SuperUser Whitelist (Android Market link) is a great little app that does exactly that. If you decide to go on and root, ask users with the same device as you for a link to a version of SuperUser Whitelist that works with your firmware. Once installed, anytime something wants to run as root, the app intercepts and asks if you would like to allow it. You’re given the choice to accept, decline, or grant the app in question full privileges each time it runs.
One last thing to touch on here. Many custom ROMs include some sort of SSH server. This can be a wonderful tool, or it can get you in hot water. This is what caused the whole “Rick-Roll” episode with the latest iPhone jailbreak. The server sits and waits for an outside connection, and if that connection provides the right password full control of the device is turned over. In the case of the iPhone, users never bothered to change the default SSH password for root. A clever (or devious) group of users simply scanned for servers listening on the correct port, then attempted to sign in as root with the default password. Lesson learned, but this is easy to prevent. Ask other users of the ROM or firmware you’re thinking of flashing if there is a server listening, and if so how to disable it or change the default password. If I root, will I still receive operating system updates from my carrier?
Maybe. More than likely if you’ve just rooted your phone so you could have access to the full file system and haven’t drastically changed things, the phone will still pass your carrier's checks and upgrade. If you’ve delved deeper and really customized your device, count on not being able to upgrade. Carrier updates were designed to work with the original software, so they need to be sure that’s what the phone is running. Again, this is for your own good. T-Mobile or Verizon can’t offer technical support for things they haven’t trained their technicians on, and if you flash a carrier approved update over custom software it’s probably not going to work.
The good news is that failing the checks the carrier does during an update won’t cause any damage to your phone. The update will just quit and you’ll be back where you started. Then you can decide if you would like to un-root and upgrade or take another path. The worst case scenario is that the phone passes the carriers checks, updates, and then things get broken. That’s pretty unlikely, but possible. If that would happen, you won’t be alone. Everyone in your situation will scramble to their favorite Android user forum and hopefully a work around can be found.
Note - a carrier update may also break the ability to root the device and a new method will need to be found. Any discussion of upgrading and root needs this mentioned as well. Most folks who root and decide to install a custom ROM wait for the ROM developer to provide an update that includes any bug fixes or new capabilities of the carrier update. Will I still get application updates?
Yes. While it’s not being used, the program that allows permissions to be upgraded just sits and does nothing. Normal applications won’t even be aware it’s there, and applications that use it expect it to be there. Application updates, whether they are from the Market or other third parties will still install as normal. If I decided to "un-root" my phone, how do I do that?
It depends on the model of your phone. Some are ridiculously easy to revert, some not so much. This is the most important question you can ask before you dive in and root your phone. Usually the website you found the method to root your phone will also have a discussion about un-rooting and going back to stock firmware. Take the time to find and read this information so you’re aware of just how difficult it’s going to be to go back. Pay close attention and create backups when recommended while you’re rooting your phone, as these may be needed to go back. I’ve not heard of any device that can’t be restored to factory firmware provided the original was backed up properly as recommended during the rooting process. The most important thing to always remember is to ask for help. If you do find yourself stuck without a backup or a working phone and need to roll back, ask for advice. Our forums are full of fine folks from all walks of life, and the majority are more than happy to help. There’s a good chance you’re not the first person in that situation and a solution has already been worked up!
As you can see it is something that needs a little thought before you dive right in. But if you decide you need root access, consider some of the information we’ve laid out here. The security and other risks are real, but are pretty easy to work with. There’s no reason you can’t safely root and use your phone, just do your homework first!
Device(s): Galaxy Nexus-AOKP w/ LeanKernel
Kindle Fire
Transformer Prime
Thanks: 288
Thanked 260 Times in 189 Posts
Thanks for bringing that over to our forum. The writers of the QA did a great job of explaining things and I now know what to look for when we get the privilege of root access. This should be stuck up top!
Great post, and it should be very helpful. This is my first smartphone, so I will be rooting for the first time. Thanks for the info, look forward to more.
"When we're finally rooted, hopefully this becomes the root help thread and the only root help thread. And the devs see this and get it out faster. "
I am slightly confused by this?
Get Root done faster?
My Dev Team isnt working and less or more than before now that we have working Exploit?
Sorry just confused.....
"When we're finally rooted, hopefully this becomes the root help thread and the only root help thread. And the devs see this and get it out faster. "
I am slightly confused by this?
Get Root done faster?
My Dev Team isnt working and less or more than before now that we have working Exploit?
Sorry just confused.....
I think by 'get it out faster', they mean spread the WORD of what's going on faster, and more efficiently.
In other words, (I assume) when the time comes, there is no confusion as to the proper forum for the conversation/announcement.
Ohhhh....That I kinda get...
But the offical word and information for anything from our Eris Dev Team will come from me and go directly to Caddyman.
He is the Member of these forums that releases our information
Last edited by acidbath5546; February 16th, 2010 at 11:56 AM.
If the 2.x update comes out before the root is completed, then should we not update to 2.x? Wouldnt that 2.x software require a whole new root process?
EDIT: Nevermind, I got my answer in the other thread.
Last edited by ssick92; February 17th, 2010 at 02:08 AM.
Device(s): rooted eris, with vanilla rom oc to 748 at 5.12 mflops
Thanks: 6
Thanked 2 Times in 2 Posts
So just to clarify, as long as I dont modify too much then i should still get updates... does cutting out all the Verizon fat (like footprints)and overclocking qualify
So just to clarify, as long as I dont modify too much then i should still get updates... does cutting out all the Verizon fat (like footprints)and overclocking qualify
I would think that would be "major" changes. I think it will only keep OTAing if nothing is changed with the core of the phone; overclocking would be changing the core processor function. But I could be wrong.
just to clairify footprints is a htc app not a verizon app which is tied to the camera which could cause camera problems. verizon kept thier bloatware to a minimum. the only app they added was visual voicemail. all others came with sense. weather can be removed. stocks can be removed. teeter can be removed. the pdf viewer can be removed and quick office to name the ones i know off the top of my head.
__________________
Some things can be summed up to user error. If 95% of the people have no problem it must be your problem.
what is the best rom to slap on after rooting my g1? cyanogen rom is nice...but development seems to have slowed down a bit since he started working on his nexus one (completely understandable).
any that are on par, or maybe surpasses cyanogen rom at this moment?
what is the best rom to slap on after rooting my g1? cyanogen rom is nice...but development seems to have slowed down a bit since he started working on his nexus one (completely understandable).
any that are on par, or maybe surpasses cyanogen rom at this moment?
i'v got the xROM-Eclair-2.1-v1.0.1 rom on my g1 works great there might be a better one out there
Check the HTC Hero forums. THe Hero is almost idenitcal HTC for sprint and has been rooted for many months now. Anyway you won't get a great jump in speed and its a trade off in stability and battery life, more speed equal more battery consumption and less stable .
Not sure exactly where to post this, so here seems good as any...
There are a lot of us new to rooting and programming in general. I beleive we all understand that this takes a lot of work and some pretty ingenious people. My question is: For someone to start from scratch learning about this particular branch of programming, if for no other reason than to save some questions to those of you doing all of the work, where should one start?
Would a Linux basic understanding suffice or is there a particular "branch" of this language that would provide a more concise understanding?
Please provide any links or articles you would recommend. We'll start thinning the "noob" numbers yet!
Already rooted, so this is just hind sight.. If i change to a different rom is there any way to keep my home screen setup like widgets and apps and wallpapers?
Or will i have to re-download and arrange all of it again?
Already rooted, so this is just hind sight.. If i change to a different rom is there any way to keep my home screen setup like widgets and apps and wallpapers?
Or will i have to re-download and arrange all of it again?
i have the same question along with will i be able to go to the stock 2.1 im running now since i have rooted but not flashed a custom rom yet. will i be able to go back to where im out now?
Already rooted, so this is just hind sight.. If i change to a different rom is there any way to keep my home screen setup like widgets and apps and wallpapers?
Or will i have to re-download and arrange all of it again?
MyBackup. Don't backup the system settings. It worked pretty well for me when I installed the leaked 2.1.
Your entire ROM should be backed up. Once you have your home screens and settings set how you want, boot up in recovery and hit Backup/restore and make a backup. Then just reboot when you're done. This will save basically your entire 'flash'. Way better than any backup app can do.
The way I understood is if I restored the backup though it is of that rom and that rom only. Whats the point in using an old rom when you want the new one installed and running.
Don't you have to wipe each time before ya flash on a new rom?
So I'm a nOob in fact this is my 1st post on this forum. Ok I have several questions so please bare with me.
1: Does flashing the 2.1 also void your warranty & will you still receive the OTA version if doing so I read the forum at the top about this & it only mention that If you root & make drastic changes to the core system then maybe, but nothing about flashing.
2: I also read somewhere that even if u root & voids your warranty that when the OTA comes it does a complete system wipe & returns it to factory 2.1 & VWZ would be none the wiser. Is this true?
3: The brand new leaked 2.1 update that just came out yesterday do you have to root that or is that just the flash version? Can I just flash 2.1(brand new version) but if doing so will I be able to return to my stock 1.5 if I back up the whole system if I feel rooting was the better method to go with?
4: I have the app Astro will that back up my full 1.5 stock Rom?
5: If so where do I back it up at?
6: If not what app should I use to back up the whole 1.5 Rom & again where do I back it up? I'm assuming you back It up on your micro sd card& then tansfer the backup folder and or folders to your desktop. Please correct if I'm wrong.
7: Last question does this forum or website have a Twitter account?
I'm sorry for the long post I'm just trying make my questions as clear as possible. I'm just essentially wanting the 2.1 update to have the new features & fix all the bugs that come with 1.5 donuts I'm not going to change anything to the core system other than updating 2.1 @ least not until I become more familiar with how to do it. Thanks for everyone's hard work on this site. And I hope by asking all these questions it may help someone else by reading the answers. Thanks again. DjKoZ78
Last edited by djkoz78; May 1st, 2010 at 10:25 PM.
Reason: better explanation of questions
Device(s): Eris>Droid X>>Thunderbolt>>>Rezound>>>>Whatever I can get my hands on!!!
Thanks: 547
Thanked 433 Times in 291 Posts
1. as far as I know upgrading to 2.1 does NOT void your warranty. Rooting however does. But root has a roll back to stock 1.5 and the leaks do not.
2.Some custom roms have disabled the OTA, so if you install those you will not receive it. If they do not disable the OTA then you will probably still receive it.
3.If you install the newest leak you WILL LOSE ROOT until they root it. Currently the only way to root is from stock 1.5. and I already answered your roll back question.
4. No it can only back up apps.
5.moot
6. there is a thread around here that explains the process to down grade from rooted 2.1 to stock 1.5. Once again this is only if you are rooted. THERE IS NO DOWNGRADE FOR LEAKS.
7.I'm not on twitter so I can't answer that.
If you are debating between installing the leak and rooting I would highly recommend rooting at this point because chances are you will want to root eventually and as of right now there is no way to root anything other then stock 1.5
Thanks for he info. Personally, I only want to be able to Root so I can enable WiFi tethering. So, I don't think I'll be messing w/ the stock ROM in any other way. Hopefully, this will let me keep my Root when I upgrade?
Thanks, guys for your help, patience, understanding, and willingness to proliferate your knowledge.
The Following User Says Thank You to gmaffPappy For This Useful Post:
After I install the original root rom (w/ the expiration date), then do amon's recovery image, can I just go straight to the VanillaDroid Rom?
I have the file for vanilladroid, does it need to be renamed anything to work??
Nevermind, I just did it...
__________________
Quote:
"you're still here eh? figured since you love the iphone so much you would deal with the shitty coverage to have one... im sure your droid doesnt get that great of service from the inside of steve jobs' ass anyway"
Last edited by BlueDC2; May 22nd, 2010 at 05:19 PM.
Device(s): rooted eris, with vanilla rom oc to 748 at 5.12 mflops
Thanks: 6
Thanked 2 Times in 2 Posts
I have a rooted Eris and a leaked Eris, on the leaked Eris will it receive the ota update or not... its my wife's phone and she wants the ota, and wont let me set up the newest leak she is still on the original leak, if I do set up the newest leak do I have to do a wipe first?
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More
Rooting Q&A
) here’s a more in-depth review of root as used in a Linux system by the 
