Comments on: DROID 2 R2-D2 Update to 4.5.622 is Ready – Security Patches, Bug Fixes and Android 2.3.4 on Board

By: Lee

Lee — Sun, 29 Apr 2012 22:27:00 +0000

Is there any way to fix this and take this off your phone?

By: TC Infantino

TC Infantino — Wed, 04 Apr 2012 19:17:00 +0000

I am not sure, I haven’t checked in a long time, but if you find out what you would be willing to sell it for you can reply to this and I will give you a way to email me and we can see if we can make a deal.

By: Tnjacklover

Tnjacklover — Sun, 01 Apr 2012 16:59:00 +0000

I have an R2D2 Droid2 with white headphones and the docking station. It has been my backup phone, so has very little use. I am considering selling it; anyone know what they might be going for on the open market these days?

By: Adam Martin

Adam Martin — Wed, 28 Mar 2012 05:37:00 +0000

Since installing the update, I’m experiencing random reboots, more duplicate texts than before, and random connectivity issues with YouTube app. I’m getting ready to send my R2 unit to Anchorhead to have its memory wiped.

By: This sucks

This sucks — Tue, 27 Mar 2012 03:13:00 +0000

BRICK!!! they want me to upgrade, wont fix

By: TC Infantino

TC Infantino — Mon, 26 Mar 2012 07:58:00 +0000

I had the OG Droid and I was so tempted to pay full price for the R2D2 when it came out. If I can find an R2D2 Droid for sale with all the accessories I will most likely jump on it. It won’t be my daily driver, but I can see myself using it on WiFi around the house, and as an alarm clock by the bed. There is just something cool about it, and the whole Star Wars theme.

By: SaurusX

SaurusX — Sun, 25 Mar 2012 19:23:00 +0000

I like the way you present yourself as the reasonable party here. Usually a nice tactic if you can pull it off, but you’re only coming off like a soundboard of Motorola talking points. Let me try and describe the current state of the union for you. The original D2 has not received the devil update from Moto, yet. The D2G has received the update and is currently stuck as being unrootable afterwards. The DX has the workaround or using the .604 SBF, but people were very fortunate to find that loophole. There are still problems associated with using blur-based ROMs after SBFing to .604, but those are being resolved. The DX2 and Droid Pro have these updates pending if they havent already come down. Both mention that there are “securiy patches” contained therein. Now that the FACTS are out there let people make their own choice, but at least they’ll be fully informed. Conversation over.

By: Tesseract 3

Tesseract 3 — Sat, 24 Mar 2012 23:22:00 +0000

Why take this stupid update when you can root and install ics roms on your droid r2d2 like i have done?

By: Pfigurella

Pfigurella — Sat, 24 Mar 2012 21:38:00 +0000

Do you have it in a case are you going full bore r 2 d 2 for all to see?

By: GrumpyOldMan

GrumpyOldMan — Sat, 24 Mar 2012 20:34:00 +0000

I have one and love it.

By: Jason Ulbright

Jason Ulbright — Sat, 24 Mar 2012 19:22:00 +0000

Ya you really are just eRaging, DX and D2 were not sold as developer phones, they were sold as droids with motoblur. motorola has no responsibility to advertise development features [unlocked bootloader] on their consumer devices if said features do or do not exist.
AFAIK no one in this thread/post has touched the FACT that these are android phones, and if you want access to the android market videos [google play videos] then the device is required to ship with a locked bootloader and no root. else that 99cents rental thing might get a little out of control.

By: Motorola Atrix forum

Motorola Atrix forum — Sat, 24 Mar 2012 15:55:00 +0000

R2D2 is supposed to be something modern, of the future, and all that. So, what the dickens are they dropping back into the dark ages of OSes for with this 2.3.4 mess? They have known for quite a long time that ver. 4.0 was around for them to use, so USE it.

By: SaurusX

SaurusX — Sat, 24 Mar 2012 13:39:00 +0000

False. A lot of people jumped to the DX and D2 without knowing that Moto had pulled a fast one and encrypted the bootloaders. That was never advertised anywhere and everyone assumed it would be a big party just like with the OG, which was free and open. THESE LATEST UPDATES KILL ROOT. Sorry for the caps, but I need to emphasize that. There is no known method to regain root once lost; all previous exploits have been closed off. You are spreading the opposite of FUD. You’re painting a picture of a rosy path to a simple upgrade, but you’re leading people to a situation where they’ll be trapped on stock and without root access.

By: Jason Ulbright

Jason Ulbright — Sat, 24 Mar 2012 13:34:00 +0000

I used the droid x from the .602 update until i bought my bionic in january. it was the most awesomely fast and crash free phone ever. I use random phones at work daily and i dont really see any problems with droid 2/2g/pro/x/x2. and the og droid is just amazing, if it had 512RAM i would have never stopped using it. moto has had stable software on their devices since about august/september but sadly their bootloader snafu has caused a lot of dissent in the modding community.

By: Jason Ulbright

Jason Ulbright — Sat, 24 Mar 2012 13:30:00 +0000

Moto has always had locked bootloaders [on VZW]. Anyone who uses an old base system for custom roms is only hurting themselves as the base rom contains the newest kernal, and since the bootloader is locked the kernal cannot be updated/changed. These updates are not nefarious in nature, they are end of lfecycle updates [droid x, 2, pro] and they have already been rooted via motofail/petes/etc. so you will not lose root, you will get a more stable system, and you will have support for the newest custom ROMs by upgrading. I really see no downside to performing the update. If youre still mad at moto for lying about unlocking bootloaders and seemingly doing the exact opposite then I can understand, but don’t troll the forum because moto lied to you, it doesnt justify leaving comments containing false claims.