Full added MangaON

dsidev/release/dev-nands.html

@@ -106,6 +106,12 @@ preview: /photos/classroom_open.jpg
         </p>
         <hr>
         <h2 id="mangaon">MangaON development DSi (v1.0J_dev)</h2>
+
+        <div class="info" style="margin-top:1vw;margin-left:auto;margin-right:auto;width:60%;color:black">
+        <h4>Update: <a href="/dsidev/release/dev-nands_update.html">This build has been recovered!</a></h4>
+        We originally thought this build was cut off, but we were not aware of fragmentation in NAND. Thanks to <b>MrPinball64</b> we now have a re-assembled and fully working copy.
+        </div><br>
+
         <p> This DSi was used for the development of <a href="https://web.archive.org/web/20090205212450/http://nintendo.joystiq.com/2008/12/22/japan-now-to-have-two-wiiware-manga-services/" target="_blank">MangaON</a>, Sunsoft's unreleased service for WiiWare and DSiWare that would have distributed comics and manga. Articles from that time mention Dragon Ball and One Piece manga being offered, as well as others from Shonen Jump later on. The DSi we found would have been on display at <a href="https://www.inside-games.jp/article/img/2008/12/20/32805/62896.html" target="_blank">Jump Festa 2009</a> for people to try and learn about MangaOn. <br>While somewhat hard to see, photos of the event show the DSis in action. In fact, there's a chance this exact unit (or the very edge of it at least) is shown here: <br>
           <div class="screenshot">
           <img src="{{ site.releasedir }}{{ page.releaseslug }}/photos/mangaon_in_real_life.jpg" alt="Jump Festa MangaON stand">

dsidev/release/dev-nands_update.html

@@ -10,6 +10,22 @@ preview: /preview.png
 <a href="{{ site.releasedir }}{{ page.releaseslug }}/files/MangaOn.srl">MangaON SRL</a><br>
 <a href="{{ site.releasedir }}{{ page.releaseslug }}/files/MangaOn.tad">MangaON TAD</a>
 </p>
+<h2>Recovery explaination from MrPinball64</h2>
+<p>
+Nintendo DSi NANDs are just a FAT12 filesystem, and for the most part are very similar to any other type of data storage - the difference seems to be that files and fragments are stored at <code>0x200</code> instead of <code>0x1000</code>. This is not in multiples, so you won't see it as <code>0x400</code>, <code>0x600</code>, and so on.
+<br><br>
+MangaOn's file begins at <code>0x699200</code> in the image, and the filesize is stored at <code>0x210</code> in the header in little endian format - so <code>F8C000</code> in this case. From where comic.bin starts (notated with a <code>BVSC</code> header), there are headers for sections of the <code>.bin</code> (<code>11 00 08 00</code>), always occurring exactly on a multiple of <code>0x10</code>, and always preceded by at least 4 <code>FF FF FF FF</code> bytes. Using this, I was able to find where they stopped occuring, and work my way down the image to find where they resumed again. By knowing that fragments can only occur on <code>0x200</code>, I was able to find exactly where it stopped and started again. This occured one more time, and from there, it was a straight shot to the end of the file, which I found by using the length of the file I was missing, and luckily the rest of the build was stored in one clear shot from that point. 
+<br><br>
+The locations from where the build was pieced back together are as follows:
+<div class="code-div"><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0><TR><TD><PRE>
+Build start: 0x699200
+Stop: 0x7211FF
+Resume: 0x91D200
+Stop: 0x9291FF
+Resume: 0x1B5D200
+End of build: 0x2A551FF 
+</TD></TR></TABLE></div>
+</p>
 
 <div class="screenshot">
   <img src="{{ site.releasedir }}{{ page.releaseslug }}/photos/mangaon_in_real_life.jpg" alt="Jump Festa MangaON stand">

dsidev/releases.html

@@ -7,6 +7,21 @@ redirect_from: /dsidev/index.html
 
 <!-- Have you thought about autogenerating based on tags and including previews in the boxes? -->
 
+<div style="margin:1%;">
+   <div class="devinfo-container-main releasepage colorbox">
+      <img src="{{ site.imgui }}menu/green/dsi_widebarnoprompt_u.png" style="width: 100%;position: static;display: block;" class="pixelate">
+      <div style="background-image: url('{{ site.imgui }}menu/dsi_widepromptnobar.png');background-size:100% 100%;position: static;display: inline-block;width:100%;">
+      <div class="devinfo-main" style="position:relative;"><br>
+      <h3 style="padding-top:0;"><a href="/dsidev/release/dev-nands_update.html">MangaON DSi Update: Build recovered</a> (2025/01/04)</h3>
+      <p style="width:100%;">
+      A build of the cancelled digital manga service called MangaON has been recovered by <b>MrPinball64</b>! This was assumed to be overwritten in our old release, but it was just fragmented!
+      </p>
+      </div>
+      </div>
+      <img src="{{ site.imgui }}menu/green/dsi_widebarnoprompt_d.png" style="width: 100%;display: block;" class="pixelate">
+   </div>
+</div>
+
 <div style="margin:1%;">
    <div class="devinfo-container-main releasepage colorbox">
       <img src="{{ site.imgui }}menu/green/dsi_widebarnoprompt_u.png" style="width: 100%;position: static;display: block;" class="pixelate">

index.html

@@ -8,8 +8,8 @@ redirect_from: /dsidev/index.html
 <!-- ^ Real sigmas up here. -->
 <div style="margin:1%;">
 <div class="info" style="margin-top:1vw;margin-left:auto;margin-right:auto;width:60%;color:black">
-<h4>News: <a href="/dsidev/release/voodooween-dsi.html">X4, X5, and X6 DSis released!</a></h4>
+<h4>News: <a href="/dsidev/release/dev-nands_update.html">MangaON DSi Update: Build recovered</a></h4>
-Photos and NAND dumps of 3 retail prototypes just got released, along with a brand new prototype firmware! Thanks <b>Voodooween!</b>
+A build of the cancelled digital manga service called MangaON has been recovered by <b>MrPinball64</b>! This was assumed to be overwritten in our old release, but it was just fragmented!
 </div><br>
 
    <div class="devinfo-container-main releasepage colorbox">