M3 T2.004.2 Official Release.

26.10.07 - An official release of Firmware Version T2.004.2 for the M3 was made available for download today from the Chinese Meizu site. Although I have not noticed any changes between this version and the previous released test version the M3.ebn is slightly larger by a few kb and is more recently dated 16.10.07.

Posted Change Log:

1. APE support lossless compression audio format (only supports Fast, High and Normal encoding).
2. Return has been added to the menu function.
3. Fixed bug in Photo Viewer
4. Amendments to other bugs. (No mention as to what they were.)

If you are already using T2.004.2 Test Version your player will not format during the update. Resource.bin is the same as the test version.

If you are running a T2.001 or T2.003 version your player will format after the M3.ebn install and you will then need to re-connect to your PC to load the resource.bin.

This is the Chinese Version so your player will default to Chinese Language after update. To return to English go to Menu - 10 from top is Settings - 7 from top is Language.

Shiiiit!!! Once again, somebody's written the piece of news before me!


I have installed it, but becareful, because it formats the M3. So, think to save your datas.

Hope this firmware will correct the bug of limited 1792 files.

With this firmware, the Meizu M3 (8Gb) is always limited to 1792 played files...

So, the bug is always available...

Nice of you to share madman. Hope the M6 firmware comes out soon...

A few experiences while upgrading from T2.003.5 to T2.004.2:

The first few times I attempted the upgrade, received message "Error upgrading! Try again!" The screen rendering at that point was corrupted, the firmware I suspect in between T2.003.5 and T2.004.2. I downloaded the .rar file twice, compared OK. I uncompressed twice. The first uncompress had been corrupt. The second uncompress successfully upgraded the M3.

The M3 shut itself down after applying the E3.EBN firmware. I powered on again. Nothing. I attempted to power on several times. Nothing. I suspected I had bricked the M3. Then I noticed a dim legend "formatting". I waited till the M3 powered down again.

On restart the M3 showed a green screen error message "Resource not found!". The T2.004.2 formatting blew away the T2.004.2 resource.bin. You must connect the M3 to the computer to copy it again. I did so, powered off the M3, powered on again.

Upgrade finished successfully.

Harry

anyone tried a known "skipping" track yet?

I'm merely reporting here that after many hours using the T2.004.2 firmware on the M3 I find no operational differences or problems in Playback and FM modes between T2.003.5 and T2.004.2. This is not an exhaustive survey of M3 capability.

Specifically, I don't use Photo Library or Video; my M3 contains much less than 1792 songs; I've never encountered skipping; I have not used the APE audio format.

Harry

Man this just isn't working. I kept trying to add this firmware but it never worked, it said no resource bin, download again, and so when it finally worked i decided to add the vista theme skin thing cuz thats what i had b4 and becuz of the re-formatting after adding the firmware it dissapeared. Ne ways so i added the vista and now its saying the whole cnt find resource bin, i think i fucked sumn up. Cn ne 1 help out

When updating firmware the .EBN file will always installed first. If you are upgrading from 2.003 then the player will format with the installation of the M3.ebn, this will delete the resource.bin file if you copied both files together. Because of this you will end up with the No Resource warning when you reboot so you need to connect the player and copy the resource.bin again, disconnect and restart the player at which time the resources will install.

The Vista resource.bin file is for firmware version T2.003.5 and can not be installed on T2.004.2.

If you are still getting the N0 Resource warning you need to copy the resource.bin file from T2.004.2 to fix it.

can anyone confirm 100% that the track skipping issue has been fixed? Perhaps you could test some previously non working files.