• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

BEFORE YOU ROOT READ THIS!

Just to reiterate, expound, and add to a few things Chief mentioned in the OP:

- rooting your device:

- is a two-edged sword: you get more control and can change things on your device, but if you change the wrong thing (i.e., system component), you can leave your device in an unusable state (boot looped, soft bricked, etc.)

- does install / change things on your /system partition; this means your device is no longer "stock" and you can no longer take/install an over-the-air (OTA) update; it used to be that all that was needed to install root was the su binary and the SuperUser.apk; this is no longer true for newer devices and several other files are installed and/or changed when rooting your device

- does not automatically give you a custom recovery or the ability to install a custom recovery--you (usually) need an unlocked bootloader to do that

- programs/apps cannot use root unless you explicitly grant permission via the SuperSU (or older SuperUser) app pop-up dialog
​
- a custom recovery:

- are very device-specific! you cannot (should NOT) use/try a custom recovery that is NOT meant for your specific device​

- typically requires that your bootloader is unlocked (there are some very clever ways around this like 2nd init, but these are rare)

- can be flashed over your current stock recovery

- can also be softbooted via fastboot boot (i.e., not flashed) in order to keep your stock recovery intact

- allows you to also make a Nandroid backup of the non user-data portions of your device; this can later be restored to take you back to a known, working state; it is highly advised you copy your Nandroid backups to another device like your PC for extra protection

- some well-known custom recoveries include TWRP, ClockworkMod (CWM), PhilZ, Amon_RA (older/early devices), and a few others...​

- you:

- should make a Nandroid backup if you are able to (i.e., via a custom recovery like TWRP or CWM)

- should also copy your Nandroid backup off to another place like your PC

- should NOT make a change to your system without being prepared (and able) to either fix/undo things or suffer the consequences​

- adb:

- is the Android Debug Bridge
- requires that you have USB debugging enabled on your device
- often requires special USB drivers
- is very different from fastboot
- can be used when your device is booted-up into custom recovery (you may have to disable MTP)
​
- fastboot:

- is used for communicating with the bootloader
- is very different from adb
- can only be used when the device is in bootloader mode
- often requires special USB drivers​

Cheers!

:)
 
Hey there...

Read all of the posts, and I'm a cat (don't pay attention to my avatar - it's new) who last rooted a phone back in '13 - a Samsung Galaxy Prevail, Version One. Many people asked, "Why would you root that piece of ****? Very little internal memory, and... sheesh... you're going to need a fast micro SD to take up some slack!"

I did it. It worked, quite well with a few of the ROMs that I located here that were stable. Alas, it died. Then, I had an LG F3 LS720 from Boost Mobile with a locked bootloader, that I fooled once with an init.apk... but, it would - due to the carrier - constantly remind you that a newer update was available (it was running Jelly Bean) - and, if someone in your life that you love very much hit the wrong radio button, thinking that she was doing the right thing:

Soft brick.

No way to implement CWMT, TWRP... so, I left it alone. It was pitiful.

My Android skills were great during the days of Gingerbread... now, things are quite complicated. I have a new Sprint HTC Desire 626s (running 5.1) that I would love to root, and get rid of the insane bloatware geared to teens - bloat that tracks your life online, creates consumer IDs, all of that crap - I've disabled Chrome, and use Ghostery. The only apps that I've allowed to update were from HTC themselves. Everything else was uninstalled to factory programs (sorry, Google - but, I love my privacy), and I only use apps that do NOT depend on tower location, or GPS (as my phone's are turned off).

If we get lost, or need driving directions - we have a Garmin...

So - if there's anyone in this thread that can get me going in the right direction - and, oh yes - I'll Nandroid backup my @$$ off, save the stock ROM and firmware in my PC (including stable Nandroids) - so that all I can have are the apps that I require - to help me learn more about how Android has evolved, and so that I can use Root Explorer and maybe an app or two for users with root access.

I'm all eyes.

LW
 
Last edited:
Hey all. I have specific reasons I need to root that I won't elaborate on here. The phone is a Motorola Razr M XT907 that was purchased using a very long-standing Verison billed contract. It's system ver. 182.46.15.XT907.Verison.en.US running Android 4.4.2.

I have a few apps loaded, and need to know if I should reset to stock before rooting and making my virgin nandroid backup, or if this would be a pointless piece of surgery.

Completely unrelated, I am seriously considering running the eset utility on this phone. Currently I only have free CM protections. As far as just getting this thing locked down well without bogging it down, would this be a wise choice for someone that runs eset nod32 on all their desktop machines?
 
(tl;dr bellow)
I'll be honest, I've been looking on rooting for the past few days, but the more I read about it, the more scared I get of even attempting to do it.

I was thinking about rooting my device simply for 2 reasons.
- Allow certain applications to turn my GPS location on and off at their own. (e.g. Tasker working together with Run Keeper)
- Allow AirMirror from Airdroid to work. (I just want to be able to write on my "To do" widgets with my computer keyboard from time to time)

But I've seen people that root constantly talking about revamping the system almost entirely.
I can't help but feel that I'm actually trying to chew from a plate that is too big for me. Or at least putting too much on risk for just 2 small conveniences.

For example, I wasn't even planning on downloading a new ROM, since I am very satisfied with the interface that came with my Asus Zenfone 2. However, from what I've read so far, it seems that I'll be forced to download another ROM regardless if I like the Stock one or not.... Because a future update from Asus could end up conflicting with my rooting and messing up my phone somehow.

But then, even if I decide "Ok, I'll download a new ROM and I'll get used to the new interface"... I then can't help but ask myself if there will be any chance that my Asus' applications will somehow conflict with this new ROM?

From what I could gather so far, rooting is somewhat easy to perform, but difficult to maintain (stable).

Is there some sort of rooting guide for people that just want to do the minimal necessary?

I really don't have plans of overclocking, deleting bloatware, changing things that came from factory, etc. I was just wanting to be able to reduce the safety standards of my phone for the sake of convenience.

tl;dr:
I have a Zenfone 2 (Model ASUS_Z00AD)

What's ASUS' stance on rooting? I mean, do their updates usually conflict with users that root?
In other words, could I root my device and keep everything from factory?

Thanks in advance. I appreciate any help or suggestions.
 
What you really need to find out is if there is a custom recovery before you root you're phone because of the capabilities that come with root. While its not a deal breaker if you don't have a custom recovery, but it is you're best bet to gain/flash recovery as a "rule of thumb" and flashing a recovery can only be and should probably be done directly after gaining root access.
 
Welcome to our AndroidForums, @Sucrilhus :).

Keep in-mind one of the biggest drawbacks of rooting is that it very likely will keep you from receiving future over-the-air (OTA) updates on your device. Attempting to install a future OTA on a rooted device can indeed render your device inoperable.

You can indeed "just root" and keep your device otherwise stock/factory (that's typically how I run my devices) -- but keep in-mind the warning about the OTA thing above. Also, things like Android Pay, etc. will likely detect root and therefore refuse to run.

Additionally, rooting without the safety net of a Nandroid backup (created in custom recovery) is a bit dangerous...

(on some devices, being able to use / flash a custom recovery is not necessarily related to be rooted)
 
And as long as u have a downloaded zip of a custom ROM for you're device on you're SD card you can always reflash it from recovery if a (Nandroid backup) fails, or just to get back up and running again incase of softbrick or any issues etc. by way of keypress combo for your specific device incase youre phone is frozen at boot logo etc. Yes nandroids are very Important for getting back to the state you're phone was in/way you had youre phn setupe before whatever may have caused you're "issue"/"issues" etc. But is not the only way to get back up and running again as long as you have a ROM that was built for you're device installed on you're SD Card. Just my point as to how recovery can save you're butt/phn if you use root access to do something abnormal that you're phone doesn't agree with. If you're unsure of anything root. Google is you're friend aswell. Researching on what root is, does, can do, why one needs/should get rid of the apks like Kingroot and placing SuperSU in its place, for instance SU rights won't pick up on a lot of root accessible apks in which need SU to run fully using King or Kingroot as you're root access granting apk etc. What system apks are safe to uninstall or not on you're model of phn. How to wipe a ROM right and fully so that the ROM you're flashing runs properly and doesn't contain remnants of you're last ROM within you're newly flashed ROM causing issues like data running slower etc. etc. There's a bit to know in which becomes much more familiar with the more you research and apply. Root itself is just that. An "access unlocker" if you will. One needs to know what and how to properly apply the things in which root can allow. One needs to be even more carefull of what one applys/tries doing with they're devices with Root without being fully aware of what one is attempting/doing. BE AWARE/KNOW WHAT IT IS YOURE TRYING/DOING with root access. Google is you're friend as well. Research, research, research, read, read, read.
 
Last edited:
Thanks for the replies. I appreciate them!

Crashdamage said:
@Sucrilhus: Is rooting really necessary for the 2 things you say you want to root for?
Click to expand...

That seems to be the case, though.

For example, if I try to activate Air Mirror from Airdroid, the app will display the following message:
"Only rooted devices are supported [by Air Mirror]. Your device has not been rooted."

Tasker is currently uninstalled from my smartphone, but I remember it saying something around the same grounds once I tried to make it have control over my GPS.

The nicest features those apps have to offer only work if your device is rooted.

scary alien said:
Welcome to our AndroidForums, @Sucrilhus :).

Keep in-mind one of the biggest drawbacks of rooting is that it very likely will keep you from receiving future over-the-air (OTA) updates on your device. Attempting to install a future OTA on a rooted device can indeed render your device inoperable.

You can indeed "just root" and keep your device otherwise stock/factory (that's typically how I run my devices) -- but keep in-mind the warning about the OTA thing above. Also, things like Android Pay, etc. will likely detect root and therefore refuse to run.

Additionally, rooting without the safety net of a Nandroid backup (created in custom recovery) is a bit dangerous...

(on some devices, being able to use / flash a custom recovery is not necessarily related to be rooted)
Click to expand...

Thanks, these forums are great!

Also, it's good to know it isn't weird to want to root and leave things factory-like still and thanks for the heads up on OTAs.

About the Nandroid backups. I'll definitely do them. We can never be too careful, right? Hahah

The-Truth said:
(...)BE AWARE/KNOW WHAT IT IS YOURE TRYING/DOING with root access. Google is you're friend as well. Research, research, research, read, read, read.
Click to expand...

True true! That's why I'm taking notes before even starting to do anything like that on my phone.
 
Tasked may want root to control GPS directly, through I don't know why. I never used Tssker much. But it should have problem just calling up an app that uses GPS.

You could use something like Google Keep or Evernote for to-dol lists.
 
The_Chief said:
If you're thinking about rooting your phone (for whatever reason), there are several vital things you need to know. One of these is called the nandroid backup.

A nandroid is your lifesaver... it takes a snapshot image of the device's entire current state, as it is right then, and saves it in a .zip file on your memory card or internal memory. I recommend all nandroid backups get saved to the external memory card, and copied to a PC or jump drive for safe keeping.

Once you root and have a custom recovery installed, your FIRST action should be to backup the phone in its pristine, stock rooted state. Save that as your baseline backup. Make backups regularly: at least every two weeks if not weekly, and especially before installing a new ROM or changing ANYTHING in the /system partition.

* -Let me say that again because it's IMPORTANT! Before you change ANYTHING in /system, STOP and make a nandroid backup in Recovery! It may be a trouble, but bricking your phone is even more trouble. -*

Both ClockworkMod and TWRP Recoveries have Backup capability. These .zip files can eat up your memory card quickly because they're large. As long as you're copying them all to the PC, you need only keep three on your card: the original stock rooted backup, and your two most recent backups. If the last one is somehow corrupted, you can always restore the one just before that without losing everything.

Want to ignore this advice because you're in a hurry? Here's what will happen.

If you STILL decide to change something in /system and you don't have a backup, you will have forever altered how your phone works... and it might not work at all. You can't get that original file back: and no, a factory reset won't fix it (that only deletes the /data partition and does not touch /system) and you will have a broken phone on your hands with only a couple of possible solutions... and none of them are fast, cheap or easy.

So save yourself from having to buy a new phone or sending yours to a distant repair facility for a costly re-flash to stock... make nandroid backups often. You can never have too many nandroids. You CAN have too few.

If you have any questions about nandroid backups, just ask! We're all here to help you, and we'd much rather help you learn how to make nandroids than help you TRY to restore your bricked phone because no nandroid is available.

For even more information on rooting (and you need to read & learn as much as you can before you start), read this great post:

http://androidforums.com/threads/rooting-best-practices.450904/

And remember: if you're unsure of what you're doing, STOP. Ask questions BEFORE you proceed! The last thing you want to have happen is to be in the middle of a system rewrite and your battery die on you while you're frantically asking questions. We're here to help you learn!

:)
Click to expand...

Thank yu The_Chief.
 
After root, Recovery. After recovery nandroid stock ROM. If any available for you're device try out a sweet custom ROM if so inclined! But you must know you're way around you're devices recovery to use recovery obviously. So read, read, read folks!
 
if you want to create nandroid backup, but your device is not supported by cwm or twrp then follow this step-by-step tutorial...
you will also create custom recovery for your device at the end of backup process...
 
funkylogik said:
I've no idea why your phone is giving you that message but you certainly DON'T need root.
Root just gives the user and root apps access to the system partition of the phone that is locked down to prevent people messing their phone up.
Some of us like to tinker with the system so we root. When is the phone telling you this? Was it an app?
Click to expand...
No of course one doesn't "need root" but if onevwants to run an unfettered O.S. and do all kinds of sweet things like run cool custom roms, cust OV kernels and SD memory expansion hacks etc. Root is the very begining and first door you must "unlock" along you're freeing you're locked down android path. Did you not pay for the device? Than You should be able to run you're device as free as possible and how you want. But plz know what is you're doing? And plz after root gain recovery and learn you're way around it. Its you're key to Nandroid backups & knowing how to save you're ass! Read, read, read. And know you're way around each step, tweak, hack and mod/optimization you attempt/and or make. Funkylogics right though youre device only reveals unrooted with root verification apks and root a device apks and root attempts alike. Read like mad. And ask me whatever. Glad to help. I been in you're shoes [emoji6]
 
kawasakiinit said:
HI

I have rooted my galaxy s2 with kingo root and was looking at what to do next with it being new to rooting so i went on the hunt for knowledge on the web but my laptop was attacked with loads of malware when trying to download siyah cwm or something like that i think so now im cautious after its taken me all afternoon to get my laptop back to normal . would you please be able to offer me advice on what to do next ? i have read so much now im confused ,i try not to ask questions on forums that have been asked a million times before so my apologies in advance ..

my main issues are

what firmware?
cwm ? what ever that is (i think its a kernal i need but not sure) being honest i dont know what a kernal is lol.
and i have odin on my laptop and my phone is unlocked but i have un rooted it again till i know what im doing .

model gt-i1900
android 4.1.2 jellybean
baseband version i9100xxms4
kernel version 3.0.31-1497824 dpi@dell133#3
smp preempt mon dec 23 22:00:54
kst 2013
build number jzo54k.i9100xwms3

thanks very much

dave .
Click to expand...
Hey there, CWM stands for (Clock Work Mod) which is a custom recovery. A custom kernel usually implies OC-UC over clock and under clock. Meaning you can control you're androids comp cores highest and lowest end speed which is ultimately speeding you're phone up or slowing it down to save a lil battery. CWM is recovery Kernels control comp cores, speeds etc. You will learn don't rush. After Kingrooting should you root again. Use flashify to download proper recovery. Get that far and hit me back!
 
Himanshu Raj said:
Could you tell a bit in detail about nandroid backup ....what exactly it is and how to use it..!!!
Click to expand...

Welcome to our AndroidForums, @Himanshu Raj :).

A "Nandroid backup" is a partition-based backup of your device done from a custom recovery (like TWRP, ClockworkMod (CWM), Philz, Amon_RA, etc...).

It's a near backup of your entire device, but typically only the /system, /data (excluding any "SD card" mounts), /cache partitions are backed-up (but you are usually presented with the option to backup other partitions like /recovery, /boot, etc.).

Keep in mind that simply restoring a backup is not all that needs to be done--you often have to do wipes of selected partitions depending on the ROM you are returning to.

edit: also see:

 
You can't be so right, I rooted my phone and I started to mess up with the system files to fix the binary files, now the app that I used to root (Kingroot) it's a part of the ****ing system and it doesn´t let me eliminate it. So I had to disable the app but it's still there. So please, listen to him, for me it's too late because my phone isn't a brick but I changed it forever
 
You must log in or register to reply here.
Back
Top Bottom