Personal View site logo
Official GH2 "Stalin" hack development topic
  • 939 Replies sorted by
  • rozrozrozroz
    hi Vitaliy,
    can you see any possibility for a 4:3 aspect by now (and will it ever be possible for AVCHD)?
    thanks.
  • oddodd
    Hi Vitaliy,
    hope the donation helps!
    We're all with you!!
  • Vitaliy_KiselevVitaliy_Kiselev
    >You think that's a possibility?

    Yes.

    Thanks for donation.
  • gbevingbevin
    I just sent money your way. I'm eagerly waiting for a GH2 firmware so that the 30 min recording limitation on my European model would be removed. You think that's a possibility?
  • bennybricenobennybriceno
    Vitaliy!!!!

    I donated...
    Can't wait to see what you do with the GH2!!!
    Thank you for what you are doing!
  • Vitaliy_KiselevVitaliy_Kiselev
    >So I suppose that maybe the last GH1 firmware expects a new firmware to be signed and encrypted in a similar way as the GH2 firmware.

    I do not think so :-)
    Until we'll have dump for GH1 it is pure specialations.
    With same approach I could declare that it is alien form of life injected in each of new GH1 bosy that prevents update :-)
  • kinokino
    >GH1 firmware is not encrypted.>

    Sorry, you are right! I was just thinking about this scenario: we know that the last GH1 firmware does not allow any update with the old firmware (even cheating on firmware vesion). So I suppose that maybe the last GH1 firmware expects a new firmware to be signed and encrypted in a similar way as the GH2 firmware. The GH2 routine in charge of acknowledge the new firmware could be, hopefully, the same.
  • jpchavezjpchavez
    >GH1 firmware is not encrypted.>

    thats amazing, thanks for the good news vitaly
  • Vitaliy_KiselevVitaliy_Kiselev
    > does the encryption algorithm used for the GH2 firmware is the same (or similar) to the last GH1 firmware?

    GH1 firmware is not encrypted.
  • LliamWLliamW
    Sounds like you are making excellent progress Vitaliy.
    This is not a surprise but wonderful and impressive none the less.

    As I'm in Australia where the GH2 is completely non existent and may be for quite awhile still, I'm forced to either wait... or try to buy now from Hong Kong or Japan... I raise this as I'm just a little concerned Panasonic may seek to change the next batch of cameras like they did with the second wave so to speak of GH1's... Fearful speculation on my behalf I realise, but a reasonable concern perhaps you think? I'd value your opinion.

    Best
    LW
  • kinokino
    Hi

    does the encryption algorithm used for the GH2 firmware is the same (or similar) to the last GH1 firmware?
    thanks!
  • Mark_the_HarpMark_the_Harp
    @Vitaliy - thank you - your outline of the process makes perfect sense!

    Good luck - and yes, good name for the hack!
  • otcxotcx
    Name of the hack is outstanding, like GH2 itself
  • Vitaliy_KiselevVitaliy_Kiselev
    @minsat

    For now I do not work on encryption anymore (but return to it after first patches will be ready and body will be in my hands).
    As soon as I'll have time I'll start moving all reversing to latest available firmware (from 1.0C that I used).
    It'll become main database (as was 1.22 for GH1).
  • mistanmistan
    So, we're at the point where you're just fiddling around with the coding and seeing what all you can change/add/remove? Then you have to run a few patch/encrypting tests to make sure it all goes smoothly. Then after that you're going o work on cleaning up the code for it? Would this be a fair assumption?

    Don't mean to hound you about your status/progress...
  • Vitaliy_KiselevVitaliy_Kiselev
    >Do you have a page somewhere that describes the process of what you're doing?

    I try to get some progress notices here.
    You can also see one more similar screen in TZ10 related topic (TZ10 firmware is more complicated and consists of many more parts, like resources, etc).
    To be short - we need to be able to decrypt, patch and encrypt back firmware.
    So, most things considering first and third steps are done (not final code, of course).
  • Mark_the_HarpMark_the_Harp
    Ah, sorry. I realise how little I understand about it. Do you have a page somewhere that describes the process of what you're doing? But not, if it distracts you from doing it! :-)
  • Vitaliy_KiselevVitaliy_Kiselev
    >So, one is a decrypted version of the other?

    What do you mean?
    Screenshots?
    They are from two different decrypted parts of 1.0D firmware.
  • Mark_the_HarpMark_the_Harp
    So, one is a decrypted version of the other?
  • stefanosstefanos
    >Here is small hex parts of decrypted 1.0D firmware content (program and eeprom)

    I wish I new what all that meant:) So what's the next step after a good night's sleep?
  • Vitaliy_KiselevVitaliy_Kiselev
    > Will you work be applicable to firmware v1.0? I have a US camera with version 1.0.

    In reality multiple firmware versions exists.
    Dumped version was 1.0C, decrypted and publically available is 1.0D.
    I know some rumors about 1.0E.
    All of them show as 1.0 in version display :-)
  • Dusty42Dusty42
    Vitaliy,

    Will you work be applicable to firmware v1.0? I have a US camera with version 1.0.
  • johnnymjohnnym
    great news
  • Vitaliy_KiselevVitaliy_Kiselev
    Here is small hex parts of decrypted 1.0D firmware content (program and eeprom)

    image

    image
    revers3.png
    679 x 201 - 8K
    revers4.png
    725 x 202 - 19K
  • Rev_BenjaminRev_Benjamin
    Awesome job man! Donated, good luck! Ps: If you're interested in seeing some of my hdslr filmmaking, would love to share what I'll end up using the hack for!
Add a Comment