I spent all day yesterday researching the DCD upgrade until I thought I was ready - boy was I wrong. I'm not computer challenged! I've been writing FW for over 20 years. Things shouldn't be this hard. Anyway, here's what i did:
1) Downloaded olipro 2.4 (except somehow I got 1.2 - not really sure how that happened). Installed it and everything was fine (expect it saysSPL-1.20.Olipro)
2) Downloaded DCD_3.0.1_Alltel.exe and tried to install. It appeared to work, except I never got to customization screen and when the phone re-booted, I just go the Alltel splash screen.
3) Tried to soft-reset, same problem
4) Tried a hard-reset, same result
5) Went into the bootloader and notice I was at 1.2 instead of 2.4, so I downloaded Hard-SPL-MFG.exe (which I believe is the code name for Olipro 2.4) and tried to run it. The batch job fails because it can't talk to my phone (says no device detected) I suspect this is because the phone cannot run ActiveSync.
6) Then I read that 2.4 should be used for GPS ROMs and not for non-GPS, So I thought I needed a non-GPS version of the ROM. So I downloaded DCD_Titan_3.0.0_Alltel.exe and tried that. This also appeared to work (dl to 100% and the phone reset). But again the phone hung at the Alltel splash screen (now it says "no Radio")
7) I'm begining to panic. I trie to download the original Alltel ROM, but they've just put up a new version. So I try RUU_TITAN_ALLTEL_WWE_3.35.671.9_RS_TITAN_03.37.20_Alltel_2.01_AM_PPST_Ship.exe. It causes the phone to reset after downloading 12%. Then stops with a "Command Error"
8) Finally I decide the bootloader must be hosed, so I tried to use the re-locker. Titan_Relocker.exe. This also will not copy the files (due to no ActiveSync) so I extract the files and try to run the RUU directly. Still no joy, the download immediately goes to 100% and when the phone resets it still says SPL-1.20 Olipro.
9) Searching a little more I found the microSD upgrade option. So I copied each of the NBH files (one at time of course) the the root directory and renamed them TITAIMG.nbh and reset into the bootloader (yes, I formated to FAT32 first). The loader never seemed to even ready the SD. It never asked if I wanted to upgrade.
So, here I am. Stuck with a phone that only seems to be able to run the bootloader. The BL does change between USB and serial when I un-plug and plug the USB cable. I can boot to the Alltel splash screen - it says "No Radio". The other red letters that used to appear when the HTC splash appeared are gone.
Any advice? I'm pretty desparate.
Jerry
[email protected]
Pop Out the Battery for a minute
Have you tried popping the battery out for about a minute while its not plugged in yet?
Your problem is you didn't read the instructions carefully enough.
First, you never should have flashed a 3.x.x ROM without making SURE you properly had the 2.4 bootloader installed.
Second, you tried flashing a 3.x.x ROM BEFORE updating your radio to 3.35.04. It says in numerous threads as well as on the first page of the thread that NO radio is included.
What appears to have happened, is you have a 3.x.x rom installed with no radio, and the 1.2 bootloader which can't even boot 3.x.x roms.
My question to you is, have you ever unlocked this phone before or before all of this were you running stock? If you still have the stock bootloader installed and not 2.4, then you need to find the STOCK alltel radio AND rom. You then must flash the stock alltel radio, followed by the stock rom. All you need to do is plug the phone in with usb, manually enter the bootloader and run the RUU's for each.
Once you get your phone back to stock and it boots, only then continue on to reflash. Now, this is VERY important...DO NOT attempt to install any 3.x.x rom without first making SURE you have the new bootloader installed correctly, and second, running the sprint update to get the 3.35.04 radio installed.
Ranger093 said:
Have you tried popping the battery out for about a minute while its not plugged in yet?
Click to expand...
Click to collapse
Yes, numerous times. Sorryy I didn't mention this in my post.
Your problem is you didn't read the instructions carefully enough.
First, you never should have flashed a 3.x.x ROM without making SURE you properly had the 2.4 bootloader installed.
Agreed, but what is done is done
Second, you tried flashing a 3.x.x ROM BEFORE updating your radio to 3.35.04. It says in numerous threads as well as on the first page of the thread that NO radio is included.
I thought the DCD_3.0.1_Alltel.exe image contained the radio. Obviously I was wrong.
What appears to have happened, is you have a 3.x.x rom installed with no radio, and the 1.2 bootloader which can't even boot 3.x.x roms.
My question to you is, have you ever unlocked this phone before or before all of this were you running stock?
I was running stock.
If you still have the stock bootloader installed and not 2.4, then you need to find the STOCK alltel radio AND rom.
I'm pretty sure I don't have the stock bootloader. It says SPL-1.20.Olipro
You then must flash the stock alltel radio, followed by the stock rom. All you need to do is plug the phone in with usb, manually enter the bootloader and run the RUU's for each.
I've tried the latest stock ROM RUU_TITAN_ALLTEL_WWE_3.35.671.9_RS_TITAN_03.37.20_ Alltel_2.01_AM_PPST_Ship.exe but it re-boots the phone while downloading (@ 12%)
Once you get your phone back to stock and it boots, only then continue on to reflash. Now, this is VERY important...DO NOT attempt to install any 3.x.x rom without first making SURE you have the new bootloader installed correctly, and second, running the sprint update to get the 3.35.04 radio installed.
IF I get the phone back as stock, I doubt I will EVER try to re-flash it again.
Here's the link to the old Alltel Rom and Radio. http://www.htcamerica.net/support/ppc6800/software-downloads.html
If that doesn't work for you, you should be able to load up any of the older 2.x radios with an older dcd ROM, then upgrade to OliPro 2.4, then load the new Alltel Radio and Rom which you already have.
I've had this exact same problem (almost) except with Verizon (shouldn't be any difference whatsoever.) With the "No Radio" error messages and such -- and the key is the microSD flash. The reason it didn't recognize the image is (probably) because of the way you formatted your SD card. It can't be formatted in windows and work, you can't use a quickformat, and it has to be unconditional. The /x dismounts the volume so the volume is totally accessable. /a:512 tells it something about how many sectors to use or something -- idk -- but it works.
Open a DOS window (start, run, type "cmd")
this is your command:
format x: /fs:fat32 /u /x /a:512
Replace x: with the drive letter of your microSD card. Be sure of this.
Other than the drive letter type it exactly as is says.
1. Run the titan relocker.
2. Rename the stock alltell rom(s) as TITAIMG.NBH one at a time if there is more than one (radio and rom, unless they are together) and put them on your microSD one at a time (in the root directory.) Order shouldn't matter, but I ran ROM then Radio. Open bootloader and make sure it's not Olipro. The screen should pick up the image on the microSD card.
Flash, after 100% remove the battery, replace, and then hard reset.
These are the steps that I took with my Verizon issue and it worked perfectly.
Once this is done don't give up on the modified ROMs. Sometimes when I upgrade friends phones it won't let me go directly to 2.4 Olipro. I have to flash 1.2, then a 1.2 compatible RADIO and 1.2 compatible ROM. Then I have to flash to 2.4 unlocker, 2.4 compatible radio (usually 3.27) and then a radio 3.27 compatible ROM (pref. DCD 2.3.2.) After which, I can flash the stock Sprint 3.35 (without ever booting the OS) and then flash the DCD 3.x.x ROM.
Hope this helps you out --
I've tried the latest stock ROM RUU_TITAN_ALLTEL_WWE_3.35.671.9_RS_TITAN_03.37.20_ Alltel_2.01_AM_PPST_Ship.exe but it re-boots the phone while downloading (@ 12%)
Click to expand...
Click to collapse
The latest stock alltel rom is a 3.x.x rom as it states in the file name...3.35.671.9
As I said before, you need the 2.4 bootloader to boot any 3.x.x roms.
If you have unlocked with 1.20, then you have a little more work cut out for you.
This is what you need to do:
Since you have 1.20 and you can't get an activesync connection, you need to first flash an old custom alltel rom (NOT the stock alltel rom). DO NOT flash any dcd 2.x.x rom as the poster instructed above as it also requires olipro 2.4. I believe if you search for dcd's 1.70 kitchen and roms you'll find one there. You also must flash radio version 1.40. THIS will allow you to boot up into windows mobile and finally get an activesync connection. Since you can't boot right now, your best bet is to flash both of these with the microsd card.
The next step is now that you can boot into windows and have an activesync connection, you need to RELOCK your phone using the titan relocker, follow the directions carefully...and if you get stuck in the bootloader after the relock, you need to use the titan exitbl application that will force you out of the bootloader.
If all is well you now should have olipro 1.06 (stock bootloader) back on the phone. Here's the catch, you won't be able to boot the 1.70 rom anymore...so now you must manually enter the bootloader (power+camera+reset) and NOW flash the stock alltel rom and radio again with the microsd card. Once you flash the stock rom and radio, you will now have the stock bootloader, stock rom, and stock radio.
Now just unlock with olipro 2.4 and MAKE SURE it is on there correctly. Then run ROM RUU_TITAN_ALLTEL_WWE_3.35.671.9_RS_TITAN_03.37.20_ Alltel_2.01_AM_PPST_Ship.exe which DOES include the 3.37.20 radio as it also states in the file name. After that, you are free to flash a dcd alltel rom, as you will already have the proper bootloader and radio.
gcincotta said:
DO NOT flash any dcd 2.x.x rom as the poster instructed above as it also requires olipro 2.4.
Click to expand...
Click to collapse
excuse me, but if you read my directions in order, that's not what it says to do in the section about fixing his current situation.
AND,
If you carefully read what I had to say about future upgrades:
"...Then I have to flash to 2.4 unlocker, 2.4 compatible radio (usually 3.27) and then a radio 3.27 compatible ROM (pref. DCD 2.3.2.)"
In no way do I mean to flame, but please read.
Thank you kindly
dizwayney said:
Here's the link to the old Alltel Rom and Radio. http://www.htcamerica.net/support/ppc6800/software-downloads.html
If that doesn't work for you, you should be able to load up any of the older 2.x radios with an older dcd ROM, then upgrade to OliPro 2.4, then load the new Alltel Radio and Rom which you already have.
Click to expand...
Click to collapse
Thanks dizwayney. This was the link I needed. From here I was able to re-flash the original Alltel 2.14 ROM and radio. It is back to it's old self (well - except for all my data).
Oddly enough it still says SPL-1.20.Olipro for the bootloader. Oh well, as long as it boots I really don't care.
One other thing I learned during this adventure. You can't flash form a 4GB microSD, it must be 2GB or less (in order for the 512 byte allocation to work). If I'd known this earlier it might have saved a lot of time.
Again, thanks to everyone who responded.
In no way do I mean to flame, but please read.
Thank you kindly
Click to expand...
Click to collapse
I strongly suggest you take your own advice and read, because I wasn't even referring to you. I was referring to the post before yours.
Cheers
Related
FIXED! Read below for details.
So i've been messing with my mogul for nearly 4 hours now trying to convert it to dcd's rom..and i've flashed it twice now and after it reboots from being 100% loaded it just sticks on the HTC black screen..I've read and read and searched and searched and cannot find a definite answer. Can anyone help?!
basics?
did you load the radio rom?
did you load the unlocker?
you may need to restart the phone to the boot loader and resend the rom
(press and hold camera and power and push reset button)
I did TRY and reload the radio and unlocker..now im stuck at the black htc screen where it says no radio though. bleh. i can't even get it back up and running. what do i do?
edit:
I'm at the multi color screen..ive tried running the unlocker RUU and then running dcd's ruu and it doesn't work..and the radio RUU does not run at this screen...I can't get the phone back to a working status! Argghhhh. It wont let me run the relocker unless im in activesync...but i can't be recognized in activesync unless the phone is up and functional..so..? how do i relock it to put hte stock rom on to try and unlock again?
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
what i dont get is..i flashed it with the unlocker, then the rom then the radio...isn't RUU just overwriting each one or something? it doesn't make sense to me. and all i can do is run RUU..i did the rom, then the radio and it was stuck in the bootloader so i used the exitbl and got out of it but then it just went back to going to the HTC black screen saying no radio. ..i'm gonna try and flash the rom from a sd card next..we'll see what happens..
jkrolcz said:
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
Click to expand...
Click to collapse
This just happened to me after flashing the ROM but not the RADIO yet. Flashing the Radio fixed the problem.
I've flashed the radio..then its stuck in the BL and i use the program to get me outta it then it just keeps saying i have no radio! what the hell..this sucks. i'm in the worst possible situation to have to buy a new phone
There are three parts to the "operating system" of your phone.
1. Bootloader (also called locker, unlocker, re-locker, SPL)
2. Radio
3. ROM
The three components are saved in discrete portions of the device's memory. Flashing one does not overwrite the others. All three must be compatible for the phone to operate properly. If you stop the upgrade process recommended by the ROM compiler prior to completion, your phone may not operate properly. If you flash the "leaked" 3.16 ROM package, it contains all three components.
To use the 3.16 stock OEM ROM, or a custom ROM based on the stock OEM 3.16 ROM, you must have a level 3.xx radio and a level 2.xx bootloader. The current implementations of those are the 3.27 radio and either the stock bootloader distributed with the "leaked" 3.16 ROM package, or the Olipro 2.40 unlocker.
If you are running a level 2.xx stock OEM ROM, or a custom ROM based on a stock 2.xx OEM ROM, you must have a level 1.xx bootloader and a level 1.xx radio.
Custom ROMs are not always named using the OEM convention, so you must research the custom ROM to determine whether it is based on a level 2.xx or 3.xx stock OEM ROM.
I hope this helps all of you get your phones back up and running.
FIXXXED!
So heres the best description I can give of what was going wrong for me..Its my first time trying flash to a different rom..and well it didn't go so well. First, I used the titan unlocker, then installed the radio (not sure which one) and then some form of the newer dcd rom and i was getting stuck on the black HTC smart mobility splash screen where it said "no radio". I had to have messed around for over 5 hours today at college trying to figure it out by doing different arrangements what order i installed the radio and unlocker and rom in. I couldn't get it to connect with activesync so i couldn't use the titanunlocker.exe..all i was going off of was RUU's. Im not sure whether or not what OS I was using effected it..I was playing in Vista earlier today but had done the correct steps to install the drivers, and now this last time i did it on XP. This last time I ran the 3.27 radio RUU as found.. here ( http://forum.xda-developers.com/showthread.php?t=362563 )...Theeen I ran this form of the newer sprint ROM. (I'm pretty sure they say it comes with a included in this RUU, but i'm just stating exactly what I did) the .651 rom can be found.. HERE ( http://forum.ppcgeeks.com/showthread.php?t=16806 ) He had a error when packing or something so you have to manually rename it to .exe because it was missing a e..I did this within winrar before extracting..ran that and about 10 minutes later it booted up and i've got service. I'm not going to promise that this is 100% functional all i'm saying is im out of that horrid black HTC screen where I can now go on to try and get the correct rom i wanted. Hope this helps..may be a bit confusing and probably did things wrong but this was my first time doing it all.
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.
Hi there, I have very minimal experience with this stuff so I will provide as much detail as possible...
I had previously successfully programmed my HTC6800 back in March by unlocking with Olipro 2.4, then I flashed the radio with 3.27 and used dcd 2.3.2 for Bell on it. Now my memory is a little foggy as that was several months ago however I made it through the process fine. This encouraged my to try to update again today. I tried following the steps in the wiki as I could not find the guide I had used previously. I already had Olipro 2.4 so I was good at that step. I then tried running the newest radio update and it would not take. It gave me an error. I reset the phone and tried several times but to no avail. I then tried putting on dcd3.2.0 which went fine. THe phone rebooted and I made a test call and everything was fine. I however wanted the new radio update still so I thought I'd take another crack at it... it still would not update. In the wiki it said about relocking the phone and putting it back to the factory ROM and starting again. So I did this, I downloaded the relocking util and followed the instructions to relock the phone. That went fine... Olipro is gone and is shows the 1.06 like it's supposed too... next it said to put the factory ROM back on... well, I am will Bell and the link for the factory ROM is dead! I can't get it anywhere!!!
So currently my 6800 sits as the 3 colour screen with 1.06 relock on it and does nothing else. It has radio 3.27 on it and dcd 3.2.0.
Is there any way to fix this?????
Run this first to exit the bootloader and get into windows mobile. Then check out which rom you are on (I think you were on dcds rom). Then load radio via sd card method listed in the wiki. Then reload dcd if you are not already on the version that you want.
P.S. I have heard things about that ROM that it caused problems. You may want to read up on that here.
Nope
Well, I downloaded the file and tried running it but to no avail. It just comes up saying that the application failed to start because RAPI.DLL is missing.
Also
I tried running that app on a Vista machine as well and it just says that it can't open the USB port. However, windows found the device and installed a driver for it when plugged in AND it shows USB on the bootloader screen when plugged in.
ok..,. let me see...
try installing olipro 2.40 again, it seemes that your phone is locked (olipro 1.06) so it can't run the dcd custom rom... reset and see if you can enter windows...
then if you enter windows normally, downgrade to olipro 1.20 and install the new radio, then, once again upgrade to olipro 2.40 so it can enter windows...
let me know if it worked for you...
Evo69 said:
well, I am will Bell and the link for the factory ROM is dead! I can't get it anywhere!!!
Click to expand...
Click to collapse
Install another carrier's stock ROM (though to keep things easier avoid the Telus one as it doesn not include a radio ROM) and avoid letting it run any customisations after boot/screen calibration.
You are fine.
Here's the problem
OK. Here's the problem. I obviously misread the instructions on setting the unit back to stock as I just read them again and I realize my mistake. I did not load the stock ROM on first. I used the Re-lock program and re-locked my unit before putting the stock ROM back on. So I sitting at the 3 colour screen with SPL 1.06 and I have radio 3.27 on the unit and dcd's latest ROM on it. I can't get it past the 1.06 bootloader. I have tried a hard reset, I have tried the program above to exit the boot loader and it does not work. Is there any way I can get Olipro 2.4 back on or exit this bootloader???
just connect your phone to the computer (it's ok to be on the tri color screen) and install olipro 2.40 from the computer...
you just need to be sure that when you connect the phone in the tri color screen it says USB...
i'm attaching Olipro 2.40
No Dice
Nope. I had tried that already. I just tried again. When I run Olipro 2.40 the command prompt comes up and then come up with a window saying "Cannot Find Device" (or something VERY close to that). It then asks if you'd like to retry, clicking retry just keeps bringing up the same message. If you click "No" on retrying it will eventually move on to the next step and load up the flash program. It will then attempt to flash the unit (Grey screen with the status bar comes up) but it just sits at 0% and eventually comes up with a 242 communication error.
i had a similar problem yesterday when i tried to upgrade the radio form 3.42.02 to 3.42.30 and taht solved my problem...
so you basically cannot exit the bootloader mode?? even when you hard reset your device??
Can the unlocker be flashed from a memory card? Has anybody ever tried?
Evo69 said:
Nope. I had tried that already. I just tried again. When I run Olipro 2.40 the command prompt comes up and then come up with a window saying "Cannot Find Device" (or something VERY close to that). It then asks if you'd like to retry, clicking retry just keeps bringing up the same message. If you click "No" on retrying it will eventually move on to the next step and load up the flash program. It will then attempt to flash the unit (Grey screen with the status bar comes up) but it just sits at 0% and eventually comes up with a 242 communication error.
Click to expand...
Click to collapse
I have the Bell ROM if you're looking for it.
TS
I didn’t think it was possible to flash back to a stock Bell (non-GPS) rom/radio after flashing to a GPS radio.
Does anyone know if it’s possible to flash the SPL (bootloader) from an SD card?
No2chem over at ppc geeks has a new SPL that loads from the device, but it needs be running.
http://forum.ppcgeeks.com/showthread.php?t=30561
jhamilton said:
I didn’t think it was possible to flash back to a stock Bell (non-GPS) rom/radio after flashing to a GPS radio.
Does anyone know if it’s possible to flash the SPL (bootloader) from an SD card?
No2chem over at ppc geeks has a new SPL that loads from the device, but it needs be running.
http://forum.ppcgeeks.com/showthread.php?t=30561
Click to expand...
Click to collapse
I haven't tried to do it yet, but I did develop a theoretical how to before I first flashed my phone as I wanted to make sure I had a way out. You can find it here:
http://forum.xda-developers.com/showthread.php?p=2017265&highlight=bell#post2017265
YES
Timeshell said:
I have the Bell ROM if you're looking for it.
TS
Click to expand...
Click to collapse
Ya, if you can post attach that file to a posting on here I would appreciate it. If you need an alternative method of send the file to me just PM me and I will figure something out.
Keystone said:
Install another carrier's stock ROM (though to keep things easier avoid the Telus one as it doesn not include a radio ROM) and avoid letting it run any customisations after boot/screen calibration.
You are fine.
Click to expand...
Click to collapse
I tried using a Sprint one... it would not work.
Timeshell said:
I haven't tried to do it yet, but I did develop a theoretical how to before I first flashed my phone as I wanted to make sure I had a way out. You can find it here:
http://forum.xda-developers.com/showthread.php?p=2017265&highlight=bell#post2017265
Click to expand...
Click to collapse
Yeah I've heard some horror stories when it came to downgrading, including a few bricked devices.
http://forum.ppcgeeks.com/showthread.php?t=26082
I would be interested to know if anyone on Bell has managed to successfully downgrade a 6800 to stock.
i thought dcd's new 3.2.0 needed a radio of 3.35 or higher to run and does not flash the radio when u flash his rom. Another problem with the phone not coming out of the bootloader is that you have to disable usb connections in active sync or windows mobile device center for the exit bootloader app to work. Try disabling the usb connection in whichever one applies for you and run the app again. If you can get out of the bootloader try to go back to ollipro 2.40 or use one of no2chems bootloaders as they work from the device and an sd card no need for a pc to flash the bootloader. once bootloader is unlocked again run a full radio/rom update like the sprint stock 3.35 easily found on htc's website under the titan (us version of the site). Don't let the carrier custimizations run ... the file that runs after u calibrate screen and set timezone just pull the battery. Then grab whatever rom / radio you want to or were trying to flash 2 before and name it put it on the root of an sd card (thats under 2gb and formatted to fat32) and rename the ruu_sighned.nbh file to TITAIMG.nbh hold power + camera and hit your soft reset button. The tri color screen will come up and should say loading then promt to hit the power button to flash and show u what u r flashing. cdma (radio). os (radio rom) or splash screen, or whatever you r trying to flash hit power button to start once done it will sit with update complete on the screen pull the battery out for about 30 sec and put it back in reboot and enjoy the custom rom or radio.
kdj67f said:
Can the unlocker be flashed from a memory card? Has anybody ever tried?
Click to expand...
Click to collapse
You can use nueSPL 2.47 to load the locker/relocker but you need to be booted into WM6 to do so. You need to reload another rom that uses the bootloader you have currently loaded and then you can move forward or backward.
Evo69 said:
Ya, if you can post attach that file to a posting on here I would appreciate it. If you need an alternative method of send the file to me just PM me and I will figure something out.
Click to expand...
Click to collapse
Uploaded to Rapidshare
http://rapidshare.com/files/1271390...3.666.1_RS_1.37.30_BM_1.27_0604_SHIP.zip.html
TS
Before I start I did searches and looked at all the posts that apply to this situation and could not find anything. After spending many hours searching decided to try posting.
Situation:
I have a Verizon xv6800 that I am trying to update so I can have GPS. The first thing I did was to flash the OLIPRO 2.4 ROM. After the flash was complete everthing seemed OK but the power button no longer worked to turn the phone on. Also if you called the phone it would not ring.
The next thing I tried was to use an SD card to load nuespl 2.47. Again everything seemed OK but the power button still did not work.
Then I loaded OLIPRO 1.2 ROM and now everything seems work perfectly including the power button.
The boot screen verifies that the OLIPRO 1.2 is loaded.
Now I am confused as to which radio I should be using since the "Step by Step tutorial for unlocking your device and cooking your own ROM!!! " post said not to use OLIPRO 1.2.
Can any body tell me the next steps I should do to get an upgraded radio?
Please make it simple since obviously I can't figure it out myself.
Thanks for any assistance.
karter said:
Before I start I did searches and looked at all the posts that apply to this situation and could not find anything. After spending many hours searching decided to try posting.
Situation:
I have a Verizon xv6800 that I am trying to update so I can have GPS. The first thing I did was to flash the OLIPRO 2.4 ROM. After the flash was complete everthing seemed OK but the power button no longer worked to turn the phone on. Also if you called the phone it would not ring.
The next thing I tried was to use an SD card to load nuespl 2.47. Again everything seemed OK but the power button still did not work.
Then I loaded OLIPRO 1.2 ROM and now everything seems work perfectly including the power button.
The boot screen verifies that the OLIPRO 1.2 is loaded.
Now I am confused as to which radio I should be using since the "Step by Step tutorial for unlocking your device and cooking your own ROM!!! " post said not to use OLIPRO 1.2.
Can any body tell me the next steps I should do to get an upgraded radio?
Please make it simple since obviously I can't figure it out myself.
Thanks for any assistance.
Click to expand...
Click to collapse
Ok no worries about the newbie thing. We all were newbies at one time!
First it sounds like the 2.40 flash did not completely go well. So since you are back to 1.20 I would upgrade in this order:
1) First update your radio to 3.42.50. This is the latest radio and seems to help with phone service issues. At least that is what I have seen. You will need the RUU install files so I attaching RUU.zip for this. Unzip this and then when you download the upgraded radio drop that file into this directory and then flash. If successful your phone should display 3.42.50 at boot time.
2) Next upgrade to 2.40 of the unlocker. I am attaching the install I use, so unzip the file and then run it to install/upgrade your phone. If successful your phone should show 2.40 when done.
3) Now you are ready to persue a ROM or kitchen that is GPS capable. There are many of them. I am currently using DCD's 3.26 kitchen but No2Chem also has a 5067 kitchen that is very stable. If you have questions about this process do not hesitate to email me at [email protected].
Steve
I did step one and everything seemed OK. Took several minutes with progress bar and exited normally. The boot screen indicates 3.42.50 as per instructions. But now the phone gets stuck at the white verizon screen. Should I proceed to step 2?
Thanks
Ken
karter said:
I did step one and everything seemed OK. Took several minutes with progress bar and exited normally. The boot screen indicates 3.42.50 as per instructions. But now the phone gets stuck at the white verizon screen. Should I proceed to step 2?
Thanks
Ken
Click to expand...
Click to collapse
Take the battery out and then put it back in. It should boot then. Go to step 2 then.
Steve
Took battery out waited 1 minute and replaced battery. Still stuck at white screen.
Ken
karter said:
Took battery out waited 1 minute and replaced battery. Still stuck at white screen.
Ken
Click to expand...
Click to collapse
Move on to step 2. Quick question...is the current ROM the stock VZW ROM or one from XDA?
Steve
Actually he gave you the instructions backwards. (Tho his method may work, it's just not what the Wiki says to do) You always update the bootloader first, then the radio, then the rom. The new radio requires a new bootloader (hence why it's locking up), go ahead and reinstall BL2.4, if that doesn't work, see if you can find an older non-gps radio, and flash it via the SD card. Once you get back to either an old bootloader and old radio, or a new bootloader and a new radio, then you will have better success getting the rom flashed.
You were fine actually with your original 2.40 install, it will boot once normally, however as soon as it goes to sleep or you turn it off it won't turn back on, a soft reset will get it back up, but it will keep crashing. So at that point you can flash the radio and ROM from the Bootloader screen.
If you can get 2.40 (actually get 2.47 if you can, worse case use 2.40 and upgrade the radio and rom to the new version, then run 2.47 from the pocketpc and it will update you to 2.47 (I just did this yesterday).
So reflash to 2.40 if you can, otherwise do some searching for an old radio (non-gps) and flash it.
Then go back and re-read the wiki, it tells you that you have to flash the bootloader, then the radio, then the rom. It's always in that order for a first time flash. Once thats all done, any future updates should only require a single flash (for radio or rom).
BTC
BillThyCat said:
Actually he gave you the instructions backwards. (Tho his method may work, it's just not what the Wiki says to do) You always update the bootloader first, then the radio, then the rom. The new radio requires a new bootloader (hence why it's locking up), go ahead and reinstall BL2.4, if that doesn't work, see if you can find an older non-gps radio, and flash it via the SD card. Once you get back to either an old bootloader and old radio, or a new bootloader and a new radio, then you will have better success getting the rom flashed.
You were fine actually with your original 2.40 install, it will boot once normally, however as soon as it goes to sleep or you turn it off it won't turn back on, a soft reset will get it back up, but it will keep crashing. So at that point you can flash the radio and ROM from the Bootloader screen.
If you can get 2.40 (actually get 2.47 if you can, worse case use 2.40 and upgrade the radio and rom to the new version, then run 2.47 from the pocketpc and it will update you to 2.47 (I just did this yesterday).
So reflash to 2.40 if you can, otherwise do some searching for an old radio (non-gps) and flash it.
Then go back and re-read the wiki, it tells you that you have to flash the bootloader, then the radio, then the rom. It's always in that order for a first time flash. Once thats all done, any future updates should only require a single flash (for radio or rom).
BTC
Click to expand...
Click to collapse
The issue with reversing steps 1 and 2 is that the Olipro 2.40 does not allow the ability to update the radio ROM. You have to back down to 1.20 and then do the radio. That has been the case for the last two radios I have upgraded to. So that is why I put it in the order I did.
Steve
Ah ok, well, I had 2.40 installed for over a month and have updated my radio 3 times (tho I did it via SD card), I assume you meant it doesn't work via USB (and I remember now seeing posts that talked about that)
I stand corrected. His way should work. Just the phone will not boot properly until all 3 items are updated to GPS compatible files, BL 2.40+ Radio 3.42+, Rom 3.x. Prior to all 3 being updated tho, you should be able to flash from the bootloader, so boot into it and flash from there until all 3 are updated.
Once all 3 are flashed, your phone should work normally.
BTC
BillThyCat said:
Ah ok, well, I had 2.40 installed for over a month and have updated my radio 3 times (tho I did it via SD card), I assume you meant it doesn't work via USB (and I remember now seeing posts that talked about that)
I stand corrected. His way should work. Just the phone will not boot properly until all 3 items are updated to GPS compatible files, BL 2.40+ Radio 3.42+, Rom 3.x. Prior to all 3 being updated tho, you should be able to flash from the bootloader, so boot into it and flash from there until all 3 are updated.
Once all 3 are flashed, your phone should work normally.
BTC
Click to expand...
Click to collapse
Yes via USB since SDHC cards are not supported and I do not have a regular SD card. I really should buy one...they are cheap now.
Steve
I reloaded the original radio using a sd card and now the phone works again. Can I load OLIPRO 2.40 using a SD card? If so how.
Thanks
Ken
Not that I am aware of (tho I don't know everything....), I flashed 2.4 from my PC via activesync, let it reboot, and then had to run out and get a flash card and flash card reader (in order to format it correctly) then was able to flash the radio, and then flashed the rom via Activesync. (I just remembered that I had to flash my radio from SD card, I had completely forgotten until I stopped to remember why I bought the memory card reader)
If you have it working with your old rom, then I would copy 2.47 BL over to your phone in windows and run it, it will flash the bootloader for you (tho it requires a preformatted SD card (not SDHC)). It will offer to format it for you if you can't get it formatted correctly yourself. If it's already in the right format, it doesn't have to be empty as it will just copy the file, reboot, and delete the file automatically. If it's not in the right format and you have stuff on it already, copy it off to your harddrive, then put it back in and it will format it for you. Once it's formatted correctly, it will still work normally in the phone and on your PC, so it's worth it to get the SD card into the right format.
Once 2.47 is installed, boot into BL mode (camera, power and reset button), and then do the rest of the flashing over USB. It will auto-reboot after each flash, so keep going back into BL mode until after you get the rom flashed. Then let it boot normally, LET IT RUN CUSTOMIZATION (pending you are installing DCD's rom) If you are installing another carrier's rom, then never let customization run (unless it's your carrier). Once customization is done running, install your carrier's cab file, this is pretty important or the phone won't properly work, I would do one more soft reset and at that point your phone is all ready to go and you can set it up, and install your programs.
BTC
Billy the Cat
I wish I had known that the power button wouldn't work untill all three steps were complete. Because of that I got concerned that I may have screwed up the phone and started trying all sorts of things to fix it (probably making it worse in the process).
Now that I know how to get back to the original ROM & Radio if something happens I will try again to get the GPS working.
Thanks Billy the Cat and stevefxp
Ken
No problem. I was like you the first time I started to flash my phone, I had just gotten the BL installed and then had to leave, my phone wouldn't stay running so my wife got extremely mad at me because she would call and since the phone wouldn't turn on it would go to VM. It took me a while to get her to appreciate my phone again, til then it was "A huge waste of money" in her opinion.
Since then tho, I have shown her the great features of being able to search for an item on ebay when we are at an auction to get an idea of a item's value before bidding, been able to take pictures and email them to her at no cost (old phone was $.25 per message), and having the GPS makes it much easier to find some of these remote auction locations we go to.
So after all that, shes not screaming at me for buying the phone anymore, tho she still isn't happy I spent the money. Oh well, she fritters more money away than I do, so I don't have a problem buying something that will last me for 2 years with the amount that shes frittered away in a week many times.
BTC
I am still having the same problem with the white Verizon screen. These are the steps I took.
1. Reloaded the original radio 1.30.60 using the SD card approach
phone worked
2. Reloaded the original ROM 1.6.7
phone worked
3. Loaded nueSPL-2.47 using the sd card
Red/Blue/Green screen had:
TITA100
SPL-2.47No2Chem TITAN SPL EVT
CPLD - 9
4. Loaded radio 3.42.50 using the SD card
Verizon white screen has
M 09 P DCAAXOM - 4350
H3B60775B R 3.42.50
D 2.17
The phone now still hangs at the white Verizon screen. I really thought I knew the process but clearly I still do not understand something.
Any help??
every thing is ok, load a gps compatible phone rom like dcd 3.2.6 using the cd card method and it will work after that
I have the 3.2.6 kitchen downloaded from DCD1182 but I can't find the nbh file unless it is the RUU_signed.nbh file and I just have to rename it to TITAIMG.nbh
If that's not it where can I download the 3.2.6 nbh file.
Thanks
Ken
karter said:
I have the 3.2.6 kitchen downloaded from DCD1182 but I can't find the nbh file unless it is the RUU_signed.nbh file and I just have to rename it to TITAIMG.nbh
If that's not it where can I download the 3.2.6 nbh file.
Thanks
Ken
Click to expand...
Click to collapse
That is it.....
You guys are great. The phone is working again and has radio 3.42.50 and ROM 3.2.6 on the white screen so I guess everthing is correct now.
I also loaded the Verizon CAB to get internet and reprogrammed the phone with *228
I have one last question. What happened to the battery indicator in the upper right hand corner?
I really appreciate all the help you guys gave me. I read all the instructions but knowing nothing about what I was doing there is some information that would have been very helpfull if I had only known.
1. If you get in troubble you can reload the original radio and ROM to get the phone working again.
2. You really need to complete all the steps before you can expect the phone to work properly. I kept trying to test the phone at each step to make sure that it still worked. This approach got me in all kinds of trouble.
3. Don't panic if something doesn't seen right just ask the experts on this board. They have a wealth of knowledge on how to get out of trouble.
4. Make sure you have a micro SD card on hand before you start.
5. While it didn't answer all my questions read the WIKI flashing documentation completely before you start.
Again - thank you everyone for helping me to get my phone upgraded.
Ken
you can get the battery by changing the registry.
hklm/software/microsoft/shell/showtitlebarclock.
not sure what all the setting do. mine is set to 0 and i have the battery icon.
alternatively you can use htc home customizer to change the value for you.
Hi I'm looking for some help. I tried upgrading my XV6800 to the windows 6.5 rom but I think I might of messed up. I tried to update my radio first but ran in to issues.
I used Oilpro 1.20 to try and tried to update the radio but along the way messed up while trying an older rom and I'm currently at a Verizon screen with the message "NO RADIO" at the bottom. I'm assuming the radio rom was erased. I might have gotten confused with the roms and used a rom without the appopriate Radio. When I try to flash that rom back to a stock Verizon upgrade it just ends 11% in to the flashing process and the rom update utility returns a Error 290 screen.
Currently I can get the oilpro 1.20 bootloader to still load up but I'm not sure what to do at this point. I tried updating the ROM to DCD's older 3.20 roms, which did complete but I still have that screen coming up. Can anyone give me some suggestions on what I should do next? Any help would be greatly appreciated.
Try using NueSPL 2.47 it's more current
Doesn't have have to be run on the phone itself once inside Windows? The only screen I can get up is the Verizon (splash) screen where it normally lists the rom and radio, or the oilpro boot loader screen. I actually can't get back in to windows to run the nueSPL 2.40.exe file.
Is there a way for me to flash the radio back from a bootloader screen and USB or SD card? The thing is I actually tried to take the 3.42.40 radio and use the Flash Rom Utility to see if it would flash the radio rom back on but even though the process completes successfully, I still get the no radio error so I guess it doesn't work. Thanks for the help, I think I may have been a few of the idiots out there who screwed things up and didn't make sure the radio was up before attempting any rom upgrade.
You should've changed the bootloader first. Your radios that you are trying are not compatible with your bootloader.
Flash an old stock rom via SD, then update your bootloader to 2.47 once you can get back into windows, then update your radio, and then your rom.
Yeah that was one of the first things I've tried a USB update back to the stock Verizon 6.1 ROM, but for some reason it prematurely ends at 11% with the PDA Phone Update Utility throwing a ERROR 290 message. This is the first time this has happened as I've flashed with this same rom tons of times. I've been looking online for the past hour on how to flash the ROM from a SD card if I can't get in to Windows. But all I could find was the USB update utility and it ends at 11% Am I doing it wrong? any ideas would be greatly appreciated.
If you can still get in the bootloader then you should be fine....I would put it manually in bootloader holding power and camera simultaneously and poke the hole to get it into bootloader.
Once you do that plug in the data cable and run Olipro 2.40 or Nue 2.47. It should be able to take after that.
Basics steps to flashing a phone:
correct unlocker-->stock ROM-->custom ROM
Most custom ROMs will not include Radios that why you would run the stock ROM first to install the radio and then run the custom ROM. Alot simpler then trying to update the Radio by itself.
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Beyond888 said:
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Click to expand...
Click to collapse
Glad to hear you got your phone back up
As far as I know you should be able to just install 2.47 and it will overwrite your old bootloader without problems. I could be mistaken but there isn't really a way to "uninstall" a bootloader, just overwrite it with a different one.
unL33T is correct...just run Nue 2.47 and let it overwrite the old one. 8p
Yeah that's what I thought too, but when I tried to over right it with 2.47 the 1.20 showed up again so I used the titan_relocker tool. Maybe I did something wrong. I'll go recheck, thanks for the replies guys.