HELP! I can no longer update my GH1 firmware hack....

Lucas Adamson

Well-known member
So, I had v1.2 when I bought the GH1 camera, and it's most certainly a hackable camera, and I've uploaded 1.32, then a ptooled 1.33 and then a 1.34. Perhaps a 1.35, I don't remember.

I also updated the kit lens firmware to 1.4

Now on the version screen it says quite simply v1.3 for the body and for lens it's v1.4

Note no second digit??!!

So, when I put ANY ptooled firmware on my card, I get no acknowledgement of their existence, just "No Valid Picture to Play".

I have searched the forum for answers, and made sure that my hacks are named right, with:

2x underscores,
all caps,
I've tried __135 __136 __137 __140 __141 __150 - none of them recognised,
All naming done from within ptool, not renaming file afterwards - like this: GH1__141.bin (I've tried caps BIN too)
Battery is full,
SDHC is brand new Sandisk 16GB Class10 (has worked flawlessly for a month now)

I'm very worried that I won't be able to update now. What am I missing?

Your help is much appreciated fellow GH1ers!!
 
Do you have any pictures/video on SD card with hacked firmware ? If card is empty, it might cause the "No Valid Picture to Play" problem.
 
I tried taking some pictures, and a few seconds of video, but then when I turn it on and hit play, I just get the images playing.
 
This is still unresolved. I am trying everything.

Can people tell me what their camera tells them for version, because mine says v1.3 (no second digit) and I have no idea why...??? I can't update to any 131.bin or 140.bin or 141.bin files at all - nothing is recognised!

Please help!
 
I had the same problem once. I reformatted the card, then made sure there was *nothing* on it--no files; no directories. Then I took a few photos (so there would be a picture to play, bypassing that error message) Then I used a fairly high number (like 144) for the patch, knowing it would rest to zero if I checked that option.
And then it worked.
 
Thank God for that! I got it to work by doing some arcane combination of things that somehow managed to make it work. What it was is that the number you enter in version increment has to match the third digit in the file name, and the file name number must be incrementally larger than the previous version.

Thankyou Lord and New Year to you all! I am on version 0.0 now, and will keep it that way.
 
I am having the same problem. I tried everything. I used to have version 0.0 but after the last hack i know have 1.3 and I can't change it. I tried 133 124 135 136 137. I tried version compare on and off. I tried 143 as I thought you were saying. Can you tell me exactly what buttons to push on this? Thanks
 
I tried 133 124 135 136 137. I tried version compare on and off.
Turning "Prevent version compare" off (unchecked) will cause the camera to become difficult or impossible to hack. It's hazardous to turn this patch off it and it serves no practical purpose to do so.

If you have accidentally patched the camera with "Prevent version compare" unchecked, you may be able to repatch it properly with the following two patches:

Version increment: 67
[checked]
Prevent version compare: [checked]

If this allows your camera to successfully update its firmware, then it should be hackable from now on. To prevent this problem from ever occurring again, always use the following two patches every time you hack the camera:

Version increment: 1 [checked]
Prevent version compare: [checked]
 
Turning "Prevent version compare" off (unchecked) will cause the camera to become difficult or impossible to hack. It's hazardous to turn this patch off it and it serves no practical purpose to do so.

If you have accidentally patched the camera with "Prevent version compare" unchecked, you may be able to repatch it properly with the following two patches:

Version increment: 67
[checked]
Prevent version compare: [checked]

If this allows your camera to successfully update its firmware, then it should be hackable from now on. To prevent this problem from ever occurring again, always use the following two patches every time you hack the camera:

Version increment: 1 [checked]
Prevent version compare: [checked]

Thankyou lpowell. You rock!
 
thank you !

thank you !

Thank God for that! I got it to work by doing some arcane combination of things that somehow managed to make it work. What it was is that the number you enter in version increment has to match the third digit in the file name, and the file name number must be incrementally larger than the previous version.

Thankyou Lord and New Year to you all! I am on version 0.0 now, and will keep it that way.

I had the same problem as you, reading your post i solved it, great ! Thanks again.

Phil
 
What it was is that the number you enter in version increment has to match the third digit in the file name...?
The number in the patched firmware's file name doesn't have to match anything, you can number your firmware files however you prefer. While the file names must conform to the format "GH1_XXX.BIN" or "GF1_XXX.BIN", PTool will not allow you to save the patched firmware with an incorrectly formatted file name.
 
Well, for me it didn't work with, for example GH1__135.BIN unless I also had version increment set to 5 in the PTool settings (not the save window).
 
Well, for me it didn't work with, for example GH1__135.BIN unless I also had version increment set to 5 in the PTool settings.
You may have noticed that my downloadable PTool 3.51d INI patch files all have "Version Increment" checked and set to 1, and "Prevent Version Compare" checked. This works with any number I select for the "GH1_XXX.BIN" file name.
 
Once in the prevent version compare mode, everything is sweet. Upgrading from v0.0 always works. Upgrading from 1.32 simply didn't work for me for about 30 attempts, and my file names were correct.
 
I have a question.

If you load footage onto your comp off the hacked gh1. Should it show the bitrate at 50...or will it still show the default settings...
 
Back
Top