[UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery

[Sk8er Boi]

It currently flashes over your boot partition and updates your system partition. User data is not affected.



[IMAGES] HMJ37 (USA WiFi 3.1)



What does it say on Settings | About tablet? Looking for Android version, Kernel version, and Build number.

Android Version
3.1

Kernel Version
2.6.36.3-gc2bee64
[email protected] #1

Build Number
HMJ37

 

[stachre]

Android Version
3.1

Kernel Version
2.6.36.3-gc2bee64
[email protected] #1

Build Number
HMJ37

Through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?

 

[Sk8er Boi]

Through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?

sorry i'm a linux noob what the commands i need to input in terminal to " look at " /system/build.prop

 

[stachre]

sorry i'm a linux noob what the commands i need to input in terminal to " look at " /system/build.prop

cat /system/build.prop

 

[dew.man]

what method works to root 3.1 that still allows this update? the common wifi-root-3.1 update includes sd support etc and causes the asert fail.

 

[mr_delphi]

what method works to root 3.1 that still allows this update? the common wifi-root-3.1 update includes sd support etc and causes the asert fail.

me too

fstab is said to be different, because wifi-root-3.1 contains another fstab

who has the original version?

 

[Sk8er Boi]

cat /system/build.prop

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37
ro.build.version.incremental=124251
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Sat May  7 02:22:32 PDT 2011
ro.build.date.utc=1304760152
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-7.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=stingray
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=trygon-user 3.1 HMJ37 124251 release-keys
ro.build.fingerprint=verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
persist.ril.mux.noofchannels=8
persist.ril.modem.mode=1
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
ro.telephony.default_network=4

# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072

# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-verizon
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
ro.setupwizard.mode=OPTIONAL
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

$

 

[stachre]

ro.build.fingerprint=verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys

Bingo. You've got something other than stock 3.1 HMJ37 going on there. If you want to use this to upgrade to 3.2, you need to flash the stock 3.1 system.img, then reconfigure su and Superuser.apk. Link in the OP.

EDIT: I'm working on including all the SU stuff in the update.zip. v04 coming sometime this evening.

 

[Sk8er Boi]

strange the thread i used to update from 3.0 said it is a stock anyway i think i will wait for the update i don't wanna miss around and lose my data witch happened on my last update

thanks for your hard work

 

[killakrishook3r]

Bingo. You've got something other than stock 3.1 HMJ37 going on there. If you want to use this to upgrade to 3.2, you need to flash the stock 3.1 system.img, then reconfigure su and Superuser.apk. Link in the OP.

EDIT: I'm working on including all the SU stuff in the update.zip. v04 coming sometime this evening.

3.1 stock in OP still gives me an error

 

[stachre]

3.1 stock in OP still gives me an error

Through a terminal or ADB, look at /system/build.prop
What's the value for ro.build.fingerprint?

 

[Jaredsk74]

File flashes fine on stock. It's once you root that things get messed up. I am on 3.2 now, but unrooted. Will I be able to just flash over with the new update.zip once you add SU to it? Or will I have to reset back to stock first?

 

[texasez]

Is this working for anyone?

 

[stachre]

File flashes fine on stock. It's once you root that things get messed up. I am on 3.2 now, but unrooted. Will I be able to just flash over with the new update.zip once you add SU to it? Or will I have to reset back to stock first?

Back to stock, unfortunately. The update patches the stock 3.1 system partition; hence the zip is a relatively small file.

 

[solarnz]

FYI: I'll have a complete update for this later, I.E you will be able to flash from any rom / kernel, as long as you have updated to 3.1

 

[mr_delphi]

File flashes fine on stock. It's once you root that things get messed up. I am on 3.2 now, but unrooted. Will I be able to just flash over with the new update.zip once you add SU to it? Or will I have to reset back to stock first?

U can just adb push su and superuser

I did this

Uk xoom. Flashed stock us 3.1. Flash update v3. Adb push su and superuser. Now all good

 

[ChadH42]

I can't seem to find the v.3 download. Anyone have a link or mirror??

Sent from my Xoom using Tapatalk

 

[stachre]

I can't seem to find the v.3 download. Anyone have a link or mirror??

[*]You've downloaded the modded Xoom Wi-Fi Android 3.2 update v03 (thanks to kurt5510 for the original OTA, thanks to solarnz for the rooted stock boot.img)

note, however, i'm uploading v04 right now, superuser included.

 

[i_am_the_one]

worked great for me using v03

 

[bpick]

Here's what I did to get it going.

Use fastboot to flash the system.img file from here:http://forum.xda-developers.com/showthread.php?t=1080963&page=2

Copy the system.img to your adb folder (typically tools).

Next extract the su.zip attached to this post. Copy the files inside (su and Superuser.apk) into your adb tools directory where you just put system.img

Run these commands in adb.

adb reboot bootloader



Doh ! V4 is on its way up. Oh well.

##wait until you see fastboot protocol support on the screen of your Xoom

then run:

fastboot flash system system.img

## When complete

fastboot reboot

When it reboots, boot into recovery. From here you can now install the update.zip you created in the OP. If it is there, flash away.

apply update from sd card

install update.zip from SD........

If not download the 3.2 update from the OP and rename it to update.zip. Move it to you sd card. You can just mount the SD to your computer by selecting Mounts&Storage > mount USB storage. When copied Unmount. Select Go Back and apply the update.

Back out and reboot.

Let Android boot. Ensure usb debugging is connected. Open a command prompt if it's not still open and cd to your adb tools directory.

then run:

adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb reboot

Once you reboot you are now fully rooted, if you get a failure at the remount then you have a permissions problem. Start over.

##NOTE: If you have issues with Superuser not working correctly you can go into the market and re-install it or update it.

##NOTE If you get an error creating the symlink with:
adb shell ln -s /system/bin/su /system/xbin/su

run the following command:

adb shell rm /system/bin/su /system/xbin/su

then run the command to create the link.

adb shell ln -s /system/bin/su /system/xbin/su

You can also test root by running:

adb shell
su


If you get a prompt and it reports su, your good.