<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>
	Comments on: Ricoh Theta S Updater and Firmware Analysis	</title>
	<atom:link href="https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/</link>
	<description>mpetroff.net</description>
	<lastBuildDate>Wed, 30 Nov 2016 02:00:25 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: crypto512		</title>
		<link>https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255372</link>

		<dc:creator><![CDATA[crypto512]]></dc:creator>
		<pubDate>Fri, 23 Sep 2016 22:20:17 +0000</pubDate>
		<guid isPermaLink="false">https://mpetroff.net/?p=2236#comment-255372</guid>

					<description><![CDATA[Found my decoder here; will normally works will all Ricoh firmware.
https://github.com/crypto512/ricohdec]]></description>
			<content:encoded><![CDATA[<p>Found my decoder here; will normally works will all Ricoh firmware.<br />
<a href="https://github.com/crypto512/ricohdec" rel="nofollow ugc">https://github.com/crypto512/ricohdec</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Gi Pi		</title>
		<link>https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255065</link>

		<dc:creator><![CDATA[Gi Pi]]></dc:creator>
		<pubDate>Sun, 04 Sep 2016 09:02:02 +0000</pubDate>
		<guid isPermaLink="false">https://mpetroff.net/?p=2236#comment-255065</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255055&quot;&gt;Matthew Petroff&lt;/a&gt;.

Indeed some files are not updated but I tried ThetaS-firmware-opening.ipynb (changing the firmware filename) and I obtained a new file with a lot of readable strings like @0x0011d1d4

TOPPERS/ASP Kernel Release %d.%X.%d for CRYSTAL(ARM946) (Jul  4 2016, 09:49:25)
Copyright (C) 2000-2003 by Embedded and Real-Time Systems Laboratory
                            Toyohashi Univ. of Technology, JAPAN
Copyright (C) 2004-2014 by Embedded and Real-Time Systems Laboratory
            Graduate School of Information Science, Nagoya Univ., JAPAN

The algorithm is not perfect, some strings have the case flipped, An xml file exists at 0x2ce85a but after some tags become garbage.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255055">Matthew Petroff</a>.</p>
<p>Indeed some files are not updated but I tried ThetaS-firmware-opening.ipynb (changing the firmware filename) and I obtained a new file with a lot of readable strings like @0x0011d1d4</p>
<p>TOPPERS/ASP Kernel Release %d.%X.%d for CRYSTAL(ARM946) (Jul  4 2016, 09:49:25)<br />
Copyright (C) 2000-2003 by Embedded and Real-Time Systems Laboratory<br />
                            Toyohashi Univ. of Technology, JAPAN<br />
Copyright (C) 2004-2014 by Embedded and Real-Time Systems Laboratory<br />
            Graduate School of Information Science, Nagoya Univ., JAPAN</p>
<p>The algorithm is not perfect, some strings have the case flipped, An xml file exists at 0x2ce85a but after some tags become garbage.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Matthew Petroff		</title>
		<link>https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255055</link>

		<dc:creator><![CDATA[Matthew Petroff]]></dc:creator>
		<pubDate>Sat, 03 Sep 2016 19:10:17 +0000</pubDate>
		<guid isPermaLink="false">https://mpetroff.net/?p=2236#comment-255055</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255053&quot;&gt;Gi Pi&lt;/a&gt;.

I had tried to find previous work on Ricoh&#039;s firmware but was unsuccessful. That repository looks quite interesting, but, sadly, there&#039;s no documentation, and I&#039;m getting errors when I try to run some of the notebooks.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255053">Gi Pi</a>.</p>
<p>I had tried to find previous work on Ricoh&#8217;s firmware but was unsuccessful. That repository looks quite interesting, but, sadly, there&#8217;s no documentation, and I&#8217;m getting errors when I try to run some of the notebooks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Gi Pi		</title>
		<link>https://mpetroff.net/2016/08/ricoh-theta-s-updater-and-firmware-analysis/#comment-255053</link>

		<dc:creator><![CDATA[Gi Pi]]></dc:creator>
		<pubDate>Sat, 03 Sep 2016 17:26:31 +0000</pubDate>
		<guid isPermaLink="false">https://mpetroff.net/?p=2236#comment-255053</guid>

					<description><![CDATA[Maybe I can help you: I read your post and I get really interested to decode the firmware: looking at the data seems obvious that it&#039;s neither (block) encrypted neither compressed since there are large blocks with constant data; I lose my mind for a day and looking at github I found a repository where a guy smarter than me sorted this out: roughly speaking the firmware is xored 0x200 bytes at times with a key of four bytes (the bytes that repeat along the block probably).

The repository is here https://github.com/trolldbois/theta/blob/master/ThetaS-firmware-opening.ipynb.]]></description>
			<content:encoded><![CDATA[<p>Maybe I can help you: I read your post and I get really interested to decode the firmware: looking at the data seems obvious that it&#8217;s neither (block) encrypted neither compressed since there are large blocks with constant data; I lose my mind for a day and looking at github I found a repository where a guy smarter than me sorted this out: roughly speaking the firmware is xored 0x200 bytes at times with a key of four bytes (the bytes that repeat along the block probably).</p>
<p>The repository is here <a href="https://github.com/trolldbois/theta/blob/master/ThetaS-firmware-opening.ipynb" rel="nofollow ugc">https://github.com/trolldbois/theta/blob/master/ThetaS-firmware-opening.ipynb</a>.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: cdn0.mpetroff.net
Minified using Disk

Served from: mpetroff.net @ 2026-03-30 09:31:13 by W3 Total Cache
-->