Step by step procedure to root mz601 and flash ics custom rom.

Search This thread

Grege50

Member
Aug 17, 2012
36
6
Melbourne, Australia
Thanks for the guide

I followed this guide to update a Hong Kong sourced Xoom with the odd partition layout. It worked well and I now have my Xoom running Android 4.04 and have access to the whole 32gb internal drive.

But, I had to make two changes. I used Rogue recovery rogue_XM-recovery-1.50-rc3.zip as the recovery.img - others I tried just did not work.

I use Eos-umts_everest-2.0.0.zip as the ICS image.

So, a big thanks for the guide. It worked and I am happily running ICS and I am ready to update to Jelly Bean when there is a stable release for my Xoom 3G
 

tafida10

Member
Apr 9, 2013
5
1
ROM and recovery

I couldn't get the files from the link am guessing is been updated sorry am very new at this don't want to brick my device just an advice on possible replacements of both ROM and recovery image, I saw something like v.157 is that correct for the ROM as for image I have no clue, can you please update any changes I have the UK 601 with wifi and 3g XOOM. Also any extras that are very vital for its running thanks in advance.
 

elkedra

Senior Member
Feb 26, 2012
77
22
hiding in the desert
I couldn't get the files from the link am guessing is been updated sorry am very new at this don't want to brick my device just an advice on possible replacements of both ROM and recovery image, I saw something like v.157 is that correct for the ROM as for image I have no clue, can you please update any changes I have the UK 601 with wifi and 3g XOOM. Also any extras that are very vital for its running thanks in advance.

Latest recovery thread: http://xdaforums.com/showthread.php?t=1999897

Latest Team EOS image for MZ601 ( Everest): http://goo.im/devs/teameos/roms/eos4/nightlies/umts_everest

Latest Gapps ( use one for Xoom only): http://goo.im/devs/teameos/roms/eos4/gapps

If you need Motorola drivers or SDK files you can Google them.
 
  • Like
Reactions: tafida10

tafida10

Member
Apr 9, 2013
5
1
xoom 601 3g

i used the updated versions still not getting it right, in the command prompt i typed the following
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot
adb reboot recovery

note: i put them all at the same time if not it doesn't work

but here is the result i get from the command prompt, adb reboot bootloader error device not found, fastboot flash recovery recovery.img can not load. to be precise here is the command prompt

"Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tafidas>adb reboot bootloader
error: device not found

C:\Users\Tafidas>fastboot oem unlock
...
(bootloader) To continue, follow instructions on the device's display...
OKAY [ 96.066s]
finished. total time: 96.073s

C:\Users\Tafidas>fastboot flash recovery recovery.img
error: cannot load 'recovery.img': Invalid argument"

my device comes on as new though please advice
Note i put both the zip file and its extracted content of the recovery image in same directory as the adb which means in platform-tools

also question do i have to unzip the files i downloaded to the tablet
 
Last edited:

wesamothman

Inactive Recognized Contributor
Apr 5, 2012
6,521
26,695
Dallas - TX
i used the updated versions still not getting it right, in the command prompt i typed the following
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot
adb reboot recovery

note: i put them all at the same time if not it doesn't work

but here is the result i get from the command prompt, adb reboot bootloader error device not found, fastboot flash recovery recovery.img can not load. to be precise here is the command prompt

"Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tafidas>adb reboot bootloader
error: device not found

C:\Users\Tafidas>fastboot oem unlock
...
(bootloader) To continue, follow instructions on the device's display...
OKAY [ 96.066s]
finished. total time: 96.073s

C:\Users\Tafidas>fastboot flash recovery recovery.img
error: cannot load 'recovery.img': Invalid argument"

my device comes on as new though please advice
Note i put both the zip file and its extracted content of the recovery image in same directory as the adb which means in platform-tools

also question do i have to unzip the files i downloaded to the tablet

Your issue is missing / wrong paths to the files you attempt to load.

Use Lord tool now. It automates it all for you. Here
http://xdaforums.com/showthread.php?p=21901018
 

elkedra

Senior Member
Feb 26, 2012
77
22
hiding in the desert
Firstly: recovery - I haven't used adb for a while and I don't have a computer to test it out.
If you already have an earlier version of CWM recovery on your xoom I think you can use the zip file from this thread by putting it on your xoom's sdcard or in your internal storage and flash it from there to update it. Otherwise you may have to look around the xoom forum for advice with adb problems. ( I just noticed wesamothmans post above.)
Secondly: you have to put the zip file of the Team EOS Rom and the zip file for gapps on your xoom's sdcard or internal storage and flash them from recovery (not thru adb). When you are first in recovery you should do a system format if you want a nice clean install. ( Don't forget to backup any apps you want to keep using nandroid or Titanium Backup )
Hope this is of some help.
 
Last edited:
  • Like
Reactions: tafida10

tafida10

Member
Apr 9, 2013
5
1
green bot of !

i have done exactly that and i keep ending with the green bot of ! (a horizontal android logo with exclamation mark) and i also used the Lord AIO tool still ended up with that logo, i heard its due to OTA update i did, please i need help on how to remove that i have seen few but they talk in high level language please help if you know.
 

wesamothman

Inactive Recognized Contributor
Apr 5, 2012
6,521
26,695
Dallas - TX
i have done exactly that and i keep ending with the green bot of ! (a horizontal android logo with exclamation mark) and i also used the Lord AIO tool still ended up with that logo, i heard its due to OTA update i did, please i need help on how to remove that i have seen few but they talk in high level language please help if you know.

What is the status of your bootloader? Is it unlocked?
 

tafida10

Member
Apr 9, 2013
5
1
bootloader status

after using the lord AIO it says succesfull although i dont know how to confirm if it is.
 

wesamothman

Inactive Recognized Contributor
Apr 5, 2012
6,521
26,695
Dallas - TX
I am not sure if I still have the files roaming somewhere in my xoom. This is very old thread. I will check though.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    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.

    • Your custom ROM will be: Eos-umts_everest-71.zip. This is the latest ROM released on May, 2012. Very stable and everything works with it. No issues found. http://goo.im/devs/teameos/roms/nightlies/umts_everest/• Your GOOGLE APPs (GAPPs) would be: gapps-ics-20120429-signed.zip http://goo.im/gapps

    Full thread in details can be found here: http://xdaforums.com/show....php?t=1459641

    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, 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/recoverie...ecovery-r6.img
    • GAPPS: http://goo.im/gapps, your GAPPs would be: gapps-ics-20120429-signed.zip
    • ROM: Your custom ROM will be: Eos-umts_everest-71.zip. This is the latest ROM released on May 2012. http://goo.im/devs/teameos/roms/nightlies/umts_everest/

    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 40 - 50 seconds).

    Advice: purchase Startup Manager from the market. Remove unwanted user programs from the startup. That will boost the boot time of your xoom. and don't remove superuser or superSU.

    To have better battery life, from the market buy JuiceDefender ultimate. configure it as aggressive. don't worry, it is ok. This will give you around 2 hours of extra battery life than the promised 10 hours. Keep that in the startup.

    You may need after that to install terminal emulator from the market if not already installed by the ROM to check if you have root permissions. Just type "su -" you will be prompted with superuser check. Click allow. and then type "id" You will see your id is root.

    Should you require further details or assistance, please let me know. And enjoy the best rom customized ever for your device

    Best Thanks to TEAM EOS for the great ROMs they provide.

    After you are done with all that, let me know and will explain to you how to work with the pre-installed gooManager in the new ROM. It will make your life much easier to upgrade to future releases of your ROM.

    Sent from my MZ601 using Tapatalk 2
    2
    i used the updated versions still not getting it right, in the command prompt i typed the following
    adb reboot bootloader
    fastboot oem unlock
    fastboot flash recovery recovery.img
    fastboot reboot
    adb reboot recovery

    note: i put them all at the same time if not it doesn't work

    but here is the result i get from the command prompt, adb reboot bootloader error device not found, fastboot flash recovery recovery.img can not load. to be precise here is the command prompt

    "Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Tafidas>adb reboot bootloader
    error: device not found

    C:\Users\Tafidas>fastboot oem unlock
    ...
    (bootloader) To continue, follow instructions on the device's display...
    OKAY [ 96.066s]
    finished. total time: 96.073s

    C:\Users\Tafidas>fastboot flash recovery recovery.img
    error: cannot load 'recovery.img': Invalid argument"

    my device comes on as new though please advice
    Note i put both the zip file and its extracted content of the recovery image in same directory as the adb which means in platform-tools

    also question do i have to unzip the files i downloaded to the tablet

    Your issue is missing / wrong paths to the files you attempt to load.

    Use Lord tool now. It automates it all for you. Here
    http://xdaforums.com/showthread.php?p=21901018
    2
    Hi,
    I've downloaded this from but the problem is that I can't use an external SD with this rom
    I even don't get access him although I can see him at settings under storage
    what the solution?

    Use a file explorer, the sd card should be mounted at mnt/external1
    2
    the recovery image link does not work anymore.

    There you go. I just checked. It is working...
    http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img

    Sent from my MZ601 using Tapatalk 2
    2
    Yeah. Now after you successfully rooted your xoom, you can go to recovery by long press on the power button. Enjoy.
    By the way, which rom version did you flash? V72 or v 74?

    Sent from my MZ601 using Tapatalk 2