Problems after using Titan Relocker - Mogul, XV6800 ROM Development

Ok here goes,
I have been using DCD rom and everything has been great.
olipro 2.40
3.27 radio
DCD 2.3.2 Rom
The problem started this morning after I ran the titan relocker to try and go back to a VZW rom/radio etc.
The relocker seemed to work fine, I am at the boot loader screen which states the following...
TITA100 ruunbh
spl-1.06.0000
cpld9
Looks normal to me, so I try to continue loading the vzw radio and then rom. When I run RUU after dropping the nbh file in the folder, I go through the motions and get a percentage screen on both my pc and the phone. It never goes above 0%. I get a communication error and have an option for recovery, which I tried and it didn't work. I dont have a microSD Card to flash from. Any Ideas?

Resolved
Found a util that would get me out of the boot loader cycle called titan_exitbl.exe. Re-Unlocked bootloader, reflashed dcd 2.3.2 rom, and reflashed radio 3.27 .

I have the same problem! There Are any ways of the decision?

Related

Think im in troubel now please help

Here is a breakdown of what i did and whats happening.
1.2 ollipro installed already
loaded new radio
loaded new rom
Now the windows mobile 6.1 screen would come up and ask to tap screen but would reboot at this screen continously. I assumed this was happening because 1.2 ollipro was installed and not 2.4.
I then decided to reinstall my old radio and old rom and now the phone gets to the htc bootscreen and reboots immediately over and over again without getting far at all. What do I do?
For TELUS P4000
BOOTLOAD MODE
1. Try getting to the BOOTLOAD MODE by pressing POWER, CAMERA and RESET all a the same time
2. You should see at screen with red green blue white
New RADIO and CE ROM
1. Hard-SPL-240-MFG.exe/titan_SPL_2.40-olipro.exe (follow the instructions)
2. Run titan_radio_3.35.04.exe (very simple GUI instructions)
3. The titan will reboot by it's self, put it back in BOOTLOAD MODE
4. Extract dcd_titan_kitchen_3.0.0.rar to a directory and run BuildNB.bat (it takes a couple of min)
5. Select the stuff you want and don't forget you carrier (TELUS....)
6. Press the PLAY button (when finished, which is hard to see, when play is green) close the BuildOS
7. In a DOS windows it will build the CE ROM (follow the instructions)
8. Titan will reboot
i cant get 2.4 on there because i can get activesync up and when i get it to run through the boot load it gets to 100% in a split sec but leaves 1.2 on and not 2.4 even though it didnt record any errors
I'm having the exact same problem. Got the new Rom and radio installed. I had to go back to 1.2 to do it. But now i cant get 2.4 to install. I run the program it seems to install but still says 1.2 and is stuck on bootloader screen. even though it said itupdated to 2.4 anyone got any ideas on how to get 2.4 on there?
Try entering the Bootloader mode of Oliprio 1.20 and connect the USB to your computer.
Although it wont start an Active Sync session it will still allow you to load thing on such as a ROM or flashing program.
Well once you are in Bootloader and have a USB connection then try installing Oliprio 2.40
This might work.
Hi, ive done that and gone through the 2.4 install. after the RUU runs the progress bar goes across in like 1 second. it reports it successful but it still says 1.2 and is now stuck in the 1.2 bootloader. as if 2.4 never installed. any suggestions?
Furman69 said:
Hi, ive done that and gone through the 2.4 install. after the RUU runs the progress bar goes across in like 1 second. it reports it successful but it still says 1.2 and is now stuck in the 1.2 bootloader. as if 2.4 never installed. any suggestions?
Click to expand...
Click to collapse
So you installed 2.40. Well once you installed 2.40 go into bootloader again and make sure it is 2.40 and then try flashing the Radio first and then the ROM.
This is how i did it:
Installed olipro 1.2
installed radio 3.35
installed dcd sprint 3.0
Now like everyone else it continually reboots cause of olipro 1.2. So i put it in bootloader and it says 1.20 spl. So now i go to install 2.4 Olipro. RUU runs and the progress bar goes to 100% in about 3 secs. AFter it goes to 100% the mogul screen flashes and it says olipro 1.2 as if 2.4 didnt install even though on my comp it says that ruu update was sucessful. So im confused. I have tried it on my computer(vista64) and my old one xp 32bit. When the batch file is running it says "no device connected. would you like to try again?" w/ a yes/no/cancel. If i hit yes it just loops. if i hitno it will ask me this about 4 times then RUU will load
Ok, for anyone stuck with an older version of olipro and the new radio:
While in the bootloader, load an earlier version of your carriers rom. This should let you boot again and will let you install the newest 2.4 olipro bootloader so you can flash the newer roms.
If you can't find an earlier version of your carriers rom you will need to find an older radio rom and an older custom rom and flash both seperately to get it to boot.
Furman69 said:
This is how i did it:
Installed olipro 1.2
installed radio 3.35
installed dcd sprint 3.0
Now like everyone else it continually reboots cause of olipro 1.2. So i put it in bootloader and it says 1.20 spl. So now i go to install 2.4 Olipro. RUU runs and the progress bar goes to 100% in about 3 secs. AFter it goes to 100% the mogul screen flashes and it says olipro 1.2 as if 2.4 didnt install even though on my comp it says that ruu update was sucessful. So im confused. I have tried it on my computer(vista64) and my old one xp 32bit. When the batch file is running it says "no device connected. would you like to try again?" w/ a yes/no/cancel. If i hit yes it just loops. if i hitno it will ask me this about 4 times then RUU will load
Click to expand...
Click to collapse
Instead of running the RUU right after installing 2.4 over 1.2 try canceling the RUU and then manually enter bootloader mode in 2.4 and then install the RADIO following the ROM.
I figured it out. feel kinda stupid. was trying to install 2.4 from the boot loader of 1.2 forgetting that it needs to install files over to the phone before it flashes. :/ thanks foryour help though
Furman69...
I'm having the same problem. Could you post a step by step?
Thanks
I think I bricked it.
Actually I think I made a bigger mistake. I'm a VZW user, and I flashed the sprint/htc update hoping I could just flash dcd on top of that = stupid. The radio settings were all f-ed up. So I believe I read in the dcd 3.0.0 thread to run the titan relocker and then flash the stock vzw rom. Big mistake. Once I relocked it, It wouldnt let me flash vzw 2.09 and now my phone's in bootloader saying
TITA100
SPL-1.06.0000
CPLD-9
I think I'm screwed because It doesnt have a rom on there, so I can even unlock it. Any help would be greatly appreciated.
Flashing the sprint update, then flashing dcd on top of it would have been completely fine if you didn't let the sprint customizations run...i've done it to 3 phones already.
I don't really get what you're saying though. Are you stuck in the bootloader? Can you boot into any kind of rom? What happens if you try and soft reset, does the phone do anything?
gcincotta said:
Flashing the sprint update, then flashing dcd on top of it would have been completely fine if you didn't let the sprint customizations run...i've done it to 3 phones already.
I don't really get what you're saying though. Are you stuck in the bootloader? Can you boot into any kind of rom? What happens if you try and soft reset, does the phone do anything?
Click to expand...
Click to collapse
Yeah I wasn't that smart though . But yeah I'm stuck in bootloader. And I don't even know how to go about putting a ROM on there because it's locked. I've already tried to redo the Sprint/HTC 3.35 update, but to no avail. It says wrong vendor. I don't know... It's brand new too, that what sucks about it.
I finally got it to work after going back and forth installing old roms and radios and then installing 2.4 and then the radio and rom as ususal.
To be honest with you guys i beat myself up because i should of done it like this from the get go 2.4,radio, rom, and thats it but i read about people having trouble and dcds post, and I just went through more trouble that way. Thanks for the help.
If you're stuck in the bootloader, download the exitbl program to forcefully exit the bootloader. This will reset the phone. Tell me what happens after that. Does it boot any sort of rom? Does it just hang at a blank screen? Let me know.
Jaquers said:
Actually I think I made a bigger mistake. I'm a VZW user, and I flashed the sprint/htc update hoping I could just flash dcd on top of that = stupid. The radio settings were all f-ed up. So I believe I read in the dcd 3.0.0 thread to run the titan relocker and then flash the stock vzw rom. Big mistake. Once I relocked it, It wouldnt let me flash vzw 2.09 and now my phone's in bootloader saying
TITA100
SPL-1.06.0000
CPLD-9
I think I'm screwed because It doesnt have a rom on there, so I can even unlock it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I had a similar experience. Here is what I did.
I had the following installed before I started.
2.40 bootloader
3.27 radio
DCD 2.3.2 rom
I wanted to upgrade to the latest and greatest so I did the following. (This was before anyone knew about the 2.40 radio flashing issues.)
Flashed to DCD 3.00.
Failed Trying to flash 3.35 radio.
Read some more and like you tried to relock my phone using titanrelocker
Locked bootloader
Failed trying to flash Verizon Radio (downloaded from ppcgeeks.com)
Failed trying to flash Verizon Rom 2.09 (downloaded from ppcgeeks.com)
So at this point I was stuck in the original 1.06 Verizon locked bootloader, but I had 3.27 radio and DCD 3.00 rom.
Execed titan_exitbl.exe (included in 2.40 bootloader) in vista which returned a nice error. (Error accessing USB blah blah blah)
Execed titan_exitbl.exe in XP with ActiveSync and phone rebooted
Phone booted into Windows Mobile 6.1 and rebooted itself.
So I plugged the mini USB cable back in hopeing it might prevent it from rebooting. Luckily it did.
Reunlocked Bootloader using 1.20 olipro
Flashed 3.35 Radio
Flashed 3.00 DCD Rom again. (Just in case)
Phone booted into Windows Mobile 6.1 with mini usb cable still plugged in.
Upgraded bootloader to 2.40.
Re-Insert my NAM settings into EPST and rebooted.
*228 to get latest PRL.
Has been rock solid since.

Have i bricked my phone? I dont kno what to doo. HELP!! :(

So here is my situation:
I had a 3.27 radio with a 3.xx rom (one of the DCD roms). I wanted to get the 3.35 radio so i decided to flash to the SPRINT 3.35 rom, to do so i had to relock the phone so i used Titan Re-locker (which may have caused the whole problem) and now I am stuck at the SPL 1.06 screen.
I tried flashing older roms and still no luck.
I am currently with Telus and only flashed the SPRINT 3.35 rom to get the 3.35 radio off it. WHat do i do? I haven't bricked my phone right?
I have tried to flash Sprint 2.09 and SPRINT 2.17 roms and have failed. The bar goes up to 1% and then restarts the phone back to the SPL 1.06 screen for any flashes i try to do.
So here is my situation:
I had a 3.27 radio with a 3.xx rom (one of the DCD roms). I wanted to get the 3.35 radio so i decided to flash to the SPRINT 3.35 rom, to do so i had to relock the phone so i used Titan Re-locker (which may have caused the whole problem) and now I am stuck at the SPL 1.06 screen.
I tried flashing older roms and still no luck.
I am currently with Telus and only flashed the SPRINT 3.35 rom to get the 3.35 radio off it. WHat do i do? I haven't bricked my phone right?
Click to expand...
Click to collapse
Ok there's a WHOLE mess of problems with this post. First of all, if you read correctly in the kitchen thread, radio 3.35.04 is REQUIRED for any 3.x.x rom. 3.27 WILL not work. Second of all, you do not need to relock your phone when installing the 3.35 sprint rom, in fact, that's what caused it to break as the 1.06 bootloader will not flash or boot a 3.35 rom or radio. The only way to fix your problem right now is to flash the stock telus rom and radio using the microsd flashing method. Once that is complete, you need to unlock again with Olipro 2.40, and then run the sprint 3.35 update.
sux 2 B U. I highly doubt it is bt\ricked, you just dont know what U R doing.
This it what I did...
I did not need to relock. I started the sprint update with the phone booted up to the titan in Hard-SPL mode(miltucolor flash screen) . It reboots to the Hard-SPL several times to finish it and may pause several times. I just let it run. Keep an eye on it, it is done when it boots to a regular boot screen. Dont let it finish booting and then manually boot into Hard-SPL (PWR + Camera + reset with stylus) and flash DCD 3.0.4. I did the same process with the alltel update to get 3.37. You will be left with the bootscreens from the Sprint or Altel rom, but booting to DCD rom with 3.37 radio, GPS, exct....

Stubborn bootloader

I previously had a DCD 3.2.6 ROM on my phone, 3.42.40 radio and 2.47 bootloader. Worked just fine. Then I thought I'd flash the latest Alltel stock ROM. At the time, I couldn't find my 1GB MicroSD card. So I downloaded ImCokeMan's 1.06 relocker and relock through USB. It flashes fine, and I am at the bootloader screen. Ready for a stock ROM, right? Well when I open up the RUU to flash the Alltel ROM, it detects my phone, and starts to flash. At 11%, it stops and tells me "Wrong Vender ID" of course meaning the phone is once again CID-locked. So I went and bought another 1GB MicroSD card (~$10) and thought I'd flash it that way. Put my Alltel ROM on the card as TITAIMG.nbh and put it in the phone. Then I got the same CID-locked error on my phone - "Not Allowed". What do I do?!?!
Okay, used bootloader exit utility, got to boot somewhat. I don't know why the bootloader exit utility doesn't work on Vista though.
--Got reset loop without USB connection. Upgrading to 2.47

What did I do wrong?

I have a (Verizon) Titan running DCD 3.0.1 with radio 3.35.04, and the Olipro SPL 2.40. I've been having some difficulty maintaining wifi connectivity and thought I'd flash to a newer ROM in the (probably vain) hope that it'll work better. So I downloaded the bootloader, the 3.42.50 radio ROM, and one of Ryan's light ROMs.
From what I've read, the radio ROM gets flashed first. So I put the radio ROM (TITAIMG.nbh) into the bootloader's directory, renamed it to RUU_signed.nbh, followed the recommended steps, and executed the bootloader. The phone went into the tricolor bootloader and progress showed 8%, and then I was informed that this ROM update utility won't work on this phone. The phone rebooted into my (dcd 3.0.1) ROM with no changes.
I thought I was doing it right, but apparently I missed something. Any tips?
Nobody Important said:
I have a (Verizon) Titan running DCD 3.0.1 with radio 3.35.04, and the Olipro SPL 2.40. I've been having some difficulty maintaining wifi connectivity and thought I'd flash to a newer ROM in the (probably vain) hope that it'll work better. So I downloaded the bootloader, the 3.42.50 radio ROM, and one of Ryan's light ROMs.
From what I've read, the radio ROM gets flashed first. So I put the radio ROM (TITAIMG.nbh) into the bootloader's directory, renamed it to RUU_signed.nbh, followed the recommended steps, and executed the bootloader. The phone went into the tricolor bootloader and progress showed 8%, and then I was informed that this ROM update utility won't work on this phone. The phone rebooted into my (dcd 3.0.1) ROM with no changes.
I thought I was doing it right, but apparently I missed something. Any tips?
Click to expand...
Click to collapse
You are running olipro 2.4 already so bootloader is fine and your phone is already unlocked. No need to do anything with it.
When flashing the rom radio 3.42.50 use the sd card method.
Place the radio .nbh file on root of sd card "2gig or less" that is formatted FAT32. That nbh file needs to have a name of TITAIMG.nbh. Enter bootloader and follow the grey screen instructions.
Then flash Ryan's rom. RUU method or sd method.

Radio ROM Upgrade -> Error [328]

Anyone encountered this error before? It gets to 8% and then phone reboots and I get this on my PC screen. It says Error [328] (see attached image)
I am using Radio 3.37.75 (verizon), and my bootloader shows 2.40 Olipro
Any ideas?
Try this RUU it is version 3.16.4.3.
Yes, thats the version that I am using. I think... when I run it, it says 3.16.4.3 in the window title bar. (see screen shot)
EDIT: I tried it anyways, and I got the same thing. Do I have the right bootloader? Would a different one help?
what are you trying to flash
trying to flash my verizon xv6800 (which has an old dcd rom on it, radio 3.27 i think) to the new radio: 3.37.75.
Then i will flash with a newer dcd or ryan mogul rom.
wildcard said:
trying to flash my verizon xv6800 (which has an old dcd rom on it, radio 3.27 i think) to the new radio: 3.37.75.
Then i will flash with a newer dcd or ryan mogul rom.
Click to expand...
Click to collapse
Just follow my post here and only use the files and Radios that I provide. Make sure you read a few times so you understand, and dont skip anything. Most important based on what I have read in this thread. Use only the radios I provide on my share site and take your time paying close attention.
http://forum.xda-developers.com/showpost.php?p=3687027&postcount=144
Thanks, I'll do it exactly like that. I will keep you posted. I have to get a new micro SD card, I only have an SDHC 8 GB
The radio can be updated via usb. I do it all the time. But it does hard reset the phone in the process.
I would try a newer radio like 3.42.40. http://wiki.xda-developers.com/index.php?pagename=TitanRadioROMs
I got my radio from there and have no problems updating the radio with ruu.
I followed the directions exactly like in Ryan's post mentioned above, (used USB instead of SD card), and it works!
Fully functional. I used Radio 3.42.02 (somewhere I saw that it was recommended over the others, went with it to be safe). Then Flashed Ryan Mogul Rom 2.2 Heavy.
Thanks everyone!
drewcam888 said:
I would try a newer radio like 3.42.40. http://wiki.xda-developers.com/index.php?pagename=TitanRadioROMs
I got my radio from there and have no problems updating the radio with ruu.
Click to expand...
Click to collapse
i have spl olipro-2.40, rom dcd 3.2.6 and want to upgrade radio to 3.42.50 using usb. should i downgrade spl to 1.20 before upgrade the radio? or i stick with current config and update the radio using RUU?
Still cant load radio
Obtained 6800 originally Alltel, not sure which radio, Had Olipro 2.40 installed, would hang on Alltel splash screen.
Could not get any RUU loads to complete (from USB or SD card), usually would fail around 50%.
Eventually was able to get RyanMogul 3.1 Cricket (lite) to load, but shows no radio and eventually screen goes blank. Never goes into active Sync mode.
We force boot loader mode and try and load several radios including Titan_Radio_ROM_3.42.50.Alltel.rar, Titan_Radio_ROM_3.35.04,
but keep Getting error 328 from RUU when I try to load a radio..
tried RyanMoguls "Here is a fix for GPS for all you VX6800 users that gps will not function!!", but cant run relocker because no active sync connection.
Stock Verizon ROM RUU also gets error 328.
Any ideas.

Categories

Resources