yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] bigsalot:
Ok this is gonna sound crazy but its the truth. I live in suburbs of Detroit and was trying like hell to get the PRI 1.4 update on my wifes rooted evo. It needed to be un-rooted for service because of a charging issue. After like 20 ##3283#'s and no luck I started doing ##786#'s and got PRI 1.4 after like 4 attempts. After getting PRI 1.4 I started the un-root process on her phone, but couldn't get the RUU to flash. I did some reading and found I needed h-boot 0.76.2000 and the ENG build, so I (Bonehead move) simplerooted the phone I had just got PRI 1.4 on.

**Face Slap**

Thats not the crazy part...

Now, with a nearly un-rooted evo I started doing ##786#'s to try and get PRI 1.4 back. I tried at least 50 times from 10 different cities between home, work, and every in between with no luck. After 2 days of messing with it gave up for a day, and start trying again a day later. After about ten tries I was ready to give up again, but I was in the middle of an attempt when I had to run upstairs to remove a baby gate from the hallway. I took my phone with me and let the activation, prl, and firmware checks run while I was messin with the gate. I checked the results and it got the PRI 1.4 update on my wifes now un-rooted evo. So.....I started trying to update my PRI on my rooted evo while at work, on my way home, and while sitting on the couch downstairs, about 30 times in all. Then I said, well **** maybe it will work in the hallway again. NO BULL****, 1ST TRY IN THE DAMN HALLWAY!

So either I have a damn PRI 1.4 wormhole in my hallway or maybe its simply the altitude giving a boost in signal strength. Both hallway updates had six bars when they updated, my first update was also upstairs but in a bedroom not sure on the bars. But, either way its some crazy ****, and gives credence to the signal strength theory.

So in short:

3 PRI 1.4 Updates recieved.

0 for 100+ Update attempts at ground level at home and around Metro Detroit.

3 for 3 Updates recieved at home, all on the second story of the house.

All at or nearly at full signal.

Both rooted evo PRI 1.4 updates had ROM - HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed by Netarchy, the stock radio, and RA Recovery. I used the ##786# method and did wipes in RA Recovery before reboots.

The un-rooted evo PRI 1.4 update was done using the ##786# method and standard rebooting (no battery pulling bs to do wipes before reboots).

Hope this ramble gives someone hope, help, or both.
[EVO 4G Android Development] churchwin88:
Dude, seriously what is your address because I am literally on my way to your house.

I have been trying like crazy the past 3 days here in Indianapolis with no luck at all. I have done like 60+ attempts with both methods all over freaking town with no luck
[EVO 4G Android Development] scottspa74:
Hahahaha. My sentiments exactly. My first thought: can I buy a ticket to the wormhole?

Man, I have tried every combination of kernel (even stock) and netarchys final odexed ROM, and wipe in recovery, no wipe in recovery, ##786, ##3282, ...etc. Every combination I could muster. What strikes me is, people keep sayin how they got it on nets ROM 'first time', that's the Rom I've been using the WHOLE FRIGGIN TIME! wtf?!

I think I'm gonna try to 'update profile' before trying again, and see if that has any effect. Or ill find the highest mountain I can, as per bigsalot ;)

Fun story bigsalot, entertaining, thank you.

Oh, on a serious note, you say when you got 1.40 it downgraded your hboot to 79.0000? I'd really like to know. Thanks. cuz I thought hboot79.000 meant you couldn't have a custom recovery. (forgive me , still a bit new to Android)
[EVO 4G Android Development] shafter09:
For cereals, we are all retarded. Try explaining any of this to anyone anywhere and they wont talk to you anymore.

I'm on my 10th try *checking pri*... damnit! 11th try
[EVO 4G Android Development] scottspa74:
Yeah, my coworkers and family avoid me the last few days. It's funny, before this thread, there was another one about this. I thought it was uninformative, but totally amusing, watching how obsessed some of em got. Guess I just joined the club.
[EVO 4G Android Development] dogbone414:
When I did this I can't do any thing when roaming call send text nothing how do you fix this.
[EVO 4G Android Development] lamboh:
didnt work the 50+ times i tried with clockwork....786 and 3282 method...flashed ra and got the pri...( doing the full wipe) factory reset method......)lost my ra nand somehow.(do not rename RA nand's if so it will fail) so had to flash back clockwork..but found an old clockwork nand...that worked

word to the wise...make backups of backups...
[EVO 4G Android Development] pgonzo2k:
finally .. i got it to update... was trying all day, i had to update RA recovery to the latest one... hope this helps....
[EVO 4G Android Development] Negrito:
****! maybe thats my problem... Where is this 'latest' Amon RA?
[EVO 4G Android Development] Dougie2187:
I tried this.

http://xdaforums.com/showthread.php?t=705026

But it didn't work for me, just so you know. I've tried like 15 times today.
[EVO 4G Android Development] :
There does seem to be a greater success rate with the latest RA Recovery....I should probably update this in OP.
[EVO 4G Android Development] akarol:
How does one update the RA_recovery?!
[EVO 4G Android Development] xHausx:
Still can't get mine to update and am using the new amon-ra, Ive been trying a few time every other day since this thread started
[EVO 4G Android Development] akarol:
No update still here in Orlando, FL. Should be going down to Miami soon. I'll try then. Heard some people getting it down there already.
[EVO 4G Android Development] lacrossev:
Went ahead and tried this method. First i got my MSL with CDMA workshop, then I flashed RA recovery and did a nandroid. Flashed a clean copy of Fresh 3.1.0.2 with the newest wimax and 2.15.00.07.28 baseband. First i tried the 2nd method without the factory reset, but that didn't take so i tried the factory reset method. The update instantly took and now i'm 1.40 pri / 60670 prl on CM6 8-21 nightly.

Haven't seen a dramatic difference in speed, but i'm posting just as a confirmation of the conditions where my PRI update worked. And btw i'm on 003 hardware using toasts's complete unlock
[EVO 4G Android Development] Stalte:
Found a solution??? Maybe.

-Deleted-

Did some research and some reading and I was wrong
[EVO 4G Android Development] smw6180:
That's a hex-edited file showing 1.40. You're still on 1.34. All they did was change the number that's displayed.
[EVO 4G Android Development] diabloazul126:
I believe that was just a mod that changed what the phone said... so you still technically have 1.34 but your phone labelled it as 1.40.. I think.
[EVO 4G Android Development] SouL Shadow:
Congratulations, you found the hex edited zip that makes your pri *look* like you have 1.40 from the "[Partial GUIDE] Flashing Images to EVO Partitions" thread. That's been around a while, really only useful if you needed to return your evo without any evidence of having been rooted.

-SLS-
[EVO 4G Android Development] Stalte:
Yep but now at least I can mess with the tech at Sprint who has a rooted Evo that he has been trying to update as well :p
[EVO 4G Android Development] :
Ok now that is fuuny. Could you post a video of that....just joking.
[EVO 4G Android Development] Lostx:
Still trying to update prl.. by the way MSL Reader from the market gives you your MSL very fast

sent with my CM6 N8/2 EVO
[EVO 4G Android Development] :
Thanks Lostx....original post updated to reflect this.
[EVO 4G Android Development] Jfree3000:
Tried at least 20 times here in the stockbridge/mcdonough/rex area here in Georgia with no luck.
[EVO 4G Android Development] Lostx:
Does 786 wipe the SD card too?

sent with my CM6 N8/2 EVO
[EVO 4G Android Development] churchwin88:
No, it does not but you should make a backup on your desktop/laptop just to be safe though.
[EVO 4G Android Development] Drybonz:
Neither method has worked for me... tried both a lot of times.
[EVO 4G Android Development] tinpusher:
Mine finally took in the DFW area.

I did something during a 786 or 3282 that stopped Hands Free Activation from working about a week and a half ago. It failed every time, and I had to activate manually every time using Sprint Zone (*2 dial).

I figured it was something during the Hands Free Activation that was pushing the PRI, and mine wasn't working so I called Sprint. Sprint couldn't get Hands Free Activation working either. But they did have me do something I hadn't done before. I did ##786#, reset and reboot. After reboot I entered ##(my msl)#, Edit Mode, and my MDN and MSID were weird #'s like 000000367. She had me enter my actual MDN and MSID then reboot. Hands Free activation failed again and I went to Sprint Zone (*2 dial) and pushed "Activate Phone". After that I had the new PRI. My PRL is still 60662, though.

I don't know if any of this is actually relevant, but this is what I did and got the PRI.
[EVO 4G Android Development] :
Ok so you just took every things bigger in Texas to a whole new level...LOL! I'm still trying to figure out exactly how you got it...
[EVO 4G Android Development] aamikam:
interesting... sounds like u basically deactivated your phone and then reactivate it.

enetering the msid and mdn is basically how u would activate a phone and if those values r not right then the phone should technically not work right.

u might be on to something here... although my opinion still tends sticks to the towers theory.
[EVO 4G Android Development] SnoopDawg:
I tried the 3282 about 10 times, no luck. Then 786 worked after the 2nd time in TN.
[EVO 4G Android Development] alafferty:
The only thing i know about this is if you MDN and MSID numbers were mostly zeros then your phone got deactivated and something was not right with your account on sprints side. What should happen is when your phone tries to contact the network it hands the network its ESN number which goes back to your account and sends down to your phone your MDN and MSID automattically. Something was broken with the auto provisioning part of your account. The sprint rep having you manually put in your MDN and MSID is kind of like putting in a static IP address because your DHCP server was broken.

Still interseting though after you got that info back into your phone you got the update. I have a feeling it is something to do with the towers and account combination of some kind. We have about 1200 phones on the sprint network so i am very up to speed on the provisioning process of a device. I have an email into my tech team at sprint about this to see if they can tell me anything. So if they come back with something ill make sure to pass it on. I can only hope.
[EVO 4G Android Development] SouL Shadow:
Wow, that's a lot of phones. What kind of company do you work for? I work for a trucking company and we have about a hundred Nextel handsets.

-SLS-
[EVO 4G Android Development] conflikt:
Strange bug, went to dial a number and my phone come up with a Verizon network error. I did not receive a single call all day or text messages. I noticed this then restrtrd my phone. After restarting I got slammed with messages. Anyone have this same problem?
[EVO 4G Android Development] alafferty:
I work for a conferencing company and we equip most all of our employees with phones and sprint is our primary carrier. We make blackberry apps so that is a bulk of our phones. I am in IT in our company so I am the main tech guy between sprint and my company so i have learned alot about the networks and about the handsets. I am hoping my inside team can shed some light on this PRI thing this week. I am more interested in what exactly is does. I have seen some posts about what peeps think it might be or and maybe they are right i dont know. Its crazy how crazy we all get on a little thing like this. I keep telling myself its part of the trade off for having root access which out weighs an update PRI :)
[EVO 4G Android Development] elingreen:
tried a few times last week, nada.

tried a few times this week, nada.

tried again tonight (always 786) and bam, 1.4.

this was done on fresh, and it did break recovery so that i couldn't nandroid back until i reflashed it.

this was in westchester los angeles.
[EVO 4G Android Development] :
This document was posted by another member but looks pretty official as too a clue:

http://www.cdg.org/_deleted_files/members-only/teams/ghrc/docs/in_dev/product_release/ghrc%20pri%20baseline%20for%20review%20in%20ghrc%2007%202005%20mtg.doc

It is basically a set of CDMA PRI minimum requirements. Now just what Sprint/HTC actually has implemented into our software from this is a mystery.

Add this to your pile of what the heck is it stack...LOL!!!
[EVO 4G Android Development] xHausx:
Nice find my friend, I searched their website for PRI and found this one too (page 75):

http://www.cdg.org/_deleted_files/members-only/teams/ghrc/docs/cdg doc 90 ghrc base 1.06.doc

PRI stands for Product Release Instructions and is apparently formatted for either Excel or XML.
[EVO 4G Android Development] scottspa74:
Yeah, having a hard time imagining this as amusing
[EVO 4G Android Development] chaofun:
Yesssss! I got it after a billion tries. Dunno if it's coincidence, but it finally worked after I flashed the stock odexed rom from netarchy.
[EVO 4G Android Development] chino0131:
Worked perfectly today in DC. Running latest Fresh.

EDIT: Tried it on my wife's EVO Runnin fresh and KiNgxKernel #4. Wouldn't take after 6 tries. Wiped everything, reverted back to kernel on Fresh Rom, and it worked perfectly first time. DO not know if this is just cooincidence.
[EVO 4G Android Development] brnail:
I don't know what causes this to work or not work. I have done 786 and 3282 about 100 times over the last week. I thought I had tried every trick listed here and was about to give up. I was trying 786 one last time while watching TV and decided to bury the phone in the sofa while it did it. The PRI updated on Calk's Evio ROM. I didn't even care about using the stock ROM to update anymore.

So, logically, either you need to bury the phone or be at the point where you simply don't care anymore if it updates, and then it will. I figured this out. :D
[EVO 4G Android Development] BadBoyNDSU:
4 times using 786 did it for me.

Fresh 3 and netarchy kernel.
[EVO 4G Android Development] nkawal:
did you lose anything by using the ##786#? I see it says to wipe cache and davlik, but not data. Just wondering if anything is lost.
[EVO 4G Android Development] dstorm:
Worked in Nebraska today. I was in Papillion area just south of Omaha. wipe method, 2nd try.

Edit:ouch now my speeds are terrible.
[EVO 4G Android Development] stinkbud:
786 told me i will lose everything, and I did.
[EVO 4G Android Development] Dougie2187:
Me too, but that's what step 1 is for (the nandroid backup).
[EVO 4G Android Development] ruudymike:
i was trying to get the pri update for days now, tried few different roms, anyways i flashed RA latest recovery this morning and on the first try using 786 method and fresh rom it worked
[EVO 4G Android Development] sturmen:
Fresh + Amon_RA = 1.40_003

Tried ##3283# many times using SteelH's rooted stock + Clockwork, no luck. This morning, I flashed the latest Fresh and Amon_RA, and ran ##786# and it worked on the second try. Restore from nandroid backup, and voila: success!

I've been skimming through, and people seem to have greater success with ##786# on Fresh, so I recommend that to people who are having trouble. Oh, and Amon_RA recovery.

I'm in Durham, NC (a 4G market).
[EVO 4G Android Development] Sporkman:
still no luck here in ohio :/
[EVO 4G Android Development] MTKnife:
I was looking at these two documents, and I noticed something.

From the first one, one of the required PRI values (sorry for the lack of formatting):

This, presumably, is the splash screen, which, as we all know, is a file of its own that can easily be replaced on a rooted phone.

This is from the second document:

Maybe the reason no one can find the PRI file is that the PRI isn't a file, but rather an external document describing the phone's default settings. That still leaves the question of why the phone itself lists a PRI version number, but that version number may just be a summary of what the phone's default settings are supposed to look like (and which is pushed out to the phone when an update that changes those settings is pushed, at least in theory), which would mean that it would be possible to "update the PRI" simply by changing all the settings on the phone to the new settings. Indeed, it could be that the file going around with the PRI number hex-edited to the new one is exactly the same (when it comes to the PRI) as the real one.
[EVO 4G Android Development] Matt H:
Worked the very first time for me. I used the ##786# method.

Fresh 3.1.0.2
[EVO 4G Android Development] aleksis2010:
anyone had success in Tampa fl? I've tried like 100 times already and NADA.
[EVO 4G Android Development] netmasta10bt:
Same boat. Probably 25 times so far. It's probably still getting pushed around the network.

On DC3.5, RA recovery doing ##3282#
[EVO 4G Android Development] :
I would have to agree that the PRI is simply this: Product Release Instructions and it went something like this:

To HTC from Sprint: Yo!!! We wanna get some phones from over there..see? Here is The PRI...Product Release Instruction Document so you won't screw us up. Each Instruction will have one of four categories of requirements as follows:

1: (M) Mandatory	The handset must support that characteristic in order to achieve approval.

2: (HD) Highly Desirable	It is highly desirable and recommended that the handset supports this characteristic. This feature may become Mandatory in subsequent versions of the document. Supporting this characteristic will be valued in the commercial promotion of the terminal.

3: (O) Optional	It is left up to the manufacturer whether or not the terminal supports this characteristic. The handset may support this characteristic.

4: (D) Discard	The manufacturer should not support this feature or function.

I may be wrong but I believe it is simply a document that resides on our phones that not only says we are keeping up with global standards but tweaked per Sprints PRI request to HTC. I don't believe it has any thing to do with the overall function of the phone but more a comfirmation of the standards placed within it.

Uh...my 2 cents.
[EVO 4G Android Development] v_lestat:
i tried 9 times using Calkulins (sorry i know i am mispelling your name) EViO 2.2 ROM.

it wouldn't go.

i restored an old backup of stock rooted 2.2 deodexed, did the ## wipe once and it took....

hboot i dont think so... but cant say even though calkulins and the stock rooted 2.2 had the same hboot i think.

rom model and version... i believe so..

what i found odd during this hole process was that EViO was keeping all my apps and stuff..... and i was never asked to setup my google account and location services, it just took me right to the dashboard.
[EVO 4G Android Development] freeza:
me too, in socal.
[EVO 4G Android Development] jtc442:
Finally!!

woo hoo, after about 10 tries, and going from calk rom, to dc, to stock htc rom, and several times on all of them, and just about ready to throw my evo, well, gently place it down and give up, i was reading this forum, since the other got closed, as i was rebooting, and sure enough, there it is!!!! thanks to you all, even gonzo or whatever!!!
[EVO 4G Android Development] edtate:
This thread is going to have the same fate as the one Goonzy started because of petty arguments as yours. If you can't respect his grammar, don't read it/ignore it/mentally correct it. If you have a problem with him, work it out through privates, emails, whatever. This is not the place; keep it topical.
[EVO 4G Android Development] Varo210:
Once I flashed back to 2.2 stock rom, it took twice. Don't ask how stuborn I was before I flashed back. :/
[EVO 4G Android Development] webs05:
Anyone with Unrevoked Forever will likely need to follow this thread to update their hboot first:

http://xdaforums.com/showthread.php?t=752832

Then the usual worked great for me. Just go to a 2.2 rom based on a Sprint stock. Make sure amonra recovery is running, I used Rom Manager to flash it. Go to dialer type "##786#", hit menu, reset. Then wipe twice, dlavik twice. Boot up, go through the usual. And bam! It works.

After I put the hboot in there it only took one try for me. Also after installing the hboot I didn't need to wipe data or dalvik or even run ##786#. It just started reactivating for me.

Good work on figuring things out everyone.
[EVO 4G Android Development] nukedukem:
Thanks for adding your experience op.

With that being said, I can't believe the hysteria that ensues when a non developer person discovers something to help everyone else out. Chaos baby!!!

Dbags are flyin' first class around here "jizzen" on unsuspecting posters as they try to regain order and determined who is in fact the supreme master forum freak.

I love chaos!!!
[EVO 4G Android Development] yutlin:
Got it on my 5th try.

More importantly, I forgot to do the wipes in RA when it worked so you can all probably skip that step if you like.
[EVO 4G Android Development] :
what different does it make from 1.34 to 1.4?
[EVO 4G Android Development] firsttimer44:
14th try on fresh 1.0.1 and I finally got it...hope I see a diff because my 3g connection was a dog.
[EVO 4G Android Development] woofermazing:
Are you all wiping the cache and dalvik twice each? I was only wiping once and it still took. I would not be shocked if it isn't even necessary, especially since non-rooted phones are able to update. Wiping each twice just sounds like voodoo witchcraft bs.
[EVO 4G Android Development] enigmatl:
Okay. To clarify, the first step is that we need to be on a rooted stock rom, is this correct? i.e. no ava, no fresh, no OMJ, but rather the latest stock rooted rom? Is this correct?
[EVO 4G Android Development] PhantomApollyon:
I tried it 10+ times on DC3.2.3 and it didn't work so I flashed stock 2.2 rooted and it worked on the first try.
[EVO 4G Android Development] adenosine3p:
I didn't wipe it at all. It didn't even boot into recovery after the factory reset.
[EVO 4G Android Development] freeza:
Which one?
[EVO 4G Android Development] minieod:
Anyone know how to do this while on cyanogen?
[EVO 4G Android Development] edtate:
Alright, as soon as my nandroid backup is finished, I will give this a try :). I took screenshots of some speedtest.net tests @1.34 and will compare those to what I get on 1.40. Hopefully the results live up to the hype 1.40 has garnered lol.

p.s- If anybody has a problem with speedtest.net, please refer me to another or better testing website; I've heard speedtest is pretty unreliable.
[EVO 4G Android Development] appzattak:
and what is the real benefit of that PRI?
[EVO 4G Android Development] ranmasaotome510:
out of curiosity, of which one of these revisions by steel did you use?

1) HTC_OTA_Froyo_2.2_build_3.26.651.6_(Rooted)_Deodex _signed_Rev.E.1.zip - NO DATA WIPE

2) HTC_OTA_Froyo_2.2_build_3.26.651.6_(Rooted)_Deodex _signed_Rev.E.zip with stock Sprint boot animation - NO DATA WIPE

3) HTC_OTA_Froyo_2.2_build_3.26.651.6_(Rooted)_Deodex _signed_Rev.E.zip with stock Sprint boot animation - DATA WIPE
[EVO 4G Android Development] jschulman:
On CM6, wiped and put down a fresh copy of DC 3.5.

This worked on the first try in Chicago, IL. On step 4, it reboots and WAIT -- I waited about 60 seconds or so for the Handsfree Update to start. Be patient.
[EVO 4G Android Development] Lostx:
This is interesting. I've changed my splash screen and haven't successfully updated the pri. Has anyone with a custom splash been able to update?

sent with my CM6 N8/2 EVO
[EVO 4G Android Development] BAleR:
Can you upload the splash screen? Is it flashable??

I have tryed everything and cant get it to work, I have a custome splash. Its the only thing i havent tryed yet please help