Database Info

[GUIDE] XOOM WIFI CUSTOM RECOVERY, ROOT AND CUSTOM KERNEL for NooB’s (Depreciated)

5/12/2011 : Thread marked depreciated due to the recent movement to get the 3.1 Honeycomb update installed. While parts of this tutorial may remain valid, the overall synopsis is not. For those of you that have used this guide I can vouch for the procedure in the thread linked below as a viable option to install the 3.1 update.
Thread to 3.1 Android Update
This tutorial was written for the NooB’s among us (like me) that are new to this stuff and are having a hard time “piecing together” all of the steps. While I am actually a not quite a beginner, NONE of these steps/methods/files have been developed by me. I have simply compiled the procedure in a document that I hope will be useful. With this in mind all the credit belongs to the many individuals that contribute in the XDA Developers forum. I have reviewed many posts by many people and have used all of the information along the way. I have intentionally chosen NOT to mention any specific names for fear that I will leave someone out. If you see anything herein that reminds you of something you posted then it probably is true and you are respectfully THANKED!!!
THIS TUTORIAL WAS CREATED AND TESTED ON THE US WIFI ZOOM. THE PC WAS RUNNING VISTA 32BIT
As a courtesy I will attempt to keep this post up to date with links to revised files. Bear in mind that I performed my upgrade using the original information/links and it was successful. I suggest that since this tutorial is for beginners that you follow the ORIGINAL links to complete the guide. Once you get that far you should have a better understanding of the procedures and be ready to "experiment" by flashing new kernals, recoveries, rom's, etc., using directions found in the corresponding section(s) of the development forum. After-all that is the real reason for most of this stuff anyway. As an example.... there is a 5/3 update below which adds links to newer versions of the Tiamat Kernel and Clockwork Mod. While you could probably just download and use the updated versions of these files in conjunction with this tutorial, I have NOT personally verified this to work. If anyone does try, or if the Dev's want to chime in, please post so that I can update accordingly. Thanks.
5/3/2011 --- UPDATE: Added Links to updated Tiamat Kernel (1.4.1) & Clockwork Mod (3.0.2.8) and added links to discussion threads.
5/11/2011 --- NOTICE: If you are wanting to upgrade to the recently released 3.1 Honeycomb Update than I suggest you re-consider following this guide. The upgrade procedure requires that the device be stock or the update will fail. Furthermore there has not been a Kernel Developed yet that works with 3.1 and some users were complaining about issues with ClockWork Recovery after applying 3.1. See the development section for more information
A) Installing ADB
ADB stands for Android Debug Bridge and simplistically stated will be used to send commands to your XOOM using the keyboard on your PC. In essence your PC will be acting like a terminal. ADB is included in a package known as the Android SDK. The following steps should be taken to insure a successful install of the SDK, therefore giving you access to ADB.1. Install Java JDK : http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.htmla. Download appropriate Java SE Development Kit (JDK) from link above
b. Double click to Install JDK
c. Accept Setup Defaults​2. Install SDK Starter Package: http://developer.android.com/sdk/index.htmla. Download SDK Starter Package from link above. There are versions available for Microsoft Windows, Linux and Mac OS X. In case of Windows, both an installer and a zip file are available but there isn’t any need to use the installer as a formal installation is not required. Download the ZIP file.
b. Once you have downloaded the SDK, simply extract the compressed file to a location on your computer. In our case, we have extracted it to the root of our C drive and that makes [FONT=&quot]C:\android-sdk-windows[/FONT] the installation location of the SDK. From here onwards, we shall be referring to this location as the ‘SDK folder’.​3. Download the SDK Platform Tools using the SDK Mamager.a. Browse to the SDK folder and launch SDK Manager.
b. When launching it for the first time, it will present you with a window to choose packages to install. The first option begins with ‘Android SDK Platform-tools’. Make sure it is checked, and uncheck all the other packages for now. You can check/uncheck a package by simply double clicking on the package. Again, the only package you want to install is the Android SDK Platform-Tools.
c. Once the process is done, you will have a ‘platform-tools’ folder inside your SDK folder. That folder will include ADB and all its dependencies.
d. Make a copy of the File “fastboot.exe” which is in the “tools” directory and place it in the “platform-tools” directory.​B) Install XOOM USB Driver
Just to be sure your XOOM is recognized by your PC it is recommended that you install the latest USB drivers for your system.1. Install MotoHelper : http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Driversa. Download the Driver with MotoHelper from the Link above
b. Double Click downloaded file and follow on-screen instructions to install.​C) Unlock Bootloader
Unlocking the bootloader gives you full control over the device so you can flash new Recovery’s, kernels, ROM’s, ETC. THIS STEP WILL DELETE ALL DATA AND SETTINGS ON YOUR XOOM.1. Put XOOM in Debug modea. On the device, go to home screen, press [FONT=&quot]Apps[/FONT] > >Settings>>Applications>>[FONT=&quot]Development[/FONT], and enable [FONT=&quot]USB Debugging[/FONT].
b. Now connect your XOOM to the PC via USB. New hardware installation should begin and it will start looking for and installing the drivers.
c. A prompt should appear that states the drivers were installed successfully. On my PC the AutoPlay Device Options also appeared. I clicked “Open Device to View Files” and saw the device Storage with 27.8 GB free of 28.7 GB.​2. Execute ADB Commandsa. Open a command prompt by navigating to the ‘SDK Folder’, Holding the shift key, right clicking on the “platform-tools” folder and selecting “Open Command Window Here” from the popup menu.
b. In the new command window type: adb reboot bootloader and press enter.
c. Wait for the Dual Core screen with “Starting Fastboot protocol support” in the upper left corner to appear and then type: fastboot oem unlock in the command window and press enter. You should see: “To continue, follow instructions on the device’s display…”.
d. Read the WARNING on you XOOM and either Continue Below or Cancel following the on-screen instructions.
e. If you decided to continue then on the XOOM Push Volume Down Button to change the selection from “Cancel” to “I accept” and then press the Volume Up to select that choice.
f. You will be questioned again so Push Volume Down then Volume Up to confirm you want to UNLOCK your device. You will see “Device Unlock operation in progress…” “Formatting UDA”
g. When the operation completes the device will read”Device unlock operation done – rebooting…” and the device will reboot. The windows new hardware “gong” will sound a couple of times during this procedure. After this step when my XOOM rebooted I also saw an “MTP Device” driver Install dialog box on my PC. Unplug the device, and quickly perform the initial set-up. You can “Skip” any steps that will allow you to (like WiFi setup). Just get back to the home screen and continue below:
h. Verify that USB debugging is still enabled and if not re-enable it as outlined above.
i. Re-connect your XOOM to the PC and close any AutoPlay dialog.​D) Install Custom Recovery
A custom recovery allows you to flash files created by community developers such as ROM’s, Radios, Kernels, Themes, ETC. It also allows you to perform special tasks such as system backup’s, partitioning, cache wiping, ETC. As of 4/28/2011 the generally accepted custom recovery for the XOOM is ClockworkMod Recovery v3.0.2.5. Clockwork Discussion Threada. Download Clockwork Mod from here: ClockworkMod 3.0.2.5
3.0.2.8 ClockworkMod
b. Place the File “recovery.img” that you just downloaded in the “platform-tools” directory
c. In the previously open command window (if you closed it then re-open as described above) type: adb reboot bootloader and press enter.
d. The device will reboot into bootloader mode (as described above) and when this completes type: fastboot flash recovery recovery.img
e. Check the screen of your XOOM and see: “Flashing StorMgr partition recovery STATUS: - done!
f. Type: fastboot reboot in the command window and press enter.
g. Your XOOM should now boot with no noticeable changes.
h. In your command window type: adb reboot recovery
i. Your XOOM will reboot and an unfamiliar screen will appear. This is the “recovery” program and at this time you should simply verify that you see a reference to ClockworkMod Recovery in the upper left corner of the XOOM. This indicates that our efforts have been successful.
j. When my device rebooted into recovery I also saw additional Device Drivers install. This took a little while and I waited to do anything until I received the “Device Driver Installed Successfully” dialog.
k. Navigate in ClockworkMod Recovery by using the volume up/down to “move” and the power button to “select”. Look for reboot system, highlight it and hit the power button. Your zoom will reboot normally.
OPTIONAL STEPS
l. At some time later (AFTER YOU ARE ROOTED) to avoid the need to execute ADB commands to enter recovery, I suggest you look for a free application called “Quick Boot”, by Sirius Applications from the market.
m. Once Quick Boot is installed run it and simply select “Recovery” to boot into ClockworkMod. ​E) Install Custom (Tiamat)Kernel to your XOOM
The Tiamat Kernel we have chosen includes many advantages over the “stock” kernel most notably being support for the SD Card slot which as of this writing has still not been released by Moto. Tiamat Discussion Threada. Download the file “Tiamat_Xoom-v1.4.0.zip” from here: Tiamat Kernel 1.4.0
Tiamat Kernel 1.4.1 A big Thanks to Cam3era who acted as a gunia pig for this....Apparently you are better off flashing the 1.4.0 Kernal first and then flashing the 1.4.1. Details are in the Tiamat Thread
b. Make sure you have an SD Card in your XOOM. Some people are having issues with the system reporting the wrong size of the SD card and it has been suggested that you format your card in another android device prior to using it with your XOOM. Another “trick” was to use a small capacity card. Apparently this may still be a current issue so I recommend you format you card prior to use. I personally had a 1GB Micro SD that I formatted in my Android Phone.
c. Enter Recovery via adb by typing: adb reboot recovery in your terminal window and press enter.
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the Tiamat kernel zip you downloaded above onto the SD Card.
iv. "Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the zip file and select it.
vi. Navigate to “Yes – Install Tiamat_Xoom-v1.4.0.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.​e. After the XOOM reboots (this could take a while) check to insure that USB debug mode is still enabled. If not, re-enable it as described above.​F) Root the XOOM and Install Superuser APK
Root access is similar to “administrator” privileges and gives you the power to run specially developed programs that take advantage of these additional rights. An example would be a program called titanium backup which coupled with the “super user” privileges can perform backup duties not available in “non-root” environments. The following file was obtained and discussed here: Link
a. Download the file Root_Xoom.zip from here: http://forum.xda-developers.com/attachment.php?attachmentid=579548&d=1303896724
b. Connect your XOOM to the PC (again be sure Debug mode is enabled) and close any AutoPlay dialog boxes that pop up.
c. In the same command window used previously type: adb reboot recovery
d. Now, using the Volume Up and Volume Down buttons on the XOOM to move the prompt and the power button to execute a selection: i. Go to "mounts and storage"
ii. Select "mount USB storage"
iii. Your SD Card will now be mounted on your computer. Copy the “Root_Xoom.zip” file you downloaded above onto the SD Card.
iv. Go Back" TWICE then go into "install zip from sdcard" then "choose zip from sdcard"
v. Navigate to the “Root_Xoom.zip” file and select it.
vi. Navigate to “Yes – Root_Xoom.zip” and select it. It will now flash and you will see some scrolling text and a progress indicator.
vii. Wait until it says “Install from sdcard complete.
viii. Back out to main menu and reboot.​e. After the XOOM re-boots check to see that you have a new App in the Drawer called “Superuser”.​G) CLEANUP
As you become more at ease with using Clockwork Recovery you will use it more and more. There are many more features than can be described here and after all, that is beyond the scope of this tutorial. I highly recommend that you seek out more information about this tool so you can put it to good use. One term you will see used a lot is “wiping”. Wiping does exactly that to a specific partition(s) and/or file(s) thereby insuring that a new installation is “clean” and no “remnants” of prior information exist. The upside to this “cleaning” is that there is less chance of corruption from using older (or incompatible) versions of files or data and the downside is that this “data” may contain useful information such as high scores, completed game levels or even previously remembered passwords. You should learn how to back-up this data using Titanium Backup or another backup application and manually reload it after your upgrade is considered “stable”. This allows you to wipe and thereby insure that any “issues” you experience are not related to “remnants”. So, with this all said, I recommend that you now Wipe your User Data and Cache. Again, if you have not backed up, this will erase and reset things that you may not want erased or reset. Proceed with caution!!!!
a. Enter Recovery via quickboot or adb as described above.
b. Using the Volume and Power Buttons as described above navigate to “wipe data/factory reset” and select it.
c. Navigate to “Yes – delete all user data” and select it. Wait until it says “Data wipe complete”.
d. Navigate to “wipe cache partition” and select it.
e. Navigate to “Yes – Wipe Cache” and select it. Wait until it says “Cache wipe complete”.
f. Navigate to “reboot system now” and select it.
g. Set up your rooted, custom recovery, custom Kernel XOOM!! ​ENJOY

I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.

Thanks for the kind words!
One step at a time my friend. This was my first attempt at creating a tutorial and I tried to handle the "pictures" with very detailed wording. Embedding screenies into future efforts is on my to do list.
The bottom line regarding this is..... I created the tutorial before I even took my XOOM out of the box and then followed it to see if it worked. While I had some minor issues with the original draft, I believe they have all been taken care of in this final.
I expect that if any issues are encountered, it will involve the SD Card size which seemed to be a common issue for some. I had NO problems with mine.
And, while I'm at it....... I was a little hesitant to include the information on "quick boot". Some members (and I'm taking this off the top of my head right now) had issues using clockwork when it wasn't initiated using the adb reboot recovery command. I seem to recall that there was a difference in this regard between the WiFi and 3G versions. In any case if Clockwork does not seem to be working for you then stick with starting up recovery using adb and NOT Quick Boot. Having Quick Boot available in your app drawer is recommended however in case you ever experience issues mounting the device to your PC.
tritran18518 said:
I really appreciate your post. This should be sticky
P/s: you can make this instruction even better if you include some pics that can illustrate the process, some frequently errors and solutions to fix those errors.
Click to expand...
Click to collapse

Thanks
This is exceptionally well done. A tremendous resource. I hope you will keep it up to date. I will refer to it often. Thank you!

I hope this works.....With this it is time to root. Thank you for a great step by step instructions.

This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk

See this tread: Stock Image
I have NOT done this procedure but will follow that thread to see how it turns out.
Someone DID apparently re-lock the device but I don't know if that procedure removes all indications that the device was un-locked in the first place.
cam30era said:
This is an excellent tutorial! Thank you. I may take the plunge now. One request : would you be so kind as to add the steps to return to stock and relock the wifi version?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse

Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
I didn't put this "guide" in the development section because I didn't actually develop anything. Perhaps I should have?

This is an awesome step by step instruction! Good Work! Thanks a lot!

Land Master said:
Didn't really want to bump my own thread but I was hoping someone would have tried this by now. Anybody?
Click to expand...
Click to collapse
Ran through it yesterday on my father in law's new Xoom, worked great!!!
I was holding out for HTC flyer with pen, or Transformer with keyboard...
But, was impressed and may be going with Xoom now myself.
Thanks so much for the guide, it worked very well and he's happily tethered to adhoc wifi on his droid now, so very thankful as well.
Sent from my SCH-I500 using XDA App

Awesome tutorial! Now I have a place to point new users to when they hijack my thread

bigrushdog said:
Awesome tutorial! Now I have a place to point new users to when they hijack my thread
Click to expand...
Click to collapse
Thanks BRD for everything you do. I added links to the 5/1 files but also a disclaimer. Your thoughts on this would be appreciated.

Feedback
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point?
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?

cam30era said:
Land Master, I just used your tutorial to root my wifi Xoom. It is very well written and easy to understand and follow. I installed the Tiamat 1.4.1 kernel. Worked fine. Have confirmed that I have Superuser permissions. And "about" shows the Tiamat 1.4.1 kernel.
First a suggestion: Under "Install Custom Kernel" your instruction states "c. Enter Recovery via “Quick Boot” application or thru adb". I tried to use Quick Boot but could not (obviously) because I was not rooted yet. Had to use ADB, which worked fine. You may want to modify the instructions here to remove the Quick Boot option at this point? Corrected This THANKS!
Second, I have a request for help. I purchased a Sandisk 16gb micro SD card. Formatted it in my rooted Droid Incredible. Placed it in my Xoom and rebooted. I can not find my external SD Card with Root Explorer. Any suggestions?
Click to expand...
Click to collapse
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.

Land Master said:
Cam30era.....Thanks for your help. Honestly I haven't played with the SD Card in mine but do know that I have an "external" directory that is viewable in Root Explorer under "sdcard". With this said you should check the Tiamat thread because I believe the SD card "stuff" was removed in 1.4.1 because it was sketchy. I personally am still on 1.4.0.
I don't really want to take people away from the "official" (Tiamat) thread because they will all need to "learn" the same way most of us have.... by trial and error. It is my belief that this is what makes all of this fun and worthwhile. With that said however, it is my belief that a "Stable" SD Card fix will not become available until after the official Moto update drops.
My goal here was to get people to a "starting point" thus allowing them to get their feet wet and subsequently give them the tools (Root, Recovery, ETC) to continue the journey into flashing different stuff. This is why I wrote the disclaimer above.... Hoping that people would just stick to what is "known good" and march onward by researching other threads and learning as they go.
Click to expand...
Click to collapse
I'll try flashing 1.4.0 and then back to 1.4.1 and let you know. Thanks for the suggestions.

OK. I just tried to flash 1.4.0 from CWM. Got following error message:
E:Error in /sdcard/tiamat_xoom-v1.4.0.zip
(status 0)
Installation aborted.
I'm getting help now on the Tiamat thread. I'll keep you posted on how this gets resolved.

Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.

cam30era said:
Land Master, FYI: I successfully flashed 1.4.0. This did create a fully functional external folder inside sdcard. I then flashed 1.4.1 and it's a go. So you may want to modify your tutorial to indicate that you must flash 1.4.0 first.
A big "thank you" for this excellent tutorial, and for your help. I probably would not have rooted my Xoom without this outstanding aid.
Click to expand...
Click to collapse
Very glad you got it sorted. I added your suggestion to the OP.

mbowe said:
It worked very well and he's happily tethered to adhoc wifi on his droid now.
Click to expand...
Click to collapse
Ad-hoc? A stock xoom doesn't support this but a rooted one can now? Didn't realize that had been enabled.

hi,
can i install the kernel and the custom recovery without root ?
i thought i need to have root first....

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

BLU Quattro 4.5 rom list and how to instructions

Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!

Internal Memory
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/

TechSoft said:
Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!
Click to expand...
Click to collapse
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!

alanfrank said:
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/
Click to expand...
Click to collapse
I've found this: http://forum.xda-developers.com/showthread.php?t=1171531
Any idea if this can be used with another phone them the LG one he have used in the guide?
I cant post in the thread because Im new user here =/

problem
I have done everithing you said, and my cell freezes on boot forever, now what????

BLU Quattro 4.5 HD & 5.7
Need to know how to restore both devices to stock. Any aplication ODIN like to restore it back to stock from the download mode?

Please help me root, i try binary method but i just get boot loop.

Recovery + Root My experience
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/showthread.php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/GalaxyNexus/rooting/GalaxyNexusRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.

Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)

Altomugriento said:
Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)
Click to expand...
Click to collapse
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks

dinizbruno said:
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks
Click to expand...
Click to collapse
Do you try the procedure posted in 3dgames . com . ar? ( its my work translated from the 592zn page, all the credits for the chinesse people)

Anyone tried the K-touch V9 kit kat in the BLU??
www
needrom
com/
download/
k-touch-v9-miui-v5-kk

Yes, those roms (v5) are very slow. Just use the 4.0.4 stock.
I want to try the JB stock, but i can´t find the official one anywhere.
Blu quattro 4.5 official rom to download, after you delete the bloatware and put a nice and clean theme you´ll get a nice speed.

orig D440 (quattro 4.5) rom
You can find the rom on google plus under BLU Products Development search for the model!
Hope that helps. I took your advice tonight and I am back running old school. Works ok husfar

I need phone.apk of this rom for Blu Quattro
Trozzul said:
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!
Click to expand...
Click to collapse
I need phone.apk for blu quatro
please send me the file
[email protected]

[Stingray] Did you BigPart and lose data? I may have the solution...

For my fellow Stingray users (and possibly Everest users as well, if they're having similar issues), I was one of the group of people who couldn't get data on any 4.4 roms after going through the BigPart process. After a bunch of trial and error (and some excellent suggestions from fellow community members, I was able to get data working again and I'm happily enjoying KitKat on my three-year-old Xoom. If you've got a bit of patience and an hour or so, I believe I've got the solution to help you restore your data as well.
IMPORTANT: This entire process should be completely harmless to your Xoom, and the goal here is to help the group of Stingray users who lost all data functionality to repair that issue so that they can enjoy the full benefits of Android 4.4 (and potential future updates). That said, you do this at your own risk, and in doing so, you agree not to hold me accountable if you brick your Xoom, or if it dies, loses data (you’re going to lose everything but what’s on your SD Card, so think about that before you start the process), or any other unforeseen circumstances.
STAGE 1: Reverting to Stock Partitions
1.) DISCLAIMER: Any and all data on anything but your external SD Card will be completely wiped. If there are any back-ups you value, move them to your SD Card, your computer, or a cloud storage account. There’s no getting them back once you start this process.
2.) First off, you need to make sure you have everything you need downloaded and ready. You will need the following on your SD Card:
-TWRP 2.6.3.0 touch recovery from @runandhide05
-TWRP 2.6.3.0 BigPart touch recovery from @runandhide05
-a standard partition Stingray rom (I used CM 10.1 from @Steady Hawkin, 10/28 build, which you can find here)
-(optional) GApps package for standard partition rom (I used the 02.20.2013 Unified GApps found here, but you seriously don’t need them for anything.
-your BigPart rom of choice (I went with CM 11, which you can find in this thread, but there’s also OmniRom, which you can find in this thread, both of which were kindly ported by @Schischu. If you opt for Omni, you’ll also need a flashable zip file of the Superuser app of your choice.)
-your 4.4 GApps of choice (I use the PA Modular Full GApps, but any 4.4 GApps will be fine once you’ve repartitioned)
-Universal Xoom root .zip file, created by @solarnz (which you can find here)
As well as the following on your computer:
-The Android SDK, specifically ADB and Fastboot (if you don’t have this set up yet, start at the very beginning: http://developer.android.com/sdk/index.html)
-a stock android rom for the Stingray (I used HRI66, which you can find here)
-TWRP 2.6.3.0 touch recovery from @runandhide05
And one last thing:
-A good wifi connection (either through a wireless router or using your phone or other device with a data plan)
3.) Reboot your tablet into recovery and flash the non-BigPart TWRP 2.6.3.0 touch recovery. DO NOT REBOOT YET!
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
5.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
6.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
7.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time. (I’ve done this process multiple times and each time, the amount of time that it needed on various reboots was different, so be patient if you don’t want to brick your Xoom.)
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’re back to the standard partitions.
9.) Tap the Install tab. Your external sdcard should be showing by default. Flash your standard partition rom (in my case, CM 10.1) and your GApps, if you so choose (though again, they serve no purpose).
10.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen standard partition rom. Ensure that everything loads (again: this may take some time) and go through the setup process.
11.) Go into Settings and enable developer options (Settings --->About Tablet--->tap Build Number several times until Developer options are enabled.
12.) Go into Developer options and make sure that Android debugging is checked. Now you’re ready for Stage 2.
STAGE 2: Returning to stock Honeycomb
1.) Find your stock Honeycomb rom (as mentioned earlier, I used HRI66) and unzip it into a folder of its own.
2.) Inside the folder you unzipped, you may find another folder designated MZ600_HRI66. Inside that folder, there will be four files, boot.img, recovery.img, system.img, and userdata.img
3.) Copy those files into the folder that has adb.exe and fastboot.exe (if you simply installed the Android SDK as instructed, it’ll be inside the platform-tools folder, which is itself inside the sdk folder).
4.) Connect your Xoom to your computer using a USB data cable (preferably a Motorola one if you have one available) and ensure that there is a notification that says “Android debugging enabled” (if you don’t see this notification, go back into Settings --> Developer options, and make sure that “USB debugging notify” has a check in the box next to it).
5.) Open a command prompt in the directory that contains adb.exe and fastboot.exe (Windows 7 and up, click the File tab and choose “Open Command Prompt”; if you’re on Vista or older, I can’t help you, but I’m sure Google can).
6.) Enter the following command:
Code:
adb reboot bootloader
7.) Your tablet will reboot to the red “M” logo and it should say “Fastboot protocol initiated” at the top in white letters. If so, proceed to step 8; if not, and assuming your tablet has rebooted normally, try step 6 again.
8.) Enter the following commands into your command prompt, one at a time, and let each one compete. You’ll get a series of status updates in both your command window and on your tablet as each process completes. Wait for it to say “Done!” before entering the next command.
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
9.) Once all those steps have completed, enter one last Fastboot command:
Code:
fastboot reboot
10.) Your tablet should now reboot into factory Honeycomb and you can disconnect from the USB cable. As mentioned before, this is one of those reboots that could take a few seconds up to several minutes, so just be patient!
NOTE: These next several steps are much easier to complete if you have a high-speed wifi connection. At this point, if you don’t have a data connection, don’t panic, at least not yet. I tried multiple times to activate my device on the Verizon network, and while it said it was successful each time, I never managed to get a 3G connection back. Your best bet is to connect to Wifi and continue the process.
11.) On your tablet, go to Settings --> About tablet --> System Updates. More than likely, your tablet has already started downloading the next update, so you can just sit back and wait for it to download. You’ll get a notification when the download is complete. While you’re waiting, on your computer, move boot.img, system.img, recovery.img, and userdata.img from your ADB folder back into a folder where you’ll have them on-hand if you need them again.
12.) Once you get the notification that the update is downloaded, you’ll have the option to reboot and install or install later. Choose to reboot and install. Your tablet will reboot into the stock Android recovery and install the update, then go to the “M” logo screen and more white text will appear. Wait for this to complete and your tablet to reboot again.
13.) Repeats steps 11 and 12 until you receive and install the IMM76L build (I believe that’s the one) – it’ll be Ice Cream Sandwich and your data should be working. If it’s not, then I’m not sure what to suggest. Your tablet will attempt to download the stock 4.1.2 build (JZO45M) and if it completes, it’s not a big deal, but MAKE SURE YOU DON’T INSTALL IT!
14.) Go to Settings --> Developer options and turn on USB debugging again. (If everything is grayed out, tap the On/Off slider in the upper righthand corner to make the checkbox clickable). At this point, you’re ready for Stage 3.
STAGE 3: Re-rooting
1.) On your computer, find the copy of TWRP 2.6.3.0 touch recovery from @runandhide05 (the standard one, not the BigPart one, yet), and unzip it into its own folder. Copy the recovery.img file from the unzipped folder into the same directory that contains adb.exe and fastboot.exe. IT IS CRUCIAL THAT YOU REMOVED THE RECOVERY.IMG FILE THAT YOU USED TO GET BACK TO STOCK EARLIER!
2.) Connect your Xoom to your computer via USB data cable and ensure that the USB debugging notification appears and that your computer recognizes your Xoom.
3.) Open a command prompt in the directory with adb.exe and fastboot.exe and enter the following command:
Code:
adb reboot bootloader
4.) Your tablet will reboot to the “M” logo screen and it will again say “Fastboot protocol initiated”. When it’s ready, enter the following command into your command prompt:
Code:
fastboot flash recovery recovery.img
5.) Once you get the “Done” notification in the command prompt and on your tablet, enter the following command:
Code:
fastboot reboot
6.) Your tablet will reboot, and when you see the “M” logo screen, wait three seconds and press the Volume Down key. “Android recovery” will appear, press the Volume Up key.
7.) Your tablet will now boot into TWRP 2.6.3.0 and it may “hang” at the TWRP splash screen for some time – that’s normal, wait it out, and when TWRP loads, tap the Install tab. Navigate to the root of your external sdcard (if it’s not showing by default), choose the Xoom Universal root.zip file, and install it.
8.) Tap the Home icon, tap the Reboot tab, and tap System from the reboot menu. Your tablet should boot back into ICS, but you should now have a superuser app installed (ChainsDD’s, I believe). If that’s the case, and you’ve still got data functionality, then it’s time to move to Stage 4.
STAGE 4: BigPart and KitKat
1.) Reboot your tablet into recovery (you have two options – either shut down your tablet, power it back on, wait three seconds at the “M” logo screen and then press Volume Down, followed by Volume Up when it says “Android Recovery”, or reconnect your tablet to your computer with a USB data cable, open a command prompt in your adb directory, and enter the following command: adb reboot bootloader)
2.) Reboot your tablet into recovery and flash the TWRP 2.6.3.0 BigPart touch recovery. DO NOT REBOOT YET!
3.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
4.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
5.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
6.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time.
7.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’ve successfully repartitioned your tablet back to BigPart.
8.) Tap the Install tab. Your external sdcard should be showing by default. Flash your BigPart rom (and, if you’re installing Omni, your superuser zip file, or, if you’re not flashing one of Schischu’s KitKat roms, the corresponding BigPart boot img or the ElementalX kernel). NOTE: BECAUSE THIS WASN'T SUCCESSFUL FOR EVERYONE, FOR THIS STEP, PLEASE FLASH SCHISCHU'S JANUARY 4TH VERSION OF CM 11 FOR THE STINGRAY, WHICH YOU CAN FIND HERE.
NOTE: You probably can flash your GApps at this point as well; however, I’m detailing the process as I had success with it.
9.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen BigPart rom. Go through the setup process, ensure you have data, and if you do (and you didn’t do so already), reboot and install your GApps.
NOTE: You may get com.android.phone force close errors when going through setup – if this happens, it’s a good thing – pull your SIM card and reboot, complete setup, re-insert SIM card and reboot again.
If this post helped you, then give thanks to the following people (because they did all the hard work):
@bigrushdog (for the hard work on BigPart) @realjumy (for the hard work on BigPart)
@Schischu (for the excellent KitKat roms)
@xyrcncp (for clarifications that led to a minor breakthrough) @rapson2000 (for thinking outside the box and leading to my breakthrough)
There are probably a bunch of other people who contributed that I missed, but I wanted to get this up there in case other people were still having issues.

Reserved to answer any questions that may arise.

LTE data still not working
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.

variatbg said:
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
Click to expand...
Click to collapse
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?
Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
Sent from my HTC6435LVW using xda app-developers app

Help with MZ605 (Everest) stock (step 10 of stage 2)
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!

LTE data still not working
webeougher said:
What were you on when you did the BigPart process for the first time?
Click to expand...
Click to collapse
I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.
It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.
One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?
Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat.

Thiago Delatorre said:
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
Click to expand...
Click to collapse
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app

webeougher said:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Not stupid at all, it could make all the difference!
I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).
The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...
Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...
Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?
Do you know what kind of file/library is the baseband?
Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?
Thank you very much for your guide, I didn't know how to revert the bigPart
Regards,
Thiago

So @webeougher ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.
I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?
One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?
Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.

Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!

rmkenney12 said:
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
Click to expand...
Click to collapse
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
Sent from my Galaxy Nexus using xda app-developers app

webeougher said:
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
...
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked;
Click to expand...
Click to collapse
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.
Step 8 also showed NO /data-partition.
I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
Click to expand...
Click to collapse
boot status - done!
system status - done!
recovery status - done!
userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)
formatting cache: CAC status: -done!
Rebooting - after 60 min of M-logo I quit.
Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?
EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP

Thank you and Question
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?

semp3rfi said:
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
Click to expand...
Click to collapse
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app

Thank you
webeougher said:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks for the reply!

What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?
I am just trying to understand the process, and see if it can be simplified.
Thanks much for coming up with a solution. I will try it soon.

I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
Sent from my HTC6435LVW using xda app-developers app

thx
The for this topic really informative

Wow
Talk about a long process but it worked for me! Thank you so very much!
I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.
I also used the omnirom instead of cm.
Again, thanks for your hard work!

Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:

[Q] TF101 - upgrade or buy a new tablet ?

Hi All, new to this forum... what brought me here is trying to figure out if I can upgrade the TF101 to android higher than 4.0.3 that seems to be the "normal" latest version you can get.
Issues I have are: lockup, freeze, twitter post (crash twitter), screen weird colors (need reboot) etc... Maybe I have some hardware issue... planing to open the case and verify all connectors are ok and well seated.
I just spent 4 hours looking around this forum and saw the KatKiss 4.4.4 thing... I say thing because I have no clue (and did not find how) to install this thing.
So! Is it worth it that I spent hours more on understanding how to upgrade, debug and all... or I just go buy a new tablet?
I saw some post around the twitter issue that did not work either after KatKiss upgrade, so not sure if it's worth it ?
I was looking at the Samsung Pro tablets with 8 cores... seems amazing! But pricy!
Anyhow, recommendations?
If you say... sure try to upgrade to 4.4.4 with KatKiss... ok, I can try that, but from the last 4 hours of reading/looking around, I did not find instructions steps I could understand.
Most of those steps I have not clue what they are!
These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL A COMPATIBLE ANDROID 4.2/4.3 RECOVERY!
TWRP >= 2.3.2.3 is recommended, new TWRP available here
Backup everything !
Go to recovery
Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
Format /system (only if Version<026)
Flash the rom
Flash KatKiss gapps
Wipe cache/dalvik
Reboot
Click to expand...
Click to collapse
Thanks for any feedback
Cheers!
Simon

I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
I have the tab pro and i like it a lot.
I also have the tf101 running katkiss.
The katkiss is running smooth for me.
All is well and no issues this far.
So I would say try katkiss.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon

SimonFiliatrault said:
Would love to try katkiss.... but I did not find a how-to steps I can understand.... Any help would be nice.
:laugh:
Simon
Click to expand...
Click to collapse
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk

r2go said:
Hi Simon.
Is your device already rooted?
You need to root your device first.
What android version are you running?
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon

SimonFiliatrault said:
Device not rooted... Android 4.0.3.
I am looking for step-by-step instructions... if they exist?
Never did that type of mod before.
Thanks,
Simon
Click to expand...
Click to collapse
Easiest way, use Easyflasher (If your TF101 has a serial number B6O or eariler (Some B7O), it is an SBK1, most B7O and all higher are SBK2) choosing the wrong one in Easyflasher will not do any harm, it just won't work
http://forum.xda-developers.com/showthread.php?t=1688012
1: Flash TWRP recovery with Easyflasher
2. Download KatKiss ROM #33 & Latest Gapps and copy to your MicroSD, stick MicroSD Card into TF101
3: Boot to TWRP Recovery by powering off the TF, then pressing and holding Power & Volume Down until the white text appears at the top of the screen, then quickly hit Volume Up once
4: Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
5: Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
6: When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
7: Once GAPPS have completed installing (Ignore any messages about failing to mount partitions etc) WIPE Cache and Dalvik Cache (Might ask you immediately after flashing Gapps, if not, do it from the WIPE menu
8: Choose REBOOT > SYSTEM or POWER OFF > REBOOT
9: All being well, you are now running the KatKiss ROM
---
TIPS:
When using Easyflasher, you're gonna need to install the "Universal Naked Drivers" from the Easyflasher thread - use a 32bit Windows 7 for least chance of any problems, 64bit windows requires driver signing, and so do all versions of Windows 8.x, you can use 8.x but you'll need to disable driver signing mode before installing them
---
Any problems, reply here and I`ll check every now and then

ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?

CRAP!!! The main reason I updated this tablet was in the hopes to fix the twitter issue... that is, when trying to post a new tweet, the app crash and restart...
SAME issue!
Any tips on this one would be wonderful.

It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!

SimonFiliatrault said:
ok here's the detail steps I did...
1) I have a TF101, B60... S/N, thus SBK1 (what ever that means!)
2) Using this thread: http://forum.xda-developers.com/showthread.php?t=1688012
- Need APX Drivers: http://forum.xda-developers.com/showthread.php?t=1514942
Found those instructions that partially work:
http://forum.xda-developers.com/showthread.php?t=1514942&page=4
Search in the start menu for Device Manager and open it.
Plug in your tablet via USB while in APX mode (hold power button and volume (+) until the screen turns off).
The driver should try to automatically install off the tablet upon plugging it in to your computer.
If it fails to install, you will have an "Unknown Devices" section in Device Manager.
Right click on Unknown Devices and hit update driver.
Then hit manually install driver. Point the file browser to the root folder of the extracted package that you downloaded.
For clarification: You downloaded the zip in the OP called Universal_Naked_Driver_0.72.zip.
When you extract it, you should get something like Universal Naked Driver 0.72 or something like that.
Point that file browser to the newly extracted folder, NOT the subfolders.
If you point it to the amd64 or the i386 subfolders it will not work. Hope this helps you out!
That is partly true... here's what I did:
1. power button + volume up
2. device manager showed "other devices" - APX
3. right-click APX and update driver
4. point to extracted naked driver folder
5. Cannot install - hash not present issue!
6. Found this how-to on installing unsigned drivers: http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/
- Cannot find the control panel advanced startup menu!!!
Found those that work! http://pcsupport.about.com/od/windows-8/a/open-advanced-startup-options-windows-8.htm
Method 2: PC Settings
Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
Tap or click on Settings.
Tap or click on Change PC settings at the bottom of the charms bar.
Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
Choose Recovery.
Locate Advanced startup, at the bottom of the list of options on your right.
Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
After reboot, I could install the Asus Transformer APX interface.
downloaded easy flasher: http://yarr.ntg.cx/pub/EasyFlasher-0.8.3b-STABLE.zip
extracted and started with SBK1
Choose TWRP 2.2.1 and clicked flash
Tablet need to be in APX mode (power + volume up)
click flash and ok
Saw this on easy flash:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
Saw this on tablet:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxx
!!! phone update success !!!
!!! phone update success !!!
Copying those file to root of flash drive
- KatKiss-4.4.4_032b.zip
- gapps-KatKiss-4.4.4_20140720.zip
- fsync_on.zip
3) Booted to TWRP Recovery
1. Pressing and holding Power & Volume Down
2. when white text appears at the top of the screen, then quickly hit Volume Up once
Now we see the TWRP!
4) Goto the WIPE menu, and wipe everything apart from External Storage (This will 100% wipe your TF, so if you have anything you want to keep, back it up, you can also make a Nandroid backup inside of TWRP, so make sure your MicroSD Card has enough room if you choose that)
- cache
- Dalvik cache
- Factory reset
- System
- Internal storage
- Format data
FAILED!
Unable to format data
5) Once everything is wiped, goto the INSTALL menu and install KatKiss ROM you copied to the MicroSD Card (Might have to select External from the INSTALL menu to navigate to the MicroSD Card)
- Choose katkiss rom
KatKiss-4.4.4_032b.zip
- clicked home
6) When the ROM says it is completed the install, go back to the INSTALL menu and install the GAPPS you also copied to the MicroSD Card
- gapps-KatKiss-4.4.4_20140720.zip
- Home
7) Also installed fsync_on.zip
- This is optional to have more speed, but can cause data loss if tablet reboot
8) WIPE Cache and Dalvik Cache
9) Reboot - System
- Should see the new OS start - with the dog and colored circles!
10) After a short minute... you will get the welcome and setup screen
- Do standard setup!
Tablet is up and running... NICE!
Thanks a LOT!
Will now re-install my stuff and test... will keep you posted.
Do this detailed how-to exist somewhere?
Click to expand...
Click to collapse
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.

706
Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
Unsure what you are referring to?
1) Rooting the TF101
2) Fixing Twitter issue
As you see in the thread, I have successfully installed 4.4.4 KatKiss.

barkeater said:
I am essentially trying to do this although I have a C20 so I use SBK2 in Easy Flash. However, after I do my wipes, then go to flash my rom, I get an error message that it can't open the zip file What is strange is that I have done this before and have had KK installed on my tablet.
Click to expand...
Click to collapse
Did you make sure the zip on the flash drive are ok? Did you try to open them on a PC?

Found a solution for twitter! Simply installed which is better! TWEEDLE

Razor64 said:
It's easy.
First root it. Rooting has a few basic common steps. just get the files right.
Then install the rom in recovery!
Voila!
Click to expand...
Click to collapse
KatKiss is already rooted!
SimonFiliatrault said:
Found a solution for twitter! Simply installed which is better! TWEEDLE
Click to expand...
Click to collapse
Great pleased you managed to get it working in the end, you can now update TWRP to either the latest official 2.3.2.3 or the unofficial which has been taken over by another member, that's possibly why you ended up with the DATA failing to wipe
Twitter works ok for me, but there are 2 different types of KatKiss, there is the normal one which has a speed increase, and the NonLinaro version which has much better compatibility with apps
Its possible twitter is not liking the Linaro version (Normal one)
Anyway, you are set to flash whichever ROMs you like now you have TWRP, but Id advise updating to 2.3.2.3 to avoid issues, that's the version Ive been running since it was released
Oh and SBK1 and 2 mean, Secure Boot Key, SBK1 was leaked and therefore very easy to flash recovery and other stuff to that required the key, SBK2 did not leak, so devs had to find workarounds in order to flash recovery

Wow Simon.
Already so much.
By the way you sound like a pro already
Now just follow what *detection* says.
That Rom is fast and smooth.
Verstuurd vanaf mijn SM-G900F met Tapatalk

I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon

SimonFiliatrault said:
I now want to update again since I have some issue with wifi disconnecting and would like to have original Twitter app working.
So here's a couple of questions:
1. TWRP... before I used EasyFlasher that have TWRP 2.2.1
- I did not find easy flasher with TWRP 2.3.2.3 what do you recommend to use to update TWRP? Link please.
2. You said Twitter work for you and you installed the NonLinaro... right?
- I would be using this link: http://forum.xda-developers.com/showthread.php?t=2592890
That's good?
Any other tips, new version since you last post?
Thanks,
Simon
Click to expand...
Click to collapse
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)

*Detection* said:
I can help you with 2.3.2.3 TWRP
Code:
https://mega.co.nz/#!0MFjWR5L!Xsf2b83h54I97z5Zsp_1PUn6mDHi6itZIc2GGoFkAeI
This Easyflasher has 2.3.2.3 updated inside (Credit to Frederuco)
Click to expand...
Click to collapse
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?

SimonFiliatrault said:
Ok... Downloaded this new version and ran it:
Running Wheelie..
>Tablet is now ready for Nvflash
Flashing twrp.SOS
>Finished, now reboot into recovery!
on the tablet, I see the !!!!! phone update success!!!! 2 time
Trying now to get in "recovery mode"...
Tried simple reboot in recovery from KatKiss, does not work.
Ideas?
Click to expand...
Click to collapse
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery

*Detection* said:
Did you reboot fully into KK before trying to get into recovery after flashing 2.3.2.3?
You need flash 2.3.2.3 > reboot fully into KK to complete the install > then reboot into recovery
Also you can try powering off the TF, then hold Vol down and Power until you see the white text at the top of the screen, then release all buttons and quickly tap Vol up to enter recovery
Click to expand...
Click to collapse
After first attempt, yes I entered KK then did reboot in recovery and did not work.
I have tried many time to do power with vol down and vol up... I see "cold-booting linux"... then KK, not recovery mode
I started another thread for this, not sure where the best place to discuss this is?