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

Motorola clamps down on Droid X's leaked Android 2.2 upgrade with cease and desist scare

Thanks for sharing. I have to hope they're just protecting us from bugs, that way I can justify not so patiently waiting
 
bwahaha, I did the same thing on my Eris, upgraded to a leak and got screwed out of root for a LONG time (it seemed like a long time anyways).

Now, guess what, even after the Eris debacle I upgraded my X to a leak also, hahaha...

Glutten for punishment I guess.:)

Chris
 
I get it. they are trying to protect the customers. but moreso, they are trying to protect themselves. they dont want a flood of bricked x's coming back to the warehouse, because 5,000 people tried to do something they had no business trying.
 
Yeah, I could care less what Moto thinks. If they cared that much they would have put 2.2 on the phone to begin with at launch, but what did they care more about at the time? Oh that's right, coming out at the same time as the iphone 4.
 
sund0wn said:
I get it. they are trying to protect the customers. but moreso, they are trying to protect themselves. they dont want a flood of bricked x's coming back to the warehouse, because 5,000 people tried to do something they had no business trying.
Click to expand...


This is true......

Chris
 
sund0wn said:
I get it. they are trying to protect the customers. but moreso, they are trying to protect themselves. they dont want a flood of bricked x's coming back to the warehouse, because 5,000 people tried to do something they had no business trying.
Click to expand...

Why don't we have any business doing it? It's not unlike flashing a custom ROM...

Also, why would there be 5000 bricked droids? It doesn't take a rocket scientist to flash back to stock using sbf... In addition, I haven't run into one problem with Froyo and I am glad that I did it.
 
DECGTC said:
Why don't we have any business doing it? It's not unlike flashing a custom ROM...

Also, why would there be 5000 bricked droids? It doesn't take a rocket scientist to flash back to stock using sbf... In addition, I haven't run into one problem with Froyo and I am glad that I did it.
Click to expand...

Installing the update is a lot easier than using the sbf. There are a lot of people that updated that I am sure could never use RSD. Especially if they had any problems. I am more tech savvy than most people and RSD and drivers kicked my ass for a while yesterday after I bricked. Of course I am rooted so it was my fault I bricked and if you can't figure out RSD you shouldn't be messing with system files like I was, but I understand MOTOs point here. I just wish they would release the official update soon.
 
It's hard to begrudge the mfg the right to release software at their own discretion. Wanting to have their ducks in row from a test/dev/release/support standpoint is a good thing for customer satisfaction. And let's face it, the power users on this site represent probably less than 1% of all users, so we can't expect them to cater to us. If you have millions of users haphazardly loading test/dev software, it would be a frickin' nightmare for moto (and verizon).

That said, I upgraded to 2.2 (at my own risk!) and am quite pleased so far. :)

-TMc
 
DECGTC said:
Also, why would there be 5000 bricked droids? It doesn't take a rocket scientist to flash back to stock using sbf...
Click to expand...

Are you referring to the SBF file that Motorola also issued a C&D order to prevent from spreading further?

From a business standpoint what Motorola is doing makes perfect sense! The DX is their design and product. They want to insure that it presents a consistent image to the public. If there are unapproved signed images for the DX available on the Internet they lose the ability to control what is run on the DX (from an OS standpoint); and how the DX is presented to the public. From what we know this image was removed from a development phone. As such it's very likely not a final approved image.

Beyond this my guess is that it's Verizon and Motorola both who are concerned about people bricking the DX and trying to return it for exchange.
 
Grad said:
Just curious, has ANYONE on here bricked their phone doing the Froyo update?
Click to expand...

nobody here has bricked their phone. but, we, as users who research our devices, and figure out our own problems, surprisingly only represent a small portion of smartphone users.
i am willing to bet verizon had a ton of Dx's returned this weekend, because people updated to 2.2, and didnt make the effort to figure out why their phones were so buggy, and how to fix those bugs with the .sbf, or fix market issues by pushing thru an updated build.prop.

so when i talk about the people who had no business doing it... i dont mean any of the people here. i updated to 2.2. i just mean the people who heard about it thru the grapevine, learned just enough about how to do it, and then ended up with a buggy phone, and no understanding of how to fix it.
 
DECGTC said:
Why don't we have any business doing it? It's not unlike flashing a custom ROM...

Also, why would there be 5000 bricked droids? It doesn't take a rocket scientist to flash back to stock using sbf... In addition, I haven't run into one problem with Froyo and I am glad that I did it.
Click to expand...

no, i dont mean the people here. i think those of us willing to do the research, and those of us willing to figure out what to do if we make a mistake, should be more than welcome to do whatever we want. but, believe it or not, we represent a small portion of phone users.
motorola has to cover their tail against all the idiots out there who try something they dont understand, and subsequently return their phones because they'd rather just get a new one than figure out how to solve the problem they caused.

does that make a little more sense? i should have made myself more clear.
 
I bricked mine but it had nothing to do with the update, it was me screwing around with system files. That being said I am again rooted and back on froyo with everything running smooth.
 
I have a feeling that Moto is going to prevent those of us who upgraded from getting the real update. If this happens, can we just use the sbf to get back to 2.1, then get the official upgrade?
 
This is exactly why I will not install the leak. Granted its fun but in my mind it could cause more damage then desired. I can wait a few weeks for froyo. It will be great when its out. More power to those who do. They can't really prevent anyone from doing it. I bet its just not the final product yet. Haas anyone actually bricked their phone from updating to 2.2?
 
i need need to have this phone for a big longer before i decide to do anything that will void warranty on it... im hoping this update comes out soon..

it bothered me when my buddy got his update on his droid and my phone is newer... wtf
 
Clittzen said:
This is exactly why I will not install the leak. Granted its fun but in my mind it could cause more damage then desired. I can wait a few weeks for froyo. It will be great when its out. More power to those who do. They can't really prevent anyone from doing it. I bet its just not the final product yet. Haas anyone actually bricked their phone from updating to 2.2?
Click to expand...

i dont think anyone has bricked for good. some people may have bricked and not been able to figure out how to fix, but with the .sbf, it is always possible to fix if you just take the correct steps.
 
lakai113 said:
i need need to have this phone for a big longer before i decide to do anything that will void warranty on it... im hoping this update comes out soon..

it bothered me when my buddy got his update on his droid and my phone is newer... wtf
Click to expand...

exactly why he got it first. if you had your dx for (let's say) 9 months when the next release came out, and someone had a phone for a week, and they got it first, you'd be pissed i'm sure.

i understand where you're coming from, but those folks have been using the phones for quite some time. i think they deserve it first.
 
One cannot blame Motorola for the C&D. The leaked update is already ubiquitous so they can't stop savvy users from using it anyway. But you can't blame them for making it difficult for average users to use this update, especially when it could cost them time and resources in support for those who screw it up.

I don't mind that they try to stop the spread of the update as long as they don't do anything to mess with those of us who have already done it!
 
You must log in or register to reply here.
Back
Top Bottom