Skip to main content

Upgrading Samsung Galaxy S to ICS

The best instruction guide for upgrading the Samsung Galaxy S is in Cyanogenmod's wiki. I followed the Mac OSX instructions using Heimdall Suite 1.3.2.

The "Installing the ClockworkMod Recovery" instructions will replace the recovery image of the phone and root it. You may then load any custom ROM to your phone after doing this. The trickiest thing in doing this is holding down Home+Volume Down while plugging the USB cable. I suggest you remove any casing you have on your Galaxy S while doing this. You will need the following files to install the recovery image. The links should be in the instructions. This step only needs to be done once. With Jelly Bean ROMs starting to appear, you will be able upgrade your phone easily using the recovery method.

heimdall-suite-1.3.2-mac.dmg (13MB)
hardcore-speedmod.tar (7.5MB)

After installing the recovery image, you can boot your phone normally and copy the ICS ROMs. There are typically 2 files that you need to install a ROM (main ROM and the Google Apps zip). The Google Apps file is usually distributed separately for legal purposes though some ROMs already have it included. I installed AOKP build 40 (Android 4.0.4) though by now there should be the newer AOKP Milestone 6 already.

aokp_galaxysmtd_build-40.zip (139MB)
gapps-ics-20120429-signed.zip (52MB)

Just follow the instructions in the wiki to install the ROM. After installing AOKP and Google Apps, I was able to boot into ICS, but the Google Sign-in did not appear. I had to boot again to recovery and reflash Google Apps. After doing that, the phone was now on ICS.

WARNING:

Installing a custom ROM will require a complete wipe of your apps and data so you will need to make a backup. I recommend Astro to backup the apps. Just use USB cable to copy your photos. For SMS, you can use either SMS Backup & Restore by Ritesh Sahu (backup to USB) or SMS Backup by Cristoph Studer (backup to Gmail). This part takes the longest.

The FM radio in the Galaxy S will not work anymore after you install a custom ROM.

Comments

Popular posts from this blog

Get uptime alerts in Telegram

You will be configuring 3 services. The assumption is that you have accounts already for these services. UptimeRobot — source of the uptime/downtime notifications. It currently supports email, Twitter, Slack, Pushover, Pushbullet and others but not Telegram. We will use the webhook notification as the way to send messages to Telegram. IFTTT — bridges UptimeRobot and Telegram by providing the webhook for UptimeRobot and triggering a message to Telegram. In IFTTT terminology: IF {event trigger from UptimeRobot}, then {send message to Telegram group} Telegram — destination of the notification. You will need to create a group for this. Telegram Configuration In Telegram, create a new group, if needed. You may opt to use an existing group. Go to @IFTTT and follow the instruction so link your Telegram account to your IFTTT account. Send /connect_group to @IFTTT and connect the group where you want to send the notifications. IFTTT Configuration Sign in to IFTTT and add a ne

Activating NDD on your Globe landline

NDD and IDD is not available by default on your new Globe landline to protect you from inadvertent charges due to calls to mobile phones and long distance numbers. Note that these instructions are for Metro Manila accounts. To activate NDD, you need call 730-1000. The problem is, an Interactive Voice Response (IVR) menu greets you at that number and there is no menu option to activate NDD. There is also no easy way to get to a human in the options. For credit card companies, I always use the "Report a lost card" option to reach an agent immediately. It appears there is no such shortcut with Globe's number. After several attempts at the menus, the way I got to an agent was to pretend to customize my plan and select the option that says the information is not helpful. Here's the guide: 730-1000 IVR Menu: 1 - English 1 - Globelines 1 - Customize your plan 1 - Customize your plan 2 - Not helpful 1- Talk to a customer agent It will take about 3 minutes for the

CI/CD for .NET Core

If you have a .NET API that you want to containerize, here are the steps to prepare it. Create docker image Push to repository Setup ECS The TLS 1.0 option is needed if your SQL Server database does not support TLS 1.2. The recommended option is to update your database to the secure protocol. You may also change sdk and aspnet version to 5.0 if you haven't updated to 6.0 yet. This Dockerfile uses a multi-stage build to get an optimal image size. Dockerfile FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build-env WORKDIR /app # Copy csproj and restore as distinct layers COPY *.csproj ./ RUN dotnet restore # Copy everything else and build COPY . ./ RUN dotnet publish -c Release -o out # Build runtime image FROM mcr.microsoft.com/dotnet/aspnet:6.0 WORKDIR /app # Enable TLS 1.0 RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@