Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,779,023 Members 43,621 Now Online
XDA Developers Android and Mobile Development Forum

[UPDATE][ICS]Stock Android 4.0.4 IMM76, Root, via CWM Recovery (US Wi-Fi MZ604)

Tip us?
 
stachre
Old
(Last edited by stachre; 1st April 2012 at 05:48 PM.)
#1  
stachre's Avatar
Member - OP
Thanks Meter 345
Posts: 98
Join Date: Mar 2011
Default [UPDATE][ICS]Stock Android 4.0.4 IMM76, Root, via CWM Recovery (US Wi-Fi MZ604)

BEFORE YOU BEGIN

CUSTOM ROM AVAILABILITY: This is a stock rooted update (stock ROM, stock kernel), NOT a full-featured custom ROM. If you want the latest custom features implemented by Team EOS, install the appropriate Team EOS ROM (Team EOS Xoom 4G MZ602 ICS ROM) (Team EOS Xoom Wi-Fi MZ604 ICS ROM); otherwise, if you want stock 4.0.4 IMM76 ROM and kernel with root, continue below.

COMPATIBILITY: This update is for the US Xoom Wi-Fi MZ604 ONLY!!! If you have a Xoom 3G/4G, this procedure may break your device. If you have a non-US Xoom Wi-Fi, this procedure may break your device (though some have reported success). The update script verifies only whether the device identifies itself as a Xoom, performing NO CHECKS on the exact model of Xoom before flashing rooted stock 4.0.4 IMM76 system and boot images. This means it won't stop you from flashing on a non-US or 3G/4G device; it will just flash and you're left with the mess (if any). Please proceed only if you're tech-savvy with Android and the Xoom, backed up and ready to restore in case of issues, and good at troubleshooting. Please provide feedback and corrections, and I'll update the post as quickly as I can. Thanks!

WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.

SUMMARY

This is a modded update package (update.zip) that updates the US Xoom Wi-Fi from any ROM to stock rooted Android 4.0.4 IMM76 using ClockworkMod Recovery:
  • Flashes bootloader from a previous update (3.2.1 HTK55D) to ensure integrity (bootloader remains unlocked)
  • Flashes the boot partition with rooted stock 4.0.4 boot image, stock kernel
  • Stock ICS update fixed the Bluetooth tethering issue that was introduced in 3.2
  • Stock kernel includes no extras (overclocking, etc.) from custom kernels
  • Flashes system partition with rooted stock 4.0.4 image (minus the recovery overwrite script; includes gapps)
  • Includes Superuser.apk 3.0.7 and su binary to enable functioning root (thanks, chainsdd)
  • Hardware SDCard continues to be read-only via documented application permissions
  • Leaves existing recovery partition intact (unmodded stock 4.0.4 update overwrites it on every reboot)
  • Leaves user data intact (note: some users updating from custom ROM's recommend wiping data/factory reset to prevent issues)

PREPARATION
PROCEDURE
  1. Backup your data
    If you have issues with this update, you may need to "wipe data/factory reset" before the system will fully boot properly. For some, simply copying the contents of the Xoom's internal storage (mostly music, pictures, videos, etc.) to their PC is enough. Others require backup of their apps, app data, etc. using more robust solutions like Titanium Backup. Backup your data according to your needs.
    .
  2. Copy/download the modded Android 4.0.4 Update package to the SDCard
    .
  3. Reboot into recovery
    1. Reboot your Xoom
    2. When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
    3. Press the Volume Up button to enter Android recovery
  4. Wipe cache and dalvik-cache
    Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also that if you are coming over from a custom ROM, users suggest backing up data and doing a "wipe data/factory reset" in ClockworkMod Recovery instead.
    1. Select "wipe cache partition"
    2. Select "Yes - Wipe Cache"
    3. Select "advanced"
    4. Select "Wipe Dalvik Cache"
    5. Select "Yes - Wipe Dalvik Cache"
    6. Select "+++++Go Back+++++"
  5. Optional: Perform nandroid backup (long)
    If you have issues with this update, you may need to "wipe data/factory reset" before the system will fully boot properly. Performing a nandroid backup in ClockworkMod Recovery allows you to fully restore your device's state if you need to revert for whatever reason. Note that backing up even a bare system runs a few minutes, so this could take a very long time and require the availability of a power charger. You also need sufficient free space on your SDCard to perform the backup; the backup process does not verify required space before starting, simply failing (and wasting your time) if it runs out.
    1. Select "backup and restore"
    2. Select "Backup"
    3. Be patient

      "Backup complete!" will indicate that the update is completed.
  6. Perform update
    1. Select "install zip from sdcard"
    2. Select "choose zip from sdcard"
    3. Select the modded Android 4.0.4 update package
    4. Select "Yes - Install <filename>"

      "Install from sdcard complete." will indicate that the update is completed.
      .
    5. Select "+++++Go Back+++++"
    6. Select "reboot system now"

      New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
  7. Enjoy your rooted Xoom Wi-Fi, running on Android 4.0.4 IMM76!

POST-UPDATE NOTES
  • Stuck on Motorola logo/Bootloops: Users report "Wipe data/factory reset" in ClockworkMod Recovery often resolves this issue.
  • /system/bin/bugmailer.sh and /system/bin/send_bug: Included in stock ICS 4.0.4, these scripts allow for bug reporting with screenshots and logs via email. A number of Galaxy Nexus users have reported annoyance with these scripts being inadvertently activated by pressing all three buttons (Power, VolUp, VolDown) at once, resulting in temporary slowdowns as the report is compiled. In testing, I haven't encountered these issues so far (Power-VolUp resets the Xoom, e.g.); however, if you wish to prevent these scripts from running, you can simply rename them. Search the forums for more info.

CHANGELOG
  • v01: First release, IMM76; includes root, Superuser.apk, su
The Following 26 Users Say Thank You to stachre For This Useful Post: [ Click to Expand ]
 
stachre
Old
(Last edited by stachre; 1st April 2012 at 04:29 AM.)
#2  
stachre's Avatar
Member - OP
Thanks Meter 345
Posts: 98
Join Date: Mar 2011
UPDATE PACKAGE DETAILS (v01)
BOOTLOADER: flashed with stock 4.0.4 IMM76 bootloader
  • Extracted from a previous update package (3.2.1 HTK55D)
  • Bootloader flashed after reboot
Code:
BCT[4->4] (vendor: 0x101 product: 0x5454 vers: 0x0)
RECOVERY: not flashed; left intact
BOOT: flashed with modded stock 4.0.4 IMM76 boot image with stock kernel
  • Kernel: flashed with stock 4.0.4 IMM76 kernel
    • 2.6.39.4-g42a0480 android-build@vpbs1 #1 SMP PREEMPT Tue Mar 13 15:58:08 PDT 2012
    • Includes no extras (overclocking, etc.) from custom kernels
  • default.prop: modded IMM76 default.prop (ramdisk)
    Code:
    ro.secure=0
    ro.allow.mock.location=1
    ro.debuggable=1
    persist.sys.usb.config=mtp
SYSTEM: flashed with modded stock 4.0.4 IMM76 system image
  • build.prop: stock 4.0.4 IMM76 build.prop
    Code:
    ro.build.fingerprint=motorola/tervigon/wingray:4.0.4/IMM76/292727:user/release-keys
    ro.build.description=tervigon-user 4.0.4 IMM76 292727 release-keys
  • REMOVED: Stock recovery install script, patch
  • ADDED: Superuser.apk 3.0.7 and su binary to enable functioning root (thanks, chainsdd)
  • Hardware SDCard continues to be read-only via documented application permissions
USERDATA: Launcher favorites updated with new Market intent (included in stock 4.0.3 IML77 update from Google)
  • /data/data/com.android.launcher/databases/launcher.db: updated with new Market intent.
The Following 7 Users Say Thank You to stachre For This Useful Post: [ Click to Expand ]
 
stachre
Old
(Last edited by stachre; 25th July 2012 at 07:47 PM.)
#3  
stachre's Avatar
Member - OP
Thanks Meter 345
Posts: 98
Join Date: Mar 2011
STOCK ROOTED UPDATE PACKAGE BUILD PROCEDURE

For the curious and do-it-yourself types, this is how I produced this stock rooted update for the Motorola XOOM Wi-Fi MZ604 (US). I use Ubuntu, but this should also work on other *nix flavors, including OSX. The handy scripts provided by alansj for unpacking and repacking boot images, however, are not Windows friendly.
  1. Ensure Android SDK is properly installed and configured on the workstation
    Both adb and fastboot must be functioning properly in order to proceed. This procedure assumes that the directory containing adb and fastboot (or their symlinks) are in the PATH environment variable, allowing them to be called from anywhere.
  2. Ensure perl, cpio, gzip, and gunzip, are properly installed and configured on the workstation
    These are necessary to unpack and repack the boot image for modding.
  3. Ensure unpack-bootimg.pl and repack-bootimg.pl scripts are properly installed and configured on the workstation (thanks, alansj)
    HOWTO: Unpack, Edit, and Re-Pack Boot Images
    This procedure assumes that the directory containing these scripts (or their symlinks) are in the PATH environment variable, allowing them to be called from anywhere simply by their name. Note that some PERL configurations may require calling perl and passing the path to the script as an argument.
  4. Ensure ClockworkMod Recovery is properly installed and configured on the device (thanks, solarnz, bigrushdog, koush, et al)
    [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
    Also ensure that the ClockworkMod Recovery image is in the working directory on the workstation in case it needs to be reflashed.
  5. Download su and Superuser.apk (thanks, chainsdd)
    http://androidsu.com/superuser/
    Extract the ZIP file containing su and Superuser.apk into the working directory on the workstation.
  6. Download stock images and previous OTA (Over The Air) update packages
    3.0.1 HWI69 Images: http://developer.motorola.com/produc...rm=unlockboard
    3.1 HMJ37 OTA: http://android.clients.google.com/pa...9.e379f0b9.zip
    3.2 HTJ85B OTA: http://android.clients.google.com/pa...7.db223b6e.zip
    3.2.1 HTK55D OTA: http://android.clients.google.com/pa...B.73617300.zip
    3.2.1 HTK75D OTA: http://android.clients.google.com/pa...D.01cd4f05.zip
    4.0.3 IML77 OTA: http://android.clients.google.com/pa...D.71a21bfe.zip
    Note that the OTA update scripts check properties to see if the device is identified as "wingray". The above linked version of ClockworkMod Recovery identifies itself as "stingray", so you will get assert errors and the installation will fail. You can disable script asserts by using the toggle script asserts menu option (under install zip from sdcard), but keep in mind that this will allow you to install the updates out of order. The other, safer but more labor-intensive option is to edit the updater-script in each package and remove the "wingray" asserts.
  7. Download the current stock OTA update package
    Google hosts the OTA updates for the Motorola XOOM Wi-Fi MZ604 (US). The devices periodically check Google for updates, and when an update has been made available, it will be downloaded (usually to /cache/) with a notification presented to the user.

    The full URL to the update package is output to the device log, which is available via logcat (adb logcat; DDMS; aLogcat app). The full URL can also be constructed from just the filename -- available in the device's /cache/ directory if downloaded, or often by searching the web -- by appending it to the following path:

    Code:
    http://android.clients.google.com/packages/ota/motorola_tervigon/
    In this case, we find that the IMM76 update package's filename is 0d062b3bcbc7.signed-tervigon-IMM76-from-IML77.0d062b3b.zip, which yields the following URL:
    4.0.4 IMM76 OTA: http://android.clients.google.com/pa...7.0d062b3b.zip
    See also the note on the previous step regarding "wingray" asserts.
  8. Save all stock OTA update packages to the hardware SDCard
    These will be installed via ClockworkMod Recovery later in the procedure.
  9. Connect the XOOM to the workstation via USB
    Also verify that USB debugging is enabled in the settings on the device. The device should show up if the following command is run from a terminal/command prompt:
    Code:
    adb devices
  10. Backup the device
    This process is going to overwrite everything on the device, so backup using whatever method is preferred. ClockworkMod Recovery's Nandroid backup is a great option.
  11. Flash stock images via fastboot
    Unpack the zip file containing the stock HWI69 images into the working directory on the workstation and run the following commands from a terminal/command prompt:
    Code:
    cd <path to working directory>
    adb reboot bootloader
    fastboot flash boot boot.img
    fastboot flash system system.img
    fastboot flash userdata userdata.img
    Keep this terminal/command prompt open, as it will be used further.
  12. Install stock OTA updates via ClockworkMod Recovery
    Reboot after each update to ensure that it completes -- bootloader updates (HMJ37 and HTK55D), for instance, are performed after rebooting -- but ensure the boot sequence is interrupted with the VolDown key and re-enter ClockworkMod Recovery before the boot animation begins, to prevent overwriting with stock recovery.

    Without a bootloader update, press VolDown after waiting a few seconds on the red Motorola logo screen. If there is a bootloader update, however, it gets tricky; after the automatic reboot, wait about 14 seconds on the red logo before pressing VolDown. If nothing happens, reset (Power + VolUp) and try again. If the boot animation begins, try resetting but note that recovery was likely overwritten by stock, requiring a re-flash of ClockworkMod Recovery.

    Repeat this procedure of installing and rebooting until the last update is complete and the device is back into ClockworkMod Recovery.
  13. Perform a nandroid backup in ClockworkMod Recovery
    This generates clean, current stock images with which to work, while also providing an easier starting point for any future mods.
  14. Download and unpack the boot image
    Run the following commands from the terminal/command prompt:
    Code:
    adb pull /sdcard/clockworkmod/backup/<directory name>/boot.img boot-stock.img
    unpack-bootimg boot-stock.img
    This will extract the kernel and ramdisk gzip files into the current directory, with the actual ramdisk files being unpacked into a subdirectory (boot-stock.img-ramdisk).
  15. Modify default.prop in ramdisk
    Open default.prop (located in the ramdisk subdirectory) in the preferred text editor and edit the following properties:
    Code:
    ro.secure=0
    ro.allow.mock.location=1
    ro.debuggable=1
    ro.secure=0 is the most important, for it enables adb to run as root, which is necessary for remounting the system partition as read/write and install su.

    Clean up any temp/backup files the text editor may have created in the ramdisk directory before proceeding.
  16. Repack and flash the modified boot image
    Run the following commands from the terminal/command prompt:
    Code:
    repack-bootimg boot-stock.img-kernel.gz boot-stock.img-ramdisk boot-root.img
    adb reboot bootloader
    fastboot flash boot boot-root.img
    fastboot reboot
    The device should now boot with a rooted boot image.
  17. Install and configure su and Superuser.apk; remove recovery overwrite files
    Remount the system partition as read/write and push the files using the following commands from the terminal/command prompt:
    Code:
    adb remount
    adb push su /system/bin/su
    adb push Superuser.apk /system/app/Superuser.apk
    adb shell
    Once in adb shell, configure the pushed files:
    Code:
    chown root.shell /system/bin/su
    chmod 6755 /system/bin/su
    ln -s /system/bin/su /system/xbin/su
    chmod 644 /system/app/Superuser.apk
    While still in adb shell, remove the recovery overwrite script and patch:
    Code:
    rm /system/etc/install-recovery.sh
    rm /system/recovery-from-boot.p
    reboot
    The device should now boot fully rooted.
  18. Extract the freshly rooted system image
    Run the following command from the terminal/command prompt:
    Code:
    adb shell
    Once in adb shell, dump the system image to the hardware SDCard:
    Code:
    dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/external1/system-root.img
    exit
    Once back to the local prompt, pull the image to the working directory:
    Code:
    adb pull /mnt/external1/system-root.img
  19. Configure the device and test
    Ensure the device and apps function normally, including root apps.
  20. Identify any updates outside of system and boot partitions (bootloader, userdata, etc.)
    Open all OTA update packages in the preferred ZIP archive manager and go through each updater-script (located in /META-INF/com/google/android/) to determine if any additional updates have been made. This will require some understanding of edify script, which is straightforward and easy to read.

    These additional updates will need to be included in the stock rooted update package in order to ensure safe update from any ROM.
  21. Assemble the update package
    This simple objective here is to package the rooted boot and system images, files for additional updates (if any), the updater-script with commands to perform the update, and any helper tools into an Android update package (essentially a ZIP file).

    While this is a complicated task, it is made easier by starting with existing custom update packages and modifying their contents and script.
  22. Test installation via ClockworkMod Recovery
    Load other ROMS -- stock Honeycomb, custom ROM's, etc. -- and test the update using the procedure in the OP. Note that you may need to reflash ClockworkMod Recovery one final time at this point.
  23. Restore personal device backup; dogfood
    Restore the backup you made prior to flashing the stock images at the beginning of this procedure, and upgrade your device with the package you've built. Bask in glory.
The Following 6 Users Say Thank You to stachre For This Useful Post: [ Click to Expand ]
 
REVHE4D
Old
#4  
Member
Thanks Meter 1
Posts: 40
Join Date: Dec 2009
Downloading now thanks.
 
willysp
Old
#5  
Senior Member
Thanks Meter 82
Posts: 568
Join Date: Apr 2010
Excellent instructions - it worked flawlessly!

THANK YOU!
 
summer_love
Old
#6  
Senior Member
Thanks Meter 18
Posts: 176
Join Date: Jun 2010
Location: UK
Thanks! Downloading, will wait for Google to (hopefully) fix the borked play store accounts before risking flashing.
 
willysp
Old
#7  
Senior Member
Thanks Meter 82
Posts: 568
Join Date: Apr 2010
Quote:
Originally Posted by summer_love View Post
Thanks! Downloading, will wait for Google to (hopefully) fix the borked play store accounts before risking flashing.
Not sure what you're referring to, but:

I did a full factory reset last night with the intent of flashing OOB HC from Moto then manually applying all OTA's today.

So, today I started with 4.0.3 fully wiped. Play Store updated itself, and I'm downloading "My Apps" with no issues.
 
summer_love
Old
#8  
Senior Member
Thanks Meter 18
Posts: 176
Join Date: Jun 2010
Location: UK
Quote:
Originally Posted by willysp View Post
Not sure what you're referring to, but:

I did a full factory reset last night with the intent of flashing OOB HC from Moto then manually applying all OTA's today.

So, today I started with 4.0.3 fully wiped. Play Store updated itself, and I'm downloading "My Apps" with no issues.
There are a number of users (myself included) who's play store accounts are broken on the server side, so we are unable to download purchased apps. Thank you for your advice, but there's nothing we can do, client side, to fix it. Your account hasn't been affected, which is why you are able to download.
 
willysp
Old
#9  
Senior Member
Thanks Meter 82
Posts: 568
Join Date: Apr 2010
Quote:
Originally Posted by summer_love View Post
There are a number of users (myself included) who's play store accounts are broken on the server side, so we are unable to download purchased apps. Thank you for your advice, but there's nothing we can do, client side, to fix it. Your account hasn't been affected, which is why you are able to download.
OK - didn't know that. Hope they fix it quickly for you.
 
summer_love
Old
#10  
Senior Member
Thanks Meter 18
Posts: 176
Join Date: Jun 2010
Location: UK
Quote:
Originally Posted by willysp View Post
OK - didn't know that. Hope they fix it quickly for you.
Thanks! Me too...

The Following 2 Users Say Thank You to summer_love For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes