Database Info

Thinking about unrooting Read this first!!!! ALL MODELS

**********Please Sticky**********
(MOTOROLA HAS RELEASED ALL THE IMAGES FOR ALL COUNTRY VERSIONS OF THE XOOM RECENTLY MAKING THIS A UNIVERSAL TUTORIAL AT THIS POINT)
Listen I notice recently there is a flood of issues with the xoom using different unrooting methods. I personally will say to unroot your device just bring it back to stock images. Its the safest method with the other methods if you do not know what you are doing you will find yourself sending your device to motorola for warranty repairs.
Here is a short and sweet way to unroot your xoom. by doing this you will lose your data and information so start by backing up your stuff to a computer if you have any important things on there.
if starting fastboot is on your xoom screen open up a command prompt:
0. For those who've modified their boot splash graphic with Team Eos' Splash Screen Logo Maker make sure to restore the stock Motorola boot splash FIRST as this process doesn't touch that part of the system. (Posted by Bait-Fish *Thanks for the update*)
1. Goto: http://forum.xda-developers.com/showthread.php?t=1049485 for stock USA 3G and Wifi Images
2. download the files you need
3. extract all the img's into the tools folder
4. with the command prompt open type: cd "replace with tools directory location"
5. disconnect your xoom from your computer and shut off the xoom
6. at the prompt type: fastboot oem unlock
7. it will say waiting for device
8. now plug it into your computer and reboot into fastboot by holding the down volume button and power on
9. follow the on screen instructions and agree to everything
10. your device will reboot you will get the motorola dual core window
11. force restart device by holding volume up and pressing the power button right after the device shuts off hold the down volume button and press power button
12 you should now be in fastboot mode
13. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

Good write up. +1 for sticky if there's not something already.
Sent from my SPH-D700 using XDA Premium App

whats good about this post is that it has been fully tested by me with wifi and 3G versions of the xoom with no problems reported. This method has also fixed some RSD issues. I say some because some people have flashed wrong boot images and ruined fastboot on their xooms from seeing the desktop.

wow you would think with all the issues happening with oneclick root etc you would think this would be a highly read thread. lol.

Nice guide man.

Good to have a thread like this as I was one of those one-click rooters. Unrooted, semi-bricked and learned ADB. If you're going to play with your Xoom, at least have a general idea of ADB.

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

Thanks!
Thank you so much!
I was also a clueless one-click rooter. I'd tried everything to get rooted again. This was by far the clearest and saved my hanging around waiting for a one-click unroot solution.
Cheers

your welcome enjoy your xoom.

I already upgraded to 3.1, and I unlocked it, but I can't get CWM to work, so I can't root. Can I use this method to go back to the older HC and relock, then go back to 3.1? I bricked mine before, trying to unroot and relock (I know...I know...) I've been adb'ing like crazy trying to get CWM to work, but I feel like giving up and going back to lock, stock, no barrel.

you can if you want it wont hurt the xoom which xoom do you have wifi or 3g?

I have the wifi, running 3.1, build HMJ37

if you go back to 3.0.1 you can root it, install clockwork, then upgrade to 3.1 using clockwork method. its pretty simple. within 25-30 minutes you can be running with clockwork and 3.1 rooted.

I learned my lesson! And the forum saved me.
I did the one-click root back when I got my Xoom a couple months ago, and then when I tried un-rooting and relocking to get the 3.1 update, I bricked it (you're welcome, angel) and sent it back to Motorola. When I got it back, I tried rooting the long way, but couldn't push CWM onto it. I got lots of help and tireless support from a forum member, and finally got it unlocked, rooted, CWM'd with SD support....re-lovin' the Xoom now. And I'm glad the guy that helped me out made me re-check re-download, and redo everything just to make sure we weren't missing any steps.
I love the Xoom NOW, but when I got it back from getting fixed, I was so not happy with it being unrooted! I love to toy with stuff, and this was a real learning experience. Doing all the commands, getting the stock images, re-flashing....it was very rewarding, even though it took so long to figure out how I screwed up. (can you believe it was a usb cable that wasn't working that made it so difficult! Pushed some things, but not others....changed cables, and everything worked fine.)

Nice walk through. I don't think I'll be unrooting anytime soon but its good fyi.
Sent from my Xoom using XDA Premium App

this tutorial should be more helpful now.

dirtymindedx said:
this tutorial should be more helpful now.
Click to expand...
Click to collapse
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom

bwcorvus said:
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom
Click to expand...
Click to collapse
how do i go about doing that.

dirtymindedx said:
how do i go about doing that.
Click to expand...
Click to collapse
I would just edit line 1 to say you can get from moto at blah blah or download from blah blah so you don't have to log in.
http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

[Q] Rooting, unlocking & updating madness

Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.

Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app

If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602

Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.

Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull

I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.

Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions

wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!

Motorola Xoom MZ640 Dev Edition?

Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

maxvsmith said:
Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do:
1. Install fastboot and adb drivers on your PC. You can find instructions for that here: http://androidteen.com/setup-adb-and-fastboot-driver-with-android-sdk/
2. Reboot your Xoom into bootloader mode. To do that, turn your Xoom off. Then, power it back on. Once you see the Motorola logo, count to three at a reasonable speed and press volume down. At the upper left of the screen, you'll see some text. Press volume down until you see "fastboot mode" and press volume up.
3. Connect the Xoom to your PC via USB.
4. At a command prompt, type "fastboot devices". You should see your device listed. If you don't, then the drivers aren't installed correctly.
5. Type "fastboot oem unlock" and follow the on-screen instructions on your Xoom to unlock your bootloader. If the bootloader is already unlocked (since it's an engineering device), you will get a message in your command prompt window telling you as much. Unlocking your bootloader will wipe all data from the tablet so make sure you back up any photos, documents, music, etc. that you want before you do this!!
6. If the bootloader did need to be unlocked, it will reboot after the unlock is done. Once it reboots, perform step 2 again to get the bootloader back into fastboot mode.
7. Go to http://www.randomphantasmagoria.com/firmware/xoom/tervigon and click the link for "images" in the first row of the table (for Android 3.0.1, build HWI69). Download that file, then unzip them somewhere on your PC.
8. Go back to your command prompt and go into whatever directory you unzipped the files into.
9. Type the following commands, in order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
10. Optionally, if you want to re-lock the bootloader (unless you're going to run a custom ROM at some point, I recommend this for security purposes), type "fastboot oem lock". Follow the on-screen instructions to re-lock the bootloader. At the end of the lock process, the Xoom will reboot. Let it boot up.
11. If you choose to leave your bootloader unlocked, just type "fastboot reboot" and you'll boot up.
12. The Xoom will now boot into stock Android 3.0.1. At that point, you'll get eight separate over-the-air updates that will eventually get you all the way up to Android 4.1.2/Jelly Bean, build JZO54K.
13. Once you get the Xoom updated all the way to JZO54K, I'd do a factory reset again just to make sure everything is clear and you're starting anew.
At that point, you should be good to go. Let me know if you have any trouble.

oldblue910 said:
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do
Click to expand...
Click to collapse
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders. I already did unlock the boot loader and installed recovery and tried a bunch of roms and I'm running CM 10.1 I was nervous of trying it at first but after realizing even if it's an engineering and testing tablet it's still the MZ604 and it should be similar to the others in terms of rooting and unlocking the bootloader. And fortunately I was right.
It actually came with really cool apps that I've never seen before too. I wish I backed those up before I factory reset. I tried factory resetting it initially but I lost a few of the apps and special things and it went to a Honeycomb 3.0 I believe. The one before the SD card support.
But I'm loving this xoom now that it's on CM 10.1 and using Jellybean 4.2. Even though it's tegra 2 and not as fast as my TF300T and other tablets out there the unique design, the placement for the ports and the accessories like the HD Dock make this a very unique tablet. It was never one I intended to buy so it was really cool getting it for free. My friend has one just like mine and he's not into hacking, rooting, and customization so I might be able to get the special apps and stuff that was on it from him. But even though I've never unlocked a boot loader once I figured out how to use command prompt it was really easy to do. Thank god for youtube.

maxvsmith said:
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders.....
Click to expand...
Click to collapse
The Verizon XOOM's (MZ600/MZ602) boot loader was not locked any differently than any other Xoom (example Wifi MZ604). It is/was unlockable out of the box, and Moto had the directions on their web site.
Funny, if it says Verizon on the front, I would not expect it to be a MZ604 model, unless the previous owner flashed the Wifi only Xoom (MZ604) firmware/software onto it. Does that bar code label on its back have a model or MEID on it?

Help - Rooting My Boostmobile HTC SV 525c USA

Hi, I have been a programmer of IT applications for several years, this is my first trip into the Android zone though. The required tribal knowledge of acronyms and associated OS's and Hardware is somewhat daunting. It's like the old days when Windows ran on DOS, a lot of fun really. Well I said all that to ask a big favor. I want to get my feet wet with my HTC One SV regarding small mods that I can make, like simply putting ring tones on and taking out a few apps that I hate.
I have read and read and read. This seems to be the best forum in the world for me and my Boostmobile HTC One SV (Android 4.2.2) phone and you seem to be an enthusiast of the SV so that's why I came to you. Here's what I have done so far.
I have unlocked my phone using the HTC site and all went rather well, nice and smooth
What I want to do is
1. Get the correct software utility tools for my phone that I will need to do some minor tweaking and poking around. (Windows 7 64bit)
2. ROOT my phone
3. Make a complete (image?) backup of my phone as it is now (maybe do this before number 2 if possible?)
4. Get advice on what new upgrades I should make regarding the OS if any to get me moving
I appreciate the forum and would like to contribute at sometime in the future. Forums like this are what started me off 25+ years ago in software programming, using FIDO net and CompuServe etc.
Best Regards
Robert
Orlando Florida

You are unlocked, next step is to flash a custom recovery.
Take the recovery from second post, the cmd to flash in fastboot you will get in first post.
Boot in recovery and make a backup (its your complete system).
To get root, you need to flash this zip in recovery (after the backup is done).

I got a bit confused witht the "Secondpost/firstpost" but I think I drilled down to the correct file finally
the dos screen just sits there, nothing happens, in developer mode debug, fastboot
C:\Fastboot>fastboot flash recovery recovery.img
< waiting for device >
Got it now! Successfully rooted and backed-up using TWRP
My problem was not entering into fastboot by clicking the power button to select, somehow I overlooked that this time. I was really just stressing over the recovery file for no good reason I think. Measure twice cut once to the extreme.

Welcome to the family
Sent from my C525c using Tapatalk

Modding.MyMind said:
Welcome to the family
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Thanks, glad to be here

old.splatterhand said:
You are unlocked, next step is to flash a custom recovery.
Take the recovery from second post, the cmd to flash in fastboot you will get in first post.
Boot in recovery and make a backup (its your complete system).
To get root, you need to flash this zip in recovery (after the backup is done).
Click to expand...
Click to collapse
Do I have the correct file?
K2_CL_TWRP_2.7.1.0d_Extended.img renamed to recovery

old.splatterhand said:
Boot in recovery and make a backup (its your complete system).
To get root, you need to flash this zip in recovery (after the backup is done).
Click to expand...
Click to collapse
Where does TWRP put the backup file, and what name should I look for?

TeeRodFL said:
Where does TWRP put the backup file, and what name should I look for?
Click to expand...
Click to collapse
It should be located in your sdcard: TWRP/Backup/Serial Number of your phone/Backup files.
They will have names like system, data, cache and md5sum files.

Thanks again, I found it.