Monday, June 25, 2012

Play Torchlight 2 Beta

So I missed the Torchlight 2 Beta (I know, my bad, right?).  Anyway I preordered the game as I was a little disappointed how Diablo 3 turned out and got a free copy of Torchlight 1 as an ordering bonus (pre-order now so you can jump on this deal as well!).  That's all well and good, but I still wanted to give Torchlight 2 a try and also wanted to show my friends the game so I'd have people to play with.  The beta may be closed; however, with a little computer wizardry you can give the beta a shot, realize how slick and smooth the game is, and have no qualms about pre-ordering it yourself!  Instructions below:

First of all, released a cracked version of the beta.  This is what we use to test the game, but there are a few steps you need to go through to get it working and, no offense to those guys, but their instruction set stinks.

The actual torrent file can be obtained here, go ahead and download that.

The file comes in a .rar format so you're going to need some software to unzip it.  I'm a big fan of 7-Zip.  The .rar is password protected, the password is ""

Once it's extracted you'll have a folder containing all the game files; however, the beta officially ended already so it's not going to work.  To avoid this problem we're going to trick the executable into thinking that the system date is something different than it actually is.  There are several different pieces of software that can accomplish this - I used Time Stopper as it was the first one I found and was extremely simple to use.

Open Time Stopper and you'll see this screen:
As you can see it's pretty clean and easy to figure out.

First we need to "Select the Main EXE of the trial version".  Click the "Browse" button and navigate into your extracted folder and select  "Torchlight2.exe".

The next step is to choose the new date the executable thinks is the system time.  The beta was during June 2012, so we set that date to 6/1/2012.  Then we enter an arbitrary name for the desktop icon.  Naming it "Torchlight 2" would be the logical choice, but it is really up to you.  Then simply click "Create desktop short-cut".
Click on your newly created desktop shortcut and the game will load.  Browse around the settings menu and enjoy the UI, then click "New Game" and create your character.  Go all the way through the process until you're given the option to play using "Internet".  If you try to connect you're going to get an error.  This is where Skidrow's crack comes into play.  Inside the Torchlight 2 folder there's a "Surprise.exe" file.  Run it.  You'll see the following dialogue box:
Type "start" and hit enter.  You will then be able to enter an arbitrary username and password and create a game and enjoy the beta!

Quick and Dirty Numbered Instructions:
  1. Download File
  2. Extract File - Password is
  3. Download Time Stopper
  4. Create a Desktop Shortcut for Torchlight2.exe with the date set as 6/1/2012
  5. Open Game Using Shortcut
  6. Run Surprise.exe From Extracted Folder, Type "start" and Hit Enter
  7. Log In Using Any Credentials
  8. Enjoy the Awesome Beta and Pre-Order the Game to Get a Free Torchlight 1 Copy
And a video for you visual learners:

How to use a PS3 Controller to Play Skyrim on a PC

I did this last night and found I preferred using it to the keyboard as I found it more fun to lean back in my computer chair while I played, also liked the way swapping spells worked better and it seemed more intuitive to me. I also don't own the software used (Motionjoy and DS3 Tool) and can't claim it's 100% legit (seems like it's from China) but it works just fine.
Originally found from here, but the instructions are outdated and didn't work right away for Skyrim.
This worked on my Win 7 x64 bit install.

1: Plug in your PS3 controller via USB, your computer will automatically install some basic drives.
2: Download full drivers (digitally signed, so no worries there) x64 x86
3: Run the .exe in the .zip. When it's done, open the DS3 Tool as prompted.
4: Tool looks like a clown college, but is actually pretty simple once you get it down. It should automatically prompt to update, if it doesn't, there's an option to update under "Options" I believe, after it's done updating it wants you to reboot, go ahead and do so. Leave your PS3 controller plugged in.
5: Computer's back up, open the DS3 Tool, click on the "Driver Manager" section, checkmark the box there and click "Load Driver".
6: Click on the "Profiles" section. Under the "Connected game controller(s)" it should now say "1. Dualshock 3/sixaxis (USB)" (or whatever controller you have). Under the "Select one mode:" section check the "Xbox 360 Controller Emulator" - need to do it this way as Skyrim only recognizes 360 controllers.
7: Click the pink "Enable" button below. More drivers will install, wait for confirmation notice from your notification area and then you should be good to go. Click on "Game Controller Panel" and confirm "Controller (Xbox 360 Wireless...)" is listed, highlight it and click on properties; this will bring you to a testing area. Click around with your controller to confirm it works properly. Press "OK", "OK", and then click the "Vibration Testing" button, vibration should work (if you have a dualshock).
8: Open Skyrim and it will detect the controller right away, continue your game, hit up the settings and remap to your liking (I don't like the 360 layout, I prefer my right and left 'attacks' to be R1/L1, not R2/L2).

Starcraft 2 4-Gate and DotA 2's Mortred Blur Statistics

I made a youtube video for people looking for a little help with their 4-gate rush build for Protoss players of Starcraft 2.  I've moved on to different games, but the video tutorial may still help some people and can be found below:

I've also been playing a lot of Valve's DotA 2 lately.  Mortred the Phantom Assassin is one of my favorite heroes, so I made a guide for on how my playstyle with her goes.  I also crunched some probability numbers in there, it can be found here (it has some really cool formatting that you can't copy with blogger), I have an excerpt from the guide listed below about the statistics of her Blur ability:
So why is Blur so good and why do we max it first?  The reason is because it scales so incredibly well per level.  Just how well?  Well, let's do some basic statistics to find out exactly how much staying power it offers you.

The probability of an event is the proportion of times it will occur if we repeated a random trial over and over again under the same conditions.  For evasion with Mortred, we see that with level 0 [[Blur]] you have 0% chance to dodge, level 1 provides a 20% chance to dodge, level 2 gives you 25%, level 3 offers 30%, and 4 gives you a 35% chance to dodge incoming attacks.

If we classify [Evading an Attack] as a success in this trial and [Not Evading an Attack] as a failure, we can deem that [Evading an Attack] is both mutually exclusive and independent of [Not Evading an Attack] as they cannot both occur simultaneously and the first does not change the probability that the second will occur. 

With that knowledge in mind we know the basic statistical formula to follow for our study:

Pr[A] and [B] = Pr[A] x Pr[B]
Pr[Evading an Attack AND Not Evading an Attack] would be Pr[Evading an Attack] x Pr[Not Evading an Attack]

This means that with level 1 Blur the probability of evading 1 attack in a trial of size 2 would be .2 x .8 or .16 or 16%

But Mortred doesn't die in two attacks.  For the sake of sanity I'll limit our trial size to a size of 5.  With this constant, 5 consecutive attacks against Mortred will provide 32 outcomes, 6 of which are unique.


We can visualize this with the following probability tree:

So how do we interpret these data?  The probability of 5 avoidances in a row is the same probability at level 4 as 3 successes is at level 1, and your chance of being hit all 5 times drops from 32.7% to almost one third of that at 11.6%!  Visualizing data can be difficult with hard numbers, so below is a bar graph comparing level 1 to level 4 Blur.

Finally, if we go back to our original example of 2 attacks, Mortred will have:

.35 x .65 or a 22.75% chance of dodging one in two attacks,
.35 x .35 or a 12.25% chance of dodging both, and
.65 x .65 or a 42.25% chance of being hit twice

This is as opposed to the 16%, 4%, and 64% of level 1 Blur, respectively. 

That's a lot of missed attacks!

maderstcok - OTA 2.3.340 (Droid X)

None are responsible for your phone but you.

After a bit of work I've created an for you guys that want a fresh install of 2.3.340 without sbfing.

This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.

What that means is that if you have 2.3.15, 2.3.151, or 2.3.320 you're one away from the OTA 2.3.340

This is useful in many ways:

  • You want stock .340 but didn't create a nandroid backup
  • Can't OTA (modded phone)
  • Get ready for an OTA
  • Remove Root
  • Add bloat back
  • Re-Odex
  • Your phone is acting weird on the update
  • Something broke
  • Fresh ROM install
  • You don't want to flash 5 update.zips or sbf to update your phone
  • etc.
This will format your system data (helps prevents bootloops - not 100%) and system (in case a rom put some apps in the /system/app) partitions and also changes the boot image to the stock moto M (to fix the Tranquility boot logo - something even an SBF won't fix).

As always, make a backup and I'm not responsible for what happens to your phone.

Download the file here and place it on your sdcard:

  1. Using the Droid X Bootstrapper make a backup. (more information here)
  2. Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
  3. Select "choose zip from sdcard".
  4. Select ""
  5. Confirm the install.
  6. Be patient, wait for the install to finish.
  7. Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
  8. Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.

Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.

EDIT: coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe

Quick and dirty instructions for activation:
  1. Dial *228
  2. Press 1
  3. Enter last 4 of primary acct holder's SSN
  4. Wait - more in depth instructions in a link further down.

This can take some time, especially on the two system installs and the radio install. Don't battery pull unless you want a brick.

The file won't flash properly if you have a botched download - this seems to be caused by the size of the file. Please check your file size before flashing:

Size: 284.7 MB (298481300 bytes)
MD5: ce7122280eafad4a39ba7fefeb764bf5

My free filehosters sometimes .zip the .zip - it looks like
Just unzip once and check the md5 to make sure it checks out - if not, redownload. Don't try to flash the without unzipping it once!

You'll have to activate your phone again after the install. See this for additional help.

If you encounter any problems during the flashing process (e.g. bootloop) follow standard ROM installation troubleshooting (i.e. battery pull, factory reset, etc.)

A lot of this stuff is from Team Black Hat - I did pull some of my own phone files too - but if you're looking to donate, please hit them up. Without them we'd be up a creek. Tell 'em I sent ya

One final note - z4root seems to work flawlessly after flashing this file. Just thought I'd throw that in there...


EDIT: Currently number 1 google search result for 2.3.340 - thanks to everyone for your support!


01/02/2011, 03:42p CST - Wrote Post
01/06/2011, 11:37p CST - Concluded Beta, Released to Public
01/07/2011, 11:28a CST - Minor Changes and Fixes
01/07/2011, 05:19p CST - Minor Change - maderstcok 1.1
01/07/2011, 07:58p CST - Added to DXF
01/08/2011, 06:04p CST - Quick and Dirty Activation Instructions Added
01/09/2011, 03:43p CST - Added Backup/ROM Install Post maderstcok Warning
01/13/2011, 07:29p CST - Bolded Some Text Due to Current Issues
01/30/2011, 05:50p CST - Added Another Mirror and Edited Regarding Bootloops

Complete Droid X .sbf Flashing Guide

Complete Droid X .sbf Flashing Guide

Can you boot into the operating system and don't want to do this?

See maderstcok - the OTA 2.3.340.

Quick Info:

I have been getting a lot of questions regarding the proper sbf to use. Here is a quick answer:

30.03 BL - 2.3.15 sbf or .320 sbf
30.04 BL - .340 full sbf

I'm not responsible if you damage your phone yada yada yada.

On to the Tutorial:

This is a tutorial on how to flash original firmware back onto your phone. This is done with an .sbf file, hence the term 'sbf flashing your phone'.

After you do this your phone will be returned to 'out of the box – brand new' status. It will be like you have never turned it on before, wiping out ROMS, THEMES, everything BUT what is contained on your sdcard.

You do not need to be rooted for this to work.

Unfortunately for OSX (Macintosh) users you will need to use either Windows or Linux to get this to work.

This tutorial will return you to 2.2 (Froyo), not 2.1 Android, and is broken up into 5 sections:
  • How to get your Droid X into the Bootloader
  • Windows and Using RSD_Lite
  • Linux and SBF_Flash
  • Common Issues and FAQ
  • Changelog

Windows and Using RSD_Lite

If you're a Windows user, you're going to be using a program called RSD_Lite. The current version is 4.8. I always recommend to use the most current version of RSD_Lite while attempting to flash .sbf files.

Files you will need:

Extract the .sbf file, RSD_Lite 4.8, and Motorola Drivers (4.7.1) onto your desktop. You may not need the drivers; however, they are nice to have if it doesn't work right away.

  • Install RSD_Lite
  • Boot your phone into the bootloader using the previous instructions (Hold Down + Camera Button while holding power)
  • Connect phone to computer using USB Cable
  • Open RSD_Lite (you must run as admin for it to work, 4.8 automatically runs as admin I believe)
  • Click the “...” button and select the .sbf file you placed on your desktop
  • Click start to begin the flashing process after you've confirmed your device and .sbf file with RSD_Lite (sometimes changing the Device ID helps RSD_Lite find the device)

Make sure you DO NOT unplug the USB Cable or do a battery pull while flashing.

If your device isn't listed it's probably a driver issue, install the drivers you downloaded after uninstalling the previous drivers you had installed. Use the device manager for this. Run/search (XP/Vista-7, respectively) devmgmt.msc. You could also toggle the DeviceID settings from the config menu in RSD_Lite. That has worked in the past.

Windows 7 64-bit can be a huge pain, even I can't get them to work. If you are really struggling to get your phone connected you may want to use Linux.

You may also have to start RSD_Lite and then plug in your phone. RSD Lite can be finicky like that. Play around with it for awhile, you might get it to work properly. Also, RSD_Lite 4.7 is worth a shot.

Video Tutorial (watch in high def to see better):

 For more information on using RSD Lite, please see this post, I found it to be very informative.

Also, make sure you do NOT disconnect your phone until the entire process is finished. It should say "pass". Even if it's hanging, just let it sit. You know you're done when the phone reboots.

Linux and sbf_flash

sbf_flash is a free utility for the Linux operating system. I've had the most success with this program and I highly recommend it to anyone attempting to sbf their phone. It is very simple to use and Linux doesn't have the same problem with drivers that Windows has. It. Just. Works.

I recommend:

Files you'll need:


1: Download the Ubuntu image. It's an .iso file - this means it can be burned onto a cd/dvd. Do so.
2: Once the burn is complete, reboot your computer, set your bios to boot from cd/dvd if you have to.
3: Ubuntu's Menu will appear, select "Try" to boot into the OS without altering your current setup.
4: Download the .sbf_flash utility and the proper .sbf file (bonus points if you have them on a flash drive ^^)
5: Flash the image onto your phone:
  • Extract the .sbf file to a directory (e.g. Documents)
  • Place the sbf_flash file into the same directory
  • Open up a terminal window
  • Change to the directory that the files are in. [cd] is the command you use, so if in Documents, type [cd Documents]
  • Ubuntu is caps sensitive, so you need to type the capital "D", if you type "ls" it lists all the files in the current directory you're in, so type [ls], if you see the files, you're golden.
  • Type [chmod +x sbf_flash] (ignore brackets) – this command makes sbf_flash an executable. If you've been rooting your phone with ADB Tools you've seen this command before.
  • Type [sudo ./sbf_flash [name of sbf file, starts with 'VRZ_']] (once again ignore the brackets) – this command runs the sbf_flash file. 'sudo' is the linux-y way of 'running as administrator' in Windows.
  • It will prompt you for your password - enter it.

Linux pro tip: type [./sbf_flash V] and then [tab]. This will autofill the rest of the name of the .sbf file for you

That's it!

Common Issues and FAQ

Q: I'm using Windows and my Droid won't show up in RSD_Lite.
A: Driver or USB Cable issue. Try to use your original USB Cable (the one that came with your phone) or a higher quality 3rd party one.

Q: Okay, I'm using the right cable and it still won't show.
A: Driver issue, update your drivers. Try a different USB Port. Try RSD_Lite 4.7.

Q: Did all that, still doesn't work.
A: I recommend upgrading your operating system to Linux, see above post. Else try a different computer with a different version of Windows.

Q: I did your sbf and now my phone won't make calls! WTF?!
This is due to the radio not working. It's a pretty simple process to turn it back on. Either reboot your phone a couple times and it will do it automatically, or dial *228 and it will turn the radio back on for you.

Q: I did your sbf and it worked but now I'm stuck in a bootloop.
A: Can be caused by a botched download of the .sbf file. Download again and re-flash. Some people also resolve this issue by performing a factory reset. To do this boot into the system recovery by holding home + power, keep holding home until an ! comes up, press "Search", browse to "Factory Reset", and perform it. You might want to try this before reflashing as it takes less time.

Thanks so much! Can I marry you?
A: No.



11/25/2010, 12:53p CST - Completed Tut
11/25/2010, 01:21p CST - RSD_Lite Video Added
11/26/2010, 05:16p CST - Turning Radio Back On Into FAQ
11/28/2010, 10:19a CST - Bootloop Solution Added Into FAQ
11/28/2010, 03:15p CST - Changed Bootloader Information/Added Note
11/28/2010, 11:02p CST - Added Bootlooping Fix to FAQ
12/15/2010, 12:33a CST - Added 30.04 .sbf File Link
12/18/2010, 04:14p CST - Changed Ubuntu Download Link
12/26/2010, 03:45p CST - Updated Linux Tutorial to be More Helpful
12/27/2010, 05:13p CST - Added Quick Bootloader-SBF Info in Top Post
01/02/2010, 03:49p CST - Added maderstock Link
01/07/2011, 08:30p CST - Updated
02/19/2011, 11:36a CST - Updated with .340 Full SBF File

Original "M" Bootloader Image (Droid X)

I created an that replaces the Bootloader image with the original Motorla "M".  This is what sparked my interest in creating "maderstcok".  If you'd like to use it for some reason you can grab the file from below:

Creating and Restoring Backups (Droid X)

FIRST STEP AFTER ROOTING - Creating and Restoring Backups - Complete Guide

Quick Note:
Two or three users have had an issue flashing the backup after creating a restore. This seems to be caused by errors in Koush's clockworkmod recovery. That said, using clockworkmod is currently the only way to create a nandroid backup.

As always (and as stated in the forum guidelines) no one is responsible for your phone but you. This is where you should start in the Android Modding world and if you have problems then remember that any time you mess with /system files it can end in tears.


The first thing you should do after you root your phone (as in before doing anything else) is create a backup. This way you have somewhere to return to if you mess something up on your phone.

I read somewhere once that it's like having 999 lives in Contra. So true. So, I'm going to help you do it.

There are three tools you'll probably want. One is absolutely necessary, the other two are just handy to have.


Koush's Droid X Bootstrapper

Recommended (search app market, both have free versions):

  • Titanium Backup
  • Rom Manager

The Bootstrapper

Koush's Bootstrapper is a tool used to boot into clockworkmod recovery. You can make a custom image of your phone, install roms, etc. all from the recovery menu.

After downloading the .apk above, install it after browsing to the file on your sdcard.

In order to do so you must allow 3rd party sources to install apps. Turn this setting on in:
  • Settings -> Applications -> checkmark 'Unknown sources'

Make sure you're rooted, then load up "Droid X Bootstrapper". Press Bootstrap Recovery (it will prompt for superuser access and then say "success"), then Reboot Recovery (it will also ask for superuser access, then reboot your phone).
Creating and Restoring Backups - Complete Guide-cap201011270220.jpg

Your phone will reboot into the clockworkmod recovery area - this is a crucial thing to get used to if you're going to play around with your phone.

Before you do anything else:
  • Use the volume buttons to navigate to "Backup and Restore"
  • Press the camera button to enter that menu
  • Select "Backup" and press the camera button

It will go through the backing up process, it may take a minute or two, don't battery pull or anything dumb like that.

When it's finished creating the backup it will kick you back to the main menu. Highlight "reboot system now" and press the camera button to reboot your phone.

Video Demonstration:

You now have a stable backup of your current system saved onto your sdcard. Anything you do - as long as you can get to clockwork recovery - is reversible back to this point.  

Restore Your Backup

To see how the backup feature functions you must first change something in your system: e.g. delete something off your home screen, a widget, anything. Do this now (make it noticeable to you - delete your clock or something).

  • Go back to Koush's Boostrapper app
  • Click Boostrap Recovery
  • Click Reboot Recovery

You're back in clockwork recovery again.
  • Navigate to "Backup and Restore"
  • Select "Restore" - this is where all your system flashes are kept, you should only have one.
  • Navigate to it, press the camera button. It will ask for confirmation
  • Select "Yes - Restore"

It will begin restoring your phone. It may take a minute. Once again do not do a battery pull. When it's finished you will be on the main menu. Select "reboot system now". It will boot you back into the operating system; however, now you're back to your flashed system file - you'll see the widget you had previously deleted returned to normal!

Video Demonstration:
Reboot your phone. It will go right back into your regular interface - no clockwork recovery. The reason for this is in order to boot into the clockworkmod recovery the .apk checks for a minute file that basically tells the phone to redirect to the recovery - on a successful reboot with clockwork (if you have the .apk installed) it will delete this file so you don't boot back into clockwork unless you want to.

Backups are stored on the sdcard in /clockworkmod/backup - you can name them to anything you want in order to help you remember what backup they are (e.g. clean 2.2 or ssx)  

dditional Things...

Additional clockwordmod recovery options:
  • reboot system now
    • pretty self explanitory, reboots your system back into the operating system
  • apply
    • not very useful. applies from the root of your sdcard.
  • wipe data/factory reset
    • deletes all user data (apps, etc.)
  • wipe cache partition
    • wipes the cache of your phone
  • install zip from sdcard
    • selecting this and then "choose zip from sdcard" opens up a little browser. select any zip on your sdcard and it will install it. useful for romming, themeing, etc.
  • backup and restore
    • see above post
  • mounts and storage
    • careful in here. you can mount your sdcard which is handy, but don't format anything. I formatted /system once and bricked my DX
  • advanced
    • ignore this one

Also, to boot into clockworkmod recovery if you're bootlooping follow these instructions:

  1. Plug usb into wall charger.
  2. Plug phone into usb w/o the battery in the phone.
  3. If it comes up with a battery with a ? in it, unplug and plug it back in.
  4. If step 3 worked, you should be in Clockwork.

Rom Manager:

This is a handy tool. You can:
  • Name backups before they're created
  • Rename old backups
  • Restore backups
All from one menu! You do need the bootstrapper for this to work, however.

Titanium Backup:

This app backs up all your apps to your sdcard (and more!). This way if you have to .sbf, install a rom, or restore a backup you can reinstall all your apps quite easily.

To backup your apps:
  • Menu key
  • Batch
  • Backup all user apps

To restore your apps:
  • Menu key
  • Batch
  • Restore all apps with data

Uninstalling The Bootstrapper

It's a little tricky to completely remove the bootstrapper; that said, follow these foolproof instructions to never see clockworkmod recovery again:
  1. Uninstall Droid X Bootstrapper
  2. Use a root file system explorer (e.g. Root Explorer) to navigate to /system/bin
  3. Delete the file "logwrapper"
  4. Rename the file "logwrapper.bin" to "logwrapper"
  5. Reboot



11/27/2010 02:39a CST - Completed Tutorial
11/28/2010 10:08p CST - Added Booting Into Clockwork Manually
01/01/2011 11:33a CST - Added Uninstall Instructions
01/06/2011 06:32p CST - Mods Reopened Thread and Added Warning

Change "Verizon Wireless" Notification Bar Name Manually (Droid X)

Change Notification Bar Name (Verizon Wireless)

You need to be rooted for this to work.

To do this you need several tools. First you need the Ninjamorph app as it makes the process very simple. Download that from the app market.

You also need a hex editor. I recommend:


First pass the checks on Ninjamorph to get it to function.

Then, select

  1. New Project
  2. Browse to /system
  3. Browse to /framework
  4. Select framework-res.apk
  5. It will extract it to your sdcard
Connect the DX to your computer
The extracted file is in /sdcard/AndroidThemes/workspace
The specific file you'll be editing is eri.xml
Full path is /sdcard/AndroidThemes/workspace/res/xml/eri.xml

Put that file onto your computer.

Open the file with Frhed

Browse to line "01b3"

Change the name from "Verizon Wireless" (or whatever it was set to by your theme) to whatever you want.

Be sure you do not use over or under 16 characters!! Fill with spaces if you must.

Put the eri.xml file back onto your sdcard.

Open up Ninjamorph again

  1. Existing Project
  2. framework-resapk
  3. Browse to /res
  4. Browse to /xml
  5. Select eri.xml
It will ask what to replace it with. Select the edited eri.xml file you put onto your sdcard.

Confirm the replace and keep confirming until it stops prompting. Then you need to reboot your phone (it actually should autoreboot, but whatevs).

Video Tutorial (watch in high def):

Droid X Superuser and Clockworkmod Recovery

Times changed, as did the customization options for Android.  These videos show how to boot into the Droid X's bootloader, a basic instruction set for the Superuser App, and an intro to Koush's bootstrapper.

Early Droid X Rooting

Some of the first videos I uploaded to youtube were tutorials on rooting the Droid X, installing wifi-tethering, and removing bloatware using the ADB commands.  These are by now outdated and there are much better methods that are offered.  These were done before I had a mic for my computer.