I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Chemdawg said:
I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Click to expand...
Click to collapse
Do you know what version of the PRL you're using? It shows up as "PRL version" under Start->Settings->System->Device Information. Someone along the line you might have ended up with an outdated one. 60613 is the latest for Sprint EVDO-capable phones.
Chemdawg said:
Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Click to expand...
Click to collapse
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Keystone said:
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Click to expand...
Click to collapse
we probably need the previous version initprov.dll. i will look tonight. thanks for finding this
You're welcome, DCD.. Thank you!
This afternoon I may also have a chance to build a new ROM with a familiar initprov.dll and see if that resolves it.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release and what I was first using in my kitchen), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
That was without rebuilding a ROM with the older initprov version in.
...to note, the April Alltel ROM was also using this latest v1.25.0.0.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
Click to expand...
Click to collapse
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
gc14 said:
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
Click to expand...
Click to collapse
Worth a shot.. Can't rebuild until I get home......
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
Click to expand...
Click to collapse
That's not necessarily true. It could have been something that was installed during the 3.56 factory customizations. Try flashing Sprint 3.35 stock rom/radio, let the customizations run. Then flash 3.2.0 and 3.42.02 or 3.42.30. If you're going to use the 3.56 stock rom/radio to flash 3.42.02, that's ok, just DON'T let the customizations run this time.
that was the issue with mine I ran the sighned sprint cab from the extended rom from the 3.56 "official" rom that was part of no2chems pre 2.2 after i did that my phone was stuck in roaming... Thinking it was the radio i downgraded 1 step @ a time from the 3.42.03 back to 3.39 still roaming went back to the stock radio that came with the 3.35 release still roaming when phone was booted. Figured it might be rom related @ that point so i reflashed to good ole 5069k left battery out after flash for 2 min... first boot it was roaming and would not lock onto a tower in sprint only mode... my muerom boot agent always runs the sprint carrier settings 4 me and on my second boot still no sprint signal only digital roam.. In a last ditch effort I reflashed via activesync the whole 3.35 stock rom/radio ... and wala all was fixed booted right up and even b4 the sprint custimization was started i had the evdo icon and no roaming triangle. Leaving the 3.35 stock rom on there i went forward 1 step @ a time radio wise and even with 3.39 and 3.42.02 i still got sprint coverage and evdo icon and connection. so i re-flashed to the nue 2.2 preview let it do tis sprint thing on first boot. then i did not go in and eun anything from the extended rom. No more roaming triangle. Something in the 3.56 exended rom i ran (sprint sighned whatever) Changed something in epst that dod not get reset even with flashes and hard resets till i relfashed back to stock 3.35 relaease full with radio from activesync.
So my suggestion would be that u can run the newer radio and roms just be sure to let your carrier settings run but don't touch files in the extended rom esp the file mentioned bc it stuck me in roaming and it would not get a sprint signal (home) for anything even after just letting it sit. and when setting roaming option to sprint only I would not get any bars @ all just the animated dots nest to the signal icon.
So it can't be anything in the new rom or settings in the new rom that is doing it nor the radio bc when downgrading back to stock radio from march update it did the same thing.
To fix your going to need to do a fill rom/radio flash then just pick your fav flavors after its flashed and has booted up the second time.
Boy, am I glad y'all started a thread on this. I've been trying to figure out what was wrong since this came out. My first flash of the new rom caused mine to be stuck in roaming, and sometimes it won't even come out.
I'll try what you guys suggested.
Customizations = Extended Rom
That's exactly what I said.
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Click to expand...
Click to collapse
Again, it's not the radio. It's in the customizations from 3.56.
gc14 said:
Again, it's not the radio. It's in the customizations from 3.56.
Click to expand...
Click to collapse
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
Click to expand...
Click to collapse
That's because you've already let them run. They don't go away after a reflash, the same way Verizon users who let them run can't just reflash their rom to make it go away. You need to flash sprint 3.35, let THOSE customizations run. Then reflash 3.2.0.
Before you do anything though, you DO have Sprint right?
Related
Anyone having issues with the GPS working? I'm unable to get any GPS Sats locked at all. I can do everything else just fine.
Just verifying, did you check the steps in the GPS thread?
I'm installing 3.0 for the first time right now. Will test GPS soon.
Yeah
I've been using GPS for a bit now with the older ROMs. I just want to confirm other VZW have it working.
Works great here. Be sure you have Be sure your Location Setting is set to Location On.
If you are using Google Maps, be sure to turn on the GPS in the GMM menu.
Also, be sure you are outside, not in a building.
etexter said:
Anyone having issues with the GPS working? I'm unable to get any GPS Sats locked at all. I can do everything else just fine.
Click to expand...
Click to collapse
DCD 3.0.0 works Excellent on my XV6800
GPS improved. I get way more satellites.
I modified the ROM a little bit and on a Bare ROM flash I get 28MB and with some major apps i get down to 25MB to 26MB
etexter said:
I've been using GPS for a bit now with the older ROMs. I just want to confirm other VZW have it working.
Click to expand...
Click to collapse
Yes, it works. I have been using Google maps. One thing, I noticed this morning is starting it up after an hour being off and in a building is "Google Maps" would get hung at "Initializing GPS" when I selected "Use GPS". The only why I have gotting it to work again was a soft reset. Not sure what is going on, yet.
Everything works fine on my xv6800 with dcd 3.0.0 including GPS.
No more issue where it takes 5 seconds to connect to a call when answering...among many other fixes from the leaked rom.
Interesting
Seems to be related to building the Kitchen on Vista for me. I can reproduce the problem if I build the kitchen on Vista. If I use all the same options on XP, it works fine. Strange. I guess something it messing with the build process on Vista. Solved for me at least.
Stupid question... assume you need the latest radio for this (3.35 or whatever, I have 3.27)? I'm a little leery on upgrading again considering I had to call VZW and apparently they're hip to people flashing these roms.
J Shed said:
Stupid question... assume you need the latest radio for this (3.35 or whatever, I have 3.27)? I'm a little leery on upgrading again considering I had to call VZW and apparently they're hip to people flashing these roms.
Click to expand...
Click to collapse
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
rschell said:
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
Click to expand...
Click to collapse
hmm... I don't have an A key on mine, but when I re-entered all the info it wouldn't let me place a call.
I'll give this a wack maybe tonight or tomorrow. I JUST upgraded to 2.3.2 and this comes out... figures.
I have only ever had to enter the A-key once, the very first time I flashed a ROM to the phone. Every upgrade since has just worked.
The latest is working great for me under VZW today. I was running 2.3.2 before that. I flashed the sprint ROM to get the new radio, then immediately flashed the ROM I built for verizon from the 3.0.0 kitchen. Did a *228 1 just in case, and verified that the PRL after that was identical to the one it had before I did the upgrade (##775 SEND, 000000).
EVDO, wifi, GPS all working. I like the new wireless today plugin.
I'd still love to see an up to date step by step on how to get VOIP working, I've never managed to get anything VOIP related on this phone.
GREAT WORK AS ALWAYS DCD! Thank you! Remember to show dcd the monetary appreciation guys.
rschell said:
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
Click to expand...
Click to collapse
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
a_lazy_dude said:
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
Click to expand...
Click to collapse
Do not let the customizations run, just soft reset before they do. Now run the new kitchen creating your ROM. Should be nothing else to do.
I've never had to call Verizon through any flashes including when 3.16 first came out.
J Shed said:
hmm... I don't have an A key on mine, but when I re-entered all the info it wouldn't let me place a call.
Click to expand...
Click to collapse
At least to Verizon customers, the EPST A-key will always be blank. It is a 26 digit number generated by Verizon that is different each time you authenticate. Once you enter it, and the device reboots the A-key disappears. I have had to call and get a new A-key every time I have made the switch from non-Rev A to Rev-A. Not sure this new radio is any different. I have had excellent support from Verizon, every time I have called, you just have to let them walk through their diagnostic tests.
The authentication issues appear to be Network Switch dependent. I just happen to be in one of those areas.
blazingwolf said:
Do not let the customizations run, just soft reset before they do.
Click to expand...
Click to collapse
So if I just go ahead and reboot while, say, I'm in the screen calibration after my initial boot, I should be in the clear?
I was thinking of yanking the battery at this point, putting it back in, rebooting into bootloader, then flashing either by the RUU or SD (can't recall if the RUU works while in bootloader mode or not, so i've got the SD option to fall back on). Or should i just do as you say: soft reset, let the device come all the way back up, let activesync connect the phone as a guest, then run the RUU w/ DCD 3.0.0?
you don't even have to soft reset, or manually enter the bootloader. once you finish flashing the sprint update the phone will boot and will stop at the tap screen to set up device screen...at this screen activesync WILL connect. just run the kitchen and the phone will AUTOMATICALLY put itself into the bootloader and flash the new rom without running sprint customizations. the sprint customizations only run after you set the device up, not before.
gcincotta said:
at this screen activesync WILL connect.
Click to expand...
Click to collapse
bam! thanks man, it's details like these that always get glazed over in the flurry of "i installed the new rom no problem!!!!111one" posts that i'm seeing all over the place around here.
a_lazy_dude said:
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
Click to expand...
Click to collapse
Starting from 2.3.2 (if you start from the pre-GPS ROM, you may need a different SPL).
I did both the radio and ROM in one upgrade, I just did not let the customizations run, actually I forced it to the boot loader just after the HTC Mobile splash screen came up. Then I installed DCD's 3.0.0 ROM from the boot loader (2.40!). See http://forum.xda-developers.com/showpost.php?p=2011926&postcount=3
Success!
Data connection confirmed working
Incoming/Outgoing calls confirmed working
Incoming/Outgoing texts confirmed working.
GPS confirmed working.
no calls to VZW customer support whatsoever.
so far, no *228 updates at all (prl seems to be current, 50989; confirmed within ##778)
Here's a quick rundown of my starting conditions, and what I did (basically, just followed gcincotta's instructions exactly)
Starting conditions:
-NexVision's no2chem 5051 - based ROM w/ 3.27 radio
-2.40 SPL
Upgrade procedure:
1) Connected phone via activesync
2) ran the official Sprint/HTC 3.35 upgrade utility, which ran successfully.
3) On the initial boot, I let activesync connect while the phone was still holding on the "tap screen here to begin" screen
4) I then ran the RUU using a DCD 3.0.0-based rom (NexVision's VZW 3.0.0), which was successful.
5) After initial boot on NexVision's rom, I let the customizer run (i think it's just an SD power management program). It soft reset, and I was good to go.
That's it! Once it booted up after the second install, everything that I confirmed above was working perfectly.
Thanks again guys!
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 .
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had them do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work correctly. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
playoff beard said:
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work fine. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
Click to expand...
Click to collapse
When you update the PRI, it does not install into your ROM, it actually updates something inside the phone (similar to flashing your radio/etc). You need to find a verizon PRI ripped from the verizon stock rom (if it is even there) and install and run PPST.exe again. My original post he reposted had said not to install on another carrier in big red letters
Read this here, should do the trick.
After doing yet another relock, stock rom, and *228, I installed the latest PPC Kitchen 5060 rom (set to Verizon) and new radio (3.42.30). As soon as the phone boots, it thinks it is roaming and *228,1,2 does not help at all. I've done all the steps on the thread that serfboreds recommended. It still thinks it is roaming. Any advice?
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
serfboreds said:
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
Click to expand...
Click to collapse
The only problem is that the phone seems to look and work fine when the stock rom is loaded, as long as the DMU reset is done for data. Problems don't appear until I load a custom rom. I can't figure out why the phone shows verizon network (1.35_002 PRI) when the stock rom is installed, but then shows sprint (2.03_003) when I load a non-carrier specific DCD roms and even carrier specific roms (i.e. ppckitchen 5060 for vzw).
I don't know how I can convince a verizon tech to swap when the phone appears normal with the stock rom.
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
When you do update to DCD 3.2.0, Are you installing the Verizon Carrier Cab?? Also, How are you getting the radio onto the device??
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
serfboreds said:
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
Click to expand...
Click to collapse
I've been unlocking with olipro 2.40, flashing the new 3.42.30 radio from a microSD card, and then installing the custom rom while still in the bootloader. After installing DCD 3.2.0, I ran the carrier cab and then used *228. Plus, I wouldn't think the carrier cab would be the issue, because I had the same problem when installing PPCkitchens 5060 verizon rom.
-Update: I've tried using radiorefurbish.exe /refurbish to reset my phone to Verizon, but when I run the radiorefurbish.exe using resco explorer, nothing seems to happen. Any more suggestions?
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Thanks to you guys and drellisdee at PPCGeeks. You guys rock. I was horrified that I was going to be stuck with the tock VZW rom.
Take the following screenshots (making sure to block out any personal information) and post them:
Device Information
EPST->Security
EPST->M.IP Default Profile
Then, flash back to stock, re-take the screenshots, and post them.
Finally, flash back to 3.42.30 and 3.2.0, install nothing except the carrier cab, re-take the screenshots one last time, and post them.
playoff beard said:
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Click to expand...
Click to collapse
I've got the same problem and I reflashed to stock Rom and reflashed to custom. Still stuck in roaming. Could you give details on exactly how you ran resco with an argument?
Thanks
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
nitro66215 said:
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
Click to expand...
Click to collapse
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
aguas said:
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
Click to expand...
Click to collapse
Yup. and yes... it did run when the Verizon stock ran it's customizations. The PRI stays as sprints PRI 2.00_003. This is the main issue. Also, the ERI is 0. I've tried updating the ERI via ##eri... to the correct 4.eri... but it just gives me a write error. Under ##PROGRAM... the ERI fails to read. Hence my dilemna with the stupid Roaming indicator. I've been back and forth flashing different roms, and am pretty fed up with it actually. This is a Sprint Mogal "Cloaned" as my original VZW XV6800. I left the 6800 in the box.
check this
this wont help for the cloned moguls. But it will help the xv6800 users if they install sprint customizations.
http://forum.ppcgeeks.com/showthread.php?p=401137#post401137
believe it or not, a few months ago i let the sprint customizations run and used it like that just for the better signal...only downfall was no data services....i just switched back to verizon radio stuff yesterday and got my data reactivated
Not to long ago i update to DCD's latest rom and radio. I never got the GPS to work for some reason though. I was wondering with the new verizon ROM out is there an easier way to get GPS. Could i flash to verizons new rom so that i have the radio and the rom and then flash back to dcds and still keep verizons radio. Becasue for some reason i just cant get the GPS to work with DCDs rom. Also i have noticed my phone lagging a TON latly and im not sure why. My contacts wont open somtimes and when i answere a call or dial out it rings but it doesnt show the phone on the screen untill about 45 seconds into the call. its been a pain coming out of sleep too and i dont think im running that much stuff on it. Any Suggestions?
(i also am getting a white spot on my screen, i have heard of this happening before. Is it a problem that gets worse and is there anything verizon can do to fix it?)
First off, if you load Verizon's latest update, you will not be able to use GPS as of yet unless you pay for VZNavigator.
If you have radio 3.42.50 and Rom 3.2.6, you should have no problem getting GPS to work.
1) Go to Settings... Phone... Services... and check the box next to 911 only. Then click ok. Exit... Soft-reset if you feel like it. Then go back and change it to Location On. Click ok... soft-reset.
2) Do the GPS - Fix found HERE
3) Download GPS Viewer... I have it attached. When you run it... hit scan.. this will find what port the GPS is on. Then select that port and hit Open Port. This will start streaming data. Go to GPS Status at the bottom... and you should see some locations popping up if you are in open air.
Let me know if you get this far.
that program you gave me doesnt work on windows mobile. thats a Computer version.
nevermindi was wrong. im just having priblems connecting to my computer. do you have a cab file?
Dmarsh508 said:
nevermindi was wrong. im just having priblems connecting to my computer. do you have a cab file?
Click to expand...
Click to collapse
Here you go.
It works!!!! Awesome! It reads the GPS port. VZ navigator still doesn't work on the xv6800. It keeps loading privacy policy and then saysits unable to getr policy setting.
But at least the GPS works now after the rom update. Thank you!
GPS won't work???
Verizon XV6800
dcd_titan_3.2.6
DCD Radio 3.42.50
SPL 240
Location set to on
(tried toggle between 911 and location on)
Ran GPSVIEW scan... found GPS on com4
set external gps program port to com4
hardware port set to none
set to automatically managed
tried reflashing rom
soft reset a million times
what else can i try?
Soon to flash...
I am probably going to finally flash a DCD rom for the first time today. It would be nice though if the images or software downloads on the GPS fix wiki were available. That's the only thing holding me back right now. GPS is the only reason to flash for me, so I want to make sure I can get it working.
GPS on VX8600 rules!
Well I finally gave in and flashed the newest DCD rom & radio. Wish I had done that a long time ago. I was having no luck with the GPS till I read this thread. The the GPS locks super fast and is VERY accurate in Google Maps. This site rules.
While I am technical, I new new to everything phone related.
I have Radio 3.37.75 and ROM 3.57.605.1
Do I need to go back and install a different Radio and Rom version to run the GPS fix and enable GPS?
Thanks!
MagnusRF said:
While I am technical, I new new to everything phone related.
I have Radio 3.37.75 and ROM 3.57.605.1
Do I need to go back and install a different Radio and Rom version to run the GPS fix and enable GPS?
Thanks!
Click to expand...
Click to collapse
You need to install a custom rom ( to replace the 3.57.605.1 VZ Rom) to enable the GPS chip on the phone. That rom has the GPS disabled. DCD 3.2.6 rom is what i'm using and it runs pretty sweet.
As far as the Radio rom goes, i dont think you have to update it. There some debates going on in the forums about wheither the new VZ radio rom is better or worse then the current radio rom that was ripped from attel. Some say its better, some say its really the same (same file size) and some say its way worse.
So in summary, to run the GPS Fix, atleast install DCD's custrom rom first. (Note: Do not let Custimization run, the rom is based off a latest sprint rom, so letting it run as a verizon users messes things up. soft reset after initial bootup after a flash and pull the battery if it starts to do it. also remember to hard reset after flashing any rom)
PS. If you flash the radio rom, you will have to do *228 again to reprogram your number back into the phone.
RiftReaper said:
You need to install a custom rom ( to replace the 3.57.605.1 VZ Rom) to enable the GPS chip on the phone. That rom has the GPS disabled. DCD 3.2.6 rom is what i'm using and it runs pretty sweet.
As far as the Radio rom goes, i dont think you have to update it. There some debates going on in the forums about wheither the new VZ radio rom is better or worse then the current radio rom that was ripped from attel. Some say its better, some say its really the same (same file size) and some say its way worse.
So in summary, to run the GPS Fix, atleast install DCD's custrom rom first. (Note: Do not let Custimization run, the rom is based off a latest sprint rom, so letting it run as a verizon users messes things up. soft reset after initial bootup after a flash and pull the battery if it starts to do it. also remember to hard reset after flashing any rom)
PS. If you flash the radio rom, you will have to do *228 again to reprogram your number back into the phone.
Click to expand...
Click to collapse
If you flash DCD 3.2.6 do let customization run, he rips out the carrier specific stuff out of the rom, so it can actually hurt not to run customization on his rom. Only stop customization run if you are flashing an original carrier specific rom that is not your current carrier, i.e. if you flash a sprint original rom on a VZ phone, etc.
While based on a Sprint rom, he has taken the time to make it safe to run on any carriers phone.
DCD's customization runs UC and I think a few other house cleaning items, so it's important for it to run.
BTC
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.