Skip to main content

Applying Jelly Bean OTA on your Nexus S

The official Nexus S OTA file for i9023 is now out!

Google OTA file
(MD5 – 12c718dbda2565609db45c9631a25adc)

I had used the Nexus S 4.0.4 factory images for my phone and left the boot loader unlocked. Unfortunately, the instructions for applying the official OTA apply only to those on boot-locked stock recovery or custom recovery. I tried doing it but got the "apply_patch_check assert failed" error message. You might want to try it first if you are on stock.

Just a tip for going to the recovery menu on stock ROM:

1. While phone is off, press Power and Volume Up continuously until the fastboot screen appears.
2. Press volume down to select Recovery, then press Power to select.
3. The phone will reboot, show the Google logo and show a robot with a red exclamation point.
4. Press Volume Up, then Power to go the recovery menu. I thought the the robot with the red exclamation was an error. Also make sure you press Volume Up first, then Power and not vice versa, otherwise nothing will happen.

I didn't want to lock my boot loader using "fastboot oem lock" because it would wipe my phone so I decided to flash a custom recovery ROM and then apply the OTA update manually.

The Cyanogenmod wiki has the best instructions for doing this. You'll need the SDK for this.

Once the custom recovery was flashed, I powered off, then reboot to recovery (Power+Volume Up). Select the apply update.zip. The update should proceed smoothly and reboot on Jelly Bean. Upon first boot, there will be an update message but all your apps and data should be intact.
Labels:

Comments

Post a Comment

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...
1 comment
Read more

iReport Default Date Parameter

If you want to set a default date for a jasperreports parameter, you can enter the following in the default value expression of the parameter. new Date() However, if you wanted the default to be relative from today, for example, 3 days ago, you will need to do go outside of the standard java date libraries (Date, Calendar) because JR parameter does not allow you to have multiple statements. You can write your own utility package or you can use Joda , a replacement library for the JDK date and time library. To use Joda in iReports, you need to extract the jar file and add it to Options -> Classpath. You may also drop the jar file in iReports' lib directory. You will also need to add this library to your application or report server. For setting a default date 5 days prior from today, use this: new org.joda.time.DateTime().minusDays(5).toDate() or this if you want the time part set to the beginning of the day: new org.joda.time.LocalDate().toDateTimeAtStartOfDay().minusDays(5).to...
5 comments
Read more

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@...
Post a Comment
Read more