[Apostata]

Hey there,

I'm a little hesitant - only because I haven't done it before - to install one of the newer, non-Rogers OS upgrades (even though I know there are many good things about them) because I'm afraid of toasting my Bold.

Before I "go there", typically how long does Rogers wait before releasing OS updates? The last one (4.6.0.162) was in October and - as you know - there have been many, many leaks since then.

My concern is installing the latest (stable) non-Rogers release, only to have Rogers release an official version which conflicts with the one I just installed.

Anyhoo - just figured I'd throw this out there in case anyone (Rogers-users I suppose) have feedback.

Cheers.

[ndub33]

In general, there really isn't a set schedule for when a carrier will release an OS. Once RIM makes the software availible to the carriers, the carriers test it for varying periods of time before they put it out to the public. Sometimes they wait to release it to existing Blackberry models to coincide with a new model release (for example, a carrier launches a 9000, and makes a new OS availible for and 8300 the same day).

[sd5187]

As a long-time Rogers customer and owner of a BB Bold I can tell you that Roger's is brutally slow in releasing new upgrades to their Blackberry devices sometimes 9+ months between o/s releases. I am running the latest non-Rogers o/s and it performs well. Just delete the vendor.xml file and you are good to go to install another carrier's release. Cheers.

[Apostata]

Thanks for the responses (particularly sd5187). I feel better about moving on to a new OS version now. Do you have a flavour you would suggest?

[Caspan]

I am also a long time Rogers customer and i have used all different kinds of OS versions with no issues. Its really hard to brick your phone doing an upgrade. When doing an upgrade your device gets wiped and there is no Java Virtual Machine installed but it gets reinstalled by DM worse case that can happen is that the lava loader does not get reloaded and you get a 507 error and if that ever happened you just have to use the loader.exe with the extension -nojvm and it will load it on for you and continue the install. so there are way around if the upgrade ever screws up