View Single Post
  #180 (permalink)  
Old 02-14-2010, 07:38 PM
jfaerr's Avatar
jfaerr
Lurker
Offline
 
Join Date: Feb 2010
Posts: 4
Reputation: 0
jfaerr is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Stuck in TITAN bootloader? Read this!

Hey guys. I have searched quite a bit on this particular problem, but have only thus far found a few bandaid solutions.

Basically, when I power-cycle/reset my Vogue (WM 6.1 when the problem started happening), it only seems to want to boot into the bootloader screen. My radio is up to date at 3.42.50 and I am currently using NFSAN's latest WM6.5 build with CoKe 2.31 bootloader. I can use my phone/data connection/GPS normally when I finally do gain access.


Bandaid solution one involves pulling out my battery, plugging in the charger cord, waiting 20 min, pulling out the charger cord, putting battery back in, powering on. This will get me out of bootloader mode, but next time I power-cycle/reset, im back into bootloader mode. Very hit or miss as it doesn't always work.

Bandaid solution two involves using ImCoKeMaN's titan_exitbl.rar uni_exitbootloader program. Ive read this entire thread, and I did make sure I was disabling ActiveSync/Mobile Device Center. Only seems to work on a specific XP machine (of two I have tried it on, and never worked on my Vista machine). Again, this will get me out of bootloader, but next time I power-cycle/reset, im back into bootloader mode. Works almost every try. Sometimes it takes two or three tries, unplugging and plugging the USB cable each time.


I would just say screw it and use the above methods to keep my phone working, but if im out on the road and I get stuck in bootloader mode, I would be in trouble. Plus, it just wouldn't be very stylish to have to tether a Windows XP box to my waist just restart my phone properly each time lol.


Anyways, I have tried flashing back to the latest stock Bell ROM and the problem has persisted.

I have flashed NFSAN's latest WM6.5 build onto my phone twice using ImCoKeMaN's 2.31.CoKe Unlocker to unclock the phone twice, and the problem has persisted.


Is it possible to change a value in the device's registry, or something such as that, to incorporate ImCoKeMaN's exitbootloader?? Is there some other file I could modify to ensure it restarts normally unless I soft-reset it into the bootloader on purpose? I am at my wits end on this one guys. Any other suggestions?

Thanks in advance guys!
Reply With Quote