**SOLVED!!** Any 3.27 Radio-based ROM & signal reception issues

[sandiegodude]

hey everyone, maybe I have a bogus phone, but I've tried multiple roms based on the 3.27 antenna, DCD's WM6 & WM6.1 versions.

Each time, after the flash (both radio and rom) it takes me over 5 minutes to get a signal (RT or EVDO). After it gets a cell signal, everything works fine including GPS. But after each soft reset, it takes me 5 minutes to get a phone signal again.

I thought it was the ROM, but after trying it with multiple versions, I am at a loss.

Any ideas?
FWIW MSL/MDN/MSID codes are intact and correct. Signal area is consistently 4 bars. Phone functions fine after getting a signal.

**SOLUTION**

1. Have MSL code ready
2. From phone app, type ##PST#
3. Click EDIT
4. Type in MSL code
5. Click VIEW INFO in bottom left corner
6. Click M.IP SETTINGS
7. Change value of MIP REGISTRATION RETRY to 1000 ms
8. Change value of MIP MODE to MOBILE IP PREFERRED****
9. Click MENU in bottom right corner
10. Click OK
11. Soft reset device

**** note, I had to adjust MIP MODE 3 times before I got it to work.

Thanks everyone!!
especially limezednem!!
:D:);)

[meccanoble]

no issues so far. My phone boots up super quick now since i did this wm 6.1 and radio update. Feels kind of naked but love the speed. It has frozen on me on multiple occassions when trying to uninstall certain programs but as far as phone connectivity, i have had no issues since i got it working. Connects right away.

[pdavis466]

I had the same issue. I flashed back to the original ROM and it signal was acquired in a flash. I have since swapped the phone from Verizon, but I am reluctant to re-flash, though I REALLY want the GPS functionality... please some one come up with a cure for this slow signal malady!

[pdavis466]

anyon else had this issue?

[x10dude]

anyon else had this issue?

I originally had problems with the dreaded Error 67 with the new ROMs (tried everything). I went back to the stock Sprint ROM and it disappeared.

On a whim I tried the upgraded ROM again (glutton for punishment). After it rebooted I couldn't get a phone signal... I went into Connections and turned off the phone and waited a minute and then turned it on again. Got a signal in less than 10 seconds. (Error 67 are gone too... go figure!)

Try that.

[2kmy477]

I'm w/Sprint and had the same issue with radio ROM 3.27,it took about 2 minutes to get cell signal after soft reset,then the data connection got disconnected every single,i was so frustrated since i did a lot of internet radio streaming and IMing.I flashed it back to 2.17,all is working fine with the old ROM,I think i can live w/o build in GPS for now.

[sovrce]

You might have already tried this, but if not, try flashing to DCD's 2.1.0 ROM with the 3.27 Radio. This is the one and only ROM I've ever flashed to and probably ever will flash to unless some godlike official update is released. I stuck with this because I feel it's *easily* the most stable, has fully working BT AND has GPS & Rev A enabled (network permitting).

If you haven't already, try 2.1.0.

[aXiMus]

hey everyone, maybe I have a bogus phone, but I've tried multiple roms based on the 3.27 antenna, DCD's WM6 & WM6.1 versions.

Each time, after the flash (both radio and rom) it takes me over 5 minutes to get a signal (RT or EVDO). After it gets a cell signal, everything works fine including GPS. But after each soft reset, it takes me 5 minutes to get a phone signal again.

I thought it was the ROM, but after trying it with multiple versions, I am at a loss.

Any ideas?
FWIW MSL/MDN/MSID codes are intact and correct. Signal area is consistently 4 bars. Phone functions fine after getting a signal.

Try programming your phone OTA, and updating your PRL.
*22803 for telus, *228 for some other carriers. Not sure what you have, but that could be your issue.

[limezednem]

Mine did this at first, I dont know what I did to change it but it went away. Problem is, when I updated my prl to 60711 or whatever the new one is, the problem came back. I reset on my way to work and it didnt get a signal until well after I parked (15 min drive) but for some reason sitting at home it would get the signal within 2 minutes. For me it hasn't been that big of an issue since I only soft reset once a week or so. But I am scared that this will occur in a time of need. Glad to hear there are others out there who share my problem.

[Willybeen]

SAME THING HAPPENED TO ME.. i made a thread about this too....

did you get it resolved?... its really frustrating.. i flashed it flawlessly to my room mates phone... then failed on mine.. figured it was my phones fault.. got a new one... and SAME thing on the brand new phone... where am i going wrong?

all ID numbers were correct... esn, mdn, msid. etc etc.


help me please

[Willybeen]

same EXACT Thing happened to me.. with 2 phones.. however, I flashed my room mates phone flawlessly and is still working without an issue...

double post... damn computer

[sandiegodude]

no luck. :(
sticking with 2.17 for now.

[dieseldennis]

i have SORT OF the same prob............ i get signal right away but it fades in and out from evo to 1x and back ...... sometimes it can take me a half hour to finally connect a phone call because of it.

any ideas?

[Willybeen]

bump because i really would like to know why this is happening to a few select people..

maybe ill just wait for sprint to release the official rom/radio... and go from there

I went back to 1.4 radio and custels 1.1 rom, now my internet isnt working....
go figure

[sandiegodude]

i have a feling it might have to do with prl's.

[Dc_striker]

try ##786# reset it and then load latest prl i hope this work

[Shiva1]

I have the latest PRL, still no luck.

[c@rL0$]

I have Verizon and just dial *228 and when prompted press #2 and it updates my roaming capabilities (PRL) all over the air with out having to look for PRL's over the net and manually updating them.


I don't know if Sprint has this feature but if it does try it out.

Ohh yeah i was playing with the registry and found a way to make your signal stronger ( I think ) I don't know if it realy does work but it give me higher bars;)

go to

HKLM -- System -- State -- Phone

There are two strings.

One is Signal Strength and Signal Strength Raw.

I change the value to 100 on both and get full bars. I dont know if it does give a real effect.

But after a little while it goes back to the original signal value:(

[Dc_striker]

I have the latest PRL, still no luck.

diid You do ##786# and reset phone ?

[biggjimmy7]

I have the sprint 7800 with 6.1 mobile and I am having an issue with my reception as well with this radio. When I make / receive phone calls I get a crackling sound. It's faint but none the less enough to be annoying whne talking on the phone for awhile. Any one else having this problem or have a solution to it? Thanks ahead of time.

[mastachillz]

I have the sprint 7800 with 6.1 mobile and I am having an issue with my reception as well with this radio. When I make / receive phone calls I get a crackling sound. It's faint but none the less enough to be annoying whne talking on the phone for awhile. Any one else having this problem or have a solution to it? Thanks ahead of time.

unless you are using coarse speaker settings most likely that is a hardware issue is it only at high vol or when it low to.

[sandiegodude]

I read on another thread that changing mobile ip to preferred fixed the error for someone. still haven't tried a 3.27 rom in a whil to test. still waiting for a solid resolution instead of taking a shot in the dark. any luck?

[rp3319]

Here's a temp solution that works for my VZW phone:

after a reset, while the phone is searching for a signal, I went to the phone func and entered *22803. It then finds a roaming signal and starts "programming". At that point I hit call end and it picks up the signal and goes to EV, full bars. The phone says programming unsuccessful, but if I close the phone and re-open it, everything is fine.

[Willybeen]

can anybody else confirm this.... ? I dont get why it worked when i flashed my room mates phone, but when i did the same thing to mine, it had the problem....

Ill give it a shot if anybody else can confirm it... my phone is finally back to a reasonable phone again.. thanks for the advice though :)

[Geckotek]

Here's a temp solution that works for my VZW phone:

after a reset, while the phone is searching for a signal, I went to the phone func and entered *22803. It then finds a roaming signal and starts "programming". At that point I hit call end and it picks up the signal and goes to EV, full bars. The phone says programming unsuccessful, but if I close the phone and re-open it, everything is fine.

Tried this and no go for me. Mine says "Programming unsuccessful" instead and still no signal.

Tried *22801 and the call dropped as ususal.

Tried *22802 and the programming was unsuccessful, but I now had signal but data was 1x. I was able to make an outbound call at that time. Data now switching back and forth between 1x and EV (usually always see EV.)

Duplicated this by reseting and trying again. *22802 works for me.

Wondered what *22802 and 03 were and found this:
*22800 for Cellular A network
*22801 for Cellular B network
*22802 for PCS A network
*22803 for PCS B network
*22804 for PCS C network
*22805 for PCS D network
*22806 for PCS E network
*22807 for PCS F network
and so on...

And this:
*228 80 - force update, ignore fails
*228 99 - force seconday tower update
*228 00 - original tower update

[rp3319]

Tried this and no go for me. Mine says "Programming unsuccessful" instead and still no signal.

Tried *22801 and the call dropped as ususal.

Tried *22802 and the programming was unsuccessful, but I now had signal but data was 1x. I was able to make an outbound call at that time. Data now switching back and forth between 1x and EV (usually always see EV.)

Duplicated this by reseting and trying again. *22802 works for me.

Wondered what *22802 and 03 were and found this:
*22800 for Cellular A network
*22801 for Cellular B network
*22802 for PCS A network
*22803 for PCS B network
*22804 for PCS C network
*22805 for PCS D network
*22806 for PCS E network
*22807 for PCS F network
and so on...

And this:
*228 80 - force update, ignore fails
*228 99 - force seconday tower update
*228 00 - original tower update

Interesting... I haven't tried any of the others yet...
PS: my old 6700 has the MIP retry setting at 1750ms (which is what my 6800 is set to right now too). I'll try setting it to 1000ms and see if that fixes the issue. If not, I'll try these other programming settings to see if they do anything different.

[Geckotek]

Retry @ 1000ms did nothing for me.

[rp3319]

Mine's already on mobile ip prefered setting, but maybe that's something that changed when it connected the first time...

[Geckotek]

I was also having this problem, what I did that fixed the problem was i reentered the MSID and MDN in the ##MSL# screen. Then allowed the phone to reset. from that point forward I get signal as soon as it powers on from reset. Hope this helps.



Thanks pkp190!!!!

[rp3319]

Retry @ 1000ms did nothing for me.

Geckotek - I did this too and nothing, but after it came back up, I did the *22803 /cancel to get a signal again (that method still working fine). I then reset my retry value back to 1750ms and I also changed a few of the other values and then reset them back to their original values before closing and it seems to have worked. I've soft reset twice and things are working now!

[Geckotek]

Yeah, I meant to repost that it stopped working again, but maybe I should reset and try a couple more times.

I was waiting on a tech that was going to call me back and review all the settings, but I think I may have reset when she called back. Grrrrrrr.

[rp3319]

My theory is that there's something that gets updated in the process of cycling through the setting options - even if all you are doing is changing them back to the original values. The settings I "edited" but didn't really change the end value were:

MIP_MODE (mobile IP only)
MIP Registration Retries (2 - only other options were 0 and 1)
MIP Reg Timeout (1750ms - I had changed this to 1000ms and saved, but that didn't fix the issue)
MIP Pre-Reg Timeout (0)

These are the same settings as my 6700, which picks up a signal in about 2 sec (it's not activated).

Best of luck to everyone else - hopefully something in here will work for others too.
Maybe someone else can narrow down exactly what's happening.

[Willybeen]

Can anybody confirm that this truly does work? my internet stopped working when i originally flashed this rom too, and that never came back for me :(

[Geckotek]

Can anybody confirm that this truly does work? my internet stopped working when i originally flashed this rom too, and that never came back for me :(

Sorry, forgot to come back AGAIN and repost that it is working for me now.


I flashed back to the stock VZW ROM (third time I think), I made sure all of my provisioning issues with Verizon were worked out (finally had the tech "kick the switch").
1) Then I proceeded to load the 2.4 bootloader,
2) then the 3.16 Unauthorized Sprint ROM w/ radio,
3) then finally installed a cooked DCD 2.3.2 ROM.

Things to note:
1) I never let the Sprint ROM boot up
2) I had no signal so ran *22802 then hit End as soon as it connected
3) Still no signal after reboot
4) No A key, MSID, or MDN issues, but I did re-enter the MSID and MDN as discussed in other threads
5) After re-entering MSID and MDN then after reboot I had signal
6) never had to run *228 to OTA program (in the past programming with *228 has reversed the effect of re-entering the MSID and MDN)

In general, I feel that the OTA from VZW sends down some programming that conflicts with the 3.27 radio...but I have nothing to prove that.

GPS is running great (I just loaded the AstroGPSLauncher)
Not sure about Rev A. It does seem snappy. What's a good site to test from the phone?

I'm happy and not re-flashing until a solid radio for Verizon arrives.

[Willybeen]

awesome.. im still hesitant, but w/e... ill wait another couple weeks before trying it with yet another new phone.. lol

[keeepinitgansta]

Try Prl 60610

[Lightman]

None of the above has worked for me...argghh I'm so mad I messed with it...I had 2.3.2 working just fine but stupidly decided I'd give a *228 a shot...now here it is again, no a-key and searching for signal..takes 15 mins.. Last time this happened I had to call vzw and get an a-key, and once I entered it, the phone reset, and it had signal immediately..just annoyed to have to do that again. I wish someone would figure out what causes this problem.

[Geckotek]

None of the above has worked for me...argghh I'm so mad I messed with it...I had 2.3.2 working just fine but stupidly decided I'd give a *228 a shot...now here it is again, no a-key and searching for signal..takes 15 mins.. Last time this happened I had to call vzw and get an a-key, and once I entered it, the phone reset, and it had signal immediately..just annoyed to have to do that again. I wish someone would figure out what causes this problem.

My last round I decided to see if I could make a call w/o dialing *228. I could, so I never ran it. Working like a champ. Seems like *228 always made things worse after the upgrade.

You did try reentering the MSID and the MDN?

[Lightman]

That was my prob, I should have never done *228 after getting the akey and everything working right. I did try re-entering the msid and mdn but to no avail..

[Lightman]

As suspected, I called vzw tech support this morning and asked for a new a-key, as it was taking 10-15 mins after each soft reset to get signal etc. As in the past, as soon as I entered the new a-key, the vzw tech confirmed the phone reset on the network, and upon soft resets now, I have signal in less than 2 seconds upon boot up. I think for now, at least for some reason the answer on my end is to NEVER *228 or hard reset. Either one loses the a-key for me and then it takes forever to get signal again.

[answerman]

Sounds like the new official 3.35 radio is fixing some of the reception issues as well.

[Lightman]

sounds like the new radio is a royal pos and causing its own problems.

[Geckotek]

sounds like the new radio is a royal pos and causing its own problems.

I wouldn't say that, it works fine for people using it with the ROM it was delivered with.

The problems come from customizations made here. Sprint can't account for that so now it's up to those doing the customizing to adjust their code for the changes in the new release.

[answerman]

The problems come from customizations made here. Sprint can't account for that so now it's up to those doing the customizing to adjust their code for the changes in the new release.
Right... DCD is already planning on a new kitchen tonight to take the missing drivers, etc. into account. I'm waiting till then to flash.

[nunyabiziz]

I think it has something to do with the SID. I have had this problem too, but after some point in time the problem went away. This happens after a reflash of the radio. So there must be some required data from the provider via OTA that the phone received at one point or another. By the way does anyone know the SID for Houston TX?

[nunyabiziz]

Just resolved the issue, "##3282#, edit, msl, MENU, Restore, OK". After the soft reset do the OTA again and this should fix the corrupted data profile. If this doesnt fix the 1012 error or the long signal reception issue then call CS(technical support) and have them force the data profile update.:D

[Geckotek]

Just resolved the issue, "##3282#, edit, msl, MENU, Restore, OK". After the soft reset do the OTA again and this should fix the corrupted data profile. If this doesnt fix the 1012 error or the long signal reception issue then call CS(technical support) and have them force the data profile update.:D

This is for Sprint right? Doesn't work for Verizon.

[nunyabiziz]

Yes instuctions was for Sprint but for Verizon you might need to know your A-key and after the restore just do a *228.

[Willybeen]

AWESOME thanks

[ThrottleAbuse]

On VZW when I dial ##778# it rings then says welcome to vzw the number has been changed or no longer is in service. WTF. It used to show the view edit cancel thing. Now it shows this. Any ideas?

[getwilde]

**SOLUTION**

1. Have MSL code ready
2. From phone app, type ##PST#
3. Click EDIT
4. Type in MSL code
5. Click VIEW INFO in bottom left corner
6. Click M.IP SETTINGS
7. Change value of MIP REGISTRATION RETRY to 1000 ms
8. Change value of MIP MODE to MOBILE IP PREFERRED****
9. Click MENU in bottom right corner
10. Click OK
11. Soft reset device


I have been experiencing this issue for a while now, too. 3-5 minute waits to acquire cell tower signal. (BTW, I haven't flashed the new Sprint ROM yet.) This seems to have fixed the problem! Whenever I reboot, I immediately acquire a celltower signal now. Excellent find!

[Shiva1]

It worked for finding a signal faster, but I still can't access the internet while roaming :(

Does anyone else have this problem?