Unable to hack GH1 second time, Firmware Version 1.B ??

G

genkifilm

New member
I purchased a used GH1 with an '09 serial number about a month ago. A friend talked me through the first hack and it seemed to work - that is, when I pushed the green playback button the camera did what it is supposed to do and loaded the firmware hack after about a minute or so. I do not recall if i had checked either Version Increment or Prevent Version Compare box and I did not properly save the file so I can't go back and find out. Since then I have spent hours reading through the threads and trying every variation in order to load a new hack and it has not worked. All I get is "No Valid Picture To Play". Something else - when I check my Version Display it shows as 1.B. That's the letter "B" and I have no idea what that means and have not seen anything about this scenario on this forum.

If anyone has encountered this problem and knows how to help I would greatly appreciate it. Perhaps there is a sure-fire way to get back to Version 1.32 and then "start over" with my first hack at 1.33 checking both boxes the first time and then only the Prevent Version Compare after that?
 
If you didn't use "Prevent version compare" the first time around, then you need to label the new firmware as a progressively higher version to get the camera to read it. You should use "prevent version compare" next time, it turns the firmware version to 0.0 and makes it so the next one doesn't have to be a higher number. I'm not sure what the 1.B is though, never seen that before.
 
As mentioned in my original post, I have tried every variation on checking and unchecking the two boxes. I've tried to set the Version Increment to 1, 2, 3, 30, 50 etc. with
no luck. Hopefully someone can give me good advice for moving forward as one who simply does not know whether the "Version Increment" or "Prevent Version Compare"
boxes were checked upon the first, successful hack. And as for my current firmware being "1.B" - I wonder if that's a clue to what's happening with my camera.
Vitally, are you out there?
 
What I meant is that sometimes you not only need to set the version increment, but may also need to change the name of the file. The default is GH1__132 and so you could try GH1__150 or something. Or maybe GH1__1C ? (Still don't know what the letter is, but maybe this will trick it into working)
 
1.B looks like it might be 1.42 (B is 42 in hex). Try going to an increment of 50, or even 100, or more. It doesn't matter because once you check no version compare it will all go away. Or, maybe you need to go to 1.C (as dasbin suggests). Who knows how the version compare was implemented. Don't forget, the file name has rwo underscores, not one.

Chris
 
Thank you for the suggestions. I tried using increments 30, 50 and 100 and it did not work. i tried saving the file as GH1__1C.bin and Ptool would not allow me to do that.
I've tried all increments with just Version Increment checked as well as both boxes checked. I tried saving as GH1_143.bin with increment as 1 thinking that perhaps
my 1.B firmware is 1.42 as cbrandin suggested but that did not work either. I am using Ptool 3.50d. I am considering a offering a reward to anyone who can figure
this one out. :)
 
did you just stop at 100? didn't try more?

"saving as" so and so filename I find does nothing. your problem is you have let your increments go to far. dont you notice the change in version numbers when you punch in an increment in ptools? v1.C tells me you punched in an increment of 142 to 157, how you managed that i don't know..ha. typo maybe. try 160 next time, that should get you over v1.C, it should be v1.D2 now. this time make sure to check version compare patch. You can rename it to GH1__1D2.bin or even GH1__132.bin, doesn't make a difference from my experience. hope this helps
 
Thanks Mr Fanny! Setting the increment to 160 worked like a charm. When I do the next hack can I go back to an increment of 1 with both boxes checked?
You rock dude, thanks a ton!
 
genkifilm said:
Thanks Mr Fanny! Setting the increment to 160 worked like a charm. When I do the next hack can I go back to an increment of 1 with both boxes checked?
You rock dude, thanks a ton!
Click to expand...


Just to say, pleased that you got it sorted - I bet panic was starting to set in? :D

I always tick both of the first two boxes - this always sets the firmware version at 0.0 (actually, 0.01 in the service menu)

I've never really understood the reason for checking one, and no the other - if you tick them both as a matter of course, you can't really go wrong.
 
genkifilm said:
Thanks Mr Fanny! Setting the increment to 160 worked like a charm. When I do the next hack can I go back to an increment of 1 with both boxes checked?
You rock dude, thanks a ton!
Click to expand...

glad it worked. once the version compare patch is done you just have to remember to have that ticked every time. ticking version increment is optional as the firmware is reverted back to 0.0 you will always be flashing with a 1.32 file so it will always accept. I tick it and leave it on 1 out of habbit myself like Mr Framerate =)
 
Bloody Hell am i glad I found this thread! Was in panic mode, mine also at 1.B with 160 increment it's 1.D but irellevant now as checked the other box too this time.

Reason I had to re-firmware is I finally reallised after months that the audio bitrate hack had made the camera stop recording whenever an audience clapped! Took me ages to figure out that was what was causing it, bought new faster bigger cards. Every time without fail, applause and stop. Never put the 2 things together until today when there were a lot of scenes and clapping in between, 5 times they both stopped at exactly same time.

Back to default 192 now, as I use separate audio recording device.

I need to find my original post about the camera stopping and update it sheepishly.
 
Reason I had to re-firmware is I finally reallised after months that the audio bitrate hack had made the camera stop recording whenever an audience clapped!
Click to expand...
Wow! I guess it's the Clapper sindrome. Clap off, clap on! LOL! I hope you solve the problem. Those things are the result of higher than normal bitrates. Somethings got to give when you push it way past the 24mbits Avchd is to max out.
 
Hi all,

I am at my wits end. I've been able to hack my GF2 without any problem. However I can't seem to hack my GH1 at all. I've read through this thread and I encounter the same problem. The current version on my GH1 is ver 1.B and I tried renaming the hacked firmware to 1.60 but my GH1 refuses to identify any firmware in the SD card. It just does not want to detect a firmware in the SD card. Please help. Thanks.
 
You must log in or register to reply here.
Back
Top