yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] frozndevl:
Just wanted to add my information to the mix. I was trying to do the ##3282# method using DC 3.2.3 w/ netarchy's 3.7.5 kernel, latest radio and wimax and was having no luck. I decided to go for the ##786# method, and after wiping, I flashed the stock rooted OTA by netarchy. It didn't take the first time, but I did another 786 wipe and after activation it was now at 1.40. Nandroid restore and I am a happy camper.

Located in downtown Seattle for those keeping score.
[EVO 4G Android Development] sgt. slaughter:
I had been trying this all morning and last night with no luck. after reading the post on geekforme i decided to try again and it failed.

Steps were:

-On DC3.2.3 with full root

-rebooted to clockwork did full wipe and reset data, then installed Netarchy's Stock FroYo rooted OTA

-rebooted and still had 1.34PRI and did ##786# and once it was all back up I still had 1.34

-After re-reading geekforme I noticed they said when they did the ## they got into recovery which I did NOT since i Had clockwork so I DL'd rommanager and changed recovery to Amon's

-did the ##786# and this time it sent me to the recovery and showed it formatted the data and cache at the bottom and I selected reboot from the menu

-once back up and activated again checked about phone and had 1.40PRI!!

All it takes is downloading rommanager again and reflashing clockwork to restore my backup and im gtg

*I dont know if it was me switching to amon or something else but amon was the only change I did and got it first try.
[EVO 4G Android Development] bludragon742:
Didn't work for me :( I think I'm gonna give up on this. What's funny is the fact that this phone came with 1.40 but reverted when I rooted.
[EVO 4G Android Development] Rocklee99:
Worked here on second try

Worked on my second try with the ##786# method, doing a restore now
[EVO 4G Android Development] sgt. slaughter:
Well now this time after restoring I got no service and tried a restart of phone and upon restart had constant force closes so Ima have to try clearing again and restoring back now. lol

Should be gtg then.
[EVO 4G Android Development] chrisctb:
worked for me using fresh.

3rd tried using the ##768#
[EVO 4G Android Development] guyver2077:
what happ to original post with instructions?
[EVO 4G Android Development] xHausx:
ok... I have an idea but am not sure which thread to put it on so I will just post it here.

It seems the PRI is only being updated either by pure luck, or most likely, if there is a certain environment or trigger that is causing it to update. Assuming it is only updating when it thinks it needs it, would it be possible to corrupt or remove the old PRI and force it to update?
[EVO 4G Android Development] nicholaaaas:
half the people say a stronger signal works... half say a weaker signal works
[EVO 4G Android Development] dmoses1969:
I just did it on avafroyo rom with terrible signal in my house. 1-2 bars all the time. It seem to take awhile for it to finish but after it rebooted and went the hands free activation mine is updated now.
[EVO 4G Android Development] TheMike1:
It is a Shame this thread was merged the way it was. There are 2 DIFFERENT ways of doing this. The original way I posted does NOT REQUIRE YOU TO DO A FACTORY WIPE.

Can a Mod please correct this?
[EVO 4G Android Development] mchunu:
My prl goes through fine. Just the voicemail errors.
[EVO 4G Android Development] TheMike1:
***THE Original Post that DOES NOT REQUIRE YOU TO DO A FACTORY RESET/DATA WIPE***

We have all seen the threads where you do a ##768# Factory Reset after doing a Nandroid Backup and this will initiate Hands Free Activation which ultimately after a couple tries will update your PRI.

Why not cut to the chase and do a ##3282#?

This will allow you to Start the Hands Free Activation Process and update your PRI without forcing you to do a Factory Reset.

Steps:

1. Dial ##3282#

2. Enter Edit Mode

3. Enter your MSL

4. Select Data Profile

5. Menu

6. Restore

7. Let Phone Reboot, and Wait and the Hands Free Activation will Start.

8. Repeat until you have 1.40 PRI.

Edit: Both of these methods seem to work sporadically, so if it does not succeed the first time keep trying. Some people report success after 10+ attempts. At lease doing it with ##3282# does not require you to Wipe Your Data and is quicker/easier to repeat ad nauseam :D

Cheers.
[EVO 4G Android Development] meo1pr:
Will this fix work on a non-rooted Evo?
[EVO 4G Android Development] cnstarz:
took me about 4 tries. i tried on fresh 3 twice. no-go. when it was in recovery from the 3rd try, i went ahead and flashed steelh's rom. no-go. tried it one more time from steelh's rom and it finally went through.

san antonio, tx.
[EVO 4G Android Development] reigndropz:
Why your PRI update isnt working

The reason most of your PRI updates are not working is because the stock rom you are flashing hasnt been changed to pc36img.zip..... i have tried every method here and i believe the reason its not working because of this. Flash the stock rom, do the whole ##786 and ##3282 thing and make sure your . Zip stock is named pc36img. Zip and you will get it after activation. Try it. If a mod tries it and it doesnt work, then close the thread. Im telling you its the only thing that worked for me.
[EVO 4G Android Development] grouse130:
After six times I finally got it to go through. I am on Baked Snack 1.2.5. :)

I am located in Birmingham, AL for those keeping track.
[EVO 4G Android Development] xHausx:
Didn't work for me, it just turned out to be a pain in the arse because I had to update the radio/wimax again and now I keep getting pcs login errors.
[EVO 4G Android Development] tyrnight:
I had to use the odexed netarchy version of the OTA rom that is rooted but UNMODIFIED in any other way, in order for this to work. Using an other rom DIDNT work for me.
[EVO 4G Android Development] topdawgn8:
I didn't flash any stock rom...

Just ##786#, menu, reset, input MSL, wipe to stock, cache and dalvik, reboot.

I had to do this twice for it to catch (second time I didn't wipe to stock). I was running Fresh 3.1.0.1.
[EVO 4G Android Development] butterbuns:
i did the same thing and worked fine aswell
[EVO 4G Android Development] Seventek:
Worked for me on 3rd try.. Fresh 3 w/ netarchy kernel..

Just had to keep doing it.
[EVO 4G Android Development] mardukeme:
Wondering the same thing!
[EVO 4G Android Development] wfrandy:
I keep seeing all of these different methods that are supposed to be "the best way", and I have to say that I firmly believe it is just a matter of luck. If I had to make an educated guess, I would say that the problem is that the update is not on all of Sprints activation servers yet. Each time you try to update you may connect with a different server. When you hit the one with the fota on it, you get updated. Simple as that. Some guys get lucky and hit it the first time, others like myself, have to try 18+ times to hit the right server.

One thing seems obvious to me though, as long as you are on a rom that alows you to do the ##----# code, it doesn't matter what software you have on your phone. I think it is pretty obvious by the variety of roms that have worked, that the activation server does not check what you are running on your phone. As long as your hardware checks out and corresponds with a valid Sprint account, and the activation server you are on has the fota, it will update.
[EVO 4G Android Development] Tilde88:
i spent countless hours yesterday doing gonnzy method.l.. all failed... flashed DC 3.5 ...786... wiped my ass 2x... got it updated
[EVO 4G Android Development] xHausx:
This problem is a result of rooting evos using older software, if you are not rooted your PRI should already be version 1.40
[EVO 4G Android Development] reigndropz:
Please dont convolute this post with what worked and didnt work, just state if it worked for you. Thanks.
[EVO 4G Android Development] rileyd5:
I have tried 2 pc36img.zip that were recommended on this site, unfortunately they did not work for me.
[EVO 4G Android Development] mardukeme:
Not if you upgraded to the leaked update, or did the ota.
[EVO 4G Android Development] dakotaSioux:
Same here. Clockwork wasn't successfully formatting data and cache, it would just reboot and skip it. Had to load Amon's via Rom manager and went through on second try.
[EVO 4G Android Development] decus22:
Fresh 3.1.0.1

Oklahoma City

Wiped everything twice

Worked on the first try.
[EVO 4G Android Development] reigndropz:
yes! At least one success story!
[EVO 4G Android Development] rac2371:
Changed to Amon RA

##786# and hit reset

recovery... i wiped everything twice.. dalvic cache etc...

reboot and now I have new pri

I tried many times with clockwork recovery
[EVO 4G Android Development] herbthehammer:
I'm sorry because this is probably not the topic to post this under but it does have something to do with this subject.

The majority of these steps that people are saying, my phone isn't acting the way theirs are. I'll get up to the point to where it wants to reboot but it won't automatically go into recovery. I obviously can't catch it before that either. I thought about doing a battery pull when it wants to reboot, but haven't tried it yet. Another thing that many people are saying is to use amon recovery. I tried to install that awhile ago per his instructions and failed miserably. I failed so bad that it screwed up things to where I didn't have a recovery working. Previously I was, and still am, running clockwork. I also tried installing amon with clockwork's rom manager and failed there too. When it was time to reboot, there was no recovery. I booted into the bootloader and tried to enter recovery there, but it would just loop back to the boot loader. I flashed clockwork back in and I had recovery.

There is obviously something I did wrong eons ago when installing clockwork that made it refuse to take amon, but I haven't a clue what.

I'm going to nandroid my setup now, 2.2 stock froyo rooted deodexed with some bugfixes, and try fresh 3101. I sure do feel like a dog chasing it's tail though. I do occasionally see the wildly fluctuating signal strength but locking on the weaker signal quite often. I will report back my findings, hopefully soon.
[EVO 4G Android Development] Testrunner:
I tried your method over and over until I realized (at least I think) the code is ##786# not ##768# like you described.

Maybe this will help others reading this post.
[EVO 4G Android Development] taverentech:
Acht ****zen, you just reminded me that I'm messing with my Evo on Friday the 13th, wtf was I thinkin! I'm having a heck of time getting PRI back to 1.4x
[EVO 4G Android Development] Mediocrates:
Follow this linkhttp://xdaforums.com/showthread.php?t=705026 , scroll down about 5 replies from the OP, to albaholic's reply, and follow the instructions to install AmonRA recovery. The part where it says "then follow" is used after opening a command window and going to the directory you put the image and fastboot.exe in. This method works 100%

Sorry for answering an off-topic post, but I had an answer.
[EVO 4G Android Development] :
Sorry all...I did not realize that I was the OP...LOL!!! Somehow a few threads got merged by toast so I attempted an update as requested. If you have any info you feel should be there let me know or if you feel you want take over the OP that's cool also...:)
[EVO 4G Android Development] herbthehammer:
I'm getting off topic definitely now but the suggestion didn't work.

users-macbook:untitled user$ ./fastboot-mac devices

HT05SHL06273	fastboot

users-macbook:untitled user$ ./fastboot-mac flash recovery recovery-RA-evo-v1.7.0.1.img

sending 'recovery' (5032 KB)... OKAY

writing 'recovery'... FAILED (remote: image update error)

Same thing as last time. Now I gotta see if I can "fix" it again without it taking hours.

nm

I stumbled across 1702 and that went in no problem. Now back to chasing my tail with 1.40
[EVO 4G Android Development] herbthehammer:
I'LL BE DAMNED!!!!!!!!!

EUREKA, IT WORKED!!!!!!!!!!

What I did was full wipe with clockwork, then install fresh 3101. Then shut down and hold vol down and then hit power. Chose fastboot while connected to computer with usb. Went to amon ra recovery topic and read about the fastboot method from the fella a few posts down from the op, like someone suggested a few posts ago.

I followed the link in his reply to grab fastboot from htc (I'm using a mac but it shouldn't make any difference). Downloaded the 1.7.0.1 img and tried flashing but kept failing. For the hell of it, I fast forwarded to the last page of this topic and someone had a link to 1.7.0.2. I dl that and the flash was a success! Rebooted into the phone. Went to dialer and followed instructions from the quote at the beginning of my post, clearing 3 different caches twice each. Continued to follow the suggestion in the quote. After the reboot from amon, the profile and prl updated and I cancelled the firmware search.

I watched the signal strength as I was booting back into the phone. It would fluctuate like before and 3g would appear and disappear a few times in the beginning but it "seemed" like the phone was locking on the stronger signal this time. I waited until the home screen settled down and kept hitting next until I got the home screen. Went to settings and about phone and software, and sure as ****, the pri FINALLY updated to 1.40!

I'm going to nandroid this install and go back to my stock rooted 2.2 deodexed and see if the pri sticks or not....

So far, the signal strength is still bouncing around. It's settling on the weaker signal again :( I am getting read to reboot into recovery now to nandroid before restoring a previous install...
[EVO 4G Android Development] rjmjr69:
1.7.2 version is just a smaller sized version of 1.7.0.1 due to there being a heck of allot of Evo's having a bad sector leaving not enough space obviously lol. Not sure if any features are missing though I never could tell
[EVO 4G Android Development] herbthehammer:
I'm kinda erked that anon didn't seem to have the ability to browse the sdcard for nandroid and time, that they both needed to be in a certain place for the recovery to "see" it. I restored a previous nandroid backup and the pri stuck, so I'm glad that's over with. I'm still getting signal/tower bouncing and it doesn't seem so far to be in my favor. Chalk up one for me one the side of no obviously noticeable improvements. I might speed test but everything seems to be okay. I might be getting good speeds now also because it's 3am here now.
[EVO 4G Android Development] herbthehammer:
Stupid spell correct! Nandroid and roms or updates.
[EVO 4G Android Development] Albaholic:
I must've tried close to 20 times now. Oh well, I give up for now. Hopefully someone finds a way to dump it and make it into a flashable zip.
[EVO 4G Android Development] herbthehammer:
Bah! I was getting faster speeds last night with 1.34. I can't seem to get over 1.2 now when I was getting over 2's last night. Big sigh!
[EVO 4G Android Development] DataDork:
I can tell you i went from 1.2-2.0 speeds to 400k -1.0 with 1.34... after gettng back 1.40.. my speeds normalized and i was rocking back up to 2.0...
[EVO 4G Android Development] Sawawa:
Placebo effect.
[EVO 4G Android Development] JackDaniels7:
I just updated my pri and now i'm reading that you can't call or use web while roaming is this true or just a select few have this issue?

i will be traveling soon so this could cause problems
[EVO 4G Android Development] TorxT3D:
even with updated PRI, im still getting terrible speedtest results, from the app, and it thinks im located in texas, even with gps on.

testing with the website, it still thinks im located in texas, and testing the houston server gets me 1mbit down/.40mb up.

so, somethings wrong with the speedtest app (as we all already know), they need to fix it.

EDIT: xtremelabs speedtest is better 1150kbits
[EVO 4G Android Development] JG-1:
I'm gonna call Sprint in a few to try and get the MSL.

So if they ask what I need it for, just say I'm having a problem with the phone and need to reset it?

What if they ask what kind of problem? What should I say?
[EVO 4G Android Development] boliviano3:
I just asked, the rep put me hold & then gave me my msl.
[EVO 4G Android Development] smw6180:
If they give you a problem hang up, call back, and get a different rep. Worst case it takes a couple of calls to get it. But typically they don't give you a hard time, you just have to say, I need my MSL and they give it to you.
[EVO 4G Android Development] talktojer:
I tried over and over with clockworkmod and damage control 3.5..all day I worked with it, and couldn't get 1.40..eventually switched to RA...still no love..

I ended up doing a ##786#, and once it boots into the recovery and formats, instead of rebooting the phone I flashed Evo-Froyo-2.2-Rooted-Stock-Odexed-netarchy-signed.zip. This worked for me. I got 1.40 and restored my damage control rom...now im back to where I was yesterday rom wise and got 1.40 now too.

no real obvious improvements.
[EVO 4G Android Development] fldash:
FML. Dude, I've been trying 1000's of times with no luck... I tried the following roms:

Official 2.1 Rooted

Official 2.2 Rooted DeOdexed

Official 2.2 Rooted Odexed

Official 2.2 Unrooted

DC 3.5

I'm using Amon-RA Recovery.

No luck on any in OKC.
[EVO 4G Android Development] dan0412:
I have tried most of the recommended methods; no updated PRI yet; I am downloading Evo-Froyo-2.2-Rooted-Stock-Odexed-netarchy-signed.zip now since the earlier post indicated success with that ROM; will post results when done.
[EVO 4G Android Development] Kornsaq:
If you have any issues, just try their online chat support. Tell them you are getting the error 67 when trying to connect to the internet.

This is what I did and he gave me the MSL in the process of him walking me through the ##data#
[EVO 4G Android Development] xx1479:
I apologize, I fat fingered it! Did it work though?
[EVO 4G Android Development] fldash:
After over 100s of tries, varying signal levels and the following ROMs, I FINALLY got it in Oklahoma City.

Official 2.1 Rooted

Official 2.2 Rooted DeOdexed

Official 2.2 Rooted Odexed

Official 2.2 Unrooted

DC 3.5

I'm using Amon-RA Recovery. All those failed using many tries of both ##786# and ##3283#.

Then I read a post this morning that someone got it the first try with Fresh 3.1.0.1 and so I did a ##786# in my current ROM at the time (DC) and when it rebooted into recovery, I wiped everything, then flashed 3.1.0.1 and when it started up and activated, I checked and I had it.

I don't understand... this at all.
[EVO 4G Android Development] Systemfraud:
When me and my brother got our phones on release date the Guy mentioned a six digit # and gave it to my brother as he is the account owner, would that be the MSL or just another password?
[EVO 4G Android Development] dan0412:
It didn't update PRI.
[EVO 4G Android Development] howdyace:
Got it working. Took maybe 45 mins.

Mainly just d/l net's stock rooted rom and flashing it and then doing the wipe 2 different times and having it stick the final one.

I'ma happy camper guys.

And when I say wipe I mean using the ##786# method. and heres net's rom i used.....http://www612.megaupload.com/files/...Final-Froyo-Rooted-Odexed-netarchy-signed.zip
[EVO 4G Android Development] maxcala:
I'm fully rooted with Calkulins Rom,

I did the ##3282# six time but no go.

I did the ##786# 1 time and there it is. 1.40

Thanks to all!:D
[EVO 4G Android Development] skydeaner:
Tried both over 30 times and no go so far... still trying lol

Trying clearing everything, wiping, fresh 3.1.0.1 rebooting now......

negative, trying a couple more times, then killing myself lol.
[EVO 4G Android Development] josh s:
I has similar results. I tried ##3282# several times, flashed Netarchy Rooted 2.2 Stock ROM did ##3282# a couple more times still no luck.

Did ##785# and worked the first time!

now to restore my nandroid backup of CM6
[EVO 4G Android Development] pbarrett:
Just tried it here in Plano, TX.

Got it on the 3rd try using the ##786# method.

Using the rooted stock 2.2 with netarchy's kernel.

Restored NAND and I'm back in business, just had to re-apply my WiMax tweaks in the ##DATA# menu.

Now we'll see if it actually helps anything. won't know for sure till Monday when I'm back at work where it's been doing a lot of bouncing between towers.
[EVO 4G Android Development] taverentech:
Good grief, the only good thing I can say about this process is that it has a higher percentage of success than winning the lottery...

I couldn't possibly document here all the various things I tried and such, there would be very little use to it. Honestly, unless you can repeat your steps two or more times on the same phone off the same tower, I'm not sure we'll ever know for sure unless someone kidnaps someone in Sprints Tier 3 support or HTC ( I'm not really suggesting this ).

However, I did finally get it to work, after 2 days and about 6 rom flashes, a couple dozen ##3424#s and 10 or so ##786#s tries. In the end, the most important step is having NAND backup and persistance. It did finally work while running Fresh Evo 3.1.0.1 w/ updated radio and wimax roms. Once I got it to work, I used my nand recovery (greatest tool in the evo world) to recover all my settings.... interesting that the heart of the issue of updating the PRI is exactly why NAND recovery doesn't undo the PRI upgrade... classic. The funny thing was, I had just used ROM manager to flash RA recovery (since RA seems to work better with these procedures and I can switch it back to Clockwork after).... anyhow, it came up clockwork still, but it worked.... weird.

I'm in Scottsdale, AZ, and that probably matters a lot wrt to PRI updates. The phoenix area doesn't seem to be high priority for Sprint (no WiMAX).

My summary is its all voodoo and witchcraft because no one seems to really know EXACTLY what it takes to get any phone to the PRI update. In the end, this was more work than rooting my phone and getting froyo.

Be nice and be patient, I've read every thread and every article trying to find any useful information and it felt like high school... some folks need to grow up (just keeping it real!).

:eek:
[EVO 4G Android Development] taverentech:
With PRI 1.40_003 back on my evo 3.1.01 w/ updated radio, I'm getting improved and more consistent data speeds:

Using SpeedTest and running 5 tests from same server in Tempe (before and after PRI update), with phone in same exact location in my home, I'm consistently getting 20-30% faster downloads, which means I'm actually hitting 1.35Mbps download. Ping latency is considerably less. The signal (netmonitor) was -95db with PRI 1.34, now with PRI 1.4 it is -92db.

More importantly, with PRI 1.34, my speedtest tests were all over the place, ranging from .43Mbps to .95Mbps. With PRI 1.40_003, same tests under same conditions (albeit today vs yesterday and 8am MST vs. 11pm), are CONSISTENTLY over 1.2Mbps.

So, while your mileage will likely vary WIDELY. For me, using Fresh Evo 3.1.0.1, with updated radio (no wimax here), PRI 1.4, data speeds over 3G are consistently better.