Develop Bugs

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

[size=+1]BEFORE YOU BEGIN[/size]
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 3G/4G MZ602 ICS ROM) (Team EOS Xoom Wi-Fi MZ604 ICS ROM); otherwise, if you want stock 4.0.3 IML77 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.3 IML77 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.
[size=+1]SUMMARY[/size]
This is a modded update package (update.zip) that updates the US Xoom Wi-Fi from any ROM to stock rooted Android 4.0.3 IML77 using ClockworkMod Recovery:
Flashes bootloader from a previous update (3.2.1 HTK55D) to ensure integrity
Flashes the boot partition with rooted stock 4.0.3 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.3 image (minus the recovery overwrite script)
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 (stock 4.0.3 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)
[size=+1]PREPARATION[/size]
Download the modded Xoom Wi-Fi Android 4.0.3 IML77 update package
update_US-Xoom-WiFi-4.0-IML77_stachre_v03.zip
MD5: d2808af539cacf2d48534bfa1169730e​
Ensure you have flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]​
Ensure a physical SDCard with enough free space is installed in your Xoom (required for ClockworkMod Recovery updates; update package requires about 150MB; run adb shell df to get a rough idea of optional nandroid backup size) and have it functioning properly
[size=+1]PROCEDURE[/size]
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.0.3 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 "advanced"
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"
Select "Backup"
Be patient
"Backup complete!" will indicate that the update is completed.
Perform update
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the modded Android 4.0.3 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.0.3 IML77!
[size=+1]POST-UPDATE NOTES[/size]
Stuck on Motorola logo/Bootloops: Users report "Wipe data/factory reset" in ClockworkMod Recovery often resolves this issue.
/system/build.prop errors: The updater-script mounts system and verifies that the product is a Xoom according to build.prop to prevent updating a completely different device. Some users are reporting issues with this. Until the issue is resolved in the update package, a version of the updater-script with this check removed (attached to this post) can be used:
Download the attached updater-script_no-buildprop-check.txt
Rename to updater-script
Make a backup copy of the update package
Open the update package in an archive manager (Winzip is usually a no-go; use 7zip in Windows)
Navigate to /META-INF/com/google/android and replace updater-script with the one you downloaded
If necessary, save the archive
Follow the update procedure above
[size=+1]CHANGELOG[/size]
v03: Accommodate devices running AOSP and Chinese leaked ROM's.
v02: (unreleased test)
v01: First release, IML77; includes root, Superuser.apk, su

[size=+1]UPDATE PACKAGE DETAILS (v01)[/size]
BOOTLOADER: flashed with stock 4.0.3 IML77 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.3 IML77 boot image with stock kernel
Kernel: flashed with stock 4.0.3 IML77 kernel
2.6.39.4-gf03a679 [email protected] #1
Includes no extras (overclocking, etc.) from custom kernels
default.prop: modded IML77 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.3 IML77 system image
build.prop: stock 4.0.3 IML77 build.prop
Code:
ro.build.fingerprint=motorola/tervigon/wingray:4.0.3/IML77/239789:user/release-keys
ro.build.description=tervigon-user 4.0.3 IML77 239789 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 update from Google)
/data/data/com.android.launcher/databases/launcher.db: updated with new Market intent.

Great! Finally time for an update.zip with the stock ROM (not that I have a problem with EOS, I love it).
Need to have the device with the latest stock Honeycomb, right?
Sent from my T-Mobile G2 using Tapatalk

rmcsc said:
Need to have the device with the latest stock Honeycomb, right?
Click to expand...
Click to collapse
The update flashes entire boot and system images, rather than just patches, so this should work with your device as-is. Wiping cache and dalvik-cache is good practice, but I'm not sure whether it's needed.
Backing up your data and a wipe data/factory reset might be needed if coming from custom ROM's, as well.

Getting an error (Status 7) - installation aborted.
The zip is on the external SD Card.
The recovery is Rogue 1.3.0 CWM 5.0.2.7 based.
Ideas?

ali4ek said:
Getting an error (Status 7) - installation aborted.
The zip is on the external SD Card.
The recovery is Rogue 1.3.0 CWM 5.0.2.7 based.
Ideas?
Click to expand...
Click to collapse
I've tested only on solarnz's CWM recovery linked in the OP, so there could be something in the package/script which Rogue doesn't like.
Also could be a botched download; does the MD5 hash match?

ali4ek said:
Getting an error (Status 7) - installation aborted.
The zip is on the external SD Card.
The recovery is Rogue 1.3.0 CWM 5.0.2.7 based.
Ideas?
Click to expand...
Click to collapse
I got the same error, wiped cache and delvik and went though using Rogue.
Works awesome thanks!

whatsamod said:
I got the same error, wiped cache and delvik and went though using Rogue.
Click to expand...
Click to collapse
I updated the instructions to include cache and dalvik wipe. Thanks!

Working perfectly up to now. Will update later on!
Sent from my Xoom using Tapatalk

what languages are on this ROM?? is it only English, Spanish and french?
and how can I add another languages like Arabic??

No multi-language support, only english-spanish-french... Waiting for greek language..

failed to stat "/system/build.prop"
No such file or directory
E:Error in /sdcard/update_US-Xoom-WiFi-4.0-IML77_stachre_v01.zip(Status 7)
what can I do I get stuck on logo motorola
please help

motazsayed said:
what languages are on this ROM?? is it only English, Spanish and french?
and how can I add another languages like Arabic??
Click to expand...
Click to collapse
there is no full Arabic menus but it can read any Arabic letters and to write you just need to install Arabic keyboard i use " swift x tablet " keyboard with no problems

Could someone of you upload the official boot animation of this release?
Thanks in advance!

Sk8er Boi said:
there is no full Arabic menus but it can read any Arabic letters and to write you just need to install Arabic keyboard i use " swift x tablet " keyboard with no problems
Click to expand...
Click to collapse
so no issues with the Arabic websites? no separated letters?

marmo said:
Could someone of you upload the official boot animation of this release?
Thanks in advance!
Click to expand...
Click to collapse
http://www.mediafire.com/?tmcsfo8yqil8s60
motazsayed said:
so no issues with the Arabic websites? no separated letters?
Click to expand...
Click to collapse
no everything works fine

Sk8er Boi said:
http://www.mediafire.com/?tmcsfo8yqil8s60
no everything works fine
Click to expand...
Click to collapse
thanks for ur help man.

Thanks installed perfectly

Many thanx!!
Intalled perfectly and is running like a dream.
Sent from my Xoom using xda premium

narxda said:
failed to stat "/system/build.prop"
No such file or directory
E:Error in /sdcard/update_US-Xoom-WiFi-4.0-IML77_stachre_v01.zip(Status 7)
what can I do I get stuck on logo motorola
please help
Click to expand...
Click to collapse
getting the same error here on rouge and solarnz recovery,made md5 check, wiped cash, factory reset, dalvik and still getting the same message!!
any help??
Edit:
when I toggle signature verification on, it fails to pass

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

[size=+1]BEFORE YOU BEGIN[/size]
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.
[size=+1]SUMMARY[/size]
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)
[size=+1]PREPARATION[/size]
Download the modded Xoom Wi-Fi Android 4.0.4 IMM76 update package
update_US-Xoom-WiFi-4.0.4-IMM76_stachre_v01.zip
MD5: f4e48ede1afd03f807233e95ac7a0a09​
Ensure you have flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]​
Ensure a physical SDCard with enough free space is installed in your Xoom (required for ClockworkMod Recovery updates; update package requires about 150MB; run adb shell df to get a rough idea of optional nandroid backup size) and have it functioning properly
[size=+1]PROCEDURE[/size]
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.0.4 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 "advanced"
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"
Select "Backup"
Be patient
"Backup complete!" will indicate that the update is completed.
Perform update
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the modded Android 4.0.4 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.0.4 IMM76!
[size=+1]POST-UPDATE NOTES[/size]
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.
[size=+1]CHANGELOG[/size]
v01: First release, IMM76; includes root, Superuser.apk, su

[size=+1]UPDATE PACKAGE DETAILS (v01)[/size]
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 [email protected] #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.

[size=+1]STOCK ROOTED UPDATE PACKAGE BUILD PROCEDURE[/size]
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)
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.
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.
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.
Download stock images and previous OTA (Over The Air) update packages
3.0.1 HWI69 Images: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
3.1 HMJ37 OTA: http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
3.2 HTJ85B OTA: http://android.clients.google.com/p...igned-tervigon-HTJ85B-from-HMJ37.db223b6e.zip
3.2.1 HTK55D OTA: http://android.clients.google.com/p...gned-tervigon-HTK55D-from-HTJ85B.73617300.zip
3.2.1 HTK75D OTA: http://android.clients.google.com/p...gned-tervigon-HTK75D-from-HTK55D.01cd4f05.zip
4.0.3 IML77 OTA: http://android.clients.google.com/p...igned-tervigon-IML77-from-HTK75D.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.
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/p...signed-tervigon-IMM76-from-IML77.0d062b3b.zip​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:
Code:
adb devices
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:
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.
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:
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).
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.
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.
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.
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
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.

Downloading now thanks.

Excellent instructions - it worked flawlessly!
THANK YOU!

Thanks! Downloading, will wait for Google to (hopefully) fix the borked play store accounts before risking flashing.

summer_love said:
Thanks! Downloading, will wait for Google to (hopefully) fix the borked play store accounts before risking flashing.
Click to expand...
Click to collapse
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.

willysp said:
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.
Click to expand...
Click to collapse
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.

summer_love said:
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.
Click to expand...
Click to collapse
OK - didn't know that. Hope they fix it quickly for you.

willysp said:
OK - didn't know that. Hope they fix it quickly for you.
Click to expand...
Click to collapse
Thanks! Me too...

Is the included bootloader unlocked? Would rather not unlock the bootloader again.

What about gapps? do we flash the Google version after the ROM??

Help please - where is the new power button setting?
Google search says - The powerbutton setting is in Settings -> Security -> Powerbutton checked instant lock / unchecked delayed lock
But, I don't see it anywhere, and I've explored all the Settings menus.
Thanks

SithDagger said:
Is the included bootloader unlocked? Would rather not unlock the bootloader again.
Click to expand...
Click to collapse
Your bootloader remains unlocked. OP updated.
ChadH42 said:
What about gapps? do we flash the Google version after the ROM??
Click to expand...
Click to collapse
It's a stock system image; it includes gapps. OP updated.
willysp said:
Help please - where is the new power button setting?
Click to expand...
Click to collapse
Settings | Security | (Screen Security) Power button instantly locks
The option appears only if you have enabled Screen lock with Pattern, PIN, or Password. It does not appear if you have Screen lock set to Slide or None.

stachre said:
Settings | Security | (Screen Security) Power button instantly locks
The option appears only if you have enabled Screen lock with Pattern, PIN, or Password. It does not appear if you have Screen lock set to Slide or None.
Click to expand...
Click to collapse
Got it - thanks much! I haven't setup up my Exchange accounts yet, and one has a policy that requires a password, so I'll see that option shortly.
Appreciate what you've done for us......

Thanks so much for this, working great and fine with tiamat oc kernal.

Is CIFS working on this ROM ?

Guys I am having a problem updating, I have the file on my sd card then I boot into Clockwork recovery v3.2.0.0.
then -
-- Wiping cache...
Formatting /cache...
E:unkown volume for path [/sd-ext]
Dalvick Cache wiped.
--Install from sdcard...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Insatllation aborted.
Any help appreciated.

REVHE4D said:
Guys I am having a problem updating, I have the file on my sd card then I boot into Clockwork recovery v3.2.0.0.
then -
-- Wiping cache...
Formatting /cache...
E:unkown volume for path [/sd-ext]
Dalvick Cache wiped.
--Install from sdcard...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Insatllation aborted.
Any help appreciated.
Click to expand...
Click to collapse
Sounds like you are not fully following the instructions in section 6 of the first post. e.g. unless you intentionally renamed the download to "update.zip", that file will not exist. Actually sounds like you are not using the right set of CWM menu options. Please follow the following instructions (copied from section 6) to the letter!!
Also, when you say SD card, it's the external SD card, right?
6. Perform update
a.Select "install zip from sdcard"
b.Select "choose zip from sdcard"
c.Select the modded Android 4.0.4 update package [the long file name that you downloaded]
d.Select "Yes - Install <filename>"

Excellent!
Installed this directly over the last one, following the instructions, no problems to report. Did not wipe data, only cache and dalvik. Running excellently. Have not installed an OC kernel yet, I might not until an updated one comes out.
Thanks!

[Q] problems with flashing ARHD, what's going wrong?

first time posting here, and it's my first time trying to root my phone.
i used the toolkit, and that went without any problems. the phone was rooted and unlocked, and I downloaded CWM.
After I dl'ed CWM, I downloaded the ROM Android Revolution HD. There were two files I downloaded, the actual rom itself, and the firmware that comes alongside with it. They are both zip files, and I placed them both into my phone's storage.
I booted CWM, and chose to flash the actual ROM first. That worked fine, and I thought I should flash the firmware as well. Some error came up, and it said it was aborted. No big deal, so I reboot, and it shows the screen of the phone trying to boot for at least 30 minutes.
I restart my phone, and then I flash the ROM again. Tried it again, and I'm going to leave it attempting to boot into the ROM over night.
If I wake up with this problem still, what is a method to work around this?

okay it seems that i can not restore my phone back to the factory settings, and I can't connect to a mobile network.
the phone does now boot into android revolution HD, but I just need to figure out why I can't get on a mobile network

Welcome kyro- okay usually ARHD has 2 files and one is the ROM itself and the other may be the Superwipe file, they are both .zip files but perhaps you are confusing the Superwipe file with a firmware file (I am going from memory here so bear with me)
If this is the case go into CWM again and flash the Superwipe FIRST then flash the Rom file.
I am hoping it's something simple like this.
Just a suggestion
LL13-

i wish it was that simple, but i seem to have messed my firmware up in some way. everything else works fine, except for the radio. Baseband version is unknown at the moment, after wiping data cache system battery and using the super wipe as well.
from the website, here are the three links to download from
Firmware package
Flash it in recovery by selecting "apply update.zip from /sdcard"
Firmware package contains newest radio and bootloader for 4.0.x ROMs
Android Revolution HD 4.0.0
MD5 Checksum: 8C5E76C0665E088F721780BF1391C040
Direct link to 6 fast server that will randomly use one of our sources ---
Thanks to Mavy170, Whiskey103, MarcoHD, Pili21181, Lizard & Denngie ---
Super Wipe Lite
This script will erase and format your system and cache partition using EXT4 file-system
It will also wipe /data partition, but /data/media (virtual SD card) will be untouched
Click to expand...
Click to collapse
when i flash it in recovery mode, this is the error
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
so i can't connect to a mobile network until this is properly installed i'm assuming.

[UPDATE][JB]Stock Android 4.1.2 JZO54K, Root, via CWM Recovery (US Wi-Fi MZ604)

[size=+1]BEFORE YOU BEGIN[/size]
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!
[size=+1]SUMMARY[/size]
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)
[size=+1]PREPARATION[/size]
Download the modded Xoom Wi-Fi Android 4.1.2 JZO54K update package
update_US-Xoom-WiFi-4.1.2-JZO54K_stachre_v01.zip
MD5: d9567c4d691b7ef0ae121c9dcee12585​
Ensure you have flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]
Note: there are more current recovery options available which are likely compatible; however, these instructions haven't yet been updated accordingly.​
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
[size=+1]PROCEDURE[/size]
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 "advanced"
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"
Select "Backup"
Be patient
"Backup complete!" will indicate that the update is completed.
Perform update
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!
[size=+1]POST-UPDATE NOTES[/size]
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.
[size=+1]CHANGELOG[/size]
v01: First release, JZO54K; includes root, Superuser.apk, su

[size=+1]UPDATE PACKAGE DETAILS (v01)[/size]
BOOTLOADER: flashed with stock 4.1.2 JZO54K 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.1.2 JZO54K boot image with stock kernel
Kernel: flashed with stock 4.1.2 JZO54K kernel
2.6.39.4-g4e32b94 [email protected] ) #1 SMP PREEMPT Mon Sep 10 14:01:08 PDT 2012
Includes no extras (overclocking, etc.) from custom kernels
default.prop: modded JZO54K 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.1.2 JZO54K system image
build.prop: stock 4.1.2 JZO54K build.prop
Code:
ro.build.fingerprint=motorola/tervigon/wingray:4.1.2/JZO54K/485486:user/release-keys
ro.build.description=tervigon-user 4.1.2 JZO54K 485486 release-keys
REMOVED: Stock recovery install script, patch
ADDED: 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)
USERDATA: Launcher favorites updated with new Google Play Store intent (included in stock 4.1.1 JRO03H update from Google)
/data/data/com.android.launcher/databases/launcher.db: updated with new Google Play Store intent.

[size=+1]STOCK ROOTED UPDATE PACKAGE BUILD PROCEDURE[/size]
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)
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.
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.
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.
Download stock images and previous OTA (Over The Air) update packages
3.0.1 HWI69 Images: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
3.1 HMJ37 OTA: http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
3.2 HTJ85B OTA: http://android.clients.google.com/p...igned-tervigon-HTJ85B-from-HMJ37.db223b6e.zip
3.2.1 HTK55D OTA: http://android.clients.google.com/p...gned-tervigon-HTK55D-from-HTJ85B.73617300.zip
3.2.1 HTK75D OTA: http://android.clients.google.com/p...gned-tervigon-HTK75D-from-HTK55D.01cd4f05.zip
4.0.3 IML77 OTA: http://android.clients.google.com/p...igned-tervigon-IML77-from-HTK75D.71a21bfe.zip
4.0.4 IMM76 OTA: http://android.clients.google.com/p...signed-tervigon-IMM76-from-IML77.0d062b3b.zip
4.1.1 JRO03H OTA: http://android.clients.google.com/p...igned-tervigon-JRO03H-from-IMM76.f85d815e.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.
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 JZO54K update package's filename is 75baa1719d30.signed-tervigon-JZO54K-from-JRO03H.75baa171.zip, which yields the following URL:
4.1.2 JZO54K OTA: http://android.clients.google.com/p...gned-tervigon-JZO54K-from-JRO03H.75baa171.zip​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:
Code:
adb devices
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:
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.
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:
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).
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.
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.
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.
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=/storage/sdcard1/system-root.img
exit
Once back to the local prompt, pull the image to the working directory:
Code:
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.

Wow! Super fast, thanks so much for sharing this
Sent from my ZTE-BLADE using Tapatalk 2

Great Work, As usual.:good:
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.
Thanks

im installing on my stringray right now!
[updated] this installed perfectly on my stingray after i used RSD lite to sbf back to ICS, re-rooted, and flashed through CWM recovery! it's running really great

i cant get pass the boot animation using TWRP to flash

ahmed007 said:
i cant get pass the boot animation using TWRP to flash
Click to expand...
Click to collapse
I wouldn't advise using twrp to install updates. It known to have issues.. Best to use cwm standard or touch

Thanks for update,
Reporting Titanium backup could not aquired root acces
Updated: problem solve after clearing cache

any suggestion on how to backup my current rooted 4.1.1? Mainly just apps - almost 100 apps and games
agh I didn't know rooted device will cause this much grief to update to 4.1.2

Thanks , works like a charm as always
Sent from my Xoom using Tapatalk 2

Thanks!
I managed to use your build to get to 4.1.2 successfully from my 4.1.1 rooted xoom. I have a couple of questions :
- In what state does the bootloader end up in (locked or unlocked) ? is there a way to check for status on the xoom ?
- can an unlocked bootloader receive OTA updates ? does one only need to reflash stock recovery prior to attempting the OTA or do you also need to unroot ?
It is as you said needed to use that specific recovery image, the latest clockwork recovery did not want to mound to sdcard for some reason....
I also updated the su and Superuser.apk to version 3.2. in your build it's version 3.1.3. don't think it matters much but i had the 3.2 versions before going from 4.1.1 to 4.1.2 so i decided to keep them.
Thanks for the guide,
Romain.

for stock you mean it's a motorola rom?

Hi all
I was on jellybean 4.1.1 without root, then I rooted via recovery. Now I'm on 4.1.1 with root,
I have just received a notification about the 4.1.2 update. Do I need to Install that before doing this or just install this update ?
Will it wipe anything ?
I'm a little confused, any help would be appreciated
Thanks in advance.
Sent from my Xoom using Tapatalk 2

ifti_a said:
Hi all
I was on jellybean 4.1.1 without root, then I rooted via recovery. Now I'm on 4.1.1 with root,
I have just received a notification about the 4.1.2 update. Do I need to Install that before doing this or just install this update ?
Will it wipe anything ?
I'm a little confused, any help would be appreciated
Thanks in advance.
Click to expand...
Click to collapse
Hey, if you update OTA from your notification then you will lose root. This ROM should be identical with the additions mentioned in the OP. I would go this route, however there are many ways to get the same result so as always its up to you.
And yes you can flash directly to this version from 4.1.1.
-----> Be sure to nandroid and no worries eh

Worked perfectly for me, no issues at all, just I prefer super such instead of supersu.....
Still great
thank you
Sent from my Xoom using Tapatalk 2

Just a feedback:
I'm from Brazil and just installed this on mine. Works flawlessly!
And I really hope this solves my hibernation problem that I was having with CM10.
Thanks!

got issue during update of 4.1.2
Hello,
I have xoom wifi usa and had rooted with previous version
this time during update - i accidently format system and then try to select from sd card and i got error that build/prop file not found and installation aborted
<<<<<<<<<<<<<<<<<<
file_getprop:failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update_US-Xoom-Wifi-4.1.2-Jz054....zip
(Status 7)
Installation aborted
>>>>>>>>>>>>>>>>>>>
i tried to restore option frm recovery and aft restart it just stuck to logo.
i tried agian to recovery and got same error.
any input will be great.

Thanks, flashed over RomTeam EOS 3 (stable release) - loop on ICS boot - wip data needed.

Mr stachre
Thanks again and again.
I've been using your work since ice cream sandwich.
I have now the latest offering for my xoom (on the very day my xoom was notifying me of the new update) i'm very happy
Cu

[Q] Refuses to let me return to stock ROM

My Kindle Fire has bad hardware, so I need to return it. Currently has TWRP 2.5.0.0 installed, and had CM until I wiped it.
I downloaded the stock software and have been following this thread's instructions. However, whenever I try to install the stock ROM I get this:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
In doing further research, it may mean I need to downgrade TWRP - some people have had trouble with versions newer than 2.3.3.0. And I just can't figure out how to do that successfully. I download the img file, follow these instructions, but when I put in "su" it says
su: not found
I tried connecting the Kindle Updater but the drivers don't seem to recognize it when I've got a ROM installed and booted up (though USB storage works when enabled), and while it DOES seem to see it and proceed when I'm booted into TWRP recovery, it doesn't actually do anything and just sits on updating partition information or something.
I'm VERY f'n frustrated. Could someone please do me a favor and hold my hand through this? I just can't get the damn thing to revert to stock.

QFT said:
My Kindle Fire has bad hardware, so I need to return it. Currently has TWRP 2.5.0.0 installed, and had CM until I wiped it.
I downloaded the stock software and have been following this thread's instructions. However, whenever I try to install the stock ROM I get this:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
In doing further research, it may mean I need to downgrade TWRP - some people have had trouble with versions newer than 2.3.3.0. And I just can't figure out how to do that successfully. I download the img file, follow these instructions, but when I put in "su" it says
su: not found
I tried connecting the Kindle Updater but the drivers don't seem to recognize it when I've got a ROM installed and booted up (though USB storage works when enabled), and while it DOES seem to see it and proceed when I'm booted into TWRP recovery, it doesn't actually do anything and just sits on updating partition information or something.
I'm VERY f'n frustrated. Could someone please do me a favor and hold my hand through this? I just can't get the damn thing to revert to stock.
Click to expand...
Click to collapse
Well if you can still access USB storage in TWRP, you can download a .zip file for the TWRP version you want and flash it in recovery. Ichigo has made a number of TWRP versions into .zip files for easy flashing.

Guitarman said:
Well if you can still access USB storage in TWRP, you can download a .zip file for the TWRP version you want and flash it in recovery. Ichigo has made a number of TWRP versions into .zip files for easy flashing.
Click to expand...
Click to collapse
OK, downloaded a zip for a 2.3.3.0 build... booted into TWRP, then ran Install with the ZIP. I get:
E:Error executing updater binary in zip '/sdcard/twrp-2.3.3.0.test5.p500.zip'
Error flashing zip '/sdcard/twrp-2.3.3.0.test5.p500.zip'
Any ideas? Am I doing something wrong?

What exactely do you mean by "bad hardware"? It's also possible that your downloaded update.zip file has been corrupted somehow.

Guitarman said:
What exactely do you mean by "bad hardware"?
Click to expand...
Click to collapse
It shuts the screen off and won't come back on until a forced reboot while plugged in is performed. It's an issue multiple owners report; Amazon typically replaces them for new owners (which I'm not)

QFT said:
It shuts the screen off and won't come back on until a forced reboot while plugged in is performed. It's an issue multiple owners report; Amazon typically replaces them for new owners (which I'm not)
Click to expand...
Click to collapse
Did it ever do that on the stock software?

Guitarman said:
Did it ever do that on the stock software?
Click to expand...
Click to collapse
I rooted it pretty soon after getting it, but yeah I think I did notice that happened once.

I had the same issue and re installed COTR and it worked