Our last article discussed the process of rooting the Droid X via z4root. While rooting itself doesn't add any features or functionality, there's plenty of applications that can make use of the elevated privileges that it provides. For example, you can access the entire file system, make modifications to kernel settings, control the built-in firewall, change the CPU frequency, etc. Most of these are apps that I currently use and can be installed directly from the market. And here, in no particular order, are the apps.

• DroidWall - Android Firewall: DroidWall allows you to make use of the built-in IPTables firewall. You can pick and choose which applications are able to talk to the Internet via 3G and/or wireless. Have a pesky bird-like application that likes to plaster ads wherever you click? No problem. You can keep it from calling home to grab the ads. DroidWall allows for both white- and black-listing of what's allowed out.
• Titanium Backup: Titanium backup works great with a few caveats. It'll allow you to back up both applications and systems settings, e.g. SMS messages, call log, ringtone settings, etc. You can quickly restore the phone if you have to wipe your ROM. Overall it works great. However, I've found Titanium Backup to be problematic if you're moving between ROMs: settings from one often cause another to break. YMMV.
• MyBackup Root: This is a solid alternative to Titanium Backup. It doesn't seem to be as low-level but gets the job done. It'll handle applications, SMS messages, call history, etc. I've been using this lately since I move between ROMs a bit too often.
• Root Uninstaller: Pretty straight-forward. This app will let you uninstall anything from the system, including the bloatware that Motorola likes to include. Useful for cleaning up a ROM.
• Root Explorer: Great file-system browser for Android. You can do just about anything with it. Functions such as zipping, unzipping, text editing, thumbnails, etc work right from the app.
• Droid X Recovery Bootstrap: This is a must-have if you've rooted your phone. Not only can it be used to flash custom ROMs, but it allows you to create complete system images of your Droid X for backups. This allows you to restore your system to the exact state of the backup without have to reinstall apps and configure settings. I use this whenever I flash a new ROM in case anything goes wrong. Well worth the small price.

That's it for now. Be sure to leave any apps you think should be included in the comments section.

I'll keep this short: if you're rooting your Droid X, changing ROMs, removing stock applications, etc, then there's a good chance you're eventually going to brick your phone. Having your phone "bricked" usually results in the Motorola logo being displayed indefinitely and or looping with the animated Droid X boot logo. A lot of users will then take it in for service, get it re-flashed, and get a lecture on potentially voiding your warranty by hacking the phone. However, there's tools available that allow you flash the phone back to the pristine state you first received it in.

This guide is designed for the 2.3.32 release of the Motorola firmware, aka the SBF. As such, you will also need to ensure that your bootloader is at 30.03 or higher. Instructions for upgrading both the firmware and bootloader can be found below.

Preparation:
You first step should be ensuring that you can get into the bootloader and taking note of the bootloader version. Upgrading to the wrong firmware or bootloader version can get you stuck in a loop. A more indepth guide is available at My Digital Life.

Getting into the Bootloader:

1. Hold down the power button at the top of the phone until you're given the option Power off. Select this option and power off the phone.
2. Boot the phone into bootloader mode. This involves some finger-ninja skills.
   1. While the phone is powered off, hold down the Volume Down button on the right of the phone.
   2. While still holding Volume Down, also hold down the Camera button on the right side of the phone.
   3. While the previous two buttons are held down, also hold down the Power button on the top of the phone.
   4. The phone will display the bootloader menu. From here we can restore the stock SBF.

Note: It's sometimes easier to pop out the battery, hold Volume Down + Camera, and pop the battery back in while holding it. You should immediately get kicked to the bootloader screen.

Necessary Tools:

• RSD Lite v4.8: This tool allows you to flash the SBF to your phone.

Necessary Files:

• Droid X 2.3.32 Full SBF: This is the image you'll need to reload your Droid X. You'll need to extract the SBF from the zip file that is downloaded.

Restoring your Droid X:

1. Get into the bootloader on your Droid X if you haven't already.
2. Open up the RSD Lite application. I usually run it as administrator.
3. Verify that RSD Lite is able to see the Droid X.
   
4. Browse to the extracted file in the previous step. It should appear under File Properties.
   
5. Click Start. The process will begin. Do not freak out, get impatient, or unplug your phone during this time.
6. Your phone will reset when finished. More than likely it'll be stuck in a boot loop.

Help, I'm Stuck in a Boot Loop:

1. Power off the phone by removing the battery. Hold down the Home Key. Plug the battery back in.
2. You should see an Android logo with an exclamation mark in a triangle. Click the Search Key.
3. Use the Volume Down key to navigate to the option "wipe data/factory reset". Click the Camera Key once.
4. Press Volume Down to scroll to the "Yes" option. Click the Camera Key once. The phone is now being wiped.
5. Press Volume Down to navigate to the option "wipe cache partition". Click the Camera Key once. The cache is now being wiped.
6. Select "reboot system now" and click the Camera Key once.
7. The phone will begin booting. The first boot usually takes a few minutes to complete. You'll need to update/activate your phone.
8. Go to Settings -> About Phone -> System Updates to ensure you have the latest version of firmware.

Note: Your phone is not rooted at this time.

Rooting Your Phone:

The processing for rooting the Droid X used to be involved and somewhat painful. Thankfully, RyanZA at XDA created an app that makes it a one-click affair.

1. Download the z4root app. Copy it over to the Droid X's SD card.
2. Ensure USB is set to Charge Only so the phone can see the SD card.
3. Go into Settings -> Applications and check "Unknown Sources".
4. Go into Settings -> Applications -> Development and check USB Debugging.
5. Open the File application, click on Phone Files, and browse to the z4root application. Click on z4root. Click Install when prompted. Click Open when finished.
6. You should now be in the z4root application. Click Permanent Root. You'll have to wait a minute while it obtains root access. Your phone will reset when it's complete.
7. Assuming z4root is successful, you should have an application called Superuser installed.

Congratulations. Coffee now tastes better, the sky is brighter, and the world is a better place. In the next segment I'll cover installing custom ROMs and applications.

In my previous article, we covered building a wireless home network using commodity hardware and DD-WRT. While it works great, you can definitely hit some snags when generating a lot of traffic, e.g. running BitTorrent, playing Black Ops, and trying to use your VoIP all at the same time. Everyone is given equal footing: that BitTorrent traffic might cause your VoIP call to drop and Black Ops to lag since it's eating up all of the bandwidth. QoS is fully supported by DD-WRT and could be used, but it's often difficult to configure, especially if you don't have a consistent up- and down-stream Internet speed. Enter the world of TCP Vegas:

Vegas is an implementation of TCP that achieves between 37 and 71% better throughput on the Internet, with onefifth to one-half the losses, as compared to the implementation of TCP in the Reno distribution of BSD Unix. This paper motivates and describes the three key techniques employed by Vegas, and presents the results of a comprehensive experimental performance study—using both simulations and measurements on the Internet—of the Vegas and Reno implementations of TCP.

Long story short, the necessary modules for TCP Vegas are already included in DD-WRT. Once enabled, the router will dynamically allocate throughput to prevent a single application from hogging all of the bandwidth. Just take the following steps to enable TCP Vegas:

1. Log into the DD-WRT web interface.
2. Click Administration -> Commands.
3. Paste the following lines into the text box labeled Commands:

echo 0 > /proc/sys/net/ipv4/tcp_westwood
echo 1 > /proc/sys/net/ipv4/tcp_vegas_cong_avoid
echo 3 > /proc/sys/net/ipv4/tcp_vegas_alpha
echo 3 > /proc/sys/net/ipv4/tcp_vegas_beta

4. Click Save Firewall. This will also automatically run the commands.
5. Your final settings should look like this:

And, with a few simple commands, you now have traffic congestion control enabled.

Summary:

For 99% of the population, the stock firmware that's included with wireless routers is just fine. For the remaining 1% of power-users, it just doesn't cut it. Whether it be increased signal range, a wireless mesh, or just the need to tweak settings under the hood, there's always a reason to want more from that commodity piece of hardware. The following guide will cover enabling No-IP, OpenDNS, and creating a bridged wireless network across your environment.

Enter DD-WRT:

DD-WRT is a Linux based alternative OpenSource firmware suitable for a great variety of WLAN routers and embedded systems. The main emphasis lies on providing the easiest possible handling while at the same time supporting a great number of functionalities within the framework of the respective hardware platform used.

The graphical user interface is logically structured, and it is operated via a standard Web browser, so even non-technicians can configure the system in only a few simple steps.

Apart from the simple handling, speed and stability are also in the focus of our development work. Compared to the software preinstalled on many WLAN routers, DD-WRT allows a reliable operation with a clearly larger functionality that also fulfills the demands of professional deployment.

In the following scenario, we're going to build a wireless bridge network that makes use of both No-IP and OpenDNS.

No-IP, OpenDNS, and DNS-O-Matic:

Your typical home Internet connection is DHCP and changes its IP address on a semi-regular basis. Again, this doesn't matter to 99% of the users. However, if you connect back home on a regular basis, it makes it impossible to find your host. No-IP allows your router to dynamically update a DNS name that always points back to the DHCP address, e.g. remote.example.org.

On the other hand, OpenDNS allows you to take back control of your DNS settings. DNS is the service that resolves names to IP addresses, e.g. remote.example.org to 192.168.1.10. The DNS service is typically handled by your ISP and results in advertising redirects, HTML injection, tracking, etc. OpenDNS allows you to control all aspects of your DNS settings, including some impress features like content filtering, malware detection, and phishing protection. Both No-IP and OpenDNS have free services. You'll need to create an account on each one for this tutorial.

There's one more service we'll use, courtesy of OpenDNS: DNS-O-Matic. It uses the same credentials as OpenDNS so there's no need to create a new account. DNS-O-Matic acts as a proxy to update both OpenDNS and No-IP all in one shot. This ensures that your DHCP address is always current with both services. After registering with both No-IP and OpenDNS, add both of the services to DNS-O-Matic. To summarize:

1. Create an account with No-IP and create a hostname, e.g. example.no-ip.org.
2. Create an account with OpenDNS and create a profile name, e.g. Home Public IP.
3. Finally, log into DNS-O-Matic using your OpenDNS credentials, and add both No-IP and OpenDNS as services to be automatically updated.

The Home Network:

In this example, the network will cover three floors with the Internet link being on the ground floor. I've got non-wireless electronics on all three floors that require a network drop, and I don't plan on running Cat6 all over the place. The design will look something like this:

The Wireless Hardware:

DD-WRT runs on a wide variety of commodity hardware. For this example we'll be using the Netgear WNDR3300. They can be found used and refurbished for around $50 each. It supports 802.11 A, B, G, N and has gigabit Ethernet ports. Not a bad deal and they're fully supported by DD-WRT. As we can see in the example, we'll be using 802.11 N for the wireless backplane, and gigabit Ethernet and 802.11 G for clients.

Installing DD-WRT:

The first step is replacing the default Netgear firmware with DD-WRT. The proper firmware images should be downloaded and saved to your desktop. You'll need the following files:

1. dd-wrt.v24_std-wndr3300.chk
2. dd-wrt.v24_std_generic.bin

Log into the DD-WRT router database and type in WNDR3300. The most recent versions of the files will be listed. It's usually recommended to use the latest development release. Even though it's listed as "development" it's actually quite stable.

Next, you'll need to replace the stock firmware with DD-WRT. Follow these steps, except using the latest firmware which is linked above. To summarize, you'll log into the Netgear WNDR3300, flash it with the first file, wait for it to reboot, and then flash it with the second file. At this point you'll have a fully-functioning DD-WRT installation. Repeat this process with all 3 APs listed in the example.

Helpful hint: visually label each AP with a name, e.g. AP1, AP2, and AP3. AP1 will be configured differently than the other two and it'll save headache down the road.

Configuring AP1:

AP1 is essentially the brains of the operation. It'll be acting as the primary router for the network and have both the 802.11 G and N radios active. You'll first connect to the web interface at http://192.168.1.1 and set both the username and password. After logging in, you'll see a basic dashboard of DD-WRT. We'll walk through each step of configuration.

1. Click on Setup -> Basic Setup. This sets the basic network settings.
   1. WAN Connection Type should be set to Automatic Configuration - DHCP.
   2. Router Name should be set to something unique, e.g. AP1.
   3. Router IP can be set to the IP range you'll be using. I'm a big fan of 10.0.0.0/8 since there's obviously a lot of space. In this example, we'll have the Local IP Address as 10.15.25.1 and the Subnet Mask as 255.255.255.0.
   4. At this point, click Save and Apply at the bottom to set the values for DHCP.
      Please note: You'll now need to reconnect to the router at http://10.15.25.1 instead of the previous address.
   5. DHCP Type should be set to DHCP Server and Enable.
   6. Set the Start Address as something slightly higher so you'll have static IPs when you need them. I'd recommend 10.15.25.25
   7. Make sure all of the options for DNSMasq and DHCP-Authoritative are checked.
   8. Under Time Settings, check Enable for the NTP Client and set the Server IP to pool.ntp.org
   9. Click Save and then Apply.
      
      
2. Click on Wireless -> Basic Settings. This sets the basic wireless settings.
   1. For Physical Interface wl0, set the following values:
      1. Wireless Mode is AP.
      2. Wireless Network Mode is NA-Only.
      3. Wireless Network Name is something unique that you'll remember, e.g. MyWireless-N. This name should be different than interface wl1.
      4. Wireless Channel is Auto.
      5. Channel Width is Auto.
      6. Wireless SSID Broadcast is Enable.
      7. Network Configuration is Bridged.
   2. For Physical Interface wl1, set the following values:
      1. Wireless Mode is AP.
      2. Wireless Network Mode is G-Only.
      3. Wireless Network Name is something unique that you'll remember, e.g. MyWireless-G. This name should be different than interface wl0.
      4. Wireless Channel is Auto.
      5. Wireless SSID Broadcast is Enable.
      6. Network Configuration is Bridged.
   3. Click Save and Apply Settings.
      
      
3. Click on Wireless -> Wireless Security. This sets the basic wireless security settings.
   1. The settings should be the same for both interfaces wl0 and wl1.
   2. Security Mode is WPA Personal.
   3. WPA Algorithms is TKIP.
   4. WPA Shared Key is a unique key you'll later use as a password. Set one and write it down.
   5. Click Save and Apply Settings.
4. Click on Services -> Services. Here you can set DD-WRT to use OpenDNS.
   1. Scroll down to DNSMasq.
   2. Set DNSMasq as Enable.
   3. Set Local DNS as Enable.
   4. Add the following under Additional DNSMasq Options:
      no-resolv
strict-order
server=208.67.222.222
server=208.67.222.220
   5. Click Save and Apply Settings.
      
      
5. Click on Setup -> DDNS. Here you can set DD-WRT to use DNS-O-Matic.
   1. Set DDNS Service as Custom.
   2. Set Do not use external ip check as No.
   3. Set DYNDNS Server as updates.dnsomatic.com .
   4. Set your User Name and Password as your OpenDNS credentials.
   5. Set Host Name as all.dnsomatic.com .
   6. Set URL as /nic/update? .
   7. Click Save and Apply Settings.

       

All done! AP1 is now configured to act as the primary access point for your network. Both OpenDNS and No-IP should be configured properly.

Configuring AP2 and AP3:

The next step is to configure AP2 and AP3 to act as client bridges to AP1. The process is the same for both AP2 and AP3, minus the IP and hostname. You will initially connect to each device at http://192.168.1.1.

1. Click on Setup -> Basic Setup. This sets the basic network settings.
   1. WAN Connection Type should be set to Disabled.
   2. Router Name should be set to something unique, e.g. AP2 or AP3.
   3. Router IP should be set to a static IP on the same subnet as AP1. In this example, we'll have the Local IP Address as 10.15.25.2 for AP2 and 10.15.25.3 for AP3. The Subnet Mask is 255.255.255.0.
   4. At this point, click Save and Apply at the bottom to set the values for DHCP.
      Please note: You'll now need to reconnect to the router at the IP address in the previous step.
   5. Under Time Settings, check Enable for the NTP Client and set the Server IP to pool.ntp.org
   6. Click Save and then Apply.
2. Click on Wireless -> Wireless Security.
   1. The settings should be the same for both interfaces wl0 and wl1.
   2. Security Mode is WPA Personal.
   3. WPA Algorithms is TKIP.
   4. WPA Shared Key is the password you specified for AP1.
   5. Click Save and Apply Settings.
3. Click on Security -> Firewall.
   1. Set SPI Firewall to Disable.
   2. Click Save and Apply Settings.
4. Click on Wireless -> Basic Settings.
   1. For Physical Interface wl0, set the following values:
      1. Wireless Mode is Client Bridge.
      2. Wireless Network Mode is NA-Only.
      3. Wireless Network Name is the value from AP1, e.g. MyWireless-N.
      4. Network Configuration is Bridged.
   2. For Physical Interface wl1, set the following values:
      1. Wireless Mode is Client Bridge.
      2. Wireless Network Mode is Disabled. We're only going to be using 802.11 N for the backplane.
      3. Wireless Network Name is the value from AP1, e.g. MyWireless-G.
      4. Network Configuration is Bridged.
   3. Click Save and Apply Settings.

Testing the Connection:

Plug your desktop or laptop into AP1 so you've got a network connection. You should be able to access the Internet. Once AP2 and AP3 have powered up, attempt to ping their IP addresses, e.g. ping 10.15.25.2 and ping 10.15.25.3. It might take a few seconds while the APs connect back to AP1. You should begin to receive an ICMP response.

In Conclusion:

That's it! Now AP2 and AP3 are joined to AP1. You can literally place AP2 or AP3 anywhere within wireless range of AP1. They'll act as switches connected directly back to AP1. It's completely transparent to anything that's connected. You can add additional APs following the exact same steps above.

On top of that, you can also enable port forwarding within DD-WRT. In combination with a dynamic DNS entry from No-IP, this will allow you to connect back to your network while on the road without having to remember your DHCP IP address.