8830m release code now available (Sprint) via RIM classic download
 

Only for those who know they need it - Released 3/13/2009 for corporates.

Software Download for Sprint L.P.

BlackBerry Handheld Software v 4.5.0.201 (Multilanguage)

Package Version: 4.5.0.201
Consisting of:
Applications: 4.5.0.135
Software Platform: 3.4.0.28
File name: 8830mAMEA_PBr4.5.0_rel201_PL3.4.0.28_A4.5.0.135.exe
File size: 82.15MB
Note: The Software Platform and Applications version numbers can be found under Options-About screen on the handheld.

If your hardware id is not 0x06000E04, this code is not for you.

sR

Thanks, it appears to be the same file we have listed in our Sticky Note at the top of this section. The M indicates the OS is multilanguage.

Appearances can be deceiving. Both are multilanguage.

The rim8830c.sfi files are different.

8830uAMEA_PBr4.5.0_rel201_PL3.4.0.28_A4.5.0.135_Sp rint.exe - 8830 rim8830.sfi 16,940,000 bytes

8830mAMEA_PBr4.5.0_rel201_PL3.4.0.28_A4.5.0.135.ex e - 8830m rim8830.sfi 16,948,752 bytes

Note that the hardware IDs are different. From Vendor.xml -

<vendor id="0x68" Name="Sprint">
<bundle id="System" version="4.5.0.201">
<devicehwid>0x04000E04 0x06000E04</devicehwid>
</bundle>

The quick and dirty test is to extract the files via an administrative install and use CFP to get the fileinfo.

cfp fileinfo rim8830c.sfi (from the 8830m package) yields:

cfp fileinfo rim8830c.sfi (from the 8830 package) yields:
Clearly there is an 8830 hardware variant with its own OS build, and its now available for download.

sR

Could you explain that in English, please?

RIM added a second entry in their Sprint downloads section for Package Version 4.5.0.201 on 3/13/2009 and it looks almost identical to the first entry that was published and stickied (as JSanders has indicated) on 2/26/2009 - See the first and last entries in the code window:

Naturally, this raised a few questions - (what's the difference between the two packages?, which is the appropriate one to download?). I responded that the new entry was for the 8830m, and not for the 8830 (on another forum). I needed to run CFP against the firmware files to reach that conclusion.

I also originated this thread, thinking that my findings were postworthy.

Looks like RIM has refreshed their 8x30 product line. There may be FCC incentives/mandates to do so. See the links in this post - Newest 8830 OS: v4.5.0.135 (Multilanguage)

The refreshed models have been assigned unique hardware and model designations. The most widely reported to date has been the 8330m.

These new hardware ids appear in the vendor.xml file, which suggests that they require unique builds -

8130 - 0x04000D04, 0x06000D04 - 8130m
8330 - 0x04000F04, 0x06000F04 - 8330m
8830 - 0x04000E04, 0x06000E04 - 8830m

In the case of the 8830, we see that the FCC has recently granted a class II permissive change for a hardware upgrade, presumably to be compliant with the new HAC standards and requirements. Under these circumstances the models being validated usually don't require a new FCC ID, but do need to be differentiated with a unique model designation, if the compatibility levels have changed as a result of a) minor hardware changes or b) updated test results, so that the deaf and hard of hearing community will be better served. Here's the guidance - OET Report Results

Exactly what hardware has changed in the 8830? Most of us don't know. But it appears that the modified hardware requires a unique build for its recently assigned hardware id of 0x06000E04, and this unique build has been recently published (3/13/2009) on RIM's download site. Why they didn't label this as a build for the 8830m is anyone's guess (They have been doing it for the 8330m.) I could further speculate, but I won't.

sR

The new models may in fact be driven by the injunction on certain Qualcomm chips - From their website:

Qualcomm will not support for use in the U.S.:
MSM6275, MSM6280, MSM7200, MSM7200A, ESM6270, ESM7205, ESM7205A, MSM7500A, MSM7600

If first sold to customer after 5/29/2007, Qualcomm will not support the following for use in the U.S.:
MSM6150, MSM6175, MSM6500-90, MSM6500-130, MSM6550, MSM6550A, MSM6575, MSM6800, MSM6800A, MSM7500
Unless used in the manner prescribed by Qualcomm for use in the U.S.

Qualcomm will not support for use in the U.S.:

1. QSC6075, QSC6085, MSM7525, MSM7601, MSM7625, MDM1000, QSD8650
and baseband chips released after 12/31/2007
2. If parent MSMxxx0/5 parts were sold to customer after 5/29/2007:
MSM6151, MSM6171, MSM6551, MSM6551A, MSM6571, MSM6801, MSM6801A, MSM7501, MSM7501A, MSM7601

The foregoing restrictions shall not apply to U.S. wireless terminals represented to Qualcomm by Verizon Wireless as being exclusively made on their behalf.
Qualcomm will provide technical support for U.S. wireless terminals using MSM6275, MSM6280, MSM7200, MSM7200A, ESM6270, ESM7205 and ESM7205A, if sold to customer prior to 12/31/2007.
---------------
Perhaps the 8830m, 8330m, and 8130m have been retrofit with supported chip sets.

sR

You have gone way too far down the rabbit hole...

It's been reported that the ESN to MEID migration (as a result of ESN exhaustion) requires significant changes to the radio code, and that this driver alone, would require a new model designation.

To sum: RIM has recently introduced 4 models to their CDMA product line -

8130m
8230m
8330m
8830m

As can be seen here - https://www.blackberry.com/Desktop/D...XML/Device.xml

Three relevant drivers for the timing of device refresh have been identified:

1) FCC mandated quotas for the introduction of new HAC devices every year
2) The ongoing Broadcom infringement judgements against Qualcomm
3) Migration from ESNs to MEIDs


These "refreshed' models require unique builds, so you can't run the 8x30m OS code on a 8x30 device and vice versa.

sR

...and then you still have variants like the 8230f.

8230f? You have a code name on this?