View Single Post
  #1 (permalink)  
Old 02-16-2009, 04:47 PM
Old Faithful's Avatar
Old Faithful
N00b
Offline
 
Join Date: Jan 2009
Posts: 47
Reputation: 20
Old Faithful is just getting started
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Major problems after unlocking - questions about Imcokemans's unlockers!

hey folks,

As you may know I'm experiencing a major problem with my HTC Touch (Bell Mobility, CDMA), in the fact that after unlocking it I cannot revert back to the OEM ROM through its EXE, whichb has more than just a VOGUIMG.nbh, and since reloading through the SD card, I've had major problems, after a couple times, now my phone radio won't turn on.

My question is mostly for ImCokeMan, but feel free to chime in.

First, I've read everything very carefully about unlocking and basically learned the procedure in detail before doing so.

I bought my device in december 2008 and ran the carrier exe update successfully in early january, basically upgrading to the 3.42.50 radio and WinCE 6.1 in the process. I then tried all kinds of programs, some with success, some without, like you can imagine. Basically until then my phone was working fine.

Two weeks ago I decided to try a custom ROM, so I used the 2.31 unlocker as I should, with all background apps killed, antivirus, firewall....

What surprised me at the time, but did not really stay with me, was how the unlocker operated: at the end, it's supposed to run an "exit bootloader" program, however, after that the phone rebooted by itself without my intervention, so I followed the instructions on that screen and let the customizations run. Remember, we're talking only Bell Mobility ROMs here.

After I unlocked it to 2.31, I ran the RUU with the custom ROM and it loaded and ran without problems.

Well, I dind't really like that custom ROM so I decided to revert to the OEM carrier EXE. This time, I couldn't: got an RUU 328 error at the start! So I extracted the VOGUIMG.nbh from the EXE, installed that on my fat 32 SD card, reinsterted it ointo the ohine, went into boot loader mode and let that run, which worked fine.

I had no major problems at this point, except that I noticed very minor loss of signal at some times, and noticed that I was losing data connections on large downloads. But most of the time, my signal strength was just as fine as before.

So yesterday I tried unlocking to the 0.40 loader, so as to allow a full OEM EXE reinstall, to lock it again, which, I tought, would make the phone completely clean again as it was before I attenmpted this unlocking process.

This time as well, after running the unlocker, the device rebooted itself at the end of the 0.40 loader run and asked me to align the screen like before, after which it reloaded all the customizations.

I then tried running the carrier exe again, but still no joy, so I reloaded the VOGUIMG.nbh from the SD card again, which worked, except that now, I have NO SERVICE.

I am starting to worry that I should not have let the customizations run, even with no changes in the radio itself. Did I do it wrong? Did I kill my device? I can still get in boot loader mode no problem, that's for sure. But I cannot run the OEM carrier EXE from WMDC, and I wonder if that is not the stumbling block, as the exe contains not only the not only the ROM file, but another nbh (Special_4350_For_BM.nbh) and a cab file as well (PPST____.CAB), a prl file, PPSTPatch.exe, among others.

By running the OEM nbh file only, was something not loaded, ending in an incomplete flash? Any suggestions as to what to do next?

Any help welcome!!!