I am taking a chance here by discussing a topic such as this, and in particular taking the stance that I am taking. So, with that in mind, let’s just get down to business.
As is usually the case with these sorts of things, we’ll start off with a disclaimer or two. Most importantly you must realize that these are my opinions and observations, and some of them might be wrong. Please feel free to let me know if you disagree with anything I say. Keep in mind also that I am not saying that rooting your device does not have its benefits, but rather that one must be careful. Now that that is out of the way…
So, you just got your fancy new G1 or MyTouch 3G (or whatever other device you happened to get) and you’ve been reading about all of the cool things that you can do with it… but there is a catch. You have to “root” your device in order to do these cool things. So, of course, you hop online, find a tutorial (or even better, the so-called “1-Click Root” method) and proceed to root your device. To your surprise, it has been made so easy by now that it worked perfectly on the first try. Congratulations.
Now, in a perfect world, every user who has gone through this process knows exactly what they are doing and, even more importantly, how to keep their device and the information within and connected to it safe afterward.
But the reality is we don’t live in a perfect world and I see new Android users every day who choose to root first and ask questions later. That is, they decide that they want or need to root their device before truly knowing what that entails.
However, I can’t really put all of the blame on the users at this point because I know that there are a lot of (really great) tutorials out there for rooting, and I know that not all of them put enough emphasis on the seriousness of it all. Some flat out fail to make it clear that you are compromising the security of your device when you root it. It is as if they make assumptions about the technical level of the reader, and we all know what happens when you assume.
Accordingly, it always concerns me when rooting guides are placed right alongside beginner tutorials. To the reader, this implies that rooting is a beginner process, and that all beginners should do it. To that I would have to disagree. In fact, there are some users that simply should not do it.
To fully explain why I think not all users should root I have to jump out of the “root” discussion for a while, but I hope it will help to make my point.
How many times have you been perusing the Android Market and seen an application or game that you wanted to download? Countless, right?
How many times have you gone to download that application or game, been presented with a list of requested permissions, and seen things like Full Internet, GPS Location, Read Contacts, etc… Do you ever think “Hmm, why would a game like Asteroids or “Insert Game Name Here” require access to these things?” Do you ever install anyway? Don’t be afraid to say yes… I have done it too.
The fact is the majority of users simply don’t pay enough attention to the permissions requested by Android applications.
The fact that the Market tells us what types of things a given application wants to do is totally awesome, but it isn’t enough. Unless the user takes this information and makes an informed decision, there is little point to this security measure. As soon as you grant these rights to an application, there is little you can do to stop them taking all of your Contacts information (for example) sending it up to their server and doing with it what they please. I am sure that your mother wouldn’t appreciate whatever repercussions this might have (spam, telemarketing calls, junk mail, etc…).
And take for example another type of app. The kind that may have the best of intentions, but the worst of implementations. Believe it or not, developers do make mistakes. Sometimes a developer chooses to use a protocol that they think is secure but isn’t. Or maybe they choose to use a single sign on for all users, and then leave in the debugging code that prints that sign-on information to the console. Suppose also that this well-meaning application also offers an option to remotely wipe your phone. What happens when someone figures out how to spoof information (they probably already have) and send it to the server and invoke a wipe of your data without you knowing it?
Basically, what I am saying is that even non-root applications can be harmful to the overly trusting user. With that being said, we’ll head back to the discussion of root access for applications.
So, with root-enabled Android applications we see all of the same potential for misuse that we see in regular Android applications and then add on a whole new level of potential. Why? Because root access circumvents the security restrictions that are put in place by the Android OS and there is not really any effective way to tell just what the application intends to do with that power.
Sure, most (if not all) modified firmware releases include the Super User application by Koushik Dutta, or a variant of it, but is that enough? Similarly to the user account control message in Windows or other similar programs in other operation systems, this app only tells when an application requests Super User access. It does not (can not?) tell us what the application intends to do with that access.
How many times have we (yes, I have done it too) granted “Always Allow” access to an application without fully knowing exactly what the app was going to do? How can we tell exactly? Most of us can’t, so we rely on what other users tell us, or we trust the developer. But, of course, that is not always reliable.
In many cases, but not all, these applications are open source so we can look at the source code to assess the risk. Then again, with an open source application, there is a greater possibility of coming across a modified version. Even if you only allow access once, your phone could be ruined.
But what exactly might a malicious root application do? Basically anything. In a little brainstorming session with a friend we came up with a wide variety of evil things that a root-enabled application could do.
- replace the Gmail application with a modified version
- replace your keyboard with a version that logs keystrokes
- delete files such as applications or application data
- download and attempt to install a different modified ROM
- download and install another application that wakes up nightly to call toll-numbers
- gain access to your Market account and make purchases on your behalf
- and the list goes on…
Luckily, we haven’t yet seen anything like these. Hopefully, we never will.
If you are now thinking, “Man, that stuff is scary…” then I am already starting to feel better. It is the user, who recognizes the potential misuse and keeps it in mind when using these applications, that will be better able to protect their device and information.
Do your research. Learn about an application and the developer before trusting them. As a precaution, don’t use “Always Allow” in the Super User application, though that will not protect you against a one-time attack.
Ideally, we wouldn’t have a need to “root” our devices for some of the things that we are rooting for.
Case in point, I’d guess that a large portion of users root because they want to apply a theme. If Android were to natively support themeing, that might reduce the number of people rooting. Some people are rooting because there are optimizations added to make the phone run faster. Perhaps some of those optimizations could be contributed to the Android Open Source Project and included in official builds. In the case of the G1, where storage is extremely limited, we are rooting so we can store apps on the SD Card, or so that we can continue to receive updates to the OS.
In the effort of full disclosure, I have two Android devices, a T-Mobile G1 and a Google Ion ( HTC Magic), and both of them are rooted. I rooted my G1 when I first got it so that I could install applications to my SD Card. I will not claim to have known exactly what I was doing at that time and I am pretty sure that I don’t now. For months I used my Ion without rooting, and only did recently to try out the “1-Click Root” method. Otherwise, I’d be pretty happy plodding along without root on my phone.
I am sure that there are a few readers who might be wondering what brought on this post? To be honest, it really comes down to an observation that a lot of new Android users have the impression that in order for your Android device to be “functional” it must have root. And while I wouldn’t normally see that as a problem, we are beginning to see more users who don’t fully understand the whole root concept and as Android continues to gain momentum, the likelihood of an attack grows.
Related Posts
About The Author
Follow on Twitter Subscribe
Justin Shapcott
Justin is the founder of and lead developer at nEx.Software.
63 Comments
I will have to agree fully!
The only thing you can preach about when you root is to be educated. I think AndroidandMe is doing a good service by letting members/users read this to let them know what to keep their eye on. One application you can download off the market is aSpotCat, it will tell you want permissions apps want and use.
The only thing I could argue is that all apps have the potential to break down your device and make it do things it shouldn’t. The Android community is quick to point it out though… so if there is a malicious app out there it would get shut down quicker than later.
Good read, I hope more Droidheads take the time to read it.
Great read! You make some excellent points and I agree these things should be communicated more widely. Root isn’t just for the ‘advanced user’ anymore and I fully agree that the novice needs to be better informed. I’ll take this back to our community as encouaged reading.
Thanks for putting these thoughts together!
Being one of the new Android users that Justin mentioned (my phone hasn’t even arrived yet) I think the post is perfectly timed.
While it’s not going to stop me, or even slow me down, from rooting my phone right away, it did make me actively aware that things could kill my new toy – and just like running a Windows machine in Admin you need to be careful what you pull down and install.
I did however follow the link to Koushik Duttas blog and download the SuperUser zip – and I’ll be following up with Ryans tip about aSpotCat once I have my phone setup.
Thank you to both of you.
This is a great article and should be posted to the XDA forums and stickied. I almost wish that this would be a mandatory read for first time rooters before they went through with it. Maybe the maker of the 1-click root software could incorporate something like this into the application and then quiz the user on the content of the above message before allowing them to root.
In my opinion the only app that you should ever grant ‘always allow’ would be terminal and that doesn’t even need to be done as it only adds about 1 second of time to click confirm SU access. Certainly the only app that I ever granted SU always allow to is terminal app as I use it quite often.
As a follow-up… I plan on using the stable builds of Cyanogen system – does anyone one know if that has SU built into it?
Yes, all Cyanogen builds include the SU Application.
Ahh… sweet. I kinda figured they would… thanks for clearing it up tho. Now I don’t need to worry about tinkering with the zip I pulled down from Koushiks site.
Keep up the good work Justin & Taylor… and everyone else at A&M. You’ve made a longtime reader out of me.
Please feel free to come into the AAM Forums too
Happy to have ya!
I’m sure I’ll be sucking up all sorts of knowledge from the boards in the next few days.
I just got back to the office from going home for lunch – had a nice surprise when I got home tho… my phone showed up a day early. It’s sitting on the hutch charging now for playtime tonight.
Very good article. I am coming from the world of Windows Mobile where after unlocking the phone you can load a ROM with a few simple button clicks on the computer. With everyone and their brother creating a ROM for people to try out, it has become second nature to just load one up, load up everything you normally use on your phone (email, contacts, visit banking websites) and never once consider the fact that you know nothing about the person who created that ROM or what “else” may be there. At least with Android you have the opportunity to look at the code (but seriously, how many of us have the time, desire, or knowledge to do so?) This is a great reminder to keep diligent and think before you click.
Interesting article, good points.
Nice piece… couple of key observations (as I see it), as a non-developer user;
1) Rooting allows themes and Wi-Fi Tehtering.
(most, if not all mobile networks don’t allow – but as long as you don’t use it to download GBs of data, then you’ll be fine – IMO).
2) Checking the permissions of all Apps.
All Apps in the market can do most of the negative things mentioned (e.g. copying contacts), but most scams will be reported on the various Android websites/general news pretty rapidly.
3) Only allow Super User access for Apps you trust.
Ensuring that you only allow Super User to programs you trust will see you right (e.g. I only allow Wi-Fi tether and CM Updater – for themes and ROMS updates). Thus avoiding all of the really nasty password access /phone call stuff.
Nag, Nag, Nag… I never read these posts and never read the permission requests. I also do not read licence agreements or user manuals.
But i do get angy when things go wrong. They should have worned me for that!!!
Thanks for the post. I’ve had my phone rooted for a couple months now and will admit that I didn’t (and still don’t) realize some of these security implications. I’m also not really sure what apps I’ve granted the “always allow” access. Can anyone give suggestions on how to locate that and change the permissions?
Open the Superuser Application… It will list the applications (unfortunately, only by id) to which you have granted “Always Allow” access. Press each entry to remove the permission.
Does this mean that, when I open Superuser and there’s nothing but a blank black screen under “Superuser Permissions”, that I haven’t granted any superuser access? No input does anything besides backing out of the Superuser app, as the menu key does nothing and other buttons just back out of the app. Thanks for the help!
While I agree with many of your points, I can honestly tell you my G1 is worthless without root. That being said you need to be smart about it. Rooted or not you should NEVER download an app that asks for a suspicious permissions. Just as you should NEVER root a phone without learning what you are doing and why. Don’t let your wants get in the way of common sense.
Jen: The G1 is an interesting case… As a first device, they got a lot of stuff wrong. I certainly don’t disagree with your assessment. The G1 becomes very crippled very quickly due to the hardware decisions that were made by HTC. For many (most?) users, rooting a G1 becomes a necessity because of this.
The expression is “Case in point” not “Case and point.”
Thanks…
Will keep in mind for next time.
First of all, I completely agree with the article. That being said, I must add that IMHO common users are overexposed to rooting. Basically, users do not pay enough attention to potential misdemeanor of freely available apps. When rooting, main question in people’s head is NOT to brick the phone, data security is not even on their minds.
Almost every website dedicated to Android has some kind of rooting information, tutorials, and/or news. I’m not saying that it’s bad. But when You take in to the account the “basic” users, it’s logical to assume that they will probably WANT to root their device, regardless if they really NEED it or not. Hype about the rooting is just enough as a cause. With appearance of one-click-root apps the process has been stripped down to it’s simplest and almost anyone knowing how to click can root their device.
It seems to me that Android’s security system is solid one, but depends on user itself to make informed decision on what applications to install and what not to. Not paying the attention to the security notification when installing an app is just ignorant. If You want a password storage/encryption app, and it requires Internet connection, shouldn’t You think twice? On the other hand if anti-virus warning pop’s up on Your’ PC’s desktop, do You ignore it or read what it says?
It all boils down to the fact that rooting does have advantages but users themselves MUST think really hard should they root their device, just like installing any other application/game from the market. And to conclude (I’ll probably sound like some manufacturer’s PR) – but if it was (amongst other things) SAFE to have all the devices rooted initially – wouldn’t they be?
I’m not sure about this next one – but as from what I’ve read, every Android app runs in it’s own ’sandbox’ thus effectively disallowing other apps to access it’s data, except if app ‘publishes’ it through public providers. Doesn’t rooting allow all applications to have root (superuser) access thus killing off the app sandboxing and whole security system which is in place?
Great read, everyone should be aware of this (especialy those who follow the root directions posted to ur site a while back lol) neways, ive always used cyanogen for the ease of use to constantly flash his newest build and have never once had a single problem even on experimentals. Thats my only advise, stick with him and u should be ok.
I am just an average android os lover; and this article was an excellent read. When I first got my g1, I did think about going the root way (all the hipe on androidcommunity), but thought better, and didn’t. I really appreciate this site – great info.
Impressive, I agree. Excellent advice. I asked questions, put in the reading and research, watched videos, asked more questions plus more before doing so.
Why doesnt’ Google allow Theming .. Maemo has it right out of the box.. and if the OS is supposed to be so flexible… why restrict theming.. .. that is very Apple-Like
An excellent article. I’m definitely a bit of a control freak/tinkerer when it comes to my gadgets, but I’ve held off on rooting my Hero so far. In truth, I was considering rooting (and I suspect I will end up doing so at some point) but this article has convinced me to continue holding off. I guess right now, it’s working fine for me and I’ve no need to squeeze any extra performance out of it, nor do I need root access for anything I require of the phone yet. If/when that time comes, I’ll re-visit the possibility of rooting.
I do have to laugh tho that one of the ads I just saw on this page is for a Free Unlocked G1 – one of those “complete the offer” things.
Great article Justin! I have to agree with most points. I actually have not rooted because of the consumer demand of my website, plus limited time to do it, lastly security has always been a concern. I have been doing research lately about permissions app request was going to sum up a piece like this but from the average consumer who don’t know or care about rooting. (Basically the pros and cons of rooting).
I agree with do and I hope more people read this article. I will put a link on the portuguese community site and eventually peak the theme and do one of my one. Thanks.
I agree with some the comments about the hype and commercialization of rooting android being a problem for under educated users. I personally rooted my g1 cause 1 I like to customize, also if I buy a $400 phone I better be able to do what I want with it and not be restricted, I also wanted the tethering cause travling and needing the internet randomly is a necessity for me and I’m not about pay an extra $80 for a mifi device when I’m paying for unlimited data anyway. Last but not least rooting shouldn’t be for some teenie bopper out there going “hey dude look at phone” and that person has really no idea what he or she is doing or done. Not mention the ones who brick they’re phone and blow up all the forumms saying “you broke my phone” its honestly gotten on my lasy nerve. My 2 cents
Applications have to request to run under the “super user”, at least in CyanogenMod they do. Ever tried running an application that requires root access? You get a pop up asking for permission.
Of course, users being ignorant to how SU works or what “root” means to a Linux-powered device does mean it’s a huge security risk.
Great article, I think everyone should read this before they consider rooting their device.
This article reads a little like FUD.
Rooting your phone provides one important security/privacy service. It allows you to do to your phone anything that google and your service provider can. Otherwise your submitting to any control they whim, your just using their phone.
This is like argument 1 in the series that leads to Apple going before congress to convince them to make jail breaking illegal because of possible terrorist activity.
And I believe the SuperUser Application makes it safe. NEVER HIT “ALWAYS ALLOW”. Very few programs should actually require root access. A game never should.
You should always review a programs requested permissions. Many of the above horrors you list don’t require root access. They just need the right combination of permissions.
As a user you can already do so much harm with the phone the last little bit of flexibility root access provides a potentially malicious app is almost insignificant.
So, the latest “rooting” app that hit the Market (Instant Root) which does not install the SuperUser application on those newly rooted phones… How do you feel about that? We can agree that people who don’t understand rooting should do their research before rooting, yes? That is the main point of this article. Like I said, I have both of my phones rooted so am not inherently against it.
great read! very informative… I would also like to add (something i personaly do) is dont use your credit card information to buy apps. for that matter I dont use my real CC information to buy anything over the internet. I use gift cards. that way, if someone some how does get my information, they gain a 25 dollor gift card. its a simple way to protect one of your most vauluable possesions. your money =)
The more pervasive networked technology becomes, the more dangerous our common lack of security awareness will become. Eventually there will be a tipping point, a day of reckoning.
Consider each of these things people commonly do:
1. Giving account credentials to Meebo.com so that you can use instant messaging more easily.
2. Giving account credentials to the likes of Plaxo and LinkedIn so that they can pull in all of your contact information from other providers.
3. Installing a tethering app from someone whose livelihood you have no serious ability to impact (ie you can seriously damage the profit of T-Mobile if you prove they did something malicious, but you cannot seriously harm developer X on the market who released AppY for free).
4. Install … um, anything… on windows mobile…
(Ok that last one is both serious and meant to be humorous.)
For #1 and #2, which a shocking number of C-level executives I’ve known happily tout as the best features of these services, the danger ought to be obvious.
For #3 I’d suggest that the danger ought to be even more obvious, but clearly it doesn’t resonate with most people.
Is there any way we can get, say, a pettition to get Google to allow theming? There’s one called Prodigal Sun over on XDA that I really like, but not sure if I want to risk rooting my Hero when it arrives in October.
Well and beautifully said. even thoug i am a computer science major, i said to myself a 100 time”dude, thats linux, u never worked on it. are u sure!” (of cose i am glad i did it) but seriously every1 in the world wants to have full access to their device (makes them think they are hardcore professionals) like in my house where i am responsible for all the electronics, every1 wants an admin account. then they screw up some thing n call me saying whats wrong. I wud not recommend rooting to bigeners cuz it will be a head ache for themselves aswell as other (no offense beginers do ur homework then root).
This info help me a lot because i’m a new android user,i have mytouch3g and i was thinking to root it,but now i think ill wait a little or maybe buy another android phone to try it.Since i don’t really know what are the real benefits of rooting a phone!thanks ..
Finally, someone said it, great article! As a developer of Android apps, I would like to add that rooting and replacing ROMs is a nightmare for app compatibility. It becomes impossible to test an app on every platform available. And users expect apps to work on hacked ROMs even before the official SDK for the leaked version of Android is released. I was browsing the Market and saw bad ratings on one application by a big online retailer because it didn’t work on some build of Android 1.6. I downloaded it on my G1 with Android 1.5r1 and it worked perfectly. I sometimes get emails asking why my app is not working on x.y custom ROM. My reply is simple, sorry I can’t provide support for non-official builds. I have even seen differences between HTC and Google Android builds. These are official builds. Does HTC provide an SDK with their ROM on emulator? No. Hopefully we will not see Android diverge, otherwise it will become increasingly difficult to provide an homogeneous user experience.
well thanks for the interesting read i am new and you said it without being snotty and i see the point.well said and well received. that is a skill that will serve you well in life. and you my friend have mastered it.
I agree. While this post covers most of the basic hacks that might become as common as a virus infected windows pc, it does not cover the extreme dangers that rooting may present. Ya hackers don’t have to stand a mile away with a laptop to steal your contacts, but what about the possibility of an application to steal the information off your fastpass card? Or the ability to remote-brick your phone? Or turn your camera into a webcam while your phone is on your dresser pointing and you and your loved one bumping uglies. While these threats may sound far fetched, they are still threats.
Study up before you preform any hack. Learn what it does and what it can or might do. Never do your banking on you mobile device. Never store any passwords on your phone. And if you have any questions regarding an app that whats some weird permissions, ask a developer (the dev of the program and an outside source) they will be glad to help. Android devs can be found on xda of on irc.freenod.net #android-dev.
can someone please help me out. I have a G1 and i unrooted my g1 from jf 1.5 back to stock 1.0 then i got the update for 1.6. Now the problem is i want my g1 to have root access so i can use programs like audio hack which helps me hear alot better but i still would like the changes that come with donut can someone please tell me what i need to do to make this happen. Thanks and feel free to email me Theend313rd@aol.com.
Great article! I have been rooted since April and have to agree 100% with you.
I think with the MT3G coming out in July and now the Hero, Cliq etc. … not to mention 1-click root, xda and other forums are getting hammered with new users that haven’t ever had to research, b/c root is now one click and they are not aware of the dangers.
Notice how many ‘brick’ threads are in the forums now………
Regardless, thanks, that was a great article, definately opened my
eyes (even wider).
I sincerely believe the fact that the “one-click root” method no longer works as of 1.6 (Donut) is actually a blessing.
I just read your blog,and being a new user of the android phone and seeing in the apps that a lot of the apps require being rooted and reading your blog,all I can say is “EGADS” and I will learn more of the pros and cons of rooting my phone.Am very glad to find this blog..Thank you for enlightening about “rooting”
Great Posting!
Thank you so much for the article. I am brand new to the android community by way of G1 and am trying to learn about the phone. I have seen the term “rooting” on every android site but never fully knew what it meant until reading this article. I appreciate the information and will not be rooting my phone any time soon.
Wow! This article was awesome. Here, I thought I was to much of a Geek to read this article. Now, I kI’now lost my Geek Card!
I’ve been in the Cellular Industry since the Moto Brick anf the Transprotable, and have watched the wireless industry change before my eyes. I Love My “MYTOUCH” but the phone runs slow. What do I do now? Delete Programs or Root? Can anyone help?
i’m curious if anyone on here would know if it’s possible to reformat an itunes app to work for my motorola droid
UNROOT! UNROOT! UNROOT!
Its been driving me crazy. You just wrote a whole article about the dangers of switching to root, without mentioning the biggest issue of all. Its not easy to UNROOT.
The process of going back to a stock phone is not mentioned once. We warn people endlessly about the dangers, potential bricking, but no one wants to share the secrets of going back. Currently there is almost no discussion on how users would go back to an unrooted phone.
Maybe it is as easy as one click, but that information is not available. So for users such as myself who desperately want my phone carrier crippled again, I am just hanging in the wind, waiting…..
hey check out this link to un root your phone it tells you how to do it hopefully this will help you out!
http://www.youtube.com/watch?v=lReoBy848PI
i have a rooted mytouch 3g running hero rom i love it its ssssooooooooo fast and smooth i followed a coups vids on youtube to do it i have never done this before the videos i watched were very informing check them out thegadgetpro he really knows his stuff
@VoLoDaR1 can you give me the link to the hero rom?
Unless one has knows exactly the advantage of rooting, they shouldn’t do it. Even tethering can be done by a purchased app (PDANet).
You have a valid reason about malicious software getting root, but there are a few more reasons. Rooting has a high chance to destroy data stored on the phone, and unless someone is completely OK with that, they should not go forward with rooting.
Rooting also voids the warranty.
Rooting, then making a mistake as root might cause a bricking. Some phones can be reflashed, while others do not have a usable flash image, so if anything outside of the /system directory gets modified, there is no way to recover. In these cases, a bootloop that doesn’t get fixed by a hard reset will definitely brick the device.
Of course, there are valid reasons to root a device. Wanting to move to a newer Android version comes to mind. Similar with wanting to drop the manufacturer/carrier stuff and just have the default Android UI.
If I were to ask one question about if someone should root their phone, it would be if they know what root is on UNIX, and the dangers of running as it. If they don’t know the dangers, then they should think twice about rooting.
This was a nice article, but the only problem with it is that it is written as if users only encounter these issues when rooting their android device.
Did anyone every use Windows XP? Probably. The biggest issue with XP is that every (as in EVERY) program is run as admin, therefore with admin rights. Not many people realize this, but everyone went around business as usual and to my knowledge didn’t raise red flags for many.
My point is that what you say is important for those unfamiliar with super user privileges to understand, but if you have used XP you have already been doing this inadvertently, and if you run Vista, Win7, any Linux distro, or Mac, you are already familiar with the concept of rights and probably just give whatever privileges when it asks.
Therefore, the real point for anything device or OS, not just your rooted phone, is to know where the software you install is coming from and make sure it is safe before you install it.
I wanted to root, purely so i can a) put a custom ROM on my HTC HERO and b) so i can install apps on the SD Card.
However, I have already installed the Modaco custom ROM and Cyanogen’s recovery image. I have not yet run out of space on my phone for apps. But after reading your post – I’m gonna think twice about adding ROOT, at least untill i have a full device..
Can you not install apps on the SD card without ROOT?? If not, this would be a great feature from Android that would prevent many people from going down the Rooting road.
Also, Even if you do ROOT your device. Do apps state that they need Root when you install them, ive not come across one that says this yet?
you dont hav
you can install app to your sd card instead of the phone by downloading the apps from 4shared.com into your computer then sending it to your phone.
Unless u have a flow chart u will never know how your changes will efect the sys for sure. Things may seem fine, u make a selection, all hell breakes loose. It could happen I programmed for years its hard to follow someones logic. It can be good thing “yes do your home work first” you’ll feel better .GOOD LUCK
I don’t have root but I’m quite happy with my phone the way it is.
Thanks for writing this, i don’t have the phone yet, but i’m trying to learn as much as I can before getting it. Is the moto cliq/dext any good?
I have a Moto Cliq, and it is my first Android device. I just read that someone has possibibly found a way to root the Cliq. My view is, since this is my first Android device, I’m going to wait until it’s lifespan is just about done, and I’ve moved onto a new device to try and ROOT it. That way, worse case scenario, I still have my new device.