Database Info

[RECOVERY] [Vodafone Smart / Huawei U8160] Unofficial ClockworkMod Recovery

Edit: February 2012: please disregard ALL information below this red text. ROM Manager now supports the Huawei U8160, and will flash the official recovery build from the app. See the Getting Started with ROM Manager & ClockworkMod section in this post.
ClockworkMod Recovery for Vodafone Smart (Huawei U8160)
Current release - v0.1 - 12 September 2011 [CWM Ver. 4.0.1.5]
What is ClockworkMod Recovery? From AddictiveTips:
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
Click to expand...
Click to collapse
Installation - Fastboot Method:
Use this method if you have never installed a build of ClockworkMod before.
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Download the latest zip release of ClockworkMod using the link(s) below.
Open the ClockworkMod .zip file and extract the recovery.img file to the same folder as the fastboot / fastboot.exe binary.
Reboot (or turn your phone one) whilst holding the power and volume down keys. Your phone will now be in "fastboot" mode.
Open a terminal or command prompt, and run the following commands:
Note: these are example instructions for a Windows user who has extracted the fastboot.exe and recovery.img to C:\VodafoneSmart. Adjust the folder path to wherever you extracted these files.
Code:
cd C:\VodafoneSmart
fastboot flash recovery recovery.img
fastboot reboot
Installation - ClockworkMod Method (zip):
Use this method if you already have ClockworkMod installed, and you wish to update the version that already exists on your phone.
Download the latest zip release using the link(s) below.
Transfer the .zip file to your SD card. Do not extract the .zip file - only copy it.
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes. Reboot and enjoy!
Usage:
To access ClockworkMod recovery, any one of the follow methods will work:
If you are running a build of CyanogenMod, choose the Recovery option from the reboot menu;
Run "adb shell reboot recovery" on any rooted ROM;
Reboot your device whilst holding the power and volume up keys.[/li]
Once you've entered ClockworkMod Recovery, you will be presented with several options (some familiar, some not). I won't try to explain all of the options, as there are better guides on the internet (example: the AddictiveTips site above). However, these are the ones you should really know about:
Wipe data/factory reset - same as before
Wipe cache partition - same as before
Install zip from sdcard -> choose zip from sdcard - this is the new method you will be using to flash ROMs and update packages
Backup & restore - this menu lets you perform a full backup or restore of your boot, /cache, /data/ & app2sd partition (which is compatible with mad2sd)
Mounts & storage -> mount USB storage - this lets you enable UMS mode to copy update packages (if you forgot to transfer before rebooting into recovery)
Advanced -> partition SD card - this lets you easily partition your SD card for use with mad2sd or any third-party app2sd solutions. It lets you select the size for the EXT4 partition as well as swap. MAKE SURE TO BACKUP ALL DATA ON YOUR CARD BEFORE USING THIS OPTION.
Changelog:
[CWM Ver. 4.0.1.5] v0.1 zip - 12 September 2011
First release.

Hi, I've been trying this guide and am having trouble with both methods.
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
ClockworkMod Method
I installed the CWM I got off the Android Market, and then tried to reboot into recovery mode (both by rebooting through CWM and by pressing Volume+Up & Power). I just end up waiting at the hourglass screen like when it's in fastboot mode.
Any idea what I'm doing wrong?

for fastboot try without battery inside (only usb) works for me
if fastboot wont work try methode 3. http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
with extractet recovery.img from zip (http://forum.xda-developers.com/showthread.php?p=17496869)

jajajim said:
for fast boot try without battery inside (only usb) works for me
Click to expand...
Click to collapse
Tried that too; didn't work.

Thanks, worked for me with fastboot on u8180

zodac01 said:
Fastboot Method
I get into fastboot mode (where it's just at the hourglass screen), and type in "fastboot flash recovery recovery.img". The command prompt just says "Waiting for device", and never updates.
Click to expand...
Click to collapse
That happens to me too... I also noticed that in device manager is missing driver for Android 1.0? I don't know what to do next. Someone knows? Thanks
EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).

EDIT: It works ... download Pulse_Drivers_xp_w7_w764.zip from dc-unlocker (sry can't post link).
Click to expand...
Click to collapse
for linux users??

just a note, the U8160 has a different USB hardware ID when in fastboot mode, and so inside 70.android.rules you need to add "12d1" and "18d1"
18d1 is the fastboot USB id and 12d1 is the adb USB id
This is for linux btw.

i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...

thanks, needed this!

renegade_82 said:
i've two questions for subpsyke:
it's planned update to cwm recovery 5?
Why don't knowledge Rom Manager cwm recovery in your cyano release for U8160?
p.s
sorry for my bad english, i'm italian's users ...
Click to expand...
Click to collapse
Yea i got this problem too, in ROM manager, this recovery isnt detected, any ideas on how to get it?
EDIT: I flashed the IDEOS recovery through rom manager then flashed back this recovery, and now it works like it should.

EDIT: done, thanks a lot
for pulse driver, turn on phone, then press power + volume down, then plug usb, PC will search for a driver
fastboot is just: power button + volume down (and then it sticks on logo or hourglass) then open command prompt on pc
pulse driver:
http://www.mediafire.com/?l9zoonl8kygcejm

Hi there
Download the Android SDK for your operating system [Windows users are recommended to download the .zip version].
Extract the fastboot / fastboot.exe file from the tools folder of the Android SDK zip file to a folder on your computer.
Click to expand...
Click to collapse
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Any suggestions?
Thanks in advance

jpcoke said:
I'm a windows user and i've downloaded the Sdk zip and there's no fastboot.exe on any of the folders... :|
Click to expand...
Click to collapse
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it

fastboot and recovery
http://www.wuala.com/freegroup/cyanogen/VodafoneSmart.zip/

u8160 cwm
iam havving problems around here
i need more instruction , i have the folder with recovery and fastbot ,but how to put tham on the phone ? i have rooted my device sucesfully iam stuck rebooting on recovery mode , i cant reboot as you show us , or enter in fastboot , please help me do it

aripelx said:
Download android-sdk-windows-1.6_r1
The latest sdk doesn't have it
Click to expand...
Click to collapse
cant seem to find this version of the sdk to download, anyone got a link?
thanks

I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?

mcpossity said:
I have a branded Vodafone Smart (U8160) and it stucks everytime at the hourglass screen. It won't get into recovery mode.
How do I fix this?
Edit: I haven't rooted it yet. Have I to do it before I could install CMW?
Click to expand...
Click to collapse
for cwm it's power button+volume UP
fastboot power button+volume DOWN
it's easy to root with gingerbreak v1.2
---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------
asidhowz said:
cant seem to find this version of the sdk to download, anyone got a link?
thanks
Click to expand...
Click to collapse
man, I have posted the link just up

Thanks, worked like a charm

[A511/A510] [01-07-2012] CWM Recovery - TESTING only (can cause bricks!!)

Hi all,
Well, it looks like it works now!
Touch is also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
For the non-touch version you can use Volume+ (one dot) and Volume- (two dots) works and use power to select an option.
** WARNINGS **
My device is hard-bricked due to the restore function not working correctly... be careful what you do!
Extra WARNING - do not use:
WIPE DATA/FACT. RESET
FORMAT PARTITIONS
BACKUP/RESTORE
FOTA
1. Avoid FOTA (software update from Acer, directly on device), see update here
2. I have not tested each function yet!
3. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
4. Try to not use wipe/backup/restore features - only install from zip has been tested and works
** Downloads **
EDIT FROM THE ARCHANGELULLED LINKS TO AVOID BRICKING DEVICES
** Uninstall **
Uninstall has not been tested in most cases. Please let me know whether this is sufficient and whether it works.
A510
Install the A510 Stock Recovery using the batchfile in the following download:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A510-stock-recovery.zip (4.48 MB)
A511
Try the steps in the following post:
http://forum.xda-developers.com/showpost.php?p=29101012&postcount=108
If that doesn't work (for instance because the install-recovery.sh file does not exist), try installing the files from the following post:
http://forum.xda-developers.com/showpost.php?p=29217619&postcount=111
** Credits **
Dees-Troy for the versions of the BoardConfig.mk & recovery.fstab on his github
Cyanogenmod for their CWM-recovery-build-website
Koushik Dutta for his porting CWM guide
** Install instructions **
1. Boot your device
2. If it's already unlocked, skip to step 7
3. Type following in a DOS-prompt:
Code:
adb reboot bootloader
4. Wait till device is booted and reconnected to pc (ie. drivers loaded)
5. Type following in a DOS-prompt:
Code:
fastboot oem unlock
6. Be quick (it times out) to unlock the device. Use Volume- key to highlight the unlocked lock and press the Volume+ key to activate
7. Type following in a DOS-prompt
Code:
adb reboot-bootloader
8. Wait till bootloader is loaded and reconnected to pc
9. Type following in a DOS-prompt:
Code:
fastboot flash recovery XXX.img
(replace XXX with the image file name of your choice)
Remark: step 10 to 12 can be skipped if you'll also root your device with my root-cwm-zip. That already removes the same file, so you shouldn't experience this issue
10. Reboot the device and hold to Volume- button to load the recovery
Make sure to do this - if you do not, it will automatically overwrite your recovery
11. Try to mount system. Be carefull what buttons you press. You can use power to cancel any menu and go back one menu
12. When system is mounted type the following in a DOS-prompt:
Code:
adb shell
cd /system/etc
mv install-recovery.sh install-recovery.old
13. Reboot and see whether you can still use your system. Reboot again with Volume- and see whether you can still access recovery (or use the following command)
Code:
adb reboot recovery
I will make this all much simpeler with a dos script, etc., as soon as the recovery correctly works.
** RECOVERY-A51x-tools.zip **
For quick usage I added the tools that I use to write recovery (adb, fastboot for writing the recovery to the device - batchfiles are included with each recovery download).
Next step... if you're willing... is root: http://forum.xda-developers.com/showthread.php?t=1729432
Regards,
Nika.

Great news

It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
See attached recovery for A510. I'm quite sure it works for A511 too.
Did you try to enter recovery using "adb reboot recovery" or by power off, power on with Volume- and wait for recovery? And did you put the 1.011 ROM (update.zip) into the external sdcard?
Flash recovery with:
1. Reboot into bootloader with:
Code:
adb reboot bootloader
2. Enter the next command from the folder with the recovery.img:
Code:
fastboot flash recovery recovery.img
By the way, I've managed to get into bootloader mode by using Volume- and switch the rotation lock back and forward at the same time...not sure whether there's another way (other than booting the device and rebooting into bootloader with the adb command).
Regards,
Nika.

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.

OP changed. It works now. It's not touch recovery, but using Volume+ and Volume- works and use power to select an option.
** WARNINGS **
1. I have not tested each function yet!
2. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
Believe it or not, my first version of the recovery was very close. I just had some problems due to invalid BoardConfig.mk entries which I had used from the Dees-Troy recovery source. I have now used the ones that were generated automatically when using the CWM-recovery-build-website (which generated the touch recovery but seems to have the before mentioned issues)...

nikagl said:
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.
Click to expand...
Click to collapse
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method

simoneser said:
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method
Click to expand...
Click to collapse
When you only installed the recovery as recovery you should be ok. Bricks only happen when you flash a new boot record... I've also tried TWRP's but didn't have any issues so far, other than that they didn't work.
Remember the tablet doesn't charge when USB connected (unless using the charger). In my case that's one of the reasons I had to stop yesterday
When it runs again (hopefully) try my new recovery. Get into bootloader mode with the Volume-, Poweron, screenrotation lock method and flash it with "fastboot flash recovery recovery.img". If it's locked again (which happens after flashing roms, it will then complain when you try to install the recovery) run "fastboot oem unlock", reboot with "fastboot reboot" and try again to flash the recovery.
Good luck and keep me (us) posted
Regards,
Nika.

The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
I only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead

simoneser said:
The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead
Click to expand...
Click to collapse
That's horrible also for others because it will make the choice to install this a little harder... although I honestly have not had any of your trouble, and I don't really understand what happened either
But.. definitely check on google. I have seen many successful recovery from APX-mode.
Good luck and keep us posted.
Regards,
Nika.

For others, still willing to play around with the device, here's a solution to get root:
http://forum.xda-developers.com/showthread.php?t=1729432

great job
any idea if it can fit in a510?

BENETNATH said:
great job
any idea if it can fit in a510?
Click to expand...
Click to collapse
root or cwm? I guess I can build CWM for A510 too, but you have TWRP and CWM already don't you (on other forums...)?

we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Ok... will build it as soon as I can (takes some time to setup the env). I haven't tested restore btw, need to backup some more stuff (with titanium backup) to make sure I don't loose anything
Also, make sure you have a large enough external sdcard when making backups. Remember the internal sdcard is huge and backups can cause the external to be full
One more thing, also good to know, you can always backup using DD commands:
Code:
dd if=mountpoint of=/sdcard/filename.img
And here's a list of the mountpoints in the A510/A511:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img

Well... I tried making a backup in my CWM and it says "Error while making a backup image of /data". Not sure yet why... will first make some dd backups, titanium backups, wipe device and will then start testing from scratch...

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Sorry for spamming, please provide a boot.img of your device/rom-version so I can use that kernel for building the recovery.

Touch is now also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
See first post

Problem with CWM
Great work. Only problem what I have is that my device is not recognized when entering CWM. In the device manager is just an unknown device. I have installed the drivers from the Acer support. Do I need somehting else, too?

Well, my A511 is stuck at "writing recovery".
Bootloader vICS-MR1-89805f0(UnlockMode) :
sending recovery 5268kb ...
OKAY 2,063s
writing recovery ...
FAILED status malformed 0 bytes
finished. total time 503.062s
Well its still booting without problems in unlocked bootloader, but i cant flash. It just stuck there even if i try it again and again.
A511 & NV Fastboot Driver are both recognized by my system, but can it cause an error that i run windows in a VB? Need to enable USB-Debugging to run adb.
I never had problems with my Arc before using fastboot in a VB.
EDIT: Same for the touch-CWM. It just stuck at writing recovery.
adb v1.0.29

3 doubts about flashing CWM and EOS ROM

Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.

All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2

wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...

NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you

Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted

I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2

NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2

You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.

Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.

Good luck...
Sent from my MZ601 using Tapatalk 2

Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!

Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2

wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?

Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2

wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.

NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.

Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?

I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).

Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)

Hi all.
A few days ago I entered the Xoom forum asking about how to modify an "unaltered" Spanish/European Xoom (Wifi Only, MZ604) running stock Android Honeycomb (3.2) and flash a custom ROM with Android 4.1.1 (JellyBean), so that I don't have to wait Motorola to release the updates (still in Honeycomb in Europe, while in US they're enjoying JB), and to enjoy the extras that custom ROMs offer (root, overclocking, etc).
Xda users "wesamothman" and "Cubanluke88" answered quickly to my question and this allowed me to unlock my Xoom bootloader, install TWRP Recovery and flash EOS3 ROM (JellyBean for Xoom from TEAM EOS). The results are awesome; the change from Honeycomb to Jellybean, plus the totally stable overclocking at 1.2 and even 1.4 Ghz is worth the fact that you void the Xoom warranty by doing this procedure. It's like having a brand new tablet.
As I found some problems/mistakes in the procedure I was given, I've created a new "Guide for Noobs" (based on wesamothman's) so that anybody can reproduce the same steps and convert an European Xoom (Wifi Model, MZ604) into a modern EOS3-powered Xoom.
NOTE: I initially wrote this tutorial using the EOS-RECOVERY-6.IMG as the CWM Recovery software to install in the Recovery Partition. The recommended recovery software now is TWRP so I've updated the tutorial replacing the download links and filename.img to flash. The procedure remains the same, although I really tested and executed it with eos-recovery-6, not with TWRP. Anyway, it is supposed to be flashed and work the same way than I initially described it.
NOTE THAT THIS PROCEDURE IS FOR EOS3 - (EOS NIGHTLY <= v155).
EOS4 (nightly >= v156) requires a slightly different procedure!!!
Please, remember that by unlocking the bootloader (and flashing non official software) you're voiding the device warranty and that I'm not responsible of any damage that your device can suffer. I'm just explaining how I did the unlocking+flashing to convert my SLOW XOOM in a fully working JellyBean system. Remember also that this procedure is for WIFI ONLY Xooms. 3g xooms need a different rom/procedure.
So, sumarizing, that's what we are going to do:
a.- Unlock the "bootloader" of the Motorola Xoom so that we can "install" custom software in both the "recovery" and the "data" partitions. Please notice that by unlocking the bootloader you void the device warranty.
b.- Flash TWRP software into the recovery partition, (I was flashing EOS-Recovery-v6 software initially but now is deprecated and TWRP must be used) so that we can launch this software pressing a combination of keys during power-on. This software will allow us to make full backup/restore of the device memory, and to install any ROM (EOS2, EOS3, cyanogenmod, EDGE, etc) in the system. Thanks to this recovery we are safe against problems in the O.S. (even if we break it), because we can always recover from backup or flash a new ROM (including the "stock" ROM, I mean, the ROM shipped oficially with the device) and solve the situation.
c.- Once recovery is installed, do a NANDROID backup of the NAND of our device, to have a copy of the "stock" system.
d.- From Recovery, flash the desired ROM (EOS3 in my case) and the Google Apps applications (they can't be included inside the ROM for legal reasons, so they are flashed separately) to the "data" particion.
e.- Restart and enjoy our new system (you can also made another NANDROID backup to save this "working point" for the future).
Steps a). and b). need a working computer with Linux, Windows or Mac. After doing b).- you can do everything from the Xoom itself and you don't need the computer anymore. After doing b)., you'll be able to download ROM images directly under your Xoom in the uSD card and reflash any new ROM directly rebooting the tablet into recovery-mode.
Steps a) and b) can be done from Linux, Windows and Mac. Although I have Linux in my laptop, I found that almost all the tutorials in Internet explain the procedure under Windows so I installed temporary a Windows system to do the "PC dependant" steps, because I didn't want to experiment with the "risky" actions in both steps.
So, let's start with the "PC dependant" actions, which includes steps a). and b).
I'll try to update the thread with screenshots in the future, as I didn't take photos/screenshots of the procedure, I'll check images.google.com to find something that fits the text, and add the later to the tutorial if they are really needed.
PART 1 .- HOW TO INSTALL TWRP RECOVERY:
Here we are going to unlock our Xoom and install a custom recovery software into the recovery partition. The recovery software is launched when you start your Xoom in recovery mode, and this is achieved by pushing Power, VolUP and VolDown key combinations when you power-on the tablet (we'll see how later).
So we'll replace the original "recovery" software by a custom one that allows us to flash NON OFFICIAL software to the data partition.
To do that, first we have to download all the required software in the Xoom enternal uSD card and prepare our PC system to recognize and work with the Xoom. We have to download:
Get the Motorola USB drivers for your system: http://developer.motorola.com/docstools/USB_Drivers/ . This step is only needed under Windows, so that the Windows System recognizes the Xoom and the Android SDK binaries (adb and fastboot) can send data to the tablet. Check that you're downloading the right drivers (32 or 64 bits) for your 32 or 64 bits System, and install them. If the Android SDK in your Linux system can recognize the Xoom, you're ready to use Linux also to do the following steps.
Download and Install in your PC the lastest JavaSE JDK from Oracle's website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download and install the Android SDK for your system: http://developer.android.com/sdk/index.html .
Download the EOS v155 ROM and GoogleAPPS for that version. My final choose was EOS3 ROM Wingray (Jellybean for Xoom), and installed v155 from the nightly compilations (which is the latest nightly in Android 4.1, being v156+ Android 4.2). "Nightly" means that as the software is still not "final version" (it's still in development) a new version is released almost everyday, correcting bugs or adding new features. I personally didn't found any bug in v155 but you can check the EOS3 thread in XDA to check that the latest version has no bugs reported by people in that thread.
ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ (as of date September-2012 - I recommend v141 )
GAPPS: Latest: http://teameos.org/gapps/wingray (I used http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip for v155).
EOS3 THREAD: http://forum.xda-developers.com/showthread.php?t=1764751
And the most important, download TWRP the "recovery software" that will allow you to work without the need of the PC (I was using Team Eos Recovery 6 initially, but now is deprecated and TWRP must be used):
Team Win Recovery Project 2.x, (TWRP): http://forum.xda-developers.com/showthread.php?t=1782235
You should download the IMG file (example: R.A.H.v3_TWRPv2.5.0.img). Check that the size of the downloaded file matches the size that is shown in the above link. This is the most important file because it will allow to install the recovery system and it's CRITICAL that the file is not corrupted..
Steps:
a.- Install in your PC the Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
This will download and install the packages needed so that we can access the Xoom from the PC for "flashing" data purposes; mainly "adb" and "fastboot". Adb allows us to work with the xoom started in the Android System, and fastboot allows us to work with the xoom started in fastboot mode, which is the mode we'll use to "flash" the recovery software.
b.- Enable USB debugging in the XOOM (in settings, development), so that we can use adb with the tablet.
c.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
d.- Plug the Xoom to your PC.
e.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices". You should see that the system identifies your Xoom with a long numbers+letters string. If you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device, so that the system can bind the right USB drivers we installed to that concrete device.
After a While, Windows will fix it and re-executing "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
Now, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup. Fastboot mode is a special bootmode in the xoom that allows the PC to send data to the Xoom and "write" to Recovery and Data partitions. You can also enter that mode starting the Xoom with "Power+Volume Up" pressed simultaneously.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Photo: fastboot mode, taken from google images)
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because Windows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot".
Issue the following command to unlock the Xoom (you'll void the warranty). If you don't unlock the xoom, data and recovery partitions will be "read only" and you can't send the "new software" to them.
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option. The device will ask you twice if you are sure that you want to unlock the device and void the warranty, and then it will make a "factory reset" of the O.S. .
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc. Enable again "USB debugging" and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the recovery file (the name may vary, with something like R.A.H.v3_TWRPv2.5.0.img) to the android-sdk/platform-tools/ folder with name "recovery.img" and execute:
Code:
fastboot flash recovery recovery.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery recovery.img
sending 'recovery' (XXXXX KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
Now disconnect the USB cable and enter recovery mode with:
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
And you'll start the TWRP Recovery recovery system. If you see the standard Android recovery system instead of TWRP recovery, you can repeat the above "fastboot flash recovery recovery.img". You don't have to unlock the bootloader again, just flash the recovery software and reboot again in recovery mode with "fastboot reboot" and "adb reboot recovery".
(Photo: my Xoom in EOS6 recovery mode, TWRP is different, with better controls and more features )
You can start recovery mode also manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE TWRP RECOVERY
How to enter in recovery mode:
A.- Manually:
- Turn Xoom off.
- Press Power to turn Xoom on.
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
b.- From "adb" in a PC system with Android running on the tablet connected to that PC:
Executing "adb reboot recovery"
c.- With a custom ROM, selecting "reboot" will ask you if you want a normal reboot or a recovery-reboot.
How to use recovery mode:
Use the Volume Up and Volume Down keys to move between options and Power button to select an Option:
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
Available options for a basic CWM / recovery are:
Reboot system now -> exit Recovery mode.
install zip from sdcard -> allows to install ZIPs to data partitions such as ROMs.
wipe data/factory reset -> delete all the contents in the data partition (needed before flashing a ROM)
wipe cache partition -> delete cache partition.
backup and restore -> allows doing "nandroid" backups and restore of our system (FULL MEMORY BACKUPS).
mounts and storage -> allows to mount aditional media to save/read data.
advanced -> extra options.
(Photo: Nandroid backup)
NOTE: TWRP is newer than the OLD EOS-recovery-6, the above capture and options may differ.
PART 3 .- HOW TO INSTALL EOS3 ROM:
Now we've installed recovery, so we don't need the PC anymore. We can enter in recovery mode at any moment and do backup/restores, flash new roms, flash updates, etc.
To install EOS3 ROM (or any other "full install" -not update- ROM, do):
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Install gmail, youtube, etc from Market (not included anymore in gapps).
Enjoy your new rom!
PART 4 .- HOW TO UPDATE EOS3 ROM or install a new different ROM:
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the new rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Enjoy your new rom!
I hope this can help people to unlock their xooms.
Thanks to "wesamothman" and "Cubanluke88" for the initial support given and specially to EOS Team and the people that created ClockWorkMod for sharing their time, work and knowledge with us. They've converted my "slow xoom" in a very powerfull and fully functional tablet.

Couldn't expect less from you. Super great guide...
Sent from my MZ601 using Tapatalk 2

Post reserved for updates in case the initial post gets too large...

I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
Sent from my Xoom using Tapatalk 2

Thanks for your words...
In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".
Thanks.
--
Sent from my Xoom with EOS3 ROM using Tapatalk 2

Updated with some pictures

Updated with links to v141...

eos 6 recovery.img not available
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial

kakrikakri said:
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
Click to expand...
Click to collapse
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.

NoP_Compiler said:
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
Click to expand...
Click to collapse
wow that was a quick reply.. THANKS (Y)

kakrikakri said:
wow that was a quick reply.. THANKS (Y)
Click to expand...
Click to collapse
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).
I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").

Same method for stock ics?
Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?
Thanks !

Help !!! In a lot of trouble
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!

kakrikakri said:
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
Click to expand...
Click to collapse
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard

wesamothman said:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
Click to expand...
Click to collapse
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
First time ROM flashing is longer than normal booting, like 5 min ,
If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
Did you finally succeded "booting" EOS3?

NoP_Compiler said:
Did you finally succeded "booting" EOS3?
Click to expand...
Click to collapse
Yes it did and it works perfectly
Thank you NoP_Compiler and wesamothman
Sent from my Xoom using xda app-developers app

Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup

dead android in step 2
Hi,
Thanks for the great tutorial.
I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"
In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.
Any idea about what I might be missing?
thanks!

[xt1920-15] [pettyl] stock firmware rooted latest ota updates fixed + 'badkey' fix

Just for the record, Motorola phones and normally quick and easy to ROOT however this is been a right pain in the ass. No guide on here has worked properly for the UK version anyway so soon after I found a working way i thought i would do this to help anyone else....
Requirements:
unlocked bootloader
THIS ZIP FILE
extract the files and open a cmd prompt in the ADB folder or run a cmd and us 'cd C:\adb\' [or location of the unzipped adb folder]
run 'fastboot boot recovery.img'
backup the cache partition so it creates the TWRP>BACKUPS>SERIAL>ROM folder
copy the rooted rom folder to TWRP>BACKUPS>SERIAL>*here* [ please note serial stands for the serial number of device and this will vary with each person]
hit restore, system + data + boot,
when finished reboot to recovery
you are now in the stock recovery so hold the power button and tap volume down to unlock the menu then you want to wipe data factory and just use data AND NOT the personalised content as well..
then reboot
do the initial set up.
then perform 2/3 system updates [security patches i believe? from the system settings > updates]
when all this is complete, afterwards click on magisk manager and let it update. It will then give you a warning error saying the version of magisk too old.
so power off your phone and then put it back into bootloader. [hold power + vol down from a powered off state]
use fastboot boot twrp_james.img [from cmd promt inside adb folder]
when the recovery loads in the same cmd prompt type adb push Magisk-v18.1.zip /sdcard/ [or u can just copy the zip file onto the storage if it shows up on ur pc]
install magisk 18.1 and then reboot to boot loader and use fastboot flash logo logo1.bin to remove bad key error
have been in a mad rush to get this done before i go work hopefully you can understand if there are any problems just msg me

TheLastAlphaUK said:
Requirements:
unlocked bootloader
THIS ZIP FILE
Click to expand...
Click to collapse
BACKUP MIRROR OF FILE [MEGA]

Hi there, im unable to backup the cache partition (showing as 0mb in cwm) think it may have something to do with encryption.
I have my phone in a somewhat usable state by restoring cwm backup i found on xda, but when booting custom recovery it will not mount /cache ,/data etc
Would love to follow your instructions, do you have any ideas

links are dead

I have unlocked the bootloader and flashed TWRP on this phone to root.
i have not found a live link for any LineageOS or other custom rom, but root still works on stock rom.
i have saved all the necessary files on my PC so if you need help just reply or message me