Downgrading to 3.39 - Testing

[serfboreds]

After reading somebody's post recently that 3.39 had a better lock I thought to try it out in comparison to see for myself (mostly to dispute).

I tried to flash this .nbh file here (http://forum.xda-developers.com/showthread.php?t=392140), but it wouldn't take. I tried reformatting the card, renaming to ensure it wasn't TITAIMG.nbh.nbh, re-extracting and renaming, everything I would do for it to work in the past.

I even tried all of the above with 1.20 bootloader with no success. Is there something preventing me from loading this particular file from where I am (3.2.2 with 3.42.30)? I would like to compare for myself and have the ability to flash from whatever to whatever.

Is this a bad file? I thought it used to work fine.

[gc14]

Try this one.

http://www.cinconet.org/titan/radio/Titan_Radio_3.39.10.rar

[serfboreds]

Try this one.

http://www.cinconet.org/titan/radio/Titan_Radio_3.39.10.rar

I can always count on you gcincotta (I put your throwback jersey on today).

I will post with results.

[serfboreds]

Ok, so 1.20 won't update back to 2.40, not sure why but it recognizes it in activesync with the OS, goes through the cmd window ok, but has an error in the RUU stating that there is a problem with the connection.

The only thing that I can think of is that one time I began the nueSPL update but did not finish as the card that was in was a sdhc so I cancelled out before it asked me to commit. Not sure why that would have been a problem as it didn't complete the flash and never showed the bootloader at 2.47, it has always been 2.40.

Any thoughts on how to clean up the bootloader?

Should I go ahead to nueSPL 2.47 (FYI I am on Verizon)?

Not really worried at this point, but would like to get at least 2.40 back on the phone for the next ROM/Radio upgrade. This could be why radio wasn't flashing, right?

[gc14]

Wait, so you have 1.20 on?

[serfboreds]

Wait, so you have 1.20 on?

Correct, wanted to rule that out and have had no problem upgrading back to 2.40 until now.

[gc14]

Are you trying to update to 2.40 or 2.47?

[serfboreds]

Are you trying to update to 2.40 or 2.47?

I have heard that I should stay away from 2.47 for now, but if I cannot load 2.40 I am game. I wonder if I have some freaky bootloader situation due to the mix of 2.40 and some effect caused by the loading of a temporary 2.47 SPL.

I think my preference would be 2.40, but I would still like to test radio 3.39 eventually. I definitely want to get out of 1.20 at this point.

[gc14]

I'm running 2.47 with no issues. In fact, it's performing better....

[serfboreds]

I'm running 2.47 with no issues. In fact, it's performing better....

That is what DCD proved on ppcgeeks, I just heard from Azclown that no2chem was testing for downgrading to non-GPS roms 1.x and such. I will proceed to 2.47 then. Can I test 3.39 on that?

[gc14]

Yes, 3.39.10 should be fine on 2.47

[serfboreds]

Yes, 3.39.10 should be fine on 2.47

Couldn't load 2.47 from 1.20, but finally got 2.40 from my laptop to stick. No boot loops, but 2.47 still won't load as it goes straight to "serial" similar to what happened with trying to load .nbh files. The only time I can get any other result is to force bootloader with no image file and it briefly states that there is no valid image file then quickly reboots.

Weird thing is that it keeps saying SPL-2.07No2Chem Titan SPL EVT CPLD-9 (yes, that says 2.07, not 2.47). It loaded the temporary SPL of the relocker version, but that wont stick if I reboot and force bootloader. It goes back to 2.40 again. What's up with that?

This card used to work great, now maybe it is one of the cards that doesn't work to flash? This is certainly an imperfect science LOL

Thanks again GC.

[gc14]

How are you trying to load 2.47? 2.47 can only be run with microsd, and you must have the card inserted while running the unlocker from your device. For example, the executable needs to be in Device Storage, and the card you're using to flash has to be inserted. That's the ONLY way to flash 2.47.

[lllboredlll]

Question..... Is your card formatted to fat32 with a 1024 or less cluster size. I had to format mine via dos to adjust my cluster size that low. XP won't let me set it that low thru their format interface. Not sure if your's is set that way yet or not. If so, tell me I'm an idiot and I'll go away ;)

[gc14]

Nue2.47 automatically detects if the card is formatted right, and will format it for you if it's not right.

[lllboredlll]

Well isn't that just easy now. Thanks for the info I hadn't messed with 2.47 or even looked into it.

[serfboreds]

Well isn't that just easy now. Thanks for the info I hadn't messed with 2.47 or even looked into it.

I have been fooling with this and this is what I have found (to my chagrin so far)...

Whether I put the .exe on the device or on the card I still hang at 2.07 "serial" bootloader, it doesn't try to load the new bootloader image.

Whether I format FAT and let it reformat, or format via cmd (format D: /FS:FAT32 /A:1024), or format using windoze default fat32 settings, it still hangs at the 2.07 "serial" screen.

It also doesn't matter if I am plugged in by USB when running executable or not, still just hangs at 2.07.

I really want this to load, and am thinking it must be the card. It used to load everything before I tried to load 2.47.

[lllboredlll]

Hmm I know absolutely nothing about 2.07 or 2.47. I still run 2.40 and am actually now running 3.39.10 radio after seeing this post..... lol... you gonna love this..... I can't dispute his findings. It locks quick for me on VZW. All the other radios I have been running had mixed results and none were great in my eyes until I loaded this. I was actually able to get great results without GC's fix. I hate to see how fast it was if I was to apply his fix.

[serfboreds]

It is my post and I cant get the stupid nbh to load without using the sprint RUU (still debating) and I hope it is just a card issue. Will have to go buy another microsd by Kingston or someone (this is a PNY) to check. Depressing cause this card ran everything at one point. Now I cant load 2.47 or any nbh files, go figure.

Glad to see that worked for you, I wonder if it is an isolated case, sheer coincidence, or if there are some locational benefits to the different radio versions. Some swear by the newest radio, but I have had mixed results compared to older radios (longer lock times for me for sure). I wish I could get this loaded so I could judge for myself. I feel like a noob, but I know some cards don't work.

[gc14]

With 3.42.30, I can lock from cold start within 15 seconds on VZW....I'm talking 10-15 hours go by without using GPS cold start.

[scrawnyb]

With 3.42.30, I can lock from cold start within 15 seconds on VZW....I'm talking 10-15 hours go by without using GPS cold start.

Mines usually no more than 90 seconds... even when I'm inside and from a cold start as well.

[azclown]

I'm running 2.47 with no issues. In fact, it's performing better....

hey GC - The issue is not that SPL 2.47 doesn't run right, it is that No2chem says you will brick your phone if you try to downgrade back to a Non GPS radio. Now since we Verizon folks do not have a "stock" verizon GPS radio, we would have to go back to 1.X to bring our phones in for service. The issue is that other carriers have 2.x radio versions that are NON-GPS and trying to downgrade to those WILL brick those devices. No2chem was going to look at why Verizon folks can actually go back to non-gps while other carriers cannot.... So, hes going to investigate why we can and they can't go back to non-gps... so until he figures it out, I'll wait for SPL 2.47.... Just incase I need to goto the Verizon store for repair or warranty work....

az

[gc14]

Meh, I could care less. If it gets that bad where I need to return to stock and bring it in, I'll let the damn thing brick and they can give me a new one (which is probably what they would have done anyway if I was bringing it in).

[serfboreds]

Meh, I could care less. If it gets that bad where I need to return to stock and bring it in, I'll let the damn thing brick and they can give me a new one (which is probably what they would have done anyway if I was bringing it in).

I agree with both of you, but being that 2.47 runs faster per DCDs benchmarking tests (see here (http://forum.ppcgeeks.com/showpost.php?p=331091&postcount=31)) I like the idea of faster and better. If it won't downgrade for sending it in, then I will find ways to brick the hell out of it by putting in my lottery numbers in QPST and then I will exchange under warranty for free. No biggie.

BTW - 3.39 runs a bit quicker after about five hours of testing in four cities. I lock faster with it for sure. I am going to go back and forth for a week and post some results with numbers.

I may also test the "fix" with it off and on, but I am pretty confident that my times were markedly improved after that, so I am reluctant to mess with QPST.

[nelsongruebr]

I'm using sprint ROM 3.56.651.0 and Radio 3.42.30 and from a cold start it takes forever... I'm talking about 1+ hours to get a lock...

Do you recommend me to downgrade to 3.39???

[serfboreds]

I'm using sprint ROM 3.56.651.0 and Radio 3.42.30 and from a cold start it takes forever... I'm talking about 1+ hours to get a lock...

Do you recommend me to downgrade to 3.39???

Load the nbh via formatted sd card that is in the first few posts in this thread.

Edit: You are on sprint??? WTF dude? What did you do to your phone to take 1+ hours? Are you locked in a lead refrigerator?

Didn't read that, you have a setting wrong. Read, read, read.

[gc14]

blah....there's NO excuse for people with Sprint to not have instant gps locks. Keep radio 3.42.30 and update your PRI.

[nelsongruebr]

What version of PRI... I have 2.04_003

and maybe I didn't explain my problem... I'm using a Sprint ROM but I'm from Caracas, Venezuela... So I'm runing Sprint ROM with another carrier... My phone is working perfectly and I get GPS locks (sometimes) but in a very long period of time...

[t0mmyr]

im still running 3.39 and 2.40spl with sprint carrier and posting from inside my car. i just ran google maps from a cold start and locked within 8-9 seconds inside my car...are u saying if i update to the newer rom, radio, spl, and pri i will get instant lock??? with sprint?

[azclown]

8-9 seconds IS an instant lock man.....

[t0mmyr]

8-9 seconds IS an instant lock man.....

o...ive always been used to 8 second locks since the first official sprint rom that had gps came out

[rawr]

On Telus, this trick fixed my problem with 3.42.30 Radio and the 3.2.2 ROM, thanks!

edit: Cancel that. still doesn't lock or hold the lock long enough to be functional.

[aguas]

well i went back down to 3.39 today to check out the GPS speeds. i was all around laguna and over at the sawdust festival today, and it was pretty surprising that I'm getting consistent 15 second locks with the test 3.39 radio, compared to about 45 seconds to a minute or more on the official 3.42.xx radios.

[uoowhoo]

3.39 for sure better than 3.35..

I usually got 4 bar in Tomtom show sat status, and after upgrade to 3.39 I can easily get 6-7 bars...in about a min.