yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] :
I hope this works....now with root a few more folks might need it. And it would make some sense if it had to be turned on...some roms had this option removed.
[EVO 4G Android Development] smw6180:
It hasn't made a difference for me either way. I had it on for the first 50 or so attempts, and off for the next 10-15. No update for me either way.
[EVO 4G Android Development] :
Thanks for the reply. If It were me I would accept the OTA FROYO then immediately do the ##786# PRI update prior to attempting 2.2 root. But that is just an opinion at this point...
[EVO 4G Android Development] smw6180:
Mmm. I'm already rooted and I have no desire to use any rooting method involving unrevoked. No offense to that team or people who use it. I've just seen too many problems with Unrevoked stuff in the past.
[EVO 4G Android Development] :
That whole s-off deal has me spooked. I mean isn't that leaving my phone wide open to being hacked by an outsider?
[EVO 4G Android Development] onelovekir:
any help would be appreciated...has anybody run into this problem like me?
[EVO 4G Android Development] :
I wish there was that magical answer for ya. The only thing I can say is that the RA recovery seems to wipe better and some are having to wipe twice to get the update.
[EVO 4G Android Development] creon100:
I'm attempting to try this on my phone rooted using CM6, but I can't get the dial codes to work. My previous experience with these codes was that the phone would detect them as you dialed them into the dialer, but my phone just sits there when I type the codes in showing ##3282# in the display and if I hit the send button it just rings and says it's an incorrect number. What am I supposed to be doing here?
[EVO 4G Android Development] :
you are not supposed to hit "send" both methods automatically send...##----# do nothing...

also a couple of roms were not allowing the use of ##'s...might be the rom you are using.
[EVO 4G Android Development] pdlboy:
Finally worked

I'm using straight Fresh 3.1.0.2. I did the 786 method a whole bunch of times with no success. I then did the following and it worked:

1. Follow 786 method until you reboot from recovery

2. When phone reboots, yank battery and remove sd card.

3. Power up phone, go through handsfree.

4. Done!

So it was removing the SD card that seems to have made the difference for me, though it could totally be a fluke. You could try removing it at any point, I just noted the point at which I decided to remove it.

As I said, possibly a fluke, but can't hurt to try!

Cheers.
[EVO 4G Android Development] rtsirois:
Must have been a fluke. Didn't work for me.
[EVO 4G Android Development] pdlboy:
That's too bad.
[EVO 4G Android Development] Rene2.5RS:
So after getting my phone to get the 1.40 update I too could not access data or make/receive a call while roaming.

I call Sprint today and they had me shut the phone down and then they told me to power up and do a PRL update and then a Profile update and now I am on PRL 60670 and can now use the phone while roaming for both voice and data.

So if you lose voice and data roaming when attempting this call Sprint and you can get this resolved
[EVO 4G Android Development] dirtyernie:
Didn't work for me.
[EVO 4G Android Development] dxearner:
When pulling the sd card, is there a chance that you corrupt the data on it if you pull from boot, or has it not mounted yet?
[EVO 4G Android Development] pdlboy:
Well, in order to pull the SD card you have to remove the battery, so the phone isn't on when you do. I just yanked out the battery when recovery rebooted, took out the SD, replaced the battery and booted the phone up.
[EVO 4G Android Development] dxearner:
Good point ahaha.
[EVO 4G Android Development] scolex89:
This worked for me on the first try after trying the ##3... method numerous times. Oddly, though, it didn't wipe the phone and I thought the 768. method did. I know I used 768 the last time because it was a different menu than I'd seen before. I pulled the battery out the second the phone actually went off and took out the sd card, put everything in, and turned it back on. It went through the prl update and stuff like with #3 but didn't go through first time setup and didn't wipe anything. This time, the PRI was at 1.4 though, finally.
[EVO 4G Android Development] dxearner:
I was on calk's and steelh rooted 2.2 ##786# many times no success...

Did this method, and first try and I am the owner of PRI 1.4. More people need to test but seems like this is producing pretty consistent results.
[EVO 4G Android Development] :
Hmm...Ok so when you "Yanked" out the battery did you have your tongue out like jordon...HAHAHAHAHA!!!! Just joking...:p
[EVO 4G Android Development] Jim M:
I tried several times before, and had no success updating the PRI. I finally did this and it worked for me:

Do the ##786# - reset - enter MSL - when the phone shut off I pulled the battery - drank 2 beers - left the battery out overnight - next morning put the battery in, turned on the phone it did the start up and activation thing, but it was a little different than it was in the past, low and behold PRI was updated 1.40_003

hth

~ Stay thirsty my friends ~ XX
[EVO 4G Android Development] smonme:
Finally got mine Bronx, NY using ##786# Method, I tried ##3283# for days and it never worked... I have also noticed no speed increases since using 1.40 still getting .18 mb/s which is pretty damn slow...
[EVO 4G Android Development] rancherochido:
Wow, first time go with newly rooted 2.2

Pri 1.40_003
[EVO 4G Android Development] trim81:
been trying for at least 4-5 hours now...dones everything 786 reset, flashed a NEW RUU stock rom, everything..

I am stuck on 1.34 and will not update to 1.40

(had 1.40 all this time, but used the new 2.2 root today and used the part #2 nand unlock method which dropped me down to 1.34)

this is frustrating, so far there is not a fool-proof method

ps- I am in los angeles area
[EVO 4G Android Development] dxearner:
Have you tried removing the sd card after rebooting from the recovery wipes (see a couple pages back)? I couldn't get ##786# to work on any rom, but this worked first go around.
[EVO 4G Android Development] karikian:
HELP

Hi, could anyone help?

I got stuck on 2.2 not root trying to upgrade the pri, and finally I was able to downgrade and root unrevoked forever... spent the whole entire day trying this method to get the pri update... both of them, read the whole forum as I tried it, and nothing yet... is there any other way, maybe a zip to flash, or what is the method people were using before sprint started pushing it? I am going nuts! I am in the Los Angeles Area

This is what happens, after ##786# or ##3282#, I get the handsfree activation, prl update and then firmware update which shows that there's no firmware updates available.

YES I AM ALSO TRYING WIPE 2X

PLEASE HELP ME SOMEONE!!!:(
[EVO 4G Android Development] karikian:
Similar is happening to me... and I am in the LA area... maybe they stopped pushing the updates to our phones in this area?!?!? Oh no!!!!
[EVO 4G Android Development] canteenboy:
Also in the LA area here. ##786# for about 2 dozen times with no results.
[EVO 4G Android Development] Zoheb318:
Over the last 10 days I've tried atleast 20 times a day by using the 786 and 3282 methods.

I tried the above method and my PRI was still 1.34. I tried again but with a slightly different method and it worked!

Here's what I did on Fresh 3.1.0.2:

1. NAND backup. I'm on the newest amon RA recovery

2. ##786# reset

3. In recovery wipe cache, dalvik, cache, dalvik

4. While still in recovery, pull the battery and let it sit for a minute or 2

5. Re-install battery and power up the phone. Even though they said no firmware was available my PRI was 1.40_003

6. NAND restore and enjoy your new PRI ;)
[EVO 4G Android Development] evohnoo:
Im in LA as well, with no update after trying about 10 times. I travel for a living, and will be in DC tonight... and am going to try the update. If it works, it could be, as someone else said, a problem pushing it around this area. Will check back in with results.
[EVO 4G Android Development] dirtyernie:
##786# Maters Reset:

1: Do a NAND Backup 1st...

2: Dial ##786#

3: Hit Menu

4: Press Reset

5: Enter your MSL 6 digit number

6: Phone will reboot into recovery mode

7: Wipe Cache/Dalvik x2

8: Reboot

The phone will go through handsfree activation and update the PRI to 1.40

If it did not just repeat the process until it does.

Worked for me today on 2nd try. Yesterday no workie...keep trying...I am in NY and might be when they feel like pushing.
[EVO 4G Android Development] bwillet:
I just can't get it to work, no matter where I am. Home (North Georgia), work (metro ATL), travelling (Grand Rapids x 4 different places, Indianapolis, Louisville, Lexington, Nashville), nothing works. Stock rooted, Fresh, DC, none work. I give up. Wonder if it has anything to do with the fact I have one of the original Google conference phones... Or just bad luck.
[EVO 4G Android Development] ryan2202:
not working so far...
[EVO 4G Android Development] onelovekir:
Ok now in theory, could I nand restore back to the old original root then RUU to 1.47 to get the 1.40 PRI and then would my recovery still be there? If so could I boot into recovery from the "volume down + power" and then select recovery and nand restore back to my 2.2 rooted ROM? If I restored fine would it carry the old 1.34 PRI back with the nand backup?
[EVO 4G Android Development] onelovekir:
I tried the other battery 3 times but I will try this one and get back with the results.
[EVO 4G Android Development] Rene2.5RS:
nand backups won't touch your PRI
[EVO 4G Android Development] karikian:
Tried too... no luck at all...
[EVO 4G Android Development] riz_o:
I was having the same trouble as well.. Kept trying over and over and it just wouldn't update.

I saw your method and tried it.

First I flashed the latest version of Amon Ra Recovery (v.1.7.0.2).

Then I did the whole ##786# thing and to my surprise... my PRI finally updated.. to 1.40_003.

Once again it pays to search and search the threads!!!
[EVO 4G Android Development] karikian:
Are you on fresh too? Where are you at?
[EVO 4G Android Development] riz_o:
I was on "HTC OTA Froyo 2.2 FINAL build 3.36.651.6 (Rooted) Odexed".

Updated to the latest Amon RA Recovery

Then did the ##786#.. updated my PRI to 1.40_003.

Now I am back on CM6.
[EVO 4G Android Development] long2know:
I had tried the 786 and 3282 at least twenty times with no success. I'm running EViO 1.1. I saw this method posted and got 1.40_003 on the first try!

Woot!
[EVO 4G Android Development] karikian:
Forgot to ask... where are you at?
[EVO 4G Android Development] karikian:
Where are you at?
[EVO 4G Android Development] karikian:
IT FINALLY WORKED!!! WOOT! WOOT!

Thank you very much... after so many tries, it happened as you said... no firmware... but checking the pri now, it's 1.40_003... Thanks! I will check the speeds now and let all know later...

JUST IN CASE ANYBODY WONDERS, THIS IS WHAT I DID:

1. FLASHED FRESH ROM 3.1.0.2, REBOOTED

2. ##786# reset, enter MSL

3. In recovery wipe > wipe cache, wipe dalvik, wipe cache, wipe dalvik

4. While still in recovery, pull the battery and let it sit for a minute

5. Re-install battery and power up the phone.

6. REPEATED STEPS 2 to 6 about 3 times

Even though they said no firmware was available my PRI was 1.40_003

I am in the LOS ANGELES area, AMON RA Newest Recovery
[EVO 4G Android Development] long2know:
I'm in Knoxville TN ..
[EVO 4G Android Development] dteze88:
Finally updated using 786 method. It just depends if Sprint is rolling it out in your area. I tried many times before. Germantown MD. :)
[EVO 4G Android Development] sidezero:
This also worked for me on Fresh 3.1.0.2
[EVO 4G Android Development] LearnIIBurn:
It's so wierd to me that mine has not updated yet. I've tried everyday less and less because it's so ridiculous. I'm on stock 2.2 unrooted. Been trying the ##3282# method over and over. Haven't tried the other way because that requires a wipe I believe. I'm in the Hollywood area. Guess I'm just gonna give up and root so I can use recovery and nandroid. I feel so silly wasting so much time for an update that I have no idea what it does. All I know is my 3G speeds are dirty slow...
[EVO 4G Android Development] karikian:
I was on your boat... it would not get updated no matter what I did... that's when they found out a way to root, I unrooted, had a hard time getting the update even rooted... I had to change my recovery to AMON RA, and ROM to fresh to get it working (see my post few posts back)... now I am free to use whatever ROM I want, including stock... I am a happy camper now!
[EVO 4G Android Development] auky:
Confirmed this is working!! woot! Got it in 2 tries.. first time i pulled the battery, i waited for less than 1 min with no success. The second time i pulled the battery, i went out for dinner, came back, pop the battery in, restarted the phone and i got 1.40. Thanks!!

btw, i'm using steel's deoxeded E.2 with netarchy 4.1.8 cfs
[EVO 4G Android Development] :
okay this battery pulling deal is getting more and more convincing...real close to shooting it up fronts.
[EVO 4G Android Development] smw6180:
Didn't work for me. Followed step-by-step, left battery out for 1 minute, then 2, etc, up to 10 minutes (this was on the stock deodexed ROM as well as Fresh 3.1.0.2), put it in, still on 1.34.

So it's not something that works for everyone, evidently.
[EVO 4G Android Development] xHausx:
The S-OFF you don't have to worry about, if anything happens it would be because an app took advantage of root access. When you allow that you are letting them do whatever they want with no holds barred, so be very conservative with what apps you give root access to.

I've already found a couple out there that want root when they can do everything they need to without it.
[EVO 4G Android Development] riz_o:
Rocklin, CA
[EVO 4G Android Development] alafferty:
I have tried this process about 5 times with no luck. I am in Overland Park KS.
[EVO 4G Android Development] alafferty:
i tried searching but couldnt find anything on this. Has anyone tried going to the sprint final release not rooted and can get 1.40_003 right away? If so then have you been able to root your 2.2 and maintain 1.40_003. I am thinking about doing this to see what happens if no one else had reported doing it.
[EVO 4G Android Development] smw6180:
Nope. because once you root the thing you use the engineering hboot, which drops your PRI back to 1.34.
[EVO 4G Android Development] alafferty:
Figured as much. I had 1.40_003 at one point and hosed up my phone so i had to re-root it and lost my 1.40_003 due to the hboot. Thanks for checking my thoughts.
[EVO 4G Android Development] bluediablito:
how many people actually updated there prl with clockwork?

and why is it so hard to update it?

when i first got my phone sprint walk me trough these steps and it updated without any problem.
[EVO 4G Android Development] karikian:
Sorry to hear? Do you have the latest AMON RAA Recovery installed? Latest radios too?
[EVO 4G Android Development] bluediablito:
hello just wondering would i get lucky if i hit update prl and it updates?

or should i keep on trying ?
[EVO 4G Android Development] Josh H.:
Pretty sure this has NOTHING to do with towers/location.

I tried a few dozen times over the course of a few weeks in Tucson and thought the towers were the problem. I was wrong.

Tonight I made a bunch of changes and BOOM! New PRI.

I...

-started with Fusion 2.5 + Clockwork recovery

-replaced clockwork recovery with Amon RA 1.7.0.2

-##786# method with battery pull after wipes, no dice

-flashed Fresh 3.1.0.2

-##786# method with battery pull after wipes, no dice

-##786# method, wipes, and clicking "reboot" within recovery - BIG DICE

So, that's how I got 1.40_003.

Things I think do NOT work:

-clockwork recovery

-##3282# method

-nothing to do with towers/location

Things I think DO work:

-Amon RA recovery

-Fresh ROM

-##786# method

Edit: by the way, my speed tests are OFF THE CHAIN with this new PRI. Twice what I was ever getting before in the same location. :)
[EVO 4G Android Development] smw6180:
OR it could be that the PRI was recently pushed to your local towers. ;)

There's entirely too much randomness in what works/doesn't work for different people. There's not any single 'standard' way of getting a PRI update. That means that it's more than just what ROM you're on, or how many times you pray to the Sprint gods, or what kind of rain dance you're doing.
[EVO 4G Android Development] godfirst:
Once I started over with no theme and just reflashed fresh 3.1.0.2 full download and did the handset activation it updated to 1.40pri
[EVO 4G Android Development] alafferty:
yep i am using the latest AMON. I have tried so many options and tired all sorts of things. I am not sure it has anything do to with Towers or location either as i was out of town in Wisconsin and tried several of these with no luck. Ill just keep trying and it will catch at some point. I have 4G where i am at in fact i have really fast 4G to the tune of 8mb down and 1mb up so i am not trippin too much on the PRI as i dont think it can get any faster than that. Its more of just want to have to say i do :)
[EVO 4G Android Development] chummer360:
GOT IT!!!

Ok, Just did it. I'm running AVA V6 with King's BFS5, I'm in Huntington Beach Cali. Here's what I did.

NAN BACK UP

##786#

WIPE

REBOOT

WHEN IT START THE HANDS FREE ACTIVATION (I CANCLED IT, THE SCREEN WILL STAY DARK, I PULLED THE BATTERY)

REBOOT INTO RECOVERY AND RESTORE AND REBOOT

IT WILL GO THROUGH THE UPDATE PROCESS AGAIN, LET IT DO ITS THING

CHECK THE PRI

So that's how I got mine, about 10 minutes ago.
[EVO 4G Android Development] godfirst:
+1 same here but instead of Ava I have fresh 3.1.0.2
[EVO 4G Android Development] sablesurfer:
I have been unable to get in home town for last two weeks, just spent a week in Atlanta (Dunwoody area) and tried both ways at least 10 times a piece. Nuthin', nada, zilch.

I aint getting any love.

(Oh, the Atlanta area I was bouncing from tower to tower to tower all the time, even just sitting in one room and I even tried from airport so this was easily done off of about 5 locations going by the town name it listed in the clock.)
[EVO 4G Android Development] :
This is exactly what I did at first...wife took the OTA...ooops!!! Was bugging me about the PRI so I would periodically troubleshoot it...was watching the football game and said what the heck...did a ##786# and got it first try. Was so happy and in my rush to post it...missed a 97yd return play...:mad: LOL!!!

Anyways, Now completly stock I did the root method by Dan Wager and now the proud owner of a stock rooted phone...even down to the HBOOT 0.93.

I am saying this because inlight of the new root access obtained this OTA option to maybe inhance your PRI update effort might be a better option now or at least a safe avenue to explore.

Thanks, Hopes you get it...
[EVO 4G Android Development] raybudd:
This method worked for me on the 2nd try on Calk's Froyo rom w/ King's kernel BFS #5. I'm sure it was the nap I took while the battery was out the 2nd time!
[EVO 4G Android Development] Josh H.:
Forgot to mention that I also modified my rain-dance to au-natural right before the last reboot ;)

Good point though... there isn't really enough evidence to say for sure one way or another, but it's my gut feeling that technique has more to do with it than tower location.
[EVO 4G Android Development] smw6180:
OHHHHH. Well why didn't you SAY so. That makes all the difference. Thanks, gonna try that out now! ;)
[EVO 4G Android Development] misterneums:
Confirmed to work for me. I'm just Northeast of Madison, WI. Had to swap to a stock rom to get it but I'm now the proud owner of an EVO with the 1.40 PRI.

=)
[EVO 4G Android Development] Jim M:
I think the biggest aid in getting the PRI update is when you do the ##786# is to pull the battery when the phone shutsdown. Leave the battery out for a while (30 minutes or more) so that the phone is off the grid so to speak... when your phone boots up Sprints network sees it new and the FOTA gets pushed to your phone.
[EVO 4G Android Development] SharkUW:
I'm about to try this in Madison, but it's worth noting that the battery wouldn't need to stay out. Just leave the phone off after you put it back in.
[EVO 4G Android Development] Razgriz:
Weird. I just did that verbatim twice and still I'm stuck on 1.34. Ugh.
[EVO 4G Android Development] GumboChief:
Failed for me with that process, too.
[EVO 4G Android Development] :
HAHAHA...you guys are killing me...:o I gots a 50/50 on "Yanking The Battery Out" so I am gonna try and squeeze it in as a possible can do in the OP. Now like I said before if you have to hold your tongue out like Jordon when you yank-a-do then I am not responsible for the biting of one's tongue...:p LOL!!!
[EVO 4G Android Development] smw6180:
Well for the past 2 hours I've had my battery out. Still on 1.34. So...*shrug* I still say it's random, or tower dependent.
[EVO 4G Android Development] YoungAceAtlanta:
Wow i can't believe this post is still on going..

Why don't you all just upgrade to the 2.2 official version and lose root. then use the guide to root 2.2. then Nandroid back to whatever rom you was using AFTER the Sprint 2.2. rom updates your pri and you root your phone again.
[EVO 4G Android Development] smw6180:
Because some of us refuse to use Unrevoked due to past issues with their stuff? Now if that can be done WITHOUT using Unrevoked I might give it a shot...but as far as I've seen you need Unrevoked to do it.
[EVO 4G Android Development] :
Ya I am with ya for sure...might even be a difference if you try wifi vs 3g. I know that the Voice Mail update I just got would only let me get it when I was wifi...:confused:
[EVO 4G Android Development] smw6180:
Whereas I had no problems downloading that on 3g.
[EVO 4G Android Development] SharkUW:
2.2 doesn't update the pri...
[EVO 4G Android Development] YoungAceAtlanta:
So you mean to tell me Even if someone completely started over. Like they got a brand new phone. using the sprint RUU or w/e and update they hboot.. they still won't get the pri update??
[EVO 4G Android Development] SharkUW:
Potentially. But not necessarily.
[EVO 4G Android Development] smw6180:
The hboot drops to .76, which is the engineering hboot. PRI is tied to the hboot version (That's a good point SharkUW, i hadn't thought of it)...so even going back to an OTA once you get 1.40 you won't keep it. The rooting method downgrades hboot .79 (I believe it is) to .76 and you go back to 1.34 during that process anyhow.
[EVO 4G Android Development] :
Simple root is probably a thing of the past...as it sits...unless updated that is. It will just have you going in circles now. So far the unrevoked root method looks pretty stable but I don't care what you say that S-OFF it gives will always spook me...
[EVO 4G Android Development] misterneums:
I pulled the battery for like 2 minutes and then it popped up. Had to do it 3 times before it stuck.
[EVO 4G Android Development] smw6180:
mmm. Yeah. Technically they say they have a way to turn that off but...*shrug*
[EVO 4G Android Development] Razgriz:
I tried like 4 or 5 with the same result. The only discrepency, now that I think about it, is when I cancel the hands-free activation, it doesn't go to a black screen...it just goes to home.
[EVO 4G Android Development] GumboChief:
Mine also goes to home.
[EVO 4G Android Development] SharkUW:
Same. Mine jumps to home.