Looking for D3200 Alpha Testers

I just released v1.13 of the online patch tool today, and it has the time limit removed for D3200 movie recording, but…. it’s not been tested, as none of the core developers have a D3200.

So we need a brave soul to test it for us. If keen come on over to the forum and let us know so we don’t have 100 people all trying it at once. ;-)

9 thoughts on “Looking for D3200 Alpha Testers”

  1. I noticed that “D5100 NEF Compression Lossless NEF ” is not beta version anymore. It’s so cool, thank you!

  2. That was due to no reported issues, but then again I don’t have any usage stats ether… that might be an interesting thing to add to the Google Analytics.

  3. Hello Simeon,

    First, i would like to thank you for all the research you did on the Nikon product.
    And here my question.

    1 year ago you reveal that you can decode the firmware Nikon V1 and i was wondering if today you find a way to exploit the Firmware Nikon V1 or not ? did you made any program or patch for the Nikon V1 ?

    I try to check inside the firmware and i saw that Nikon block some features on purpose (like better frame buffer or slow motion HD, the Aptina can easily record in 4K or offer a better quality of slow motion) it’s too bad that Nikon block that ability of the Nikon V1… it look like a BMCC Pocket blocked

    Surely we can improve the performance and features of the Nikon V1 and offer more possibility to this camera.

    If you want i can test any custom firmware or patch that you want to test on the Nikon V1, please let me know

    Also do you have any idea where i can find a firmware Nikon V1 already decrypted ?
    and did you release any tool to be able to reencrypt everythings or force a flash firmware without asking any secure ?

    Thanks

  4. 1 year ago you reveal that you can decode the firmware Nikon V1 and i was wondering if today you find a way to exploit the Firmware Nikon V1 or not ? did you made any program or patch for the Nikon V1 ?

    We tested and found the encoding of the firmware package file was the same/similar to that of the DSLR firmware bundles. We didn’t actually find what processor was used, so not reverse engineering was done. Maybe the processor was found, but it was different what I was use to reading to all look Russian to me.

    I try to check inside the firmware and i saw that Nikon block some features on purpose (like better frame buffer or slow motion HD, the Aptina can easily record in 4K or offer a better quality of slow motion) it’s too bad that Nikon block that ability of the Nikon V1… it look like a BMCC Pocket blocked

    Surely we can improve the performance and features of the Nikon V1 and offer more possibility to this camera.

    If you want i can test any custom firmware or patch that you want to test on the Nikon V1, please let me know

    There is nothing to test.

    Also do you have any idea where i can find a firmware Nikon V1 already decrypted ? and did you release any tool to be able to reencrypt everythings or force a flash firmware without asking any secure ?

    The code to decrypt the file bundles is on the Google code project, but we didn’t rebundle that code, but it’s should just be a matter of reversing the process of bundling…

  5. I didn’t expect a fast answer :).
    Thank again Simeon
    By the way, can you confirm the absence of a debug menu on the Nikon DSLR/Nikon 1 Products ?
    I didn’t find anything about that, i was hoping to see Nikon leave some debug command but actually everything on the Nikon Products is bug free.

    About the Processor or anything else on the Nikon 1 V1, chipworks give a lot of information and clue.
    http://www.chipworks.com/blog/recentteardowns/2011/11/04/teardown-of-the-nikon-v1-camera-aptina-found/

    If this can help :)

    Well the code to decrypt i saw, look like a partial code, nothing is missed ?

  6. On the D5100, I can confirm there’s no hidden menu’s as I’ve decoded all that data, unless the menu is 100% code driven, while the rest of the menu’s are very data driven.

    The tear down just say “nikon chip” or more or less that and just quote Nikon marketing.

    The code correctly pulls the two J1/V1 A & B firmware files.

  7. Ok, so I looked again at the J1 firmware, and the A firmware is an ARM processor, like noted on the web, and you should load the file as memory location 0x80000.

  8. Hmm, sorry to hear that. I assume it’s using dcraw under the hood, as this doesn’t seem to handle the files correctly.

Comments are closed.