Ever since 3.04 up to 3.12 using DCD's code when I answer calls there is absolutely no sound until I reset my phone. Users at the other end say the phone just goes to a busy signal.
I looked for 2 weeks to find the answer but got nothing. Today I had to reset 5 times. I need help, fast!
Thanks to all.
Have you tried reflashing again? Try a clean rom and see if it still happens.
The phone was brand new when I flashed it. I had it replaced and the original phone did the same thing. Any suggestions on which rom to run with? I find since radio 3.39 it is worse.
I currently use 3.39 radio and 3.1.2 rom with no issues...What radio are you using now?
Originally I was using Sprint 3.35 and 3.04; phone wouldn't answer once every 2 or 3 days. Then I up'd to 3.12 and phone wouldn't answer once a day. I got fed up and convinced my supplier to switch my phone with a new one because some buttons weren't working. With the brand new one (wasn't referbushed according to EPST) I did a strait Oli2.4, then 3.39 radio, then 3.12 of DCD's rom. Now I'm getting 2 to 3 times a day. Today was the worst with 5 before lunch.
Try flashing back to 3.35 radio and reflashing DCD rom and see if that helps any... Actually reflash the rom...not just hardresetting
We think alike. As i was writing the first port I started the Sprint flash process. I will leave it there for a few days to see what happens then try 3.04.
What have you added to the rom? List both OEM's and cabs. Also, did you cook a rom with the kitchen or are you using the precooked rom?
Whos your carrier?
2 answer both questions, my carrier is Telus, and I've always used the Telus based rom from DCD. I've also gone days without any modifications. The only thing that gets installed after re-flashing from scratch is my email config.
Did you install the Telus carrier cab after installing the 3.1.2 Telus Rom?
Yes I did.
Did you program with *22803?
No I did not. What are the steps to complete this and what does this step do?
Also to update, I have been running with the Sprint 3.35 rom and no dropped sounds in the call, but I did notice that every now and then when a call was coming in my phone would vibrate but wouldn't ring. I'm starting to think maybe the mp3 sound as my ringer may be at fault here. Either way I will wait the results of tomorrow's test to see what happens.
I also had a problem like this before, and it only happens when receiving calls. Then after a few weeks it just stopped happening. So I assumed it to be a network problem.
Another update. I had a "no sound" call today and had to reboot. So even with the Sprint 3.35 it happens. My next step will be to remove my mp3 file that I use as a ringer.
Also, does anyone have that procedure to #22803 your phone?
Also, does anyone have that procedure to #22803 your phone?
Click to expand...
Click to collapse
Just call it and follow the prompts.
-Hard resetted
-Flashed with 3.04 of DCD version Telus (already had oli 2.4 and sprint's 3.35 radio)
-Didn't let customizations run
-Ran the *22803 procedure
Ran a full day with many, many calls and no issues yet. Will update again tomorrow.
Here's hoping!
P.S. Congrats to DCD and his wings.
There a reason you're not using 3.1.2?
I found a better battery performance with 3.04 and i use my alot.
Related
Relatively quiet member here, flame away if you like but I was not able to find the answer by searching the forum.
I’m running ROM 2.06.502.3 and have been having some problems with the radio. I’m using the radio ROM that was bundled with it (1.34.00.10) but nearly every day I have a number of problems occur. The OS is stable and no crashes or bugs that I have noticed but periodically the phone (8525) will stop receiving calls but still show full connectivity. I can make outgoing calls fine but incoming ring to voicemail. When I send texts I get no indication that they failed or no connectivity is present but once I realize my phone is having this problem I soft reset and all the texts go out at once and all the ones Ive been missing come in. Additionally several times when I have dialed out, finished calling and the phone will not hang up. The unit does not freeze - all OS functionally still present - but I can not end the call and the call timer keeps going until I soft reset even if other party disconnects.
Is this a problems with the rom, my hardware, or the combination of ROM and radio version? Any other radio version that is more stable with this ROM? Thank you in advance to everyone here. Even though I don’t post much I read quite a bit and appreciate what everyone contributing to the community does for all of us.
Anyone? I think Im going to flash with the .35 radio , although I would assume the .34 was included with the ROM because it was most stable with it. Please correct me if Im wrong. Thanks.
I've had similar things happen a while ago with my old Typhoon; it was some kind of issue with Cingular. Can you go to some other area (that uses a different tower for sure) and verify that this still happens? Or maybe just hard-reset and don't install anything for a while. I just don't think the 1.34 radio was reported to be this bad.
I had a similar issue with the 1.27 radio (can't end calls). I haven't seen this since I went to the 1.35 radio. The fact that you get them with the 1.34 radio is surprising to me however b/c I was under the impression that there were very few differences between the two.
hi there, i recently upgraded my rom from the orginal orange one, as my phone was playing up. it was always not wanting to wake up from going in to standby without doing a soft reset. so then i upgraded to the WM6 vinilla rom, the same thing happened then but it was alot worse, then upgraded to the 0.21 rom. and im still getting the problem, without having any new programs installed its still doing it, so im not to sure whats the cause?
heres some info about it. Im in the UK with the network Orange too.
Thanks.
Radio Version: 1.06.00.00
Protocol Version: 32.37.7010.01W
ROM Verion : 3.22.110.1
Hi,
I have also recently upgraded from the original Orange rom etc to XDA Live 0.2.1. I also had occasional (only occassional) failure to wake up issues.
Since upgrading I have not had this, and the ROM is much faster and seems more stable. Today I upgraded my radio to 1.27 as well, but too early to comment on that.
I also use Phone Alarm, SPB Time, SPB Weather, and Pocket Plus. I had an issue with PA not changng profiles automatically but reverted to an slightly earlier version and touch wood it seems to have resolved it.
Can't really advise much theefore, but maybe the fact mine works (so far) could rule out a few things.
its really annoying, i would of thought that flashing a new rom it would be fine. but its still playing up, alot worse, i have to soft rest the phone everytime i want to make a phone call or to check i have a text. cant stand much longer of this. where can i get that radio rom from?
just flashed it with xda live 0.10 this time see if thats any better.
still no luck, fronzen about 4 times since i last posted. just wont wake from sleep, even if i set it to stay on without the backlight it will still freeze, im testing without a sim card in atm to see if that makes a difference,
anyone what can be causing this?
thanks.
@bomber456
Your Problem With The Calls In WMXL Is That If You've Upgraded Straight From The Orange ROM Then You Have An Old Radio Installed. Upgrade You Radio After Installing The WMXL OS And That Should Help Iron Out Your Calling Problems.
Cheers
Are you using a micro sd card?
If so, try starting from scratch WITHOUT putting the card anywhere near the phone. (ie don't use the card at all until you can prove it has nothing to do with it.)
Just a thought. I am sure some cards caused problems. (although I am using one (sandisk).
EDIT: Just seen Mousey's post - definitely a good idea, although I had the same radio as you using WM6 till I upgraded the radio today, with no problems.
where can i get a good radio for the orange network in the uk?
also i tried it without putting the sd card in and it was still the same. one thing i tried was not to put the sim card in and it was much better, dont think it crashed atall, so its down to the phone side of it.
thanks.
oh another thing, when flashing the rom it said it would take 20 mins, it only took about 5-7 mins maybe less :S is that a problem?
No. The XDA Live install is quicker than a normal rom.
"where can i get a good radio for the orange network in the uk?"
I am using 1.27 - check the wiki for radio only upgrades - same process as upgrading rom to XDA live but with a different file.
I understand that 1.34 or 1.35 are supposed to be OK, but anything from 1.27 should be OK - I have been using 1.27 today with no issues yet, but still early.
I am struggling to find any notes etc to specify the differences or specific advantages of the different radios.
Try one and see - DOESN'T NEED A HARD RESET.
installed 1.34 and its worse. losing signal etc. but im still getting crashes. i dont know what the hell is the fault. its so unstable its unbelieveable.
update : the phone doesnt crash or freeze or anything, if there is no sim card in the device. but it will crash when there is one in, i think its due to switching from 3g to gsm. also ive notcied that sometimes when i boot the phone where its supposed to display the radio and protocol info, it says no GSM!
ive now installed radio 1.27
would any software beable to still be in my phone after a rom upgrade?
any help would be great.
Perhaps try with a different SIM? may be a dodgy SIM...
seemed to work fine with my gfs orange pay as you go sim. but crashed once in a few hours. ive now unlocked my phone and CID unlocked it, and it hasnt crashed once. i think the boot number has cahnged from 04 to 06 too, seems to be stable now, (hopefully)
I installed the dcd 2.1.0 verizon rom with the v3.27.0 radio (following these instructions:
http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/)
and everything went fine but now my device is freezing up and generally not acting healthy. Can anyone vouch for this set up and/or recommend the best current rom for verizon? Im not too concerned with having GPS available (but would be nice), I would really like to have a nice no junk rom above all else. Thanks for any advice.
I haven't had good luck with any of the gps/reva roms on verizon... Seems every rom combination has it's share of quirks/bugs it's just a matter of finding the one that has some u can live with
I'm yet to find one that is FLAWLESS... if you find one let me know!
I have flashed several VZW xv6800s. If you have the 3.35 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Edit: sorry guys, was not thinking as i typed. I meant 3.35 radio (the one from the sprint update). Flash the 3.35 or 3.37 radio!
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
mdjkim said:
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
Click to expand...
Click to collapse
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
This is VERY bad advice and will only screw your phone up even more. It says in numerous places on these boards that 3.27 radio is NOT compatible with 3.x.x roms. The only roms that will work with the 3.27 radio are the 2.x.x roms.
My question to you though is why on god's green earth are you still wanting to run a 2.x.x rom with the old crappy buggy beta radio 3.27? Just update with the alltel updater to get radio 3.37.20, don't let customizations run, then flash dcd 3.0.4...much much better and will probably fix your gps problems.
corey113888 said:
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
Danger!
radio 3.27 is NOT compatible with dcd 3.0.4 rom!!!
1) radio 1.30 or radio 1.40 = use dcd 1.7 (non gps rom)
2) radio 3.27 radio = use ONLY dcd 2.x.x series roms (with gps , revA - experimental)
3) radio 3.37 radio = use dcd 3.0.1 or 3.0.4. (gps and revA official)
my recommendation would be option 1 or 3. Depending on whether you want gps or not.
Zenoran said:
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
Click to expand...
Click to collapse
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
maccaberry said:
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
Click to expand...
Click to collapse
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Edited my original post...
Also, i have had 2 replacement xv6800s. One was for white spot in the bottom left part of the screen. I had to call VZW and tell them they were out of replacements at the store. The other was replaced a week later for data not working.
Zenoran said:
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Good luck
maccaberry said:
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Click to expand...
Click to collapse
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Zenoran said:
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Click to expand...
Click to collapse
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
maccaberry said:
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
Click to expand...
Click to collapse
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
gcincotta said:
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Click to expand...
Click to collapse
gc, this is so true. The 'techs' at the verizon stores (bless their hearts) know nothing at all about the titan. you could go in there with a fully "sprintized' titan and seriously they wouldn't notice.
I found this out the first time I tried to flash. I thought I had bricked the device and took it to the "service center" verizon store near my location to get the data back working (yeah that's all the problem was, but I was a noob and didnt know better). They didnt have the slightest idea what to do to solve the problem. They screwed around with it for a while and gave it back, basically the same. they offered to switch it out for me, but I said i will try just a bit longer (and it had a customized 'colonel - ppcgeeks' rom on it - if you have ever seen one it is completely unmistakable - looks nothing like a verizon rom).
I went outside, called *8899 and got a service support tech to fix the phone over the air. The problem had just been the data account needed to be reset at their end. Not only did the guys in the store have no idea how to fix it, they didnt even notice that my device was clearly not stock.
Zenoran said:
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
Click to expand...
Click to collapse
Yeah, if you do the flashes separately the boot screen never change. I still had the original verizon boot screens until just recently when I did the upgrade to dcd 3.0.4. Its the running of the sprint installer that overwrites your verizon splash, not the rom or the radio themselves.
Anyway, i used the dcd kitchen to create my 3.0.4 rom and selected HTC animation. That creates a HTC splash to overwrite the sprint stuff, and then I did this and this and my machine looks sweet when it boots.
The instructions of how to load them is explained in the thread http://forum.xda-developers.com/showthread.php?t=379822
Enjoy. (I cant post pics of the screens because the xda database is busted at the moment)
I flashed my Verizon XV6800 to DCD 3.1.2 Radio 3.39..
I have always had 1 bar at home and barely one bar at my office. with my last 3 phones reception was identical. I'd drop maybe every 10th - 15th call at home and every 5th - 10th call at my office. This was no big deal, I'd call back and finish. Text messages / MMS incoming calls were always reliable. (Rarely an incoming call would just go to voicemail and not ring)
SO..
I flashed my 6800.. Everything works great everywhere except the office. I can’t receive Text messages.. Maybe every hour or so, 30 Texts will flood in at once. (I get a lot of text messages from server monitoring software.) My Phone will not ring any longer(only at the office). All incoming calls go to voicemail. I assume that since the Office had poor reception.. losing just a bit of signal would knock me out completely.
Anyway.. GPS doesn’t help if I can’t get calls where I need them the most, so I flashed back to stock... and I STILL have this issue. My phone no longer works at my office.
I have ruled out coincidental tower issues in the area.. my co-worker has the same phone with untouched stock software.
In debug, our signals are identical. All other version numbers and settings are identical. His phone works fine. When sending a Text through vtext.com to both phones, his gets the message immediately, my phone will receive it after an hour or longer.. sometimes 3 or 4 hours later. Outgoing calls drop after 30 seconds.. the phone is now unusable at the office.
Other than swapping out the phone... can anyone tell me if there are any settings i can compare or check on? Perhaps the reflash back to stock kept some settings or something? I know there are tweaks like setting how often your phone polls the tower for a call etc... Things like this could have an effect maybe?
Anyway.. After 2 days of searching and playing with settings.. I figured I was better off with 3.1.2 / 3.39 since the phone dont work anymore at the office anyway. so now I'm back to that.
should I try 3.35 or 3.37 Radio??
Any advice would be much appreciated.
Did you install the Verizon Carrier cab?
Yes on the 3.1.2 firmware.
Obviously not when I flashed back to the stock because it doesn't need it.... right?
Also.. I used a PPCGeeks Thread for the Flashing back to stock. (Maybe this helps)
http://forum.ppcgeeks.com/showthread.php?t=21161
Yes on the 3.1.2 firmware.
Obviously not when I flashed back to the stock because it doesn't need it.... right?
Click to expand...
Click to collapse
Right. Have you tried OTA programming?
Yeah, Each time I've flashed.. I first run the OTA both option 1 and 2. then I usually need to call VZW for my AKey, or to reset the data Services because they do not work.. they have been cool each time though
I haven’t actually tried OTA FROM the office... because i cant hold a call long enough to have it complete. I'm not sure if the location matters though.
I can certainly get the phone swapped, but the first thing i'll wanna do with the new one is try DCD 3.1.2.. Unless there is a recommendation on a different Rom / Radio?
I've read a good many of your posts on other threads and you seem to be good at this stuff... so I'm willing to try whatever you recommend.
Also I seriously appreciate your time.
Go into Device Information in Settings and list me your PRL Version and PRI Version.
gc14 said:
Go into Device Information in Settings and list me your PRL Version and PRI Version.
Click to expand...
Click to collapse
PRL 51056
PRI 1.35_002
Ok try rolling back to the 51020 PRL.
Download the attached file, unzip the PRL, and copy it to your phone.
Dial ##775 send.
Enter 000000 for unlock code.
Tap the box underneath Setting to highlight it, then click Menu->Edit.
Browse to where you put the prl file (51020.prl), and open it, then click OK.
Click Menu->Ok to update it and let the device reset.
See if this helps your issues.
I get Turn on LPM failed.
Maybe I should not try it from the storage card... let me try again.
** Update: It did update the PRL when i moved it off the SD Card.
However I sent 3 text messages and called the phone twice from my desk.. No change.
x51 said:
I get Turn on LPM failed.
Maybe I should not try it from the storage card... let me try again.
** Update: It did update the PRL when i moved it off the SD Card.
However I sent 3 text messages and called the phone twice from my desk.. No change.
Click to expand...
Click to collapse
did you recently get an aluminum or metal case?
also, what is your slot cycle index under modem settings in EPST?
Actually I have a custom case I made myself out of Lead.. it gives the phone a nice weight.. LOL.. No... No cases or anything.. However.. I know this should be irrelevant but..
I went on vacation for a week and got an extended battery the day I was leaving. The day I got back I flashed my phone FROM stock.
Had my issues at the office..
Flashed Back...
Still had issues...
Decided that.. MAYBE the extended battery being thicker and all is blocking signal... Swapped back to normal battery.. No good.
Went back to DCD312
Slot Cycle was 2... I just now changed it to 1 and it makes no difference.
did you happen to flash the stock RADIO with the stock ROM? flashing back the stock radio would most likely screw your device, but ive flashed the stock ROM several times with no problems.
try flashing to the current radio 3.39. heres just the radio, without the Sprint ROM. Radio 3.39
it can be tricky flashing it without a non-SDHC card. PM me if you dont have one.
after that, just flash a compatible ROM and it should fix everything.
Well the whole procedure was this:
1) Stock phone
2) Run unlocker
3) Flash 3.1.2 rom
4) Device locks at boot
5) Flash 3.39 Radio from SD Card
5a) Ran VZW Provider Cab.. from DCDs 3.1.2 page.
6) Had the reception issues mentioned.
7) Run Titan Relocker
8) Flash Stock VZW Rom that includes original Radio Version.
9) Reception Issues remain. (Lived with it for 2 days)
10) Repeat steps 1-5a above.
so I'm on 3.1.2 / 3.39 again right now.
I CAN flash the radio again... I guess... i already have it on a 512 SD card ready to flash.
Outside of DCD 3.1.2 What would you say is the most recommended / stable Rom / Radio Combo?
x51 said:
1) Stock phone
2) Run unlocker
3) Flash 3.1.2 rom
4) Device locks at boot
5) Flash 3.39 Radio from SD Card
5a) Ran VZW Provider Cab.. from DCDs 3.1.2 page.
Click to expand...
Click to collapse
you need to flash the radio before you flash the ROM
aguas said:
you need to flash the radio before you flash the ROM
Click to expand...
Click to collapse
Yeah I read that somewhere.. but the instructions I followed had me flash the rom, wait for the device to lock up on the verizon screen... then use PWR+CAM+RESET and flash the radio.
Even if it were in the wrong order, wouldnt flashing back to the VZW Stock Rom that includes the original stock radio still work as it did previously?
(maybe the answer is obviously not?.. Perhaps I sould reflash everything in a different order?)
So I flashed back to Stock again last night. Had to call and have data services and AKey reset... as usual.
I'm at the office now, and so far I had several people send me test SMS and only one of them took a while to show up. The others came in pretty fast.
Here are the differences between this time, and the last time I flashed back to stock.
1) I DID NOT install any applications at this point... I have ONLY Configured my Exchange Activesync Email.
2) I do not have the extended battery installed.
3) I reset before the verizon custom cabs installed from the stock ROM.
It's only been 10 minutes, but so far it looks promising... I'll update if that changes.
**UPDATE
Still can not hold a call... Text messages are now taking 10 - 20 minutes to arrive. My co-worker with the same phone still has no issues. Will stop by Verizon after work to have it swapped.
Stopped at Verizon.. Explained that the phone worked most places but just not at my office.. Explained that my co-worker has the same phone and does not have issues.
I expected to get a lot of crap.. but they were cool. They tested the phone, and claimed there was an issue. They didn't have any in stock, and have to mail me a new one.
SO... I havent seen many people complain about reception issues with thier radio upgrades... I'm wondering, should I upgrade the Roms and radio on the new one? Should I assume my reception issue was hardware and not caused by the software?
I'm still hoping someone with a lot of Rom experience can provide me with some recommendations.. I hear GPS Locks are flaky on DCD3.1.2..
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
nylaw said:
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
Click to expand...
Click to collapse
My first guess, assuming you turned the GPS on, is that you did have the MR 1 update.
You may as well try reverting back to stock winMo6.0 then back up to 6.1 via the standard method.
Secondly you could flash stock MR1 update then install valhalla GPS server cab.
What PRI do you have. If its 2.xx then you prolly did have MR1.
How did you unlock and what ROM/radio etc did you use?
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
nylaw said:
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
Click to expand...
Click to collapse
Thanks for the info on the splash screen. Did not think of asking that. If you have the standard VZW splash screens then you didint update correctly wiht the sprint ROM and not knowing where the ROM was before you started I would hazzard a guess and say you were on MR1. If you were not on MR1 then you hosed something during the sequence of flashing but that usually leads to a phone that sticks booting... I would try this before I revert back.....
Keep phone unlocked, flash sprint firmware and be careful not to let the customizations run, apply aGPS fix for VZW, test. If it fails then I can certainly say you were on MR1 and must revert back to stock. There may be another way of doing it but I honestly think starting fresh is always best.
Good news to report. I couldn't sleep last night as this was really bothering me. I went back to the stock radio and rom then flashed the radio and rom back to 3.42.50 and DCD's 3.4.4. All is working now but I still have the Verizon splash screen. I would have to say this must have shipped with the MR1 update. There was one value in the regisrty that I missed with the agps settings but that shouldn't have had any effect on the GPS from just the sats.
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
nylaw said:
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
Click to expand...
Click to collapse
That PRI is a bastard to get of. I found the best way to get rid of it is to kitchen a ROM, and then add in the Extended ROM from the stock VZW rom (non-GPS) and it was able to finally get rid of the PRI.
If you are still having issues with that PRI, let me know, I might be able to supply my PRI killer ROM if I still have it around.
Thanks but I am all set. Everything is working fine. I believe the guru's feel the 2.xx PRI is the one to have, just not the rest of the update.