Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

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

OP stachre

12th July 2011, 11:02 PM   |  #1  
stachre's Avatar
OP Member
Thanks Meter: 345
 
98 posts
Join Date:Joined: Mar 2011
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).

SUMMARY

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...

ASSUMPTIONS
PROCEDURE
  1. Rename the modded Android 3.2 Update file to update.zip
  2. 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
  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).
    1. In ClockworkMod Recovery, select "mounts and storage"
    2. Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
    3. On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
    4. In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
    5. 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
    6. Select "+++++Go Back+++++"
    7. Select "apply update from sdcard"
    8. Select "Yes - Install /sdcard/update.zip"

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

POST-UPDATE NOTES

CHANGELOG
  • 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 by stachre; 27th July 2011 at 09:12 AM.
The Following 39 Users Say Thank You to stachre For This Useful Post: [ View ]
12th July 2011, 11:05 PM   |  #2  
willverduzco's Avatar
Portal Administrator
n͖̜̺y̥͔̗̝̠̩̜c̖͙͇̲̞
Thanks Meter: 2,898
 
6,422 posts
Join Date:Joined: Apr 2010
Excellent work! Guide stuck for the time being.
12th July 2011, 11:40 PM   |  #3  
Senior Member
Thanks Meter: 18
 
309 posts
Join Date:Joined: Apr 2007
More
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
12th July 2011, 11:40 PM   |  #4  
Member
Thanks Meter: 4
 
32 posts
Join Date:Joined: Oct 2010
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!)
12th July 2011, 11:46 PM   |  #5  
stachre's Avatar
OP Member
Thanks Meter: 345
 
98 posts
Join Date:Joined: Mar 2011
Quote:
Originally Posted by LynnL

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?

As long as the file is there, you're good to go.
The Following User Says Thank You to stachre For This Useful Post: [ View ]
12th July 2011, 11:54 PM   |  #6  
xMemphisx's Avatar
Member
Thanks Meter: 33
 
78 posts
Join Date:Joined: Dec 2008
More
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."
12th July 2011, 11:58 PM   |  #7  
Senior Member
Thanks Meter: 47
 
245 posts
Join Date:Joined: Feb 2009
More
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
13th July 2011, 12:03 AM   |  #8  
Senior Member
Thanks Meter: 18
 
309 posts
Join Date:Joined: Apr 2007
More
By the way, i have a UK Xoom but i went to 3.1 via stock US FW.
13th July 2011, 12:03 AM   |  #9  
Senior Member
Thanks Meter: 20
 
125 posts
Join Date:Joined: Aug 2010
Quote:
Originally Posted by eliteone

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

I'm running stock with a custom kernel and getting the same error.
13th July 2011, 12:05 AM   |  #10  
Senior Member
Thanks Meter: 47
 
245 posts
Join Date:Joined: Feb 2009
More
you need to be running stock kernel i believe

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes