[ZombieArmy]

I've just managed to flash firmware 1.10 for K-50 into my K-30
The camera seems to work fine. The only issue I've encountered so far was all the settings reset to the factory defaults. Not a big deal.
In EXIF, K-50 is now saved as expected.

This isn't a joke. I've uploaded some proof-pics here.

Unfortunately, I don't have either Eye-Fi card, or 55-300 PLM to test the main K-50 features.

I wonder how similar the K-50 is to the K-01, would be nice to get PLM and Astrotracer support.


I'd try it on mine but it's my only camera so

---

Last edited by ZombieArmy; 04-04-2017 at 10:25 PM.

[mee]

I wonder how similar the K-50 is to the K-01, would be nice to get PLM and Astrotracer support.


I'd try it on mine but it's my only camera so

Those are very different I suspect.. you'd REALLY have a yellow brick after that attempt.

[Jeff Lopez]

I've just managed to flash firmware 1.10 for K-50 into my K-30
The camera seems to work fine. The only issue I've encountered so far was all the settings reset to the factory defaults. Not a big deal.
In EXIF, K-50 is now saved as expected.

This isn't a joke. I've uploaded some proof-pics here.

Unfortunately, I don't have either Eye-Fi card, or 55-300 PLM to test the main K-50 features.

May I have a tutorial to do that, please? Im willing to risk my k30

[ABel]

I wonder how similar the K-50 is to the K-01, would be nice to get PLM and Astrotracer support.
I'd try it on mine but it's my only camera so

If you really want to experiment, I could prepare a modified K-50 firmware which can be possibly be installed in your K-01
The specs of K-30/50 and K-01 are rather close, but there are radical differences between these models. So as mee said, most likely you'll brick your Brick.

---------- Post added 04-05-17 at 11:13 PM ----------

May I have a tutorial to do that, please? Im willing to risk my k30

There's no tutorial. And I'm not sure if it's necessary.
But I can give you my modified K-50 firmware file. I'll send you a PM with the link and the instructions.

[The Squirrel Mafia]

I've just managed to flash firmware 1.10 for K-50 into my K-30
The camera seems to work fine. The only issue I've encountered so far was all the settings reset to the factory defaults. Not a big deal.
In EXIF, K-50 is now saved as expected.

This isn't a joke. I've uploaded some proof-pics here.

Unfortunately, I don't have either Eye-Fi card, or 55-300 PLM to test the main K-50 features.

This is very impressive!

On a side note, I've always wondered if the K-30/50/500/01 are able to produce 14 bit RAW files with a bit of firmware hacking or if that was hardware dependent. Hmmm......

[Jeff Lopez]

So far I have installed ABel's modified K50 firmware on my K30 and its all good until now..Iso 51200 is operational and I percieve better focusing in low light, (single tungsten bulb small room small object targets)..
Thanks,! I really need that 51200 for artistic effects..

[niceshot]

If you really want to experiment, I could prepare a modified K-50 firmware which can be possibly be installed in your K-01
The specs of K-30/50 and K-01 are rather close, but there are radical differences between these models. So as mee said, most likely you'll brick your Brick.

---------- Post added 04-05-17 at 11:13 PM ----------


There's no tutorial. And I'm not sure if it's necessary.
But I can give you my modified K-50 firmware file. I'll send you a PM with the link and the instructions.

Can you post this modified firmware for the K-30.?

[ABel]

Can you post this modified firmware for the K-30.?

I'm going to release this firmware to public, but only after a small period of testing to make sure the K-30 owners won't break their cameras.

If you are willing to participate in the testing, I can send you the link to the firmware.

[mee]

I'm going to release this firmware to public, but only after a small period of testing to make sure the K-30 owners won't break their cameras.

If you are willing to participate in the testing, I can send you the link to the firmware.

Did you actually do more than rename?

[ABel]

Did you actually do more than rename?

Yes, I had to change the hardware IDs in several places, and fix the block checksums afterwards.

[mee]

Yes, I had to change the hardware IDs in several places, and fix the block checksums afterwards.

Ah so there is more to it. Did you try to load the firmware with a simple file rename? When I tried that the K-30 would see the K-50 firmware, was not willing to give it a go when I owned a K-30 as 4 years ago it was a 650 dollar camera. Probably fails the checksum natively but still curious..

[ABel]

Ah so there is more to it. Did you try to load the firmware with a simple file rename? When I tried that the K-30 would see the K-50 firmware, was not willing to give it a go when I owned a K-30 as 4 years ago it was a 650 dollar camera. Probably fails the checksum natively but still curious..

I've started with simple rename of course
The camera reported something like "Broken firmware file" (I don't remember exact message).
So I had to use IDA Pro to locate the firmware validation routine, and after decompiling it I could modify the firmware to pass the validation.

BTW, the validation logic deserves to be described.
Is it better to write it in this thread, or open a separate topic in PHDK wiki?

[ABel]

I think K-500 can be flashed with K-50 firmware too

[mee]

I think K-500 can be flashed with K-50 firmware too

That would be exciting. I think some of us were concerned the lack of AF points on the K-500 was hardware based and could cause an issue..

[ABel]

That would be exciting. I think some of us were concerned the lack of AF points on the K-500 was hardware based and could cause an issue..

Disabling "Superimpose AF Area" option would most likely help in this case.