I'm classified as a noob, but have been reading over this forum for about two months now trying to gain as much knowledge as possible. I have learned a lot. But I don't really learn until I do "it". Unfortunitly I'm probably one of the last people in North America who doesn't own a PC, therefore I can't just do "it". Too, many bills, mortgage, etc...a PC purchase isn't possible at the moment. I have access to multiple PC's, but I can't really use any except for my parents to do rooting stuff...but they live 2.5hrs away.
So, my question today is... other then the initial root, what "mods" require a PC? Messing around in the file explorer I have on my phone, I see that if I was rooted that I could open the files I currently can't. And be able to see the code in the "notes" style that it's written.... through the "notes" style app viewer I have. So after I rooted, could I open say... the folders containing Ciq files, alter/delete them through my phone, then restart my phone and not have Ciq anymore? I see that I can flash kernals and roms straight through the phone, but if I wanted to "mod" the stock rom a bit...well, I wasn't sure if that was possible or not. Not sure if it matters, but I'm also hboot 1.5
gokart2 said:
I'm classified as a noob, but have been reading over this forum for about two months now trying to gain as much knowledge as possible. I have learned a lot. But I don't really learn until I do "it". Unfortunitly I'm probably one of the last people in North America who doesn't own a PC, therefore I can't just do "it". Too, many bills, mortgage, etc...a PC purchase isn't possible at the moment. I have access to multiple PC's, but I can't really use any except for my parents to do rooting stuff...but they live 2.5hrs away.
So, my question today is... other then the initial root, what "mods" require a PC? Messing around in the file explorer I have on my phone, I see that if I was rooted that I could open the files I currently can't. And be able to see the code in the "notes" style that it's written.... through the "notes" style app viewer I have. So after I rooted, could I open say... the folders containing Ciq files, alter/delete them through my phone, then restart my phone and not have Ciq anymore? I see that I can flash kernals and roms straight through the phone, but if I wanted to "mod" the stock rom a bit...well, I wasn't sure if that was possible or not. Not sure if it matters, but I'm also hboot 1.5
Click to expand...
Click to collapse
netbooks are very cheap. pretty decent models brand new with 6 hrs battery life around $299 on newegg/dell. i have one i've done java android application coding on in eclipse. there are also cheap/used laptops on ebay for under $100.
you can do a lot of things from the device but having a PC is probably best for keeping backups, editing/modifying files, decompiling/recompiling for ROM tweaks and coding.
i do mostly all my device modification over adb (android debug bridge) with the device including app installing, logcat for debugging/troubleshooting, shell for testing and mods, etc.
hope that helps!
I understand using a PC is preferred, crap I prefer it. I'm super tight with my budget right now, new house, f-ing credit cards, student loans, propane, child support, my wife....I just can't get one yet. Hoping after the new year. I plan on rooting and running stock rom until I get a good grasp of everything. But I wanted to do a couple mods (remove HTC and Android spy-ware mainly). It seemed like it could be done through the phone, but I wasn't sure.
To tell you the Truth since I used my computer to Root my phone I Haven't really even needed it again... And I'm Constantly doing things to my phone!!
Related
I have always been one to keep my OS and apps up-to-date, even using custom ROMs on my pre-Android, Windows Mobile devices. Right now I have the latest official ROM installed, but would like to apply/install some of the nifty things rooted phones can eg. SetCPU, Titanium Backup, etc. Now here's the newbie/naive question. Why doesn't the Android OS come pre-rooted? If we want to mess around with our phones and potentially turn them into expensive paperweights then that should be our decision. To me, going root seems to be a choice tricky to go to and difficult to return from, and one that disallows future "official" updates. Damned if I do... damned if I don't syndrome. Do the benefits so greatly outnumber the (perceived) risks?
My Hero, and the XDA app, made this post possible.
It doesn't come pre-rooted because of the security breaches that would allow. Think about it...
Get universal androot and you can use most of the programs you mentioned. Really simple. Click root and you have root - click unroot and you have a non rooted phone. Couldn't be simpler. You've been reading those out of date guides again
Even from a Custom ROM it's really easy to return. I don't know where you've got your information from but its incorrect or outdated XD
It's about the money.
Who would upgrade to a new handset when their existing one will receive perpetual updates from the community?
Again, new to Android so security breeches are unknown to me. I fairly regularly modded my WM phone (also HTC) but guess I am wary of the negative responses I read every so often. I am sure though that once I start on this platform there will be no stopping me. Regardless, even something as 'simple' as rooting elicits a number of "oh, I bricked my phone" statements. Mostly, I guess, I am looking for that (maybe not so) gentle push to get me going. Thanks for the responses all the same.
My Hero, and the XDA app, made this post possible.
O no - the security breaches are not android specific! If you have root (administrator) access on ANY system it is a security hazard. If someone somehow got access to the system they would also have full admin rights and therefore the ability to do what they like. It doesn't matter whether its Windows 7, Windows phone, PalmPre, Blackberry, iPhone - the reason phones don't come with root access is because it would make that phone a target for hackers. Also most people (like yourself) clearly don't understand what root access means. AFAIK there have been no major android security breaches - its meant to be one of the most secure platforms but it is at least partly because root access is not allowed by standard that it is so secure. For this reason modding your WM phone is just as risky (if not more) as doing it on Android - just no-one mentions the security aspects of it.
Rant over. Hopefully you understand a little bit more about what you're doing when you get root access now. In order to do so and start tinkering with your system there is a guide here for you: http://forum.xda-developers.com/showthread.php?t=645253
btdag said:
It doesn't come pre-rooted because of the security breaches that would allow. Think about it...
Get universal androot and you can use most of the programs you mentioned. Really simple. Click root and you have root - click unroot and you have a non rooted phone. Couldn't be simpler. You've been reading those out of date guides again
Even from a Custom ROM it's really easy to return. I don't know where you've got your information from but its incorrect or outdated XD
Click to expand...
Click to collapse
What? How? Did I miss this comming out.......oh yes I see it's in the Nexus section which I dont go near cos I have a Hero...however Thanks for the pointer
Oddly enough I did administrate a UNIX network years ago, and not that long ago a Windows 2000 server environment. Stupidly I am now realising the similarities and connections. A light just went on... of course, root. Unix prided itself on security, and a superuser (like I was) is king. "Rooting" (the word) used here just didn't seem the same. But what you are also saying is that the phones can be compromised from external sources, like any network? And/or via malicious software granted root access?
My Hero, and the XDA app, made this post possible.
Android has it's own user account control system in the form of the superuser prompt.
But it's easy to bypass If you're clever, although with universal androot, everyone should be careful what they do on non rooted handsets too.
Hi.
This is my first post on xda, and I am hoping to learn a lot whilst I am here.
I am not expecting any help here, but there has been small hype about getting android onto this phone. And I understand that you may be critical about noobs like me expecting an easy fix from you.
I appreciate that the idea makes no sense from many perspectives, this is mine.
I purchased the windows 7 phone 3 months ago, I was a complete idiot and fell for the sales pitch, the salesman promised me the earth, he said I would be able to WiFi Tether on the next update, he told me it would be better then the android evo 4 that I wanted.
As you are probably aware, I am a complete fool. I have however spent many hours on the phone with a certain mobile phone outlett, and my provider, neither will help. And I am stuck with the phone till 2013.
The phone's buyback price has gone down to 1/3rd what it was on the day I bought the phone.
I have now made it my mission to get this phone to run android. I feel so strongly I may even remove the windows logo from the bottom of my touch-screen.
I have already researched some, and expect days more research before I'll be able to do, whatever it is I need to do.
I am and will be keeping a log, of all my research, and hopefully can use what I learn to help people out later on.
So....
Any comments, or questions or support?
CleverNoob
I have picked up a few things. And therefore want to clarify,
I don't want to dual boot the 2 OS's, I want to REMOVE windows 7 and replace it with Android.
From what I gather this means I need to develop an android ROM to work with the mozart, and then Flash it to the phone...?
So my logical mind tells me to look for the android ROM that works on the most similar spec phone.
I am however aware that the firmware or something is different in the mozart, from the HD7 and does not allow for certain android commands to work, therefore the ROM (gingerbread?) used on the HD7 will not be remotely compatible with the HD7?
It seems that there may be a few options for the actual flashing of the ROM already available... So I am going to concentrate on learning more about ROM development now.
If anyone wants to correct me, point me in the right direction, or hurl abuse at me... feel free to do so
I do not know all that much about ROM development.
What about drivers though? Sure it is fine for the chipset as there are Android devices with the same chipset (CPU and GPU)... Although the WiFi, bluetooth, radio etc. I guess it's built into the SoC?
Drivers for the screen, capacitive buttons, camera etc?
I think if you look around, you should be able to find a phone similar to htc mozart and the name which comes to my mind is Nexus one and htc desire...
Although it depends on you that you extract drivers from the OS of both of those android based phones then extract drivers from your mozart and compare if they have same chipset....
I really wonder if it's possible to do all this virtually instead of physically installing OSes on phones for development purposes.
You didnt give up did ya mate!
All of the Australia Telstra Community who got Conned into buying the Mozart over an iPhone due to This Service Provider not having a Contract with Apple are 'root'ing for your Success
just checking if i got it right...
you want android in the mozart just to enable wifi tethering.
well, FYI, its been done and done bro, just unlock your device and install any of the excellent custom ROMs here. my notebook is tethered to my mozart right now.
but if you want to further explore the capabilities of the hardware, no worries- many good samaritans are already doing that. explore the development forums here and thy shall learn!
take care!
Tethering is working now, even with Telstra and no unlocking (7720).
This is my first post too! I was about to post something like yours. I have an HTC Mozart too and I want to install an Android ROM on it though my reasons are different.
As a software developer I have no experience about ROM development but I'm very interested.
So what did you do until now? Any success?
Hey guys,
I am really curious as to what it takes to build a custom ROM. I am very interested in building my own and want some pointers on the best places to start so I don't waste my time. Any advice will be useful, books, websites, w/e.
Thank you,
r3xx3r
get ready cause this one's going wayyy over your head.
Its one of those things where if you have to ask, you'll never know.
spitefulcheerio said:
Its one of those things where if you have to ask, you'll never know.
Click to expand...
Click to collapse
I really hate this mentality. People have to start somewhere. Sure they could spend years figuring everything out on their own. Or you could save them a year by pointing them in the right direction. There is such little discussion about this and it's honestly just annoying and a huge negative aspect about the development community.
EDIT: This is for HTC and I haven't watched it, but it might get you started: http://www.youtube.com/watch?v=94Az1kcQvc4
Also, you should definitely look through the source code for open source ROMs. I'm not a ROM developer so I can't really help you more than that, but I hope a real dev gives you an answer.
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Pirateghost said:
first and foremost, learn how to use ADB. if you cant use ADB without some kind of script/batch file to do it for you, then stop right here!
personally the first thing i learned was how the updater-script (at the time, we didnt have edify scripting, so it was plain-jane update-script) worked. have a look in a rom's zip file and learn the layout.
learn how to edit apks (decompile/compile) with apktool.
get comfortable with linux (this is just an opinion, as you CAN build roms in windows, but i have found it much easier on my dev laptop with ubuntu 10.10 64bit)
apkmanager is a good tool to have if you are on windows (there is a linux/osx version too, but i havent used it)
learn what zip-aligning means and what it does for your rom
learn what deodexing means and what it does for your rom
different devices benefit from different tweaks within your /system/build.prop . learn which ones work best for your rom (this requires a lot of flashing and testing on your own device)
this whole process is very time consuming and takes a ton of effort on your part. be prepared. while it is a lot of work, it is a lot of fun learning.
once you get proficient at building and tweaking roms, you can start learning how to edit smali
Click to expand...
Click to collapse
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Diviance said:
This is good information. I, personally, build Aura completely on windows with minimal assistance from cygwin. I use batch files for the common things I use on ADB and the like but I built the scripts myself, so it isn't like I can't do it manually I just don't wanna.
It is both easier and harder than it looks. Aura is the first rom I have built.
One thing, though, is to not accept the current ways as best. Things can always be improved. I have two common mods in my rom that are done completely differently in my rom, without either database editing through scripts or modifying smali inside apk's (the hotspot entitlement check and the 1 signal bar fix). No other roms for the Atrix (I haven't check other phones...) do it this way, not even Darkside which is based somewhat no Aura.
If you are building a rom through the Rom Kitchen... don't use the garbled updater-script it puts out. It mostly works, but it is trash and you won't learn much from it.
Experimentation!
Click to expand...
Click to collapse
Thanks for the input. I love hearing from other devs and the methods they prefer.
Sent from my Inspire 4G
this thread died quickly.
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
supermerkin said:
too bad because I want to do some studying up on it and creating some coolness myself eventually.
I know with iphones a lot of development was done right from the phone itself especially for app development, is there the same concept here?
and one other question, do you guys make any money off of these things at all? Im always looking for side work...
Click to expand...
Click to collapse
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Pirateghost said:
you can create scripts, push and pull files directly from the phone, so in a sense, yes you can work straight from the phone.
as for money...LOL...dont look to this for a secondary income by any means.
i have made all of $28 for my work on the inspire, and nothing from my work on the captivate
Click to expand...
Click to collapse
Hey 28 bucks is 28 bucks, granted I made 40 per screen when I used to replace iphone digitizers but money is money you never have enough.
Thanks for the info though!
Sent from my MB860 using xda premium
I spend a lot of time flashing my Rom when I am working on it. I usually don't push and pull from the phone since most users aren't doing that and I want to emulate what they will be doing.
As for money... Yeah, not a method of reliable I income if you intend to use it as such. I have probably had around... $125 donated to me by some incredibly awesome people.
If you intend to become a Rom dev, be friendly and responsive. People really appreciate someone who is willing to answer questions and give help where needed. Being standoffish like some I have seen is a sure way to get labeled with some bad words
Thank you guys for the responses. This is something I've been wondering as I've taken the plunge into modifying my Atrix. To say it's been addictive is an understatement. I started toying with the idea of putting my own ROM together pretty early on, so basic info like this is much appreciated.
Like someone said early on in the thread, everyone has to start somewhere so even seemingly small bits of info are always welcome.
The biggest hurdle is understanding adb commands and when to use them. Then, how to view the individual file strings inside the /sytem/build.prop and apks AND actually understand what it means. I have spent hours wandering around in root explorer look in folders and seeing what is inside. Pulling something with adb actually removes it from the phone right? Then I have to adb push back into the folder I pulled from. Should I use Ubuntu on my Win7 pc? I tried eclipse, installer r13, and I do have apkmanager but have yet to figure out how to actually use it.
I learn by doing what someone is telling me so reading it sometimes doesn't make sense since I can't "see" it and what it's supposed to look like. WIsh someone lived nearby to just to help get me started.....Beers and food on me LOL. Or at least had some time over the phone even.
Thanks Diviance (again) and to you PirateGhost for your help.
no adb pull does not remove it from the device. it copies to your local machine
as far as using windows vs linux. use whatever will make you more comfortable. i can assure you a lot of tutorials, and howtos are written with linux in mind, but if you can understand the basics, you will be able to translate it to windows. not to mention once you get into tearing down APKs, jars, dexes, etc....its all the same code inside no matter what tools you are using to get to them. i find linux easier to work with when it comes to stuff like this, some people think windows is easier.
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Phoneguy589 said:
If I were to get linux on my PC, would adb work within the linux evironment...meaning can I adb from linux and compile/decompile etc from there?
Click to expand...
Click to collapse
well you would compile/decompile directly on the phone unless you were using the sdcard....it wouldnt be pretty
you adb pull /system/file modify it, then adb push /system/file
it works the same in windows as it does in linux from that aspect. i just find working in linux easier.
here, this should help get you started somewhere, its not exactly like this phone, and the guide should be used as a reference and not a manual.
http://forum.xda-developers.com/showthread.php?t=915435
if you are technical enough, just by looking at that thread, you will understand a good portion of whats going on.
Thanks for all the help. Im getting bored flashing other peoples work and would like to help tweak things. And develop some stuff.
Thanks bro.
I am more than a little cofused regarding the functionality of Google store/Market after root of an android device. I have read seemingly cotradictory posts, some say there is no problem some give work arounds involving Roms. A newer post seems to indicate Google has done something that only alows Chinese android devices to use Market after rooting. Which is true? Do all devices even act the same?
I have an Archos that needed a fix to get it at all but I had not heard that Market didn't work after root until a friend mentioned it a couple of days ago.
Was this something Google did with intent?
My new Phone
Unlocked Bell Galaxy SIII (I747)
on AT&T
WavyA70 said:
I am more than a little cofused regarding the functionality of Google store/Market after root of an android device. I have read seemingly cotradictory posts, some say there is no problem some give work arounds involving Roms. A newer post seems to indicate Google has done something that only alows Chinese android devices to use Market after rooting. Which is true? Do all devices even act the same?
I have an Archos that needed a fix to get it at all but I had not heard that Market didn't work after root until a friend mentioned it a couple of days ago.
Was this something Google did with intent?
My new Phone
Unlocked Bell Galaxy SIII (I747)
on AT&T
Click to expand...
Click to collapse
I have used a number of Android devices, and while I have not rooted all of them, I do know that there are no problems witch accessing the Play Store with those that I HAVE rooted. You see, in this world of rapidly changing technology, humans are overwhelmed by the sheer amount of information they have to learn or process just to operate a simple device that is used for making calls. So, at times like these, there are people who tend to take advantage of the not-so savvy users and play with their mind by telling them that this won't work or that won't work. You can call them practical jokers or whatever.
In essence, rooting is nothing but gaining "root" privileges; that is, you take control of the device. The Play Store is nothing but a front-end for users to download apps which they would otherwise have great difficulty finding or getting to work. The Play Store doesn't do much. It download's the app that you want from it's servers and initiates the Package Manager to install the downloaded app.
Rooting does nothing to the Play Store. It is in fact a completely different scenario altogether. You GRANT the phone root privileges, and that may mostly be to modify system files. Other than that, "root" does nothing at all on your device. Rooting your device installs a Superuser app. This app is the GUI frontend that gains the root privilege after you give it permission.
Now, I don't know if Play Store has been officially launched in China or not. If it isn't, then rooting your device is the only way to get Play Store to work. It usually includes a modified version of Play Store that tricks the Google server into thinking that you aren't in China, even though you are.
So, you can root your device, at no cost to the access to the Play Store.
I hope this helped you.
Playstore/market after root?
gadgetroid
Thanks so much for your answer. I had asked a friend if he had rooted his phone (Sprint SIII) and he told me he did not want to loose the Store.
I said I did not think he would, but when I tried to confirm that I started to get really confused (doesn't really take much). I really did not want to mislead him. Is it possible that I have conflated what I have read about rooting with flashing a Rom?
WavyDroid said:
gadgetroid
Thanks so much for your answer. I had asked a friend if he had rooted his phone (Sprint SIII) and he told me he did not want to loose the Store.
I said I did not think he would, but when I tried to confirm that I started to get really confused (doesn't really take much). I really did not want to mislead him.
Click to expand...
Click to collapse
That's no problem at all. The thing in the Android world is that there are just too many devs who have their own ways and opinions of going about stuff. And then, there're the taggers on, like me, who haunt the developer threads and pick up 25-50% of stuff (and mind you, they hardly understand about 10% of the stuff ) and THEN form their OWN opinions and spread around half-truths to their friends to show that they KNOW something about developing, although in reality, they don't. Thankfully, this hasn't happened in Linux or Symbian.
Is it possible that I have conflated what I have read about rooting with flashing a Rom?
Click to expand...
Click to collapse
Yes, that is possible. You see, the majority of the custom ROMs out there for devices that are popular are either AOKP, CM7 or CM7 based. Stock ROMs differ greatly from the formers. Flashing an update.zip that contains the permissions and superuser.apk and flashing a custom ROM like CM7 are almost same. So it's VERY possible that you might've been confused, of course! And also, most of these aftermarket ROMs like CM7, MiUI and AOKP require you to flash "gapps.zip" which contains all the Google applications. If you do not flash that zip, THEN you will end up not having access to Play Store.
Hope this helped you.
Ahha!!:good:
Now if I can only get my main computer to talk w/ my SIII I can try my hand at this myself
Since I asked a lot of question on this forum I would like to share the answers with everybody and maybe help them.
NOTE: Please don't post any replys as I want to keep the post clean and room for updates, send me a PM if you have and idea or any fails that I made in this post, if this post helped you don't post hit just the thanks button. Cheers.
Current list of questions with answers(will be updated):
Why would I want to root my phone?
Is rooting worth the trouble?
Is rooting illegal?
Will I have any customer support?
Is it dangerous?
Isn't rooting a complex and difficult process?
Will I still receive operating system updates from my carrier?
Application updates?
What if I want to un-root my phone?
Do I run the risk of bricking my phone?
Could my phone overheat and explode?
Why would I want to root my phone?
Everything in a Linux system is a file, or is treated as a file. Since Android runs on top of Linux, it acts the same way. 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 updating the version of Android on your phone, 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. You'll find that the open source community is usually pretty helpful and encouraging new people to do new things is common. And when you get to the point where you can lend a hand to the new folks, pay it forward.
Is rooting worth the trouble?
The answer is a resounding yes. The phone is faster than it has ever been, the battery lasts longer, and have all kinds of new features, including free wireless tethering and notification-bar widgets. Rooting your phone is generally a fairly quick process, though the complexity depends on your specific situation. Once you're rooted your handset, you can begin installing apps (many directly from Android Market) that will take advantage of your handset's new capabilities. Installing custom ROMs (replacement operating systems) built by hackers is a longer, more involved process , and generally involves your wiping all the data from your phone, but even that is worthwhile.
Is rooting illegal?
Nope. You bought the phone, it's your equipment, you own it, and you can do what you want with it. No one is going to come and get you, and your service provider will not cancel your contract. In fact, the U.S. federal government recognized the legality of rooting a phone in July 2010.
What you will do, however, is void the warranty on your device. If you don't want to live without a warranty, rooting isn't for you. Personally, I finally decided to take the plunge when I realized that the potential benefits outweighed the potential consequences. My phone was becoming slow and buggy, with lots of force-closes, and I was just about eligible for an upgrade anyway.
Will I have any customer support?
Rooting can be daunting because there is no toll-free number you can call for help, and no governing body to which you can turn for definitive answers. But the collective process of rooting phones and creating custom ROMs has engendered cool and supportive communities. The user-generated forums out there contain a staggering amount of information; the CyanogenMod forum has offered answers to almost all of my questions, as has the XDA Developers forum, but you can find many more. No matter your question, the forums most likely already have threads that can answer it. If you really can't find anything, you can always start a new thread to ask your question. If you think you've really mucked things up and you need immediate help, many IRC chat channels specialize in support for rooters. (Download an IRC client on your computer and head to irc.freenode.net, where the channels #android and #android-root are particularly helpful.)
Is it dangerous?
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 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.
Isn't rooting a complex and difficult process?
Yes and no. It really depends on what model of phone you have. On many phones (such as the Nexus One, Motorola Defy, or EVO 4G) the process is incredibly easy: You can download an app such as Simple Root, Universal 1-Click, or Z4root that will safely root your phone with a single click. Those apps are no longer available from the Android Market, but you can find them online with a simple search and install them onto an SD Card.
It is important to note that different approaches will work for different phones. For example, Z4root will work on many Android phones, but it won't work on most HTC models. Some rooting apps will work on an early build of Android 2.2 (Froyo), but will not work on later builds (though more and more apps are being released for that now). Rooting is phone/OS specific, so make sure to check that the root tool you're considering is compatible with your phone. For other models, rooting may take much more work. You might be required to connect the phone to your computer and enter some lines of code in a terminal utility.
Fortunately, more and more root apps do not require you to hook up your computer and get in that deep. Do some research as to what is required for your setup, read some step-by-step guides, and be honest with yourself about how comfortable you would be trying to follow the directions. If it feels like you'd be in over your head, it's probably best to avoid rooting.
Note that generally rooting is even tougher to do if you use a Mac, as most of the software for doing this sort of thing is written for Windows or Linux.
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.
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.
What if I want to un-root my phone?
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!
Do I run the risk of bricking my phone?
This is one of the Internet's favorite bogeymen. "Bricking" is the idea that if you try to tinker with root access, you'll mess something up so it becomes completely unusable, and you'll essentially turn your phone into a paperweight. While that's certainly not outside the realm of possibility, the good news is that Android phones are generally very hard to brick. Yes, even the Droid X, which was purported to be the "unrootable" phone, has been safely rooted for quite some time (Z4root reportedly works with the Droid X).
If you do get caught in a boot loop, you may have to connect your phone to your computer and rewrite some code, but if you are patient and willing to do some more reading, you will almost always be able to find a way to at least restore your phone to its original state (read more on where that help comes from in the next section).
A common mistake that actually will lead to a bricked phone is running out of battery power in the middle of trying to install a custom ROM. The operating system only half installs, and that really is tough to fix. So always make sure that your battery is full before you install a new OS or ROM.
Also, just because a phone is rootable does not mean you can install any custom ROM you want. Differerent ROMs will work for different phones. Even the extremely popular CyanogenMod works for many phones, but certainly not all, so do plenty of research to make sure your phone is supported before trying to install a custom ROM.
Could my phone overheat and explode?
One of the major incentives to root your phone is the ability to overclock your processor to gain more speed (or underclock it to extend battery life). My phone has gotten considerably faster because of overclocking. When you overclock your processor, though, it will get hotter. If you try to push your phone too far and you don't set any fail-safes (a maximum allowable temperature in the overclocking utility), then you could burn out your processor. However, it is very easy to set safety thresholds to ensure that you don't do that.
SetCPU, the most popular app for overclocking or underclocking, allows you to set up various profiles.
Reading the rooting forums will give you plenty of advice on how far you can push your specific device and maintain stability. It pays to do some experimentation: Different phones behave differently, even if they're the same model.
Sources: androidcentral.com, pcworld.com
Useful threads:
[TUTORIAL] Unlocking, rooting, custom roms installing, going back to stock
[INDEX] HTC Desire X (protou) - Everything Desire X is here!
Reserved.