Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
blueglide said:
Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
Click to expand...
Click to collapse
well if you mean that activesync wont connect in bootloader, then yes. i had this happen to me during reflashing. just run the RUU while the device is connected to your computer. should work fine. also, if you hard reset, make sure you let it boot before entering bootloader.
Problem solved...but i have no idea why!! I downloaded and installed the 3.1.2 ROM already cooked in the original post and flashed that. Hooked up my PPC6800 via USB and instantly Activesync saw my device and synced. Everything is working fine. Still have no idea what could be the difference as I used DCD's 3.1.2 kitchen for my cooked ROM. I did not add anything other than what was in his kitchen but at least it upgraded this time.
Related
Got the radio upgrade 3.3x and all works well with 2.x dcd rom, but upgrading to 3.0.1 has problems with phone calls. Both receiving or outgoing, the device resets 10 sec into the call. Also Voice Command 1.6 not working. sucks.
verizon xv6800
I'd be willing to bet millions you didn't follow directions when flashing.
Nope. Cooked a kitchen, tried the Verizon Rom....neither work with 3.0.1. works great with 2.x though.
Voice Command 1.6 now working OK as well under 2.3.2. I is happy. Still looking for good GPS software. I really liked Earthcomber, but doesn't work with this rom.
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
OK so I cry for help. Why the heck would I apply a Sprint update to a Verizon handset, granted both CDMA. I upgraded the radio at the same time as 2.2. The 2.2 DCD rom I'm using that WORKS WELL should be no different than the upgrade to 3.0.1. Unless I'm forgetting to stop customization with a soft reset.
You're not getting the point!!!
The only reason to flash sprint's official rom is so you can update the radio to its latest version. After this is done, it DOESN'T MATTER whatever rom you flash next, such as a Verizon rom. Use DCD's 3.0.1 rom it should be working. You would have known this if you read instructions. If you flashed the radio alone first, then your settings (ESN, MSID, etc) will be wiped. You will have to re-enter these either manually or call up Verizon to do it for you. This is probably why you can't make calls.
Exactly my point. I flashed the radio with the Oli 2.4 and updated the radio from stock verizon. Then flashed 2.3.2 and all is good with the new radio. So why doesn't it work with 3.0.1? I just found my way to the In and Out Burger via Odyssey Mobile locator.
Everyone keeps telling me that i didn't follow the destructions but they don't point to where they are.
Maybe wrong radio ver?
Crap. Mine says 3.24.00. I guess that's my problem. I'm an idiot.
Please point me to the proper radio D/L.
Thanks,
Sorry for asking what is probably a simple question, but I am having the same problems. I have SPL-2.40.Olipro atm, installed the verizon ROM upgrading to 3.0.1 from NexVision's Hybrid rom. My radio is upgraded to 3.25 or whatever it was supposed to do fine. On vibrate mode, when a phone call is incoming, I get stuck in an ever ending vibrating. I can text, and attempt to cal lsomeone but nothing can be heard and no one can hear me. I know i screwed up somehow- but what exact steps do I do to remedy this?
Thank you in advance
We have to do the Sprint radio update to 3.35 first, which is an upgrade from 3.27. Then go to ROM 3.0.1.
It's always interesting to me how people jump up to say "you're doing it wrong" but don't tell you how to do it right.
Here's how to do it right.
http://forum.ppcgeeks.com/showthread.php?t=17667
Gecko122, There is more to the Sprint file than just the radio... It includes the ROM as well.... My understanding is this:
1st - Run Olipro unlocker 2.4
2nd - Run Sprint Official upgrade , NO CUSTOMIZATIONS.
3rd - Load Custom ROM.....
That has worked for me.....
PS - the DCD 2.x.x series do NOT play well with the new radio, hence the 3.0.1 kitchen.... Driver differences....
do i have to flash back to a former version of dcd or anything? or can i start from a messed up 3.0.1?
hi Penn,
Well, exactly what have you done to your phone?
Bootloader version?
ROM version?
Radio Ver?
Then we can start from there and develope a plan to help ya.
Ignore that above - I re-read you original post....
Here's what you can do and correct me if I'm wrong Penn...
You have Oli-pro 2.4 bootloader loaded
You have DCD 3.0.1 ROM loaded
You have the 3.27 Radio loaded?
If the above is true, then we have options..... Let me know
gcincotta said:
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
Click to expand...
Click to collapse
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
Click to expand...
Click to collapse
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Gecko, the reason why I did not "tell" you how to do it the right way is because dcd's thread has 94 pages of information on how to do it the right way. I've even posted several times on different pages in that thread with explicit instructions on how to. While I am always very eager to welcome newcomers to this community, I also strongly encourage them to read, research and educate themselves before touching their device. It doesn't mean I'm not a nice guy and don't like to help, because if you search my posts you will see that I help a lot around here. If you had simply taken 20 minutes and even skimmed dcd's thread, you would have found the answer yourself in no time.
gcincotta said:
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Click to expand...
Click to collapse
Wow... I'm sorry, I had not been keeping up with the issues of others, so until you said that just now, I had no idea. You are right, I am really lucky, so thanks for bringing it to my attention.
No problem
Had dcd 3.1.1 installed running fine. This morning decided to upgrade to 3.1.2. Another post advised it was easy to upgrade using sprite backup (new version allows restores across dif device platforms and OS) so I wouldn't spend several hours...again...tweaking my device. Made a backup and flashed dcd 3.1.2. Installed fine and then I used Sprite to reinstall my software. Device appeared to be restored back to dcd 3.1.1 and Activesync would not connect. Sooo I figured I would start from scratch again and did hard reset. Rom is dcd3.1.2...phone works...boots....everything appears normal but still no activesync. Tried disabling 'advanced network funtionality' on device...several reboots...uninstall activesync...reinstall...etc etc...still no connection. I've searched and tried the suggestions mentioned but I'm at a loss. Does anyone have any ideas how to get activesysnc to connect. BTW...when I connect via USB I hear 'chime' and the activesync icon spins but then times out with no connection. Sorry for lengthy popst but I wanted to try and provide all info....help please!?!?
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Well..I fixed it...sorta....reflashed 3.1.1 with SD card and all is well again...I think I borked up something when I used Sprite....not gonna do that again. Will try 3.1.2 again and tweak for a few hours.
edsai said:
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Click to expand...
Click to collapse
if you have data you can always download it from the thread but I suppose that wouldn't work without verizon customization...hm...I was going to flash to this (sorry nochem dcd comes out with a really stable and fast rom, now about that kitchen...)
at any rate...I hope the problem gets settled
Well 3.1.1 works great...flashed 3.1.2 via SD card and back to same problem...no activesync and no data. Strange...I have the updated Alltel radio on my device. Anyone else experiencing this. I'm on Alltel
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
gcincotta said:
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
Click to expand...
Click to collapse
Yes...installed the proper alltel carrier cab...still didn't work. Am considering downloading 3.39 radio and see if dcd 3.1.2 will work with that radio...currently I have the new alltel radio.
I realized that I forgot to upgrade the radio shortly after upgrading to the dcd 3.1.2 rom. Now my phone can't send/receive calls (it either restarts when I make a call, or it makes/receives the call with no sound).
How do I upgrade to the Alltel 3.37 rom (the one I need for my verizon phone, right?) without using an micro SD card.
Thank you!!
I dont think it is possible. You are going to want to go the route of the SD card. I am fairly certain you will need to flash to Stock(see the Wiki). Then start over with the Radio 3.35 or 3.39 then DCD 3.1.2. 3.39 is better on the 6800 in my eyes. It cleared up dropped calls and signal issues.
Dont forget to run the Verizon Cab and not to allow Sprint to customize.
Thanks for the reponse but I fixed it; I installed the Alltel radio rom (3.37.20) which also downgraded the O.S to the previous (but not stock) windows 6.0. Now that the radio had been upgraded, I then reinstalled the DCD 3.1.2 windows mobile 6.1 rom. Internal GPS and REV A work like a charm!
edit
PS I hate using the SD cards. I like updating through USB from my pc, because if I run into any problems I can just push another rom through the bootloader and it's all back to normal. It's safer IMHO, and saved my phone countless times where the SD never could have.
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