Database Users

Full Revert from DamageControl2.0

I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?

You have to use either Sprint 1.29 RUU or Fresh's 1.56 RUU. That will make it stock again.

jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Yeah I believe I used the 1.29 RUU from the stock rom

jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
I used 1.56 RUU and went back to stock. Worked fine on mine w/ stock radio.

jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone

So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.

jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
Yea give it like 24 hours after the release, someone will do a nand dump, root it and post it on here. One thing I would reccomend people stay away from would be a new version of an RUU based off of 2.1, as that would put you up a **** creek if a root isn't found. I hear lots of problems trying to .29 RUU after a .56 RUU, I'm sure the same will be said for whatever the next version is.

jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
They may, or may not close the exploit that was found in 1.5 but if so it will only be a matter of time before some of these guys who are far more talented than I find a way to root 2.1, 1.5 was not rootable when it was released. Regardless the 2.1's you will see later today will be far superior to whatever sprint ends up releasing.

You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028

xanadu1979 said:
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
Click to expand...
Click to collapse
This fix didn't work for me, however I was able to RUU, update to DamageControl 1.0, download some protected apps, and then upgrade to DC2.0r2 (without wiping between DC1 and DC2). This opened up protected apps and solved the black on black contact problem for me.
-obviously do so at your own risk and all-

&RoidRage said:
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
Click to expand...
Click to collapse
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Also as far as the update is concerned, I know on the droid forums there were instructions on saving the update before installation so all could get it! What is the procedure for doing so!
It seems with the current state of affairs the update could come in a minute or a day or a month, basically no one know, so it could be anytime, so I just wanna be prepared for when it drop to hand it off to the real DEV.!
Roman

Eh, you could go ahead and flash a new ROM right now if you want. A fix was found for people getting bricked from the RUU, so you're safe to use the RUU now without fear of having a permanent brick on your hands.

Roman G said:
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Click to expand...
Click to collapse
Good question

2.1 official release for rooted users?

This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?

I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse

It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.

danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.

And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.

It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.

jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL

Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?

cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.

Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.

Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.

Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.

jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.

ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!

Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?

lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.

yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.

Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept

[q] will ota updates stop me getting root in future?

OK a nice simple one,
had my dhd a few weeks now very pleased with it. Am a massive fan of cyanogenmod roms, previously had a magic 32b and his roms were the best thing to happen to the phone, so am holding out for a cyanogenmod dhd rom - fingers crossed!
So if I install OTA updates will it stop me from getting root with S-OFF in the future. Golden rule of flashing anything (apart from backing up first!!) is not to update to the latest system software. Well this has always been the case with anyhing I have flashed in the past (psp, ps3, magic 32b, ipod, iphones etc...) is that also the case with the DHD?????
DHD on T-Mobile UK.

nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so).
btw: if you have root and recovery - you will not get any OTA, the recovery blocks it,
but you will get it from your costom rom vision.

As I thought, same deal as my old magic 32b then. Still think i'm going to sit on the fence for a while an watch what roms get developed or ported over.
I just miss a few of the mods in CM roms, silly thing like being able to enter a custom field in the add contact menu. Im sure i'll get over it. Although I believe that was a wysie mod to the phone book.
Thanks for the quick response.
Just gotta say how nice this phone is after my magic 32b, its like upgarading the ram and processor on your PC, it flies!!

An afterthought,
it seems it would be sensible to install the first few OTA updates before rooting so any stock software bugs are fixed before you loose the ability to update OTA.
Unless of course you are flashing a custom ROM which I assume the devs would include the bugfixes within their ROMS.

Why dont you try the CM rom now and if you dont want to keep it unroot the phone ?

Its brilliant by the way

I didnt realise there was a CM rom for the DHD, i couldnt see a category on his site for the DHD

But I do see it on the first page here in the dev section. Very pleased CM for the DHD and the phone has only been out a short while!
http://forum.xda-developers.com/showthread.php?t=844703

liorra3 said:
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so)...
Click to expand...
Click to collapse
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force

forelli said:
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.

dr.m0x said:
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
Click to expand...
Click to collapse
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force

forelli said:
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Couldn't you make a goldcard with sdk and a HxD hex editor??...then flash the ruu and you should be able to OTA..
Not as I see a need to do this as the Devs will always make new custom roms with the updated offical roms anyway..

[Q] Is it wise to update to the new software version when available?

We all know that the new update will come soon.
But does everyone know that it looks like with the new update we won't be allowed to flash back to older versions of the software. We won't be able to downgrade to a previous version it seems, due to journaling being enabled. We will lose functionality.
Does anybody know what this would mean for rooting and mods?
Is this something that we would have to be concerned about?

Speaking in purely speculation here, wouldn't it be beneficial to at least try the previous "retain root" strategy? It's possibly, though incredibly unlikely, that they haven't fixed that loophole yet. Might as well also try Gingerbreak on it too.
In the long run though, someone will eventually crack it it. It's inevitable really. And with Motorola claiming that the bootloader will be unlocked later this year, perhaps patience is really what we all need.

Gingerbreak should work fine because its not a logic crack such as psneuter its an overflow crack. Retain root should also work but Im not sure about that.

A good rule of thumb is to let others who are either developers or brave souls update and report back what can and can't be done after an update. If you want to retain what freedom you have with your Atrix to date, do not update until official word comes from enlightened.

Dont worry the minute the new update rolls out, im going to try to root it using gingerbreak

Heh, I plan to just go ahead with it. The only root apps I really use anyway are TB and screenshot stuffs and I can live without GingerBlur. Especially since they allow you to simply uninstall the AT&T apps ^^
Speaking of which, what do you guys think, should we flash a fresh SBF before updating if we've already flashed a pseudo-ROM?

Fresh start so we don't bash the new update caused by a third party app or mod, good luck
Sent from my MB860 using XDA App

KefkaticFanatic said:
Heh, I plan to just go ahead with it. The only root apps I really use anyway are TB and screenshot stuffs and I can live without GingerBlur. Especially since they allow you to simply uninstall the AT&T apps ^^
Speaking of which, what do you guys think, should we flash a fresh SBF before updating if we've already flashed a pseudo-ROM?
Click to expand...
Click to collapse
There is an screenshot app that doesn't need root - screen grabber - on the forum and in the market.
As for SBF before an update - based on past experience, you have to. The udpate will fail with the yellow triangle if you don't.

DON'T UPDATE YET. we need the time to analyze it. It is suggested this update modifies the bootloader to disallow flashing back to a previous version.

I'm aware of the conditions. They'll either crack it eventually or I can just wait for the bootloader unlock. I don't need root. Losing Amazon would be annoying though.

franciscojavierleon said:
DON'T UPDATE YET. we need the time to analyze it. It is suggested this update modifies the bootloader to disallow flashing back to a previous version.
Click to expand...
Click to collapse
This is actually my biggest concern...

...........

Should I update my ATRIX ?

Should I risk to update my unblocked, rooted and sideload enabled ATRIX or not (on the next possible update) ?
As the ATRIX is my first smartphone, I am still not so experienced on the smartphone / Android level. So I would would like to hear your opinions and experiences and ideas.
Would like to give some explanations first. I spent quite some time reading the xda threads and implementing these ideas. Result: my ATRIX is in a very "nice" condition now: Unblocked, rooted and sideloading enabled. I cleaned some annoying apps, did some fine-tuning (all thanks to the xda forum) and I am really happy with this nice little masterpiece of technology.
There are two update possibilities I am talking about:
- Build number (actually on my phone OLYFR_U4.1.8.3)
- Android version (actually 2.2.2)
According to the threads here in the forum, already the build number will get me back to unrooted. Can imagine what a Android version could do.
- So is it really worth ? All the hussle again after the update.
- How can I prevent (just in case) an update ?

Updating to 4.1.83 will also put you on 2.2.2.
You will lose root.
If you have uninstalled any Moto apps you will have to sbf 4.1.26 or 4.1.57 first. If you have frozen any Moto apps, you can just thaw them.
Personally I would back everything up, screenshot your home screens so you can set them up the same in worst case scenario of a wipe,, then go for it.
What all have you done to your phone up to now? i.e. gingerbreak, gladenable, theme......
Beamed in from WinBorg 4G via XDA Premium app

CaelanT said:
Updating to 4.1.83 will also put you on 2.2.2.
You will lose root.
If you have uninstalled any Moto apps you will have to sbf 4.1.26 or 4.1.57 first. If you have frozen any Moto apps, you can just thaw them.
Personally I would back everything up, screenshot your home screens so you can set them up the same in worst case scenario of a wipe,, then go for it.
What all have you done to your phone up to now? i.e. gingerbreak, gladenable, theme......
Beamed in from WinBorg 4G via XDA Premium app
Click to expand...
Click to collapse
Please read first what I wrote. My Atrix is on 4.1.8.3 and 2.2.2
Sent from my MB860 using XDA Premium App

1.ATRIX-in-PT said:
There are two update possibilities I am talking about:
- Build number (actually on my phone OLYFR_U4.1.8.3)
- Android version (actually 2.2.2)
Click to expand...
Click to collapse
What update are you asking about if you have 4.1.8.3? Are
you asking about the Gingerbread update? I won't update it
until the functionalities that I currently have are available on
that build.

OSNPA said:
What update are you asking about if you have 4.1.8.3? Are
you asking about the Gingerbread update? I won't update it
until the functionalities that I currently have are available on
that build.
Click to expand...
Click to collapse
Is that update even available to download??

Nope. 10char

1.ATRIX-in-PT said:
Please read first what I wrote. My Atrix is on 4.1.8.3 and 2.2.2
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
There are two update possibilities I am talking about:
- Build number (actually on my phone OLYFR_U4.1.8.3)
- Android version (actually 2.2.2)
If you already have it, why are you asking if you should update to it???

For safety, unroot your phone first
Swyped from MB860

+1 It sounds like you are already up-to-date. The version you posted is the same one your running.

Will explain my idea better
Sorry. As English is not my native language, I noticed that I explained wrong. Let me try better:
Yes. I am up to date. If I am updated, I do not know, but my ATRIX is ;-). 4.1.8.3 and 2.2.2. But ...
... as we read a lot about an upcoming Android Gingerbread for our Atrix, I am sunk in thoughts what should I do (when it happened !).
Actually everything is perfect on my Atrix, after a potential update probably not anymore. So will it be worth to update ? And to get everything back to "normal" (rooted, sideload, ...), the risk to brick the phone ...
Of course nobody really knows now, but how was it in the past with other Motorola smartphones ? For example the update from 2.1 to 2.2 ? What was your experience ?
Anyway. There is still my question, how can I disable an automatic update ? Would be happy, if somebody knows.

Solution for disable update 2.2.2
Just found a solution (already prooved if working ?) by WiredPirate in the xda forum
Titanium Backup
<backup/restore< "click to edit filters"< filter by name: "updater"< apply< updater2.2.2< freeze!

DO NOT FREEZE UPDATER
Sorry for caps - I've done it before & my battery life was shocking - Although i did freeze it after i started to get notifications to update

So what to do ?
- Update (when an update will be availiable) ? and all the work to get it back to rooted etc
- No update ? and to keep the Atrix like it is (as it is running fine)
Tell me.

1.ATRIX-in-PT said:
So what to do ?
- Update (when an update will be availiable) ? and all the work to get it back to rooted etc
- No update ? and to keep the Atrix like it is (as it is running fine)
Tell me.
Click to expand...
Click to collapse
I plan on waiting for the update to be out for awhile and read what others are saying about it.
Once they know how to get root, I'll update.
Keep in mind Titanium Backup can backup/restore just about everything after a wipe so it wouldn't be too much work..

I think this next update will be very much worth the hassle of rooting it again (you won't have to worry about sideloading - AT&T is going to enable it). I've read somewhere that for the gingerbread version, motorola's priority was for performance and this next version of motoblur isn't as bad as froyo's. Not only that, but gingerbread can make the 2 cores on the atrix work on every app, not only dual-core-optimized ones, and of course bug fixes, optimizations, etc. "Everything" should improve overall.
I'm in the same boat as you are (sim-unblocked, rooted, sideloaded) and when it goes live, i will wait a couple days before updating to see what people say about it. The only case i won't update it is if it removes sim-unblocking, which i doubt it will. Enabling root will be done eventually, these devs are awesome.

1.ATRIX-in-PT said:
Sorry. As English is not my native language, I noticed that I explained wrong. Let me try better:
Yes. I am up to date. If I am updated, I do not know, but my ATRIX is ;-). 4.1.8.3 and 2.2.2. But ...
... as we read a lot about an upcoming Android Gingerbread for our Atrix, I am sunk in thoughts what should I do (when it happened !).
Actually everything is perfect on my Atrix, after a potential update probably not anymore. So will it be worth to update ? And to get everything back to "normal" (rooted, sideload, ...), the risk to brick the phone ...
Of course nobody really knows now, but how was it in the past with other Motorola smartphones ? For example the update from 2.1 to 2.2 ? What was your experience ?
Anyway. There is still my question, how can I disable an automatic update ? Would be happy, if somebody knows.
Click to expand...
Click to collapse
When Gingerbread for the Atrix comes out, you'll lose your root if you update. However, Gingerbread will enable sideloading, which is a huge reason for many AT&T users to root anyway. You will have to go back to stock 2.2.2 in order to receive the OTA update to Gingerbread. It's your decision as to update or not, but I think that the benefits of Gingerbread outweigh the downsides of losing root, etc.

I would say wait for the update, let others who knows what they are doing do the update and root etc. then read the thread and update if/when needed. At least that's my approach. I like Gingerblur 4 on my Atrix.