[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
Related
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7
Thanks Quarx, Epsylon3 and maniacc103 for all your hard work in CM7.
** Always start the procedures with 80% - full charge (don't worry if your battery die during the process, you can still go mcgyver =)
** Make a backup of your apk's, There's a lot of programs to do that (File Explorer, AndroZip, AppMonster, etc.). If you want to backup your configurations too, use Titanium Backup.
** If you have any problem, don't blame CyanogenMod Team, Quarx, Epsylon3, the FAQ or whatever. This ROM works, if it's not working for you, it's mostly because you used wrong versions or are doing something wrong. For real bugs, use github **
ALWAYS USE THE RECOMMENDED VERSIONS
ESSENTIAL DOWNLOAD LINKS:
- RSD Lite and Motorola Drivers
- 3.4.2-179-2 CEE DEBLUR
- SuperOneClick 2.1
- http://www.defy-cm.net/tools/SndInitDefy_2.0.apk]Defy 2ndinit 2.0
- CyanogenMod 7.1
- Google Apps
1) What SBF version should I use when flashing CM7.1?
2) How can I install CM7.1?
3) How to update from/to nightly's?
4) My market is not downloading/installing any program. What to do?
5) Flashed CM7.1 (or any other ROM) now i'm stuck at Motorola or CyanogenMod logo. What I have to do?
6) Can I restore my phone to send it to warranty after flashing CM7.1?
7) How to install CM7.1 and keep downgrade-ability? (Froyo or Eclair)
8) Can't connect to my wireless network.
9) I love this ROM, how can I help Quarx and Epsylon?
10) How can I install Defy 2nd Init?
12) Gmail (or any other software) isn't available on market. How can I install it?
13) How can I make GPS work better (be more fast and precise)?
14) How can I install swype in CM7.1?
15) How to overclock/undervolt in CM7.1?
16) My GoogleMaps (or other application that uses OpenGL) is freezing/irresponsive. What can I do?
1) What SBF version should I use when flashing CM7.1?
- You can use whatever Froyo (2.2.x) you want. I'm actually using CEE 3.4.2-179-2 as a base, but you can use SEA or any other.
2) How can I install CM7.1?
- Copy update-cm-7.1.0-11-Defy-signed.zip and gapps-gb-20110828-signed.zip to your SD Card
- Enable USB Debugging
- Root via SuperOneClick
- Reboot
- Install 2ndInit Recovey, go to the app and click "Install 2ndInit Recovery" (use the latest version) button
- Disable USB Debugging
- Reboot, and in Bootmenu select Recovery -> [Custom Recovery] or [Latest Recovery]
- Select "wipe cache partition" then "wipe data/factory reset"
- Select "install zip from sdcard", "choose zip from sdcard", then select "update-cm-7.1.0-11-Defy-signed.zip"
- Select "choose zip from sdcard", then select "gapps-gb-20110828-signed.zip"
** You can install any other patches that you have now, like Swype or GPS Fix **
- Select "+++++Go Back++++++" then "reboot your system now"
** Sometimes, during the first boot after installation, the bootanimation doesn't stop. If you dont see anymore a led activity, remove your battery and reboot
3) How to update from/to nightly's?
- Copy update-cm-7.1.0-11-Defy-signed.zip (or the nightly), gapps-gb-20110828-signed.zip to your SD Card
- Reboot and go to Bootmenu (wait for led turn blue then press Volume Down). Enter Recovery -> Custom Recovery
- Select "wipe cache" then go to "advanced", select "wipe dalvik cache"
** If you have 100% battery, algo in advanced select "wipe battery stats" to calibrate your battery **
- Go back, select "install zip from sdcard", "choose zip from sdcard", then select "update-cm-7.1.0-11-Defy-signed.zip" (or the nightly)
- Select "choose zip from sdcard", then select "gapps-gb-20110828-signed.zip"
4) My market is not downloading/installing any program. What to do?
- Just log in Google Talk
5) Flashed CM7.1 (or any other ROM) now i'm stuck at Motorola or Cyanogen logo. What I have to do?
- Go to Custom Recovery then clear cache. If the problem persists, you can try to wipe dalvik cache (in advanced) too. The next boot will take some time to build dalvik cache again. If you don't have Custom Recovery for some reason, power off your phone, press and hold Volume Down + Power to go to Stock Recovery (only to clear cache/wipe data). Use Volume Up + Volume Down to show the options at Stock Recovery.
- Some people related freeze on the first boot of CM7.1, just remove your battery ans try again.
6) Can I restore my phone to send it to warranty after flashing CM7.1?
- You can in these two situations
1 - You have a full SBF of your original ROM (for carriers that already released 2.2 is very easy to find one)
2 - You have a nandroid backup AND a fixed SBF of the version you need.
For a list of (fixed) SBF's you can check:
SBF - Service Flash - all files + fixed sbf + Bootloaders
[[sbf:defy]] And Developers
7) How to install CM7.1 and keep downgrade-ability? (Froyo or Eclair)
If you don't flash the full SBF, your downgrade-ablility is fine.
Here's the safe steps to install CM7.1 and keep your downgrade-ability:
- Copy nandroid backup of 3.4.2-179-2 CEE to your sdcard. Uncompress it in the folder clockworkmod/backup/ of your sdcard, create this if needed.
- Enable USB Debug
- Root via SuperOneClick
- Disable USB Debugging
- Install Defy 2nd Init
- Reboot to enter Bootmenu, then go to Custom Recovery
- In Custom Recovery, go to "backup and restore", then "Backup". This will take some time, your backup will be at /clockworkmod/backup. Copy it to a safe place.
- Still in recovery, go to "backup and restore", "restore", and select the nandroid backup of 3.4.2-179-2 CEE (not your backup!)
If you have MD5 mismatch error, try to rename the folder of the nandroid to something simple without spaces, like "nand"
- Reboot your system and immediately press and hold Volume Up to enter Bootloader Mode (if you couldn't enter, remove the battery, wait 10s, put it again with Power and Volume Up pressed)
- Flash Fixed SBF of 3.4.2-179-2 CEE via RSD Lite
Now go to question 2 and do all the process to install CM7.1.
If you want to go back to your original ROM
- Disable USB Debuging
- Copy your nandroid backup to your SD Card, put it in /sdcard/clockworkmod/backup (must be a folder with simple name inside backup)
- Reboot phone in Bootmenu (Volume Down when the blue led lights at Motorola logo) then go to Custom Recovery
- Wipe data/factory reset, wipe cache and wipe dalvik cache (in advanced)
- Choose "backup and restore", "restore", and select your eclair nandroid backup. If your backup doesn't show in this screen, is most likely you placed it in the wrong folder.
- Reboot your system and immediately press and hold Volume Up to enter Bootloader Mode.
6. Flash the Fixed SBF of your original ROM. For a list of (fixed) SBF's you can check:
SBF - Service Flash - all files + fixed sbf + Bootloaders
[[sbf:defy]] And Developers
8) Can't connect to my wireless network.
- Tap and hold the SSID of the network and select Forget. Try to configure the SSID again.
9) I love this ROM, how can I help Quarx and Epsylon?
Donate to Quarx
Moneybookers: [email protected]
WebMoney: USD:Z319203344726
Yandex money: 4100188263979
Click to expand...
Click to collapse
And donate to Epsylon3 (tpruvot)
PayPal: [email protected]
http://forum.xda-developers.com/donatetome.php?u=803131
Click to expand...
Click to collapse
10) How can I install Defy 2nd Init?
http://www.defy-cm.net/tools/SndInitDefy_2.0.apk
11) Gmail (or any other software) isn't available on market. How can I install it?
- Download MarketEnabler via Market
- Select US Provider (T-Mobile)
- Open Market and search for Gmail or any other software, it will be available now
- Don't forget to select your correct Baseband in Applications => Defy Baseband Switcher
12) How can I make GPS work better?
- Make a backup of your /etc/gps.conf (use a file manager to rename or copy to another place)
- Visit this thread
- Click in the link "XDA Members Click Here" at the final of the post, and search for the correct .zip for your country
- Copy the .zip to your SD Card and reboot in Bootmenu, then flash the zip via Custom Recovery
13) How can I install swype in CM7.1?
- Go to http://beta.swype.com, (create a account if needed), download the Swype Beta and install it
- Open Applications -> Swype Installer and follow the instructions on the screen
14) How to overclock/undervolt in CM7.1?
CM7.1 already comes with 1000/600/300 clock, but if you want to modify these settings or undervolt:
- Reboot and enter Bootmenu
- System -> Overclock
- Set your parameters and select [save] before exit.
Remember that if you experience freezes, reboots and other problems, OC/UV can be the cause. Try to disable in this situation.
Also, DON'T INSTALL SETVSEL!
15) My GoogleMaps (or other application that uses OpenGL) is freezing/irresponsive. What can I do?
Open terminal or adb shell and type these commands:
Code:
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# echo sysctl -w vm.min_free_kbytes=4096 >> /system/etc/install-recovery.sh
# chmod 744 /system/etc/install-recovery.sh
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
I'm a newbie, so any help to complete this FAQ will be welcome =)
And sorry for my english =S
Thanks to everyone that helped me in this FAQ, sending suggestions and fixes.
Thx for the post.
this is awesome. I should give u credit.
Sent from my MB525 using XDA App
nice... quarx thread should be more focus about bug reporting..
The kernl of CM7 in Quarx's is Nordic , mean 3.4.2-177.5 not 3.4.3
3) How to update from Beta 4.0/4.1?
- Copy Fix.zip, CM7 and Google Apps to your SD Card.
- Reboot your Defy then go to Bootmenu (blue light at Motorola logo) then Custom Recovery
- There's no need to wipe data/cache!
- Select "install zip from sdcard", "choose zip from sdcard", then select "Fix.zip"
- Select "choose zip from sdcard", then select "update-beta5-cm7.1.0-03.05.11-Defy.zip"
- Select "choose zip from sdcard", then select "gapps gb 20110503 signed.zip"
- Select "+++++Go Back++++++" then "reboot your system now"
Click to expand...
Click to collapse
I think, after flashhing fix.zip need a reboot:
Quarx said:
Update to Beta5:
Before update you need install fix.zip and after reboot you can flash new version.
If you do not, then you get an error when installing the new version. And you will need to reflash with RSD.
Click to expand...
Click to collapse
Yes please change that. After flashing Fix.zip a reboot is absolutely necessary.
i created tutorial to install CM7 and keep the downgrade-ability to eclair.
in here: http://forum.xda-developers.com/showpost.php?p=13527057&postcount=3
maybe you can create that tutorial too in this thread.
I think we should better start a wiki that way everybody can contribute
Can we create pages on the XDA Wiki? Dunno how to but I think that's easier for everyone!
we have a wiki here:
http://forum.xda-developers.com/wiki/index.php?title=Motorola_Defy
I once made a comparison between 3.4.3_11 and 3.4.2_177, hope this can answer someone's question about the sbf.
http://forum.xda-developers.com/showpost.php?p=13244959&postcount=1806
Solution for (most of) not-connecting wifi
http://forum.xda-developers.com/showpost.php?p=13435452&postcount=2355
I'm on the US official Froyo() currently, and since the aGPS has been fixed, I'm planning to go for the CM7 made by Quarx.
Before I do, I've got a little concern. If I follow the normal procedures to flash CM7, am I able to go back to the Official Froyo I currently use? I ask because there is no SBF for this official US Froyo, there is only leaked version and the OTA.
you tuto is perfect , but the gapps has a new version , try update
boa mlk exelente topicuuu mas tu viu q o gapps ta velho saiu uma nova esse mes com o app do 2.3.4 se quiser o link pede
wyxpark said:
I'm on the US official Froyo() currently, and since the aGPS has been fixed, I'm planning to go for the CM7 made by Quarx.
Before I do, I've got a little concern. If I follow the normal procedures to flash CM7, am I able to go back to the Official Froyo I currently use? I ask because there is no SBF for this official US Froyo, there is only leaked version and the OTA.
Click to expand...
Click to collapse
Item 7 of the FAQ. You will only need a fixed SBF version that matches the number of your original ROM, there`s no need to be the same ROM. These parameters will be overrided by the parameters in your nandroid backup (version and name of your original Froyo).
FAQ Updated to Beta 5.1 (thanks Quarx!) and 2nd Init Recovery Installer 1.4 (thanks pedrodh!)
is defy bootloader unlocked?
why it can flash cm7
ygvuhb said:
is defy bootloader unlocked?
why it can flash cm7
Click to expand...
Click to collapse
using 2nd Init Recovery, so nothing to do with locked bootloader
@antony.ps : nice tutorial
One question: How do I install Custom Recovery / Clockworkmod?!!
I am trying to do step 7 but I am stuck I am unable to install Bootmenu+Clockworkmod that Quarx provided. If I use Root Explorer to install, it will not install as after reboot I don't see the System Recovery app; I have tried installing via emulator as well but same result. (I dunno which folder to extract the files to. I have even copied to the root folder and the install.sh seemed to execute but after restart it dint work and weirdly the copied folder also vanished!)
I, however, managed to take a nandroid backup of my system using DEFY SD-Recovery. However, if I try to restore the "nandroid backup of 3.4.2-177" I get md5 mismatch and the process aborts NOTE: I cannot move folders if I use this app; so instead of clockworkmod/backup/ I have to use goapkrev/backup
I am unable to proceed unless I perform the restore. Can someone help me with step-by-step solution for installing Clockworkmod Recovery, and also 2nd Init / Bootmenu as that is needed for the next step? Thanks!
candra_aja said:
using 2nd Init Recovery, so nothing to do with locked bootloader
@antony.ps : nice tutorial
Click to expand...
Click to collapse
Since we're in the FAQ-topic here can you or someone else give a little explanation what 2nd Init actually does? I'm guessing it sort of circumvents some limitations by the bootloader.
abhi.eternal said:
However, if I try to restore the "nandroid backup of 3.4.2-177" I get md5 mismatch and the process aborts
Click to expand...
Click to collapse
This has been mentioned already about 1000 times by now on this forum but the simple solution is to remove all the spaces from the folder name. Easiest is to use short simple folder names such as "nand" or something else that makes sense to you.
AgentSmith said:
Since we're in the FAQ-topic here can you or someone else give a little explanation what 2nd Init actually does? I'm guessing it sort of circumvents some limitations by the bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12837303&postcount=1
candra_aja said:
using 2nd Init Recovery, so nothing to do with locked bootloader
@antony.ps : nice tutorial
Click to expand...
Click to collapse
Can all moto locked bootloader phone use 2nd recovery ?
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]
You are currently running Android 3.1 (stock 3.1 images here, thanks, bwcorvus)
You've downloaded the modded Xoom Wi-Fi Android 3.2 update v05 (thanks to kurt5510 for the original OTA, thanks to solarnz for the rooted stock boot.img)
You've flashed ClockworkMod Recovery (thanks, solarnz, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
[size=+1]PROCEDURE[/size]
Rename the modded Android 3.2 Update file to update.zip
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
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"
Enjoy your rooted Xoom Wi-Fi, running on Android 3.2!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: [KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana" [Update: 07/14]
[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
Excellent work! Guide stuck for the time being.
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
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!)
LynnL said:
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?
Click to expand...
Click to collapse
As long as the file is there, you're good to go.
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."
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
By the way, i have a UK Xoom but i went to 3.1 via stock US FW.
eliteone said:
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
Click to expand...
Click to collapse
I'm running stock with a custom kernel and getting the same error.
you need to be running stock kernel i believe
eliteone said:
you need to be running stock kernel i believe
Click to expand...
Click to collapse
At this time, yes. solarnz made a rooted stock boot.img which i'm working on including in an update.zip.
xMemphisx said:
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."
Click to expand...
Click to collapse
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.
I'm getting some corby apk error when trying to run the update. Using stock 3.1 but rooted.
Xoom wi-fi US version.
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
will this method wipe any of my data ?
Were do i find the stock 3.1 Kernel?
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
Sk8er Boi said:
will this method wipe any of my data ?
Click to expand...
Click to collapse
It currently flashes over your boot partition and updates your system partition. User data is not affected.
jzun223 said:
Were do i find the stock 3.1 Kernel?
Click to expand...
Click to collapse
[IMAGES] HMJ37 (USA WiFi 3.1)
Sk8er Boi said:
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
Click to expand...
Click to collapse
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?
stachre said:
It currently flashes over your boot partition and updates your system partition. User data is not affected.
[IMAGES] HMJ37 (USA WiFi 3.1)
What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.
Click to expand...
Click to collapse
this is also happening to me my data is
build# hmj37
kernel 2.6.36.3-gc2bee64 [email protected]#1
version3.1
v03 posted, see OP.
[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 ImagesThis 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.zipNote 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.zipSee 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!
[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 ImagesThis 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.zipNote 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.zipSee 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