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.
THIS IS NOT A CUSTOM ROM: 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 developers, install the ROM appropriate for your model (Team EOS Xoom 4G MZ602 JB ROM, Team EOS Xoom Wi-Fi MZ604 JB ROM, others in the forums); otherwise, if you want stock 4.1.2 JZO54K ROM and kernel with root, continue below.
COMPATIBILITY: This update is for the US Xoom Wi-Fi MZ604. Users with Xoom 3G/4G and non-US models have reported success with these stock rooted updates for MZ604; however, if you perform this procedure on any other model, you may break your device. 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.1.2 JZO54K 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 if there are any issues, you will need to deal with them. 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!
This is a modded update package (update.zip) that updates the US Xoom Wi-Fi from any ROM to stock rooted Android 4.1.2 JZO54K 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.1.2 boot image, stock kernel
Stock kernel includes no extras (overclocking, etc.) from custom kernels
Flashes system partition with rooted stock 4.1.2 image (minus the recovery overwrite script; includes gapps)
Includes Superuser.apk 3.1.3 and su binary to enable functioning root (thanks, chainsdd)
Hardware SDCard continues to be read-only via documented application permissions (at /storage/sdcard1 as of 4.1.1 JRO03H)
Leaves existing recovery partition intact (unmodded stock 4.1.2 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)
Download the modded Xoom Wi-Fi Android 4.1.2 JZO54K update package
Ensure a physical SDCard with enough free space is installed in your Xoom (required for ClockworkMod Recovery updates; update package requires about 155MB; run adb shell df to get a rough idea of optional nandroid backup size) and have it functioning properly
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.
Copy/download the modded Android 4.1.2 Update package to the SDCard
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
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.
Select "wipe cache partition"
Select "Yes - Wipe Cache"
Select "Wipe Dalvik Cache"
Select "Yes - Wipe Dalvik Cache"
Select "+++++Go Back+++++"
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.
Select "backup and restore"
"Backup complete!" will indicate that the update is completed.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the modded Android 4.1.2 update package
Select "Yes - Install <filename>"
"Install from sdcard complete." will indicate that the update is completed.
Select "+++++Go Back+++++"
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom Wi-Fi, running on Android 4.1.2 JZO54K!
Stuck on Motorola logo / Bootloops: Users report "Wipe data/factory reset" in ClockworkMod Recovery often resolves this issue.
file_getprop:failed to stat / assert_failed: The update checks the ro.product.model property in /system/build.prop to verify that the device is a Xoom before proceeding; if the system partition was formatted prior to installing or the currently installed ROM doesn't have this property set to "Xoom", the check will fail. Flash any compliant ROM (the stock system image from Google will also work) and retry.
v01: First release, JZO54K; includes root, Superuser.apk, su
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.
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.
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.
Ensure unpack-bootimg.pl and repack-bootimg.pl scripts are properly installed and configured on the workstation (thanks, alansj)
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.
Ensure ClockworkMod Recovery is properly installed and configured on the device (thanks, solarnz, bigrushdog, koush, et al)
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.
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:
See also the note on the previous step regarding "wingray" asserts.
Save all stock OTA update packages to the hardware SDCard
These will be installed via ClockworkMod Recovery later in the procedure.
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:
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.
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:
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.
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.
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.
Download and unpack the boot image
Run the following commands from the terminal/command prompt:
Once back to the local prompt, pull the image to the working directory:
adb pull /storage/sdcard1/system-root.img
Configure the device and test
Ensure the device and apps function normally, including root apps.
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.
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.
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.
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.
I've been using your updates since HoneyComb on my Euro Wifi without any problems.
I generally adjust the boot image manually, I like to persist adb in the default.prop, I find watching the logcat helps ease the nerves on the first boot after the flash.
Don't forget to click Thanks If this post has helped. It gives me a little warm feeling inside
I WILL NOT RESPOND TO PM'S REQUESTING TECHNICAL SUPPORT
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?