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.
Related
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!!
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
what is your question specifically?
just curious about what they are and do basically.
kevinallen4325 said:
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
Click to expand...
Click to collapse
I'll try and help.
First you must ROOT your phone. This basically grants you access/permission to FIDDLE with a lot of things you can't normally. I use the word *fiddle* loosley, meaning you can install root tools (like overclock) custom Roms, change system settings, flash themes... the list goes on. It's kind of like the equivalent to "jailbreaking"
Rooting is the "first and foremost"... basically do this first. and all other things follow.
kevinallen4325 said:
just curious about what they are and do basically.
Click to expand...
Click to collapse
Well the sticky in the main forum really is a good place to start, as all these terms are defined there:
http://forum.xda-developers.com/showthread.php?t=1483113
As well as step-by-step instructions how to root. That should get you started!
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It is much more than that. I wrote this out before, so I will copy it again:
People have problems when rooted because they are not careful or do not know what they are doing. Rooting gives you (to put in Windows terms) full Administrator rights to your phone. With this right comes responsibility, so you must be careful and do research. This is why rooting also voids the warranty. The phone is now open for the user to do whatever they want, and circumvent any restrictions put on the phone by the manufacturer (including those in place to prevent harm to the device). But like a computer with Admin rights, rooting allows you to install any application, any "OS theme", and tweak the hardware to do what YOU want with it, not what the manufacturer wants.
So please be sure to READ READ READ all you can before you start!!! You don't want a $600 phone coaster. Just browse the forums for a couple weeks and learn from the posts.
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
Android isn't like iOS. I had an iPhone for four years before my Note and I know where you coming from. What the other guy was saying is that rooting can be viewed similar to jailbreaking, but it is kind of completely different. You don't need to be rooted to use themes (or most of the stuff on Cydia). Rooting allows you to back up apps, flash custom ROMs, etc. Otherwise, you most likely don't need root.
tbran said:
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
Click to expand...
Click to collapse
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
kevinallen4325 said:
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
Click to expand...
Click to collapse
Trust me, if you go the root and custom rom way, you will never install an official update. not because you can't, but because it will be leaked and debloated months before it is official.
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
I rooted my Note a couple days ago and am still trying to figure out the benefits of doing so. I guess just spend time reading through this forum for the answers. That's what I am doing, but so far I see no benefit at all. The phone does all I want it to do so far. Maybe I am missing something.
Also, When i run quadrant, the scores are consistently lower after rooting the device then they were before. Not sure why though.
You are correct that the Note and newer phones may need no help. Not like two years ago. But, the big advantage to rooting even if you don't want to flash roms is Titanium Backup for app mgt and nandroids or full image backups--imho. The other like mentioned is earlier os releases. I have had ICS on my N1 for quite awhile and is still not on most new phones.
Ken
kevinallen4325 said:
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
Click to expand...
Click to collapse
If you are sure you are rooted, a dialog box with a little Android head wearing an eyepatch will pop up asking if you want to allow the application to have root access. You must allow it here.
Hi all - just signed up. I'm receiving my 10 Monday. I have an Infinity and wanted to give the Nexus 10 shot as it seems like a great tablet. I'm not likely to root either one. Is there anything you all suggest to get the most out of the Nexus 10? I'm fairly new to the tablet world although have owned an android phone for several years.
Thanks!
Welcome and congrats! Here is a link someone started that shares your question.
http://forum.xda-developers.com/showthread.php?t=2023608
Sent from my Nexus 10 using Tapatalk HD
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
TheEmpyre said:
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
Click to expand...
Click to collapse
I did read that thread but as I said - I'm not likely to root...at least not right away.
stormricker said:
I did read that thread but as I said - I'm not likely to root...at least not right away.
Click to expand...
Click to collapse
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
TheEmpyre said:
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
Click to expand...
Click to collapse
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
From what I've gathered, and from experience, I think the benefits of Root give the user a great deal more control of what goes on with his/her device -- that is, in part, what apps are accessing resources. For example, with my HTC One XL, I was able to install an app (which requires root access) that allows me to freeze apps while they are not in use -- launch them to unfreeze and use them when I need but when I'm not using, they aren't going to automatically run processes that drain my battery. I also installed a custom Kernel, and there is a root-required app that allows me to adjust my CPU frequencies and voltages to maximize battery life and performance.
I am relatively new to rooting devices, as I started in late October, but I can tell you that I have had a ton of fun doing it.
In any event, I really dont think rooting is that valuable to mainstream users if you ask me -- If you aren't looking into flashing custom ROMs or using special utilities/apps on your device then I wouldn't bother rooting/unlocking bootloader.
Since you asked risks I'll address that too: The risks are bricking (completely unusable) your device if you flash an incompatible ROM, but this is easily avoided by sticking only to flashing ROMs for the Nexus 10. You can also damage the components of your device if you overclock too much etc....Other risks are that ROMs are buggy sometimes despite the very hard work of the devs here (They are truly amazing here) but the bugs may take away from your experience potentially. There may be plenty of other risks but these are the ones I can think of so far.
I was completely unaware of root/unlock up until about 2 months ago and was completely new to the process. I was able to read great guides put together by the XDA community here that walked me through the process and I was successful in unlocking my One X and I now finally feel like I am getting the moneys worth out of my device that I payed good $$$ for.
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Benefits are basically the freedom to remove system apps and make backups of any of your apps. There are also a ton of root apps that allow you to customize your device the way you like it. With root, you get full control and the freedom to tinker.
Nexus devices are absolutley meant for consumers who don't root or unlock, but what is great about them is if you want to do either of the latter..it is much easier to do.
Also, I suggest you try and personally compare your N10 and Infinity before you read any of the general comparison threads. lol
Oh and welcome to the vanilla side of Android! :good:
- Mac
xIC-MACIx said:
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Click to expand...
Click to collapse
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
espionage724 said:
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
Click to expand...
Click to collapse
Absolutely agree with you on that one. My first Android device was a Infuse 4G. Every root and recovery procedure was absolutely manual. Not to mention most of the methods were hackjobs from the OG Galaxy S and required some extra coersing w/ Root Explorer and a terminal lol. Once I got my GNex, I could do anything I needed to do manually; I was actually rather shocked at how simple things were w/ a Nexus device.
Really though, I don't at all mind these toolkits, it might be important to learn what goes on behind the scripts, but lots of ppl here would have never attempted to tinker w/ android w/o some sort of script/batch automation. That said, i'm sure they cause quite a bit more traffic in the Q&A section when things to go wrong. lol
Thanks for all of the replies.
It should arrive today and I'll compare it with my Infinity first and then go from there.
Looking forward to know the N10
When I first received mine, I didnt think that I would recieve it till closer to the end of day, as stated with UPS. But it arrived at 10am! Hoping it happens the second time around for my replacement. Would love to have the whole day playing with it
Sent from my SPH-L710 using xda app-developers app
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.
Hi all. I am hoping for some very basic advice. I got a Kindle HDX 7 a few days ago. I have not connected it to wifi yet to avoid automatic updating of the firmware. When I go to settings>device>system update it tells me that my current firmware version is 13.3.0.5 installed on Jul, 30, 2013. From all I have read that is a good thing if I want to root my device.
The big question I have is if I actually should?
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
-Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
-How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
-How would I keep my device from upgrading automatically after rooting?
-Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
I would appreciate if the experienced rooters amongst you could advise me on this. Thank you!
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
snorklm said:
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
Click to expand...
Click to collapse
This is entirely doable, not all builds are buggy.
snorklm said:
Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
Click to expand...
Click to collapse
Not completely, but since root is what you are after currently, go to the dev section and check out the roundup on the rooting tool. Read through the posts.
However, it is simple for you to root. You can go to towelroot and do it that way. Regardless, I suggest reading the dev threads to see some of the other options. Also, there is some good info in the rollback, now what? Threads in this section.
snorklm said:
How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
Click to expand...
Click to collapse
All it does is give you the option of allowing root permissions to an app. Root in it of itself is perfectly harmless. It won't change the function of the device at all if you do not utilize this new power. However, if an app (or you), change the wrong file, it could be devastating.
snorklm said:
How would I keep my device from upgrading automatically after rooting?
Click to expand...
Click to collapse
There are some block updates threads. Probably the easiest is to use the kindle fire xposed plugin (I think that still works). Be careful with xposed. It does allow you to make changes which can make your device unstable.
snorklm said:
Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
Click to expand...
Click to collapse
Yes, and achieving root access is looked at as a security hole by Amazon. You also will be missing out on new "Features." This could include KitKat. Although, you can flash the new software with TWRP which if done correctly will be stable, but that will require a lot more reading. It is really only the custom builds which are unstable. They are buggy because they are not quite finished. Head over to the dev section to find out more. In the end, it all comes down to what you plan to do with it, and how much you plan to learn along the way.
Good luck,
Leko
Sent from my KFTHWI using Tapatalk
Hi Snorklm - welcome to the forums. The title of your post made my day
If you haven't already read through the response from Leko. Hits all the important points and mirrors what I was going to write (beat me to the punch).
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
I know you were hoping for a step-by-step tutorial. While that may become reality someday I suggest you spend an evening reading through the forums before deciding on a course of action. Yup, a ton of information is old/confusing but there is no one right answer for everyone. Ask questions along the way. Lots of folks are happy/willing to help if you've done your homework.
Good luck!
lekofraggle said:
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
Click to expand...
Click to collapse
Thanks for the overview and answering my questions! I'm still iffy on the whole process but I'm going to do some reading before I decide if this is for me .
Davey126 said:
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
Click to expand...
Click to collapse
Thanks for the reply. I'm especially grateful that you name-dropped some specific recommendations because it gives me a starting point to research. I have already read about TWRP (though as of yet I have no idea how to install it) and I will definitely take a look at HDX Toolkit.
I am probably going to try rooting while keeping an eye on the stock Android variant. I'm not sure if I'm ever going to be brave/clever enough to dare try that though. Bricking my device would seriously make me cry .
I have one more question about the Firmware versions (well, I probably have several, but this is the only one I remember right now.) I have seen somewhere on this forum that you can also upgrade the amazon firmware manually until you have the version you want instead of getting pushed to the newest one from amazon itself. Is that correct? If yes, which is the best version to stop on while still being able to root and keeping the option of stock Android open? I ask because I would like to strike a balance between a reasonably upgraded OS and one I still can do stuff with without getting nannied by amazon.
Here is where I recomend you start reading.
http://forum.xda-developers.com/showthread.php?t=2986004
This is the link for the thor twrp.
Here is how a normal device works.
You gain root permissions, and then if you mess up, you jump into a recovery and fix things. You probably (definitely) will lose some data, but you learn, curse, and move on with your life.
However, the bootloader of the Kindle hdx is locked. This means that if you cannot boot right, and you cannot get to recovery, you have a 200 paperweight.
Now, on the old firmware, brilliant people found a way to unlock (sort of) the bootloader. So, you have a pretty universal reset switch. This is why the recommendation is there to grab twrp. It really is helpful if you have a hankering to tinker. In reality there is less of a risk of bricking the device with it. Once you have it, then you can update to the newest firmware (in theory) if you do so the right way, you still keep twrp.
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
I hope this helps.
~Leko
Sent from my KFTHWI using Tapatalk
Edit: whether you go the easy route, and choose towelroot (just google it or go to towelroot.com for that route), the more involved twrp, or something in between, I highly recommend you learn what adb is and how to use it. The hdx toolkit comes with the drivers and it is not too difficult to use, but it is essential if you get into a sticky situation. Here is the toolkit link.
http://forum.xda-developers.com/showthread.php?t=2665683
lekofraggle said:
I hope this helps.
~Leko
Click to expand...
Click to collapse
Yes, this helps. Thank you! :good:
lekofraggle said:
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
Click to expand...
Click to collapse
@snorklm - you can go up to 13.3.2.6, secure root and still retain the option to later install TWRP and a different ROM without having to engage Amazon for a downgrade (you will still have to roll your device back to an earlier FW before installing TWRP but you can do this yourself). Note the 13.3.x.x series is based on the previous version of Fire OS (which in turn is based on Jellybean) but it remains perfectly serviceable. A lot is happening with more recent Amazon firmwares which ultimately may allow other ROMs and recoveries to be installed without having to downgrade to 13.3.x.x. Keep an eye on the forums.
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
I don't mind about the warranty as I think I will not break my Kindle Fire some how, just care about the services from Amazon Prime.
Actually I already contact Amazon service to roll back to version 3.2.5 and I'm waiting for the instruction email. My plan is going to root it, play around with the device then if something doesn't satisfy me, I will do un-root.
Would anyone show us the real advantages of rooting Kindle Fire here? As far as I know basic users just root their device to install Google Play Store which can be done on other un-rooted ones (like the method of Imma Wake) I still like Amazon service for Movies streaming so I'm a bit confused of what to do next, keep update it accordingly or give Rooting a try
Please share more your stories here.
Thank you
leoclark said:
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
Would anyone show us the real advantages of rooting Kindle Fire here?
Thank you
Click to expand...
Click to collapse
I ran with 3.2.6 (rooted) for nearly a year before installing a different ROM. I was able to obtain most apps from either the Amazon store or 1Moble. The primary reason I rooted was to squash various Amazon services that launch at boot and consume resources in the background (CPU, memory, battery). Goodreads, FreeTime and numerous communication services to name a few. I also wanted to install Xposed for a few modules I find especially handy and block OTAs to retain maximum flexibility. I side loaded many gapps but never installed the play store and associated services. Also Opera (never liked Silk). I retained my Prime privileges and for the most part enjoyed the mostly stock tablet as Amazon intended. Ultimately I began to miss some purchased apps not available elsewhere and longed for Apex or Nova. Other launchers can be made to run on Fire OS but the experience isn't as fluid. There is also something to be said about having a fairly consistent UI across my various Android devices.
While Fire OS isn't horrible I recommend rooting (when possible) and blocking OTAs to maximize current/future options As others have pointed out the act of rooting generally does not introduce instability unless the method used to exploit a vulnerability has side effects or the conditions for root are not fully met. There are some risks as you now have the power to brick your device. SuperSU (or similar privilege manager) is your friend and should keep you out of trouble if used judiciously.