Yes userdata will wipe...you can try without but may bootloop.do i need to flash the user image? wont that wipe all current apps?
Sent from my PG86100
Yes userdata will wipe...you can try without but may bootloop.do i need to flash the user image? wont that wipe all current apps?
You would need to flash the official 3.0.1 from my other sticky post.OK, got my Moto Xoom today, updated to 3.2 and rooted it (which of course required unlock and new boot). Problem is, I have a dead spot...was broken in shipping I guess. Since these are unofficial, what can I do to get back to an official image (3.1 for example) so I can unlock? Thanks so much guys
Any reason why 3.1 won't work? Can I damage by trying?You would need to flash the official 3.0.1 from my other sticky post.
Sent from my PG86100
Cause you need official images for locking...you can try, but will most likely softbrick. I tried 3 times with the official update, and softbricked all three timesAny reason why 3.1 won't work? Can I damage by trying?
Thanks that worked beautifullyCause you need official images for locking...you can try, but will most likely softbrick. I tried 3 times with the official update, and softbricked all three times
Sent from my PG86100
Almost...just skip step 2. There is no reason to root the os, that you are going to replace. Unlock, Load stock/wipe, DO NOT LOCK...you could root at this point if you want. Now i can't promise the stock Japanese images will work on a USA xoom though. Worst case, you softbrick and i can get you out of thatBwcorvus,
Thanks for all your work. I want to pick up a xoom for my inlaws in Japan. I stopped by Staples today and they had it onsale for $399 after coupon. However, when I messed with it, I noticed that the rom was 3.2 instead of 3.1. Can you give me the steps to install the Japanese Stock Image (In Laws can only read Japanese and I need the Japanese Market, etc). I have been doing some reading today, and please let me know if this is right.
1. Unlock the bootloader
2. Root the Xoom
3. Use the Android SDK and load the Japanese Stock
4. DO NOT LOCK the bootloader at the end
Please let me know since we are leaving for Japan soon and I don't want to make the purchase without the expert opinion, thanks so much.
If you want to oem lock, you need to grab the stock ones from the other tread.OP, what do you recommend I do if I want to restore to stock and do an oem lock?
I'm currently rooted running, 3.2.
1) Can I run the 3.0 factory images from your other thread? OEM lock that way and manually update back to 3.2.
or
2) Use your 3.2 images and do everything but oem lock and then use the 3.0 images to oem lock.
Thanks in advance.
Thanks, last question. So I can go from 3.2 back to 3.0 using those images with no problem. Thanks again.If you want to oem lock, you need to grab the stock ones from the other tread.
CorrectThanks, last question. So I can go from 3.2 back to 3.0 using those images with no problem. Thanks again.
NO...You need the 3.1 bootloader. If you have 3.1 you can use the 3.2 images to upgrade.I have the 3.0 that came factory in my Xoom, can I put this image Direct 3.1? And then to 3.2?![]()
As long as you have the 3.1 update, you should be fine with 3.2 images.Hello, thank you all for sharing, I wanted to ask, I have installed 3.1 on my OTA update mz604 Xoom LATAM wifi, I can flash the image directly to RDS 3.2 Without problems?.
Thank you very much!.
If you use the images here, no you can not lock. If you want to lock you have to pull the stock images from my other sticky. Flash the stock images, lock, then update via the OTA.I am on 3.2 rooted. Can I downgrade to 3.1 using the link on the OP for 3.1 then upgrade to 3.2 using OTA on the xoom. will this automatically unroot the xoom and lock it again. Or can I manually lock it after the OTA 3.2 updtade. I want my xoom to be completely stock again with no modifications whatsoever. Thanks
If you use the images here, no you can not lock. If you want to lock you have to pull the stock images from my other sticky. Flash the stock images, lock, then update via the OTA.