Wiki > Main > SamsungZ5 (compare)
Difference: SamsungZ5 (r18 vs. r17)
7 tactile buttons and a touchpad (directions).
Dedicated hold switch
SoC: Sigmatel STMP360(B)
Screen resolution: 128 x 160 (RGB) [there are 2 LCD variants, see below in the hardware section]
RAM: 16 Mb
Radio (where present): Philips TEA5767
Nand: 1 - 2 - 4 GB splitted in various logical partitions (see under)
Hardware variants: from the bootloader I understood that there are at least something like 8 HW revisions. Of course these revisions are not very different one another, but features are missing. For example my 2 Z5 have both a microphone as well as the FM radio, while the Z5 that someone took apart below has neither FM radio nor microphone. Other variants are NAND type and LCD type.
SLC version --> 1 GB
MLC version --> 2/4 GB
2 firmware updates are available here: http://www.anythingbutipod.com/forum/showthread.php?t=32690. The update is performed by placing the =Z5Update.dat file in the root of the player or the System/Data folder, depending on the current version you're player is running. This player runs Linux as well as a particular Java virtual machine! Indeed, the firmware UI is made up in Java and all the class are visible (and hacker-able ). Lots of interesting scripts and executable are present in the firmware.
With the help of the Z5 updater (recovery) application we can restore the firmware through the STMP3600 recovery mode. A updater.sb as sent to the device. This ~1,8MB file is really complex since it includes some code to load a Linux kernel with a rootfs-based recovery. Then a z5-fw.dat is sent to the user memory (through UMS) and the process of decryption + flashing begins!
Z5Update?.dat is a mixture of plain and encrypted bytes.
To get the player to present itself as a STMP3600/Player Recovery Class device, hold the middle select button while connecting to USB from the off state.
Keep in mind that this device has a sleep mode and the only way to truly turn it off is by pressing in the reset button on the bottom. (applies to OF, not other modes!!!)
Touchpad device shall be enabled via the TX/TY +/- pins. See the "Default value" in the table above.
I'm working on this port and things are going fine, what is implemented so far in a "playground" code to be sent to device is:
r23 - 02 Dec 2013 - 10:57:08 - LorenzoMiori?Revision r18 - 29 Dec 2012 - 23:07 - LorenzoMiori?
Revision r17 - 28 Dec 2012 - 22:12 - LorenzoMiori?
Copyright © by the contributing authors.