Related
Got the radio upgrade 3.3x and all works well with 2.x dcd rom, but upgrading to 3.0.1 has problems with phone calls. Both receiving or outgoing, the device resets 10 sec into the call. Also Voice Command 1.6 not working. sucks.
verizon xv6800
I'd be willing to bet millions you didn't follow directions when flashing.
Nope. Cooked a kitchen, tried the Verizon Rom....neither work with 3.0.1. works great with 2.x though.
Voice Command 1.6 now working OK as well under 2.3.2. I is happy. Still looking for good GPS software. I really liked Earthcomber, but doesn't work with this rom.
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
OK so I cry for help. Why the heck would I apply a Sprint update to a Verizon handset, granted both CDMA. I upgraded the radio at the same time as 2.2. The 2.2 DCD rom I'm using that WORKS WELL should be no different than the upgrade to 3.0.1. Unless I'm forgetting to stop customization with a soft reset.
You're not getting the point!!!
The only reason to flash sprint's official rom is so you can update the radio to its latest version. After this is done, it DOESN'T MATTER whatever rom you flash next, such as a Verizon rom. Use DCD's 3.0.1 rom it should be working. You would have known this if you read instructions. If you flashed the radio alone first, then your settings (ESN, MSID, etc) will be wiped. You will have to re-enter these either manually or call up Verizon to do it for you. This is probably why you can't make calls.
Exactly my point. I flashed the radio with the Oli 2.4 and updated the radio from stock verizon. Then flashed 2.3.2 and all is good with the new radio. So why doesn't it work with 3.0.1? I just found my way to the In and Out Burger via Odyssey Mobile locator.
Everyone keeps telling me that i didn't follow the destructions but they don't point to where they are.
Maybe wrong radio ver?
Crap. Mine says 3.24.00. I guess that's my problem. I'm an idiot.
Please point me to the proper radio D/L.
Thanks,
Sorry for asking what is probably a simple question, but I am having the same problems. I have SPL-2.40.Olipro atm, installed the verizon ROM upgrading to 3.0.1 from NexVision's Hybrid rom. My radio is upgraded to 3.25 or whatever it was supposed to do fine. On vibrate mode, when a phone call is incoming, I get stuck in an ever ending vibrating. I can text, and attempt to cal lsomeone but nothing can be heard and no one can hear me. I know i screwed up somehow- but what exact steps do I do to remedy this?
Thank you in advance
We have to do the Sprint radio update to 3.35 first, which is an upgrade from 3.27. Then go to ROM 3.0.1.
It's always interesting to me how people jump up to say "you're doing it wrong" but don't tell you how to do it right.
Here's how to do it right.
http://forum.ppcgeeks.com/showthread.php?t=17667
Gecko122, There is more to the Sprint file than just the radio... It includes the ROM as well.... My understanding is this:
1st - Run Olipro unlocker 2.4
2nd - Run Sprint Official upgrade , NO CUSTOMIZATIONS.
3rd - Load Custom ROM.....
That has worked for me.....
PS - the DCD 2.x.x series do NOT play well with the new radio, hence the 3.0.1 kitchen.... Driver differences....
do i have to flash back to a former version of dcd or anything? or can i start from a messed up 3.0.1?
hi Penn,
Well, exactly what have you done to your phone?
Bootloader version?
ROM version?
Radio Ver?
Then we can start from there and develope a plan to help ya.
Ignore that above - I re-read you original post....
Here's what you can do and correct me if I'm wrong Penn...
You have Oli-pro 2.4 bootloader loaded
You have DCD 3.0.1 ROM loaded
You have the 3.27 Radio loaded?
If the above is true, then we have options..... Let me know
gcincotta said:
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
Click to expand...
Click to collapse
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
Click to expand...
Click to collapse
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Gecko, the reason why I did not "tell" you how to do it the right way is because dcd's thread has 94 pages of information on how to do it the right way. I've even posted several times on different pages in that thread with explicit instructions on how to. While I am always very eager to welcome newcomers to this community, I also strongly encourage them to read, research and educate themselves before touching their device. It doesn't mean I'm not a nice guy and don't like to help, because if you search my posts you will see that I help a lot around here. If you had simply taken 20 minutes and even skimmed dcd's thread, you would have found the answer yourself in no time.
gcincotta said:
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Click to expand...
Click to collapse
Wow... I'm sorry, I had not been keeping up with the issues of others, so until you said that just now, I had no idea. You are right, I am really lucky, so thanks for bringing it to my attention.
No problem
Hey guys,
I've been doing a lot of reading on the forums here, and finally decided to go with the DCD 3.0.4 from here http://forum.xda-developers.com/showthread.php?t=385336
I installed the SPL-2.40.Olipro, did the Sprint ROM for the Radio, then did the DCD 3.0.4
The issue I have now is that it's connected as an international roaming connection, with the triangle at the top. I couldn't find anything about this, so I decided to post. I did ##778 and set the NAM Name and verified that the MSID and the ESNs were correct, and they were, and I did *22803
Am I missing something?
Thanks in advance,
Okay, so I think I found out what I did... I let the Sprint ROM load the files after installing it... Which changed the EPST(?) What I don't know, is how to fix this..
You should be able to just reflash your stock rom. You may have to relock your phone. Activate it again. Run olipro again, and reflash the sprint rom. Once it starts to boot put it back into the boot mode. Reflash DCD's rom - reactivate. You should be good to go.
EDIT: So the ROM did have the Radio built in... contrary to what I read in another thread. Working on starting over. Thanks for the help.
Even on the stock ROM after a hard reset I'll often get the roaming triangle. I set it to Sprint Only in the roaming menu and after a few minutes it's OK .
Well I just attempted to upgrade my Rom.. First I loaded titan_SPL_2.40-olipro on.. It seemed to all go fine.. I can boot into the Bootloader on the phone fine and it shows that version. Then I loaded dcd 3.1.2 (Official GPS/RevA) - Windows Mobile 6.1 OS 5.2.19213. It seemed to load fine to.. went to 100% and finished phone restarted and is now stuck on the Telus screen.. Tried reloading the ROM again same thing.. Tried a different rom same thing.. I also cant establish a active sinc to my PC anymore.. Any ideas? Thanks..
I was going to try loading a factory ROM again.. I just read that people advice not to load a factory RON on this verion of SPL, correct?
Well I decided to give it a shot and load a factory ROM on again and it worked its back to life.. So my question is what should I do now, I would still like to upgrade the ROM but don't wont this to happen again.. Do I try reloading the SPL?
You are missing a step.
steps are
1. Load bootloader
2. Load Sprint or alltel OEM rom with 3.xx radio.
3. Load custom rom. If possible one with extended rom, that will erase customizations from ext rom.
here are detailed instructions for telus
http://howardforums.com/showthread.php?t=1369027
here is another 6.1 cutom rom
http://www.howardforums.com/showthread.php?t=1372511
jim_l, as mentioned you are not using the appropriate radio for your chosen ROM.
The previous post is in error because you may not mix any 3.xx radio with the latest ROMs. Avoid using radio 3.27 as that was only paired with a briefly used leaked ROMs. The compatible radios are 3.35.10, 3.37.20, and what most now seem to recommend, 3.39.10.
There are no special instructions for Telus when flashing. The highlighted Wiki and radio stickied threads at the top of this forum have all of the troubleshooting and instructional information that you required.
A hint to others, rather than first posing questions and waiting for help, it's often quickest for you to first see what existing threads and solutions are present in a forum. There's a search function and some very self explanatory labelled threads stickied to the top that occasionally get overlooked.
Thanks, I will do some more reading.. I read until my eyes bleed and thought I had it figured out. Guess not... I have been browsing forums since forums existed and know my way around... dohhhh
Thanks again..
Well I did more reading and I got it going with dcds ROM thanks all...
Only question I have now, is it seems my phone cant geta data connection.. It just doesnt dial out for it..
jim_l said:
Only question I have now, is it seems my phone cant geta data connection.. It just doesnt dial out for it..
Click to expand...
Click to collapse
Did you install one of DCD's appropriate carrier CAB?
Ya I did install it.. I just reinstalled it and all is well.. Thanks a million..
Did you also record and now check your EPST data? Is it all as it should be?
I did record all the EPST data, I couldnt get into EPST for a while.. I rebooted a couple times and now it lets me in.. seems to be all the same.. THanks..
So I bought a phone that was branded qwest. It is the Mogul Titan 6800 I'm not sure of the point for all the different names but it looks like the Sprint or Telus Phone (circle instead of square navigation button) Anyways I paid someone to flash it to cricket. It ended up having a Verizon splash screen and a radio version of 3.37. The person who flashed it said GPS would not work with this particular flash, and if I wanted it to work he would have to do it on his own time because the guy he worked for had a certain ROM they liked and he could not flash a GPS ROM on his boss's time.
So I flashed to Gamedics ROM and then flashed To) V3 ROM. CI could not get GPS to work with either. I then upgraded the radio to 3.42.50. Still GPS does not work. I added GPS toggle and quick GPS but they did not help either.
I read somewhere about the Verizon MR1 update and how GPS would not work with it. Is there anyway that the original flash that I got was this MR1 and for some reason it has stuch through my other flashes preventing GPS from working? Is there anything I can do to make GPS work on this phone? I also have something QPST if that helps.
Thanks in advance.
My thoughts, and it's only my thoughts, this was probably flashed to MR1, which disables GPS, when your cricket dealer flashed it, he didn't flash it back to an older Verizon stock rom first to undo the GPS lock, you might try flashing an older Verizon stock rom, let it run customizations, then take it back to the dealer and ask him to flash it again, let them do whatever rom they want, but when you get it back home and go back to GAMedics, or whoevers rom, GPS should work.
You might call the cricket guy first, make sure they won't charge you to flash it again, and if not, then do what I suggested.
Or at least ask the tech guy who did the flash for you and see if maybe their rom uses the same verizon locks.
BTC
BillThyCat said:
My thoughts, and it's only my thoughts, this was probably flashed to MR1, which disables GPS, when your cricket dealer flashed it, he didn't flash it back to an older Verizon stock rom first to undo the GPS lock, you might try flashing an older Verizon stock rom, let it run customizations, then take it back to the dealer and ask him to flash it again, let them do whatever rom they want, but when you get it back home and go back to GAMedics, or whoevers rom, GPS should work.
You might call the cricket guy first, make sure they won't charge you to flash it again, and if not, then do what I suggested.
Or at least ask the tech guy who did the flash for you and see if maybe their rom uses the same verizon locks.
BTC
Click to expand...
Click to collapse
I now have the capability to flash it myself. Could you direct me to an approbriate ROM to undo the lock?Then I can flash it back to my current ROM.
Thanks for the reply.
The only rom that I know of is the original stock Verizon rom, it's windows mobile 6.0, it will do carrier customization, which I believe it has to do in order to unlock the GPS.
Hopefully your Cricket rom restores the Cricket customizations.
BTC
Same problem here
Almost the exact same problem, but I have a Verizon branded refurbished (insurance) phone.
It had the latest Verizon ROM (6.1 - 3.37 radio) on it when I got it.
Am I able to put the Verizon 6.0 ROM on it?
I thought that would downgrade to a non-GPS radio , and that could brick the phone?
Here is my two cents... I Have xv6800 on VZW and Verizon users always had a hard time with GPS until GC figured out a GPS setting you had to apply with QPST. Its in the "HTC Titan Links/Information - PLEASE READ BEFORE POSTING ANYTHING" section sticky in this forum. Since then I use Baf GPS toggle today screen plugin to toggle GPS on or off. It always locks in 2 or 3 seconds. It looks like you said you are on cricket and I don't know if there are similar settings to apply with QPST. This all assumes you haven't flashed the MR1 Verizon upgrade, you are on a 3.something radio and are using a GPS enabled ROM (most if not all in this forum are). I never messed around with the MR1 upgrade so i don't know about it. Flashing back to the original verizon wm6.0 ROM in my case has involved re-locking the phone, and flashing the original ROM (which includes the original Verizon radio), then un-locking again, flashing the latest radio, then a wm6.1 ROM.
If you do some searching on this forum you can find answers to most of your questions.
Thanks. I have searched, but it was unclear whether I should downgrade to a non-GPS rom/radio (I've read that it's dangerous).
The guide I read here was actually pre-GPS rom release.
I went ahead and did downgrade, and then upgraded radio and installed a custom rom.
Now I get super fast locks.
Thanks again.
For those who know me, I have flashed a zillion times and am no rookie. I want to verify that this GPS chip is toast before sending in the replacement phone to get another and want to make sure I am not missing something simple.
FYI here are the steps I did:
updated BL to 2.40, updated radio to 3.42.50, updated ROM to 3.2.6, did GC aGPS tutorial (QPST, location/GPS settings, cab), ephemeris data streams but no lock (using HTC GPS tool).
Rolled back to stock, started from scratch above and verified QPST persisted, still no lock but I am getting ephemeris data to start but it never has anything exciting showing, just empty lines after hours of running (see screenshot).
Any thoughts or do I send it back? This is the first time this has happened after receiving several xv6800s where it never locks. There is a white dot so I can use that as an excuse to get a new one sent.
Did the phone come with MR1 or MR2 on it? I've read you need to flash an older stock ROM before upgrading to have working GPS if it came with that.
unL33T said:
Did the phone come with MR1 or MR2 on it? I've read you need to flash an older stock ROM before upgrading to have working GPS if it came with that.
Click to expand...
Click to collapse
That's new to me. Most of my previous replacements were pre MR1 and MR2. I will work on it and repost.
If anyone else has any thoughts let me know.
He's right. If you flashed to a ROM from MR1 or MR2, the aGPS fix doesn't work.
You have to flash back to a stock ROM, then flash to the custom ROM again. Once that's done, it'll work.
I made this mistake the first time I flashed a phone.
after you go back to a stock 6.0 rom make sure you go back and do the GC gps fix again
steps
roll back to 6.0 stock
install Custom ROM (dcd,Reloded)
GC fix again
GeLopez said:
after you go back to a stock 6.0 rom make sure you go back and do the GC gps fix again
steps
roll back to 6.0 stock
install Custom ROM (dcd,Reloded)
GC fix again
Click to expand...
Click to collapse
Does this mean BL relocker 1.04 (see here) then 2.09.605.8 (Radio 1.30.00) for me on Verizon?
Why are there no tutorials or notes for GC? He is usually pretty good at that kind of thing.
I just received a refurb which has MR2 as well, so I'm going to have to do the same thing.
I'm going to use the Re-locker
Flash back to stock
Use NueSPL 2.47
Flash a Rom
Do DCD aGPS fix
See if it works
Now to go and find Stock Verizon Rom...
Ok, so the stock rom is in the Wiki. I really don't want to call Vzw for a new a-Key though....
hmm...does the gpsserver.cab work without doing the aGPS fix?
ok, the gpsserver.cab does no good, so I was forced to downgrade.
The good news is I now have aGPS back on the phone! The bad news is my aKey is wrong, and I need it reset by Verizon. So after calling customer support apparently they only offer in person customer support until 11pm
So I will have to call in tomo and get it reset. The good thing is, data works fine....
I tried to use the new *228 and option 3, but since I didn't switch phones a new aKey was not set. Oh well, no worries....
MrTek said:
ok, the gpsserver.cab does no good, so I was forced to downgrade.
The good news is I now have aGPS back on the phone! The bad news is my aKey is wrong, and I need it reset by Verizon. So after calling customer support apparently they only offer in person customer support until 11pm
So I will have to call in tomo and get it reset. The good thing is, data works fine....
I tried to use the new *228 and option 3, but since I didn't switch phones a new aKey was not set. Oh well, no worries....
Click to expand...
Click to collapse
MrTek, please post your exact steps (if they are different from your prior post) and maybe we can update the wiki with the new instructions.
Do you mean that you needed to downgrade to stock vzw 6.0 because gpsserver.cab didn't work?
If anyone else wants to pitch in and help write the instrux, feel free.
If you start with MR1 and go custom the gps is locked by Verizon. You first must relock the phone and downgrade to a pregps Verizon rom. Then unlock phone and flash gps radio and custom rom. Then apply agps fix.
I did the steps in the Wiki as they are, so I don't think they need to change.
When I said the gpsserver.cab didn't work, I meant that it didn't work on a custom rom after I applied the QPST info. I didn't expect it to work, but it was just an idea to keep me from having to truely downgrade the radio.
The exact steps were:
1 - Use Nue's Re-locker to get back to SPL 2.07
2 - Use a SDcard to flash back to Stock VZW rom,reboot
3 - Use SDcard to flash latest Titan Radio
4 - Use RUUupdate to load your choice of custom ROM,reboot
5 - Use QPST to set aGPS ip settings in config
6 - install the aGPS.cab settings
7 - GPS works as expected now
8 - Call VZW to reset my Akey
9 - Phone is fully functional, with aGPS working correctly
I believe there should be a step between 2 and 3 to change bootloader to nue 2.47, right?
Otherwise this is great.
MrTek said:
I did the steps in the Wiki as they are, so I don't think they need to change.
When I said the gpsserver.cab didn't work, I meant that it didn't work on a custom rom after I applied the QPST info. I didn't expect it to work, but it was just an idea to keep me from having to truely downgrade the radio.
The exact steps were:
1 - Use Nue's Re-locker to get back to SPL 2.07
2 - Use a SDcard to flash back to Stock VZW rom,reboot
3 - Use SDcard to flash latest Titan Radio
4 - Use RUUupdate to load your choice of custom ROM,reboot
5 - Use QPST to set aGPS ip settings in config
6 - install the aGPS.cab settings
7 - GPS works as expected now
8 - Call VZW to reset my Akey
9 - Phone is fully functional, with aGPS working correctly
Click to expand...
Click to collapse
That is correct after the stock rom install you need to unlock the phone with 2.47
So here is updated with links, I will put in main forum to make it easier for people who are searching with a better thread title.
1 - Use Nue's Re-locker to get back to SPL 2.07
2 - Use a SDcard to flash back to Stock VZW 6.0 rom,reboot
3 - Use nueSPL-2.47 to update bootloader
4 - Use SDcard to flash latest Titan Radio
5 - Use RUUupdate to load your choice of custom ROM,reboot
6 - Use QPST to set aGPS ip settings in config (use GC tutorial)
7 - install the aGPS.cab
8 - GPS works as expected now
9 - Call VZW to reset my Akey
10 - Phone is fully functional, with aGPS working correctly
Oops, I missed that in the list, sorry. yes, I had used nueSPL 2.47
I just flashed the the 6.5 B2, and everything works great so far...
Just got my refurb (2nd one cause first replacement had a white dot out of the box) and followed the steps and my phone is better than ever. Thanks again for your help guys.
Actually, what might be a good recommendation is to Do the unlock, and Flash BEFORE you switch to the refurb phone.
When you receive your refurb, you dial #228 on the refurb phone, and choose option #3. This walks you through moving your service to this new phone.
During the process, a new A key is also set I believe, so if you unlock and flash before you do the process you won't need to call VZW for the aKey.
MrTek said:
Actually, what might be a good recommendation is to Do the unlock, and Flash BEFORE you switch to the refurb phone.
When you receive your refurb, you dial #228 on the refurb phone, and choose option #3. This walks you through moving your service to this new phone.
During the process, a new A key is also set I believe, so if you unlock and flash before you do the process you won't need to call VZW for the aKey.
Click to expand...
Click to collapse
Or if you have not yet sent back the other device , login to the website at verizonwireless.com and activate your old phone again. Wait 10 minutes, activate the new phone.. and the Akey should be fine.
Verizon will update your phone 24 hours a day. If you listen to the message on their 800 number "If you cannot make phone calls from your phone, please press" and you can get customer service after hours.
I've done it two times by screwing with my phone late at night.