Mogul stuck in reboot loop
 

I've been searching around for a couple of days and haven't found any help regarding my problem. I have a Sprint Mogul that I flashed with the new 3.16.651.0 ROM and the newer Hard-SPL (2.40, I think?). However, that ROM was too buggy for me, so I wanted to switch back to the official Sprint 2.17 ROM. I tried to flash the 2.17 ROM back on to the phone with the 2.40 SPL in place, but it wouldn't work. So I used the relocker to get rid of the Olipro and ImCoKeMaN SPL. Now, when I go to bootloader, it says:

TITA100
SPL 1.07.0000

I can now flash the official ROM back on to the phone and it looks like it's successful. However, after resetting, it just keeps rebooting. The initial HTC screen comes up for about 1 second, and then the phone resets. I've reflashed the phone about 5 times now with this same ROM, soft reset and hard reset more times than I can count, and it still does this. I've removed the microSD card like some posts have mentioned and that didn't work. Also, after some research, I found another post that mentioned the user just let the phone reboot about 20 times and the phone eventually booted up just fine. I tried that. I left my phone to reboot continuously for about 20 minutes, which equates to about 200 reboots. The phone is still stuck. I tried flashing the 3.16.651.0 ROM back but I get the same thing.

Anyone have any ideas? Is there a way to do a complete low-level flash of the bootloader and ROM and ext. ROM? I can't change the bootloader as it is right now because the Hard-SPL and the Relocker both require ActiveSync connections, which I obviously can't do. I'd like to get this thing completely back to stock. Are there any utilities out there that will allow me to force flash everything?

Thanks in advance!

Matt

use SD card.
rename signed_RUU.nbh with TITAIMG.nbh, copy to SD,
insert SD card, put in bootload mode (power+camera+reset).

When it reboots does it stay up long enough to show you the revision numbers for everything? I am curious if the old radio took during your update... If you have the 2.17 ROM and the newer radio still, you will have issues (though I am not sure if these are the exact symptoms you would experience)

Also, activesync is NOT actually required for any of this to work in Windows. As long as you are at the bootloader screen the NOID RUU should allow you to flash to the device. I do it all the time using Vista, well I used to at least anyway... the SDcard method is much easier so I do almost all my flashing that way now.

Re: Mogul stuck in reboot loop
 

The phone doesn't stay up long enough to see any version numbers. As soon as the first Sprint splash screen pops up, it reboots.

I went in to my local Sprint store and they're ordering a new one for me.

Re: Mogul stuck in reboot loop
 

A new one? Lucky you, Last Friday I was told by a salesman @ the Sprint kios @ a local mall in MD, that the Mogul have been discontinued as of Feb. Don't know if there's any truth to this, but he had a Mogul in his possesion that he refused to sell to me because of this.

Re: Mogul stuck in reboot loop
 

Having the same problem.
I've tried to load the ROM from the mem card using the method described above.... and it just takes me back to the three color screen each time. Never changes.

Thoughts?

Re: Mogul stuck in reboot loop
 

I had the same problem on a stock , non-flashed mogul..in fact it was one that was given to me by sprint to replace the one that wasnt working because of a bad power connector...

so it kept in a looping reboot...it would stop and load correctly every once in a while, then after an hour or so..whammo! back again..

just picked upthe new replacement which works fine...

thank god for TEP