Unbricking the U8665

Some may recall that my personal smartphone is an AT&T branded Huawei Fusion 2, model U8665. This past weekend I bricked that phone, but thankfully it is now up and running again.

This device has been discontinued by the manufacturer, although surplus units are still available as of today from Amazon and other vendors. It’s inexpensive but adequate for my needs and I’ve come to really like its look and feel.

After successfully rooting the device some time ago I decided this weekend to try installing a now orphaned custom build of Cyanogenmod 10.1 that was created around a year ago and posted here. Note that to date no official or unofficial image for the Fusion 2 has been posted to the Cyanogenmod site. That fact should have stopped me before I began, but for some reason I seem to have been determined to act the old fool.

Now I had already successfully re-imaged an first generation Kindle Fire (“otter”) with the 10.1.3 official stable build that went so flawlessly I found myself in a very dangerous “what, me worry?” mood.

The actually flashing of the Fusion 2 went well, except that even after applying the supplied custom baseband file, 3g still wasn’t working. This was a big disappointment because I knew it meant that Google Navigation was not going to work right when away from 802.11 wifi coverage. So I decided to roll back the change. Unfortunately I had an incomplete understanding of exactly how to recover the phone’s prior state and I was left with a “white screen of death” emblazoned with the AT&T logo.

Fortunately, someone was kind enough to post an official Huawei recovery image for the U8665 along with clear and concise step-by-step documentation on how to apply it. The thread is here:

http://forum.gsmhosting.com/vbb/f717/need-huawei-u8665-att-firmware-solved-1747972/

This is the file link:

HUAWEI_FIJI_firmware(U8665_Android_2.3_V100R001USAC07B037_USA_AT%26T_05010VXD).zip

(the .pdf documentation is included in the zip file)

It only took a few minutes to download the file, transfer it to the phone’s external sdcard and then initiate the recovery process as directed in the included documentation (the infamous “press down simultaneously on volume up and down, and then hit the power button” move — gymnastics reminiscent of the old Mac “reset the P-ROM”). Once completed, my phone rebooted into its original, just-out-of-the-box state. In essence I had a completely new phone, at least from a software standpoint.

Having gone through the rooting and re-imaging process with this phone a couple of times I have to admit that any benefits derived don’t seem to have been worth the effort. At this point I think I’ll stay on the stock firmware. I don’t think I’ll be going down that road again unless an official or unofficial Cyanogenmod hosted image becomes available, which doesn’t seem likely now that the device has been discontinued.

Many thanks to the kind soul who made this available. Saved me a world of hurt, and not a few dollars as well.

This entry was posted in Hardware, System Administration, Systems Analysis on by .

About phil

My name is Phil Lembo. In my day job I’m an enterprise IT architect for a leading distribution and services company. The rest of my time I try to maintain a semi-normal family life in the suburbs of Raleigh, NC. E-mail me at philipATlembobrothersDOTcom. The opinions expressed here are entirely my own and not those of my employers, past, present or future (except where I quote others, who will need to accept responsibility for their own rants).