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.
Related
just to dispel the myth;
SPL 1.01MFG Flashing via mtty is NOT faster than using the RUU; HTC do not deliberately slow down the process, that's just bloody stupid; the reason it can take longer is if you include a Radio ROM, because flashing a radio takes sodding ages, but can people please learn that using a proper NBH is a smarter and safer way to flash their Hermes.
I second that. this myth appeared because 1.01MFG was the first bootloader that allowed us to flash unsigned, but it didn't allow to flash a radio. So there was the general "feeling" that signature checking was slowing down the process, but it was not: the slowness is caused by flashing the radio.
True, but from strictly a ROM cooker perspective, its not faster. It takes time to build/run the RUU & when you're testing cooked roms, its just far easier to fire up the sspl 1.01MFG and lnb the new os.nb directly.
I understand safety to be the presence of BL v1.10.Oli at location 50020000.
Consequently, I keep this version flashed and test out cooked ideas (currently I'm working on the ATI video issue so I've been flashing a lot of test roms) using your 1.01MFG sspl bootloader.
Expanding on this, I believe that production cooked ROMs should include your 1.10.Oli SPL bootloader from a safety perspective based on my understanding that the BL is flashed first in the RUU under the control of the 1.09Des SSPL loader. This will guarantee a safety net should something go wrong during the OS and/or Radio flashing portion of the process. I would also imagine that this is why you state that RUU flashing is safer too.
Maybe this should be SOP whenever a new production ROM is released by Operators too: Repackage everything into a sspl that also loads 1.10.Oli. Of course, when HTC takes their inevitable next steps in this "spy vs. spy" battle, all this may be invalidated...
Here's an interesting thought: Your bootloader advancements have actually helped Operators since using this technique should result in far fewer bricks being returned for new devices. Now the question is this: does this cost HTC I wonder? Or to put it differently: who sucks up the cost of a bricked Hermes that is replaced in warranty. Whomever this is is very happy with you Olipro and likely to offer you a job as a top developer . Conversely, whomever sucks up the cost is gonna put a contract out on you....
JK: The fact is this: both have a contract on you b/c you've invalidated CID
When I run the RUU, I'll open the Windows Media Player to play the MP3 files, and the update process will be finished in 2-3 minutes.
I guess my major question is this:
At what time during the RUU flashing process is the bootloader flashed? If its the first thing to be flashed then my points above are valid. If not, then everybody who flashes needs to insure that they have 1.10.Oli in flash before stripping the bl out of any ROM they wish to flash. Perhaps we could begin to go through production ROMs and designate those that have had this done with another column on the Wiki.
Sleuth255 said:
At what time during the RUU flashing process is the bootloader flashed?
Click to expand...
Click to collapse
In the order it is placed on the NBH file, generally IPL & SPL are the first.
Sleuth255 said:
If its the first thing to be flashed then my points above are valid.
Click to expand...
Click to collapse
Yes they are: the HardSPL is flashed but the process continues with the current bootloader on device... but after the flashing process ends (or fails) HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
pof said:
HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
Click to expand...
Click to collapse
But there isn't a 1.09 hardSPl yet, no?
VivaErBetis said:
But there isn't a 1.09 hardSPl yet, no?
Click to expand...
Click to collapse
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
politby said:
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
Click to expand...
Click to collapse
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Olipro said:
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Click to expand...
Click to collapse
that's what I thought. Any forecast on when (if) you'll have one available?
politby said:
that's what I thought. Any forecast on when (if) you'll have one available?
Click to expand...
Click to collapse
no... I mean you either need to have flashed on a Hard-SPL before you buggered it up, or you need to be able to still get into Windows after buggering it
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
VivaErBetis said:
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
Click to expand...
Click to collapse
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Olipro said:
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Click to expand...
Click to collapse
Ok. Fortunately I don't need it ***yet***. Thanks Olipro.
BTW: I got your 1.10 version installed and it works very well. Thanks.
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
i installed the wrong rom on the wrong hard spl. i had the hard spl a 1.30 installed and dcd 3.2.0. now the screen is stuck at the loading screen that says htc smart mobility. and no radio at the bottom. please help and the phone wont sync.
Good luck on that.. You installed a bootloader for a different model -- likely the TyTn or Trinity. What phone do you have? What instructions did you follow?
If you do have a Titan, then possibly via the SD Card you can change the bootloader to the new 2.47 (I haven't played with it yet but another may provide a solution). You are likely out of luck in flashing to any of the other Titan bootloaders as you must be able to boot into the OS, but with you error of installing an inappropriate bootloader you are out of luck there.
no it was a bootloader 1.30 for the titan
Your information is incoherent.
What rom/bootloader did you have prior to updating?
What rom/bootloader did you try to upgrade to?
You need a minimum SPL of 2.40 to install DCD 3.2.0
I use 2.47 from no2chem and it works great. http://forum.ppcgeeks.com/showthread.php?t=30561
Are you able to boot up the device? If so copy the SPL 2.47 to the card then to the PDA and run it from there.
If not, put the PDA into Bootloader mode and try to install Olipro 2.40
http://www.lifesnotsogood.com/dcd1182/titan/spl/titan_SPL_2.40-olipro.exe
Failing that you can try to flash back to an official ROM if you have one.
You need to soft reset your phone while holding the Camera and power buttons. This will force your phone in to the bootloader. You should then be able to reflash to lower ROM. Then you need to search for Olipro or whatever the 2.40 bootloader is. Your best bet after that is to flash the official Sprint 3.35 Radio and Rom then flash to DCD's.
**Edited**
Sorry Hamilton didn't realize you gave a link to the 2.40 bootloader.
If he is sure that it is "bootloader 1.30 for the titan" then I know of NO such bootloader. He has likely installed the wrong bootloader (for another device) and therefore no amount of flashing to an OS ROM will help him boot into the OS. Unless via an SD card for 2.47, beastmode216 is stuck with a borked device.
So, beastmode216, I'll ask again, where did you get such instructions and where did you source your bootloader 1.30?
What is one of the earlier bootloaders? I was thinking my Mogul orginally had something like 1.30 or 1.40.
thanks guys but the problem is solved. just make the phone go in to the bootloader
Verizon stock bootloader is 1.30 if I remember correctly. It has been several months since I have seen a stock bootloader
calash said:
Verizon stock bootloader is 1.30 if I remember correctly. It has been several months since I have seen a stock bootloader
Click to expand...
Click to collapse
My mistake, as pointed out by gc14 the stock bootloader is 1.04.
Ahh, ok, my fault as I thought that he had also installed a bootloader under the name of 1.30.. That could've been an unlocker for a TyTn or another device.
Correct, OEM bootloader should be 1.30.60.
Click to expand...
Click to collapse
This is incorrect. The stock bootloader is 1.04. The stock radio is 1.30.60.
SPL 1.30 does NOT exist for the Titan.
Stickies exist for a reason...to read them as they contain valid, useful information. http://forum.xda-developers.com/showthread.php?t=392133
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"
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