View Single Post
  #14 (permalink)  
Old 02-17-2009, 12:49 AM
Old Faithful's Avatar
Old Faithful
N00b
Offline
Threadstarter
 
Join Date: Jan 2009
Posts: 47
Reputation: 20
Old Faithful is just getting started
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: No Service after ugrading ROM HTC Touch

Quote:
Originally Posted by detroit_doug View Post
my only thought is why do you keep attempting to drop down to .40?
If I don't, I can't get it back to the original OEM boot loader. In other words, I've bneen trying with great effort to revert to the original carrier ROM so that i could re-run the carrfier EXE and hopefully solve my problem. (whenever i run the carrier EXE now, i get RUU error 320 or 328, invalid command, and the RUU qjuits)

If I run the OEM nbh file from the SD card with the 2.31 loader is installed, upon reboot the loader hasn't bee overwritten, it's still Coke 2.31. The only way I could get it back to the original boot loader was to load the 0.40 Coke, which can be overwritten. However when i did that, although everything appeared to get back to OEM, the phone radio got killed.

In other words, I simply can't go back to OEM at all, no matter what I tried. The OEM EXE, whcih contains all these custom things, simply won't run anynore

I sure wish ImCokeMan would have a look at this and help, I'm at my wits 's ends

Are you supposed to be able to simply run then carrier exe once unlocked and get back to OEM condition? I sure haven't been able to!!!

To sum it up: no matter what, I simply haven't been able to revert the phone to is OEM setting (3.08.666 ROM, august 2008, with 3.42.50 radio) in its original condition. Unlocking the phone, in essence, made it impossible for me to go back... And trying to killed the radio...

Quote:
Originally Posted by detroit_doug View Post
unlock it to the 2.xx or whatever and then follow the steps to get it up and running...

Detroit Doug
It was the first thing I did after I tried that custom ROM, but ever since the phone was unlocked, I haven't been able to run the Carrier EXE, the only way i got it to work the first time was to extract the nbh file from the carrier exe, load that on an SD card and put it in b oot loader mode. But that did not relaod all the other stuff that the carrier exe does to setup gthe phone properly.

The idea behind using the 0.40 unlocker was to get it in a state where it wold accept the OEM loader, I thought that it would make it close enough to the original conditionm that the carrier EXE would finally run normally, but it didn't

My last hope is finding a way to run the carrier exe without getting an RUU 320 or 328 error. At bthis time whenever i try that, the phone rebots while itg's being detected, the USB connetion gets cut off ans satrted a few times, it just can't work.

Running the exact same RUU contained in custom roms, no problem whatsoever. The problem appears only when I try to run the carrier EXE. The hidden loader that runs when you run the carrier exe first decompresses rhe nbh and other files, the problem happens after that when it tries to recognize th phone. the problem app seems to be "PPSTPatch.exe", which doesn't exiosty in custom ROMs. But I'm sure it's essentiel to the proper setup of the phone, since there are TWO nbh files a, a cab file and that exe on top of the well known RUU.

Am I the only one with this problem? has anyone with Bell tried to revert to OEM after unlocking? That's the question!