[GUIDE] WiFi MZ604 Models - Change from 'your-region' image to US 3.2

Lothaen

Senior Member
Jun 4, 2010
4,078
413
0
plus.google.com
this is weird why the updates ain't coming through what I did was turn my devices wifi off overnight and the next morning I put it on and the update came through they can't of bared the IP cause people are still getting the 3.1 update ota so its working OK the only thing I can think of is do a hard reset if it don't come through.
or wait.

someone at HTC once said they have 'slots' when the slots are full you wait till the next 'day'... a bit like google+ :p

So probably all the 3.2 slots are full for the moment but in a few hours maybe they'll open up again
 

Lothaen

Senior Member
Jun 4, 2010
4,078
413
0
plus.google.com
http://android.clients.google.com/p...igned-tervigon-HTJ85B-from-HMJ37.db223b6e.zip

put on usb drive (you don't actually need to rename to update.zip)
plug in usb drive to otg (usb host cable) and into xoom
power on, but tap vol down at motorola screen
power up to select recovery
at Android (andy) with !, hold power tap vol up
Vol down to select 'apply update from USB drive'
press power
wait till finished and reboot


so the above worked for me...

this worked for me to get 3.1 -> 3.2 update without waiting for it to come down


thanks poisike and iammodo :)
 
Last edited:
  • Like
Reactions: jss42

JaroCooke

Member
Jul 13, 2011
22
5
0
I think he means the OTG USB host cable, you can probably get one over the internet. I was hoping there would be some instructions that didn't involve using the USB otg cable, but rather a connection to ta computer with the android sdk installed on it.
 

Lothaen

Senior Member
Jun 4, 2010
4,078
413
0
plus.google.com
will i lost all of my data if i do this?
no data is fine with OTA - only lose data with reflashing images (if you are on UK 3.0.1 -> US 3.0.1 for example you will lose data, but update with OTA to 3.0.1 -> 3.1 -> 3.2 will not

can u pls explain how u do it pls?

noob question: what mean plug in usb to ota?
yes sorry typo - OTA cable = OTG or host cable. my bad.

I think he means the OTG USB host cable, you can probably get one over the internet. I was hoping there would be some instructions that didn't involve using the USB otg cable, but rather a connection to ta computer with the android sdk installed on it.
afraid I had an OTG cable to hand - although I think I saw someone tried to use a laptop as an OTG cable before for mass storage? no idea how it worked out.

also I saw a post from someone who pushed the update.zip to the /sdcard/update.zip location and it auto-updated... although that might need root or su to do
 

Lothaen

Senior Member
Jun 4, 2010
4,078
413
0
plus.google.com
it just applies the update via the usb - no need to flash anything (unless you are not on the US image already, if you are you need to flash the US image then go to 3.1 and 3.2 from the US 3.0.1)

what do you have running at the moment?



by the way i fixed my typo! :)
 

Hussain Isa

Senior Member
Jul 9, 2010
106
6
0
now i got the adb to work, but now new problem..

my divece is on the starting fastboot protocol support and cmd promt is on the
c:\tools>fastboot oem unlock
<waiting for device>

how long should i wait there???
HOW did you solve it??? I tried to disconnected & reconnect but it doesn't work for me :(
 

JaroCooke

Member
Jul 13, 2011
22
5
0
Yep, I got the upgrade to 3.2 this morning, seems to work very well. Though the SD Card is not really useful, as far as I can tell. Too limited without support for its content built into apps. It does feel like a genuine improvement though, I just waited it out in the end, as I didn't have a OTG cable and it would have taken a couple of days to get one.
 

JaroCooke

Member
Jul 13, 2011
22
5
0
kill adb.exe and try again?
If that doesn't work, then I'd look at the drivers you've installed for the Xoom. I used an Ubuntu computer and I got that message all the time. While Ubuntu comes with the necessary drivers 'out of the box', it does need the device id, which I had put in improperly. It could be something similar, just caused by not having the drivers installed correctly, try reinstalling them and sending a few device queries from your terminal first.
Code:
adb devices