No sympathy for the rooted users.

[tntdroid]

I listened to birdman and staying on the leak 2.2 with Flyx untill this is all worked out. What's the rush the the official 2.2 anyway.

Sent from my DROIDX using Tapatalk

 

[sniffs]

Root has gotten a bad rap recently.

OP, imagine this, imagine buying a new laptop from Best Buy, but ONLY EVER BE GIVEN "USER" priveledges. Imagine not having access to your file system, or do what you want with YOUR hardware. Imagine not being able to uninstall the garbage that PC manufacturers put on the laptops, or not being able to re-install vanilla Windows..

Root = Administrator account. Plain and simple. It's called ROOT on Linux, it's called Administrator on Windows.

Not sure about you, but I don't like being told what to do with MY hardware. I bought this phone, it belongs to me. All Verizon is doing is providing service.

Same thing with your TV.. imagine only being able to watch shows that Time Warner, Cox TELLS you to watch.. f that..

 

[DaRkL3AD3R]

root has gotten a bad rap recently.

Op, imagine this, imagine buying a new laptop from best buy, but only ever be given "user" priveledges. Imagine not having access to your file system, or do what you want with your hardware. Imagine not being able to uninstall the garbage that pc manufacturers put on the laptops, or not being able to re-install vanilla windows..

Root = administrator account. Plain and simple. It's called root on linux, it's called administrator on windows.

Not sure about you, but i don't like being told what to do with my hardware. I bought this phone, it belongs to me. All verizon is doing is providing service.

Same thing with your tv.. Imagine only being able to watch shows that time warner, cox tells you to watch.. F that..

qft +1,000,000

 

[Dural]

...Not sure about you, but I don't like being told what to do with MY hardware. I bought this phone, it belongs to me. All Verizon is doing is providing service...

Completely agree. I support your right to Root, unlock, etc. The problem is that when you do so, you accept the good, the bad and the ugly. VZ/Moto is under no obligations to configure their OTA to accomodate or provide support for your off-spec configuration. On the contrary, their responsibility is to the average user who is spec. Have to admit that the majority (but not all) of the problems this am are in those phones which are/were rooted or pre-released. The update is getting a bad rap in no small part due to the users who did significant mods on their devices.

 

[anon(19758)]

Now if you were a SMART root user, and you flashed to stock and THEN updated the phone, you'd essentially have a phone thats no different than your Aunt's Droid X because she doesn't know what root is.
...
On the flip side I will say this, I have no sympathy for anyone who ONE CLICK ROOTED. That's about the dumbest concept around and I would only say you're excused from using it if you already had experience with manually rooting first, and are just aiming to save time. With the risks involved with rooting and modifying the phone, anything you can do to spare yourself from EXPERIENCE and KNOWLEDGE is probably the DUMBEST thing on the face of the planet. "Herp derp I have no clue what I'm doing, it's effectively dangerous for my phone but I'm going to jump blindly into this without having a clue. OH SHOOT MY PHONE IS BRICKED WHAT NOW BIRDMAN SAVE ME." With these individuals I agree 110% with you OP. No sympathy for them. But don't make a blanket statement that its all because of root itself. It's not.

Problem is the users.

Root = Administrator account. Plain and simple. It's called ROOT on Linux, it's called Administrator on Windows.

What they said. I one-click rooted because of the easy unroot option, and i wanted to explore root abilities. Same reason I jailbroke my iPod and downloaded hybrid OS builds on my BB. Tweaking. Knowing full well that if I borked it, it was on me because I was the one who borked it. Not the thread or individual I got the instructions from.

Also. I was rooted on the 2.2 leak. Then I SBF flashed, factory reset, wiped cache, rebooted, activated, and downloaded it just effing fine.

And I just explained root to someone like that yesterday. That's all it is. Think about how often your Vista pops up the stupid "do you want to do this" prompt. It's just popping into the Windows version of Root and then back out.

 

[besjr69]

I would suggest booting into recovery and doing a wipe/factory reset. I had this issue with the leak and going back to the SBF and it fixed it both times.

 

[Bald Steve]

I listened to birdman and staying on the leak 2.2 with Flyx untill this is all worked out. What's the rush the the official 2.2 anyway.

Same here. I'm an admitted n00b that knew nothing about modding two months ago, and although I'm learning I used one-click root and ROM Manager to get 2.2 and FlyX. My phone is dialed in perfectly right now, so why mess with it? I haven't had any problems with the leak other than the new battery manager crashing for a few days (but that has somehow resolved itself). More experienced and qualified people than I will find a way to keep us in the update loop, and I'll gladly pay them for their hard work. It's like the EVO Froyo update all over again - Bricks, bricks, and more bricks. I'll wait. Yoda taught me well.

 

[thebizz]

I agree with both sides motorola doesn't owe the root user anything. Nor are they responsible for ensuring a valid update path. Its on the root user to understand what's goin on research and learn but if said person jakes I will help in a heartbeat. Because how else are you going to learn but I emphasize read and be patient. It was said over a month ago that if you delete things and change them the update will fail. I hate what Motorola is doing though say you install this version of Froyo and something goes wrong with the install you can no longer sbf your phone due to this cat and mouse game their playing so your stuck asking for help or taking your phone to some incompetent vzw employee. That either doesn't know what root is. Or of going to blindly claim that your phone is rooted when it hasn't been. Because they were given a broad thing to look for with root users that they themselves don't understand.
I had to get my d2 replaced because it bricked itself trying to install that small update. The first thing they said was that I was rooted when I wasn't because it wouldn't boot past the m and wouldn't flash the sbf. Their looking at the stock recovery telling me its a rooted one. They had to boot into recovery on a display d2 to prove my point that I wasn't. Its dumb and the d2 has turned me off of Motorola all the resources going to blocking root could be put to use in making blur great but it isn't

 

[moosc]

Its simple it's not root vs nonroot. The update would be fine for all if vzw/moto. Didn't tinker with the keys/signature. There trying to be smarter then the developer community and it bit them in the azz. If you enjoy your bloated, locked Droid have at it. Ill stick with my clean rooted bloat, blur free and themed X. That will spank your stock X.

 

[bloodoak]

Most of the issues I've seen people having this morning come from 3 categories:

1) people who rooted and then deleted/renamed stock apps, which anyone who spent 5 minutes reading the forums when the leak came out could tell you you have to restore back to default by reinstalling them or sbf flash.

2) people who installed rom manager and didn't remove all of koush's bootstrap before running the update.

Both of these categories would be easily solved if people had just researched a tiny bit before trying to update.

3) stock users that updated and found out that verizon didn't fix some of the major bugs that were in the original leak when they released the official update.

The slide lock issue, m logo continuous reboot, battery status FC, market issues. All of these were discovered within the first day of the original leak coming out. Regardless on how moto/vzw feel about the fact that it was leaked, thousands of us basically beta tested this for the last several months and they didn't even fix the build.prop?

Unacceptable.

 

[thebizz]

^^ and that's what pisses me off
Or the stock users that get bricked I doubt everyone that gets bricked is rooted
And its not the build prop that's the problem the version released may not be updated in googles system