After reading somebody's post recently that 3.39 had a better lock I thought to try it out in comparison to see for myself (mostly to dispute).
I tried to flash this .nbh file here, but it wouldn't take. I tried reformatting the card, renaming to ensure it wasn't TITAIMG.nbh.nbh, re-extracting and renaming, everything I would do for it to work in the past.
I even tried all of the above with 1.20 bootloader with no success. Is there something preventing me from loading this particular file from where I am (3.2.2 with 3.42.30)? I would like to compare for myself and have the ability to flash from whatever to whatever.
Is this a bad file? I thought it used to work fine.
Try this one.
http://www.cinconet.org/titan/radio/Titan_Radio_3.39.10.rar
gc14 said:
Try this one.
http://www.cinconet.org/titan/radio/Titan_Radio_3.39.10.rar
Click to expand...
Click to collapse
I can always count on you gcincotta (I put your throwback jersey on today).
I will post with results.
This is weird
Ok, so 1.20 won't update back to 2.40, not sure why but it recognizes it in activesync with the OS, goes through the cmd window ok, but has an error in the RUU stating that there is a problem with the connection.
The only thing that I can think of is that one time I began the nueSPL update but did not finish as the card that was in was a sdhc so I cancelled out before it asked me to commit. Not sure why that would have been a problem as it didn't complete the flash and never showed the bootloader at 2.47, it has always been 2.40.
Any thoughts on how to clean up the bootloader?
Should I go ahead to nueSPL 2.47 (FYI I am on Verizon)?
Not really worried at this point, but would like to get at least 2.40 back on the phone for the next ROM/Radio upgrade. This could be why radio wasn't flashing, right?
Wait, so you have 1.20 on?
gc14 said:
Wait, so you have 1.20 on?
Click to expand...
Click to collapse
Correct, wanted to rule that out and have had no problem upgrading back to 2.40 until now.
Are you trying to update to 2.40 or 2.47?
gc14 said:
Are you trying to update to 2.40 or 2.47?
Click to expand...
Click to collapse
I have heard that I should stay away from 2.47 for now, but if I cannot load 2.40 I am game. I wonder if I have some freaky bootloader situation due to the mix of 2.40 and some effect caused by the loading of a temporary 2.47 SPL.
I think my preference would be 2.40, but I would still like to test radio 3.39 eventually. I definitely want to get out of 1.20 at this point.
I'm running 2.47 with no issues. In fact, it's performing better....
gc14 said:
I'm running 2.47 with no issues. In fact, it's performing better....
Click to expand...
Click to collapse
That is what DCD proved on ppcgeeks, I just heard from Azclown that no2chem was testing for downgrading to non-GPS roms 1.x and such. I will proceed to 2.47 then. Can I test 3.39 on that?
Yes, 3.39.10 should be fine on 2.47
gc14 said:
Yes, 3.39.10 should be fine on 2.47
Click to expand...
Click to collapse
Couldn't load 2.47 from 1.20, but finally got 2.40 from my laptop to stick. No boot loops, but 2.47 still won't load as it goes straight to "serial" similar to what happened with trying to load .nbh files. The only time I can get any other result is to force bootloader with no image file and it briefly states that there is no valid image file then quickly reboots.
Weird thing is that it keeps saying SPL-2.07No2Chem Titan SPL EVT CPLD-9 (yes, that says 2.07, not 2.47). It loaded the temporary SPL of the relocker version, but that wont stick if I reboot and force bootloader. It goes back to 2.40 again. What's up with that?
This card used to work great, now maybe it is one of the cards that doesn't work to flash? This is certainly an imperfect science LOL
Thanks again GC.
How are you trying to load 2.47? 2.47 can only be run with microsd, and you must have the card inserted while running the unlocker from your device. For example, the executable needs to be in Device Storage, and the card you're using to flash has to be inserted. That's the ONLY way to flash 2.47.
Question..... Is your card formatted to fat32 with a 1024 or less cluster size. I had to format mine via dos to adjust my cluster size that low. XP won't let me set it that low thru their format interface. Not sure if your's is set that way yet or not. If so, tell me I'm an idiot and I'll go away
Nue2.47 automatically detects if the card is formatted right, and will format it for you if it's not right.
Well isn't that just easy now. Thanks for the info I hadn't messed with 2.47 or even looked into it.
lllboredlll said:
Well isn't that just easy now. Thanks for the info I hadn't messed with 2.47 or even looked into it.
Click to expand...
Click to collapse
I have been fooling with this and this is what I have found (to my chagrin so far)...
Whether I put the .exe on the device or on the card I still hang at 2.07 "serial" bootloader, it doesn't try to load the new bootloader image.
Whether I format FAT and let it reformat, or format via cmd (format D: /FS:FAT32 /A:1024), or format using windoze default fat32 settings, it still hangs at the 2.07 "serial" screen.
It also doesn't matter if I am plugged in by USB when running executable or not, still just hangs at 2.07.
I really want this to load, and am thinking it must be the card. It used to load everything before I tried to load 2.47.
Hmm I know absolutely nothing about 2.07 or 2.47. I still run 2.40 and am actually now running 3.39.10 radio after seeing this post..... lol... you gonna love this..... I can't dispute his findings. It locks quick for me on VZW. All the other radios I have been running had mixed results and none were great in my eyes until I loaded this. I was actually able to get great results without GC's fix. I hate to see how fast it was if I was to apply his fix.
It is my post and I cant get the stupid nbh to load without using the sprint RUU (still debating) and I hope it is just a card issue. Will have to go buy another microsd by Kingston or someone (this is a PNY) to check. Depressing cause this card ran everything at one point. Now I cant load 2.47 or any nbh files, go figure.
Glad to see that worked for you, I wonder if it is an isolated case, sheer coincidence, or if there are some locational benefits to the different radio versions. Some swear by the newest radio, but I have had mixed results compared to older radios (longer lock times for me for sure). I wish I could get this loaded so I could judge for myself. I feel like a noob, but I know some cards don't work.
With 3.42.30, I can lock from cold start within 15 seconds on VZW....I'm talking 10-15 hours go by without using GPS cold start.
Related
Ok, I am going to get flamed I am sure... but I was trying to update to the 3.39 radio on my Tytan earlier today. I previously had the 3.35 radio and DCD's 3.12 ROM on there (using olipro2.40). I followed the directions on the forums best I could, and reflashed from 2.40 to 1.20 in the olipro. Now it is just stuck there. I cant reflash it to 2.4 or anything? Also everyone keeps talking about the RUU for the radio to flash it, but I have searched for two hours and cannot find a simple post about where I am supposed to find this program. Just a billion mentions of the RUU folder... which doesnt help me at all.
I just went ahead and reloaded the dcd 3.12 rom using olipro 1.20 and it looks to be booting, but this still doesnt help me with the radio issue... ( the SD card option will not work for me either.) Thanks for any help
Gaigebacca said:
Ok, I am going to get flamed I am sure... but I was trying to update to the 3.39 radio on my Tytan earlier today. I previously had the 3.35 radio and DCD's 3.12 ROM on there (using olipro2.40). I followed the directions on the forums best I could, and reflashed from 2.40 to 1.20 in the olipro. Now it is just stuck there. I cant reflash it to 2.4 or anything? Also everyone keeps talking about the RUU for the radio to flash it, but I have searched for two hours and cannot find a simple post about where I am supposed to find this program. Just a billion mentions of the RUU folder... which doesnt help me at all.
I just went ahead and reloaded the dcd 3.12 rom using olipro 1.20 and it looks to be booting, but this still doesnt help me with the radio issue... ( the SD card option will not work for me either.) Thanks for any help
Click to expand...
Click to collapse
RUU stands for Rom Update Utility. I have heard that flashing a radio ROM using a RUU with Olipro 2.4 is problematic. The SD card method is much better and easier. Can you get into bootloader? (power/camera/reset)
...
I have been able to get back to everything the way I had it before (as far as ROM and olipro version) and I can get into bootloader, but I dont have a compatible sd card.
Gaigebacca said:
I have been able to get back to everything the way I had it before (as far as ROM and olipro version) and I can get into bootloader, but I dont have a compatible sd card.
Click to expand...
Click to collapse
If its up and running as before I would buy/borrow a SD card and update your radio that way. Why can't you use the SD card method?
Ooops...just saw that you don't have a compatible card. The microSD card in your phone will work fine if its not SDHC.
I dont have a card reader or access to one in order to format the card and put the file in the root.
Gaigebacca said:
I dont have a card reader or access to one in order to format the card and put the file in the root.
Click to expand...
Click to collapse
Sorry I don't have another idea...I wouldn't attempt any further radio mods until you can get a SD card with the radio ROM on it. Too risky you might muck up your phone and at least now its working. If I remember correctly its the newest 3.x radios that were causing problems when being flashed with a RUU on Olipro 2.4. Perhaps one of the senior members has an idea.
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
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
paulash said:
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
Click to expand...
Click to collapse
I have not seen this... but my suggestion would be to do the Power + Camera + reset... and let it go into bootloader... then just reflash the rom.
paulash said:
It reaches windows mobile, and the "tap screen to begin". It then restarts moments later. Why is it doing this????
Click to expand...
Click to collapse
Like the other guy said, force bootloader but take note of the version. Make sure you are running version 2.40 or greater. If you are running stock bootloader 1.06 or anything else it will have the reboot loop. Read the wiki in my signature fully before doing anything else. Did you read this before flashing?
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5?????
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
Click to expand...
Click to collapse
You need to be upgrading to 2.40 before you do ANYTHING, not just the radio. That was probably your problem before. From stock, bootloader, radio, rom in that order.
paulash said:
QUICK question
I've put everything back to stock now.
can I install the radio AFTER I install DCD 3.2.5????? Because the radio 3.42.30 wouldnt boot on the stock rom, and I'd have to upgrade to 2.40 to reinstall wouldnt I?
Click to expand...
Click to collapse
This wiki tells you the steps.... I did it as follows... but... after doing the radio... you have to force it into the bootloader. It will not load into the phone rom.
xv6800 Rom Upgrade Instructions Wiki
gc14 said:
You need to be upgrading to 2.40 before you do ANYTHING, not just the radio. That was probably your problem before. From stock, bootloader, radio, rom in that order.
Click to expand...
Click to collapse
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
paulash said:
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
Click to expand...
Click to collapse
I put radio 3.42.30 on there but had to get HardSPL-2.40 on it first. The wiki explains it very well.
But doesn't 3.42.30 need SPL 1.20 to install correctly??? I don't think it'll let me install it on olipro 2.40.
Click to expand...
Click to collapse
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
gc14 said:
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
Click to expand...
Click to collapse
I didn't go through those steps GC. I did the olipro 2.40... then the 3.42.30... then had to force it into bootloader.... then did the DCD 3.2.3 update. That's it... and all done via USB cable.
nitro66215 said:
I didn't go through those steps GC. I did the olipro 2.40... then the 3.42.30... then had to force it into bootloader.... then did the DCD 3.2.3 update. That's it... and all done via USB cable.
Click to expand...
Click to collapse
Damn GC, that's a lot of extra work compared to what I have people doing in my tutorial...
gc14 said:
With the ridiculously cheap prices of 1gb microsd cards these days, you'd think you all would be flashing from the card and not the crappy usb.
Anyway, if you must flash everything with usb, this is what you need to do.
From stock:
- Olipro 2.40
- Official Sprint 3.56 Rom Update for Radio 3.42.02 (DON'T LET CUSTOMIZATIONS RUN!!!)
- 3.2.5
- Olipro 1.20
- Radio 3.42.30
- Olipro 2.40
See the hassle it is when you don't flash from the card?
Click to expand...
Click to collapse
There's a REALLY annoying problem going on. I had to reflash to stock twice again. 2.40 installs successfully, and im in the boot loader. I open up the sprint 3.56 (and 3.42.02 radio) with the RUU, and it just reverts to SPL 1.20!!!! Why does this keep happening?
scrawnyb said:
Damn GC, that's a lot of extra work compared to what I have people doing in my tutorial...
Click to expand...
Click to collapse
Why does everybody say you must have an SD card to do the upgrades? I never did anything with an SD card and was able to flash all the way to 3.2.5 without it.
paulash said:
There's a REALLY annoying problem going on. I had to reflash to stock twice again. 2.40 installs successfully, and im in the boot loader. I open up the sprint 3.56 (and 3.42.02 radio) with the RUU, and it just reverts to SPL 1.20!!!! Why does this keep happening?
Click to expand...
Click to collapse
It's because you aren't into the true HARD spl. You have the soft 2.40 spl. You have to verify that the bootloader is 2.40 by doing the power + camera + reset.
nitro66215 said:
It's because you aren't into the true HARD spl. You have the soft 2.40 spl. You have to verify that the bootloader is 2.40 by doing the power + camera + reset.
Click to expand...
Click to collapse
I have the hard SPL. I'll verify it again once stock rom reinstalls (I have to keep reinstalling to stock everytime it switches back to SPL 1.20... really frustrating).
paulash said:
I have the hard SPL. I'll verify it again once stock rom reinstalls (I have to keep reinstalling to stock everytime it switches back to SPL 1.20... really frustrating).
Click to expand...
Click to collapse
It shouldn't be reverting back to 1.2. If you have 2.4 installed correctly... and you check with the "Reset"... then you can do the RUU update right from that bootloader screen. If it is 1.2... then attempt the 2.40 hard spl from that screen instead of redoing the stock rom.
nitro66215 said:
Why does everybody say you must have an SD card to do the upgrades? I never did anything with an SD card and was able to flash all the way to 3.2.5 without it.
Click to expand...
Click to collapse
Who said you HAVE to do this by SD? I think we are saying it is easier.
GC detailed that to flash by USB/Activesync is about six or seven steps and about an hour of work, versus flashing by SD which is less than five minutes and a step or two.
serfboreds said:
Who said you HAVE to do this by SD? I think we are saying it is easier.
GC detailed that to flash by USB/Activesync is about six or seven steps and about an hour of work, versus flashing by SD which is less than five minutes and a step or two.
Click to expand...
Click to collapse
I don't agree that the USB / Activesync is 6 or 7 steps. I did 4 or 5 at the most.. and I'm counting the power+camera+reset as a step.
flash
When the bootloader screen comes up with 1.2, are you just assuming its done...or do you actually then keep clicking through the options until it actually flashes the phone with the ROM?
i was with DCD 3.2.5 and wanted to flash to new telus wm6.1 from telus... now i'm stuck with bl spl-2.07...tried to flash back with stock rom Telus_HTC_P4000_WM6_07252007 but at 1% it says not compatible...tried also uni_exitbootloader but nothing happen...whenever tried to flash with SD card...it's always keep saying "loading...", is anyone have suggestion to bring back my mogul to life?
thanks
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
scrawnyb said:
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
Click to expand...
Click to collapse
I would say the same. I would go ahead and unlock OliPro 2.4 (never tried 2.47) then flash Telus rom. After doing so you should be fine.
scrawnyb said:
uhh 2.07 is a relocker SPL
I think you have to downgrade to a stock firmware/SPL, then do the process properly.
Use SPL 2.40 or 2.47 before trying to flash on a GPS rom.
Click to expand...
Click to collapse
what do you mean by "I think you have to downgrade to a stock firmware/SPL" ? du you have any recommendation ?
belmont said:
what do you mean by "I think you have to downgrade to a stock firmware/SPL" ? du you have any recommendation ?
Click to expand...
Click to collapse
Sorry, I read his post wrong. HEre is what I would do:
1. Download OliPro 2.40 and run it. Ignore the part that asks you to verify the Active Synch connection. Its not needed for anything but a connection confirmation.
2. After running OliPro 2.40 you should be stuck at the three color bootloader screen, Like you are now. If not hold Camera and Power and use stylus to put phone in bootloader. Make Sure it says OLIPRO 2.40 for the version on the bootloader. If not then re-run oliupro and make sure to follow the directions. Especially noting that it asks you to disconnect then reconnect the device.
3. Flash your Stock ROM back.
4. Hard Reset.
In my experience you do not have to go back to a stock ROM to flash a new carrier ROM as long as you have OliPro.
Let me ask you this: What exact steps did you take when you flashed Telus ROM image?
I was on the same setup you were, DCD 3.2.5 with Radio .50 and OliPro 2.40. I simply flashed the Telus image and all was well for me. Hell it was better than all well. This is the best ROM I have ever used. PERIOD. No, its not pretty but damn, its fast as anything I have used and the GPS is insane!
BTW: Im a Verizon user. Anyone know how to make the phone not say "Telus" when I go to the connection manager?
scrosler said:
Sorry, I read his post wrong. HEre is what I would do:
1. Download OliPro 2.40 and run it. Ignore the part that asks you to verify the Active Synch connection. Its not needed for anything but a connection confirmation.
2. After running OliPro 2.40 you should be stuck at the three color bootloader screen, Like you are now. If not hold Camera and Power and use stylus to put phone in bootloader. Make Sure it says OLIPRO 2.40 for the version on the bootloader. If not then re-run oliupro and make sure to follow the directions. Especially noting that it asks you to disconnect then reconnect the device.
3. Flash your Stock ROM back.
4. Hard Reset.
In my experience you do not have to go back to a stock ROM to flash a new carrier ROM as long as you have OliPro.
Let me ask you this: What exact steps did you take when you flashed Telus ROM image?
I was on the same setup you were, DCD 3.2.5 with Radio .50 and OliPro 2.40. I simply flashed the Telus image and all was well for me. Hell it was better than all well. This is the best ROM I have ever used. PERIOD. No, its not pretty but damn, its fast as anything I have used and the GPS is insane!
BTW: Im a Verizon user. Anyone know how to make the phone not say "Telus" when I go to the connection manager?
Click to expand...
Click to collapse
thanks for quick reply. i tried so many times to use olipro 2.40...whenever i ran it...it popup that device is not connected and asked me to try again...tried also with SD but still hung on tri-color bars
belmont said:
thanks for quick reply. i tried so many times to use olipro 2.40...whenever i ran it...it popup that device is not connected and asked me to try again...tried also with SD but still hung on tri-color bars
Click to expand...
Click to collapse
Thats interesting. I have hosed so many XV6800's and used OliPro and a stock GPS sprint ROM to get them back (Thanks alot for nothing Verizon!).
IM assuming you are still on the tricolor screen? Take out battery and place back in. Then try again. Dont wait long. Someonelse has discoverd the phone can only be connected for so long before it "drops" connection with the windows machine. Someone else's therory but I can certainly second it.
What SPL were you using with DCD 3.x before upgrading?
scrosler said:
Thats interesting. I have hosed so many XV6800's and used OliPro and a stock GPS sprint ROM to get them back (Thanks alot for nothing Verizon!).
IM assuming you are still on the tricolor screen? Take out battery and place back in. Then try again. Dont wait long. Someonelse has discoverd the phone can only be connected for so long before it "drops" connection with the windows machine. Someone else's therory but I can certainly second it.
What SPL were you using with DCD 3.x before upgrading?
Click to expand...
Click to collapse
before flashing to new telus wm6.1 rom, i had olipro 2.40 with .30 radio and dcd3.2.5 kitchen...i have tried upgrading to radio .50 with no success. but failing to update radio didn't affect anything to my phone. tried your suggestion by romoving battery and still telling me that device not connected.
belmont said:
before flashing to new telus wm6.1 rom, i had olipro 2.40 with .30 radio and dcd3.2.5 kitchen...i have tried upgrading to radio .50 with no success. but failing to update radio didn't affect anything to my phone. tried your suggestion by romoving battery and still telling me that device not connected.
Click to expand...
Click to collapse
Hmmm, maybe try a different USB port at this time. Also, try this...
Before you connect your device open device manager in Windows. Look for M/S USB sync to appear after you connect. What OS are you using? This is what it will look like in Vista.
In XP I beleive it will show up under USB at the very bottom of Device Manager.
Does the phone show up at all?
Flash a stock pre-gps rom first.....then go ahead and upgrade the hard spl to 2.4 or 2.47.....then flash away with whatever you want....
You cannot flash Hardspl to Hardspl...they have overwrite protection not signed by HTC....
..................................
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.