SAMSUNG YH-920

[umanzor]

Is it possible to install rockbox on this model.

I read they are made by portalplayer, like the ipods and the irivers.

So, if rockbox can be installed on them, is there any way to install it on a YH-920?

[saratoga]

http://www.rockbox.org/twiki/bin/view/Main/TargetStatus

[Bagder]

It uses the mi4 firmware format. Use mi4code to decrypt and start working on a port. Chances are existing PP/mi4 work are similar.

[umanzor]

It uses the mi4 firmware format. Use mi4code to decrypt and start working on a port. Chances are existing PP/mi4 work are similar.

That's what I thought... you mean there are people working on mi4 firmwares for other players?

Hmm, if only I could something about programming.

Well, thanks for the info.

[Bagder]

you mean there are people working on mi4 firmwares for other players?

Yes, the iriver h10 and Sansa e200 both use mi4 files and at least the h10 seems to be progressing nicely.

Still, the file format of the firmware is only a little detail, there are much more than so to figure out before you have a "port".

[dan_a]

I have one of these on the desk in front of me.  Now, if I could only figure out how to get the main PCB out without breaking it...

[pyro_maniac]

Hi folks,

I have a Samsung YH 920 and i am trying to port the iRiver H10 port for my device. Is that easily possible or completely the wrong way?

My current result is, that the bootloader stops and is warning for a corrupt firmware. I think my operations on the mi4 file were wrong.

Could anybody help me?

I hope this is the right way to ask.

[Bagder]

Have you decrypted the yh920 mi4 successfully with mi4code?

Have you tried to re-encrypt such a decrypted mi4 with mi4code and verified that it then works on your target?

[pyro_maniac]

I only decrypt the original file and tried to encrypt the new file with that key. I will try your way to verify my work.

Have the file to be as big as the original?


/EDIT: I decrypted the original file and tried to encrypt the decrypted file.
It doesn't really work:

Code: [Select]

#mi4code decrypt -s pp5020-org.mi4 pp5020-decrypt.mi4
mi4code v1.1.2-DSA (c) by MrH 2008
Secondary label end offset 'default' (0xec)
Decrypted ok with key 'default' (20d36cc0 10e8c07d c0e7dcaa 107eb080)

#mi4code encrypt pp5020-decrypt.mi4 pp5020-encrypt.mi4 20d36cc0 10e8c07d c0e7dcaa 107eb080
mi4code v1.1.2-DSA (c) by MrH 2008
Invalid magic in mi4 header (maybe not mi4 file)!

What made i wrong?

[linuxstb]

The "-s" option you used with the mi4code decrypt command strips the mi4 header - you don't want to do that.

I can confirm that if I do:

./mi4code decrypt PP5020.mi4 decrypt.mi4

followed by:

./mi4code encrypt decrypt.mi4 encrypt.mi4 20d36cc0 10e8c07d c0e7dcaa 107eb080

then the original file (PP5020.mi4) and the final output file (encrypt.mi4) are identical.

[pyro_maniac]

Thanks, that problem seems to be fixed. But there is still the problem that the bootloader is warning for a corrupt firmware.

Which step i missed?

[Bagder]

Uh, if the two files are identical after this process then the process isn't the one to blame surely?

Then the original mi4 you're playing with is also considered "corrupt", isn't it? Then perhaps you should start researching on getting an mi4 file that works?

[pyro_maniac]

The encrypted original file works fine. Only the rockbox mi4 file is declared as corrupt.

/EDIT: Is the size of the mi4 file relevant? The rockbox mi4 is much smaller than the original file. The checksum will be edit by mi4code encrypt, right??

[Bagder]

Since there's no rockbox support for the yh920 (yet), how are you creating the "rockbox mi4" with the right encryption key?

[pyro_maniac]

The build got an mi4 file that i tried to encrypt and run on my device.

And as a key i took it form here:

Code: [Select]

#mi4code decrypt -s pp5020-org.mi4 pp5020-decrypt.mi4
mi4code v1.1.2-DSA (c) by MrH 2008
Secondary label end offset 'default' (0xec)
Decrypted ok with key 'default' (20d36cc0 10e8c07d c0e7dcaa 107eb080)

There is something missing, right?