I had to turn my Titan in for a replacement. Knowing about relocking breaking the usb port, I figured I'd do it anyway and just flash via the SD card. Well to my amazement I was able to relock and flash the OEM Radio and Software without and problems. Once it booted up Activesync connected and charge light came on.
Just figured I'd share since there is so much fear about relocking.
Went from 3.56 based ROM and 3.42.30 Radio back to OEM.
I had to turn my Titan in for a replacement. Knowing about relocking breaking the usb port, I figured I'd do it anyway and just flash via the SD card. Well to my amazement I was able to relock and flash the OEM Radio and Software without and problems. Once it booted up Activesync connected and charge light came on.
Just figured I'd share since there is so much fear about relocking.
Went from 3.56 based ROM and 3.42.30 Radio back to OEM.
Click to expand...
Click to collapse
I'm not sure what you mean about fear of relocking and relocking breaking the usb port.
The story on the street has always been.... DONT go from a GPS to a non-GPS radio. Something about how it will screw up the USB port.
http://forum.ppcgeeks.com/showthread.php?t=21953
Read first post
This is only a small example but I'm sure I could find more than 10 instances of this throughout threads. Including NO2Chem saying not to do it aswell.
The story on the street has always been.... DONT go from a GPS to a non-GPS radio. Something about how it will screw up the USB port.
Click to expand...
Click to collapse
I have never heard that story, nor have I ever had any problems going back and forth between GPS and non GPS radio.
While testing the new Sprint PRI way back when 3.49 came out (I'm on Verizon), and now testing the new Verizon update, I've had to go back to stock more times than I can count and have never ran into any issues.
May I ask where you found these rumors?
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Read the first post in the link I gave you. Then you can do a search on downgrading issues to find more reports.
I know it can be done because I've done it on 2 different Titans now. I made the thread to help prove that it can be done so other arent so scared by the rumors as you call it.
gc14 said:
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Click to expand...
Click to collapse
Exactly... I'm attempting to put the rumor to rest. Atleast as far as Verizon customers are concerned.
What SPL are you using before relocking to 1.06?
yep
Rom 2.09
Radio 1.30
yep
Rom 2.09
Radio 1.30
Click to expand...
Click to collapse
I think you misunderstood me....SPL = bootloader.
What bootloader are you using before relocking?
lllboredlll said:
yep
Rom 2.09
Radio 1.30
Click to expand...
Click to collapse
I am not sure if you answered his question. Which bootloader are you running, nueSPL or other?
I have heard some concern with reverting to non-GPS stock using the no2chem tools, but obviously there is no worry with the relocker and such.
gc14 said:
I think you misunderstood me....SPL = bootloader.
What bootloader are you using before relocking?
Click to expand...
Click to collapse
Sorry I misunderstood you. I was running 2.40 before taking it back to 1.06.
It gets hard to think straight with people flying in and out of my office every 5 seconds. I'll try to read a little more throughly next time.
Sorry I misunderstood you. I was running 2.40 before taking it back to 1.06.
Click to expand...
Click to collapse
In my encounters with going back and forth, this is what I've come up with (for Verizon users):
If using SPL 2.47, steps to relock are as follows:
- Install Olipro 2.40 via USB
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
(DO NOT EVER USE nueSPL Relocker!!!)
To get back to SPL 2.47 from stock, all you need to do is run nueSPL Unlocker and use the microsd card to go from SPL 1.06 right to SPL 2.47, then flash a 3.x.x rom/radio. Going FROM SPL 1.06 TO SPL 2.47, SPL 2.40 is not needed.
If using SPL 2.40, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 2.40 from stock, all you need to do is run Olipro 2.40 via USB, then flash a 3.x.x rom/radio.
If using SPL 1.20, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 1.20 from stock, all you need to do is run TitanUnlocker via USB, then flash a 1.x.x rom/radio.
Now all there is left to do is link this to ppcgeeks and be done with the rumor. Thank you for your input....
gc14 said:
In my encounters with going back and forth, this is what I've come up with (for Verizon users):
If using SPL 2.47, steps to relock are as follows:
- Install Olipro 2.40 via USB
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
(DO NOT EVER USE nueSPL Relocker!!!)
To get back to SPL 2.47 from stock, all you need to do is run nueSPL Unlocker and use the microsd card to go from SPL 1.06 right to SPL 2.47, then flash a 3.x.x rom/radio. Going FROM SPL 1.06 TO SPL 2.47, SPL 2.40 is not needed.
If using SPL 2.40, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 2.40 from stock, all you need to do is run Olipro 2.40 via USB, then flash a 3.x.x rom/radio.
If using SPL 1.20, steps to relock are as follows:
- Install SPL 1.06 using Titan Relocker via USB
- Flash stock rom/radio
To get back to SPL 1.20 from stock, all you need to do is run TitanUnlocker via USB, then flash a 1.x.x rom/radio.
Click to expand...
Click to collapse
I vote to have this added to the return to stock wiki. GC will you post?
How about USCC?
Brings me back to my previous question, GC (Previous Thread); How can I back-up the current ("Stock" for USCC) OS ROM and RADIO on my new Titan? It was discussed that it [dumping current ROM and Radio and then using dump to re-flash] couldn't be done. I wanted to do a ROM dump before flashing to DCD's so that I could revert to it if needed; also, so that I could re-flash to "stock" on my old unit before sending it back to USCC... however, I don't how to accomplish this, if at all possible to do so!
If anyone can guide me through this, I could upload the USCC "Stock" (for lack of a better word, since USCC has no actual "Stock" Roms) ROM and RADIO and make it available to other unfortunate USCC customers. I agree w/Serfboreds, and also vote to have this thread added to the "Return to Stock" Wiki.
Thanks, Guys!!
gc14 said:
I have never heard that story, nor have I ever had any problems going back and forth between GPS and non GPS radio.
While testing the new Sprint PRI way back when 3.49 came out (I'm on Verizon), and now testing the new Verizon update, I've had to go back to stock more times than I can count and have never ran into any issues.
May I ask where you found these rumors?
EDIT: Ahhh ppcgeeks...yeah don't really frequent those forums much. Not sure why n2c would say something like that because like I said, I've probably gone back and forth between GPS/Stock at least 15-20 times with no problems at all.
Click to expand...
Click to collapse
I think the issue lies with Sprint customers..... I personally have reflashed to stock at least 15-20 times.... from a GPS ROM and back.....
That is a very nice summary of steps for re-locking from various spl's and definately needs to be entered into the !iki.... If GC doesn't have time I'll do it when I get done here at the dentist.... booooooo....
I think the real issue was going from bootloader nueSPL 2.47 to a stock GPS rom caused problems. But because verizon customers dont have a stock gps rom to flash back to we go to a non-gps (1.XX) radio which does not cause the problem.
No2chem originally made the advice not to go back to a stock assuming stock included 2.XX or 3.XX radios. Once he was alerted to the fact that going back to stock 1.XX (i.e with verizon) did not cause a problem he modified his warning advice.
Once again, the warning is only valid for bootloader nueSPL 2.47
GC, does going from nueSPL 2.47 to olipro SPL 2.40 prior to relocking negate problems for everyone? I ask that question because I have refrained from moveing to 2.47 for fear of problems in the future. As far as I can see the benefits of 2.47 are marginal at best. But if I have a sure fire escape mechanism I might upgrade my bootloader at some stage
GC, does going from nueSPL 2.47 to olipro SPL 2.40 prior to relocking negate problems for everyone? I ask that question because I have refrained from moveing to 2.47 for fear of problems in the future. As far as I can see the benefits of 2.47 are marginal at best. But if I have a sure fire escape mechanism I might upgrade my bootloader at some stage
Click to expand...
Click to collapse
Yes, it negates the problems.
gc14 said:
Yes, it negates the problems.
Click to expand...
Click to collapse
Thanks dude. And I agree with Serfboreds that you should add this advice to your wiki. Very easy to understand and maps out all (most) of the possible relock escape routes.
Once again gc you are a font of wisdom.
ugh.... i can't keep up with all the misinformation anymore. If it works for you verizon users in your personal experience though good for you. I know for a fact it can cause problems. I'm starting to narrow it down to the original 3.35 leaked rom with GPS radio from sprint, but have no firm proof it's that narrow scope yet . Still have myself a brick from the GPS to pre-gps and I didn't use nueSPL Relocker thats for sure =P
For more info on the problem and others that experienced this "rumor" first hand go to ppcgeeks and search for "download mode"
Related
My bro has a Titan and is thinking about having me upgrade but I saw that his bootloader version states 1.04 not the 1.06 that mine was when I flashed (and also the one that the wiki says too). Is the process the same? Should I just use unlocker then upgrade to 2.40 then install radio then DCD? A little wary as it is not my phone. Please be specific when answering. I am planning to do the most recent radio and rom.
serfboreds said:
My bro has a Titan and is thinking about having me upgrade but I saw that his bootloader version states 1.04 not the 1.06 that mine was when I flashed (and also the one that the wiki says too). Is the process the same? Should I just use unlocker then upgrade to 2.40 then install radio then DCD? A little wary as it is not my phone. Please be specific when answering. I am planning to do the most recent radio and rom.
Click to expand...
Click to collapse
In order to flash a dcd rom you need 2.40...Go through the same process you would in order to flash a 3.1.x rom.
prepsssuck said:
In order to flash a dcd rom you need 2.40...Go through the same process you would in order to flash a 3.1.x rom.
Click to expand...
Click to collapse
So it still needs unlocker then 2.40 right? or is unlocker unnecessary now?
Who is his carrier? As forthe bootloader question, I'd be asking Ollipro... I've not seen a bootloader 1.04....
azclown said:
Who is his carrier? As forthe bootloader question, I'd be asking Ollipro... I've not seen a bootloader 1.04....
Click to expand...
Click to collapse
bootloader 1.04 is the "stock" verizon bootloader you should still update to the 2.40 if you plan on having any 3.xx.xx radio's
Just to clarify...
When the phone ships it comes with SPL-1.04 which is the stock bootloader, which is why it doesn't say Olipro.
1.06 is also a "stock" bootloader provided by Olipro which allows you to flash stock roms/radios.
Edit: WINGS 1 - PENS 0!!!!!!
gcincotta said:
Just to clarify...
When the phone ships it comes with SPL-1.04 which is the stock bootloader, which is why it doesn't say Olipro.
1.06 is also a "stock" bootloader provided by Olipro which allows you to flash stock roms/radios.
Edit: WINGS 1 - PENS 0!!!!!!
Click to expand...
Click to collapse
Thanks, I have been flashing since the time you needed the old Olipro to flash the radio and when my brother once before flashed going straight to 2.40 it caused problems. I haven't had a new phone since then and wondered if the unlocker was still necessary. I am gathering that it is not and that you can go straight to 2.40, am I correct?
mogul with slight crack along the frame of screen
i've been reading for a while, and someone wrote that it doesn't matter about the bootloader when returning the phone to the store as long as you have the stock rom. i'm using the newer stock rom (3.35), though i did use the unlocker to put olipro 2.40 on it a while ago to mess with other roms.
the work order for the replacement mogul is already in and it (the new or refurbed mogul) should arrive tomorrow or the next day. should i go through the trouble of putting the stock bootloader on there if i already have the newer stock rom from htc/sprint on my phone?
also, i read that sprint has no warranty (or it's only 30 days). i use total equipment protection for $7 per month (which is how i'm getting a new or refurb mogul because of a case fracture). i'm using the newer stock sprint rom (with gps) and my bootloader says olipro 2.40.
does anyone think that i should be worried if i don't do anything before the new one arrives and just give them the cracked one?
i clearly didn't read the terms and conditions closely enough to find anything that tells me not to modify the bootloader or really ANYTHING about the bootloader...is total equipment protection a warranty that i could possibly void by putting olipro 2.40 on it even with the sprint official 3.35 installed?
I wouldn't worry about it. 1.06 is not the official stock bootloader either, 1.04 is, and I've swapped out my xv6800 a couple times with 1.06 on it and the Verizon stock rom. They don't usually check the bootloader. Just make sure the new Sprint stock rom is on there with radio 3.35.04 and you should be fine.
thanks much for your quick reply. i'll rest easier tonight.
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....
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
paulash said:
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
Click to expand...
Click to collapse
I have not seen this... but my suggestion would be to do the Power + Camera + reset... and let it go into bootloader... then just reflash the rom.
paulash said:
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
Click to expand...
Click to collapse
Like the other guy said, force bootloader but take note of the version. Make sure you are running version 2.40 or greater. If you are running stock bootloader 1.06 or anything else it will have the reboot loop. Read the wiki in my signature fully before doing anything else. Did you read this before flashing?
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5?????
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
Click to expand...
Click to collapse
You need to be upgrading to 2.40 before you do ANYTHING, not just the radio. That was probably your problem before. From stock, bootloader, radio, rom in that order.
paulash said:
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
Click to expand...
Click to collapse
This wiki tells you the steps.... I did it as follows... but... after doing the radio... you have to force it into the bootloader. It will not load into the phone rom.
xv6800 Rom Upgrade Instructions Wiki
gc14 said:
You need to be upgrading to 2.40 before you do ANYTHING, not just the radio. That was probably your problem before. From stock, bootloader, radio, rom in that order.
Click to expand...
Click to collapse
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
paulash said:
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
Click to expand...
Click to collapse
I put radio 3.42.30 on there but had to get HardSPL-2.40 on it first. The wiki explains it very well.
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
Click to expand...
Click to collapse
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
gc14 said:
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
Click to expand...
Click to collapse
I didn't go through those steps GC. I did the olipro 2.40... then the 3.42.30... then had to force it into bootloader.... then did the DCD 3.2.3 update. That's it... and all done via USB cable.
nitro66215 said:
I didn't go through those steps GC. I did the olipro 2.40... then the 3.42.30... then had to force it into bootloader.... then did the DCD 3.2.3 update. That's it... and all done via USB cable.
Click to expand...
Click to collapse
Damn GC, that's a lot of extra work compared to what I have people doing in my tutorial...
gc14 said:
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
Click to expand...
Click to collapse
There's a REALLY annoying problem going on. I had to reflash to stock twice again. 2.40 installs successfully, and im in the boot loader. I open up the sprint 3.56 (and 3.42.02 radio) with the RUU, and it just reverts to SPL 1.20!!!! Why does this keep happening?
scrawnyb said:
Damn GC, that's a lot of extra work compared to what I have people doing in my tutorial...
Click to expand...
Click to collapse
Why does everybody say you must have an SD card to do the upgrades? I never did anything with an SD card and was able to flash all the way to 3.2.5 without it.
paulash said:
There's a REALLY annoying problem going on. I had to reflash to stock twice again. 2.40 installs successfully, and im in the boot loader. I open up the sprint 3.56 (and 3.42.02 radio) with the RUU, and it just reverts to SPL 1.20!!!! Why does this keep happening?
Click to expand...
Click to collapse
It's because you aren't into the true HARD spl. You have the soft 2.40 spl. You have to verify that the bootloader is 2.40 by doing the power + camera + reset.
nitro66215 said:
It's because you aren't into the true HARD spl. You have the soft 2.40 spl. You have to verify that the bootloader is 2.40 by doing the power + camera + reset.
Click to expand...
Click to collapse
I have the hard SPL. I'll verify it again once stock rom reinstalls (I have to keep reinstalling to stock everytime it switches back to SPL 1.20... really frustrating).
paulash said:
I have the hard SPL. I'll verify it again once stock rom reinstalls (I have to keep reinstalling to stock everytime it switches back to SPL 1.20... really frustrating).
Click to expand...
Click to collapse
It shouldn't be reverting back to 1.2. If you have 2.4 installed correctly... and you check with the "Reset"... then you can do the RUU update right from that bootloader screen. If it is 1.2... then attempt the 2.40 hard spl from that screen instead of redoing the stock rom.
nitro66215 said:
Why does everybody say you must have an SD card to do the upgrades? I never did anything with an SD card and was able to flash all the way to 3.2.5 without it.
Click to expand...
Click to collapse
Who said you HAVE to do this by SD? I think we are saying it is easier.
GC detailed that to flash by USB/Activesync is about six or seven steps and about an hour of work, versus flashing by SD which is less than five minutes and a step or two.
serfboreds said:
Who said you HAVE to do this by SD? I think we are saying it is easier.
GC detailed that to flash by USB/Activesync is about six or seven steps and about an hour of work, versus flashing by SD which is less than five minutes and a step or two.
Click to expand...
Click to collapse
I don't agree that the USB / Activesync is 6 or 7 steps. I did 4 or 5 at the most.. and I'm counting the power+camera+reset as a step.
flash
When the bootloader screen comes up with 1.2, are you just assuming its done...or do you actually then keep clicking through the options until it actually flashes the phone with the ROM?
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