Database Info

[Q] Convert a U.S. Zoom Wifi into Japanese?

I have the backwards problem here. I am trying to bring the xoom to Japan as a present for the In-Laws. I can pick up the Xoom wifi in the U.S. for around $399, but the In-Laws and only read Japanese. Could I convert the U.S. version to Japanese (need much more than just the language settings, need the icons and the Japanese market, etc)? Thanks for all your help.

Go over to the Moto Dev site and download the stock wifi image for Japan, flash using the instructions on the site. There you go, your US Xoom is now a Japanese Xoom. Oh and don't relock the bootloader.

Seriously, that would be amazing, thanks so much.
I have flashed different kernels and roms on my cellphone but never done this before. Can you please answer the following questions when you get a chance.
1. Do I need to root the xoom?
2. Do I need to download clockword mod recovery?
3. Can I do all of this via terminal manager (type in the commands for flashing), the instructions on the site only has these lines... Where do I type this stuff or should I unzip the Japan kddi.zip file?
Instructions to Flash & Re-Lock Your Motorola XOOM:
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
Thanks so much for your help again!!!

calculus1918 said:
Seriously, that would be amazing, thanks so much.
I have flashed different kernels and roms on my cellphone but never done this before. Can you please answer the following questions when you get a chance.
1. Do I need to root the xoom?
2. Do I need to download clockword mod recovery?
3. Can I do all of this via terminal manager (type in the commands for flashing), the instructions on the site only has these lines... Where do I type this stuff or should I unzip the Japan kddi.zip file?
Instructions to Flash & Re-Lock Your Motorola XOOM:
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
Thanks so much for your help again!!!
Click to expand...
Click to collapse
He said: "Oh and don't relock the bootloader."

1. no root needed
2. no cwm needed.
3. u need adb and fastboot, motodrivers, latest sdk, official images from motorola
i think there is a thread here in XDA, for non US xooms flashing US image. just look for it.
Sent from my HTC Desire using XDA Premium App

As above.
Follow OP's post in this thread to unlock the Xoom.
Then download the Japanese image, flash using the instructions you posted above from a command prompt in Windows.
Important: ignore the last command on the Moto site. You do not want to lock the bootloader. Locking the bootloader when you're running a different image than intended on the device may brick your Xoom.

[Q] [solved] Can a stock ROM 3.2 be rooted at all?

Hey all,
I read through quite a few threads here and am a bit confused.
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) a good while ago.
Recently, I got interested into rooting the device. So I launched the recovery mode on my Xoom (just to see if it works before I start flashing anything) and sadly, I get the green bot of ! there.
edit: solution in this thread!
So for now:
From my understanding here, there's only one way to fix this using ADB:
1) unlock bootloader
2) flash stock xoom dev rom (that would be H.6.1-38-1)
3) flash cwm
4) root
Even if all these steps were correct, wouldn't that mean I can impossibly OTA update to 3.2 as the device is already rooted (read somewhere it will cause issues when trying to update a rooted device)?
Even if I updated via OTA anyway it would overwrite CWM, wouldn't it?
I'd prefer to have a latest stock ROM + root as end result without a green bot interfering. Any advice is appreciated!

If I'm not mistaken you can root your device, using one of the Universal Root Tools on xda's xoom android development section.
I also rooted mine, using Xoot, I think it was called. Which will convert it into a GED device (wifi-only)
Or you can use Lord AIO's tool, which also worked fine, and then you can flash Team Eos' 2.0 Umts-everest (EU 3G) ROM over it.
Both have worked well for me.
Good luck! And let me know if you have any questions left!

found this that would do the trick for sure. As always, you're not the only one
Originally Posted by okantomi
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse

reference post: CWM + rooting issue solved here (no downgrading was needed):
http://forum.xda-developers.com/showthread.php?p=25998728

[Q] Xoom on wrong baseband [SOLVED]

Hi,
i use a international version of motorola xoom mz601 in india and have updated to android 3.1 and use the latest baseband n_01.83.35p. my stupidity changed the seeting to USA band
after this band changed to USA band 800Mhz? i cannot use any network 2G or 3G and the motorola doesn't show any network operators.
i really want to revert back the settings.now how can i downgrade my baseband and what commands i need to execute also i have tried moving to stock 3.0.1 but no change in baseband.
any apk file that would help me change the band?
thank you.
Please help
Solution: Backup everything in external sd as everything in internal memory will be erased by the proceeds
1)Download and keep the instructions from (be sure to check your exact model no)https://developer.motorola.com/products/software/
2)extract all the zip contents to android sdk folder otherwise download it from Android sdk
3)Fully charge your device
4)Power off your device.
5)While holding the volume down button, press the power button for about 1 second and release the power button. The device will power-up and display AP Fastboot Flash Mode. At this point you can release the volume down button.
6)Attach your device to your computer with a USB cable and install the Motorola Device Drivers.
7)INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
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(Remember this will relock your xoom although you can unlock afterwards)
8)Reboot and let it load
9)turn on wifi and get the OTA updates for the second update I got my 3g & 2g signal Back
10)Wish u good Luck
Sorry for Bad Bad Bad English I am uneducated

just found a little tool http://forum.xda-developers.com/showthread.php?t=1052745
called baseband switcher but thats only for motorola defy
am no hardcore developer but someone please help
also i did try to flash that using cwm but error 0 occured

You can also unlock after that and install any Custom rom you prefer

You're a life saver, thanks for this!!! I too did the same thing as you ... *#*#4636#*#* > Tablet Information > Select Radio Band ... "Oh, only USA Band is available?" ... *click* ... "Damn, Data connection is gone... knew I shouldn't have clicked that..."
Your steps to resolve fixed the issue after the baseband update ... Now, I think this all could have been much simpler if we could have just reloaded the Baseband, but I couldn't find any to download.

[Q] I think I've killed it

I have a UK Xoom WiFi (604) which I only recently bought reconditioned and it was in perfect order - you would have said it was brand new.
I also have a Galaxy S3 and S3 mini which I rooted and both are running KitKat and both are great so, I thought I would do the same with my new Xoom, and thats where the trouble started.
After some reading here on the forum, I followed this thread http://forum.xda-developers.com/showthread.php?t=2506997
I thought I had followed everything to the letter, but now I can no longer load recovery - screen just shows TWRP loading screen (the blue screen with TWRP) and the tablet freezes at this point.
When I try to load fastboot (I did successfully unlock the boot loader) I get "Starting Fastboot protocol support." and my Xoom freezes again, and when I try RDS I get "Starting RSD protocol support 3 "
Can someone help me here or have I killed it?:crying:

Fixed it - managed to get into fastboot and reinstalled factory image using adb, updated OTA once booting again and back to where I was with a fully functional Android 4.0.4 tablet - happy once again

How'd you do it?
zeb1801 said:
Fixed it - managed to get into fastboot and reinstalled factory image using adb, updated OTA once booting again and back to where I was with a fully functional Android 4.0.4 tablet - happy once again
Click to expand...
Click to collapse
Would you mind a few details? Exactly which firmware file did you use? Please post a link or PM me.
How do you use ADB from Fastboot?
I'm in the same spot with a Xoom which has lost recovery but does have fastboot and rsd. For some reason, nothing I flash to it (without error, mind you) is there after and I'm stuck at the M.
Thanks!

This is what I did - All of these instructions were done on an Windows-based PC, This is not my work - I found this info on the web.
You'll need a USB data cable, Motorola drivers, an original system image of the Xoom firmware - I got mine from this thread on here: http://forum.xda-developers.com/showthread.php?t=1049485 and part of the ADB SDK - I got this from here http://www.android.net/forum/downloading/67/guest/SDK_tools.zip - extract this zip to the root of your C: drive so the folder looks like this: C:/SDK_tools
Once you have downloaded the correct system image for your device (I used Build H.6.2-24 for Retail Europe as I have a Xoom WiFi 604) extract all the files from the zip and copy them into the SDK_tools folder, make sure they are not in a sub-folder - they should be in the same directory as the fastboot files. The directory contents should look similar to this - don't worry if its not identical - as long as your img files are there together with adb and fastboot you should be OK:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
ddms.bat
fastboot.exe
recovery.img
system.img
userdata.img
Make sure you also have the Motorola windows drivers installed.
Once you've done this turn on your Xoom and enter fastboot (power on with power button plus vol+ then after 3 seconds press Vol- till you get fastboot on screen) as long as you see "Starting fastboot protocol support" on your Xoom screen it should work. Connect your Xoom to your PC via the USB cable. Open a command prompt on your PC and cd into the SDK_tools directory. Once in there type the following commands at the C:> prompt one at a time:
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
This should completely restore your Xoom to factory and lock the bootloader. This will allow official updates to download and should get you back to original.
This worked on my UK Xoom WiFi and allowed me to install official OTA updates from Motorola. The first time I ran the above I left my Xoom unlocked but was then unable to update OTA.
I hope the above is helpful. As I've said this is not my work and was gathered together from resources on the internet. It worked for me so hopefully will work for you too - good luck and let me know how you get on.

zeb1801 said:
This is what I did - All of these instructions were done on an Windows-based PC, This is not my work - I found this info on the web.
You'll need a USB data cable, Motorola drivers, an original system image of the Xoom firmware - I got mine from this thread on here: http://forum.xda-developers.com/showthread.php?t=1049485 and part of the ADB SDK - I got this from here http://www.android.net/forum/downloading/67/guest/SDK_tools.zip - extract this zip to the root of your C: drive so the folder looks like this: C:/SDK_tools
Once you have downloaded the correct system image for your device (I used Build H.6.2-24 for Retail Europe as I have a Xoom WiFi 604) extract all the files from the zip and copy them into the SDK_tools folder, make sure they are not in a sub-folder - they should be in the same directory as the fastboot files. The directory contents should look similar to this - don't worry if its not identical - as long as your img files are there together with adb and fastboot you should be OK:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
ddms.bat
fastboot.exe
recovery.img
system.img
userdata.img
Make sure you also have the Motorola windows drivers installed.
Once you've done this turn on your Xoom and enter fastboot (power on with power button plus vol+ then after 3 seconds press Vol- till you get fastboot on screen) as long as you see "Starting fastboot protocol support" on your Xoom screen it should work. Connect your Xoom to your PC via the USB cable. Open a command prompt on your PC and cd into the SDK_tools directory. Once in there type the following commands at the C:> prompt one at a time:
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
This should completely restore your Xoom to factory and lock the bootloader. This will allow official updates to download and should get you back to original.
This worked on my UK Xoom WiFi and allowed me to install official OTA updates from Motorola. The first time I ran the above I left my Xoom unlocked but was then unable to update OTA.
I hope the above is helpful. As I've said this is not my work and was gathered together from resources on the internet. It worked for me so hopefully will work for you too - good luck and let me know how you get on.
Click to expand...
Click to collapse
OMG you are a legend you just saved my XOOM

inick73376 said:
OMG you are a legend you just saved my XOOM
Click to expand...
Click to collapse
I'm glad it worked for you

[Q] Returning to complete locked /stock from CM11 BigPart

This is my first post as I have been an avid XDA lurker but I wanted to get some community advice before I potentially brick my Xoom.
I am currently running CM11 Wingray with TWRP 2.6.3 BigPart R.A.H.05 Edition and want to unroot my Xoom, return it to stock OS / Recovery, and re-lock the bootloader. I have found many ADB tutorials in this community http://forum.xda-developers.com/showthread.php?t=1468298 as well as some youtube tutorials https://www.youtube.com/watch?v=pT8NF-_nLCo. My concern is all of the tutorials are from the pre-KitKat days and would potentially not account for the new partitions required.
So my question is, do these tutorials re-partition my Xoom just fine or will I end up bricking my device since my new partitions would no longer work with the old stock roms?
Thank you for the advice.

nrreynolds1 said:
This is my first post as I have been an avid XDA lurker but I wanted to get some community advice before I potentially brick my Xoom.
I am currently running CM11 Wingray with TWRP 2.6.3 BigPart R.A.H.05 Edition and want to unroot my Xoom, return it to stock OS / Recovery, and re-lock the bootloader. I have found many ADB tutorials in this community http://forum.xda-developers.com/showthread.php?t=1468298 as well as some youtube tutorials https://www.youtube.com/watch?v=pT8NF-_nLCo. My concern is all of the tutorials are from the pre-KitKat days and would potentially not account for the new partitions required.
So my question is, do these tutorials re-partition my Xoom just fine or will I end up bricking my device since my new partitions would no longer work with the old stock roms?
Thank you for the advice.
Click to expand...
Click to collapse
hi,
i just unroot my xoom from cm11 bigpart, this is what i have done:
1. re-partition my xoom to normal partition
http://mobility.forumsee.com/a/m/s/p12-9321-0659159--how-undo-bigpart-repartition.html
2. Then, follow this instruction
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
Click to expand...
Click to collapse
i have download official rom from xda forum, i ithink i have problem with the rom (mz601 europe), so i suggested for u to request directly from motorola support.
https://motorola-global-portal.custhelp.com/app/standalone/rom-images
thanks

I came across the same link you provided above which is what made me think about the effects of the Big Part partition structure. This route makes sense to me and I will end up following the same steps you posted.
Thank you.