GH1 firmware research volunteers required

As tester13 stated, Panasonic originally posted version 1.21 that was actually 1.21, but updated it the next day. 1.21 allowed 3rd party batteries, whereas 1.22 supposedly removes that capability...although I don't have any 3rd party batteries so I cannot confirm this. Unfortunately, I never got 1.21.

Note that both 1.21 and 1.22 have the same filename: GH1__121.bin

1.21 was posted on 9/17/2009 and 1.22 was posted on 9/18/2009
1.12 was posted on 6/18/2009

1.22 md5:
d6380d59838964f9492a67f5f1e27521

1.12 md5:
e371c4887dcaa6ab0143a02dfe972586

I believe the first reference to the version is found at bytes 1805 & 1806
 
As tester13 stated, Panasonic originally posted version 1.21 that was actually 1.21, but updated it the next day. 1.21 allowed 3rd party batteries, whereas 1.22 supposedly removes that capability...although I don't have any 3rd party batteries so I cannot confirm this. Unfortunately, I never got 1.21.

Note that both 1.21 and 1.22 have the same filename: GH1__121.bin

1.21 was posted on 9/17/2009 and 1.22 was posted on 9/18/2009
1.12 was posted on 6/18/2009

1.22 md5:
d6380d59838964f9492a67f5f1e27521

1.12 md5:
e371c4887dcaa6ab0143a02dfe972586

I believe the first reference to the version is found at bytes 1805 & 1806


I have both the 1.21 and the 1.22 files since I was lucky enough to grab 1.21 the first day. Because the only difference between these versions is the third party battery detection logic, could this not be reverse engineered into a patch by comparing the two sets of code? A direct file compare should show exactly what changes need to be made to disable the battery check.

It would seem that when Panasonic releases the new 1.3 code in a few weeks, many people will want to upgrade to this for the improved autofocus. It would be helpful for those people if there could be a patch to disable the third party battery check. Unfortunately, I cannot test this as I only have Panasonic batteries.

This is just a thought for what may be the simplest and immediately useful patch that could be engineered. Thank you Tester13 for starting this project and making such good initial progress. This could be a very impressive upgrade for everyone with a GH-1.
 
"1.21 was posted on 9/17/2009 and 1.22 was posted on 9/18/2009
1.12 was posted on 6/18/2009"


now only the 1.22 is available, please could anyone upload all firmware versions to rapidshare or megaupload?

would be nice to have all for testing purposes
 
I only have the 1.21 firmware, which should be the version that allows 3rd party batteries but I cannot check, as I can't check the checksum. (http://www.megaupload.com/?d=4B7SR5OZ)

But let's not derail the thread too much to the differences between original versions. :)

We're getting pretty close to the funds to buy a GH1 for testing purposes, which should help a lot!

EDIT: It's NOT 1.21, it's 1.22.
 
Last edited:
If it allow you to update, it is prove, as latest is actually 1.22. And one without battery check is 1.21 :-)

That would suggest to me that they do have a version check - unless they just want their service engineers to be able to tell them apart (so the bastards can flash the new version if you send your cam in for servicing :) ).
 
Can somebody post the 1.12 file?
I want to prove that one can go ack and forth between 1.1 and 1.2.
I know this works on my LX3 and ZS3 because i tried it.
So if the patched version gets a number 1.4 or higher it will be always possible to go back to the current release 1.2
 
Last edited:
got the actual version 1.21. here are all the md5 checksums so people can figure out what they have:

v1.12: e371c4887dcaa6ab0143a02dfe972586
v1.21: feb92634ea3c83edba243024bc595e95
v1.22: d6380d59838964f9492a67f5f1e27521
 
So I was thinking about how fast donations have been coming in, and it seems in a few days we'll have enough for someone to buy a GH1 body. But then what? We might have to wait 2-3 weeks for the delivery from eBay.

Like many others I'm anxious to see tester13 get what he/she needs to move forward. As an alternative: is there anyone willing to express ship their own GH1 to tester13 in exchange for the donation money? This would reduce our wait time significantly.

I might consider this, but I'm planning on using mine in the next 2 weeks.
 
Tester, are the firmwares Panasonic released complete? The HV30 firmware was a patch, ie. there were parts missing that had to be dumped from the cam.

Also I assume that any crucial calibration values are stored safely in a separate EEPROM, a firmware flash can't kill them?

It would be good to find a way to dump the calibration values, so they can be restored if they get trashed during experiments.
 
Unfortunately the downgrade of firmware does not work on the GH1.
Tried it with 1.1 over 1.2.
The camera ignores the file.
 
Wait, hold the phone.....

If the firmware for the cameras from EMEA and Americas is identical then it's the serial number or ID challenge check that locks out the cams ability to tape over 30min,
prob non-destructible NVRAM.

As in is the firmware geo location specific, as in AsiaPac, EMEA and US? If so then which one are we reversing?

It looks like the co.jp available firmware is identical to Panasonic.com download (same link)

MD5 (GH1__121.bin) = d6380d59838964f9492a67f5f1e27521
MD5 (GH1__121.bin_USA) = d6380d59838964f9492a67f5f1e27521

There is a region code that is set when the main motherboard is installed or replaced. That code drives the supported language group, TV standard (PAL or NTSC) and the 30 min recording limit. Updating firmware has no effect on the language set. This comes up frequently as many tourists buy cameras in Japan and are stuck with Japanese only language, which can't be fixed by using firmware from other regions.
 
Region is not a problem, as I said.
Anyway we'll hold complete PAL/NTSC switching and few related things.
We don't like to pay more for the same body, right? :-)
As soon as working simple method will be available to make USA and Japanese models to be converted their body prices will be up. May be not much, but...

Downgrade - I have good solution for this problem, but as said it is crucial patch, and any problem with it and you'll be stuck with certain firmware :-)

About camera body. Hmm, we also need PentaxK to m4/3 converter and some third party batteries (ones that don't work in 1.22). Both things can be ordered already and then added to camera package.
And about delivery time. Our own post work is such fashion that 7 days is just statistical error in last months, so don't bother :-) I'll provide Car3o necessary instructions how to inrease speed up to maximum possible.
 
You cannot just byte-compare, you have to unpack the firmware first, then it may be just a single int, or jmp jnz change.... But after reading up on their C++ dev platform for the firmware, i'm convinced there would be an object chained up to get a couple of bytes from "battery vendor id". - All in the name of the exploding lithium ion laptop on a plane incident...


Yes, I understand that we cannot byte compare the two versions. Each firmware needs to be disassembled back to assembly code and then the two text files need to be compared for differences. Because we know that the only change between 1.21 and 1.22 firmware is the battery test logic, then it should be relatively simple to figure out what the changes are to disable the battery check. If Panasonic are devloping in C or C++, then the task is more difficult as the compiler will optimize the code differently, but figuring out the changes should still be possible. I am just suggesting that this may be the easiest problem to attack out of all the suggested changes people want to the firmware.
 
PayPal balance: $547.51 USD

I'd sell my Gh1 to tester, however it's a Japanese model....if he's willing to do that.

Things are going good so far. Thanks all our sponsors! :-)
May be it is good idea not to stop donation process then we got necessary sum (as upcoming v3.00 patches could bring us more donations).
We'll keep money on our collector account and will use them for useful things (like may be 2nd body for 3D synchronous recording patch).
But it'll desided only if in reality it'll be possible and necessary. Otherwise we'll move money back, even if with 5% fee for longer than 60 days period.

And I really don't think that Japanese model is good idea.
Despite that we can patch regional checks, we don't know all consequences for that. We can just brick the body.
So, such patches must be moved to later stages then we could understand inner working in more details and remove unnecessary risk.
 
Last edited:
Back
Top