After i upgraded to this radio i have had interesting problems with my phone. ithought it was bricked and it very well could be. But sometimes it decides it wants to work but after a minute or two it cuts off. when a softreset or hard reset are perfromed i get nothing but a white screen. I can tell it goes thru the whole process bekuzz usually after putting it to sleep a few times i get my regular screen but the radio doesnt seem to be connected. any help would be appreciated. also the buttons on the face of the phone dont seem to work.Thanx
What is "Regular Screen"?
Regular screen means the screen u would normally get after your boot and splash screen. Or better said my today screen. Sometimes i cant get my today screen up. i had BL 1.04 before the upgrade if that matters any
Today screen is very good! your device isn't fully bricked. It may be a bad radio flash or it may be a hardware issue that merely coincided with your radio upgrade. Next time you get a today screen, try to flash one of the other sspl based radio only updates (find in wiki under radio only upgrades). Remember to practice safe flashing techniques!
usb on rear usb port. No usb hubs!
all winapps closed
running winXP Pro
activesync connected
screensaver/sleep mode off (flashing takes 20+ minutes)
i have flashed the 1.27 radio again without having my today screen and that did nothing. It went thru the whole process of flashing and everything but same results, just a white screen when booting up and afterwards. im downloading the 1.34 radio now.
You need to flash the sspl version which requires first being on the Today Screen (not white screen). Tri-color boot screen will show v1.09-Des if you do this.
i guess i will have to wait to see if i get another today screen and hope that it doesnt reset itself
does it matter that i can put my phone to sleep and wake it up over and over, i just keep getting the white screen. bekuzz now i cant seem to get my today screen back anymore
ok i have done what u said and flashed the 1.34 radio and still have the same problem. after the flash i had my today screen for a minute then it reset itself and now is gone and back to the white screen. also when i was on the today screen i didnt have control of the buttons only touch screen.
i think i may have a different problem. it doesnt seem to be resetting itself everytime it goes blank but that the screen is dying on me. hmmmmmm....... this is quite strange. i can also recieve calls. i cant answer them but the handset rings.
This may be silly but if I were in your place I'd just reflash everything with an official rom that replaces everything (i.e. SA 1.35) and see if that fixes the problem (though i might wait until somebody who knows more then me verifies this is a good thing to try). I'm wondering if the bad flash somehow effected something in your OS or something.
When I mess something up like this, I like to get back to a place which has been known to work - then I have a better idea of where I am (ie brick or bad flash)
Hope this helps
yea i actually went back to the original cingular ROM that came with the phone. so we shall see what happens from here. i also will have Cingular send me a new phone, i was tired of the scratches anyway. So far they havent noticed that my phones are supercid yet. Keeping my fingers crossed
Hardware problem IMHO...
Sleuth u are right. No matter what i do to the phone it yields the same result. My screen still turns off and the buttons dont work. iwonder what couldve caused this. i didnt drop it. well not recently anyway. BTW.... is there anyway to get the original 1.16 radio back on there. i tried doing it but it just hangs at 0%.
Thanks Sleuth for all your help, you are definetly one of the reasons this forum is helpful. That and that good ole WIKI.
OK, I've been thru this twice now, so I'm pretty sure it's not a busted phone...
Personally, I've got a Sprint Mogul - runnin' Radio 3.39.10, and DCD 3.1.2 - everything's peachy-keen.
At work, I've got some XV6800's, stock, right outta the box.
I did the following the phone #1, didn't work at all (as described below), and repeated on phone #2 after thinking #1 was just a bad phone.
HELP!?
Phone #1:
Took it out of the box, booted it, let customization run, activated it - everything's happy-scrappy.
Flashed spl-1.20-olipro.
Went into boot-loader, flashed Radio 3.39.10 with RUU (don't have a card to do the SD method with - seemed to work fine)
Went into boot-loader again, flashed DCD 3.1.2
Booted to the first WM 6.1 screen, flashed spl-2.40-olipro.
Booted into DCD 3.1.2, can make calls, rcv/end txts...
NO DATA - and NO LOCK WITH GPS (installed QuickGPS & VisualGPS) - NOTHING.
Called VZW - spoke to some schmuck, said phone was busted, would send new one...
Phone #2:
Same process as #1, except I didn't activate this one with VZW, wanted to see if I could get GPS to lock up first... It sees Zero birds... NOTHING...
Since I got the same result with both phones, I'm assuming I missed something.
Yes, I ran DCD's carrier .cab for VZW on Phone #1, but it didn't solve anything. Didn't bother on #2 - I shouldn't have to do this for GPS, should I?
Please... What am I missing??? Anybody?
NetworkPIMP said:
OK, I've been thru this twice now, so I'm pretty sure it's not a busted phone...
Personally, I've got a Sprint Mogul - runnin' Radio 3.39.10, and DCD 3.1.2 - everything's peachy-keen.
At work, I've got some XV6800's, stock, right outta the box.
I did the following the phone #1, didn't work at all (as described below), and repeated on phone #2 after thinking #1 was just a bad phone.
HELP!?
Phone #1:
Took it out of the box, booted it, let customization run, activated it - everything's happy-scrappy.
Flashed spl-1.20-olipro.
Went into boot-loader, flashed Radio 3.39.10 with RUU (don't have a card to do the SD method with - seemed to work fine)
Went into boot-loader again, flashed DCD 3.1.2
Booted to the first WM 6.1 screen, flashed spl-2.40-olipro.
Booted into DCD 3.1.2, can make calls, rcv/end txts...
NO DATA - and NO LOCK WITH GPS (installed QuickGPS & VisualGPS) - NOTHING.
Called VZW - spoke to some schmuck, said phone was busted, would send new one...
Phone #2:
Same process as #1, except I didn't activate this one with VZW, wanted to see if I could get GPS to lock up first... It sees Zero birds... NOTHING...
Since I got the same result with both phones, I'm assuming I missed something.
Yes, I ran DCD's carrier .cab for VZW on Phone #1, but it didn't solve anything. Didn't bother on #2 - I shouldn't have to do this for GPS, should I?
Please... What am I missing??? Anybody?
Click to expand...
Click to collapse
personally i am running the 3.35.04 radio with more luck and quick gps lock. i also am using 3.1.2 dcd rom
and as far as data.... you have to have a dmu reset for it to work i'd just call and tell them you want a DMU reset i've had to do it more than once
EDIT also i have changed GPSmode to 4 instead of 2
coffey_joshua said:
personally i am running the 3.35.04 radio with more luck and quick gps lock. i also am using 3.1.2 dcd rom
and as far as data.... you have to have a dmu reset for it to work i'd just call and tell them you want a DMU reset i've had to do it more than once
EDIT also i have changed GPSmode to 4 instead of 2
Click to expand...
Click to collapse
Thx for that, Josh... I changed my GPSmode to 4, but to no real joy...
I figure I need the DMU reset and/or new AKEY from VZW - which I'm fine with calling and getting - but, I've got no workable GPS on either of these phones, and I'm still thinking that it's independent of data/activation, right?
BTW - let me define "workable" -> I put my Mogul next to either of these 6800's and turn on VisualGPSce, and the Mogul finds 7-10 birds and locks on within 5-20 seconds... This = "workable" to me. The 6800, on the other hand might see 1 or 2 birds, on occasion, then back to zilch, and never a lock. (This applies to BOTH of the 6800's I have in front of me!)
Also, I'd like to add that yes, I did turn Location ON in Phone/Options...
I've seen some of the big-wigs here seem to be running 6800's with DCD and Radios 3.35.04 & 3.39.10 with good results - i.e. a LOT better than mine...
So I ask again - any other idears!?
Like I said, no troubles on my Mogul - so what am I doing wrong? I'm pretty sure it's me .
Very frustrating seeing all the success others having with VZW phones, but not me? I'm noob-like, but I'd like to think I can hold my own!
Thx in advance to ALL!!
having the same problem, using new dcd with newest radio. tomtom 6.01.
i can surf the internet, does that mean i have data? or will i still need to reset dmu/akey? what's akey?
I can get a gps signal at all. using astro luancher.
auto3251 said:
having the same problem, using new dcd with newest radio. tomtom 6.01.
i can surf the internet, does that mean i have data? or will i still need to reset dmu/akey? what's akey?
I can get a gps signal at all. using astro luancher.
Click to expand...
Click to collapse
If you can surf in IE, you have data...
If you can make/rcv calls & texts, you have voice...
My experience is you can have voice and no data, or both, or none...
Two things:
Seems that you're saying you flashed the ROM, then loaded olipro 2.4-- should be other way around (of course after flashing radio on olipro 1.2)
Also, for DCD, you need to run the carrier cab after flashing the ROM. So if you didn't do that, that would account for the data problem.
ebb said:
Two things:
Seems that you're saying you flashed the ROM, then loaded olipro 2.4-- should be other way around (of course after flashing radio on olipro 1.2)
Click to expand...
Click to collapse
no, he did it right. the new radio roms will flash from RUU under olipro-1.2, but not under olipro-2.4. his order allowed him to flash the radio with RUU.
Also, for DCD, you need to run the carrier cab after flashing the ROM. So if you didn't do that, that would account for the data problem.
Click to expand...
Click to collapse
correct, there is no data connection configured without the .cab, unless you manually configure it under connections.
as for gps, we have been testing lately. it is totally possible that your gps refuses to work. it is very unlikely that the gps hardware is defective or bad in any way. there are low level radio parameters that are set differently on different carriers - some xv6800's are set in some way that screws up GPS. thats about all i can tell you right now. there is not a reasonable solution currently for VZ. some people are lucky and some are not, which may suggest that some XV6800's came provisioned differently. we are not sure yet...
i think that there are 2 differences between my device and yours:
a) my radio has sprint aGPS server info set.
b) my radio has some other provisioning flag set differently
we cannot do anything about A until a vz agps server is identified. we are working on identifying B.
without A or B, your GPS can work, but i've heard of it taking hours to pick up initially. try quickgps and clear line of sight to clear sky..
there seem to be some VZ users who somehow picked up "B" and the setting stuck. we cant confirm or reproduce this yet but it seems likely.
i'm not going to give any more details right now because people will start doing stuff to their phones to create themselves problems...
I use BAFS GPS launcher with verizon to get GPS working. I just turn it on for a couple of minutes, and then get a good, quick satellite fix with googlemaps or Live Search. You can find it in the GPS sticky topic at the top of the forum.
I thought I did agree in my earlier post about using 1.20 for the radio flash (that's how I do it), I just thought he had kept it at 1.20 for the ROM flash, then loaded 2.40, then flashed again. Maybe I read his first post wrong.
ebb said:
I use BAFS GPS launcher with verizon to get GPS working. I just turn it on for a couple of minutes, and then get a good, quick satellite fix with googlemaps or Live Search. You can find it in the GPS sticky topic at the top of the forum.
I thought I did agree in my earlier post about using 1.20 for the radio flash (that's how I do it), I just thought he had kept it at 1.20 for the ROM flash, then loaded 2.40, then flashed again. Maybe I read his first post wrong.
Click to expand...
Click to collapse
sorry, i misread your post earlier. i think we are all agreeing.
ebb if you start visualgpsce without doing anything else after a bootup, how long does it take you to lock? you shouldnt need to activate the port, vgpsce will do it.
Phone #1 has to go back in the next 48 hours or so, but I have phone #2 available to me probably `til Thurs or so...
Let me know if you want me to test anything with it...
I can get it activated in it's current state (olipro-2.40, radio 3.39.10, DCD 3.1.2)
dcd1182 said:
.....
ebb if you start visualgpsce without doing anything else after a bootup, how long does it take you to lock? you shouldnt need to activate the port, vgpsce will do it.
Click to expand...
Click to collapse
I'll d/l it and try and post back.
NetworkPIMP said:
Phone #1 has to go back in the next 48 hours or so, but I have phone #2 available to me probably `til Thurs or so...
Let me know if you want me to test anything with it...
I can get it activated in it's current state (olipro-2.40, radio 3.39.10, DCD 3.1.2)
Click to expand...
Click to collapse
But did you or did you not load the verizon carrier cab after the ROM?
ebb said:
But did you or did you not load the verizon carrier cab after the ROM?
Click to expand...
Click to collapse
I did.
After installing carrier .cab:
On Phone #1, after a hard-reset with DCD3.1.2 still on there, *228 (option 1, then option 2 later) gets me voice/txt, but no data - will need DMUreset/Akey. I'm confident I can get that part working with some more time/effort.
On Phone #2 (which is the replacement sent for Phone #1), *228 (option 1) gets me a referral to customer service, not suprisingly.
I fully expect this to reverse once I activate #2 in place of #1.
What I'm gathering from DCD's reply is that both phones are probably fine, physically. Regardless, I need to get #1 back to VZW before they ding me another stack of cash I don't have
That said, I'll have #2 a bit longer before I'm committed locked in (i.e. the grace period on returning it us up).
1. I just think then that going to a 3.xx.xx radio wiped your Akey out, and you need to call and get it re-provisioned. Just tell the tech you had to hard reset from a software conflict, and they'll do it.
2. DCD, I had to restart visualgpsce a couple of times to work at all- on the third try, it asked me what comm port, and after setting it at comm port 4, I get immediate lock (like as soon as I click "accept" on the first screen).
ebb said:
2. DCD, I had to restart visualgpsce a couple of times to work at all- on the third try, it asked me what comm port, and after setting it at comm port 4, I get immediate lock (like as soon as I click "accept" on the first screen).
Click to expand...
Click to collapse
OK, so... to date, I haven't gotten to activating phone #2... BUT...
I took it outside (my Mogul works fine inside here, but OK, I'll play along ) and fired up VisualGPSce... It took a while (I sat around for about 15 minutes) and it eventually worked it's way up to seeing 10 birds and using 6 - but NEVER locked on... and it wasn't very reliable... went up and down between seeing 10 and 0, and never "used" more than 6. Again, it never got a "fix"
(Yes, I also installed QuickGPS and updated it using ActiveSync connection.)
As I've said, carrier .cab is installed, tho the device is not activated so there's no data/voice service.
Inside (again, where my Mogul works just fine), the thing is useless for GPS...
Not sure if that helps, but there it is.
dont knwo if this is related but you messed up when using spl-1.20-olipro. the dcd thread cleary states "Hard-SPL 2.40-olipro is REQUIRED.
A device with SPL 1.20-olipro will constantly reboot with this rom!"
newone757 said:
dont knwo if this is related but you messed up when using spl-1.20-olipro. the dcd thread cleary states "Hard-SPL 2.40-olipro is REQUIRED.
A device with SPL 1.20-olipro will constantly reboot with this rom!"
Click to expand...
Click to collapse
Thx - this was addressed above... I am, in fact, running olipro 2.40... I used olipro 1.20 to get the radio rom on, then subsequently upgraded.
NetworkPIMP said:
Thx - this was addressed above... I am, in fact, running olipro 2.40... I used olipro 1.20 to get the radio rom on, then subsequently upgraded.
Click to expand...
Click to collapse
check your pm's please, there are a few things i can walk you thru trying.
dcd1182 said:
check your pm's please, there are a few things i can walk you thru trying.
Click to expand...
Click to collapse
if there are some "suggestions" if you'd let me know some because i used the 3.49 radio and i felt like i took a step backwards as far as GPS. it would show 10 sats but would never lock no matter what i tried via info in the threads.
however i'm back to 3.35 and happy as can be!
it picks up and locks within 30 seconds
coffey_joshua said:
if there are some "suggestions" if you'd let me know some because i used the 3.49 radio and i felt like i took a step backwards as far as GPS. it would show 10 sats but would never lock no matter what i tried via info in the threads.
however i'm back to 3.35 and happy as can be!
it picks up and locks within 30 seconds
Click to expand...
Click to collapse
maybe you are onto something for users on vz (who have no agps info and possibly missing another parameter)
i have not paid close enough attention to the reports to tally up votes. can the difference in lock time be consistently reproduced?
Ever since the VZW Update released my GPS no longer works, (didn't Update my phone)
I used to get locks right away (8-10 satellites) when I was outside now I get ZERO.
I use GPS today and Google maps.
anyone have any explanation why it would suddendly stop working?
Running DCD 3.2.5 and 3.42.50
sorry man I have no idea. my device still gets locks but I always have to toggle location on settings. (go in and turn it to 911 only say ok till I am back to the main screen then go abck and turn it on and say ok till I am back at the main screen again) then soft reset. it takes me a while now to gets locks but I do get them (no2chem5066 with radio 3.42.50)
evanbriggs1 said:
Ever since the VZW Update released my GPS no longer works, (didn't Update my phone)
I used to get locks right away (8-10 satellites) when I was outside now I get ZERO.
I use GPS today and Google maps.
anyone have any explanation why it would suddendly stop working?
Running DCD 3.2.5 and 3.42.50
Click to expand...
Click to collapse
have you updated your phone via *228? llboredll spoke about how me might of found some issues when programing his phone after verizon released the software update.
I had some serous issues trying to get a fix yesterday but just now I walked out my basement and got 7 sats and lock within 15 secs or better. So I will have to chalk it up to some weird anomaly yesterday.
guys thanks for the quick response, ya il try resting my "location" setting and yes i did do a *228' 2 ealyer today trying to fix the issue, it didn't change my PRI.
ya the location reset didnt work im still dead
evanbriggs1 said:
ya the location reset didnt work im still dead
Click to expand...
Click to collapse
Try a GPS program that displays the NMEA messages like GeoScout. If you don't see any then your GPS is not turning on. So either flash the ROMs again or you have a back GPS possible.
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
scrawnyb said:
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
Click to expand...
Click to collapse
But he said in his original post that he didn't flash the VZW update.
scrawnyb said:
I wish you guys would read the damn forums.
The OFFICIAL VZW update kills GPS for anything but VZW Navigator, got it?
Click to expand...
Click to collapse
Read the first post, he didn't (repeat) didn't update his phone. His theory is that Verizon did something to the network to work only with the update such that us on Custom ROMs it will not work. Obviously that is not the case but that is what he was asking or theorizing about.
I think we all have read the forums on it and are tired of people updating their phones and then complaining on this forum that it screwed up their phone. I can only say "Do your homework before flashing anything" otherwise don't whine about what you have now.
so you think it may be more along the lines of software??
give me your top 3 pics and ill try them all out.
Thanks a lot, and yes I was theorizing it was a network issue not my phone its self. seeing if anyone else may have had a issue recently with it.
Fixed it, uninstalled GPS Today
Installed GPS Toggle, and got locks 30 secs after i turned it on, thanks for leading me in the right direction!
I even get locks in my Room witch did not happen before. so defiantly awesome!
Recently my phone has been suspending the screen and not bringing it back when I press the power button. I was running 3.2.6 before, reverted to 3.2.3. Tried hard-resets, taken out the battery, tried running with just the rom and nothing else installed after flashing, still doesn't work.. I've also tried taking out my memory card and running without that.
The power button still works because it will still turn the phone on, and bring the phone out of sleep sometimes, but if it doesn't work on bringing it out of sleep it seems that I have to soft-reset or the phone just doesn't work...
Any suggestions? Also.. I this is a bell phone, they have stock roms available on their site, but am I able to get the stock bootloader back on in case I have to warranty this thing?
You've tried most things that people could suggest, however have you tried a different ROM?
I know this used to be a very common problem when the Tilt came out, but once everybody started changing ROMs, it slowly disappeared.
My suggestion in short: Try relocking the bootloader
My Two Cents:
This is actually the most evil bug ever for this phone. I got this bug on my Sprint Mogul and couldn't get rid of it. Some people say it's because Java is running and then causes the phone to hang, but I never found that to be the issue. I got a Verizon XV6800 and experienced this problem only when I was flashing from stock to dcd 3.2.6. It occurred after I unlocked the bootloader, but after I flashed to dcd it went away. It was between having the stock and dcd roms that I found that most people experienced this problem when the loaded they new bootloader.
If I had to guess, based on my knowledge of operating systems, that some process is taking up a lot of resources, mostly CPU time, and is not allowing the phone to come out of standby. I guess this because sometimes I have had this happen and the screen would come on after a LONG delay.