Download For: T-Mobile BlackBerry® Curve 8320
Download:Handheld Software (v 4.2.2.180)
Software Platform: 2.5.0.33
Filename: T-Mobile_BlackBerry_8320_v4.2.2.180.exe

Date Updated:10/22/2007

Size:83 MB

DeviceDownloads


To install this software on any 8320:

1. Download and install the latest Desktop Manager from here
2. Download and install the OS packaged linked above.
3. Delete the vendor.xml file located in c:\program files\common files\research in motion\apploader
4. Connect BB, open Desktop Manager and you should be prompted to upgrade.

(Link to previous 4.2.2.175 OS Click Here.)

Here is the edited "blackberry.alx" file: (this file has the vendor ID codes removed for other carrier theme installaton).

I suspect that most owners of an 8320 are T-Mobile customers, so I assume deleting the vendor.xml file per step #3, above is unnecessary?

If a user had previously loaded .175 version, it is important to delete the vendor.xml file.

i dont know how you do it... i am always just a bit late by a matter of minutes to inform the forum of the new version, its the second time, quite a bit frustrating, but all is well. i had been checking either every day to every other day for a month..... its out nonetheless and thats what counts

I had no problems upgrading and I didn't delete it.

As a T-Mobile user, I upgraded without deleting the vendor.xml file. 180 seems to work good at first test.
The calendar entries on the Today screen are missing just like they were on the 175 version.
I had to reset my Profile Scheduler settings.

JSanders, thanks for including the ALX file in your sticky, It's nice to at least have SOME other themes that have the UMA signal indicator, and unfortunately the 3rd party themes do not have them at this point. But at least all of the other vendor's themes DO have the UMA indicator.

I am @ work and can not check the Desktop Manager version....but since I DL'd .175 last week there has not been any update to the Desktop Manager has there???

Hey--thank you HaTaX, I copied your file from the old thread over here... Credit is yours.

that isnt true about deleting the vender.xml file if coming from .175. I came from .175 and never deleted my vender.xml file and it loaded just fine. You only have to delete that file only if you are loading another venders OS. Since this is a Tmobile OS you will be fine

Just finished upgrading..First thing I noticed, when I did a battery pull and restarted my bb, it switched to UMA right away and I have full bars, on the previous OS, when I'm in my room, I never get full bar, only when I'm close to my router.

It's because some people here check every 30 seconds.

how's the wifi speed on the new OS?

Just finished the update and then loaded the other vendors themes.. Update process went smoothly and enterprise activation automatically re-activated on it's own and completed within about 5 minutes.

Will give some more feedback as to how it behaves after I have some more time with this OS.

It's just stock language we have been placing in the update OS threads. If you don't need to do so, you obviously don't.

Unfortunately, bluetooth and wifi is still an issue

what wifi issue?

Wow! One thing I can tell right away is it appears to be grabbing the UMA network MUCH faster when coming out of sos (my house has no tmo network inside). Very cool!

I use them together all the time in my home... what's the problem you're seeing?

No I meant to say the bluetooth through wifi, I tried connecting my S9 and I keep getting an Error, and my UMA dropped to EDGE.

For a n00b like myself...what do I do with the blackberry.alx file? Where do I copy it to? TIA!

Wirelessly posted (BlackBerry8320/4.2.2 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Strange thing. Was browsing digg river on my blackberry browser and all of a sudden the screen went black the red led came on like a reboot and a second later the browser was up where I left it. It was microseconds. I wiped my 8320 before loading this os. I had all settings and apps installed. I was also able to download live search via ota now!

The BlackBerry.ALX file should be placed in:
C:\Program Files\Common Files\Research In Motion\Shared\Loader Files\8320-v4.2.2.180_P2.5.0.36

Rename your old BlackBerry.ALX file to something like BlackBerryALX.OLD so that if you ever need to refer to it, you've got it.

After it's been copied there, open up desktop manager and open the Application Loader, it should detect there's an update to the core software and push the extra themes to your device then.

I personally only remove the vendor lines from the theme I'm going to use so I can save space on the BB for other applications and data. But the modified file will load all the available themes.

Mine drops bluetooth objects whenever it feels like it. I've discovered if I turn off WiFi Idon't have the problem

Thanks JSanders! No questions from this Noob yet - I have been reading up on the Curve before I got it (today) and it's my first BB but I have gotten it set up and it seems to be working correct with UMA, bluetooth, etc. I am loving this phone!

Do the other vendor's themes have UMA indicators...?

Yes they do, all of the themes available in the .180 OS file have the UMA indicators present and working. Seems they still don't go up and down with the signal strength though....

Yes they do

Edit: Gah! Ya beat me!

How did you do that?

Hehe, sorry about that. Been watching the forums while I test out .180 and get my berry back to the way that it was.

A few observations with .180:

Seems very similar to .175 as far as speed goes, nothing I can see as a huge change other then it seems to start up from cold very quickly.

As far as bluetooth with wifi goes, I'm actually having MORE trouble with the .180 version. Bluetooth was off and a UMA connection was made, I turned bluetooth on and fired up my bluetooth headphones / headset. (They actually work quite well as a headset in a quieter environment) The result was the headset connected quickly to the device but when I went to make a call to 611, the call never went through, was dropped, and then it reverted back to EDGE.

Here's where things get strange and I hadn't seen this with .175.... After the dropped call, I tried it again on EDGE and the call went right though. I then waited for the device to reacquire it's wifi connection and then UMA, this took about 2-3 minutes for it to do it on it's own. After words I tried again to make a call and it again dropped the call, and reverted to EDGE with no call being completed at all. When I let it sit this time, it did reconnect to the wifi network, but did not establish UMA. So I went into wifi diagnostics to see what the error was with UMA and it said ISP error, as I was in this menu the UI started becoming very unresponsive, and then the phone rebooted itself.

After it had come back up I again tried the bluetooth + UMA dialing and was still unable to even get it to connect when dialing out, if even for a few seconds, all I ever heard was the call lost tone (3 pitch climbing tones). Also odd was that after it dropped it this time, I simply shut off the headset and the bluetooth on the device and attempted to make a call. It STILL gave me the call lost tone and refused to make an outgoing call, the only resolve I had to this was to shut off wifi, and after it had hooked back up on the EDGE network I could make outgoing calls again. After I had made a successful call to 611 on EDGE I turned wifi back on and it is working as expected again.

This is no good and I may revert back to .175 if .180 fixes nothing else and makes the bluetooth with wifi worse then it was.

After doing the update I noticed that it deleted all the pre-installed MyFaves icons from the MyFaves folder. I know most of them are goofy, but I did use the "Mom" icon for...well...my Mom!

Anybody else missing the MyFaves icons or was it a fluke for me?

Does anyone have information that can be shared here about any updates, etc., from RIM v4.2.2.175 to RIM/T-Mobile v4.2.2.180?

I have asked for Release Notes from T-Mobile, but they don't normally hand them out.

Upon further testing it seems to be that it doesn't like this particular headset...

With a motorola HS850 it connects fine and works as it should, but with my stereo headset it will not even make a call over UMA. I have a few other headsets at my disposal that I will give a shot and see how it works.

Anyone with a regular headset (Not stereo headphones with a mic) having luck with using bluetooth and UMA together now?

Seems they still have some bluetooth bugs to get out of the system with these devices. I will try re-pairing my headphones to see if it makes a difference.

For any of you that had experienced the same problems as me with Empower's BES MailBox software (working on .171, not working on .175), I'm happy to say that it works again on .180! Excellent!

I have it on two curves so far and everything is working great. One more curve to go!

Dumb question, but what is the difference between wiping with JL_CMDER and the regular "wipe handheld"?

JL_CMDER fully wipes the OS and everything off the BB, doing a wipe handheld resets the device back to exactly the way it would be if you had freshly installed the OS that is currently on the device.

If you do a JL_CMDER wipe, you will have to reload the OS on the phone with desktop manager and is typically only done if you have had a serious problem with your BB or it will no longer startup.

Thanks! I asked because I am trying to use JL_CMDER for the first time so I can upgrade to .180 but it won't connect (I followed Stinsondog's FAQ's) after numerous attempts so now the "what to do if JL_CMDER won't connect?" says I have to do the DOS thing and I'm a little bit sketched because it is a little involved and I was never good at DOS stuff and I'm afraid I'm going to mess something up. My BB was working OK on .171 except for some UMA issues with dropped calls but I fixed that by keeping it on mobile network for phone only but allowed for wifi for data. Is it really worth upgrading to .180?

Thanks.

Wipe Handheld erases all customer data. It does not erase any third party applications installed (so it doesn't exactly put it back to the point of a fresh re-install). The applications are still there.