[HOW TO] Install the leaked Android 4.0.4 ICS build on the Droid 4 (XT894)

---

Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich (build 6.16.206). This is an official build pulled from a Motorola server.

WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.

Android 4.0.4 System Version 6.16.206
Blur_Version.6.13.219.XT894.Verizon.en.US.zip (354.9 MB)
Blur_Version.6.13.219.XT894.Verizon.en.US.crc (10 bytes)
DOWNLOAD

INSTRUCTIONS:

(If you have never edited your build.prop file or modified the contents of your /system folder, you can most likely skip step 1.)

If you have an external SD card:

1. Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
2. (To keep root) Open Superuser, click the Settings icon, and update the su binary
3. Download/extract D4ics6.16.206.zip and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
4. (To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
5. Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
6. Use the volume down button to navigate to "Recovery" then use the volume up button to select it
7. When you see the android/triangle, press both volume buttons together
8. Select "apply update from sdcard" then press the power button
9. Select the zip file and wait for the installation to finish
10. Reboot
11. (To keep root) Open OTA RootKeeper and select "Restore root"

If you do not have an external SD card (root required):

1. Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
2. (To keep root) Open Superuser, click the Settings icon, and update the su binary
3. Download/extract D4ics6.16.206.zip and copy the enclosed zip and crc files to your phone's internal storage (do not change the file names)
4. Install ROM Manager
5. Install ES File Explorer, go to Settings, and check "Root Explorer" and "Mount File System"
6. Move the zip and crc files from internal storage to the /cache folder
7. (To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
8. Open ES File Explorer again, navigate to the /cache folder, click on the zip file, and open with ROM Manager
9. Select "OK" when you see the Reboot and Install message and wait for the installation to finish
10. Reboot
11. (To keep root) Open OTA RootKeeper and select "Restore root"

I wonder if there is a way to use the kexec exploit to make a rom out of this, with custom kernel.

There is no kernel source available to compile custom kernels for Motorola ICS builds, even if kexec were working on CDMA/LTE variants, which it isn't yet, so there is no work being done to debug or fix the current release of the kexec exploit until the ICS 3.0 kernel source drops.

Say you install this leaked ics and the OTA ics comes out... then the OTA ics is by far better then leaked current ics.... I know there is not a way to predict the future... what then do you'll think there will be a way to obtain said OTA update.....?

Sent from my DROID4 using XDA

So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.

Originally Posted by lorddunlow

So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.

Someone correct me if I'm wrong, but when you start flashing with a fastboot file, there are a certain number of specific partitions that are flashed individually. It's my understanding that this update changes the partitions in some way, so if you try to flash a Gingerbread file, it will expect certain partitions that aren't there any more.

OTA updates are always from one specific version to another. If VZW decides to make the official ICS build anything other than 6.16.200, then when the next update is released however long down the line, it will only push to devices running that particular build.

Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )

Also, even though we don't have source for the newer kernels, would it be possible to use the kernel from the leak (no changes), or is this just not possible w/out source?

Originally Posted by podspi

Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )

I'm sure it wouldn't be too difficult for a developer to create a fix similar to the one Timmy10shoes developed for the Bionic.

And VZW sent me a replacement so I was only without my D4 for a day

What version of kernel is included in this rom?

So have people been able to successfully install ICS and keep root with this method? Does safe strap install?