diff --git a/dsidev/release/dev-nands.html b/dsidev/release/dev-nands.html index 971f6ab..f377e76 100755 --- a/dsidev/release/dev-nands.html +++ b/dsidev/release/dev-nands.html @@ -106,6 +106,12 @@ preview: /photos/classroom_open.jpg

MangaON development DSi (v1.0J_dev)

+ +
+

Update: This build has been recovered!

+ We originally thought this build was cut off, but we were not aware of fragmentation in NAND. Thanks to MrPinball64 we now have a re-assembled and fully working copy. +

+

This DSi was used for the development of MangaON, 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 Jump Festa 2009 for people to try and learn about MangaOn.
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:

Jump Festa MangaON stand diff --git a/dsidev/release/dev-nands_update.html b/dsidev/release/dev-nands_update.html index 881ce48..e043b57 100644 --- a/dsidev/release/dev-nands_update.html +++ b/dsidev/release/dev-nands_update.html @@ -10,6 +10,22 @@ preview: /preview.png MangaON SRL
MangaON TAD

+

Recovery explaination from MrPinball64

+

+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 0x200 instead of 0x1000. This is not in multiples, so you won't see it as 0x400, 0x600, and so on. +

+MangaOn's file begins at 0x699200 in the image, and the filesize is stored at 0x210 in the header in little endian format - so F8C000 in this case. From where comic.bin starts (notated with a BVSC header), there are headers for sections of the .bin (11 00 08 00), always occurring exactly on a multiple of 0x10, and always preceded by at least 4 FF FF FF FF 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 0x200, 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. +

+The locations from where the build was pieced back together are as follows: +

+Build start: 0x699200
+Stop: 0x7211FF
+Resume: 0x91D200
+Stop: 0x9291FF
+Resume: 0x1B5D200
+End of build: 0x2A551FF 
+
+

Jump Festa MangaON stand diff --git a/dsidev/releases.html b/dsidev/releases.html index f1f3424..c0923af 100755 --- a/dsidev/releases.html +++ b/dsidev/releases.html @@ -7,6 +7,21 @@ redirect_from: /dsidev/index.html +
+
+ +
+

+

MangaON DSi Update: Build recovered (2025/01/04)

+

+ A build of the cancelled digital manga service called MangaON has been recovered by MrPinball64! This was assumed to be overwritten in our old release, but it was just fragmented! +

+
+
+ +
+
+
diff --git a/index.html b/index.html index ba491fe..6eff9c7 100755 --- a/index.html +++ b/index.html @@ -8,8 +8,8 @@ redirect_from: /dsidev/index.html
-

News: X4, X5, and X6 DSis released!

-Photos and NAND dumps of 3 retail prototypes just got released, along with a brand new prototype firmware! Thanks Voodooween! +

News: MangaON DSi Update: Build recovered

+A build of the cancelled digital manga service called MangaON has been recovered by MrPinball64! This was assumed to be overwritten in our old release, but it was just fragmented!