OTA_Ville_U_TMOUS_1.84.531.2-1.53.531.16_release_2651973pm4j0bopq68v1g1.zip

---

Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.

Do not flash this .zip, it's for developmental purposes. I just made it available because I received the OTA on my phone this morning and did not see it posted yet.


https://docs.google.com/open?id=0B3Q...XpZcVR2M2NlQUU

Here's an alternative link if the above one fails or is too busy

http://db.tt/lLyptM9n

Sent from my HTC VLE_U using XDA

Originally Posted by ozzie1p

Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.


https://docs.google.com/open?id=0B3Q...XpZcVR2M2NlQUU

Epic thank you sir

You guys rock!!!

EDIT: Sorry that sounded really NEWBish... I am unrooted and am currently having an issue re-unlocking my bootloader to root.

Is there an RUU available that I might be able to flash?

I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think

Originally Posted by Cayniarb

** this assumes that you have adb and fastboot in your PATH and that you know how to use them.

** this also assumes that you have some recovery.img file (named as such) saved in whatever directory you are running terminal commands from.

** this also assumes you are running linux. If all of the above conditions are met, the process should also be the same on Windows and OS X, but I have not tested that and cannot confirm that.

** this assumes that if you do not fully comprehend all of the above, that you will stop reading now. I am not responsible for any damage caused to your device by following these instructions.

Step 1: Find and download the following images from the 1.78.41.2 RUU: radio.img, wcnss.img, and adsp.img. Save them on your device's storage partition (/sdcard) named as listed here (** this assumes that if you use other names you also know how to adjust future commands).

Step 2: Boot your device into fastboot mode. Your choice of 'adb reboot bootloader' or manually powering down, booting to hboot, and selecting fastboot. (Future commands assume your device is plugged in to the computer at this point)

Step 3: On the computer, run: fastboot boot recovery.img

Step 4: Wait for your device to boot in to what looks like a normal recovery session. While it looks this way, it is not normal. In this recovery, you have the ability to do pretty much everything you can on an s-OFF device (flashing boot or other partitions, etc).

Step 5: This will depend on your recovery. Whatever the process is, make sure that your /sdcard partition is mounted (not mounting USB, but making the /sdcard partition readable to things like adb).

Step 6: On the computer, run:
adb shell
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/wcnss.img of=/dev/block/mmcblk0p19
dd if=/sdcard/adsp.img of=/dev/block/mmcblk0p18

Step 7: In the same recovery session, on the device, flash whatever 1.78-based ROM you like (Note: I have not seen ill effects using this on a 1.53-based ROM, but YMMV).

Step 8: Reboot. Enjoy.

This is from the radio thread i would assume, that it will work the same way. All those files are included in the OTA zip file. Thoughts?

Originally Posted by ozzie1p

I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think

Right now I just want to get my damn bootloader unlocked and I cant seem to figure out what is going on with it. I've done this a million times so its not that I dont know what im doing like all the others have accused me of, its simply an issue that the unlock token flashes fine but upon rebooting the bootloader is still relocked. Its driving me mad right now... I just want to flash an T-Mo RUU to get back to stock at this point.

go to the official ruu thread by football and download the tmous ruu from there... put your phone into fastboot usb mode and start the ruu.

Will that RUU overwrite a newer H-Boot?