Thread: 9520 OS 5.0.0.428 Findings & Fixes

Originally Posted by markeratmarkus

Hi Sunkast, it doesn´t work regardless of carrier. My carrier is vodafone.

In what way is it not working for you?

Originally Posted by sunkast

In what way is it not working for you?

With bbsak, with Blackberry Master Control and with app loader.

With wipe before and without wipe before.

Vendor.xml delete and not delete.......

Originally Posted by markeratmarkus

With bbsak, with Blackberry Master Control and with app loader.

With wipe before and without wipe before.

Vendor.xml delete and not delete.......

Alright, you're gonna have to explain your steps with more detail. I assume you are using App Loader to try and load the OS right? What happens from there?

Originally Posted by sunkast

Alright, you're gonna have to explain your steps with more detail. I assume you are using App Loader to try and load the OS right? What happens from there?

Yes i´m using the App Loader to load the OS. It won't install. Loader.exe doesn't find the OS, and neither the DM or the other ones.

This is the nodrm Version.

Digital Rights Management

Some vendors use it and some don't.

Vodafone does, so this 'nodrm' version will not install. In fact DM and Loader will not even acknowledge it's existence on your hard drive.

Hopefully it will be like .402 and the drm version should follow shortly.

I am not sure if anyone can use the 'no drm' version, I have been on many a website and not seen one review/comment of this firmware so far.

Maybe the Eastern Asians have had more luck, but certainly the European camp is pretty quiet.

Originally Posted by RobinM

I am not sure if anyone can use the 'no drm' version, I have been on many a website and not seen one review/comment of this firmware so far.

Maybe the Eastern Asians have had more luck, but certainly the European camp is pretty quiet.

Follow the instructions, and it works great. :haha:

Edit by lyricidal:
If you are unable to install this on your 9520, follow these steps:
1) Install .402 and .428 leaks
2) Delete Vendor.xml
3) Navigate to either:
x64/64-bit users: C:\Program Files (x86)\Common Files\Research In Motion\Shared\Loader Files
x86/32-bit users: C:\Program Files\Common Files\Research In Motion\Shared\Loader Files
4) Click and open the 9520 .428 folder - select the CDMA and Java folder and Right click > Copy or Ctrl + C
5) Go back and open the 9520 .402 folder and Right click > Paste or Ctrl + V
6) When asked to overwrite files, click Yes to all until both folders are copied over
7) Uninstall .428 from Control Panel
8) Install as you did for .402 leak

Tell me... after this procedure... on the phone... options-->about
Does the platform read 4.2.0.182 or 4.2.0.171?

If it still reads 4.2.0.171, then the OS has not been upgraded in any way.

I think I will wait till someone else can post an 'About' screen to verify this procedure or a DRM leak.

I know lyricidal is renowned for his hybrids, but my question would be the alx files in the root of the installation folder that make specific reference to the file name of the sfi file.

If these names do not match (and they don't), then how can it work?

I see from the response in the other forum that the OS has indeed gone untouched and remains 4.2.0.171.

What you may find now is that because you have only updated the application layer the applications may start to get pretty buggy as they are making calls on the OS that it doesn't understand.mfg:

Originally Posted by RobinM

I see from the response in the other forum that the OS has indeed gone untouched and remains 4.2.0.171.

What you may find now is that because you have only updated the application layer the applications may start to get pretty buggy as they are making calls on the OS that it doesn't understand.mfg:

It can´t unttouched. I wiped the Storm before, and i have only the 428 files on the desktop.........

Did you delete the .402 CDMA directory prior to moving the files and the temporary cache of .402? Or did you just copy them over on top of the existing .402 installation?

The .402 sfi file name is different to the.428 one so copying the folder over would not overwrite the .402 sfi file. PLUS there are a number of .alx file in the root of the installation (e.g. platform.alx etc.) that are still pointed towards the .402 filename.

If you look at the filename PL4.2.0.182 - it has to be getting the OS of .402 from somewhere on your PC.

And where is the leak with DRM???

Dunno... i've be trolling all day with absolutely nowt to show for it. :no:

The "nodrm" OS has a different hardware id value (0x0e001404) than the Vodofone 9520 (0x0d001404) is looking for.

I tried modifying the PkgDBCache.xml and specification.pkg files to use the Vodafone hardware id values and I even had to modify the registry settings for the hardware id associated with the installed files, but still no luck. I was able to get AppLoader to detect the OS, but it fails to install saying there are missing files when it tries to set up the "email setup" software.

I tried replacing the sfi file (which also refers to the E001404 hardware id) with the sfi file from the 320 OS (which was a "drm" OS), but I still have the same problem with the email setup.

Going back to 320 until the correct OS is leaked for the Vodafone 9520...

fbrimm

Yeah, I got to that 'e-mail setup is missing files' bit, but if you match the files that it is after they are all there.

Even changing the drm to 'true' has no affect.

.402 is a good release though.

RobinM,

Thanks for the response.

The 402 I have is also a "nodrm", so I didn't give that a try.

I couldn't figure out which files it was complaining about with the email setup. Since I was using the original 428 files I figured it had to be something else. Oh well.

I was wondering about changing the drm to false (not true) in the device.xml, but it sounds like you've already been down that road.

How come the 0x0e001404 device id in the OS files doesn't show up in any of the device.xml files? Seems kind of strange to me...

fbrimm

Dear all,

Do you happen to know what carrier in which country has been selling NO DRM version of 9520 device? (I believe that 9500 devices marketed through various carriers in many countries are all DRM editions which work with rim0x06001404OMADRM.sfi radio file.)

Sincerely,

P.S.

It appears that NO DRM edition of 9520 devices are available in quite a few countries in Europe and Middle East. Please note that the files listed below contain rim0x0E001404.sfi (in place of usual rim0x0D001404.sfi).

----------

9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_Globul.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_MobiTel_Bulgaria.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_MTC_Touch.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_Nawras.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_Qtel.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_Telenor_Pakistan.exe
9520_omanodrmM_PBr5.0.0_rel721_PL4.2.0.189_A5.0.0. 436_Zain_Jordan.exe

A jEastAsia variation of OS 5 has been released for non-DRM edition of 9520 devices sold by Celcom Malaysia.

RapidShare: 1-CLICK Web hosting - Easy Filehosting

Apparently the Japanese Input option CAN be invoked with this particular OS distribution . . . I wonder if it is possible at all to DISABLE the DRM features of 9520 devices sold in the U.K. and elsewhere.

----------

Download Details

Software Name: BlackBerry Handheld Software v5.0.0.721 (EastAsia)

File Name: 9520_omanodrmjEastAsia_PBr5.0.0_rel721_PL4.2.0.189 _A5.0.0.436_Celcom_Malaysia.exe

Download Size: 126.217 MB

Language: English

Published Date: 02/04/2010

P.S.

The same file has been released for M1 as well.

----------

Download Details

Software Name: BlackBerry Handheld Software v5.0.0.721 (EastAsia)

File Name: 9520_omanodrmjEastAsia_PBr5.0.0_rel721_PL4.2.0.189 _A5.0.0.436_M1.exe

Download Size: 126.217 MB

Language: English

Published Date: 02/04/2010