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
Related
Hi all,
So I installed the Official Sprint ROM issued this month and I have the following problems:
- Battery won't last more than one day
- Phone won't wake up from standby at certain times
- Phone slow after running some applications, including built-in apps like Word, Excel, or IE. Sometimes this result in the phone just simply hanging
In either situation above, except battery issues, a soft-reset is required.
I have tried the following:
- Do a hard reset, try without ANY applications
- Remove HTC_CM_Guardian.exe and SDDAEMON.exe
Anyone have the above three problems? with the new Sprint Official ROM?
I feel like going back to the old Sprint ROM. I have a separate BT GPS, so I don't care about A-GPS functionality as long as my phone is stable.
Why don't you cook a clean rom with the 3.0.1 kitchen and get rid of the sprint rom?
One question - did you let the customizations run after you installed the ROM?
If not, you need to hard reset let the customizations run, hard reset again and then you can bypass the sprint customization.
Otherwise......
......now that you have the new radio installed, I'd recommend trying one of the clean ROM's from either No2Chem (over at PPCGeeks) or DCD's 3.0.1 ROM.
DCD's has a "Touch" look to the skins and has over 24MB of RAM free on first boot.
All you'd need to do is run the 2.40 Olipro SPL unlocker and then flash DCD's 3.0.1 ROM.
Much more stable than the OEM.
nosmohtac said:
One question - did you let the customizations run after you installed the ROM?
If not, you need to hard reset let the customizations run, hard reset again and then you can bypass the sprint customization.
Click to expand...
Click to collapse
I did on the 1st try, but something gone wrong, most troublesome is that the "Text Message" account now shown in Pocket Outlook. So I hard reset again and let the customizations run.
nosmohtac said:
Otherwise......
......now that you have the new radio installed, I'd recommend trying one of the clean ROM's from either No2Chem (over at PPCGeeks) or DCD's 3.0.1 ROM.
DCD's has a "Touch" look to the skins and has over 24MB of RAM free on first boot.
All you'd need to do is run the 2.40 Olipro SPL unlocker and then flash DCD's 3.0.1 ROM.
Much more stable than the OEM.
Click to expand...
Click to collapse
So you're saying that it's better to use Sprint's official Radio but use DCD's ROM?
What I gather from this forum and PPCGeeks is that people either use Sprint's Official Radio and ROM or just forego that and use kitchen's ROM completely, but not a combination of both as mentioned above.
[EDITED]
OK, so I got Olipro and DCD 3.01 Kitchen. Just so I am doing the right thing since I have ALREADY installed Sprint Official Rom with Radio v. 3.35.05, please let me know if this step is correct:
1) Connect to ActiveSync. Sync as usual
2) Run Olipro v. 2.40. This will open a Command Prompt. Let it do it's thing.
3) Once done, load DC 3.01 Kitchen ROM. No other Radio ROM needed.
4). Done.
Am I correct?
There is no radio with the kitchen. The sprint official radio release (3.35.04) is the official radio whether you use the sprint official update rom or a custom rom of your choosing. No other radio works with the newer roms except this radio. That is why if you choose to use a custom rom, you STILL have to flash the sprint update to get the radio, then you flash your custom rom on top of it (with no radio) to get your own rom on there.
lanwarrior said:
Hi all,
So I installed the Official Sprint ROM issued this month and I have the following problems:
- Battery won't last more than one day
- Phone won't wake up from standby at certain times
- Phone slow after running some applications, including built-in apps like Word, Excel, or IE. Sometimes this result in the phone just simply hanging
Click to expand...
Click to collapse
I've cleaned that ROM (gutted to the base OS and functions) and have experienced none of those issues and none of those complaints are voiced in the thread using that kitchen.
I do not think that your problems are due to that specific base of Sprint ROM. Possibly some of the apps or simply a bad flash? Did you attempt to remove HTC Guardian or other components from within the active OS or did you extract and build your own ROM from the Sprint?
For severe battery problems there a couple of threads where a few people have experience excessive drains, but that's with the more recent DCD builds.
gcincotta said:
There is no radio with the kitchen. The sprint official radio release (3.35.04) is the official radio whether you use the sprint official update rom or a custom rom of your choosing. No other radio works with the newer roms except this radio. That is why if you choose to use a custom rom, you STILL have to flash the sprint update to get the radio, then you flash your custom rom on top of it (with no radio) to get your own rom on there.
Click to expand...
Click to collapse
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Keystone said:
I've cleaned that ROM (gutted to the base OS and functions) and have experienced none of those issues and none of those complaints are voiced in the thread using that kitchen.
I do not think that your problems are due to that specific base of Sprint ROM. Possibly some of the apps or simply a bad flash? Did you attempt to remove HTC Guardian or other components from within the active OS or did you extract and build your own ROM from the Sprint?
For severe battery problems there a couple of threads where a few people have experience excessive drains, but that's with the more recent DCD builds.
Click to expand...
Click to collapse
Yes, I tried it after Hard Reset. I did remove HTC Guardian from the active OS.
lanwarrior said:
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Click to expand...
Click to collapse
You are correct, you can flash any custom ROM on top of Sprint's. DCD's is a good choice.
lanwarrior said:
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Click to expand...
Click to collapse
That is correct.
DCD's ROM doesn't include the Radio, and the new radio version is what unlocks the GPS and EVDO REV A features. The SPL unlocker is what allows you to load ROM's that aren't OEM on your device, and If you aren't familiar with how to build your own ROM using DCD's kitchen (it's pretty easy once you get started), then he has carrier specific ROM's already linked on his most recent release page. The links are just above the images.
http://forum.xda-developers.com/showthread.php?t=376150
Yeah just unlock with olipro 2.4, then you have a choice between dcd (which I personally use) or another clean rom like no2chem's.
same issue as stated in first post
Hey just want to say great site guys! There is no other website that can comes close to the knowledge available here. But in response to the who started this thread the official sprint rom is crap! Once phone goes into standby or "LOCK" 99% of the time "Soft Reset" is required. Ive "Soft Reset" my mogul no B.S. 100 times since I've flashed there ROM. Radio is a great improvement but honestly, they need to hire or pay NOCHEM or DCD for their talents because w/out their ROMS the MOGUL would've ended up on the side of the highway. I agree with the last post. Use the official radio, but don't run yourself through the wringer with the SPRINT ROM. You will rip your hair out!
meek420, again, I've had zero issues of lock-ups using a cleaned out version of the Sprint ROM.
I do not think such problems are endemic to that ROM.
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
Hello all!
I'm running dcd 3.2.6 with 3.42.40 radio and a Titan on Verizon. The GPS was working with Google Maps with the Verizon 6.1 update, but the phone was so slow to use (and no BT ICS), so I went to dcd. Since then, I get BT ICS, and the phone is much faster, but the GPS cannot lock on any sats. Any ideas?
I'd check to make sure all your aGPS settings are correct using QPST.
Already did that, but I checked them again to confirm.
What next? Is there a CAB I need to install? Should it just work out of the box?
it should work fine. Makesure it's set for com4 in google.
Actually I got my gf a touch and it was working fine til earlier this week now its back to the slow non aGPS where we have to wait 15 mins to get a lock. and i just got a new titan and cannot get gps working on the nuerompre3 rom. Maybe they blocked it?
did you make sure the location setting was set to on and not to 911 only?
It is on COM4, and it is set for Location Only. It was working with the Verizon MR1 release...
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
BillThyCat said:
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
Click to expand...
Click to collapse
That was it! I re-locked and flashed with a stock Verizon rom, and then installed SPL 2.47, dcd 3.2.6, and radio 3.42.40 and everything works perfectly! GPS, BT tethering / internet sharing, and it's quite responsive. Thanks for the tip!
No verizon ROM, but still the same problem
Well, I've never used a Verizon ROM (I'm in Mexico city, my carrier's IUSACELL), but I have the same problem. I got GPS working with DCD 3.2.5 and after upgrading to Radio 3.42.30 and DCD 3.2.6 (same day, one after the other), I've been unable to lock onto a satellite in spite of leaving the unit in the open for over half an hour and prepping the unit with toggleGPS.
I've tried flashing back the radio and ROM to the working versions and even cooked several ROMS using PPCKitchen, to no avail. The system can open the port, does read up to 7 satellites, but cannot lock onto them.
I tried setting the GPS up with the QPST tool and Verizon settings, and got nowhere.
I'll try and relock and unlock tip that eclipse used, but maybe I'm missing something here...
any help will be mucho appreciated.
Thanks
Hey there. I found the aGPS settings for IUSACELL here (site is in spanish and the info is on post 27 of this thread). I'll reproduce them here for quick reference:
PDE IP: 207.83.200.238
PDE Port: 8888
PDE Transport: IP
Position Calculation: PDE
I've tested them using dcd radio 3.42.50 and they work like a charm
Anyone know if/how we can get them listed in the tutorial and/or included in the Iusacell carrier cab?
I know I'm a senior member..and as a senior member I should know better than to ask something nooby like this: so please excuse my noobness and help me out!
I'm considering on flashing to dcd's 3.2.6 ROM but I had a couple of questions in mind first:
1) I'm on Sprint running on Evdo Rev. A speeds, I was wondering if I'd still have these speeds after flashing to dcd
2) I read about several GPS problems after flashing to dcd..but most of them came from Verizon devices..will this happen to me if I did the same?
3) Does it have MS Office Mobile in it as well?
Thanks a lot to whoever answers me! I really appreciate it!!
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
drnoir said:
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
Click to expand...
Click to collapse
Helps a lot drnoir! Appreciate it, will flash to dcd tonight
I have spent hours trying to fix this GPS thing. I followed this tutorial (http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix) to the letter. Everything on the phone works fine except this gps. What am I doing wrong???
-I upgraded to the VZW MR1
-Then switched to DCD3.2.5 (Radio 3.42.4)
-Then followed that above link
Nothing seems to work.
If you aren't going to use MR1, then don't upgrade to it. Downgrade back to official Verizon WinMo 6.0 stock rom, then unlock, flash to a newer radio and then flash DCD 3.2.6 and your GPS will work.
The Valhala cab thing only works if you are running MR1, if not, then you don't want to install MR1 or it will disable your GPS.
BTC
I have read so many of these xda and ppcgeek threads now my brain is spagetti. I have also come across MANY conflicting threads discussing the whole GPS issue - on a wide range of ROMS, radios etc. Is there a tutorial on how to do this?
The only reason I switched to DCD's ROM was I was hoping to get ICS working. Alls I want is a WM 6.1 ROM that will give me unrestricted use of my GPS, and ICS to work properly.
Go to Settings > System > Device Information...
What PRI (Not PRL) version are you running?
chs200123 said:
The only reason I switched to DCD's ROM was I was hoping to get ICS working. Alls I want is a WM 6.1 ROM that will give me unrestricted use of my GPS, and ICS to work properly.
Click to expand...
Click to collapse
Try my rom gps works and ICS (usb) the only conflict is mms but should be working soon
scrawnyb said:
Go to Settings > System > Device Information...
What PRI (Not PRL) version are you running?
Click to expand...
Click to collapse
Rom Version: 3.2.6
Radio Version: 1.42.40
Hardware Version: 0003
PRL Version: 51210
PRI Version: 1.35_002
ERI Version: 4
BillThyCat said:
If you aren't going to use MR1, then don't upgrade to it. Downgrade back to official Verizon WinMo 6.0 stock rom, then unlock, flash to a newer radio and then flash DCD 3.2.6 and your GPS will work.
The Valhala cab thing only works if you are running MR1, if not, then you don't want to install MR1 or it will disable your GPS.
BTC
Click to expand...
Click to collapse
Dude you are a genius!!!! Your quick instructions have finally ended a long hunt in searching for this solution. After I did what you told me, I have both blazing fast GPS connectivity, and fully working ICS. I want to mention a few things in case anyone else runs into the issue I did.
First, after I successfully downgraded, and then reinstalled DCD’s 3.2.6 (radio 3.42.50 & PRI 1.35_002), I did NOT follow the instructions to enable AGPS. I dont know if this is being overlooked somehow on all these forums, but after I installed my carrier cab, with DCD’s 3.2.6 ROM, everything worked as is. There was no need to install anything else. Also keep in mind, that I did exactly as BillThyCat instructed, and that was flashing directly from the stock WinMo 6.0 (no MR1 update) to DCD’s 3.2.6.
If I read your last response correctly, it sounds like you did not do the aGPS fix afterwards. It's not a requirement, but it will get you 15-20 second GPS locks almost every time you try. It's well worth it.
Glad you got everything else working tho. Your issue is a pretty common problem. With most carriers you want to load their latest stock rom then upgrade from, however Verizon being the bastages that they are, lock the GPS down. There have been a few work arounds found, named the Valhala cab, however if you are going to run a custom rom anyways, why even mess with all that. Just use a custom rom and work.
BTC
Yes, I did not do the AGPS fix posted on that wiki site. Im not sure I understand why doing that AGPS fix would give me 15-20 second GPS locks, when I have like 8-10 second GPS locks now. Perhaps the magic is just in the latest radio. Either way, I'm happy with the way it all worked out.
When I first programmed my phone I would get syncs instantly one day and 10 minutes or more the next. If you are consistantly getting them in 8-10 seconds don't mes with anything, just keep in mind if that nice feature goes away that aGPS is available in the future.
BTC
I've got a refurbished Verizon XV6800 that had the latest Verizon ROM installed (radio 3.37).
I unlocked with No2chem SPL 2.47 and flashed a GPS PPCKitchen ROM.
The phone is flashed for cricket.
I can not get GPS to work. I upgraded the radio to 3.42.50.
GPS stil does not work. I added GPS toggle and quick GPS but they did not help either.
I've read about the Verizon MR1 update and how GPS would not work after it is installed.
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?
I've searched this awhile now, and can't find a specific set of instructions for a GPS enabled Verizon to get GPS working with a custom ROM.
If I can flash a pre-MR1 Verizon ROM, where would I find it?
Thanks for any help.
Check here as Mr-Free stated.
http://forum.xda-developers.com/showthread.php?t=444342&page=80
also see post 803 in that thread...
That was taken from the last couple of pages of the Official Verizon Wireless GPS/aGPS Discussion thread.
edit: fixed link
http://forum.xda-developers.com/showthread.php?t=376873 his link is not working for me so i gave you this.
you can go down to stock
GeLopez said:
http://forum.xda-developers.com/showthread.php?t=376873 his link is not working for me so i gave you this.
you can go down to stock
Click to expand...
Click to collapse
I've read this thread, but it was written before GPS roms, and I don't think it addresses the issue of downgrading radios from 3xx (3.42.50, in my case).
skank_boy said:
I've read this thread, but it was written before GPS roms, and I don't think it addresses the issue of downgrading radios from 3xx (3.42.50, in my case).
Click to expand...
Click to collapse
The stock rom contains the downgraded radio as well.
Thanks for your help, but I need to know.
I've heard going back to a non-GPS radio is really dangerous (this is a non-GPS radio, right?)
Just don't want to brick it.
It's very hard to brick this phone. I am one of the few that have, but, wasn't due to software issues, it was hardware. I've gone down to stock plenty of times and it's not that hard. In order for you to use a custom ROM WITH gps and yer trying to flash from a stock 6.1 rom, you HAVE to flash back to a 6.0 rom and then upgrade from that or gps will not work. Check out the guides mentioned above and the guide in the wiki.
Thanks for the advise, folks.
I will...(gulp)...give it a try.
If you hear screaming from the direction of Dayton, Ohio you'll know why.
lol
Thanks again.
i think i heard screaming already do you need us to call an ambulance?
I downgraded, and then upgraded successfully.
Now I just need to see if GPS is working.
>>EDIT<<<
GPS is working! Thanks so much for the help guys! I've done about 12 Moguls, but this was the first VZW one, so it was a new problem for me.
..but there is something weird. My data connection keeps starting up by itself.
I done everything as I always do, but I've never had this quirk before.
Could it be a radio problem?
Thanks.
skank_boy said:
I downgraded, and then upgraded successfully.
Now I just need to see if GPS is working.
>>EDIT<<<
GPS is working! Thanks so much for the help guys! I've done about 12 Moguls, but this was the first VZW one, so it was a new problem for me.
..but there is something weird. My data connection keeps starting up by itself.
I done everything as I always do, but I've never had this quirk before.
Could it be a radio problem?
Thanks.
Click to expand...
Click to collapse
With every ROM I've used including all the official Telus ROMs I'm pretty sure the data connection always connects by itself...
The only application I had that wouldn't start a data connection on it's own was SBSH Weather (it had a specific option to automatically establish a data connection).
I've been fighting a similar problem,trying to learn ppc kitchen.Every rom I've made can't get the data connection to stop,keeps cycling back on