What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Man.. wish i woulda rooted.

StepDroid

Official DF Vendor
Premium Member
no excuse whatsoever... I kinda feel stupid but, I always thought I would. FROYO is as good a reason as any... Seems like Froyo stock will make rooting more and more difficult to do going forward... is this true?

now I gotta learn how to do this... damnit!
 
EVERYONE should root if they are capable of doing it. There is NO DOWNSIDE to rooting at all.

For some people, voiding the warranty would be a downside. I did root, but it definitely isn't for everyone, really only for tech enthusiasts who can fix crap when it stops working. Encouraging everyone else to root just results in a thousand threads a day saying "OMGWTFBBQ I haxored my phonez and now it wont start."
 
EVERYONE should root if they are capable of doing it. There is NO DOWNSIDE to rooting at all.

For some people, voiding the warranty would be a downside. I did root, but it definitely isn't for everyone, really only for tech enthusiasts who can fix crap when it stops working. Encouraging everyone else to root just results in a thousand threads a day saying "OMGWTFBBQ I haxored my phonez and now it wont start."

The warranty is not voided if you install a stock rom back to the phone which is easy to do. Also I said "if they care capable of doing it." So I do encourage everyone who is capable to do it.
 
EVERYONE should root if they are capable of doing it. There is NO DOWNSIDE to rooting at all.

For some people, voiding the warranty would be a downside. I did root, but it definitely isn't for everyone, really only for tech enthusiasts who can fix crap when it stops working. Encouraging everyone else to root just results in a thousand threads a day saying "OMGWTFBBQ I haxored my phonez and now it wont start."

The warranty is not voided if you install a stock rom back to the phone which is easy to do. Also I said "if they care capable of doing it." So I do encourage everyone who is capable to do it.

It's a pretty tiresome discussion but I'll note just for the record that there are legitimate reasons not to root even if one is "capable of doing it." If your Droid is a toy and playing with it is a hobby, rooting can be a rewarding experience.

If, on the other hand, your Droid is an essential tool for activities like, you know, your job or, you know, your life, the downside of rooting is that you tie yourself to a development path that is unsupported except by a small and shifting group of hobbyists. And when you run into issues with your phone's performance and reliability you have just one more (very large) set of differences that have to be accounted for in any diagnosis and correction.

With a stock phone, there are literally millions of other users whose droids are more or less identical to yours. With a rooted phone running a custom rom, the chances are there are perhaps hundreds or maybe dozens of others whose configuration might resemble yours. Being an alpha tester for a developer can be an enjoyable experience as long as you realize what you're letting yourself in for. Otherwise, it may well make more sense to rely upon the extensive regression testing that a stock version of the o/s involves.

In short, if you're fortunate enough to have a Droid as a toy playing with it can be fun. Treated as such, there's nothing wrong with rooting and customizing the o/s to suit your fancy. If you have priorities other than tinkering with your phone, you may find the stock version of the phone meets your needs.
 
For some people, voiding the warranty would be a downside. I did root, but it definitely isn't for everyone, really only for tech enthusiasts who can fix crap when it stops working. Encouraging everyone else to root just results in a thousand threads a day saying "OMGWTFBBQ I haxored my phonez and now it wont start."

The warranty is not voided if you install a stock rom back to the phone which is easy to do. Also I said "if they care capable of doing it." So I do encourage everyone who is capable to do it.

It's a pretty tiresome discussion but I'll note just for the record that there are legitimate reasons not to root even if one is "capable of doing it." If your Droid is a toy and playing with it is a hobby, rooting can be a rewarding experience.

If, on the other hand, your Droid is an essential tool for activities like, you know, your job or, you know, your life, the downside of rooting is that you tie yourself to a development path that is unsupported except by a small and shifting group of hobbyists. And when you run into issues with your phone's performance and reliability you have just one more (very large) set of differences that have to be accounted for in any diagnosis and correction.

With a stock phone, there are literally millions of other users whose droids are more or less identical to yours. With a rooted phone running a custom rom, the chances are there are perhaps hundreds or maybe dozens of others whose configuration might resemble yours. Being an alpha tester for a developer can be an enjoyable experience as long as you realize what you're letting yourself in for. Otherwise, it may well make more sense to rely upon the extensive regression testing that a stock version of the o/s involves.

In short, if you're fortunate enough to have a Droid as a toy playing with it can be fun. Treated as such, there's nothing wrong with rooting and customizing the o/s to suit your fancy. If you have priorities other than tinkering with your phone, you may find the stock version of the phone meets your needs.


Interesting point of view, but how many real world examples can you think of where anyone who rooted had any issues with "work-related" applications that couldn't be fixed very easily?

The biggest issue I ever had was re-installing Googlemaps, which took me about 20 minutes. Never even close to having an issue with email (what I think you are referring to).

In fact, the only thing that happened was my phone got easier to use for work-related issues.
 
Rooting does this to your phone....................NOTHING.

Rooting only allows you to do things to your phone.

You can root, not do a thing and still get all the updates that Verizon/Motorola push, etc.....(you'll lose root though).

Rooting does nothing to your phone except give you ability/access/permission to your systems files.

Now...once you are rooted you can do things that get you in trouble....but rooting doesn't do anything to your phone as the way it sits right now as far a ROM, Kernal, OTA support, etc...
 
Interesting point of view, but how many real world examples can you think of where anyone who rooted had any issues with "work-related" applications that couldn't be fixed very easily?

The biggest issue I ever had was re-installing Googlemaps, which took me about 20 minutes. Never even close to having an issue with email (what I think you are referring to).

In fact, the only thing that happened was my phone got easier to use for work-related issues.

You seem to be missing my point. Even in its stock configuration the Droid demands far more attention to maintain its functionality and performance than, say, an average blackberry device. Adding another layer of configuration complexity to the Droid results in even greater demands for attention to the device and its operations.

This board has literally thousands of examples of "issues" raised by users that may or may not be related to (a) a custom configuration or (b) the particular version of a custom configuration they are running.

Frankly, with some exceptions I've been impressed by the diligence and commitment of developers who have churned out custom roms for the Droid without compensation. That doesn't mean, however, that a user running a custom rom can count on its quality and the testing it undergoes to the same degree that a stock version of the o/s receives.

Nor does it mean that if I decide to root my phone and install a custom rom because of specific features it has that I can count on the developer to be around to fix it. In most cases a user wouldn't even know whom to contact if the developer disappeared.

All of these risks and the requirements for literally constant attention to the performance and functionality of the Droid don't matter if one doesn't rely on the device as an essential tool and can view its use as a hobby. They make a huge difference to someone for whom a non-functioning phone is a major inconvenience.

Look, I consult on enterprise level technology decisions for a living. If a customer asked me whether he should root his phone to enable wireless wifi tethering, for example, I would strongly advise against it unless it didn't matter whether it worked or not. Likewise, if a customer asked if he/she should allow his/her employees to overclock their Droids to improve performance I'd advise against it. Just as I'd advise a client using pirated Microsoft Office software to get rid of it.

In each case, these actions involve both legal and technical risks, not to mention increased costs to monitor, track, and fix problems. None of these factors impact the average hacker. They all impact a user for whom time is money and risk mitigation is important.
 
Back
Top