= Samsung Galaxy S =

The Telstra model.

 * GT-I9000T
 * IMEI: 352622040146883
 * IMEI SV: 01
 * Firmware: 2.1-update1
 * Baseband version: I9000TDVJH3
 * Kernel: 2.6.29
 * Build: ECLAIR.DVJH3

*#1234#
 * PDA: I9000TDVJH3
 * PHONE: I9000TDVJH3
 * CSC: I9000TTELJH3

A recommendation for settings:
 * http://whrl.pl/RcEPvy (http://forums.whirlpool.net.au/archive/1646702)
 * http://whrl.pl/RcDhej

Handy links:
 * http://www.addictivetips.com/mobile/how-to-install-clockwork-recovery-to-your-android-phone/
 * http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000/
 * Rooting: http://forum.xda-developers.com/showthread.php?t=728754
 * This is a smart guy who's done some Android+Samsung hacking, ''and actually writes shit down''!  http://www.galexander.org/android/

Cyanogen Mod 7:
 * http://forum.xda-developers.com/showthread.php?t=1067074
 * Setting the SMSC: http://forum.xda-developers.com/showpost.php?p=11827819&postcount=1

http://www.romkitchen.org/samsung/?s=generator

Good howtos: http://forum.xda-developers.com/showthread.php?t=723596

Hardcore hacking: http://forum.xda-developers.com/showthread.php?t=1018862&page=10

Making a "recovery jig" if Three Button Recovery isn't working: http://forum.xda-developers.com/showthread.php?t=819551

Other useful links:
 * http://dougpiston.com/?page_id=85
 * http://forum.xda-developers.com/showpost.php?p=8789391&postcount=3
 * http://romkitchen.org/logs/4df7357052362.txt
 * http://romkitchen.org/tmp2/tmp.4df7357052362/JSD_No_Wipe-v13-12-18-30-14-06-4df7357052362.zip

Bootloaders for 2.3:
 * http://forum.xda-developers.com/showthread.php?t=1089989
 * http://forum.xda-developers.com/showthread.php?t=1047924


== Upgrading to MIUI ==

After the previous Romkitchen upgrade, a few things didn't work. It's taken this long to bother getting around to trying again.
 * No Gallery app
 * The SMS app force-closes pretty much immediately, had to install an alternate messaging app

Current:
 * GT-I9000
 * Firmware: 2.2.1
 * Baseband: I9000TDVJH3
 * Kernel: 2.6.32.9 hardcore@speedmod-k13d-500hz #22
 * Build no.: FROYO.Rom Kitchen XWJSD

Setup:
 * Disable 2-factor google auth
 * Nuke shitty Kies software from PC in case I need to use Odin at some point

Links:
 * Nifty bootloader flasher: http://forum.xda-developers.com/showthread.php?t=1047924
 * Something about 3-button recovery: http://forum.xda-developers.com/showthread.php?t=821698


Following http://forum.xda-developers.com/showthread.php?t=1047924

APNs:
 * Telstra Internet - telstra.wap
 * Telstra MMS - telstra.mms

Well here goes nothing:
 * 3-button download
 * connect to USB
 * drivers installed (again? different USB port this time)
 * ran Odin3 v1.7
 * confirmed it shows "Added!!"
 * Selected PDA file
 * Checked "Phone Bootloader Update"
 * Start !  (crossed fingers) {{{
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Gingerbread_Starter_SpeedMOD_ODIN.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> zImage
<ID:0/006> Removed!!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Added!!
}}}
 * The device reboots as advertised by Odin
 * Boots to OS as usual, whoo! Now I should never need to do this again.

What's changed? Only the kernel, nothing else (as expected).
 * Kernel: 2.6.32.9 hardcore@speedmod-k13e-500hz #36

Now flash it:
 * Reboot to CWM
 * Backup DATA
 * Wipe all DATA
 * Wipe Dalvik cache
 * Apply from SD card
 * Select it, hits Checking BML/MTD
 * Reboots, new bootloader splashscreen mentioned Cyanogenmod
 * Goes back to CWM, continues flashing
 * Completes, reboots to MIUI automatically
 * Initial setup wizard, connect to google account
 * Running MIUI-109300

Syncing includes all your apps, so it's busily installing all my shit again. I guess that's okay.

 * MIUIStats (anonymously submitted)
 * Unique ID: 85827C2E16FB3D46088F8BA0A059476F
 * Device: galaxysmtd
 * Version: MIUIUS-1.9.30-EN-GALAXYSMTD
 * Country: au
 * Carrier: Telstra Mobile

Hm, I guess BML/MTD is optional?

New details:
 * Baseband version: I9000XXJVK
 * Kernel version: 2.6.35.12-g4a2814b atinm@wolverine #1 Tue Sep 27 15:08:38 EDT 2011
 * Build number: MIUI-109300


== Problem with Google Authenticator ==

Google Authenticator reliably force-closes at startup, exactly as documented here: http://code.google.com/p/google-authenticator/issues/detail?id=140

The issue is that it tries to `chmod` something, and the `chmod` command isn't found where it's expected. This sounds like it's only a problem on Cyanogen-based distros (I'm running MIUI).

This comment has a workaround: https://market.android.com/details?id=com.google.android.apps.authenticator&reviewId=15071831872562752248

Summary:
 1. Start a terminal
 1. Get root
 1. Remount `/system` as read-write (not sure if this is strictly necessary) {{{
mount -o remount,rw /system
}}}
 1. `cd` to `/system/bin`
 1. Symlink the `chmod` binary into here {{{
ln -s ../xbin/chmod chmod
}}}
 1. Now Google Authenticator works again, and you're no longer locked out of your account. \o/