View Single Post
  #10 (permalink)  
Old 02-16-2009, 08:06 PM
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
As for the file "Special_4350_For_BM.nbh" Im not sure at all, Im a sprint user so I dont know what the "special" part of it is but the rest seem related to the BM (Bell Mobile) but I would look for something more generic than something "special" after all you want it to get back to working after all LOL
So I loaded that "Special 4350..." file on the SD card renaming it to VOGUIMG.nbh, like you do when your unlocker won't load from WMDC or ActiveSync, and the result was, NO RADIO and it stuck in the bell splash screen. So I presume it is a radio uninstaller, but can't be sure. No one from HTC on these forums?

Anyway after that I reloaded the Bell OEM NBH and I was back to where I was, no phone service. I then loaded the cab file that's in the OEM carrier exe, PPST____.cab, which I believe loads the PRL, still no joy.

In other words, I've tried everything included in the carrier EXE that I could figure, but still no joy.

BTW, loading the carrier ROM does NOT overwrite the 2.31 Coke loader. That is, the only way to do it is to downgrade the loader, which is what I'm about to do.

I'll keep you posted.

Quote:
Originally Posted by detroit_doug View Post
As for the double flashing, every custom ROM I install on my phones I always do twice, seems to work even better after the 2nd flash, but in your case I state to flash twice as that is how I had to do it, when I double flashed each step it finally worked for me where the single flashing in prior attempts would always seem to crap out for some reason, besides it doesnt take long per flash so it cant hurt.

Detroit Doug
Very strange. It's as if the first flash only results in a partial data write... Wouldn't that mean that the flash memory/flash memory writing process itself is defective?