This is the instructions that ended up working flawlessly to root my G1, install JesusFreke’s 1.51 T-Mobile US ROM,  and setup AppstoSD.  I must’ve wiped my phone about a half-dozen times and spent ridiculous amounts of time trying to make this work the way it was supposed to.  (By the way,  thank you Krista,  for convincing me to get a G1 over a Blackberry Bold.  I love this phone.)

Androidandme has a great guide to root your phone which I’ve condensed here – and stripped out everything that didn’t work for me.

First backed up all of my data using MyBackup Pro ($4.99 in Market) and saved it to my SD card.

Hooked the phone up to my system and mounted,  then copied over all my pictures,  videos,  and backups.

• Click the notification on your phone that says “USB Connected”.  Select the “Mount” option.

Formatted the entire SD card using FAT32 (do not use Quick Format).

• Right click Removable Disk and select Format.
• Select FAT32 for the file system,  then click Start

Once the disk is done formatting,  download DREAIMG.nbh.  You can do this with the root application below,  but this always downloaded corrupted over 3G & Edge (I did both, several times) and wasted a bunch of time.  I’ve uploaded a copy of RC29 DREAIMG.nbh to my Dropbox account.

• DREAIMG.nbh http://bit.ly/wfAOO (90mb)
• Copy DREAIMG.nbh onto the SD card root (don’t put it into a folder) through the USB mount.
• After the copy finishes, right click Removable Disk and choose Eject.
• Disconnect the USB cable from your phone.

Now we’re going to wipe the phone entirely (make sure you’ve used MyBackup Pro,  or Nandroid before doing this,  seriously) and install RC29 with the exploitable root hole.

• Power off your phone by holding the red ‘end talk’ button (Power) down, and choosing Power Off
• Hold the Camera button down,  and power the phone back with the Power button
• Once the bootloader fully loads,  press the Power button to start update
• When completed press the trackball (Action Key) to continue
• Reboot the phone by pressing Talk, Menu, Power at the same time
• Go through the steps to setup a fresh install of Android

Now download the root script here from the Android browser: http://bit.ly/L9ast (Leads to: http://www.androidactivity.com/root/root.apk)

Tap on the root.apk in your browser download list,  it will notify you that this program needs to be allowed because it is a non-Market application.  Click the provided Settings button and allow non-Market apps.  Hit the back button,  then tap the root.apk download to install.

Now there are two ways to do this,  both worked for me,  but I’m paranoid of downloading critical updates OTA at this point.

• OTA: Run the root.apk in your apps list and tap Step2:  Download IMG and HardSPL files to get the recovery files.
  • or
• Direct: Download the IMG and HardSPL files directly on your computer,  and copy onto the root of your SD card with a USB mount.
  • Recovery (2.7MB) [recovery.img] – http://bit.ly/K7FXI
  • HardSPL (177k) [update.zip] – http://bit.ly/qdm7P

Once the files are downloaded onto your SD card’s root perform these steps.

• Go to the home screen and open up your keyboard.
• Hit enter, pause a second, then hit enter again.
• Type telnetd in all lower case minus the quotes. Ignore the contact search that comes up.
• Press enter again.

Now run the root.apk application and tap Step3: Protect your root.  This will root your phone with the SPL upgrade.  Any errors means telnetd is not running,  so go back and do those steps again.  Now we need to reboot the phone again and run the update.zip on the SD card.

• Hold the Power button down and choose “Power Off”
• Hold the Home button down and the Power button until the phone turns back on
• When the yellow warning sign appears,  hit ALT+S on the keyboard
• When finished reboot the phone by pressing Talk, Menu, Power at the same time

Last step before adding the custom build is updating the radio to support Android 1.5.

• Download the radio update (9mb) [update.zip] – http://bit.ly/102Ndj
• Plug your phone into your computer and mount USB
• Copy update.zip onto the root of the SD card (overwrite or remove previous files if still there)

• Hold the Power button down and choose “Power Off”
• Hold the Home button down and the Power button until the phone turns back on
• When the yellow warning sign appears,  hit ALT+S on the keyboard
• When finished reboot the phone by pressing Talk, Menu, Power at the same time

Time to update to a custom build of Android.  I went with JesusFreke’s 1.51 US build,  which has the T-Mobile apps built in.

• Download the JF 1.51 update (36mb) [JFv1.51_CRB43-US.zip] – http://jf.andblogs.net/wp-content/plugins/download-monitor/download.php?id=14
• Plug your phone into your computer and mount USB
• Rename JFv1.51_CRB43-US.zip to update.zip
• Copy update.zip onto the root of the SD card (overwrite or remove previous files if still there)

• Hold the Power button down and choose “Power Off”
• Hold the Home button down and the Power button until the phone turns back on
• When the yellow warning sign appears,  hit ALT+L to display loader
• Press ALT+W to perform a factory wipe [Thanks to David for pointing this out in the comments,  ran into the same issue on a friend's G1 and a wipe prior resolved.]
• Once wipe finishes,  press ALT+S to load update.zip
• When finished reboot the phone by pressing Talk, Menu, Power at the same time

Alright.  Now you’re running a custom Android build.  Other builds are available as well,  here’s a few resources in case you’re curious (the steps are the same to install those instead).  Haykuro & The Dude both have their own builds,  and you can download different JF versions at his blog.

Before doing anything else I highly suggest running configuring your Apps and Cache to run off of your SD card – the whole reason I went through all of the nonsense above is because I screwed my installation up trying to do this after I already had my phone pretty loaded with stuff.  Without AppstoSD eventually your G1 will run like absolute crap as the memory dwindles down and it can be pretty frustrating.

• Format your SD card one more time to FAT32 just to be safe
• Download this zip containing a2sd.sh and init.rc – (1k) [a2sd.zip] – http://bit.ly/3QXx1
• Unpack a2sd.zip to your SD card’s root
• Start the Terminal Emulator and type:
  • su
  • cp /sdcard/init.rc /data/
  • cp /sdcard/a2sd.sh /data/
• Reboot your phone

Now install the AppstoSD2 application created by MarcusMaximus

• Go here in the Android browser to install – (68k) [AppstoSD2.apk] - http://bit.ly/18jVr7
• Choose the amount you want to partition your card,  I did around 500-600MB,  doubt you’ll need even that much.  Whatever you do,  don’t go past 1.5GB.
  • It might take a minute – do not restart/power off your phone,  just wait.  It’ll eventually reboot on it’s own. [Update: I've been told that it might not reboot automatically and the app will give a 'reboot now' button instead,  I haven't seen this myself,  drop me a line in the comments or on twitter if it does!]

• After the reboot run AppstoSD2 and press Copy Apps to SD

• Start the Terminal Emulator and type:
  • su
  • mkdir /system/sd/app-private
  • mkdir /system/sd/dalvik-cache
• Reboot one last time

You’re done!  If you check the Settings it should say that you have however much space you made your Ext2 partition as available system memory – and your phone should never lag.

The guide mentioned Intrepid has the ability to create an automounting private folder using ecryptfs‐utils with next to no setup. That’s nice, but I’d rather have a bit more control over the folder – having it just pop up on login isn’t very appealing since my system gets used from time to time by other people. A bit of googling around turned this up:

1. How to auto-configure
   
2. How to configure hands on
3. The basic truecrypt way

Ubuntugeek has a nice writeup on the under-the-hood way to use ecryptfs-utils. The reason I’m going with this over Truecrypt is I’d rather have the files encrypt on the fly without needing a set amount of space first (as in a container). I’ll keep the containers on my thumb drives for now.

Started with the Ubuntugeek step by step:

• sudo aptitude install ecryptfs-utils
• mkdir ~/crypt
• chmod 700 ~/crypt
• sudo mount -t ecryptfs ~/crypt ~/crypt
  • chose 4 for passphrase
  • created passphrase<
  • selected aes for cipher
  • 16 for blocksize

After selecting my options:

Attempting to mount with the following options:
 ecryptfs_key_bytes=16
 ecryptfs_cipher=aes
 ecryptfs_sig=1c56a17407ef3160
 WARNING: Based on the contents of [/root/.ecryptfs/sig-cache.txt],
 it looks like you have never mounted with this key
 before. This could mean that you have typed your
 passphrase wrong.

Would you like to proceed with the mount (yes/no)? yes
 Would you like to append sig [1c56a17407ef3160] to
 [/root/.ecryptfs/sig-cache.txt]
 in order to avoid this warning in the future (yes/no)? yes
 Successfully appended new sig to user sig cache file
 Mounted eCryptfs

Not quite sure what just happened there. I just installed this thing, of course I haven’t mounted with this key before. I wasn’t asked for a plaintext passthrough either. Check to see if it worked anyways.

• cp Firefox_wallpaper.png ~/crypt
• ls ~/crypt
• sudo umount ~/crypt
• ls ~/ | grep crypt

Crypt is still there! Blast.

• ls ~/crypt

It still shows my png file too!

• gnome-open ~/crypt/Firefox_wallpaper.png

“Fatal error reading PNG image file: Not a PNG file”

Alright, so that’s good, it’s probably encrypted then. I’ll remount and see if it’ll open.

• sudo mount -t ecryptfs ~/crypt ~/crypt -o key=passphrase,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_passthrough=n
• gnome-open ~/crypt/Firefox_wallpaper.png

Yep, opens fine now. Since I was expecting Truecrypt style mount behavior from Windows I was expecting the entire folder to just disapear (even though I specifically created one, duh). Reading through the ecryptfs page and here made a bit more sense. Without pre-allocation there isn’t much of a choice anyways. Time to turn this bulky command into an easy use alias:

• echo "alias mount-crypt='sudo mount -t ecryptfs ~/crypt ~/crypt -o key=passphrase,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_passthrough=n'" | tee -a ~/.bash_aliases
• source .bashrc

Figuring out the above took a bit longer than those two lines… here’s some insight into my rookie mistakes. (460 through 471 was me playing videos in terminal via ascii, heh.)

Restart firefox,  it’s good to go.  Tested it with Wordle and GoToMyPC and didn’t have any issues at all – every other Java install method I’ve used hasn’t worked.

Installed & tested on:  Ubuntu 8.10,  9.04,  9.10 Alpha 2

hyperq just replaced his InputDevice section with the code below, when I checked my own xorg though I didn’t even have an InputDevice area at all – so I just pasted the following into the end of my xorg.conf and restarted X (ctrl+alt+backspace).

Section "InputDevice"
       Identifier      "Configured Mouse"
       Driver          "evdev"
       Option          "CorePointer"
       Option          "Buttons"       "7"
       Option          "ZAxisMapping"  "4 5"
       Option          "ButtonMapping" "1 2 3 6 7"
       Option          "Name"  "Logitech USB-PS/2 Optical Mouse"
EndSection

Once X loaded up I was able to use the buttons in Firefox, but that was about it. Still didn’t work in Nautilus, which is really where the functionality should be.

After a bit of hunting around I found this excellent UbuntuForum post by detyabozhye.

First step was to make sure that xserver-xorg-input-evdev was installed:

• locate evdev


Returned this for me:

xserver-xorg-input-evdev is already installed, no need to snag that particular package. Next was checking my installed USB devices to see exactly what Ubuntu thinks my Logitech MX-518 actually is.

• cat /proc/bus/input/devices

The device list is quite extensive, and I just pulled out the Logitech related bit

I: Bus=0003 Vendor=046d Product=c01e Version=0110
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:0b.0-4/input0
S: Sysfs=/devices/pci0000:00/0000:00:0b.0/usb1/1-4/1-4:1.0/input/input4
U: Uniq=
H: Handlers=mouse1 event1
B: EV=17
B: KEY=ff0000 0 0 0 0
B: REL=103
B: MSC=10

Perfect, this is the same thing I added into my xorg from earlier, so it definitely has the right mouse, and the Firefox back/forward buttons show this – but time to get it working with Nautilus. Unfortunately there isn’t a native way to do this, the buttons actually have to be bound to certain keys.

To do this there are two necessary packages, xvkbd and xbindkeys.

• sudo apt-get install xvkbd xbindkeys

Then xbindkeys needs to be configured to map the keys to Nautilus shortcuts.

• gedit ~/.xbindkeysrc

Paste in the following:

"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
  m:0x0 + b:6
"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
  m:0x0 + b:7

Hit CTRL+S to save, then ALT+F4 to close.

Started up xbindkeys and tested it in Nautilus – and nothing happened. Made sure the key commands themselves worked by hitting ALT+LEFT and ALT+RIGHT – moved back and forward just like it should, but my side buttons didn’t do it. The only thing different from what detabozhye did and myself is I defined the buttons, so I removed that part and matched deta’s suggestion, then restarted X. Firefox still worked, Nautilus didn’t.

This time I loaded xev to try and see what button was /actually/ being pressed since it obviously wasn’t 6 or 7 at this point.

• xev

(That was easy, eh?) Unfortunately xev is a pain in the arse to actually use. What I had to do was click, and hold the button to stop xev output from spamming my terminal and make very sure to not move the mouse (or more mouse movement spam would scroll by).

When I held down my large side button and scanned the output I saw this:

ButtonPress event, serial 34, synthetic NO, window 0x4000001,
root 0x13b, subw 0x4000002, time 13076697, (36,18), root:(1014,814),
state 0x10, button 8, same_screen YES

Finally, it’s not 6, it’s 8. Great. The little upper one was 9. Changed my .xbindkeysrc to update with the new buttons and then restarted xbindkeys

• killall xbindkeys
• xbindkeys

Finally works.

Of course, after doing all of this I had a flash of insight… I could’ve simply had xev output to a file instead of trying to watch the terminal window and then searched for it later, which I did as a test with a left click, then a right click, then a middle click.

• xev > xevoutput.txt
• left click, right click, then middle click (in the xev window)
• cat xevoutput.txt | grep button

Returns:

state 0x10, button 1, same_screen YES
state 0x110, button 1, same_screen YES
state 0x10, button 3, same_screen YES
state 0x410, button 3, same_screen YES
state 0x10, button 2, same_screen YES
state 0x210, button 2, same_screen YES

There ya go… left click = 1, right click = 3, middle mouse click = 2. If I did that earlier (and made life easier on myself) it would’ve returned 8 and 9 respectively.

Now this needs to be added to your startup list so it isn’t necessary to start it each time manually. The easy way to do this in Gnome is by clicking System -> Preferences -> Session. Click “Add”, then type xbindkeys for the name, and xbindkeys for the command, and a description if you’d like.

I don’t like doing things through the GUI if I don’t have to, so I hunted around for a way to configure it manually (mainly because I spent half my time SSH’d into the box from work and would rather have the way to work with or without a mouse). After all of the above though I decided I’m done screwing around with this nonsense for the day and will make that into another post later tonight.

• Hit <Alt>F2 then type gconf-editor and hit <enter>
• Click Apps > metacity > keybinding_commands

gconf-editor - Apps > metacity > keybinding_commands

You’ll notice I’ve already added some common programs and commands in.  Under keybinding_commands panel simply double click the Value line and type in the command you would like to make a shortcut for. Now click on global_keybindings to make the actual keyboard shortcuts.

gconf-editor: Apps > metacity > global_keybindings

Here I’ve actually created the shortcuts themselves.  <Super> is for the Windows key,  followed by a letter to finish it off.  <Super>g opens up pidgin,  <Super>c for xchat,  ect.

• sudo apt-get install flashplugin-nonfree
• killall firefox

Started Firefox back up again and was able to click the link he sent me – viewed just fine. Love how easy it is in this version of Ubuntu.

First thing I did was go and get Bootchart, “a tool for performance analysis and visualization of the GNU/Linux boot process”. Bootchart is easy enough to install,  and unpacks at 51mb:

• sudo apt-get install bootchart

Wandered over to the bootchart documentation to see if there was anything special I ought to know about and realized I’m using Ubuntu… none of this is necessary.  Simply install and restart.

• sudo shutdown -r now

Once restarted,  you’ll want to check out /var/log/bootchart for the png files with the bootchart output.  Here’s an example from my 8.04.2 test machine I’ve been working with today.

Ubuntu 8.04.2 bootchart

Ubuntu 8.10 bootchart

Ubuntu 9.10 Alpha 2 bootchart

For added awesome, since I have Dropbox running on my work ubuntu, work XP, and home ubuntu installations I was able to do this to get the .png over to my WinXP while writing this post:

cp /var/log/bootchart/*.png /home/kyle-test/Dropbox/Public

By the time I had turned back to XP Dropbox had already synced, and I was able to right click the uploaded PNG and choose Dropbox -> Public link, send a copy to my friend, and upload here into the post with absolute minimum effort. I’ll also have the file for comparison when I get home and do the same thing on 8.10.

Once I’ve learned enough to sufficiently decode this I’ll make another post explaining what each thing is and what can be configured/removed to make boot times faster.

In a nutshell, my HP dx5150 here at work boots in 30 seconds.

[UPDATE 6-20-09 4:36pm]
Just ran another bootchart on a fresh install of Ubuntu 9.10 Alpha 2 on my main machine – dropped from 24 seconds to 15, probably due to ext4 being the main filesystem.

[UPDATE 1-28-09 12:28am]
Finally got around to getting bootchart up on the 8.10 installation at home,  this one clocks in at 24 seconds!  Taking a look between the two it seems as if hard drive throughput is my biggest limiter – I only dropped 6 seconds on total boot time and this machine is at least 5 times as powerful as the dx 5150 at work.

• sudo apt-get install xchat
• wget http://mircryption.sourceforge.net/Downloads/mircryption_xchatsrc.zip
• wget http://voobar.follvalsch.de/files/mcps_xchat_0.4.0-alpha.tar.bz2
• unzip mircryption_xchatsrc.zip
• tar -xvf mcps_xchat_0.4.0-alpha.tar.bz2 -C /src
• cd /src/mcps_xchat_0.4.0-alpha
• mv Makefile ../ && mv dh1080 ../ && mv mircryption.cpp ../
• cd ..

Ran into this error on install and realized I hadn’t installed a compiler since reinstallation. There actually is no readme.txt and no .so file was created.

Trying to install mircryption.so into ~/.xchat2 (see readme.txt for more info)
cp mircryption.so ~/.xchat2
cp: cannot stat `mircryption.so’: No such file or directory
make: *** [install] Error

• sudo apt-get install g++
• make install
• xchat

On first load mircryption will have you set a masterpass phrase.  /setkey <key> sets your key.  Oh yes,  and you’ll want to remove everything afterwards…

• cd ..
• rm -R src/ README.txt mircryption_xchatsrc.zip mcps_xchat_0.4.0-alpha.tar.bz2

i386 instructions:

• sudo apt-get install xchat
• wget http://mircryption.sourceforge.net/Downloads/mircryption_xchatsrc.zip
• unzip mircryption_xchatsrc.zip
• cd /src/xchat
• make linux
• make install
• cd ../..
• rm -R src/ README.txt mircryption_xchatsrc.zip

• cp /etc/apt/sources.list sources.list.bak
• sudo gedit /etc/apt/sources.list

Paste the following at the bottom of the file (for 8.04 change intrepid to hardy):

deb http://linux.getdropbox.com/ubuntu intrepid main
deb-src http://linux.getdropbox.com/ubuntu intrepid main

• sudo apt-get update
• sudo apt-get install nautilus-dropbox
• killall nautilus

For Ubuntu 8.10 Intrepid Ibex

* (cp /etc/apt/sources.list sources.list.bak ; cat sources.list.bak ; echo “deb http://linux.getdropbox.com/ubuntu intrepid main” ; echo “deb-src http://linux.getdropbox.com/ubuntu intrepid main”) > sources.list.done && sudo rm /etc/apt/sources.list sources.list.bak && sudo mv sources.list.done /etc/apt/sources.list && sudo apt-get update && sudo apt-get install nautilus-dropbox && killall nautilus

Haha… went a little overboard here, don’t know what I was thinking. Don’t drink and linux!

A blue box icon should appear in the icon tray, right click and choose “Start Dropbox” to login or create an account and choose where the Dropbox folder will reside.

(Update for Hardy Heron) – My work test machine was installed originally as 8.04, so I changed the above to match:

* (cp /etc/apt/sources.list sources.list.bak ; cat sources.list.bak ; echo “deb http://linux.getdropbox.com/ubuntu hardy main” ; echo “deb-src http://linux.getdropbox.com/ubuntu hardy main”) > sources.list.done && sudo rm /etc/apt/sources.list sources.list.bak && sudo mv sources.list.done /etc/apt/sources.list && sudo apt-get update && sudo apt-get install nautilus-dropbox && killall nautilus

Worked fine. =)