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 3e_recovery_installer.zip 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:

su
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
exit

Now you have 3E recovery (the correct version) and it accepts update.zip 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 3e_recovery.sh or whatever. Fire up connectbot and run /mnt/sdcard/3e_recovery.sh