Going from 2.3.x (Gingerbread) to CyanogenMod 7.2 (Gingerbread) is surprisingly simple unlike upgrading from Froyo. I’ll go into more detail below, but there are two necessary bits: an updated recovery rom and a custom (non-official) CyanogenMod rom. This version of CyanogenMod is specific to the Samsung Gio.
Before upgrading your Samsung Gio, you must first be running at least 2.3.x (Gingerbread) before continuing because of the use of ext4 instead of rfs. Please follow my upgrade guide “Upgrade Samsung Galaxy Gio from 2.2.x Froyo to 2.3.x Gingerbread” first.
Warning: Caveat emptor – While I used to this process to update my phone, I take no responsibility if you brick your phone. Be sure to back up anything you wish to save, this procedure works best when your Gio is fully wiped of data.
Awhile back I wrote about ‘Doing battle with a Dell R620 and Ubuntu‘ where I touched on the fact that booting from USB thumb-drive was a painful problem. In short, the same USB thumb-drive that would work in the R610 would not work in the R620.
It comes down BIOS support for USB and how it is handled. On the R610 there are 3 options: ‘auto-detect’, ‘floppy emulation’ and ‘hard drive’. Auto was hit-or-miss, floppy would not work but ‘hard drive’ worked every time. On the R620 there are no options so I can only suppose that it supports ‘floppy emulation’ upon detection of a USB thumb-drive.
Dell System E-Support Tool (DSET) is an informative tool used by Dell’s support engineers to help diagnose problems for their clients. It is almost a requirement now and Dell usually refuses to continue support without a DSET report.
The problem is that DSET is only supported on Redhat and SuSE Linux and there isn’t any information on how to get it running in Ubuntu. I’ve assembled a rough guide on how to get DSET up and running on Ubuntu 10.04 and 12.04 and it is tested against a Dell R610 and R620.
Going from 2.2.x (Froyo) to 2.3.x (Gingerbread) is an involved process as there is always the fear that you will ‘brick’ your phone. This fear usually keeps most people away from upgrading. I’ve found a process, with Google’s help and trial/error, that managed to get process done painlessly and without a dead mobile.
Here is a little back story: I was lucky enough to come across the Galaxy Gio in a bad state while at work. The mobile would turn on, give the Samsung logo then black-screen and would not boot any further. It wouldn’t have made a good paperweight but if I could salvage it, it was mine.
Note: This process is a requirement before upgrading to a Cyanogenmod release.