So it seems that there are a few that still want to know how to upgrade their Droid X to 2.2.  We’ve all seen the Motorola post attempting to discourage people from using the leaked version of 2.2. … No one cares.  There is always a way to upgrade … Sanctioned or not.

If you can’t wait for Motorola to drop the official 2.2 update (they’ve been wrong about update releases before) and you understand the risk you are taking … then proceed with the following:

** Not responsible if you break/brick your device or if your dog gets diarrhea**

• Download the gift that was released from mydroidworld.com here
• Copy the update.zip file to the root of your sdcard and shut down your Droidx.
• Restart your Droidx in the recovery console … Power+Home until you see the moto logo.
• Once in recovery, press your search button to bring up the recovery options.  Use volume to navigate the menu and the camera to confirm a selection.
• Select apply update.zip and have fun … the update.zip already has flash 10.1 included.

I had a buddy that wanted to test out the leaked Droid Incredible froyo RUU … The 3.21.605.1 RUU with the 2.15 radio.  Problem was that he quickly found out that he lost root and his clockwork recovery.  The race condition that allowed you to pop in an sdcard had been fixed and unrevoked’s root and reflash utility didn’t work on this new leak.  It was also pretty safe to say that any future shipments of DInc’s would have this type of load as well by default.  Oh noes!

Fortunately we have an exploding community.  Forumite smwoodward posted a guide on xda-developers.com to roll back your Radio, HBOOT and OS.  With his guide, you can install the rom.zip file for any RUU applicable to your DInc.  Seems smwoodward saw that the EVO users were in the same boat in the past and the same fix for them applies to the DInc.  This fix should also apply to any new DInc’s that come to stores with 2.2 already installed.

Unfortunately, smwoodward didn’t have enough posts under his belt to post links in his thread.  It was kind of hard to follow without working links.  Here’s my reiteration of this fix:

** Not responsible if you break/brick your device or if your dog gets diarrhea.  This guide was written assuming you have a basic understanding of ADB and it is required that your SDcard be formatted in FAT32**

• If you haven’t already, download the Android SDK here.  Extract it to the root of your C: drive.
• Download the downgrade files here mirror.  The zip contains 3 files.  Extract those 3 files into the tools directory of the SDK folder.  Should be “c:\android-sdk-windows\tools”.
• Download the PB31IMG.zip file here.  Place this file in your “c:\android-sdk-windows\tools” directory.   This was originally the rom.zip file found within the DInc’s RUU for 1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494.  I renamed it to PB31IMG.zip.  This will be the file that the bootloader will look for.  More on that later.
• With your phone on, plugged into your computer and “USB Debugging” enabled (Settings > Applications > Development > USB Debugging), open a cmd prompt and type

cd C:\android-sdk-windows\tools

• Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.

adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd0.img /sdcard/
adb push PB31IMG.zip /sdcard/

Note: the PB31IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.

• Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell

adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin

Note: You will now see some text on your cmd prompt screen explaining the exploit.

• Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this: “C:\android-sdk-windows\tools>”
• Typing adb shell now should produce a # prompt.

cd /data/local
./flash_image misc /sdcard/mtd0.img

• that will flash your misc partition with Toast’s mtd-eng.img.  Once completed, This should return you to a blank line with #.

reboot bootloader

• This will reboot your device into the bootloader and start to automatically install the PB31IMG.zip file you pushed on to your sdcard.  The load process will take a little while.
• After a minute or so, there should be a prompt on your DInc’s screen asking if you want to apply the update.  Press the volume up key to confirm.  This will take a while.  Your phone will reboot a couple of times during this process.  Just let it sit.  There will be a confirmation message once its done.
• Congrats!  You are now rolled back to 2.1.  Your HBOOT is rolled back prior to the race condition fix.  Downloading the unrevoked root and reflash utility and running it will root your DInc and install the latest clockwork recovery.

Source: xda-developers.com

I love these guys.  They were the first to deliver froyo on the moto droid and from what I can tell by this thread that P3Droid made, this just might be a signed zip that your unrooted and stock Droid X can “apply update.zip”.  Forum followers are all indicating that you need to be stock to apply this.  That means to put back that bloatware and undo any custom hackery you applied for custom notification bars and themes.  Now I should be able to get my wife off my back about getting flash installed on her phone. =D

Source:  MyDroidWorld.com

This is going to be just a quick screenshot review of our beloved SetCPU.  Looks the the dev of SetCPU finally got around to responding to the beta requests  he asked for  No worries.  As I was getting this post ready he already sent out a beta2 update.  Wowzers.  He’s working fast.  Since this is a paid app that everyone should gladly pay for, I cannot post the link or apk.  This isn’t a warez blog.

For the most part, in his email, the major change will be the UI.  You can see it looks a great deal better from the screenies below.  My main concern was will it work with my droid running a froyo rom (Kanerade v1.1) with a 32 kernel … yes my friends … It does. =D

So a few of my friends that have froyo loaded on their phones are having issues with updating their google maps app through the android market.  It fails to install the update and it looks like the market doesn’t even register that its installed … But the old version still works.

Here’s what you do.  All of my friends already have the android SDK installed on their computers so I assume you do to.  Plug your droid into your computer.  Do not mount the SDcard.  Make sure debugging is enabled and run these commands:

adb shell

su

mount -o remount,rw -t yaffs2 dev/block/mtdblock4 system

busybox rm system/app/Maps.apk

cd system/bin

sh pm uninstall com.google.android.apps.maps

cd ..

cd ..

mount -o ro,remount -t yaffs2 dev/block/mtdblock4 system

sync

After you do all this, you will be able to go back into the android market and install that google maps update with no problems.

Source: Droid-Life

I wanted to get this last bog in tonight.  This video shows my Droid running Quake3.  Nothing special right? … RIGHT?  Well this time I’m playing it with a wiimote and a nunchuck.

• First you need to download kwaak3.  Big thanks to thunderbird2k for making this nice little app.
• Second you need a PC copy of Quake3.  You can download the demo from ID Software.  I used my Q3 cd.
• Third, download Wiimote from the android market.

Ill revisit this post again tomorrow with better instructions on how to set this up for those that are interested.  I’m sleepy.

If you haven’t yet … Go and download the rom.  Its the release candidate that their source has been showing on their site @ MyDroidWorld.com.  Its 75MB and available in nandroid backup.  One disclaimer is that WiFi doesn’t work.  They generated a new kernel.  Seems the ROM’s kernel was where Motorola would track who was the leaker of this delicious Droid froyo.