[HTC Vivid, Raider, Velocity] GSLEON3:
Edited in blue font on 3/24/2012 @ 9:11PM

FYI:

WARNING!

Several people have had serious issues in updating to ICS while using a custom rom/recovery. I hate seeing bricked devices & if you were an early user of the custom recovery, there was an overwrite flaw that can cause serious issues when updating using ruu's & other factory firmware such as OTA's.

While this has been used by many & is the safest way to update, I do not know what changes you have made to your device/firmware. As always, anything custom is used at your own risk, that said I believe this is the safest way to update to ICS particularly for those that have not changed their recovery since the first release or two. Theire are detailed instructions to help you minimize the risk involved with updating an unlocked device.

Before updating to ICS, make sure you have a newer version of Recovery. One of the first recoveries released could not be overwritten without first flashing another moddified factory recovery first. Updating your device firmware with the older non-writable recovery will stop the device from reflashing the needed files after the first reboot & may cause other issues for some users.

If you try to update to ICS using this recovery you will get BSOD, boot loop or worse, qshsub_dload. All of these are fixable, but the last is still being worked on & as of this time requires jtag/riff to recover from.

If you're using a custom recovery that is older, take note of version & try to flash newer recovery. If recovery fails to be updated, then you are using a flawed recovery & need to flash two files before updating to ICS.

I highly recommend fastboot flashing to the attached recovery before updating your device. This recovery has many features & is more current than the release in the thread. You will have to re-install the recovery again after using the PH39img ICS update, which changes your SBL, Radio & other component firmware required to run ICS.

If you want to use the stock OTA, it is recommended that you return to stock recovery & relock your device using ADB/Fastboot. To flash stock ruu or OTA, you must relock your device. It can be unlcoked using the unlock bin file again from HTCDev.

The command to relock you device is "fastboot oem lock"

This info is in particular for AT&T customers.

The absolute safest way to update to ICS is to relock your device & return it to as close to stock as you can get it. Relocked you can flash the leaked GB AT&T rom in football's thread. Once complete, you can now download a final RUU from the HTC website at: http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe

Using the stock GB recovery & firmware in conjunction with the new RUU is probably the best way to ensure a safe flash since you are then using firmware tested by HTC on devices & made to work together. We have know for some time that locking the device is temporary & unlocking it again can be acheived in many cases with your original unlock_code.bin, or by simply obtaining a new unlock_code.bin after registering/logging in to the htcdev.com website.

The next safest way to update is to return to GB & the stock recovery, relock your device & receive the OTA update. But for those that want to live in the fast lane, lol, this is the method that I & several hundred others have used without incident.

I am posting a link that includes many tools & a custom recovery that I highly recommend. Take note of the information in the Instructions.txt to have a safe ICS upgrade experience.

The recovery included is CWM based recovery. The only difference is it adds some touch support & correct Nand backup abilitiy as well as some nice tools available in newer versions. If you are NOT familiar with flashing via fastboot, all you have to do is extract the zip to the any folder & double click the batch (.bat) files & they will automatically write the recovery or whatever boot.img you select. The recovery script is only for the WCX version of CWM though. Just make sure you extract the files to a folder on your PC that does not have any spaces in the naming. That means if your pc is named Joe Smith-PC, you cannot use the Documents folder or any library folders, so I suggest using C: or create a new folder in c: without space, i.e. C:/Android

The wcxrecovery is CWM based, just more recent, updated with full nand backup support & capacitive button support. All of the files have been safely used & tested extensively by WCX, his rom team & his beta testers. The recovery is also compatible with all of the custom roms (GB & ICS) that I have played with. These items are for users & not to be cooked into public roms without permission of Wild Child. I posted it here due to all of the requests for help I have gotten over the last several days & the amount of time it was costing with one on one support.

If you choose to use the All-In-One tool located Here: http://xdaforums.com/showthread.php?t=1498003 to unlock your device again & still want to use the newer wcx recovery in my zip, you can simply navigate to the /data/recovery folder for the all-in-one kit & replace the recovery included there with the wcxrecovery.img & then copy the existing recovery name (should be recovery-cwm-vivid-5.5.0.4B2.img) delete the file recovery-cwm-vivid-5.5.0.4B2.img, & rename the wcxrecovery.img to recovery-cwm-vivid-5.5.0.4B2.img. You can then use the all in one tool to unlock & flash the new recovery, albeit a few more steps than just using the batch file I included.

Thank you to the developers & owners of the included firmware/tools for allowing users to safely update custom roms to ICS. Please do not Donate to me for any of these items, I merely packaged together the work of others & wrote a pair of scripts to make things easier.

http://www.mediafire.com/?n4x2pcn1jw0g206