HOWTO: Clockwork Mod From T-Mobile Froyo (Official KB5)

These are my notes. In standard disclaimer fashion, I am heavily tanked as I write this up. These are being written for a Windows 7 SP 1 computer with a Samsung Vibrant running KB5 FROYO. Use kies to get there if you’re playing along at home. Also drink a fifth of scotch.

The problem: KB5 is rootable via SuperOneClick BUT you can’t use clockwork. I suspect it’s because T-Mobile got seriously burned with the voodoo kernel and it’s Samsungs fault for not sticking to EXT3/4. On the other hand, it’s the users fault for not disabling voodoo before upgrading. That being said, if you’re reading this it’s because you didn’t send your phone in because you bricked it with voodoo.

BEFORE YOU DO ANYTHING: In the root of the internal sd card, make a folder called Voodoo (capitol V), and make a subfolder in there called disable-lagfix (all lowercase).

Step 1: Verify you can boot into download mode. To do this, hold VOL UP and VOL DOWN. Plug in the USB or the charger. If you get the shit shoveling android, you’re doing it right. If you don’t enter download mode, STOP. Figure out why.

Step 2: Grab Heimdall. Odin is crap. Thats the windows version.

Step 3: Grab any clockwork enabled kernel. I suggest overstock, which also works with Cyanogen. Its the de-facto kernel for voodoo and flashing, but most importantly it includes the clockwork recovery.

Step 4: Enter download mode, connect the phone and wait for the driver installation to fail. Now run zadig.exe from the heimdall drivers folder. Click “install drivers”. Windows will bitch. Install it anyway.

Step 5: With the phone connected and in download mode, open heimdall. Select the kernel I told you to download earlier. In the kernel field in heimdall, select the kernel. Click flash. The phone will reboot when this is done. Don’t panic, the phone will be slow and junky when it first starts. Don’t touch it for 10 minutes or so. I have no idea what the fuck it’s doing.

Step 6: Power off the phone. Disconnect the USB/Charger. Press and hold VOL UP and VOL DOWN and POWER until you see the word “vibrant”. You will be in red clockwork. Choose “backup” and let it do it’s thing. Once you choose backup you can plug the charger back in.

The end. You can now use clockwork to flash whatever ROM you want and you can use your old ROM to restore if you don’t like it.

Can’t Use Clockwork After T-Mobile’s 2.2?

So my wifes phone is fragged and I really hate to say it but I think running voodoo once to convert it to EXT4 and then undoing voodoo to convert it back to RFS is going to be the only way to fix it. RFS has a known problem with crosslinking and it’s just straight up garbage. In traditional tech fashion, cleaning up someone elses mess is typically an excersize in circumventing security and then hitting it. Samsung Galaxy S has a kernel backup and flasher app which lets you backup your kernel and apply whatever you want, but it doesn’t do much for applying voodoo. Running a voodoo kernel does you no good without the EXT4 conversion process. Therefor, we must use the appropriate clockwork to do the voodoo update process and… Clockwork doesn’t work!

I’ve run into problems with clockwork before and Jeeves, I know you read this, feel free to chime in with an alternate method. If you’re stuck not being able to apply update.zips and you know it’s a correctly signed zip, you need to change out your /system/bin/recovery executable. This process is the manual version of this process, and you must visit that post to grab the first so you have a recovery to put out there. Nothing against untermensch for his writeup but I feel like the whole adb thing is a crutch for a real shell on these phones.

REQUIREMENTS: Busybox, connectbot, root. Two braincells to rub together.

Grab the recovery binary out of the zip linked to in that post. Put it on the root of your internal storage (the ~12GB one). Fire up connectbot and connect to localhost so you have a command line. Cut and paste the following:

mount -o remount rw /system
mv /system/bin/recovery /system/bin/recovery.original
cat /mnt/sdcard/recovery > /system/bin/recovery
chmod 755 /system/bin/recovery
mount -o remount ro /system

Now you have 3E recovery (the correct version) and it accepts files. You can proceed with clockwork as normal. Now to streamline the voodoo process.

And if you’re really lazy – just paste that into a file called or whatever. Fire up connectbot and run /mnt/sdcard/

T Mobile Samsung Galaxy S Official Froyo Update Using Linux and VMWare Running Windows XP SP2

Yes, the Froyo update is out for the Galaxy S. If you’re like me, you’re running Linux as your host OS and you’re boned for the update because T-Mobile is a bunch of tossers and won’t OTA all at once.

There’s nothing particularly esoteric in this guide. If you’ve got a Galaxy S device and you’re a TMobile customer, you can use this guide.

If you got here googling for mini-kies and want the official update, that’s what we’re going to do.

REQUIREMENTS: Windows XP SP2. VM is OK. You also need a Samsung Galaxy S device running Android 2.1. You want Samsung mini-kies. You probably want to read this document.

The biggest question every asks: Does it work? Yup. Not only does it work but it enables wifi calling which is the #1 reason why I want to use it. With Wifi calling, when you call your spouse or whatever, it’s done over your wifi router (in my case, Verizon FIOS) and you don’t use your minutes.

The second biggest question: Does it put the AVATAR icon back which was the reason I rooted my phone? You betcha. You will look at that blue cat UNTIL THE END OF TIME.

Step 0: Uninstall all task managers and task killers you’ve added to the device. Reboot the phone. Seriously people leave a lot of cruft running.

Step 1: Fire up windows XP. Ensure you have all the updates. You’ve been warned. Your XP VM must have unmolested access to the internet.

Step 2: Press “properties” on the phone on the home screen (leftmost button). Select SETTINGS. Select APPLICATIONS. Select DEVELOPMENT. Enable USB Debugging. Do not plug in the phone yet.

Step 3: Click the link. Download and install mini kies. Run it once. Close it. Run it again. Get the update.

Step 4: Open Mini Kies. Plug the phone in. If you’re running VMWare you will be notified hardware is available but not connected. In the bottom right corner is a phone on a modem icon. Click it. Connect it.

Step 5: Allow Windows XP to install all the drivers it wants. Eventually kies will pick up the phone. If it doesn’t, unplug and replug the phone.

Step 6: Mini Kies will find the device and prompt you to update. It will sometimes fail to download, tough shit everyone reads my blog and now you’re the first to be last in line.

Step 7: About halfway through the install (the android digging you into a hole on the screen) you’ll get a second prompt from VMware to connect new hardware. DO IT. The update cannot complete if you don’t.

Step 8: You’ll probably get a third prompt to connect hardware (I set my VMWare to Just Do It). Let it do it. Answer YES to windows XP asking if you want to install drivers for new hardware.

Step 9: Enjoy Froyo. The phone takes about 10 minutes to do housekeeping and it runs like crap after that until it catches up.

Cool new stuff: Wifi calling, new marketplace (now I have to update everything), and the one no-one expected – TMobile TV. However TMobile TV is a trap and it bills you $10/mo for the premium TV. Skip it and instead look at the newly unlocked samsung media hub. Ohhhh…

No word on if Z4Root can root the official Tmobile froyo, so enjoy your blue cats icon.

Yes, you can do the mini-kies update if you’re rooted – but the update removes the superuser application and busybox.

UPDATE: z4mod (or z4root) doesn’t work anymore, one click root doesn’t work anymore, and the old version of Rage Against the Cage doesn’t work anymore. What are we to do? SuperOneClick works. As usual it takes forever to get the hook. When you use it, be sure you enable “non market apps”. As usual, root, enable apps, and then promptly reboot or you’ll end up in a weird place. If you plan on using titanium backup, root it first, then install the TB busybox, then reboot.

Obligitory rooted phone porn:

T-Mobile Confirms Froyo (Android 2.2) for Galaxy S on December 15th

You heard it here first folks. Complete transcript below:

You have been connected to ~Diane S.
~Diane S: Welcome to T-Mobile Chat service Josh. My name is Diane and for your reference my rep ID is 13-20532. First, please allow me one moment to review the information you have provided.
~Diane S: Hi there Josh, how are you today?
josh knarr: Doing fine
josh knarr: although overtaken by jealousy of my recently upgraded andoid buddies.
~Diane S: I can certainly help you today to see when the 2.2 upgrade for your phone will be coming out.
josh knarr: excellent.
~Diane S: Please allow me 3 minutes to research this for you.
josh knarr: sure.
~Diane S: There is a froyo 2.2 update coming out by Dec 15th, if this is compatible with your phone you will receive a message with regards to this.
josh knarr: It will be available to download immediately?
josh knarr: (immediately on the 15th, anyway?)
~Diane S: Unfortunately, this is all the information I have resources to, you will need to refer to google for this, as they are doing the upgrade.
josh knarr: OK
josh knarr: good enough.
josh knarr: thanks!
~Diane S: Is there anything else I can help you with today?
josh knarr: nope, I’ll look for frodo on the 15h. thanks.