Re: Sprint Mogul HTC 6800 (problem)
I apologize for the mistake; being new to this board and not knowing how to navigate or post anything correctly played a big part in the mishap. I appreciate your kindness and value your knowledge as well as everyone here, I am glad I found Wckediden.
Unfortunately I still can't get the "SPL" to update from 1.20... Keep in mind I can't operate my mogul through the software (Windows Mobile) it gets stuck on the first screen where you have to go through alignment. Doesn't connect through sync so anything that is needed to correct the SPL using sync is not capable since it doesn't recognize the mogul. I can use (the only way the pc will recognize mogul) power, camera and reset feature to access the four colored screen; this is all I can do. I already used "Hard-SPL-MFG" on the four colored screen and it passes 100% on errors but fails to update SPL leaving me (no change) with SPL-1.20 Olipro only. Here what I get when I try and update (power, camera, reset and using micro sd) the rom higher than 3.xx...
00018003
TITAIMG.nbh - FAIL
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
OS -
Update Terminate
UPDATE FAIL
On Rom this is what I get after updating to 2.17 keeping in mind I am unable to use any software feature (Windows Mobile) to access any settings or connecting both devices (pc and mogul) through sync. Touch screen fails to respond like it was intended to any touch (finger or stylus) and I can't get passed the alignment screen. Here's the boot screen message...
"HTC Logo"
M 09 No Radio
B 03 C 2.17
Maybe I should give up already, a voice within is starting to say "your mogul is no good". I really liked my mogul; it’s a shame to see it not functioning the way it was designed to. Please will someone help me with the situation I'm going through? Be honest with me and tell me like it is... if it's no good just say it, I've already put too much time trying. I need to know whether or not I got a bricked mogul... because that's exactly what it seems to be at the moment.
Thanks again TweetyBear..!
|