Hello all
i need some help. just finished upgrading my mogul and it keeps on rebooting after a few seconds after it reaches the today screen. i have tried dcd 2.2.4 and 2.2.6 with same results.
i believe if i keep it plugged into the computer it will stay on. any help please!??!
thanks
I just had the exact same problem. Did you load any other software after flashing the radio and rom?
Unfortunately i couldnt find a solution that involved DCD's roms. I flashed to 2.4 2.6, 1.6 new radios but nothing worked. I had to use no2chems nuerom 2.0 buld 5044 which works great, but doesnt have the verizon specifics. GPS is good and its fast. If anyone else comes up with something please let us know as i would like to have some of that software back.
this has been posted many times.
most likely you do not have the new bootloader installed.
http://forum.ppcgeeks.com/showthread.php?t=9093
go here get the 2.40 bootloader and start over
thanks for the quick responses!!
first time doing all this, but nothing to hard i think in my opinion. you just have to get over the learning curve.
i used this guide: http://forum.ppcgeeks.com/showthread.php?t=17667
which bootloader should i use if that guide led me to the wrong one?
also where can i find the other rom?
thanks for the bootloader. i will give it a shot now
2. If you are using 3.16+ code then you need either:
>>>a. The reLocker if upgrading to the unofficial carrier released rom
>>>b. the unLocker (new) 2.40 if running custom built roms
you'll learn the terms eventually....
just an FYI
do a search on here and on google FIRST if you run into problems because most likely you'll not be the first to have the issue.
but if you can't find any answers most people here will be willing to help
just verified, i am already using 2.40
also im not new to forums... i am well aware of google and search tools. these forum websites are getting annoying with spam protection that half the time when i tried doing a search, it would not complete it.
i knew i was running a stock 3.16
did you have an old custom bootloader? you need to relock it if so then run the 2.40
if its like mine then when you relock it you will lock up on the bootloader and have to do exit bootloader to get back to the splash screen where it will lock again. I even flashed back to the stock rom and it relaoded. I think it may be an glitch in the s.27 radio personally.
i went from the latest stock to custom using the guide above. is there a need to relock it or do you leave it unlocked?
if you go from stock to custom bootloader and upgrading the radio 3.27 and a DCD rom you don't need to relock it.
you only need to relock for the leaked sprint rom
did you upgrade the radio too?
yes i used titan_radio_3.27.00
when i go into boot mood i get this:
TITA100
SPL-1.20.0lipra
Click to expand...
Click to collapse
is this how it should be?
please and thank you everyone for your help!!!
that should say olipro 2.40
who is your carrier? sprint, verizon.......
my carrier is sprint
http://forum.ppcgeeks.com/showthread.php?t=9093
run the 2.40 spl and start over
okay so you want me to run the hard spl again and then dcd??? or should i do the titan radio 3.27.00 before dcd
Related
Verizo 6800
After following the rom and radio upgrade steps I relocked the phone using Titan relocker as I was instructed. Now I get the rainbow boot screen showing SPL 1.06. Now the phone won't take any other programming on the USB. The best luck I had was using the Sprint rom but that fails at 11% with an wrong provider error. The Verizon rom fails at 0%. I tried relocking again and unlocking but all attempts fail. Any help would be appreciated.
Verizo 6800
After following the rom and radio upgrade steps I relocked the phone using Titan relocker as I was instructed. Now I get the rainbow boot screen showing SPL 1.06. Now the phone won't take any other programming on the USB. The best luck I had was using the Sprint rom but that fails at 11% with an wrong provider error. The Verizon rom fails at 0%. I tried relocking again and unlocking but all attempts fail. Any help would be appreciated.
Click to expand...
Click to collapse
I would like to know WHERE you found the instructions that said to relock the phone after upgrading to a custom rom and radio.
Also please provide more information in your post...are you upgrading from verizon stock? Are you trying to flash a custom 3.0.x rom with the new 3.35.04 radio?
More Info
Upgraded from stock 2.09 to Titan 2.10 then Titan radio 3.27. All Went well then the relocker!
http://forum.ppcgeeks.com/showthread.php?t=17667&highlight=verizon+6800
"Upgrade to 3.35.651.2:
3. If running pre-3.16 code,
>a. run the relocker
(don't worry about getting out of the bootloader - tri-color screen)"
It won't get out of the tri-color bootloader and won't respond to downloads. The computer can't see the phone on the usb port.
You should ignore the name in "re-locker" You don't have to re-lock anything after flashing. Now your best bet is to run olipro's 2.40. It is the new Titan un-locker, then flash your ROM.
The problem you're having is you're trying to flash a 3.0.x rom on your phone and you have a stock bootloader that will only flash/boot verizon signed roms. I'm not sure who wrote that tutorial, but you don't have to relock anything after you unlock (unless you're trying to flash BACK to stock).
Run 2.40-olipro titan unlocker to unlock your phone again so you can run the sprint/htc update. Then cook a verizon 3.0.x rom, or flash the clean rom already cooked.
Wont work now
gcincotta said:
The problem you're having is you're trying to flash a 3.0.x rom on your phone and you have a stock bootloader that will only flash/boot verizon signed roms. I'm not sure who wrote that tutorial, but you don't have to relock anything after you unlock (unless you're trying to flash BACK to stock).
Run 2.40-olipro titan unlocker to unlock your phone again so you can run the sprint/htc update. Then cook a verizon 3.0.x rom, or flash the clean rom already cooked.
Click to expand...
Click to collapse
I do not think he is not going to be able to run 2.4 in from the bootloader screen because it is not signed by VZW. He is going to need a stock VZW RUU, run it in, then he can go forward again.
Right...i kind of assumed he knew this by me posting that 1.06 would only flash/boot signed verizon roms. I guess I shouldnt have assumed.
You need to get the stock verizon rom AND radio...flash them from the bootloader youre in. Once the stock stuff is on there...let the phone boot up. Now you can unlock with 2.4...and run the sprint update once again...and after that...a custom 3.x.x verizon rom.
Do NOT relock after!
aThanks
Where can I find a stock verizon Rom?
ftp://up.ppcgeeks.com/Titan/CarrierRoms/Verizon_Stock_ROM/VZW_Passworded_Ruu_signed/Ruu_signed.nbh
http://forum.xda-developers.com/showthread.php?t=376873
^^ if you need more info about the stock verizon rom flashing
Hello everyone i Just got a xv6800 and am trying to flash to a newer rom...However i cant seem to boot into the bootloader it just hangs at Loading.... There is nothing installed its factory rom and settings
Thx in advance
How are you attempting to load into bootloader?
The way I saw on the forums....holding power and camera button and hittig the reset..i get the tri color screen then it goes to Loading... and just sits there dosnt do anything else
Do you have a microsd card in while trying this? If so, does it contain any .nbh files on it in the root directory? If so, do you have a TITAIMG.nbh file in the root directory?
The only way the bootloader would try loading something the way you're describing is if this is the case.
I agree with gcincotta.
If you are in fact trying to flash from the SD card though, most people have reported that it won't work using an SDHC card. It needs to be a standard (non high-capacity) card.
I did have a card in it..now i took the card out and it goes to tri color in the red i get tita100 and i the white i get serial...thats all it does now
Well i got it to go to usb but now the .exe file for the 2.40 unlocker wont run on x64 systems so i guess im out of luck huh
Did you already run the unlocker? If so, you should be ready to flash a custom ROM. It is normal to be stuck in the bootloader after an unlock. Just flash away.
If the unlock did not go successfully, you will have to try again, making sure to follow directions precisely (on a 32bit system preferably, less headaches). To unlock you must be booted up into Windows Mobile. You can try the exit bootloader program from the PPCGeeks Titan Upgrade forum, or try flashing a stock ROM to get back into WM.
Edit: You can tell if the unlock was successful by looking at the SPL in the bootloader (right under TITA100 MFG). It should now say SPL-2.40.Olipro. If it does not, try the steps above to get back into Windows Mobile.
I did have a card in it..now i took the card out and it goes to tri color in the red i get tita100 and i the white i get serial...thats all it does now
Click to expand...
Click to collapse
You need to be more specific. Everyone's titan says TITA100. What SPL is installed? Post the entire contents of your screen and then we can get somewhere.
I have a new 6800 from Verizon.
software 2.09.605.8
firmware radio 1.30.60
pri ver 1.35.002
pri check 11ab822d
SPL-1.04.000
Do I need to unlock it first ?
Which unlocker do I use ? is it TitanUnlocker.exe
Then the way I read it I need to first flash the Sprint ROM 3.35.651.2
Then what ever rom I want after that.
I was able to udate to 2.52 rom...the 3.04 wasnt working correctly and it would not up date using *228..and there was no sound...i was not using the radio 3.35 because i heard people saying that it was a bad one to use...is there much difference in performace between 2.52 and the 3.04?
So I need to install Sprints 3.35.651.2 rom and not let the sprint customazations run.
Then use the unlocker 2.4
Then use DCD or No2Chem custom rom.
craig540 said:
I have a new 6800 from Verizon.
software 2.09.605.8
firmware radio 1.30.60
pri ver 1.35.002
pri check 11ab822d
SPL-1.04.000
Do I need to unlock it first ?
Which unlocker do I use ? is it TitanUnlocker.exe
Then the way I read it I need to first flash the Sprint ROM 3.35.651.2
Then what ever rom I want after that.
Click to expand...
Click to collapse
You are starting from scratch with an unlocked phone. Before rushing forwards you have some reading to do:
http://wiki.xda-developers.com/index.php?pagename=HTC_Titan
All of your answers are there.
Yes I have read many threads and think that is why I am so confussed. I upgraded from a 6700 which I had flashed to WM6 many times before.
I will follow your linked procedure.
Two questions.
Is my phone being stock and never flashed before locked or unlocked, and do i need to run Olipro 2.40 by executing Hard-SPL-MFG.exe or start with the Sprint Radio (3.35.04)
Also the tutorial says Upon its completion, press the power, camera and reset buttons to force the phone into the bootloader/SPL mode.
What will I see to let me know it is finished loading.
Thanks for your reply.
craig540 said:
Yes I have read many threads and think that is why I am so confussed. I upgraded from a 6700 which I had flashed to WM6 many times before.
I will follow your linked procedure.
Two questions.
Is my phone being stock and never flashed before locked or unlocked, and do i need to run Olipro 2.40 by executing Hard-SPL-MFG.exe or start with the Sprint Radio (3.35.04)
Also the tutorial says Upon its completion, press the power, camera and reset buttons to force the phone into the bootloader/SPL mode.
What will I see to let me know it is finished loading.
Thanks for your reply.
Click to expand...
Click to collapse
1st- update to 2.4 olipro
2nd- update sprint 3.35 rom (stop at the "tap the screen" customization screen) this gives you the radio
3rd- from customization screen start the 3.0.4 rom and flash that rom
Your phone will restart after loading and will boot into wm6.1
4th- Read untill you understand before flashing roms
After 2.4 olipro do I hit reset to let it boot up again or start the sprint rom while its still in bootloader mode
craig540 said:
After 2.4 olipro do I hit reset to let it boot up again or start the sprint rom while its still in bootloader mode
Click to expand...
Click to collapse
Does not matter, if you do it in rom it will force into bootloader anyway.
Ok up and running dcd 3.04
date 2-22-08
radio 3.35.04
I did not let sprint cutomazation run.
Tried to make a call and get message saying verizon can not authenticate and to dial #8899
Should I do that now?
Had to call VZW to get new A-Key
No GPS detected in google maps is there anything I need to do to set it up ?
Try installing VisualGPSce -- it's a good little & free diagnostics program too see GPS satellite reception.
....after seeing that running on COM4 at 4800 baud, then you should see a list of visible satellites. Now, whether or not you get a sufficient lock within the first half hour depend's upon your luck in the draw for a GPS functioning Titan -- GPS hardware-wise, not all are equal.
I saw something here about this from azclown and really want to know if it is true.
After flashing nueSPL is it possible to downgrade to other bootloaders?
I tried to run unlocker (Olipro 1.20) and it wouldn't connect right. Do I need to use relocker then load 1.20 then load stock rom. I am testing this out for another phone right now and am a little curious why this would be created so that no other bootloaders could be reloaded.
What I am realizing is that this bootloader is not such a good idea for Verizon users, being that they will not be able to revert to the stock rom (as Verizon has not released a GPS Rom yet).
Am I right here?
serfboreds said:
I saw something here about this from azclown and really want to know if it is true.
After flashing nueSPL is it possible to downgrade to other bootloaders?
I tried to run unlocker (Olipro 1.20) and it wouldn't connect right. Do I need to use relocker then load 1.20 then load stock rom. I am testing this out for another phone right now and am a little curious why this would be created so that no other bootloaders could be reloaded.
What I am realizing is that this bootloader is not such a good idea for Verizon users, being that they will not be able to revert to the stock rom (as Verizon has not released a GPS Rom yet).
Am I right here?
Click to expand...
Click to collapse
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Thanks for chiming in on this no2chem, there's a lot of good information in that post!
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Click to expand...
Click to collapse
True, I see your point about returning a complete brick. The rest is fine I guess.
Thanks!
no2chem said:
:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
Click to expand...
Click to collapse
now, by that do you mean they werere were bricked by downgrading the radio with nueSPL previously (or currently) loaded on the device, or downgrading the radio on a device that never had nueSPL loaded on it?
the only reason i ask this is because ive done several radio downgrades from olipro 2.4 to 1.2 to the stock radio/ROMs for refurbishment and ive never had a problem. i dont use the stock SPL because theres no tech around here smart enough to check it.
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Click to expand...
Click to collapse
No2chem.. I think I am an exception or my XV6800 must be special because I actually messed up my phone because i wanted the new Radio 3.42.02 but couldn't get my Phone to Flash From SD.. So I had to flash a sprint 3.56 ROM to get the Radio and then flashed Verizon kitchen before Sprint customization started.. but for some weird reason.. Sprint customization still ran after i flash the Verizon ROM.. My EPST Settings were all Sprint.. lols..
These are the steps I took to bring it back..
1. Ran Titan_Relocker to relock SPL from version 2.40 Olipro
2. Flashed Stock Verizon ROM and let Verizon Customization run
3. Unlock using NueSPL2.47 letting it format my SD card to enable Flashing from SD [Thank GOD you added this feature]
4. Placed the new Radio 3.42.30 onto my SD card and enter Bootloader and Flashed it [Thanks to You]
5. then flashed my Verizon kitchen.. All with no problem..
I've discussed this method with some of the guys over at PPCKitchen.org and they were concerned about me bricking my phone.. but I said oh what the heck.. my phone is already messed up..
every one was supprised that it worked.. lol.. I must be one of the lucky few..
b16daddy said:
No2chem.. I think I am an exception or my XV6800 must be special because I actually messed up my phone because i wanted the new Radio 3.42.02 but couldn't get my Phone to Flash From SD.. So I had to flash a sprint 3.56 ROM to get the Radio and then flashed Verizon kitchen before Sprint customization started.. but for some weird reason.. Sprint customization still ran after i flash the Verizon ROM.. My EPST Settings were all Sprint.. lols..
These are the steps I took to bring it back..
1. Ran Titan_Relocker to relock SPL from version 2.40 Olipro
2. Flashed Stock Verizon ROM and let Verizon Customization run
3. Unlock using NueSPL2.47 letting it format my SD card to enable Flashing from SD [Thank GOD you added this feature]
4. Placed the new Radio 3.42.30 onto my SD card and enter Bootloader and Flashed it [Thanks to You]
5. then flashed my Verizon kitchen.. All with no problem..
I've discussed this method with some of the guys over at PPCKitchen.org and they were concerned about me bricking my phone.. but I said oh what the heck.. my phone is already messed up..
every one was supprised that it worked.. lol.. I must be one of the lucky few..
Click to expand...
Click to collapse
weird. what were you running before step 1?
the problem seems to manifest itself when you take a GPS radio, and flash a 2.xx RADIO onto it. When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?
the reason everyone was concerned about your phone though, was because there were several bricks produced by downgrading radios - ask ImCokeMan, he'll tell you..
no2chem said:
weird. what were you running before step 1?
the problem seems to manifest itself when you take a GPS radio, and flash a 2.xx RADIO onto it. When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?
the reason everyone was concerned about your phone though, was because there were several bricks produced by downgrading radios - ask ImCokeMan, he'll tell you..
Click to expand...
Click to collapse
I didn't quite understand your question..
"When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?"
When I ran Titan_Relocker.. it installed version 1.06..
Before the Sprint radio upgrade I had...
Hard SPL2.40 Olipro
Radio 3.39.10
No2chem wm6.1 5067 Kitchen
I have also went from a GPS radio to the stock verizon radio/rom a few times because of accidentally letting sprint customizations run.
i am not 100% sure if i had the stock radio on my phone. however it worked with stock verizon rom and phone/ data/ text all worked in stock verizon rom/radio.... so i assume it was the correct radio since it worked with the stock rom...?
EDIT: i do believe i had verizon 1.3 radio on my phone after flashing back from a GPS radio
also i remember reading somewhere that if you do flash back to a stock radio/ rom that it might say stock radio but it will still have components of the gps radio's... i think i read it at ppcgeeks
aguas said:
ive done several radio downgrades from olipro 2.4 to 1.2 to the stock radio/ROMs for refurbishment and ive never had a problem. i dont use the stock SPL because theres no tech around here smart enough to check it.
Click to expand...
Click to collapse
i also have downgraded radio from 3.xx to 1.xx without any problems.
I flashed back to non gps as well. I was having bad experiences with dcd's 2.x so I went to his 1.7. No issues flashing at all.
I have also downgraded to 2 different phones from GPS radios to NON-GPS radios.... Verizons stock radio is 1.30, not a 2.x radio, so that may be the issue for some other folks on different carriers.... It may be an incompatibility with 2.x radios and GPS radios.... I have a folder on my desktop that has all the files necessary AND the instructions clearly written out on how to downgrade..... It has saved my butt 2 times now....
azclown said:
I have also downgraded to 2 different phones from GPS radios to NON-GPS radios.... Verizons stock radio is 1.30, not a 2.x radio, so that may be the issue for some other folks on different carriers.... It may be an incompatibility with 2.x radios and GPS radios.... I have a folder on my desktop that has all the files necessary AND the instructions clearly written out on how to downgrade..... It has saved my butt 2 times now....
Click to expand...
Click to collapse
hmm, it might actually be an issue with 2.X radios. I'll do a little bit of research on this one.
no2chem said:
hmm, it might actually be an issue with 2.X radios. I'll do a little bit of research on this one.
Click to expand...
Click to collapse
the radio i downgraded to was 1.59
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
Click to expand...
Click to collapse
Ya I used to switch from gps to nongps all the time back when the original leaked radio was the only one out... I also converted my last phone (sent in for broken button) back to complete stock vzw (locked and all) as well....
I haven't tried doing any downgrading after installing nueSPL though... are you indicating this is a probelm after flashing nueSPL? Your post has me a 'lil scared now but I'll wait for followups before I attempt anything.. no plans to go back to nongps anyways, though... the new radios seem to have the bugs worked out.
Zenoran said:
Ya I used to switch from gps to nongps all the time back when the original leaked radio was the only one out... I also converted my last phone (sent in for broken button) back to complete stock vzw (locked and all) as well....
I haven't tried doing any downgrading after installing nueSPL though... are you indicating this is a probelm after flashing nueSPL? Your post has me a 'lil scared now but I'll wait for followups before I attempt anything.. no plans to go back to nongps anyways, though... the new radios seem to have the bugs worked out.
Click to expand...
Click to collapse
Only No2chem knows for sure, but after reading his post again I think he's saying you can downgrade to Ollipro 2.4, if thats the case then one should be able to downgrade back to stock as well....
I think no2 is onto something here. I am on VZW also and have gone back to stock from a 3.xx gps radio --> stock 1.30 radio.
I have a feeling that for once we may be glad that verizon never does any updates - they still use 1.30 radio - and that may be the common thread in all our (vzw) success at going back to non gps.
I'd say that I was onto this before him.... He just knows how to verify it...
azclown said:
I'd say that I was onto this before him.... He just knows how to verify it...
Click to expand...
Click to collapse
and i would agree with you!
Speaking of the man himself ^^^^ .. I would note that you had all the data, I just thought it was odd that anyone who tried to go back to a 2.X radio would brick it, while us verizon folks would go back to 1.X and have no issues....
i was with DCD 3.2.5 and wanted to flash to new telus wm6.1 from telus... now i'm stuck with bl spl-2.07...tried to flash back with stock rom Telus_HTC_P4000_WM6_07252007 but at 1% it says not compatible...tried also uni_exitbootloader but nothing happen...whenever tried to flash with SD card...it's always keep saying "loading...", is anyone have suggestion to bring back my mogul to life?
thanks
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
scrawnyb said:
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
Click to expand...
Click to collapse
I would say the same. I would go ahead and unlock OliPro 2.4 (never tried 2.47) then flash Telus rom. After doing so you should be fine.
scrawnyb said:
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
Click to expand...
Click to collapse
what do you mean by "I think you have to downgrade to a stock firmware/SPL" ? du you have any recommendation ?
belmont said:
what do you mean by "I think you have to downgrade to a stock firmware/SPL" ? du you have any recommendation ?
Click to expand...
Click to collapse
Sorry, I read his post wrong. HEre is what I would do:
1. Download OliPro 2.40 and run it. Ignore the part that asks you to verify the Active Synch connection. Its not needed for anything but a connection confirmation.
2. After running OliPro 2.40 you should be stuck at the three color bootloader screen, Like you are now. If not hold Camera and Power and use stylus to put phone in bootloader. Make Sure it says OLIPRO 2.40 for the version on the bootloader. If not then re-run oliupro and make sure to follow the directions. Especially noting that it asks you to disconnect then reconnect the device.
3. Flash your Stock ROM back.
4. Hard Reset.
In my experience you do not have to go back to a stock ROM to flash a new carrier ROM as long as you have OliPro.
Let me ask you this: What exact steps did you take when you flashed Telus ROM image?
I was on the same setup you were, DCD 3.2.5 with Radio .50 and OliPro 2.40. I simply flashed the Telus image and all was well for me. Hell it was better than all well. This is the best ROM I have ever used. PERIOD. No, its not pretty but damn, its fast as anything I have used and the GPS is insane!
BTW: Im a Verizon user. Anyone know how to make the phone not say "Telus" when I go to the connection manager?
scrosler said:
Sorry, I read his post wrong. HEre is what I would do:
1. Download OliPro 2.40 and run it. Ignore the part that asks you to verify the Active Synch connection. Its not needed for anything but a connection confirmation.
2. After running OliPro 2.40 you should be stuck at the three color bootloader screen, Like you are now. If not hold Camera and Power and use stylus to put phone in bootloader. Make Sure it says OLIPRO 2.40 for the version on the bootloader. If not then re-run oliupro and make sure to follow the directions. Especially noting that it asks you to disconnect then reconnect the device.
3. Flash your Stock ROM back.
4. Hard Reset.
In my experience you do not have to go back to a stock ROM to flash a new carrier ROM as long as you have OliPro.
Let me ask you this: What exact steps did you take when you flashed Telus ROM image?
I was on the same setup you were, DCD 3.2.5 with Radio .50 and OliPro 2.40. I simply flashed the Telus image and all was well for me. Hell it was better than all well. This is the best ROM I have ever used. PERIOD. No, its not pretty but damn, its fast as anything I have used and the GPS is insane!
BTW: Im a Verizon user. Anyone know how to make the phone not say "Telus" when I go to the connection manager?
Click to expand...
Click to collapse
thanks for quick reply. i tried so many times to use olipro 2.40...whenever i ran it...it popup that device is not connected and asked me to try again...tried also with SD but still hung on tri-color bars
belmont said:
thanks for quick reply. i tried so many times to use olipro 2.40...whenever i ran it...it popup that device is not connected and asked me to try again...tried also with SD but still hung on tri-color bars
Click to expand...
Click to collapse
Thats interesting. I have hosed so many XV6800's and used OliPro and a stock GPS sprint ROM to get them back (Thanks alot for nothing Verizon!).
IM assuming you are still on the tricolor screen? Take out battery and place back in. Then try again. Dont wait long. Someonelse has discoverd the phone can only be connected for so long before it "drops" connection with the windows machine. Someone else's therory but I can certainly second it.
What SPL were you using with DCD 3.x before upgrading?
scrosler said:
Thats interesting. I have hosed so many XV6800's and used OliPro and a stock GPS sprint ROM to get them back (Thanks alot for nothing Verizon!).
IM assuming you are still on the tricolor screen? Take out battery and place back in. Then try again. Dont wait long. Someonelse has discoverd the phone can only be connected for so long before it "drops" connection with the windows machine. Someone else's therory but I can certainly second it.
What SPL were you using with DCD 3.x before upgrading?
Click to expand...
Click to collapse
before flashing to new telus wm6.1 rom, i had olipro 2.40 with .30 radio and dcd3.2.5 kitchen...i have tried upgrading to radio .50 with no success. but failing to update radio didn't affect anything to my phone. tried your suggestion by romoving battery and still telling me that device not connected.
belmont said:
before flashing to new telus wm6.1 rom, i had olipro 2.40 with .30 radio and dcd3.2.5 kitchen...i have tried upgrading to radio .50 with no success. but failing to update radio didn't affect anything to my phone. tried your suggestion by romoving battery and still telling me that device not connected.
Click to expand...
Click to collapse
Hmmm, maybe try a different USB port at this time. Also, try this...
Before you connect your device open device manager in Windows. Look for M/S USB sync to appear after you connect. What OS are you using? This is what it will look like in Vista.
In XP I beleive it will show up under USB at the very bottom of Device Manager.
Does the phone show up at all?
Flash a stock pre-gps rom first.....then go ahead and upgrade the hard spl to 2.4 or 2.47.....then flash away with whatever you want....
You cannot flash Hardspl to Hardspl...they have overwrite protection not signed by HTC....
..................................
Check your current bootloader
1. Hard reset your phone by holding down both softkeys, hitting reset, and pressing R (just for good measure)
2.
Hit POWER-CAMERA-RESET to check what version of bootloader you have installed.
* At the tri-colour bootscreen you will see the version number installed.
* if it is 1.04 or 1.06 then your Titan is locked and has the correct bootloader to flash to the stock ROM of your choice --> skip to step III
* if it is 1.20, 2.40, or 2.47 then your phone is unlocked with a third party bootloader and must relock your phone.
---------------------------------------------------------------------------
I have a Sprint HTC Mogul and have been shuffling through all the threads and still confused, sort of...
I am at the Tri-color screen and none of those version number matches mine.
on my tri-color screen it displays:
Tita100
SPL-2.06.0000
CPLD-9
i searched the board and found but it didnt give me a clear answer.
http://forum.xda-developers.com/showthread.php?t=284404
So far i have downloaded
Sprint Cab
dcd_titan_3.2.5.exe
Titan_Radio_ROM_3.42.40.exe
[OliPro MFG 2.40] (Hard SPL)
I'm hoping someone can help me figure this out, whether or not i need to downgrade/upgrade.
And Also was wondering what type of neat things i can do with the roms/kitchen im a total noob at this but trying to make sense of all of this.
Other Phone info:
rom Version 3.35.651.2
radio ver. 3.35.04
I'm *PRETTY SURE* that's just an updated version of the relocker SPL.
You should be able to flash back to a stock (non-GPS if I remember right) ROM from there.
I think what *MAY* have happened was the process got interrupted when you were unlocking?
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
scrawnyb said:
flash back to a stock (non-GPS if I remember right) ROM from there.
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
Click to expand...
Click to collapse
You are right on the money.......
that should be the stock bootloader for a stock gps rom.
if you want a custom rom you will need to unlock using 2.40 or 2.47.
kitchens just allow you to cook in apps that you want instead of installing them later. the problem is the install is permanent and they cannot be removed.
i prefer to flash a clean rom and install my apps later.
im pretty sure 2.06 is the temporary bootloader used by no2chem's nueSPL to ram with 2.47. if your bootloader shows 2.06 you will need to flash nueSPL again as it did not flash correctly. 2.07 is nueSPL Relocker.
i had not heard of anyone getting "stuck" in 2.06 and the op didn't mention he had tried flashing 2.47 or relocking.
i think you are correct though as i just checked and i am @ 2.07 (relocked).
lafester said:
i had not heard of anyone getting "stuck" in 2.06 and the op didn't mention he had tried flashing 2.47 or relocking.
i think you are correct though as i just checked and i am @ 2.07 (relocked).
Click to expand...
Click to collapse
it happened to me, although i didnt get stuck. it was flashed on a card that isnt flashing compatible (telus). i only noticed because it didnt reset itself like it said it should have. returned the card, got a San Disk, and reflashed nueSPL. this time it soft reset itself, and displayed the correct bootloader, 2.47.
I got stuck in 2.06 last night... earlier in the day I dropped my mogul in water and somehow cracked the screen at the same time. After drying everything out for 12 hours the phone came on with barely anything on the screen, I got the phone into bootloader (it was at 2.47) flashed a stock sprint rom, I immediately ran the nueSPL relocker (had to use my mobler to see the screen), after the relocker ran I was stuck in a 2.06 bootloader for some time, eventually I got out of the bootloader (not quite sure how... I flashed the stock sprint rom a few more times and mash some buttons) eventually I was able to run the relocker again and get my phone back to 2.07... a little bit of trouble but it was worth it now that I know I should have absolutely no problems getting a new (probably refurb) phone through TEP
scrawnyb said:
I'm *PRETTY SURE* that's just an updated version of the relocker SPL.
You should be able to flash back to a stock (non-GPS if I remember right) ROM from there.
I think what *MAY* have happened was the process got interrupted when you were unlocking?
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
Click to expand...
Click to collapse
My phone is stock, i hadnt done anything to it yet. Im just unsure what to do because 2.06 was not shown at the step-by-step instructions.
so let me see if i understand what i need what to do....
flash the current rom, stock 2.06, with [OliPro MFG 2.40] (Hard SPL)
then run dcd_titan_3.2.5.exe and Titan_Radio_ROM_3.42.40.exe
then Sprint Cab??
Thanks for the replys