yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] th3taman:
WARNING: I'm concerned that this update took away my ability to use data or voice while roaming.. It's not a huge deal for me but does suck because I need it sometimes. I get a message from Verizon telling me they can't validate my phone number (or something like that). I probably would have left my PRI alone if I had known that this would be the result. :(

Are others having this problem? :confused:
[EVO 4G Android Development] Milz02315:
YES, I got this yesterday as well while trying to ##3282#, however I still have the 1.34 PRI.
[EVO 4G Android Development] th3taman:
So you lost your ability to use voice or data while roaming AND don't have the 1.34 PRI?

Damn this sucks.
[EVO 4G Android Development] ycats:
must be a better way to get 1.4, doing the ##786# and ##3282# a hundred times has gotten old
[EVO 4G Android Development] blueblur:
I got this problem too last night.. I was roaming because the building I was in didn't have a sprint signal so when I tried to call, I got a message from Verizon saying it couldn't complete the call because my phone could not be authenticated.

I thought it might have been a glitch....

No SMS, voice or Data would work..

:::edit::: looks like its being discussed in http://xdaforums.com/showthread.php?t=696073&page=112 ... going to try the webchat and see if it can be fixed.

FYI.
[EVO 4G Android Development] th3taman:
Thanks, looks like I need to call Sprint.
[EVO 4G Android Development] sanjsrik:
I tried this last night and it didn't update the PRI, NOW, however, I can't invoke (start) either ##3282# or ##786#

When I input either of them I get the prompt that it's starting services and then goes back to my dialer screen. Any and all advice on how to get to EPST would be greatly appreciated.

Thank you in advance.
[EVO 4G Android Development] lamboh:
mee 3 :(:mad:
[EVO 4G Android Development] blueblur:
No problem!

Update: contacted sprint through Webchat and I told them the problem I was having: When calling while roaming a message comes on saying that Verizon can't complete the phone call because it can't authenticate the phone.

He updated some information on his system and told me to turn off the phone for 3 minutes and then plug it back in. I took out the battery during this period and turned it back on.

This is kinda ghetto but I had to go to our bathroom here at work where it switches over to verizon and I was able to make a call! CONFIRMED WORKING w/ 1.40 PRI.

If you're phone shy, go for the webchat...a lot easier.

Good luck!
[EVO 4G Android Development] th3taman:
I already called. They did a similar thing with me. Except the rep also wanted me to changing the roaming from Automatic to Sprint Only. Did the chat rep ask you to do that as well?

Getting ready to go test now.
[EVO 4G Android Development] blueblur:
No, he said nothing about setting to sprint only (I wouldn't want to do that anyway or otherwise I'll have no signal when there's no Sprint signal so technically it wouldn't solve my problem, just avoid experiencing it!)
[EVO 4G Android Development] MalaysianMafia:
what is a PRI and why should I update it
[EVO 4G Android Development] sniggle:
I had this problem when I was running the BakedSnack rom. I ended up ultimately flashing Fresh and it worked fine.
[EVO 4G Android Development] th3taman:
Your right, making this change just gave me no signal. I switched it back to automatic and now I can call while roaming! :D

Anyone that loses their ability to roam after getting the PRI update, just contact Sprint. They will do some kind of update that will enable it again.
[EVO 4G Android Development] ycats:
can we call them to get the PRI update instead of doing all these ##786# and ##3282# resets?
[EVO 4G Android Development] sanjsrik:
I was running Fresh, had to to a complete wipe and reflashed Fresh, just restored using TI Backup.

man, if it wasn't for TI backup, i don't know how I'd get back to working in 10 minutes. Best money ever spent.
[EVO 4G Android Development] th3taman:
No, they may ask why you have a different (lower) PRI. Which would be from rooting...I wouldn't want to mention that to a CSR.

I only called to get my roaming fixed after the PRI update was made. I just mentioned I had done a software update and that roaming didn't work anymore. I can say that ##3282# didn't work for me after 20 some tries in several different locations.

##786# worked for me on second try. I would do that method...just my two cents.
[EVO 4G Android Development] JG-1:
Did all the non-rooted phones that did the OTA 2.2 update to 1.40?

Just checked my wifes phone and she has 1.40....she's unrooted.
[EVO 4G Android Development] th3taman:
Out of the box EVO's come with 1.40. If you rooted via toast's method, that downgraded you to 1.34. Some other root methods do not.
[EVO 4G Android Development] jedil1c1ous:
Just my experience but I believe I know what matters - the tower you are connected to.

I tried multiple times the ##786# method to no avail. As soon as I left work and started driving, I was on a different tower and the ##786# method worked the first try. I was able to nand restore my backup and good to go on 1.40x.

For those with problems, try doing it on different towers. I firmly believe that's the deciding factor. FWIW, I'm on Netarchy's Odexed Stock Root build.
[EVO 4G Android Development] JG-1:
Gotcha....didn't know that.
[EVO 4G Android Development] blueblur:
I was hoping going to 1.40 PRI would resolve my 3g speeds (which are 256k! in rochester) when they used to be 2mbit+ ... not sure when it slowed down but I think it was right around the time I started trying different PRLs... reverting back to sprints regular PRLs didn't fix it either.. Not sure if its 2.2 froyos issue or Netarchys kernel (not pointing fingers but just thinking of possibilities) or even Baked snacks... Perhaps I'll nandroid and go back to full root stock and try again...
[EVO 4G Android Development] sanjsrik:
I have a follow-up question to this:

IF I go back to Stock non-rooted OTA that was released for 2.2 and then flash Fresh over it after doing a complete wipe, will that still retain 1.4 or will it bring me back down to 1.34?
[EVO 4G Android Development] th3taman:
I believe that it was the actual root process that downgraded to 1.34. Flashing ROMs doesn't change your PRI...as mentioned by a post from Fresh (on his site) where he suggested to do a nandroid backup and flash it after getting the 1.4 update.

Flashing ROMs should not change or update your PRI...going forward or backward with your software version.
[EVO 4G Android Development] bigsalot:
Nope, my wifes phone is un-rooted (not stock) and hers won't take the PRI fix. I took hers back to the release RUU and OTA updated to 2.2 and its still at 1.3. I've also tried at least 40 reboots using the various methods of getting 1.4 with no luck. Her phones keeps loosing connection while charing, but now im worried about the 1.3 tip off of a past root.
[EVO 4G Android Development] :
In my original post prior to updating it, I too had unrooted to accept the OTA Froyo. I was completely stock except for the PRI 1.34. Since I received my phone I have been exploring potential apps and theming it so once it got cluttered I would make notes of what worked for me then do a factory reset to start fresh. The PRI had also been bugging me which left me at bay on the final look and feel I wanted. I did a factory reset then said what the heck...did a ##786# reset and got it first try.

I am saying all this because after closely following this thread I too feel that the actual tower plays a major roll. If her phone is stock like mine was maybe if possible try a different tower?
[EVO 4G Android Development] SgtSpike:
##786# method doesn't boot into recovery

I tried the ##786# method and I get a reset followed by a standard boot. No recovery mode as the instructions state. Then runs through activation, PRL update, firmware update, no errors, everything works.

PRI still at 1.34

Any thoughts?

rooted, RA, Fresh 3.1.0.1, stock kernal, Riptide themes

(also my 4G turns on, scans, then turns off, over & over & over, this has been happening for days which is why I tried the PRI update)

Thanks,

Spike

UPDATE: wiped and installed flipz new 3.1.0.2 ROM and now the ##786# DOES do a recovery boot & wipe as it should. I had Riptides V4 then V5 themes installed. (not blaming Riptide which is a killer theme, just sayin what I did is all)
[EVO 4G Android Development] hdad2:
I've seen it asked a bunch of times, but I've not seen any response. Can anyone answer the questions:

Can the updated PRI be extracted and flashed? -We all flashed down to 1.34, so it stands to reason that would could flash the updated version.

If the answer is no, why not? Is the area of memory not accessible to extract from? -Again, my simple brain says that we flashed it once so flashing it would not be a problem. The problem must be extracting, right? Has anyone tried?

Anyone?
[EVO 4G Android Development] th3taman:
Don't know the answer but you downgraded as part of the root process, which is different than flashing a ROM or theme...I'm guessing. Sorry I can't answer better than that.

Sometimes to get what we want...we have to go the hard route...unfortunately.
[EVO 4G Android Development] bigsalot:
So you have an un-rooted 2.2 evo with PRI 1.4. Thx for the conformation Cardiox. I'll keep trying. It's just funny because my evo is rooted and I got PRI 1.4 easily at the same location I'm tryin to get it on her un-rooted evo. Thx again.
[EVO 4G Android Development] gessin64:
Just got my PRI update in Miami Fl no real speed difference but my ping came back faster...just glad I have it back to fresh rom
[EVO 4G Android Development] hdad2:
Thanks, but since I'm in the unlucky bunch who can't get the update, I sure would like to understand why it can't be done thru flashing. I thought that flashing the eng hboot was the point when we got downgraded. So somehow a PRI was packaged into that. I'd love to know why that wouldn't work with the new one. It makes sense if its just because no one has been able to extract yet. But I've not seen this stated
[EVO 4G Android Development] eniamg02:
Ok i tried the ##3282## about five times didnt work.So i tried ##786## and it worked on the first time im getting much better 3g speeds.with 1.34 i was getting around 500-600kb maxed i got 1,500kb easily on 1.40.btw did this on calkulins evio 1.1

My question is this:i have a nand backup from a couple days ago with pri 1.34 if i restore that back up will the 1.40 pri still stick or will it revert back to 1.34?
[EVO 4G Android Development] Kyral Retsam:
I'm getting the 4G cycle as well. You can kill it manually if you turn it off when it's "on". Also the ##3*** method hasn't worked for me yet either :(

NAND Unlocked, Rooted, DC 3.5, Netarchy's 4.1.2 Kernel.
[EVO 4G Android Development] omv0:
FINALLY

Wow after going back and forth with each method the PRI finally updated to 1.40! I didn't do ANY wipes, so that step is definitely not needed. It took approximately 10 tries. Thanks for the support =)
[EVO 4G Android Development] beartrap:
I'm giving up. Tried the wipe and no wipe methods about 15 times in 5 locations in San Antonio and tried in 3 locations in Tampa. I've tried loading other ROMS. I tried the ##MSL# method with no luck. I don't know what else to try.
[EVO 4G Android Development] :
As long as you don't for some reason re-root you should be fine. Flashing roms was not the reason the PRI downgraded.....rather the root process did it. Do not re-root and PRI should stick.
[EVO 4G Android Development] alafferty:
I was able to restore my backup after getting the 1.40 PRI update and it kept the 1.40 PRI. The reason for this from what i can tell is because when you do a restore it doesnt re-activate on the network and that data seems to be written to maybe a some ram or a part of hardware but that is just my guess and i am no expert. I have been researching what the PRI actually does. I have an inside guy at sprint and he didnt know for sure but was going ask around for me.
[EVO 4G Android Development] scottspa74:
Ok, I'm skimming thru this thread, but I'm at work and its taking forever, so I'm just gonna ask. If I do this, and it goes thru, I will still keep my eng-hboot right? Or will it put me on .79.0000 hboot?

I was on 1.40 before and my 3g was crazy fast. Now on 1.34, almost unusable. Doing a Ti backup right now.

BTW, just called Sprint, not even tier 2, and got my msl, no questions asked, no hesitation. There's probably an internal memo circulating at Sprint tech sayin all Evo owners want their msl ;)

Anyhow, thanks in advance.
[EVO 4G Android Development] churchwin88:
You will still keep the .76 eng-hboot with either method. If you haven't, I would do a nand backup as well as the titanium.
[EVO 4G Android Development] scottspa74:
@churchwinn

Right on, thanks bro. And damn that was fast. ;)

Edit: ok, I'm at work. Have tried the #786 method about 8 times. Sometimes wiping, sometimes not, sometimes twice. Nogo . Did however keep eng-hboot .76.2000. About to try the 3282 method. Also, when I reset, I got a msg sayin a voicemail update was available (usually have Sprint updater disabled) I'm a bit afraid to accept it.

So, got home from work, about 15miles:confused: difference. True some more, both methods. Wipe, no wipe , etc. Still nogo. So frustrating. I remember how fast my 3g was on 1.40.

Im in the Seattle area/market. In a 4g market, fwiw.

Using netarchy rooted stock 2.2 and had reverted back to stock kernel to do this and am using amonRA, just don't know what the hell?! (was previously on his 4.0 kernel), again fwiw. :(
[EVO 4G Android Development] seriousblack25:
FINALLY!!!

After a Weeks worth of trying(actually tried 3 times and give up for a week) i finally got this working lol
[EVO 4G Android Development] makskylan:
I try to do the ##786# and after I enter the msl code, hit menu, and reset, it takes me to recovery and says "formatting data, formating cache " and just sits there. I let it sit there, seems like forever. I finally hit reboot and it ends up doing a bootloop. Am I not waiting long enough or am I doing something else wrong?
[EVO 4G Android Development] aamikam:
u r probably on a custom rom that might have issues with it...

try to flash to a rooted stock rom... then it will work for sure.
[EVO 4G Android Development] jwterminator:
Having a custom rom doesn't seem to really matter that much. I was able to get the update using fresh 3. What finally did it for me was flashing amon ra recovery. After I did that, using the 786 method, my phone automatically booted into recovery as part of the reset process. I went ahead and wiped all the data/cache partitions for good measure and thus cannot confirm wether it was necessary or not but once the phone rebooted and activated, I had pri 1.40
[EVO 4G Android Development] alafferty:
Can someone that has PRI 1.40 do a ##768# and scroll to the bottom where it says PRI version and PRI checksum and tell me what you have for the checksum.
[EVO 4G Android Development] dfrias:
I have PRI Checksum - 9CF1D419
[EVO 4G Android Development] alafferty:
Interesting. I am trying to update to 1.4 and my checksum is all zeros. The one thing to note is that I did get to 1.40 a couple of weeks ago and hosed up my phone so i had to re-run the root process and that downgraded me to 1.34_003 and now i cant get it to update at all and i have tried probably a 100 times with different roms and different recovery images.

if there is someone else out there having issues getting to 1.40 and are still on 1.34_003 can you do the ##768# and scroll to the bottom and see what your checksum is if you have one? Just trying to see if we can piece this PRI thing together.
[EVO 4G Android Development] chazglenn3:
Yeah...same here. Tried MANY times in the Seattle/Tacoma areas. No dice...
[EVO 4G Android Development] cowfodder:
All zeroes.
[EVO 4G Android Development] nukedukem:
I had all zeros on 1.34 and now I have a checksum value after upgrading to 1.40. I think it will be the same for everybody.
[EVO 4G Android Development] erikjonpeterson:
All zeros in Chicago and no luck updating after 50+ tries.
[EVO 4G Android Development] alafferty:
oh well it was just a thought, trying to make sense of it. Hopefully someone will figure it out. I know this XDA community has some crazy smart peeps in it, i just dont happen to be one of them ;)
[EVO 4G Android Development] cowfodder:
Making some headway. My PRL version is 60670 instead of 60690. Still 1.34 though. Giving up again. I'll try in a few days.
[EVO 4G Android Development] beartrap:
My PRI Checksum = all zeros and I can't get PRI 1.40
[EVO 4G Android Development] hdad2:
I hate to be the jerk on the forum who keeps drilling home the same question, but....still haven't seen a reasonable answer.

I have such an appreciation for the awesome devs and the work and information they share on this forum. I'm just waiting for a glimmer of hope that someone can get this extracted to be flashed...
[EVO 4G Android Development] anothertmobilemda:
strange after 20+ attempts my prl changed from 60690 to 60670 aswell ...im gonna try several diff towers around portland and see what happens:(
[EVO 4G Android Development] drizkol:
PRI Version: 1.40_003

PRI Checksum: 601985A5

Took me 2 tries with the ##786# - "Reset" - I'm running latest Fresh and Amon
[EVO 4G Android Development] sanjsrik:
Mine updated as well, 670 rather than 690, but every once in a while the PRL is updated. Nothing surprising.
[EVO 4G Android Development] tommy96814:
so what's the point of updating the pri?
[EVO 4G Android Development] akarol:
Still on 1.34 here in Orlando, FL. Anyone in the area able to get 1.40?! If so, where from?

I've tried from the Sea World and UCF area with no luck. :(

BTW - 60670 here.
[EVO 4G Android Development] msolis03:
Any one in Stockton, South Sacramento, Sacramento, Folsom, or Rancho Cordova tried the PRI update and had success?
[EVO 4G Android Development] uclajw1:
PRI update

My PRL went back to 60670 but still the same 1.34 PRI. However, I now get 4G coverage (0-1 bar) in a room where before, I was never able to get any 4G signal. Hacienda Heights CA. Maybe they turned up the signal and this is just a coincidence.
[EVO 4G Android Development] rugedraw:
PRL and PRI are not the same thing, guys. The new PRL is available to anyone, as Sprint just started pushing it out so anyone who does this process trying to update the PRI gets the updated PRL by default now that it is being pushed.

The PRL (preferred roaming list) is a list of bands and channels in order of preference which the phone uses when it attempts to locate and connect to a cell system, such as when you first turn the phone on. It is a list of SIDS (System IDs) that the carrier has roaming agreements with.

A PRI (Primary Rate Interface) is a telecommunication standard used in the Integrated Services Digital Network or ISDN, for carrying multiple DS0 voice and data transmissions between two physical locations.
[EVO 4G Android Development] gabesir:
what gives.....i flash fresh rom and updated the PRI by doing ##786#....;)
[EVO 4G Android Development] fuzion22:
Confirmed this method works in El Segundo, CA

1. First I reset my phone by using ##786# Method

2. Phone rebooted into recovery (using Amon RA BTW)

3. Wiped data/factory reset, wipe cache, wipe dalvik-cache in that order

4. Flashed Netarchy's HTC OTA 3.26.651.6-final-froyo-rooted-odexed rom

5. Reboot Phone

Waited for the hands free activation to complete, updated PRL, let phone check for firmware update. Hope this helps for anyone else in the LA County area.
[EVO 4G Android Development] stroths:
I tried both methods probably about 10 times using fresh and vael's roms. No luck, so I moved to Netarchy's Rooted 2.2 Stock ROM. Tried both methods and still no update.

All previous attempts were w/Clockwork. Flashed RA and it worked the first time using the ##786# method on the Netarchy Rooted 2.2 Stock ROM.

Now I am flashed back to my CM nightly w/PRI 1.40 and the new PRL (60670)

EDIT: I am not seeing any real difference in speed. Might just be the tower near my house. Will try at a different location later.
[EVO 4G Android Development] deusofhearts:
Finally decided to do this update. Flashed my CM6-RC2 rom to netarchy's deodexed 2.2 and did ##3282# for hands free activation. Two tries and was still stuck on 1.34, so I went ahead and did ##786# for the full wipe and PRI is now updated. Relatively painless procedure :)
[EVO 4G Android Development] beartrap:
Yea!!!! I finally got 1.40 PRI !!!! Easily my 25th or more try. I ran the wipe method, no update. Then ran the unwipe method, no update. I then ran the wipe method again and it updated. Now to restore my nand backup and put this behind me.

Update - I went to restore my nand backup and the folder wasn't there. I hooked up by USB to my computer and my SD card was wiped. I must have selected that option by mistake while I was wiping. At least I had copied my last nand backup to my computer so I can put it back on the phone. I'm doing that now - success. Now I've got to get my music copied over but I'm back to where I was last night but with 1.40 PRI.
[EVO 4G Android Development] SouL Shadow:
Just to clarify, prl updated from 60669 (not 60690) to 60670. In case someone reads the previous posts and mistakenly thinks their prl was downgraded... I can see the flood of posts already...

-SLS-
[EVO 4G Android Development] nsxla:
Wow this is doing my head in, initially i was running Fresh Evo 3.1.0.2, with a custom kernel KiNgxKernel #3, my PRi didn't change after about 5 tries.

So i installed HTC-OTA-3.26.651.6-Final-Froyo-Rooted-Odexed-netarchy-signed after a complete wipe, not no SD partition, and flashed the stock kernel 2.6.32.15-g746f4f0 htc-kernel@and18-2#58 <- hopefully the right kernel? and still not working for me here in Carson,CA

Update okay finally got it after 20+ tries!! Is it safe to do wipes now cache and dalvik? i can't afford to go back to the older pri!
[EVO 4G Android Development] metayoshi:
I finally decided to do this... I was on DC 3.5 and I tried to update there with no luck, but I flashed over to the stock rooted ROM by netarchy, and first try did it.

I don't really see a change, but at least I know I'm up to date.