[UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery

Search This thread

stachre

Senior Member
Mar 30, 2011
98
347
ATTENTION: Custom Android 3.2 ROM available! Both 3G and Wi-Fi users can enjoy Team Tiamat Xoom Rom 2.0.1 Manta Ray. If you want the latest features implemented by Team Tiamat, install Manta Ray; otherwise, if you want stock 3.2 with root, continue below.

IMPORTANT NOTE: This update is for the US Xoom Wi-Fi MZ604 with Android 3.1 ONLY!!! As of v05 of this update, the update script performs NO CHECKS of files before flashing rooted stock 3.2 system and boot images. This means it won't stop you from flashing on a Xoom 3G; 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, ready to restore to stock 3.1 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.

COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WI-FI MZ604 with Android 3.1 HMJ37. If you have a non-US Xoom Wi-Fi, this procedure may break your device. If you have a Xoom 3G, this procedure may break your device. If you're running a version of Android prior to 3.1, this procedure may break your device (update to 3.1 first).

[size=+1]SUMMARY[/size]

Here's a run-down on the current procedure:
  • Updates the Xoom Wi-Fi from 3.1 HMJ37 to 3.2 HTJ85B using ClockworkMod Recovery (update.zip)
  • Flashes system partition with rooted stock 3.2 image (minus the recovery overwrite script)
  • Includes Superuser.apk and su binary to enable functioning root (thanks, chainsdd)
  • Flashes the boot (kernel) partition with rooted stock 3.2 kernel (thanks, solarnz)
  • Stock kernel means no extras (overclocking, etc.) from custom kernels
  • Leaves existing recovery partition intact (stock 3.2 update overwrites it on every reboot)
  • Leaves user data intact
  • Includes Android 3.2 support for hardware SDCard (shows in Settings|Storage, /mnt/external1)

Outstanding Issues:
  • Too many steps: Include the edited updater-script, su, Superuser.apk in a custom update.zip
  • Requires stock 3.1 Boot partition (kernel): Need to include solarnz's stock rooted 3.2 boot.img and just flash that over whatever is there
  • Requires stock 3.1 HMJ37 System partition (ROM): Might include a stock 3.2 system.img and remove the checks for stock 3.1 system files, but it will make the .zip huge
  • Users with custom ROM's report issues after update: users suggest factory reset/full wipe (including user data) in ClockworkMod Recovery prior to updating (read through the thread for more info)
  • Superuser update available in market, but update fails: my bad for not including the latest and putting the apk in /system/app makes upgrading less easy. Delete superuser.apk using adb, terminal, or rootish file manager app, and the upgrade should work (thanks, GeekyGuy)

Now, without further ado...

[size=+1]ASSUMPTIONS[/size]

[size=+1]PROCEDURE[/size]
  1. Rename the modded Android 3.2 Update file to update.zip
  2. Reboot into recovery
    • Reboot your Xoom
    • When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
    • Press the Volume Up button to enter Android recovery
  3. Perform update
    Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also if you are coming over from a custom ROM, users suggest doing a factory reset/full wipe (including user data) ClockworkMod Recovery prior to performing the following steps (read the thread for more info).
    • In ClockworkMod Recovery, select "mounts and storage"
    • Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
    • On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
    • In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
    • In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
    • Select "+++++Go Back+++++"
    • Select "apply update from sdcard"
    • Select "Yes - Install /sdcard/update.zip"

      "Install from sdcard complete." will indicate that the update is completed.
      .
    • Select "reboot system now"
  4. Enjoy your rooted Xoom Wi-Fi, running on Android 3.2!

[size=+1]POST-UPDATE NOTES[/size]


[size=+1]CHANGELOG[/size]

  • v05: Removed system file checks and patches; instead flashes 3.2 system image with Superuser.apk and su binary preinstalled and recovery overwrite removed.
  • v04: Included Superuser.apk and su binary; no need to have them prior to updating. Still requires stock 3.1 HMJ37 system/ROM.
  • v03: First release of modded update.zip, removes check for stock 3.1 boot partition, flashes solarnz rooted stock 3.2 boot.img
  • v02: Added su symlink to updater-script
  • v01: First release, modded updater-script for manual mod to update.zip file
 
Last edited:

Epedemic

Senior Member
Apr 4, 2007
390
32
Nice. Had just finished "downgrading" to stock 3.1 and was about to try my luck with the original update file. Then i saw this. Installs fine, but i do not seem to have root nor will superuser from market update su. (i did replace the file in the .zip and installed via cwm).

But damn 3.2 seems fast at first glance, but might just be me ;)
 

LynnL

Member
Oct 29, 2010
40
4
If you have your Xoom powered down before you start, can you drag and drop the update.zip file to the SD card on your PC rather than doing the mount-and-copy? (If this seems like a stupid question, I only just rooted last weekend and don't want to take anything for granted!)
 

xMemphisx

Senior Member
Dec 7, 2008
81
33
Can't seem to make it work. I have tried several different times.

My output is always:

"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."
 

eliteone

Senior Member
Feb 23, 2009
248
46
are you on stock 3.1? afaik this only works on stock roms. thats the same error i get, and im running tiamat 1.1
 

stachre

Senior Member
Mar 30, 2011
98
347
Can't seem to make it work. I have tried several different times.

My output is always:

"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."

Xoom 3G users will likely get this error.
Xoom Wi-Fi users on any ROM other than stock 3.1 HMJ37 will likely get this error.

You need to be Wi-Fi on stock 3.1 HMJ37 at this point.
 

BrumBrum74

Senior Member
Dec 19, 2006
447
22
I'm getting some corby apk error when trying to run the update. Using stock 3.1 but rooted.

Xoom wi-fi US version.
 

Epedemic

Senior Member
Apr 4, 2007
390
32
Oh never mind. I missed that i needed to be rooted on stock 3.1... I will await solarnz boot.img or start over tomorrow if i get too impatient ;)
 

Sk8er Boi

Senior Member
Feb 11, 2005
114
12
38
Alexandria
getting same problem as above

"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."

i'm on stock 3.1 wifi us rooted
 

stachre

Senior Member
Mar 30, 2011
98
347
will this method wipe any of my data ?

It currently flashes over your boot partition and updates your system partition. User data is not affected.

Were do i find the stock 3.1 Kernel?

[IMAGES] HMJ37 (USA WiFi 3.1)

getting same problem as above

"Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys"
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted."

i'm on stock 3.1 wifi us rooted

What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.

EDIT: Also, through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    ATTENTION: Custom Android 3.2 ROM available! Both 3G and Wi-Fi users can enjoy Team Tiamat Xoom Rom 2.0.1 Manta Ray. If you want the latest features implemented by Team Tiamat, install Manta Ray; otherwise, if you want stock 3.2 with root, continue below.

    IMPORTANT NOTE: This update is for the US Xoom Wi-Fi MZ604 with Android 3.1 ONLY!!! As of v05 of this update, the update script performs NO CHECKS of files before flashing rooted stock 3.2 system and boot images. This means it won't stop you from flashing on a Xoom 3G; 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, ready to restore to stock 3.1 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.

    COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WI-FI MZ604 with Android 3.1 HMJ37. If you have a non-US Xoom Wi-Fi, this procedure may break your device. If you have a Xoom 3G, this procedure may break your device. If you're running a version of Android prior to 3.1, this procedure may break your device (update to 3.1 first).

    [size=+1]SUMMARY[/size]

    Here's a run-down on the current procedure:
    • Updates the Xoom Wi-Fi from 3.1 HMJ37 to 3.2 HTJ85B using ClockworkMod Recovery (update.zip)
    • Flashes system partition with rooted stock 3.2 image (minus the recovery overwrite script)
    • Includes Superuser.apk and su binary to enable functioning root (thanks, chainsdd)
    • Flashes the boot (kernel) partition with rooted stock 3.2 kernel (thanks, solarnz)
    • Stock kernel means no extras (overclocking, etc.) from custom kernels
    • Leaves existing recovery partition intact (stock 3.2 update overwrites it on every reboot)
    • Leaves user data intact
    • Includes Android 3.2 support for hardware SDCard (shows in Settings|Storage, /mnt/external1)

    Outstanding Issues:
    • Too many steps: Include the edited updater-script, su, Superuser.apk in a custom update.zip
    • Requires stock 3.1 Boot partition (kernel): Need to include solarnz's stock rooted 3.2 boot.img and just flash that over whatever is there
    • Requires stock 3.1 HMJ37 System partition (ROM): Might include a stock 3.2 system.img and remove the checks for stock 3.1 system files, but it will make the .zip huge
    • Users with custom ROM's report issues after update: users suggest factory reset/full wipe (including user data) in ClockworkMod Recovery prior to updating (read through the thread for more info)
    • Superuser update available in market, but update fails: my bad for not including the latest and putting the apk in /system/app makes upgrading less easy. Delete superuser.apk using adb, terminal, or rootish file manager app, and the upgrade should work (thanks, GeekyGuy)

    Now, without further ado...

    [size=+1]ASSUMPTIONS[/size]

    [size=+1]PROCEDURE[/size]
    1. Rename the modded Android 3.2 Update file to update.zip
    2. Reboot into recovery
      • Reboot your Xoom
      • When the Motorola logo splash screen appears, press the Volume Down button to scroll through boot options and select "--> Android Recovery"
      • Press the Volume Up button to enter Android recovery
    3. Perform update
      Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select. Note also if you are coming over from a custom ROM, users suggest doing a factory reset/full wipe (including user data) ClockworkMod Recovery prior to performing the following steps (read the thread for more info).
      • In ClockworkMod Recovery, select "mounts and storage"
      • Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
      • On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
      • In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
      • In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
      • Select "+++++Go Back+++++"
      • Select "apply update from sdcard"
      • Select "Yes - Install /sdcard/update.zip"

        "Install from sdcard complete." will indicate that the update is completed.
        .
      • Select "reboot system now"
    4. Enjoy your rooted Xoom Wi-Fi, running on Android 3.2!

    [size=+1]POST-UPDATE NOTES[/size]


    [size=+1]CHANGELOG[/size]

    • v05: Removed system file checks and patches; instead flashes 3.2 system image with Superuser.apk and su binary preinstalled and recovery overwrite removed.
    • v04: Included Superuser.apk and su binary; no need to have them prior to updating. Still requires stock 3.1 HMJ37 system/ROM.
    • v03: First release of modded update.zip, removes check for stock 3.1 boot partition, flashes solarnz rooted stock 3.2 boot.img
    • v02: Added su symlink to updater-script
    • v01: First release, modded updater-script for manual mod to update.zip file
    3
    FYI, Tiamat 1.4.5 which will come soon (i.e next few days) will support 3.2. (Unfortuantly it won't support earlier versions)
    3
    FYI: I'll have a complete update for this later, I.E you will be able to flash from any rom / kernel, as long as you have updated to 3.1
    2
    This superuser update bug is annoying....keeps trying to update but fails.

    Sent from my Xoom using XDA Premium App

    This worked for me:
    Used Rom Manager and deleted the superuser.apk from \system\apps
    Rebooted
    Immediately downloaded the newer superuser from the Market
    Ran superuser and updated the su binaries
    2
    OP Updated:

    v04: Included Superuser.apk and su binary; no need to have them prior to updating. Still requires stock 3.1 HMJ37 system/ROM.