<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Simeon Pilgrim</title>
	
	<link>http://simeonpilgrim.com/blog</link>
	<description />
	<lastBuildDate>Mon, 14 May 2012 18:10:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/SimeonPilgrim" /><feedburner:info uri="simeonpilgrim" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Nikon D7000 Video Beta Testers Wanted</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/mwGCALaaCJ4/</link>
		<comments>http://simeonpilgrim.com/blog/2012/04/24/nikon-d7000-video-beta-testers-wanted/#comments</comments>
		<pubDate>Wed, 25 Apr 2012 01:14:20 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2376</guid>
		<description><![CDATA[Thanks to the testing efforts of Brett Dikeman we now have a verified D7000 version of the of the Time Restriction Removal patch. The FirmwarePatch tool has been updated to v1.2 and supports patching Nikon D3100 &#38; D5100 &#38; D7000 firmware. [Update &#8230; <a href="http://simeonpilgrim.com/blog/2012/04/24/nikon-d7000-video-beta-testers-wanted/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Thanks to the testing efforts of Brett Dikeman we now have a verified D7000 version of the of the Time Restriction Removal patch.</p>
<p>The <a href="http://nikon-firmware-tools.googlecode.com/files/FirmwarePatch_v1.2.exe">FirmwarePatch</a> tool has been updated to v1.2 and supports patching Nikon D3100 &amp; D5100 &amp; D7000 firmware.</p>
<p>[Update 24th April] A <a href="http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html">web-browser cross platform patch tool</a> is also available.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/04/24/nikon-d7000-video-beta-testers-wanted/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/mwGCALaaCJ4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/04/24/nikon-d7000-video-beta-testers-wanted/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/04/24/nikon-d7000-video-beta-testers-wanted/</feedburner:origLink></item>
		<item>
		<title>Web Browser Based Nikon Firmware Patch Tool</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/ynrHfS8fHEU/</link>
		<comments>http://simeonpilgrim.com/blog/2012/04/24/web-browser-base-nikon-patch-tool/#comments</comments>
		<pubDate>Tue, 24 Apr 2012 22:17:15 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2438</guid>
		<description><![CDATA[I have just released a Silverlight based patch tool. Thus it works on both Mac and Windows PC&#8217;s http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html It auto-detects the supported firmware models (D5100, D3100, D7000) and shows a list of available changes (current just one for each &#8230; <a href="http://simeonpilgrim.com/blog/2012/04/24/web-browser-base-nikon-patch-tool/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I have just released a Silverlight based patch tool. Thus it works on both Mac and Windows PC&#8217;s</p>
<p><a href="http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html">http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html</a></p>
<p>It auto-detects the supported firmware models (D5100, D3100, D7000) and shows a list of available changes (current just one for each model).</p>
<p>This will be how I&#8217;ll release future versions of patches.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/04/24/web-browser-base-nikon-patch-tool/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/ynrHfS8fHEU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/04/24/web-browser-base-nikon-patch-tool/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/04/24/web-browser-base-nikon-patch-tool/</feedburner:origLink></item>
		<item>
		<title>Nikon D3100 Video Beta Testers Wanted</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/CBvkL44l5q4/</link>
		<comments>http://simeonpilgrim.com/blog/2012/03/31/nikon-d3100-video-beta-testers-wanted/#comments</comments>
		<pubDate>Sat, 31 Mar 2012 20:43:32 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2366</guid>
		<description><![CDATA[Thanks to the testing efforts of 4cc3ss we now have a verified D3100 version of the Time Restriction Removal patch. The FirmwarePatch tool has been updated to v1.2 and supports patching Nikon D3100 &#38; D5100 &#38; D7000 firmware. [Update 24th April] A web-browser &#8230; <a href="http://simeonpilgrim.com/blog/2012/03/31/nikon-d3100-video-beta-testers-wanted/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Thanks to the testing efforts of <strong>4cc3ss</strong> we now have a verified D3100 version of the Time Restriction Removal patch.</p>
<p>The <a href="http://nikon-firmware-tools.googlecode.com/files/FirmwarePatch_v1.2.exe">FirmwarePatch</a> tool has been updated to v1.2 and supports patching Nikon D3100 &amp; D5100 &amp; D7000 firmware.</p>
<p>[Update 24th April] A <a href="http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html">web-browser cross platform patch tool</a> is also available.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/03/31/nikon-d3100-video-beta-testers-wanted/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/CBvkL44l5q4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/03/31/nikon-d3100-video-beta-testers-wanted/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/03/31/nikon-d3100-video-beta-testers-wanted/</feedburner:origLink></item>
		<item>
		<title>Nikon D5100 Video Beta Testers Wanted</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/AhZEK4Ba3bs/</link>
		<comments>http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/#comments</comments>
		<pubDate>Sat, 31 Mar 2012 03:44:59 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2355</guid>
		<description><![CDATA[The Nikon Hackers team would like to announce the release of the first hack for the D5100 (also D3100 &#38; D7000): Removing time limit restrictions on video recording. The FirmwarePatch tool is available here (now v1.2), it&#8217;s a .Net application, so &#8230; <a href="http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://nikonhacker.com/index.php">Nikon Hackers</a> team would like to announce the release of the first hack for the D5100 (also D3100 &amp; D7000): Removing time limit restrictions on video recording.</p>
<p>The <a href="http://nikon-firmware-tools.googlecode.com/files/FirmwarePatch_v1.2.exe">FirmwarePatch tool is available here</a> (now v1.2), it&#8217;s a .Net application, so you will need the 4.0 Framework installed. It should run under Mono.</p>
<p>[Update 24th April] A <a href="http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html">web-browser cross platform patch tool</a> is also available.</p>
<p>To use:</p>
<ol>
<li>Download the D5100/D3100/D7000 firmware</li>
<li>Download the FirmwarePatch tool</li>
<li>From a command prompt run the patch tool with the first argument pointing to the location of the above firmware</li>
<li>Copy the resulting output to your SD card and remove the &#8220;.patched&#8221; extension</li>
<li>Upgrade firmware from D5100 menu, as per the normal Nikon instructions</li>
</ol>
<p><strong><em>This should not brick your camera, but if it does I and the other Nikon Hacker team members will not have/take responsibility for any damages or liability. I have this firmware on my camera, and have taken a 25 minute video with it, but result may vary. Also damages that may occur due to camera operation times longer than specified by original manufacturer are your responsibility.</em></strong></p>
<p>The <a href="http://nikonhacker.com/index.php">Nikon Hacker forums</a> is the place for discussing this patch, future patchs, or just to get involved.</p>
<p>We would like to invite any interested developers to help progress the firmware decoding process.</p>
<p><del datetime="2012-04-02T22:11:57+00:00">Soon we will be releasing the same patch for D3100 and D7000 camera&#8217;s but we have not tested these patches at all, so we are looking for VERY KEEN Alpha testers to try it out these changes. Contact me directly (simeon@simeonpilgrim.com) if you are interested and don&#8217;t mind possibly bricking your camera. If you don&#8217;t know what bricking means, don&#8217;t apply.</del> <strong>All three tested and released.</strong></p>
<p><strong>[update]</strong> If you apply the patch please report results here or On this <a href="http://nikonhacker.com/viewtopic.php?f=2&amp;t=71">Nikon Hackers Forum  post</a></p>
<p><strong>[Update 31/3]</strong> v1.1 has been released with support for D3100 camera&#8217;s<br />
<strong>[Update 2/4]</strong> v1.2 has been released with support for D7000 camera&#8217;s</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/AhZEK4Ba3bs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/feed/</wfw:commentRss>
		<slash:comments>95</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/</feedburner:origLink></item>
		<item>
		<title>Nikon D5100 Video Record Time Limit Found</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/kH0hTpAfHnE/</link>
		<comments>http://simeonpilgrim.com/blog/2012/03/26/nikon-d5100-video-record-time-limit-found/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 07:29:37 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2343</guid>
		<description><![CDATA[I&#8217;ve found the memory location of the video recording limit (20 minutes on the D5100) and change it to 1 minute to allow for faster testing. Here&#8217;s a really exciting video where is stops record after 1 minute with no &#8230; <a href="http://simeonpilgrim.com/blog/2012/03/26/nikon-d5100-video-record-time-limit-found/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve found the memory location of the video recording limit (20 minutes on the D5100) and change it to 1 minute to allow for faster testing.</p>
<p>Here&#8217;s a really <em>exciting</em> video where is stops record after 1 minute with no user involvement.</p>
<p><iframe src="http://www.youtube.com/embed/G7T3rhJi_F0" frameborder="0" width="420" height="315"></iframe></p>
<p>[Update 40 minutes later]</p>
<p>The D3100 10 minute limit has been located, and the D7000 20 minute limit has also been located.</p>
<p>[Update 30th March]</p>
<p>Here&#8217;s a screen snap of a 25:59 minute video (1080P 30fps @18mbps) I just recorded on my D5100. At lowest quality settings (424 30fps @4mbps) it says I can record 59minutes of video, so I assume the it doesn&#8217;t display hours because 1h 59m @4mbp is 3.5GB which is around the size of my ~26m video.</p>
<p><a href="http://simeonpilgrim.com/blog/wp-content/uploads/2012/03/25min_movie.jpg"><img class="alignnone size-full wp-image-2353" title="25min_movie" src="http://simeonpilgrim.com/blog/wp-content/uploads/2012/03/25min_movie.jpg" alt="" width="640" height="241" /></a></p>
<p>[Update 1st April]<br />
Patch available from here: <a href="http://simeonpilgrim.com/blog/2012/03/30/nikon-d5100-video-beta-testers-wanted/" rel="next">Nikon D5100 Video Beta Testers Wanted</a></p>
<p>[Update 24th April] A <a href="http://simeonpilgrim.com/nikon-patch/Nikon-Patch.html">web-browser cross platform patch tool</a> is also available.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/03/26/nikon-d5100-video-record-time-limit-found/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/kH0hTpAfHnE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/03/26/nikon-d5100-video-record-time-limit-found/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/03/26/nikon-d5100-video-record-time-limit-found/</feedburner:origLink></item>
		<item>
		<title>Nikon J1/V1 Firmware decoded</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/K902LXvsAVc/</link>
		<comments>http://simeonpilgrim.com/blog/2012/03/18/nikon-j1v1-firmware-decoded/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 01:58:38 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firmware]]></category>
		<category><![CDATA[nikon]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2323</guid>
		<description><![CDATA[I started looking at the J1/V1 firmware last weekend. As compared to the DSLR firmware the XOR pattern is different, but using knowledge from the D5100 firmware, I made very quick progress getting past the first two XOR layers, the &#8230; <a href="http://simeonpilgrim.com/blog/2012/03/18/nikon-j1v1-firmware-decoded/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I started looking at the J1/V1 firmware last weekend.</p>
<p>As compared to the DSLR firmware the XOR pattern is different, but using knowledge from the D5100 firmware, I made very quick progress getting past the first two XOR layers, the third was a little tricky.</p>
<p>Then yesterday, I got an email from Петр Кудинов that showed where in the D5100 firmware the XOR tables were stored. With this new insight (that they were stored verse calculated) I proceeded to search for what I had already found of the V1 XOR pattern in that firmware, and struck gold.</p>
<p>Here is the firmware based patterns used to decode the V1 and J1 firmware:</p>
<pre class="brush: plain; title: ; notranslate">
static byte[] Xor_Ord1_5 = {
	0xBB, 0x85, 0x12, 0xA7, 0xD7, 0x11, 0x15, 0x30, 0x53, 0x5C, 0x72, 0xCA, 0x61, 0x9F, 0xA3, 0xAC,
	0x2D, 0xC7, 0x05, 0x9C, 0xDF, 0x22, 0x37, 0xF5, 0x93, 0x6F, 0x24, 0x6B, 0x98, 0xB2, 0x0D, 0x44,
	0x8B, 0xCD, 0x3D, 0x33, 0x65, 0xF3, 0xF7, 0x52, 0x89, 0xB7, 0x34, 0x26, 0x79, 0x8F, 0xC1, 0x84,
	0x87, 0x07, 0x3A, 0xE2, 0xE0, 0x0C, 0xA1, 0xF0, 0xA0, 0x77, 0x4A, 0x7E, 0xFF, 0x25, 0xB6, 0x9D,
	0x4F, 0x36, 0xF4, 0xC8, 0xA9, 0xA8, 0x70, 0x00, 0x99, 0xC3, 0x32, 0x2A, 0x1F, 0xDA, 0x9B, 0x64,
	0xEA, 0xBA, 0x63, 0xC2, 0x23, 0xAF, 0xBF, 0x2C, 0x39, 0x16, 0x9E, 0x6D, 0xDC, 0x31, 0x02, 0x19,
	0x2F, 0x47, 0xAE, 0xE3, 0x5B, 0x74, 0x0F, 0x71, 0xD4, 0xFE, 0x50, 0xD6, 0x3E, 0xD0, 0x18, 0xA4,
	0xE8, 0x29, 0x80, 0x5A, 0x7D, 0xE5, 0x45, 0xE1, 0x62, 0x6C, 0xE6, 0xB5, 0x9A, 0x78, 0xA5, 0x7B,
	0x03, 0x81, 0x27, 0xB0, 0x06, 0xF1, 0xE7, 0x8E, 0xD2, 0xD9, 0x1E, 0x3F, 0x5E, 0x95, 0xED, 0xFA,
	0x20, 0x90, 0xEE, 0xFD, 0xDD, 0x4E, 0xDB, 0x6A, 0x82, 0x7A, 0x56, 0x1B, 0x8A, 0x1C, 0x09, 0x57,
	0x6E, 0x2B, 0xE4, 0x04, 0xAB, 0x67, 0xDE, 0xF6, 0x1D, 0x2E, 0x46, 0x86, 0x8C, 0xCB, 0xB8, 0x14,
	0x66, 0x10, 0xD1, 0xF2, 0x8D, 0x08, 0x54, 0xB4, 0x42, 0xF8, 0x49, 0xD5, 0x75, 0xBE, 0x76, 0x68,
	0x51, 0x7C, 0xEF, 0x96, 0xCE, 0x0E, 0xE9, 0xEB, 0x41, 0x28, 0x59, 0xEC, 0xB1, 0x13, 0x91, 0x40,
	0x0A, 0xCF, 0x5D, 0x01, 0xC9, 0x3B, 0xC0, 0xAA, 0x88, 0xC5, 0x92, 0x38, 0x4B, 0x5F, 0xD3, 0xA6,
	0x69, 0xA2, 0x35, 0x58, 0xFB, 0xC6, 0x0B, 0x17, 0x7F, 0x21, 0x3C, 0x83, 0xBC, 0xCC, 0x4D, 0x97,
	0xC4, 0x60, 0x48, 0xF9, 0xBD, 0x73, 0xB9, 0xB3, 0x1A, 0x55, 0xD8, 0x4C, 0xAD, 0xFC, 0x43, 0x94
	};

static byte[] Xor_Ord2_5 = {
	0xB6, 0x0A, 0x9C, 0xBF, 0x54, 0x5C, 0x80, 0x8F, 0xFE, 0x1E, 0xF9, 0x3A, 0x8C, 0xEA, 0x78, 0x2A,
	0x01, 0xF7, 0x56, 0x38, 0x39, 0xE5, 0x72, 0xE6, 0x44, 0x0C, 0x41, 0x73, 0x82, 0x34, 0xCD, 0xC2,
	0x14, 0x37, 0xC7, 0xBD, 0xD3, 0xF3, 0x29, 0xAA, 0x8D, 0xC5, 0xE4, 0xEB, 0x9D, 0xE9, 0xFB, 0xF1,
	0x1F, 0x7D, 0x07, 0x93, 0x53, 0x95, 0x4A, 0x24, 0x05, 0x4D, 0xCE, 0x7E, 0x7F, 0x28, 0x22, 0xC8,
	0x6E, 0x40, 0x55, 0xE3, 0x65, 0xC3, 0x3B, 0x0F, 0xE2, 0xDC, 0xED, 0xBC, 0x1B, 0x61, 0xEF, 0x0B,
	0x92, 0x99, 0x1D, 0x64, 0x8E, 0x7C, 0xE1, 0x60, 0xAF, 0xA6, 0x85, 0xEC, 0x4C, 0xB8, 0x69, 0x23,
	0xDB, 0xBA, 0xCC, 0xC6, 0xEE, 0x0D, 0x27, 0x43, 0xF8, 0x11, 0x32, 0xFC, 0x75, 0xD1, 0xA1, 0x20,
	0x71, 0x63, 0x88, 0x2B, 0xD9, 0x2E, 0x89, 0x68, 0x3C, 0xF4, 0xDF, 0x33, 0xFD, 0xAC, 0x6C, 0xB3,
	0x19, 0xC1, 0x10, 0x57, 0x17, 0xFA, 0x79, 0xCF, 0x13, 0xF2, 0x86, 0x35, 0x51, 0xB1, 0xD5, 0xCB,
	0xA3, 0xAE, 0x94, 0x03, 0x5F, 0xD8, 0x6B, 0x31, 0x74, 0x81, 0xBB, 0x3D, 0x15, 0x16, 0xF6, 0xB5,
	0x4B, 0xF5, 0x77, 0x6F, 0x49, 0xA8, 0xA7, 0xCA, 0xAD, 0x02, 0x9A, 0x5E, 0x59, 0x25, 0x98, 0x62,
	0x1A, 0xB7, 0x9F, 0x2F, 0xA0, 0x76, 0x6D, 0xB4, 0x47, 0xB0, 0xA9, 0x06, 0xDA, 0x2D, 0x5B, 0xD7,
	0x8A, 0x66, 0x7B, 0xA5, 0xFF, 0x6A, 0xB9, 0xE0, 0xBE, 0x9E, 0x2C, 0x36, 0xF0, 0xD2, 0xD0, 0x97,
	0x26, 0x3E, 0xA2, 0x08, 0x5D, 0x58, 0x4F, 0x91, 0x70, 0x8B, 0xC0, 0x90, 0x0E, 0x00, 0x5A, 0xE7,
	0x45, 0x87, 0xB2, 0x83, 0x1C, 0xC4, 0x52, 0xD4, 0x96, 0xDE, 0x21, 0x04, 0x7A, 0x3F, 0x12, 0x30,
	0x67, 0x50, 0x09, 0x48, 0x42, 0xAB, 0xD6, 0xDD, 0x9B, 0xA4, 0x18, 0xE8, 0xC9, 0x4E, 0x46, 0x84
	};

static byte[] Xor_Ord3_5 = {
	0xBF, 0xB7, 0x80, 0x05, 0x48, 0xDA, 0xF0, 0x77, 0xA0, 0x93, 0xE5, 0x0C, 0x07, 0x69, 0xE7, 0x2F,
	0xF4, 0x0D, 0x6F, 0xD4, 0x2C, 0x3B, 0x1E, 0x43, 0x71, 0xF5, 0x1A, 0xA8, 0x57, 0x31, 0x4B, 0x6D,
	0x35, 0x8E, 0xC8, 0x92, 0xED, 0x0F, 0xC2, 0xD7, 0xB9, 0x58, 0xB2, 0xC5, 0x7B, 0x18, 0x4A, 0x98,
	0x3C, 0x11, 0xBB, 0xFD, 0xAA, 0x41, 0xB5, 0x17, 0xE1, 0xF3, 0x22, 0x5B, 0xE4, 0x19, 0x9B, 0x42,
	0x81, 0xFF, 0x21, 0xA2, 0x64, 0xB1, 0x5E, 0x23, 0xC0, 0xDE, 0x28, 0xFC, 0x99, 0xF1, 0x0E, 0x9A,
	0x50, 0xB3, 0x09, 0x1B, 0xEC, 0x4D, 0x51, 0x6B, 0xD2, 0x33, 0x90, 0x79, 0x5D, 0x97, 0xB0, 0x60,
	0x1D, 0x63, 0xEF, 0xE9, 0x8F, 0x87, 0x75, 0x06, 0xBC, 0x68, 0xA5, 0x13, 0xD1, 0x26, 0x38, 0x82,
	0xBA, 0x04, 0x10, 0x56, 0xAF, 0x34, 0x62, 0x3E, 0x30, 0x5C, 0xAC, 0xE2, 0x91, 0x45, 0x2B, 0xCB,
	0xEE, 0x47, 0x2E, 0xB8, 0xA9, 0x96, 0xA3, 0x7C, 0xFE, 0xB6, 0xE0, 0xD3, 0xA6, 0xDF, 0x59, 0x84,
	0x32, 0xBD, 0xD5, 0xC6, 0x39, 0xA1, 0xA7, 0xBE, 0xAD, 0x4E, 0x66, 0x2D, 0xF8, 0x9E, 0xDC, 0xC7,
	0x7D, 0x03, 0x70, 0x40, 0x20, 0x8B, 0xE6, 0xD9, 0x7E, 0x85, 0xCC, 0x8A, 0x01, 0x16, 0xE8, 0x5A,
	0xAB, 0x4C, 0x74, 0x2A, 0x3D, 0xC9, 0x72, 0x29, 0xE3, 0x7F, 0x52, 0x94, 0x0A, 0x89, 0x8C, 0x37,
	0x1C, 0xEA, 0x3A, 0xD6, 0x6A, 0xB4, 0xC1, 0x65, 0x55, 0x3F, 0xF6, 0x08, 0x36, 0x95, 0x0B, 0x9F,
	0x73, 0xCD, 0x7A, 0x15, 0xCE, 0x9C, 0x14, 0xCF, 0x46, 0xFB, 0x02, 0xCA, 0xDB, 0x88, 0xF9, 0xC4,
	0x49, 0xEB, 0xDD, 0x6C, 0x00, 0x4F, 0x6E, 0xF2, 0x67, 0x24, 0xD0, 0x25, 0x9D, 0x54, 0xA4, 0xAE
	};
</pre>
<p>Of interest is that the file is packaged the same as the newer DSLR firmware files, but that the A firmware is the larger file, while the B firmware is tiny.</p>
<p>I have no plan to start work on a J1/V1 firmware hack presently, as the D5100 work is all occupying, but people are welcome to come over to the <a href="http://nikonhacker.com/index.php">Nikon Hacker forums</a>, and discuss this work if they would like to progress it, or help with the DSLR work.</p>
<p>[Update] The A firmware does not appear to be a Fujitsu FR CPU like the DSLR are.</p>
<p>Also there are references to &#8220;SANYO&#8221; and &#8220;SANYO Digital Camera&#8221; in A firmware, how very strange Nikon.</p>
<p>[Update: 25th March - Thanks to Петр for pointing out that I had a row missing from table three due to cut'n'paste errors]</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/03/18/nikon-j1v1-firmware-decoded/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/K902LXvsAVc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/03/18/nikon-j1v1-firmware-decoded/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/03/18/nikon-j1v1-firmware-decoded/</feedburner:origLink></item>
		<item>
		<title>New Transformers are Crazy Hard</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/JHHOpn8vaVc/</link>
		<comments>http://simeonpilgrim.com/blog/2012/01/04/new-transformers-are-crazy-hard/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 13:02:39 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Toys]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2173</guid>
		<description><![CDATA[When I was ten, Transformers where not that hard to transform. Meet modern Bumblebee, This transformer was crazy hard to transform, in the couple of days I was visting with the 4 year old owner, the head &#8220;popped off&#8221; multiple &#8230; <a href="http://simeonpilgrim.com/blog/2012/01/04/new-transformers-are-crazy-hard/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When I was ten, Transformers where not that hard to<em> transform</em>.</p>
<p>Meet modern <a href="http://en.wikipedia.org/wiki/Bumblebee_(Transformers)">Bumblebee</a>,</p>
<p><img class="alignnone size-full wp-image-2174" title="Bumblebee" src="http://simeonpilgrim.com/blog/wp-content/uploads/2012/01/Bumblebee.jpg" alt="" width="312" height="448" /></p>
<p>This transformer was crazy hard to transform, in the couple of days I was visting with the 4 year old owner, the head &#8220;popped off&#8221; multiple times, and I couldn&#8217;t get it back on without feeling I was going to break the toy. Lucky said child&#8217;s mother had the magic touch.</p>
<p>But transforming challenge aside, it was a pretty cool model/toy. Just not like the <a href="http://en.wikipedia.org/wiki/Starscream">Starscream</a> or <a href="http://en.wikipedia.org/wiki/Optimus_Prime">Optimus Prime</a> of my days gone by&#8230;.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/01/04/new-transformers-are-crazy-hard/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/JHHOpn8vaVc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/01/04/new-transformers-are-crazy-hard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/01/04/new-transformers-are-crazy-hard/</feedburner:origLink></item>
		<item>
		<title>Expectation Stress</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/72K4Rbv4D68/</link>
		<comments>http://simeonpilgrim.com/blog/2012/01/04/expectation-stress/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 12:48:44 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2170</guid>
		<description><![CDATA[Wow, since doing the easy work of decrypting the newer Nikon firmware, I&#8217;ve felt an immense pressure to pull another rabbit from the hat, when in reality the last reversing engineering project I worked on took years (2-5), and thus I feeling real burnt out. a) due to trying &#8230; <a href="http://simeonpilgrim.com/blog/2012/01/04/expectation-stress/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Wow, since doing the easy work of decrypting the newer Nikon firmware, I&#8217;ve felt an immense pressure to pull another rabbit from the hat, when in reality the last reversing engineering project I worked on took years (2-5), and thus I feeling real burnt out. a) due to trying to find the next &#8220;cool&#8221; insight, and 2) wanting to be part of the action, and keep up with others are finding.  (<em>the index scheme is an insiders joke</em>)</p>
<p>To this end, I point would-be-helpers to <a href="http://nikonhacker.com/index.php">nikonhacker.com</a>, I&#8217;ve been contributing there, as best I can.</p>
<p>It&#8217;s very addictive having such large inflows of traffic to your site/blog, that I was reluctant to redirect it, but I have also felt since November a presure not to post stupid stuff like I used too, or am about to post, thus have been silent (besides the travel and working on things that are not up for chatter).</p>
<p>So there&#8217;s <strong>my</strong> Nikon update&#8230;. I have been having a good family holiday..</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/01/04/expectation-stress/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/72K4Rbv4D68" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/01/04/expectation-stress/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/01/04/expectation-stress/</feedburner:origLink></item>
		<item>
		<title>Monopoly Deal</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/7nj0wG6De54/</link>
		<comments>http://simeonpilgrim.com/blog/2012/01/04/monopoly-deal/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 12:29:35 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Games]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2166</guid>
		<description><![CDATA[The family was given Monopoly Deal for Christmas, and it&#8217;s a fantastic game. My first game was a six person double deck game, which was slower, and very brutal. Since then I have played many a game with Jacob (single &#8230; <a href="http://simeonpilgrim.com/blog/2012/01/04/monopoly-deal/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://simeonpilgrim.com/blog/wp-content/uploads/2012/01/Monopoly_Deal.jpeg"><img class="size-full wp-image-2167 alignright" title="Monopoly_Deal" src="http://simeonpilgrim.com/blog/wp-content/uploads/2012/01/Monopoly_Deal.jpeg" alt="" width="300" height="300" /></a>The family was given <a href="http://en.wikipedia.org/wiki/Monopoly_Deal">Monopoly Deal</a> for Christmas, and it&#8217;s a fantastic game.</p>
<p>My first game was a six person double deck game, which was slower, and very brutal. Since then I have played many a game with Jacob (single player) and it&#8217;s fast and fun.</p>
<p>In fine to twenty minutes, you can compact all the fun and rage of the full 4 hour game, but it&#8217;s done, and you can move on so much quicker. It has stealing, ripping people off, double crossing, saying no (it&#8217;s a card, but it the best feeling in the game rejecting a big play, just watch out for the reverse no,back at you&#8230;).</p>
<p>It&#8217;s a very fun game, and while there it can have all the rage of the original it, also can be started and finished within 30 minutes.. so many hands can be played giving the &#8220;balance&#8221; missing from Monopoly.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/01/04/monopoly-deal/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/7nj0wG6De54" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/01/04/monopoly-deal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/01/04/monopoly-deal/</feedburner:origLink></item>
		<item>
		<title>IDA Script: Fixing 16bit pushed data segment references</title>
		<link>http://feedproxy.google.com/~r/SimeonPilgrim/~3/Uxo5VRZXhuo/</link>
		<comments>http://simeonpilgrim.com/blog/2012/01/03/ida-script-fixing-16bit-pushed-data-segment-references/#comments</comments>
		<pubDate>Tue, 03 Jan 2012 20:18:36 +0000</pubDate>
		<dc:creator>Simeon</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[ida-pro]]></category>
		<category><![CDATA[idc script]]></category>

		<guid isPermaLink="false">http://simeonpilgrim.com/blog/?p=2152</guid>
		<description><![CDATA[A good friend has started reversing an old 16bit Borland C++ (3.1?) program, and had lots of stack push data segment offsets that were not correctly cross referencing. After telling him the shortcuts for manually fixing the issue (press O &#8230; <a href="http://simeonpilgrim.com/blog/2012/01/03/ida-script-fixing-16bit-pushed-data-segment-references/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>A good friend has started reversing an old 16bit Borland C++ (3.1?) program, and had lots of stack push data segment offsets that were not correctly cross referencing.</p>
<p>After telling him the shortcuts for manually fixing the issue (press <strong>O</strong> for the data segment, or <strong>Alt-R</strong> for any segment offset), he wrote an IDC script to do it en mass.</p>
<p>Thus (made up example code)</p>
<pre class="brush: plain; title: ; notranslate">

push ds;

mov ax, 0x1234;

push ax
</pre>
<p>should look like:</p>
<pre class="brush: plain; title: ; notranslate">

push ds;

mov ax, ds:dword_1234;

push ax
</pre>
<p>Here&#8217;s his script:</p>
<pre class="brush: plain; title: ; notranslate">
#include &lt;idc.idc&gt;

static main()
{
    auto seg, loc;
    auto movloc, movtarget;
    auto xref;
    auto dsegbase;

    dsegbase = SegByName(&quot;dseg&quot;) * 16;
    Message(&quot;dsegbase=%x\n&quot;, dsegbase);

    Message(&quot;========================================\n&quot;);
    seg = FirstSeg();

    while(seg != BADADDR )
    {
        Message(&quot;----------------------------------------\n&quot;);

        loc = SegStart(seg);

        if( Byte(loc) != 0xCD || Byte(loc+1) != 0x3F)
        {
            Message(&quot;Fixing indirect push [ds:xx] refs from %s\n&quot;, SegName(seg));

            while(loc != BADADDR &amp;&amp; loc &lt; SegEnd(seg))
            {
                if (GetMnem(loc) != &quot;push&quot; || GetOpnd(loc, 0) != &quot;ds&quot;)
                {
                    loc = NextHead(loc, BADADDR);
                    continue;
                }
                loc = NextHead(loc, BADADDR);

                if (GetMnem(loc) != &quot;mov&quot; || GetOpType(loc, 1) != o_imm)
                {
                    loc = NextHead(loc, BADADDR);
                    continue;
                }
                movloc = loc;
                movtarget = GetOpnd(movloc, 0);
                loc = NextHead(loc, BADADDR);

                if (GetMnem(loc) != &quot;push&quot; || GetOpnd(loc, 0) != movtarget)
                {
                    continue;
                }

                // At this point, we know we're pushing a [ds:x] combo.
                //Message(&quot;%x: mov %s, %s\n&quot;, movloc, movtarget, GetOpnd(movloc, 1));

                // Abort if there already exists a Dxref
                xref = Dfirst(movloc);
                if (xref != BADADDR)
                {
                    continue;
                }

                Message(&quot;  Updating %s:%04x\n&quot;, SegName(seg), (movloc - seg) &amp; 0xffff);
                OpOff(movloc, 1, dsegbase);
            }
        }

        seg = NextSeg(seg);
    }
}
</pre>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="medium" count="1" href="http://simeonpilgrim.com/blog/2012/01/03/ida-script-fixing-16bit-pushed-data-segment-references/"></g:plusone></div><img src="http://feeds.feedburner.com/~r/SimeonPilgrim/~4/Uxo5VRZXhuo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://simeonpilgrim.com/blog/2012/01/03/ida-script-fixing-16bit-pushed-data-segment-references/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://simeonpilgrim.com/blog/2012/01/03/ida-script-fixing-16bit-pushed-data-segment-references/</feedburner:origLink></item>
	</channel>
</rss>

