Database Info

[RECOVERY][UPDATE] Unofficial port of ClockworkMod Recovery for folio100 - BETA

This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel

wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread

Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work

Great Job!! Now we just need some AOSP/CM7 love

Can I use it with stock rom too? Tnx

Great work thanks alot for taking the time to do this

girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.

boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.

Of course dude, take your time and slowly churn that tasty gingerbread dough

wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there

Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..

Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery

Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.

Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)

boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot

wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?

wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.

nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you

I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).

Looking very nice. Just flashed it and made a backup

Huawei Ideos U8150 Recovery Guide

Many people seem to be having a lot of trouble flashing recoveries for their Ideos so I figured I would write this thread because I haven't found any other guides for flashing U8150 recoveries.
Method 1
1. Install Terminal Emulator from the market.
2. Install Root Explorer from the market.
3. Download the recovery of your choice and copy the recovery.img to your sd card. (if its not named recovery.img rename it)
4. With Root Explorer, navigate to where the recovery is and copy it to /system/bin/ (remember to select mount as R/W first in order for it to copy.)
5. Open Terminal Emulator and enter the command "su" (without the quotes)
6. After that enter the command "flash_image recovery /system/bin/recovery.img" (again without the quotes)
7. That's it, the recovery has been flashed. Reboot in recovery to confirm.
8. Once you've confirmed the recovery flashed properly remember to delete the recovery.img from /system/bin/ (using root explorer, and mount as R/W)
Method 2
I find this method much easier because you don't have to go through the trouble of installing drivers. Also you don't need to connect your device to your PC. Your device needs to be rooted though. If your device isn't rooted simply download z4root from the market and root it.
1. Download and install ROM Manager from the market.
(If you simply want to flash the latest working ClockworkMod Recovery and not an older version or UltraJack skip to step 6.)
2. Navigate to the folder /clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries/ (create the folders if they are not already there)
3. Delete any files in that folder.
4. Download the recovery you want to use from the recovery links below. Unzip the file. Rename the "recovery.img" file to "recovery-clockwork-3.0.2.4-ideos.img". (See note below)
5. Copy the renamed "recovery-clockwork-3.0.2.4-ideos.img" into the recoveries folder (/clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries/)
6. Open ROM Manager and select Flash ClockworkMod Recovery. It will bring up a list of devices, just scroll down until you find Huawei U8150 Ideos and select it.
7. ROM Manager will flash the recovery image for you and you're done.
Now you have a working recovery. To test select Reboot into Recovery from ROM Manager.
Since you are renaming the recoveries remember to keep track of which recovery is currently in the recoveries folder.
Note: recovery-clockwork-3.0.2.4-ideos.img is the name of the latest ClockworkMod Recovery in rom manager at this time (28/04/2011). If it is updated and I haven't updated the thread, change the name of the recovery to the latest version.(i.e if the latest recovery is ClockworkMod 3.0.2.5, rename the img to recovery-clockwork-3.0.2.5-ideos.img instead of recovery-clockwork-3.0.2.4-ideos.img)
Method 3
Installing Drivers
Windows 7:
Download and install PDANet. That should install the drivers for you.
Alternatively, you could download the drivers and install them manually. First download the drivers for your OS from here.
Drivers Windows 32-Bit Mediafire Multiupload
Drivers Windows 64-Bit Mediafire Multiupload
Connect your device(you don't need to turn on USB storage) then open device manager. Right click on your device and select properties, select the hardware tab and then select properties. Select the drivers tab, then select Reinstall/Update Driver. Choose the option (Browse my computer for driver software) and select the drivers you just downloaded. (Extract the zip file first)
MacOS
Download and install PDANet. That should install the drivers for you.
Linux
Follow this guide by bloodychaos to get ADB working.
Flashing Recovery
1. Once you have the drivers installed download the recovery of your choice from the links below.
2. Extract the zip file and open the folder.
3. Turn off your phone.
4. Connect your phone to your PC.
5. Reboot your phone in bootloader mode. (Turn it on while holding the Volume Down button and the End(Red) Key.)
6. Run the install-recovery file/script for your OS found in the extracted recovery folder.
7. Once it flashes your phone should reboot.
N/B If you have trouble with the drivers or any other problems try Method 1.
Now you have a working recovery. To test turn off your phone, then turn it on while holding the Volume Up Key and the Green(Call) Key.
Recovery Links
ClockworkMod 3.0.2.4 (by marcnvidic)
Download Mediafire Multiupload XDA Thread
UltraJack 6.2.2 (by Ultrakiller)
Download Mediafire Multiupload XDA Thread
ClockworkMod 3.0.1.(by udK)
Download Mediafire Multiupload
Credits
marcnvidic, Ultrakiller, udK for making the recoveries. bloodychaos for the Linux ADB guide. Koush for ROM Manager. f1ng3r for pointing out the terminal emulator method.
All other Ideos devs who've helped me along the way because I picked up a lot of this info from random threads.

Reserved for future use.

Thnx, very informative

No Huawei U8150 Ideos on the list of ClockWorkMod
wachw said:
6. Open ROM Manager and select Flash ClockworkMod Recovery. It will bring up a list of devices, just scroll down until you find Huawei U8150 Ideos and select it....
Click to expand...
Click to collapse
I've just downloaded Rom Manager Premium c4.2.0.2 (latest) from the market and i can't find the Huawei U8150 Ideos on the list of ClockWorkMod
Am i missing something? I copied the image file to the directory specified.
cheers,
Simon

sayo9394 said:
I've just downloaded Rom Manager Premium c4.2.0.2 (latest) from the market and i can't find the Huawei U8150 Ideos on the list of ClockWorkMod
Am i missing something? I copied the image file to the directory specified.
cheers,
Simon
Click to expand...
Click to collapse
For some reason the ideos does not appear on the list, I have no idea why, you might have to try one of the other methods to flash a recovery.

wachw said:
For some reason the ideos does not appear on the list, I have no idea why, you might have to try one of the other methods to flash a recovery.
Click to expand...
Click to collapse
Thanx for the quick reply, i ended up using method 3.
Just one thing about method 3, the batch file doesn't exist in the ClockworkMod 3.0.2.4 (by marcnvidic) link as it's only an .img file. So i simply downloaded the ClockworkMod 3.0.1.(by udK) zip file, and replaced the image with the newer 3.0.2.4 after unzipping it.
Thank you for the guide, i've successfully flashed clockworkmod, and backed up the phone. now all i have to do is choose a ROM.
which ROM do u suggest???
cheers,
Simon

sayo9394 said:
Thanx for the quick reply, i ended up using method 3.
Just one thing about method 3, the batch file doesn't exist in the ClockworkMod 3.0.2.4 (by marcnvidic) link as it's only an .img file. So i simply downloaded the ClockworkMod 3.0.1.(by udK) zip file, and replaced the image with the newer 3.0.2.4 after unzipping it.
Thank you for the guide, i've successfully flashed clockworkmod, and backed up the phone. now all i have to do is choose a ROM.
which ROM do u suggest???
cheers,
Simon
Click to expand...
Click to collapse
That was the official link from marcnvidic, the multipuload & mediafire mirrors should have the batch files. Anyway, for the rom I would suggest FUSIONideos or Dronix 0.4, there's a poll somewhere on this forum and those are the most popular, Gingerman V4 is also pretty good but I wouldn't suggest it as your first rom because its still relatively new and is still being improved so it isn't perfect as a daily use rom yet. I switch btw fusion & gingerman, but I can tell you fusion is pretty stable. One thing to note however, if you are not using gingerman or another cyanogenmod port, I would suggest using clockworkmod by udK as your recovery, cwm 3.0.2.4 has some issues making backups of other roms.

Mate, I'm loving this
So far i've flashed CM6.1 port, Fusion, and Dronix 0.4! hehe i'm addicted now! Right now i'm back to CM6.1, but will try Gingerman V4 soon
Thanx for your help mate, you're a champion.
EDIT: thought i'd explain why i'm on CM6.1. Reason being is that I even though i think Fusion is the better one so far, I can't seem to have a solid 3G connection.
I'm from Sydney Australia, and with Optus. The APN seems to be correct and all, but the phone keeps switching from 3G to H.

tq for this information...i have done it

thanks !!!!!

I'm having a bit of trouble.
I was trying method 2 and clicked the wrong phone model. I went to change it but found that "Huawei IDEOS U8150" is not listed. Now I cannot access my recovery menu, and cannot install clockwork recovery. How would I fix this? I've been searching for hours and only found ways to remove it via the recovery menu.
Everything is functioning fine so it's not a big problem, I just can't get to the recovery menu/boot loader.
Also, I attempted method 1 because it doesn't involve the use of the recovery menu. It says, "flash_image: not found" when I type the command.
Nevermind, put about another hour into searching. Thank you so much for this guide it helped me alot.

I installed ROM Manager and pressed "Flash ClockworkMod Recovery".
It downloaded some files and flashed the Mod.
(I have my u8150 rooted using SuperOneClick)
Now it shows that my ClockworkMod Recovery version is 3.0.2.4
BUT the problem is that:
1>If I press reboot into recovery, the phone reboots and I end up staring at the IDEOS logo for ... like ever.
2>I pressed Backup Current ROM and after giving it a name (Stock ROM), I pressed OK and again the same result.
3> I found on the internet that to go into the recovery mode I need to press the SEND (green button) and the Volume UP together and then press Power.
I did it, even held the three buttons in the next try... but sadly every time the phone got stuck and I ended up looking at the IDEOS logo.
and the only way to get the phone working again was to take out the battery and press Power. (the phone itself is running fine)
PLz kindly help me out on this.. am I missing something??
Thnx

That means the recovery didn't flash correctly. Are u sure u selected the right phone from the rom manager list. Try flash recovery again. But first u need to delete everything in the clockworkmod/download directory on the sd card. Or if you know how to, just delete the recovery image in that folder.

yes I selected the corret phone i.e. Huawei u8150 Ideos
i deleted everything in the clockworkmod/download directory on the sd card
re-flashed..
still the same problem
btw.. during flashing, twice I got a pop-up asking me to either "force close" or "wait" and I pressed "wait" both times.
P.S. I just noticed after removing the battery that it says the model of my phone is U8150-D. I wonder what the "D" stands for?

It shuld not be force closing. Maybe rom manager has a problem. Try reinstalling it. If that doesn't work I suggest trying one of the other methods to flash the recovery.

ok so ive just tried Method 1 and followed every step... and the funny thing is that when I enter the following command in terminal emulator:
flash_image recovery /system/bin/recovery.img
.. it says
flash_image: not found
lol
now im downloading ultrajack
Update:
Ive tried Method 3:
and for 10 minutes now.. my command prompt is still showing this message:
< waiting for device >
:-(

For method 3 try running the bat file first then when it shows you the waiting for device message turn on the phone in bootloader mode.

just did as you said, i turned off the phone.. ran the bat file, when it said waiting for device I plugged in the phone (battery charging started), then I pressed power while holding Red and Volume Down...
the result is the same..
(the same was the result when running ultrajack)
>im just wondering... do I need to install any kernel or something before doing this??
>also I noticed that the CWM's recovery.img that I got from this forum is 3.94MB, while the one I downloaded through the Rom Manager was 3.71MB (on both tries).
P.S. how do I completely remove CWM and its files? so i can start the process fresh. I read at some forum that there is some file related to this called update.zip... whats that?
(Sorry for being a bother and thnx for your help)
UPDATE !!!
Its done... its finally done. Yattaaaaa!!!
ok so here is is what I did....
>I deleted everything in the clockworkmod folder like you once mentioned before.
>You said that while flashing I shouldn't be getting a pop-up that asks me to either force close or wait.
>So I had a hunch that the popup that appeared during the flashing might have been caused due to the screen timeout set at 30 sec (i mean a clash of two processes)
>So, i set the screen timeout to 30 minutes (hehe) and pressed Flash ClockworkMod Recovery from the Rom Manager.
>It flashed without any pop-ups and it successfully booted into recovery mode (and the first thing I did was to backup my phone)
Once again thnx for your support wachw.
... and if you don't mind can you help me with one more thing (if it's convenient for you)... plz guide me how to install multitouch for my phone provided here (coz nobody at that thread has been generous enough to guide me ;_; )
http://forum.xda-developers.com/showthread.php?t=1014183
[i have downloaded the multitouch patch and the complied kernel, plz guide me on what to do next. thnx ]

Sorry about the delay, been busy, but, if you send me the link to your provider's rom I can make a multitouch version for you. Why don't you want to install a custom rom?

here is the link to my provider's rom:
http://webftp.myppc.it/index.php?dir=Ideos/ROM/
direct link
http://webftp.myppc.it/index.php?dir=Ideos/ROM/&file=U8150 V100R001C230B828SP02(Pakistan Ufone ).rar
custom rom, hmm.. well ive heard about them but for now i want to see how much can the stock rom be modified xD
btw is it really possible to edit the rom and remove the simlock
someone here says so:
http://forum.xda-developers.com/showthread.php?t=850110&page=5

[Q] Root my xoom ?

I just bought a second hands xoom , I really had bad luck because my device reboots itself automaticaly too often
it's about a MZ601 3G 32g. of course I can't find the seller back in my life ...
OS 3.2
build number H.6.5-17-3
Kernel 2.6.36.3
I don't know my xoom belongs to which country . I would like to root it
Becasue I've heard it might be helpfull .
I 'm really an newbie !
Can someone help me out ?
Best Regards
Kevin

The MZ601 is the MOTO/EU/umts_everest 3G: 3.2/H.6.5-17-1 GSM (means you can use any SIM card in your device, you can send and receive SMS)
You first need to install Android SDK, Here is a link to the ADB Tutorial.
http://www.xda-developers.com/android/adb-easy-tutorial/
Instructions assuming that you have successfully installed the Android SDk -
(solarnz)
1. Downloading the rooting-update zip file.
Download the zip file from here - http://goo.gl/Om9aP
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
2. Flashing recovery
1. Download this Recovery image. http://bit.ly/iLRAIV (place this image in you SDK PlatformTools Folder, or which ever folder that contains your adb.exe)
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
AS Always, If This Was Helpful - Hit The Thanks!

Mjamocha said:
The MZ601 is the MOTO/EU/umts_everest 3G: 3.2/H.6.5-17-1 GSM (means you can use any SIM card in your device, you can send and receive SMS)
You first need to install Android SDK, Here is a link to the ADB Tutorial.
http://www.xda-developers.com/android/adb-easy-tutorial/
Instructions assuming that you have successfully installed the Android SDk -
(solarnz)
1. Downloading the rooting-update zip file.
Download the zip file from here - http://goo.gl/Om9aP
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
2. Flashing recovery
1. Download this Recovery image. http://bit.ly/iLRAIV (place this image in you SDK PlatformTools Folder, or which ever folder that contains your adb.exe)
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
AS Always, If This Was Helpful - Hit The Thanks!
Click to expand...
Click to collapse
Thx so much I've root my device now .
I've one extra icon calls superuser ??? What can i do with it ?
What is now difference between a normal and an root device ?
What do I have more possiblilitie with rooted device ?
best regards
Kevin

Is this method workable in 4.0.3 or even freshly released 4.0.4?

@Kevin
superuser gives you access to your device settings and all files.
Install root explorer, and you can browse your system files, but be very careful.
With root you can customize you xoom.
To find out more on what root access can do for you, use google to search,
this would not be the place for that. After you get a better understanding of the
root process, browse this forum for Modifications and what not.
Now you gotta find a ROM that fits your taste. You can start here:
http://forum.xda-developers.com/showthread.php?t=1459641
Make sure you Flash the GAPPS directly after you flash your new ROM, then reboot. There are many ROMS to choose from in this forum. Find the one that fits your device and your needs. Welcome to the Dark Side my Friend!
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
Ftnjohn said:
Is this method workable in 4.0.3 or even freshly released 4.0.4?
Click to expand...
Click to collapse
Yes you can root your device on stock 4.0.3 using this method. From there find a 4.0.4 ROM to your taste and flash it in CWM recovery. (If you are using a XOOM) I prefer the EOS 4.0.4 ROM which is their Nighty Builds. You can find the Xoom EOS Nightly ROMs that fits you device by searching the Forum.
If This Was Helpful Hit The Thanks!

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

[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