Tuesday, July 10, 2012

HTC Raider LTE ICS (Ice Cream Sandwich) Update goes to white HTC Screen


HTC Raider LTE ICS (Ice Cream Sandwich) Update goes to white HTC Screen

notes:
- phone is a Rogers HTC Raider LTE
- I cellular unlocked / carrier unlocked the phone months ago before this
- I HTC Dev unlocked the phone
- The phone is S-ON / Security-ON still, as I haven't S-OFF'd it yet

I went to do the Rogers ICS 4.03 update that was finally released on July 7th.

- downloaded the update over wifi
- initiated the ICS update
- during the update, the phone showed a download/progress bar several times in between reboots (at least 4 or 5 reboots, and new progress bars)
- it seemed to be stuck on a white HTC screen
- after waiting about 30 minutes for the update to finish (while still on the white HTC screen), I finally pulled the battery
- tried booting the phone several times
- started researching on the net
- came to the conclusion that I should try re-locking it first
- installed HTC Sync for this phone (including all 4 pieces of software and drivers that it suggested), no reboot of the desktop was necessary
- installed Android SDK
- second stage of Android SDK prompted to install the 4.1 (API 16) kit, I didn't install this, instead, I made sure to pick and install the following from the SDK Manager:
  - Under Tools: Android SDK Tools
  - Under Tools: Android SDK Platform-tools
  - Under Extras: Google USB Driver
- once again, no reboot of the desktop was required
- plugged my HTC Raider into USB on my computer
- held-down VOLUME-DOWN button while pressing and holding the POWER button until I saw something on the screen (should be HTC boot menu for Fastboot, Recovery, Factory Wipe, etc, etc)
- after it finished loading (it tries to run any updates on the internal (or SD?) flash cards first, I then chose the FASTBOOT option
- I opened a command prompt in windows (right-clicked and ran as administrator)
- ran "cd \Program files (x86)\android\android-sdk\platform-tools" to change to the correct directory where my android SDK tools were installed
- then ran "fastboot oem lock" which returned with:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.115s

- I then either powered off the phone or it rebooted, I don't remember
- I then held-down VOLUME-DOWN button while pressing and holding the POWER button until I saw something on the screen (should be HTC boot menu for Fastboot, Recovery, Factory Wipe, etc, etc)
- this time I chose Recovery.. I should have just booted it normally instead, I don't think I needed to choose recovery, but I'm including it here for completeness
- it then continued to show a black screen with a small phone and three green arrows (2 arrows circling another green arrow), and a progress bar
- I continued to watch it (the phone was still plugged into my computer USB cable)
- it got to the end of the progress bar, and sat there, I got a little impatient and was googling while I was waiting, and someone had suggested (on another phone model) that during their update when it stopped on a similar screen, they unplugged their USB cable from the phone, and it continued on, so I did the same, I don't know that it really needed to be unplugged... your mileage may vary, maybe having just waited a littler longer, it might have continued on anyways.
- the phone continued to reboot
- it eventually started showing a more light-green/bluey colored arrows (the first hint that the ICS upgrade is continuing!! yay!)
- it continued to do this for a bit, and eventually got to a new screen saying it was updating components or packages (I forget the exact words)
- it eventually finished updating and I was able to use the phone again
- I had one touchwiz (I think) crash fairly quickly after the update.. but everything has been alright since then (these touchwiz crashes were common when I was using/reorganizing my Producteev todo lists, so I can always try that again and see if I have more crashes)

Anyways... maybe this will help some people out.