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!
Related
Hi all.
with the 6800-
I flash nexvisions rom and the new radio. After reading ppcgeeks tutorial, I thought I needed to run IOTA.cab to get my data settings even though I'm on Verizon. Well, after doing a *228 and calling verizion to get my calls to go though, my data is now screwing up.
The problem is- when I run internet explorer (with google mobile as my homepage) it chokes after about 50 K downloaded and wont finish. The data connection is lousy. If I try to close out my data connection using the connection manager it comes up with a warning about IOTA data errors.
Now I know that vzw users do not need IOTA. Is there a way to reset what IOTA does to your data connection settings without doing a hard reset? I can't find a 'unintstall' IOTA.cab anywhere.
Anyone have any ideas?
Cook ROM as Verizon, not Sprint?
Maybe just run the ROM again
I can not think of a good way to get it all out but maybe someone has an idea. I am on VZW and it worked perfectly.
You should reflash.
Perhaps you shouldn't use Nexvision's ROM since it obviously has Sprint "parts" in it that seem to be interfering.
Here is what worked and is still working very well for me. I have no data or voice issues at all right now:
Geckotek said:
In fact, all is well.
I flashed back to the stock VZW ROM (third time I think), I made sure all of my provisioning issues with Verizon were worked out (finally had the tech "kick the switch").
1) Then I proceeded to load the 2.4 bootloader,
2) then the 3.16 Unauthorized Sprint ROM w/ radio,
3) then finally installed a cooked DCD 2.3.2 ROM.
Things to note:
1) I never let the Sprint ROM boot up (this is VERY important!!)
2) I had no signal so ran *22802 then hit End as soon as it connected
3) Still no signal after reboot
4) No A key, MSID, or MDN issues, but I did re-enter the MSID and MDN as discussed in other threads
5) After re-entering MSID and MDN then after reboot I had signal (even though they are there and correct, type re-enter the information anyway)
6) never had to run *228 to OTA program (in the past programming with *228 has reversed the effect of re-entering the MSID and MDN)
In general, I feel that the OTA from VZW sends down some programming that conflicts with the 3.27 radio...but I have nothing to prove that.
GPS is running great (I just loaded the AstroGPSLauncher)
Not sure about Rev A. It does seem snappy. What's a good site to test from the phone?
I'm happy and not re-flashing until a solid radio for Verizon arrives.
Click to expand...
Click to collapse
Thanks everyone for your feedback.
First- I'll try a hard reset first and see if that clears it up.
Then if that doesn't work, I'll try reflashing nexvisions rom and see if that clears it up.
If that doesn't work, I'll reflash trying the dcd rom.
spreeway said:
Thanks everyone for your feedback.
First- I'll try a hard reset first and see if that clears it up.
Then if that doesn't work, I'll try reflashing nexvisions rom and see if that clears it up.
If that doesn't work, I'll reflash trying the dcd rom.
Click to expand...
Click to collapse
If that doesn't work, you should do like I did and start with a clean slate. All the reflashing of ROMs and radios did me no good. Whatever issues I had were not going away with just another flash from one ROM to another.
Hard resetting fix everything.
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?
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
Hi!
I have been over most of the GPS fixes but they do not seem to be working for me. I figured I would toss this out there:
It appears that there is a problem opening the GPS if one has gone from the official Verizon MR1 and then to a custom ROM. Well, without knowing that, that is exactly what I did.
I had an older DCD ROM which was running with the GPS opened.
Upgraded to the Verizon ROM MRI and lost GPS.
Tried the Valhalla fix and still couldn't get GPS opened. Figured it must have been an error in how I flashed so I went to a newer DCD ROM.
Still couldn't get GPS to work.
Flashed to the Round 4 Reloaded ROM and am currently running:
dcd 3.2.6
radio: 3.42.02
I am unable to get GPS to open with Google Maps. It searches for satellites and a few minutes and then tells me it cannot find them.
GPS settings are Location On, COM 4 (also tried it as none), Baud 4800, Hardware Port None, Windows manages GPS.
I have gone to the wiki for the GPS fix for people with custom ROM's using QPST but all of the software links from that site have been broken for weeks.
Any suggestions?
brett3333 said:
Hi!
I have been over most of the GPS fixes but they do not seem to be working for me. I figured I would toss this out there:
It appears that there is a problem opening the GPS if one has gone from the official Verizon MR1 and then to a custom ROM. Well, without knowing that, that is exactly what I did.
I had an older DCD ROM which was running with the GPS opened.
Upgraded to the Verizon ROM MRI and lost GPS.
Tried the Valhalla fix and still couldn't get GPS opened. Figured it must have been an error in how I flashed so I went to a newer DCD ROM.
Still couldn't get GPS to work.
Flashed to the Round 4 Reloaded ROM and am currently running:
dcd 3.2.6
radio: 3.42.02
I am unable to get GPS to open with Google Maps. It searches for satellites and a few minutes and then tells me it cannot find them.
GPS settings are Location On, COM 4 (also tried it as none), Baud 4800, Hardware Port None, Windows manages GPS.
I have gone to the wiki for the GPS fix for people with custom ROM's using QPST but all of the software links from that site have been broken for weeks.
Any suggestions?
Click to expand...
Click to collapse
Yes, if you had MR1 then you need to relock down to Pre-GPS radio status. Then do a normal upgrade.
I dont have the links handy right now but I am sure someone does.
Tried going to phone options?
Have you tried going to the phone options by hitting the phone button go to menu then options and click the services tab. Then look for Location and turn it to ON. It fixed my problem with this been awhile though i switched to sprint and bought a Touch Pro
scrosler said:
Yes, if you had MR1 then you need to relock down to Pre-GPS radio status. Then do a normal upgrade.
I dont have the links handy right now but I am sure someone does.
Click to expand...
Click to collapse
Can I just reload the radio down and back up again without changing the ROM or do I have to reflash the ROM as well? I have your ROM set the way I like it...so far it seems great!
brett3333 said:
Can I just reload the radio down and back up again without changing the ROM or do I have to reflash the ROM as well? I have your ROM set the way I like it...so far it seems great!
Click to expand...
Click to collapse
No, your going to loose the ROM. I think I put SPB BackUp in there just for purposes like this. Go ahead and use that. It works great with this device / ROM. After you do that pay close attention to the downgrade instructions. Not hard but be careful. You wont hose the device but you may not get the results you expected.
Post back any other questions or problems.
Ranger093 said:
Have you tried going to the phone options by hitting the phone button go to menu then options and click the services tab. Then look for Location and turn it to ON. It fixed my problem with this been awhile though i switched to sprint and bought a Touch Pro
Click to expand...
Click to collapse
YEah, this is not like what you resolved yours. He has a radio firmware / SPL issue to deal with. I wish it was that easy.
Look for the original stock Verizon rom, its the one with Mobile 6.0, once you have flashed this, then follow the normal procedure to flash a custom rom, SPL, Radio and then rom, and you will have GPS. There is no other way to do this other than to flash back.
BTC
Well, I have tried going back to the stock Verizon ROM/Radio pre-gps. I have now been stuck in the tri-color mode for an hour. Exitbl is not working for me and I cannot seem to get back to any workable ROM.
SPL is now at 1.06 so I think I properly relocked. I just cannot get into the OS now.
Help?
Thanks Billy! I found the original WM6 Verizon ROM here (in case anyone else also has trouble):
http://forum.xda-developers.com/showthread.php?t=376873
and that seemed to be acceptable to the phone to get it out of bootloader mode. Whew.
Now I will pretend I have a brand new old ROM/Radio phone and bring it back up to speed without going through the "official" Verizon MR1 piece of garbage.
Thanks to everyone for the assistance. Hopefully, my next post will say: done and have GPS back. We'll see...
brett3333 said:
Thanks Billy! I found the original WM6 Verizon ROM here (in case anyone else also has trouble):
http://forum.xda-developers.com/showthread.php?t=376873
and that seemed to be acceptable to the phone to get it out of bootloader mode. Whew.
Now I will pretend I have a brand new old ROM/Radio phone and bring it back up to speed without going through the "official" Verizon MR1 piece of garbage.
Thanks to everyone for the assistance. Hopefully, my next post will say: done and have GPS back. We'll see...
Click to expand...
Click to collapse
Sorry I assumed you had the links. My bad. But yes, you would have been stuck at the tri color screen. That is normal for what you did.
I was able to get back to the R4R and now with the suggested radio following my downgrading to stock however, I am still unable to get GPS.
Now, Googlemaps just says "initializing" and then fails.
Now double check your settings. Under options in Google Maps, make sure it's set to Com Port 4 for GPS, make sure in Settings on the phone that your GPS settings are set to Com 4 and hardware Com 0. And then double check your location settings.
I bet you'll find one of those set wrong.
BTC
brett3333 said:
I was able to get back to the R4R and now with the suggested radio following my downgrading to stock however, I am still unable to get GPS.
Now, Googlemaps just says "initializing" and then fails.
Click to expand...
Click to collapse
BillThyCat said:
Now double check your settings. Under options in Google Maps, make sure it's set to Com Port 4 for GPS, make sure in Settings on the phone that your GPS settings are set to Com 4 and hardware Com 0. And then double check your location settings.
I bet you'll find one of those set wrong.
BTC
Click to expand...
Click to collapse
Phone: Location on
GPS Program Port: COM4
GPS Hardware port: COM0 (this had been set to none)
Baud: 4800
Access: manage automatically
Googlemaps: Set GPS Manually, COM4, 4800 Baud (This had been set to manage autamatically)
Okay...now, it no longer says "initializing GPS" but is actually seeking and finding satellites.
Holy crap Bill, you rock!
Did you update the PRI?
abuttino said:
Did you update the PRI?
Click to expand...
Click to collapse
Yup, I had to update the PRI and was able to get Google Maps to work now. Still cannot get LiveSearch to get a GPS fix (it is set to intermediate) but I am trying not to be picky.
Just to recap (for a mod newbie)
I'm having a similar issue, but just wanted to clarify before I go about the break-fix-break scenario... I was able to get MR1 (with the Valhalla fix) to use the GPS fine. Then went to R4R and nothing. Haven't tried the QRST fix yet, but in my case, you think going back to the stock WM6.0 ROM/Radio, then back up to R4R (or dcd, or nuerom, etc) will resolve this? Will it 'stay' fixed when moving from rom to rom after that, or will I have to do the back and forth thing every time I want to try a new one?
Thankee kindly!
GPS and MR1
So if I am reading this correctly there is no way to get GPS working under Verizon if MR1 had been flashed into the device, then the device was unlocked and flashed with a ROM from the DCD 3.2.6 kitchen. Is that correct?
ksquake said:
So if I am reading this correctly there is no way to get GPS working under Verizon if MR1 had been flashed into the device, then the device was unlocked and flashed with a ROM from the DCD 3.2.6 kitchen. Is that correct?
Click to expand...
Click to collapse
No, further up it says that one has to go back to the PRE MR1 ROM, and then go to the DCD rom from there (MR1 does something funky to the GPS?), but I'd rather have someone smarter than I to verify.
To clarify
So if I am reading this correctly there is no way to get GPS working with the radio installed by MR1 if using a ROM from the DCD 3.2.6 kitchen. Is that correct?
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.