yashsingh1/xdaforums huggingface dataset:
[Xoom General] scramer:
Thanks your post was not there when I started typing lol. I found it and moved the file.
[Xoom General] Alxoom33:
I just got it, on Morey 2.2.1 I'll wait for team Tiamat.:cool:
[Xoom General] Zammo76:
Damn the notification has come back an hour after deleting the zip file stored in the cache folder.:mad:
[Xoom General] grenness:
Don't know if it is of interest, but here's the OTA file.

I received it OTA today, on my Tiamat US Xoom Wifi, but here in Norway :-)

(so it doesn't seem to matter whether your (US) Wifi Xoom is stock or not, or where in the world you happen to be)

Christopher
[Xoom General] Lothaen:
I got it this morning - no idea what it includes - bootloader went on fine too - UK xoom -> US image (no root)
[Xoom General] rohit3192:
received update.

so far tablet seems secure.

will see if now it is more faster
[Xoom General] albion01:
My guess is that this update fixes the stock browser's trust of DigiNotar and other hacked CAs.

Anyway, on to my problem.

I am running a rooted stock 3.2 image. I got the update notification this morning. I started it, my Xoom rebooted into recovery and tried to patch with a zip file (the same one linked in this thread). After about 30 seconds I got an error. I should have written it down, but I didn't. Now when I go into "About Tablet" it displays HTJ85B for the build Number and System Update says "You system is currently up to date". Any ideas?
[Xoom General] tikiral:
Similar situation here. I've been running Tiamat Katana for a long time and had actually done all my backing up yesterday in preparation for upgrading to the latest Tiamat today so I figured, "Hell, why not?". When it restarted it simply gave me the Android guy / Exclamation point error image. I force restarted (power + vol up) and the updates say "up to date" even when manually checking, kernel still says katana and my build number is still htj85b (as opposed to the htk55d update build).

System seems to be running fine.
[Xoom General] playya:
Brave man... see no real reason to risk anything like that. Tiamat will make a superior rom to stock so why even risk it... Just My Opinion
[Xoom General] DarkTharen:
This update could be in preparation for Ice Cream Sandwich. Just a thought
[Xoom General] SMRPOWER:
The only improvement i noticed was on Youtube, it loads videos faster on HD at home, i was unable to see a 720p video without stops on my 3mb internet, now its fluid.
[Xoom General] Alxoom33:
Thanks for being on top this. Do you think it will it work with the rooted 3.2.1 image that you posted a while back? I flashed it this morning and than tried to accept the update and my wifi did not connect. Not sure if the update took since the xoom did not reboot into recovery, but the update notice went away.????:confused:

I then loaded my nandroid of morey 2.2.1 and all is well, except for nnyoing periodic update notices.
[Xoom General] playya:
well said except for the part where we are all now getting the update but still well said. I seen this type of stuff go on everytime the Evo came out with an update. FYI - The questions that keep getting asked over and over are more your preference than somewhere here answering. You should think about what your typing and thinking about doing and see if it sounds a lil crazy to you before expressing here....lol - IMHO

Hmm - Should I unroot so I can root again? Really

I agree patience is the best thing to have in this situation. Good things come to those who wait... Also what else do you have to do?

Stock - Upgrade and enjoy

Rooted - Don't upgrade unless you don't like being rooted anymore.
[Xoom General] zone23:
My only thoughts on this are "save you breath" and "waste of time". BTW Xoom Zone got notification of an available update.. just saying..
[Xoom General] BiGMERF:
gotit this morning.. Xoom running a lot better than it was with the last update. No freezing, so far
[Xoom General] BigBadBuddy:
We're you on a stock rom? Did you have to re-root or restore data?

I have not been able to read everything, but want to make sure that this is a simple update only.
[Xoom General] double1:
Just installed 3.2.1. Took long time to startup at first.

1. The annoying popup that would ask you what program you want to open a link with appears to be gone. I would always get a popup asking which browser I wanted to open a link with and even if I click set to default it would still always ask me. This update appears to fix that.

I have a problem when I click a link the screen becomes dim and does not go to the link and then i tap the screen again and the dimness goes away. I can only open some links by longpressing and say open in background tab.
[Xoom General] GReddySetGO:
I've had this happen to me too. When you try to open a link and the screen gets dim, you're getting a pop-up notification, its just not visible for some reason. When the screen is dim, try changing the orientation(if you are in landscape rotate the tablet to portrait or portrait to landscape), I have noticed this will then allow the pop-up to be seen. If this is happening to you while clicking a link its most likely just asking you what browser you want to use to open the link. ;) hope this helped!
[Xoom General] tonemand:
Ditto that. The file is definitely gone, but the script, requesting to run the update (assume it is running in memory), keeps nagging. I am tempted to reboot the device to get it to clear, but Murphy's Law is strong with me, and the file would be redundant somewhere else and the update would install on reboot.

Anyone delete the file (on a rooted Wi-Fi) and either get the update prompt to go away or reboot to have it gone? I don't have to reboot yet, but would like to know some nasty unpleasantness isn't hiding, waiting to strike!
[Xoom General] rootfan:
This update is extremely small. It is not even quite two megabytes. If it updates the bootloader I would guess that is the only thing it does. Go to stock get the update,unlock,flash cwm, and reinstall moray. It will say it is the previous android version of course, but you will have your shiny new apparently more secure bootloader:D

Edit:

While the update notification is annoying, it is in no way dangerous, and is not going to destroy your device when it is off. All of these updates have a script in them to check your system to make sure it is the appropriate one. If it tries to install the script will kill the process before anything is flashed.

Hey everybody, you can look this up on the internet, but i thought i would write it here so everybody knows. Thanks to solarnz's excellent work, you can get root on this update via his universal root tool. Already did it, and it works like a charm.Also it is safe to flash the tiamat tachi kernel, and it works perfectly.

Thanks solarnz, my xoom would be nothing without you and your team :-)

P.S. if any of this information helped you please press the thanks button.
[Xoom General] Sistema1927:
I deleted the file, rebooted, and still have the stupid update nag. :mad:

UPDATE: Modpack3 in the Moray thread fixed the problem. :D
[Xoom General] airbillion:
Can we extract the bootloader and flash it separately? If I remember correctly I think brd did this with the update to 3.2.
[Xoom General] ntron1:
If it has not been posted....The update was a minor security update from Google according to Motorola.
[Xoom General] double1:
Nope. Chuck Testa the rotating the screen didn't work. I think the site I'm usig is trolling me. :D
[Xoom General] kenfly:
Hey its working!

NOPE!

Its Chuck Testa
[Xoom General] Yazan76:
Have you managed to flash CWM on stock 3.2.1 ? Whenever I try flashing CWM on 3.2.1 I always get the android guy with an exclamation mark after rebooting into recovery, although the flashing process completes successfully.This never happened with me on 3.2
[Xoom General] mrschmitz:
This update is more than just a bootloader update. There are a ton of patches to the system apps as well. Without a changelog we won't know, but it is more for sure.

Here is the difference in the build.prop file that the updater-script is looking for, to verify:

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2/HTJ85B/140714:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.2.1/HTK55D/180627:user/release-keys");
[Xoom General] tonemand:
Ok, thanks. Gotta see if it is compatible with Hammerhead 2.1, which it may be, cause both are Team Tiamat offerings, but are different ROMs.
[Xoom General] tonemand:
UPDATE: Those on Hammerhead (like I was) can update (no wipe) to Moray and then pick up the Mod Pack 3 update (in the Moray thread) as suggested by Sistema1927.

Works awesome, and I was able to retain my red theme as well. A win-win for me today!

Thanks Sistema1927!
[Xoom General] mingiunate:
does anyone know if this update fixes the chrome bookmark sync issue with the browser?

thx
[Xoom General] mrschmitz:
I just built an 3.2.1 update.zip file that can be flashed directly over stock and rooted 3.2 from CWM 3.2.0.0, and it seems to have worked.

It doesn't update the kernel module for wireless or boot loader stuff, just the Android system files/frameworks/apks.

I'm now updated to 3.2.1, still rooted, still with the Tiamat kernel and overclocked, just with the goodies that matter. I'll test it a bit and maybe post it later this weekend.
[Xoom General] shakuyi:
excellent news thanks for the update!!!!! still no word on what changed huh?
[Xoom General] mrschmitz:
Nothing official that I've heard, no. Although when you break apart the update, in addition to the bootloader and recovery updates, there a ton of binary patches to the system APK files, frameworks, and libs, including a wifi driver update (that wouldn't be included if you change kernels).
[Xoom General] flexor224:
Hope it works! Im really sick of the nagging update window. I also let me daughter play around with it . Just dont want thing getting messed up in the wrong hands Been running the Tiamat Kernel with it rooted for a long time now! Keep us posted.
[Xoom General] mrschmitz:
So far it is working fine. Although the permissions on the su binary were messed up, but that was easily fixed by applying the universal root patch.
[Xoom General] tincbtrar:
This would be a great addition to us Stock Rom users. Eagerly waiting here.

Thank you very much in advance.
[Xoom General] mrschmitz:
I can give out a link to a patch .zip that works if you have never changed anything in /system (including renaming or deleting any system apk files) if you like? I cannot provide any form of support at this time.

This patch would not touch your kernel, boot image, or recovery. It does check against the current system to verify what it is patching, so if anything doesn't match up, it bails before any modifications are made.

Want the alpha version? Remember, I won't be able to answer emails or anything tonight about it...but with the patch verifications it should be pretty safe.
[Xoom General] tincbtrar:
I would love it. If it isnt patching boot image or CWR a nandroid should be able to restore properly anyway.

I dont mind being a guinea pig. Worst case scenario...reinstall image.

Did you get to update your bootloader as well?
[Xoom General] mrschmitz:
Nope, no bootloader update in this, I ripped that out of it. I didn't want to risk messing with CWR or anything. All this does is update your Android system files to 3.2.1. I also made a new version (v0.2) that I'm hoping lets you stay rooted without re-applying the universal root patch, but can't test it.

And yes, if you make a backup in CWR first, you should be able to restore that just fine if you have any issues. Here goes:

*** USE AT YOUR OWN RISK, EXPERIMENTAL! ***

*** MAKE A BACKUP IN CWM FIRST! ***

*** DON'T BE DUMB! ***

*** I CANNOT SUPPORT THESE RIGHT NOW! ***

(*** MAKE A BACKUP IN CWM FIRST! ***)

(Known) Requirements: STOCK and ROOTED Honeycomb 3.2, WIFI XOOM (U.S.)

Updates to: Honeycomb 3.2.1 android system (minus wifi driver update patch, boot loader update patch, and recovery update patch)

Does not touch: To reiterate, this DOES NOT touch your kernel/drivers, boot loader, or recovery.

Download and flash with Clockwork recovery:

HC3.2.1_stock_root_update_v0.2.zip to update from STOCK and ROOTED WIFI 3.2 to 3.2.1 with experimental change to hopefully stay rooted.

* If the above .zip succeeds and you have root access still, you are done.

* If you DO NOT have root after the above .zip succeeds to flash, use the Xoom-Universal-Root.zip (download: Xoom-Universal-Root.zip)

* THEN you should be good to go.

* IF the above 3.2.1 .zip bails before it updates anything for some reason, flash the following two .zip files in Clockwork recovery, IN THE ORDER LISTED:

1. 1st: HC3.2.1_stock_update_v0.1.zip

2. 2nd: Xoom-Universal-Root.zip

GOOD LUCK! (don't yell at me if you mess up your xoom) (I can't answer questions about this tonight!)
[Xoom General] tincbtrar:
Ill give this a shot in a few. It just started raining here in Vegas (anomaly) while I was about to change my transmission fluid. Oh well.

Did your original patch fix up the bootloader and the drivers? Id be willing to test that as well.

Ill report back results. Seems like a harmless update.zip as long as we know what we are doing.

Edit : Couldnt the Wifi Module be inserted and loaded at startup? On my old Incredible I had some experience with auto-loading modules via script at boot.

Does this update the build.prop as well?

I really couldnt care less about the bootloader or recovery updates.

---------- Post added at 01:30 PM ---------- Previous post was at 01:00 PM ----------

I tried to use the patch but it aborted. I wanted to see if your script really does check for modified .apks and it does :)

Ill do some further testing.
[Xoom General] tincbtrar:
So...after playing around I can confirm that it does update.

However, I had to reinstall CWR and lost my backups.

I dont know what happened...but its ok because after going to my Stock nandroid from when I first got my Xoom I was able to flash your file. And then I re-Rooted the device.

I have some data recovery work to do...but nothing serious. Its a fresh restart with 3.2.1!

Edit : Everything came back on its on. Weird.

Thanks again!
[Xoom General] tomtreas:
Beautiful job mrschmitz! I had, in one of my weaker moments, told the new OTA to 'go ahead' on my rooted xoom. It did nothing at all but then stopped nagging me about said update. I still wanted to bump this up to HTK55D so when I saw you'd posted this I decided to try it. I backed up the rom in CWMR as advised and then rebooted back into CWMR again and applied the zip after having move it to the sdcard folder (internal memory) on the unit. It flashed in flawlessly and I have verified that my system now says HTK55D and 3.2.1 and also that my rootedness is intact, in fact!

TYVM!
[Xoom General] mrschmitz:
Um...let me see if I can answer what I think you didn't already for yourself. :-)

- None of my 3.2.1 update .zip files touch the bootloader or the recovery. However, when i was searching around, I saw that there is a recovery script hanging around in the /system directory by default, but I don't know what it is for.

- I stripped out the update of the wifi driver, which is already a module, because when you use a different kernel, like the tiamat kernel, it is replaced anyway (since the kernel modules must be built against the running kernel)

- Yes, the build.prop is updated to 3.2.1, so you can't have made any changes to that file either, or the script will bail before changing anything.

- You lost your CWR? That surprises me, since my modified update scripts don't touch the recovery or bootloader...I wonder if it has something to do with that recovery script in /system. Or did you NOT lose your CWR? I was confused with the responses. :-)

---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------

Great news! Enjoy.
[Xoom General] tincbtrar:
It was fun playing around yesterday with this patch, lol.

I don't think your patch had anything to do with my losing CWR. I checked it like 3 times before install.

Sorry about all the questions. Just looking to learn a bit more. You rock!
[Xoom General] mrschmitz:
Whew! And no worries about the questions. Hope it helps people out.
[Xoom General] JRd1st:
Wow! This patch worked PERFECTLY! Thanks!
[Xoom General] tincbtrar:
Anyone else wifi wacky after update? Can someone upload the wifi driver from update so I can play with it?
[Xoom General] Chipster0:
Took the plunge. Reverted boot, system, and recovery to pure stock. Allowed the full OTA update - bootloader and all. Re-rooted via universal root after flashing Rogue recovery 111.

All OK. Updated wpa_supplicant. Threw caution to wind and CWM Rogue kernel 131.

Appears this new bootloader plays nice with 3.2 kernels.

Finally.. added my battery tweaks and desktop UA to framework. All Ok for 12 hours so far.
[Xoom General] tincbtrar:
Thats odd. Are you sure the update went through? When I tried to flash the Rogue Kernel on 3.2.1 it wouldnt let me - stating that the script didnt detect a 3.1, 3.2 or 3.2.2 ROM.

Maybe because you are using Rogue Recovery?
[Xoom General] mrschmitz:
My WiFi seems to be the same as it was before. The only thing I'm having issues with is the "WiFi disconnect policy" won't reliably stay on "never," but that was happening before the update.

If you are using a non-stock kernel, I don't think the wifi module will work, but can't hurt to try. Somebody who updated stock will just have to give you the .ko module to test out.
[Xoom General] buzzdroidx:
whoa whoa whoaaa bro

oops post deleted by me
[Xoom General] tincbtrar:
That is what is happening to me as well...but it just started now. Of course, nothing to do with your update.zip but probably another issue somewhere else.

Any stockers around that can post that module?
[Xoom General] mrschmitz:
I *think* it started happening to me when I started using the Tiamat kernel, but it could have been before that even, if I didn't notice it...don't know.
[Xoom General] Chipster0:
Sorry. Had to edit the Updater script in the kernel zip.. to recognize 321 and treat as 32. Details.. details..
[Xoom General] jaa93997:
another success

I too had success updating to HTK55D and still rooted. Wifi MZ604 also with tachi stock gpu kernel :cool:
[Xoom General] tincbtrar:
Figured as much..but it has been a while since I have used a Tiamat kernel anyway so I went with it.
[Xoom General] Lothaen:
did 3.2.1 add in 'other' keyboard support?

i.e. UK layout? I seem to have a £ on mine now (after fiddling) but not sure if that was there before or not... I was sure it wasn't with 3.2, it definitely wasn't with 3.1...

Does it work with the external BT keyboards anyone know?
[Xoom General] ssmithri:
With the patched file? My attempts result in installation aborted with mrschmitz file.
[Xoom General] mrschmitz:
Update patch from rooted HTK55d to HTK75d

Hey all,

If you were able to update your stock and rooted system to HTK55D with my previous update flashable .zip file, you should also be able to use this one to update to HTK75D.

** THIS WILL ONLY WORK IF YOU ARE ON HTK55D STOCK, (U.S. only?) WIFI **

1. It SHOULD keep you rooted (it did for me, because I modified it to retain correct perms on the su binary)

2. It will NOT update your boot image, boot loader, kernel, or recovery.

3. It WILL update you FROM HTK55D -> HTK75D, with all the android system goodies.

4. It will NOT work if you have removed/modified any individual file in /system. ADDing to /system is ok.

5. It WILL perform checks on your current system before it modifies anything to make sure the patches apply correctly. It is merely a CWR flashable, but neutered, version of the official HTK75D update that came out today.

6. I don't really have a lot of time to support this, but it was a simple thing to make, but I will be able to answer some questions.

7. DO THIS AT YOUR OWN RISK! (but remember it checks the files it will patch first and doesn't touch any of the boot/kernel/etc., so it's pretty safe)

8. MAKE A BACKUP

9. Love potion.

Make it this far? Download it: HTK55D_to_HTK75D_keep_root-v0.1.zip
[Xoom General] aslsthlm:
Thanks, worked like a charm :-)
[Xoom General] tincbtrar:
Do you know if the bootloader or kernel were updated or was it just minor stuff.
[Xoom General] mrschmitz:
They were not updated, it was just minor stuff.

Well, "minor" if you mean just a bunch of small patches to the frameworks and system APKs, but no boot loader or kernel/driver modifications.
[Xoom General] jaa93997:
Yes it works! you the man!, from HTK55D to HTK75D, still HC 3.2.1, still on tachi kernel, still with root, and the new market. Pretty cool. Thanks are in order of course.....
[Xoom General] Yazan76:
Thank you a lot. You saved me the trouble of flashing back to stock. I think you need to put this update in a new thread to make it more visible to the people looking for it.
[Xoom General] mrschmitz:
I have thought about that, I just don't have a lot of time to support it. Still, I might...
[Xoom General] Tiger62651:
Ok having troubles. Doing file check and says error on applicationsprovider.apk and cant even update to HTK55D. Tried both ways to update and both give same error. Figured something not checking right with the file. Running moray and tachi kernel. I made my own theme but didnt touch this file. Any ideas?
[Xoom General] mrschmitz:
Isn't moray a ROM? My patch won't work on that if so, just stock with a diffent kernel and bootloader...
[Xoom General] Tiger62651:
Ah ok makes sense now. Just have to wait for another release of the rom.
[Xoom General] bitbitbit:
I was on stock rooted 3.2 and I used mrschmitz's scripts to update to HTK55D to 75D. Everything seems to work fine, except when I plug the Xoom into my computer, it doesn't show up anymore in Windows Explorer. I need to enable USB debugging before it shows up. Anyone else experiencing this?
[Xoom General] tangiers:
I am on stock wifi US with Tiamat kernel.

When I try to install the zip files, I get a status 7 error on both scripts (v. 02 and v 0.1) when trying to upgrade from 3.2?
[Xoom General] mrschmitz:
Does it say which assert is failing? If you modified any of the files it is patching, including build.prop, the patches won't work.

---------- Post added at 10:04 AM ---------- Previous post was at 09:13 AM ----------

FYI -- I figured out what was going on with my wifi disconnect policy refusing to stick on "never." I was using an app called "teradesk" to access files between phone/tablet/computer, and it does some funky stuff to jack with the wifi status, I guess. Anyway, I uninstalled it on a hunch yeterday, and have seen the wifi disconnect policy stay on "never" ever since.

So, long story short -- I don't think the wifi module is the problem, I think we both may have an app that jacks with the wifi policies somehow, and I managed to find the culprit on my XOOM. Good luck!
[GT540 Optimus General] DarkCaine:
Guys, i really like the swiftdroid ROMs but they are all battery drainers.And i cant be at home all day or at work and charge my GT540 all day. Seriously it isnt alive more than 1 day.So want to learn which rom is the best battery saving.
[GT540 Optimus General] Man_u:
try 2.1 Rom ,they have a good battery life
[GT540 Optimus General] jhonnyx1000:
It all depends on the conditions. Swiftdroid does use more battery life. Try to go for something lite.
[GT540 Optimus General] -Grift-:
2.3 is power hungry and very fast, 2.1 has very good battery life but not so fast

so..... 2.2!!!!!! stable fast good battery life!

i recommend project utopia
[GT540 Optimus General] tejasjadhav:
Get Utopia. You'll get the speed of 2.3 and battery of 2.1!
[GT540 Optimus General] androidboss7:
Yeah but Utopia doesn't have all the

features!!
[GT540 Optimus General] bataya:
^like?

Sent using Tt.
[GT540 Optimus General] androidboss7:
My GT540 lasts at the longest 3days

and at the shortest one day!! :):)

Using cyan 2.3.5
[GT540 Optimus General] jhonnyx1000:
My device only lasts for 3 hours of continuous use. Using Swiftdroid v1.9 RC4.
[GT540 Optimus General] pwned686:
i use swiftdroid v2.0 Asis

And it has very good battery life .

On my damaged battery it handles one day