Upgrade E2 to ES2 and vice versa!

[Telengard]

Here goes:

Code: Select all

E2toE2S:
6493a128a1011938d8827a894b5b5e15 *SYSTEM.VSB

E2StoE2:
4b50df1977ccbc2c1ccc90fb96e55b5d *SYSTEM.VSB

I just checked with mine and got the same results with the ones downloaded from facebook. Using regular md5 for hashing.

[Mulldoon219]

I tried to modify the files yesterday, but only found three numbers to be different in the header and not four like the hacking manual says. Could someone of you with working files (e2 to e2s and e2s to e2) provide the md5 checksums of these files. People like me would then be able to check if we messed up the editing part before we brick our unit.

You could use http://onlinemd5.com to find out the checksum of both files.

Here let me help you...

I love this place. I'm asking for a checksum to make sure to not flush $400 down the crapper. The answer I get is a picture of a toilet. You can't make this s**t up!

Laugh it up! Well at least your $400 paperweight will make a nice conversion piece.

[GMC#1]

Thanks to Poumtschak and Telengard! You improved your karma today. Everybody can now check their modified files before messing with their firmware. I got the same checksum and my files are working!

Laugh it up! Well at least your $400 paperweight will make a nice conversion piece.

The joke is on you pal!

[Ted3000]

With my hacked e2, I'm laughing all the way to the bank. The sample bank.

[Mulldoon219]

Thanks to Poumtschak and Telengard! You improved your karma today. Everybody can now check their modified files before messing with their firmware. I got the same checksum and my files are working!

Laugh it up! Well at least your $400 paperweight will make a nice conversion piece.

The joke is on you pal!

Yup. Just pray you never need warranty service.

[_INTER_]

Yup. Just pray you never need warranty service.

Software update doesn't void warranty. a) its not specified that a modified firmware is a warranty violation b) it can not be proven that you used the modified firmware (unless you walk in with the mod)

[Mulldoon219]

Yup. Just pray you never need warranty service.

Software update doesn't void warranty. a) its not specified that a modified firmware is a warranty violation b) it can not be proven that you used the modified firmware (unless you walk in with the mod)

Whatever helps you sleep at night. If you've had the 'tribe for more than 30 days, your retailer will tell you to send it in. If you think hacking firmware doesn't void the warranty and there isn't a change log of every FW update, you are deluded.

[scum]

i still do not get it, why do you need the sampler - every decent DAW with proper vsti sampler and some hardware controller can do way more..

[sauce]

i still do not get it, why do you need the sampler - every decent DAW with proper vsti sampler and some hardware controller can do way more..

The same can be said for the synth version.. Even more so, if you ask me. A laptop/controller combo doesn't feel nearly as intuitive as an Electribe to most people.

[apapdop]

The same can be said for the synth version.. Even more so, if you ask me. A laptop/controller combo doesn't feel nearly as intuitive as an Electribe to most people.

+1

[_INTER_]

Yup. Just pray you never need warranty service.

Software update doesn't void warranty. a) its not specified that a modified firmware is a warranty violation b) it can not be proven that you used the modified firmware (unless you walk in with the mod)

Whatever helps you sleep at night. If you've had the 'tribe for more than 30 days, your retailer will tell you to send it in. If you think hacking firmware doesn't void the warranty and there isn't a change log of every FW update, you are deluded.

I have the E2S, I don't switch firmware. Still sleeping pretty bad with the crappy noise output, the lowlevel backrow pads, the clipping on pattern switch... with this kind of quality Korg is delivering lately, I doubt that Korg is logging anything at all (they can't even save a sample to memory of 24 MB).

[Proppa]

@mason any luck with a fix m'man? I hope you get it sorted out.

To anyone who's been less than sympathetic to a brother in arms here: shame.

[GMC#1]

I doubt that Korg is logging anything at all (they can't even save a sample to memory of 24 MB).

I highly doubt that too. If changing the header of a file is enough to hack the machine then they obviously did not implement any safeguard against corrupted files at all. This means that if the download of a firmware update goes wrong, the broken file could actually kill the electribe. They did not implement even basic security functions, so I doubt they went to go the extra mile to build in some obscure logging function.

[Mulldoon219]

@mason any luck with a fix m'man? I hope you get it sorted out.

To anyone who's been less than sympathetic to a brother in arms here: shame.

Wait - I thought he was a Korg plant and not a "brah"? Make up your mind boys.

[Poumtschak]

I highly doubt that too. If changing the header of a file is enough to hack the machine then they obviously did not implement any safeguard against corrupted files at all. This means that if the download of a firmware update goes wrong, the broken file could actually kill the electribe. They did not implement even basic security functions, so I doubt they went to go the extra mile to build in some obscure logging function.

Seconded.
IIRC, Dutchcow even bricked his unit by flashing a legit firmware.