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

Root Rooting help?

Hey apple2005!

I rooted a while ago (before the update), but have found the following for you:

http://www.youtube.com/watch?v=IODIH0TTO-w

I can only go by the comments on the video but it does appear to work. If you do go for it, let me know if it works and I will get the link put in the All Things Root sticky :)

Thanks D-U-R-X for your help. I am unable to follow the video. One more thing to clarify is that I want only root access and not installing any custom rom. I am happy so for with stock rom. Further i want to update the usual way after rooting.
 
Upvote 0
Once you have rooted, you can install stock, rooted, firmware :)

If you root, it is not generally a good idea to take OTA updates though. Usually, a couple of days after an atOTA update, the devs bring out a rooted version of the stock firmware though :)

Thanks once again. At the moment, I can't Afford to put myself into trouble. I don't know how to do that? And further many people are complaining of the moded Roms as well. So I want root only at the moment.
 
Upvote 0
Thanks once again. At the moment, I can't Afford to put myself into trouble. I don't know how to do that? And further many people are complaining of the moded Roms as well. So I want root only at the moment.
One of the things that I just love about the Android OS is the simple but powerful security implementation. When a person "roots" an Android device, they override a signifcant amount of that protection in exchange for some other benefit.

I repeatedly get the impression when reading posts from various users that many don't really understand that the risks imposed by rooting may be much higher than those of installing custom ROMs. The worst thing a custom ROM can do is brick your device, but rooting an Android device can "brick" your personal security if not managed very judiciously.

Considering the wide variery in experience levels of users with respect to Android and Linux internals, it seems reasonable to include a note with the "rooting" tip in this thread to warn of the risks, which are not limited to merely bricking your device. I suspect that most users who "root" their devices do not understand the risk, and so are less likely to be able to protect their private data, or prevent the installation of malicious software in their devices. All it takes is one app to install a worm. Once the worm installed, you could delete the carrier app, but the worm would remain as part of your system, indefinitely. You'd go about your business using credit cards, paying bills, banking, etc., feeling perfectly safe for days, weeks, months, and then wonder why your accounts were suddenly being used by criminals located 4000 miles away. A worm may do little more than act as a nuisance, help someone steal your identity, or make you and your device unwitting accomplices in criminal activity. The options are endless.

Your risk is greater when you are personally using root access also. I have been a "root" user on various *nix systems for many years, and I have seen significant problems caused merely by accident when root users were just slightly inattentive, even some who were fully aware of the risks -- including myself. This form of risk is less costly though than the malware type, because it is merely of the bricking sort.

I was thinking of writing a more detailed post about this, but I figured that by now a number of folks had probably already done that, and I was right. I found this blog on the topic to be very simple and quite accurate: The dangers of rooting your Android phone | Android and Me.

This is worth reading also: https://www.securelist.com/en/analysis/204792222/Mobile_Malware_Evolution_Part_5

When you root, you do a part of the job that the hacker would otherwise have to do before attacking. It's true that hackers can use methods similar to what you use to root your device to gain access anyway, but that takes more specific effort than is required for attacks on devices that are already rooted. Restated, generic attacks can be used on almost any rooted device, where instead for non-rooted devices, more difficult device and version specific attacks are needed. There is apparently already some older malicious code out there that reverts to just using existing root privileges if an attempted crack at rooting does not work on a given device.

Giving root privilege to an app produced by a person you don't know is like giving a complete stranger a master key that works on your car, your house, your bank, etc. Malicious software can be very stealthy... so sneaky that you may never know that you have been attacked.

If you do root, understand the risk so you have a better chance of protecting your security. If all you use the tab for is browsing, Angry Birds, and solitare, maybe you can throw caution to the wind. If you use it for more sensitive tasks, realize that you are always going to be at greater risk than if you had not rooted, and be very stingy and cautious about giving apps such access.

For any dedicated "rooters" who might read this: Please don't misunderstand my point. I think that it is very cool that there are so many great ROMs available, and that rooting is an option. I plan to root one of my devices and try a custom ROM when I get time. The point of this is merely to inform/remind folks of the risk, not to berate what can be a reasonably safe and rewarding practice if managed very carefully. ...but this particular post of mine is not intended to point out the many rewards, because that seems to be well covered already. This is merely to balance that a little more by warning of some potential costs. I just thought that potential root users should also see more than the typical "brick" or voided warranty.
 
Upvote 0
That is an excellent and easy to understand explanation of Android security from the user perspective, and is as valid today as it was a few years ago.

The only thing that I would add to it today is relative to what I've already discussed in my post about "root" above. More specifically, if you read through the full list of permissions detailed in that article, keep in mind that when root privilege is granted to any app, it effectively opens all of those other permissions at once, and adds more, such as permission for full OS access, to both read, modify and add to operating system software or data, etc. Such changes to the system cannot be fixed or purged by a Factory data reset.

I looked at the "thanks" on that post, and am impressed (but not surpized) at how popular it has been. This seems like a very good place to reference it. Thank you.
 
Upvote 0
That is an excellent and easy to understand explanation of Android security from the user perspective, and is as valid today as it was a few years ago.

I looked at the "thanks" on that post, and am impressed (but not surpized) at how popular it has been. This seems like a very good place to reference it. Thank you.

I just thought that the permissions and security tips seemed to fit in well with what you were saying :)


The only thing that I would add to it today is relative to what I've already discussed in my post about "root" above. More specifically, if you read through the full list of permissions detailed in that article, keep in mind that when root privilege is granted to any app, it effectively opens all of those other permissions at once, and adds more, such as permission for full OS access, to both read, modify and add to operating system software or data, etc. Such changes to the system cannot be fixed or purged by a Factory data reset.

I agree that you must be careful about what you do... you actually have to give apps root permission though, they don't automatically get it. I only give root access to stuff I trust... as an example, I use Titanium Backup to back my app data up (I like to change my ROM's every now and then) and I have to give it root access using superuser.
 
Upvote 0
Thanks Mrhelper and DURX again. I am not happy to root my device but what to do? There are some essential applications which without root access will not work. Like another member said above, titanium backup, like droidwall, like orbot.
Would you like to tell us what to do if you need those applications? Is there anyway to use those applications without rooting. Thanks. No rudeness is intended.
 
Upvote 0
I agree that you must be careful about what you do... you actually have to give apps root permission though, they don't automatically get it. I only give root access to stuff I trust... as an example, I use Titanium Backup to back my app data up (I like to change my ROM's every now and then) and I have to give it root access using superuser.
I understand and agree completely. There are some major conveniences in having root and then allowing select apps to use it. The whole point of my post was to increase understanding of the risks, and how important it is for users to be very conservative about which apps they allow to use root privilege. The post you referenced just added the icing on the cake -- i.e., if a user is concerned about allowing location access, network access, or sensitive personal data access, then they need to keep in mind that allowing apps to use root opens all of that and much more. You really have to trust your app developers for root to be reasonably safe. I like the comments in that post you linked about how you need to really check with the user community if you are uncertain about an app before giving it root permission, and read app reviews carefully. There were also some very good points about ensuring that you only download apps from reliable sources.

Thanks Mrhelper and DURX again. I am not happy to root my device but what to do? There are some essential applications which without root access will not work. Like another member said above, titanium backup, like droidwall, like orbot.
Would you like to tell us what to do if you need those applications? Is there anyway to use those applications without rooting. Thanks. No rudeness is intended.
The important thing to take away from this is that if you are armed with this knowledge, you can better mitigate the risks. You have to decide how much any particular app is worth to you, and weigh the permissions required by it against the risks. That point is true for several of the permissions, not just root, though root clearly imposes the highest risk. There are certainly as many opinions as there are a500s about which apps are essential, and every owner has to make the decision on how much risk they want to accept relative to the benefits of any given app. I won't even begin to presume that I or anyone can give a general answer that resolves all of that for everyone. It is certainly great to have the choice.

On a similar note, I would prefer that vendors provide owners a safe front door method to access root and then shut down back door root exploits as soon as they can. This would possibly reduce the incentive of developers to crack their own devices, because they would have already been granted access. I believe that this practice could reduce external root-based threats considerably. If something I own is locked so I'm restricted from using part of it, then I'm more likely to bring out the tools to break it open. If I already have the key, why do all that work? If vendors are concerned about the service issue, they could just include a read-only recovery ROM or a recovery SD card to restore the system to factory specs if needed for diagnostic purposes. Of course, that's just a wish, and not likely to ever happen.
 
Upvote 0
On a similar note, I would prefer that vendors provide owners a safe front door method to access root and then shut down back door root exploits as soon as they can. This would possibly reduce the incentive of developers to crack their own devices, because they would have already been granted access. I believe that this practice could reduce external root-based threats considerably. If something I own is locked so I'm restricted from using part of it, then I'm more likely to bring out the tools to break it open. If I already have the key, why do all that work? If vendors are concerned about the service issue, they could just include a read-only recovery ROM or a recovery SD card to restore the system to factory specs if needed for diagnostic purposes.

THIS ^^ :)

Android is open source... I guess I understand why devices have some sort of lock, so people can't just start messing and screw things up... but I 100% agree with you... if it was straight forward... an option to allow root access without having to hack/get round security, then it would be better. OK... put warnings on it saying that, should you allow yourself root access and screw your system, you are to blame, not the manufacturer! :)
 
  • Like
Reactions: apple2005
Upvote 0
I was scared to death to root my tablet. But push came to shove and with the help of Mrhelper, I got the courage and rooted my machine. It'S still working properly, my ears didn't turn upside down, my arms are still attached and my eyes didn't stick cross eyed. So I guess I'll be ok. Rooting was the only way I was able to use my tablet as my GPS device. So thanks to alot of people in the forums here, I didn't brick my tablet. AS a matter of fact, I had read several posts on how to root and was just dazed and confused. I did a google search and found one that was easy to folloW and after on click it was a done deal.
Now I am able to use my taBLET AS IT WAS INTENDED.
 
  • Like
Reactions: apple2005
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones