No sympathy for the rooted users.

[Stang68]

I know I'm going to get flamed, beaten, etc, but almost all of the Froyo issues are happening to people who were rooted when they tried to update. I'm sorry, but I don't have any sympathy for you. Don't complain that the update failed and Motorola sucks. You knew it would bring on problems. Don't bring down the rest of us users who behaved (at least during the update).

/end rant.

 

[Camphill]

I was rooted and my update to 2.2 went just fine. Of course I'm no longer rooted though.

 

[bmaner_AC]

I was rooted and my update to 2.2 went just fine. Of course I'm no longer rooted though.

did you unroot before you updated ?

 

[jsaren]

I know I'm going to get flamed, beaten, etc, but almost all of the Froyo issues are happening to people who were rooted when they tried to update. I'm sorry, but I don't have any sympathy for you. Don't complain that the update failed and Motorola sucks. You knew it would bring on problems. Don't bring down the rest of us users who behaved (at least during the update).

/end rant.

I am rooted with 2.2 leak I have not done the OTA. My girl was on stock 2.1 no root nothing like that she did the OTA and now her phone is stuck on "M" logo and will not come out of it.. So it is not related just to root

 

[Stang68]

I am rooted with 2.2 leak I have not done the OTA. My girl was on stock 2.1 no root nothing like that she did the OTA and now her phone is stuck on "M" logo and will not come out of it.. So it is not related just to root

What have you guys tried to do to fix the problem?

 

[jsaren]

What have you guys tried to do to fix the problem?

We have only done a bunch of battery pulls. From what I am reading I can not flash to 2.1 sbf since she downloaded. The only option I was thinking of doing but I am waiting to get confirmation on is I have the leaked 2.2 on my sd card I was thinking of putting it into her phone, and putting that on, but I do not know if that will work. I do not know if I can get it into recovery mode to do it either at the moment. She is at work and the phone is with her.

 

[Camphill]

Nope.

 

[Camphill]

did you unroot before you updated ?

I did NOT unroot before updating.

 

[judasmachine]

The only problem I am having is everytime I press Battery Statistics it force closes. Not a big deal to me. However I would like to see it rectified.

EDIT: It is actually called usage statistics, and for some reason it just started working. Hmm. BTW I was rooted but unrooted before downloading the update.

 

[mflynn]

I Agree with the OP on this and also those people who loaded the leaked version of froyo who are now running to into issues as well. Little sympathy.

 

[Stang68]

We have only done a bunch of battery pulls. From what I am reading I can not flash to 2.1 sbf since she downloaded. The only option I was thinking of doing but I am waiting to get confirmation on is I have the leaked 2.2 on my sd card I was thinking of putting it into her phone, and putting that on, but I do not know if that will work. I do not know if I can get it into recovery mode to do it either at the moment. She is at work and the phone is with her.

So the phone Is unuseable right now?

 

[Itlan#AC]

Was rooted using one click on 2.1, did not unroot, had no issues upgrading.

Sent from my DROIDX using Tapatalk

 

[D2TSHR1439]

It has nothing to do with root and unroot. I just think there are more active users who a rooted and posting about the issues than those who are not. I have seen quite a few posted that they were never rooted and running stock and are having the Boot M problem. I dont think your assessment is correct, but thats just me .....


jsaren .... Can you boot into recovery and try a factor reset or wipe cache and date and then reboot?

 

[Stang68]

It has nothing to do with root and unroot. I just think there are more active users who a rooted and posting about the issues than those who are not. I have seen quite a few posted that they were never rooted and running stock and are having the Boot M problem. I dont think your assessment is correct, but thats just me .....

Well, what I'm saying is that rooted user having problems shouldn't be complaining to all hell or cursing out Moto. People with real, stock problems are obviously going to get our help!

 

[D2TSHR1439]

So your willing to help someone who stayed stock but not help a person who rooted with the same problem???? Everyone is experiencing the same problems ..... That doesnt make sense.

 

[thebizz]

yeah that makes little to no since. The update jacked up allot of phones. And had nothing to do with root. I could see if people were trying to load the update over a leaked version of froyo. But people aren't their going from 2.1 to 2.2 motorola screwed the pouch

 

[mflynn]

It has nothing to do with root and unroot. I just think there are more active users who a rooted and posting about the issues than those who are not.

I'm not sure that can easily explain it.

I think its more that that users who rooted their phones also made changes that were previously not allowed, unless you were root. Those changes are in my opinion the root (pun intended) cause for the update to fail.

The update expects a certain configuration, rooting alters that.

 

[DaRkL3AD3R]

Look its simple. Whether you rooted or not, is irrelevant. Now if you rooted, modified certain things like the framework, and DID NOT flash back to a stock setup then yes those individuals will experience serious problems updating.

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.

Root itself has NOTHING to do with the problems. It's the users who rooted and messed with things without flashing their phone before updating that have problems. Not to mention from what I'm reading many STOCK phones are having serious issues with this update as well.

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.

 

[Stang68]

So your willing to help someone who stayed stock but not help a person who rooted with the same problem???? Everyone is experiencing the same problems ..... That doesnt make sense.

It makes plenty of sense.

I'm talking about people who updated while rooted and are COMPLAINING. I have noooo sympathy for them. They should have known what they were getting into.

If you were a non-rooted user, then by all-means, complain away

 

[D2TSHR1439]

Wow ...... So the same problem occurring that has nothing to do with the root that would have happened anyway if you werent rooted, and those people cant complain. But the people with the SAME problem that just didnt happen to be rooted. Ok.