Anonymous

Changes

From Rare Gaming Dump
5,047 bytes added ,  13:52, 8 August 2019
no edit summary
Line 27: Line 27:  
*The firmware for both the SuperCard and the XG/Neo get erased. This cannot be recovered.
 
*The firmware for both the SuperCard and the XG/Neo get erased. This cannot be recovered.
   −
Plus, a 2nd (and even more) obscure version was uploaded named "DS Owata", showing 5 different hentai images, and with some altered text, with the rom pretending to be Dragon Quest IX. After the erasing job is done, some text and hentai will be displayed on the screen:
+
Plus, a 2nd (and even more) obscure version was uploaded named "DS Owata" with some altered text, and the rom pretending to be Dragon Quest IX. After the erasing job is done, some text and hentai will be displayed on the screen:
    
{|style="margin: 0 auto;"
 
{|style="margin: 0 auto;"
Line 80: Line 80:  
== CrashMe (2011) ==
 
== CrashMe (2011) ==
 
Another trojan popped up around 2011, found by a GBAtemp user known as '''osm70''', and that he found it on a regular warez site, pretending to be Mario Party DS. The file size is 58,5MB.
 
Another trojan popped up around 2011, found by a GBAtemp user known as '''osm70''', and that he found it on a regular warez site, pretending to be Mario Party DS. The file size is 58,5MB.
 +
 +
== DarkFader's appology (2005) ==
 +
After everything went down, DarkFader has appologised for his actions and behaviour as he clears everything up, including some recovery tools for the bricked consoles and flashcarts.
 +
<nowiki>
 +
I want to say sorry to everyone out there. I should have realized the impact. Not just few DS'es that were hurt, but all the damn media and whatnot.
 +
I cannot really justify my actions. It was also very selfish to draw some attention, which I tend to do in odd ways.
 +
It caused some harm to some non-targetted and targetted people owning a DS with non-Nintendo-approved hardware.
 +
And that is a terrible thing to do. Even more so with the reputation I had in the DS homebrew scene that now completely abandoned me.
 +
I do not have clear reasons and I can't blaim the little headache I had at the time. I just had to realize the idea I had after seeing the PSP variant of a bricker.
 +
The files do not come with any form of name/signature of me, a thing I would do if it could be trusted.
 +
I won't release any more of this crap for DS and I don't think parts of this trojan or the idea itself will emerge in future homebrew releases.
 +
The point is probably clear. Do not run any form of untrusted code that just suddenly appears without any name.
 +
If you only use official Nintendo games, there is absolutely nothing to worry about.
 +
Untrusted code includes ROM loaders and that sort of stuff. It's probably not a very good reason since it has been proven before.
 +
I can tell that the negative feedback is far greater than the positive ones. I received one donation of $6.66 and I'm not proud of it.
 +
One news site completely ignores the r0mloader version and reasoning behind it. grrrrr.
 +
Another common mistake: A TROJAN IS NOT A VIRUS! That means that it does not propagate on its own. And thus non-intrusive.
 +
 +
The trojan was released in two forms:
 +
Trojan.DSBrick.A, 151361 bytes, md5sum a959cfa514f4c7162a81421ee99d3356, r0mloader.nds
 +
Version A was intended for the so called ROM-pirates. Hence the name of the filename and description. It was anonymously posted to just a few IRC channels and one forum. Elsewhere, it was known that is was a trojan.
 +
After doing its thing, it shows a picture of a brick wall. Apropriate to the situation.
 +
 +
Trojan.DSBrick.B, 548673 bytes, md5sum 8e7a3728759df265ca3a78553cf27bb8, taihen.nds
 +
Version B was not really released into public and should rarely be seen. It was only directly released in a closed IRC channel with prior notice of what it did and a comment that might have triggered some (less evil than me) persons to pass it along.
 +
After doing its thing, it cycles through five attractive drawings.
 +
 +
I cannot control the propagation of the files or the names it might be disguised as.
 +
 +
Ok, on to the more technical details:
 +
The trojan _tries_ (but not definately succeeds) to:
 +
* Erase DS firmware. Practically the first 64 KBytes are write-protected and thus is recoverable when the FlashMe firmware was installed.
 +
* Erase first few sectors of CompactFlash card inside GBA movieplayer. You can try to sort out your data sectors if you really want something back.
 +
* Erase GBA movieplayer firmware. Fairly easy to fix using flashmp utility.
 +
* Erase Supercard firmware. A fix is currently being worked on.
 +
* Erase/lock XG/Neo flash card. Seems it was forgotten to be mentioned in r0mloader.txt.
 +
If you have a legal use for these functions like testing recovery tools, you're welcome.
 +
 +
Here are some fixing utilities and links:
 +
ppflash.zip - Contains info, sourcecode and binary to flash the fail-safe loader also contained in FlashMe using a parallel port connection. Some soldering skills are required to perform this operation. Don't worry about voiding your warranty because you already have according to the DS manuals.
 +
FlashMe - The page to get FlashMe. You can't survive without it.
 +
flashmp.zip - Firmware flasher for GBA Movie Player. Supports writing to Supercard, but the included firmware IS NOT WORKING probably because of a bad firmware dump! If you have an original firmware version and Flash Advance Linker, let me know.
 +
Probably more to come.
 +
You can detect DSbrick by using DSbrick.signature and the utility grep:
 +
grep -F -U -f DSbrick.signature FileToBeTested.nds
 +
A good way to prevent malicious firmware access is to keep a record of known ARM7 binaries. This could be incorporated into ndstool.</nowiki>
 +
 +
== References ==
 +
*[https://www.youtube.com/watch?v=pNO_Vfl_aQk A video of Trojan.DSBrick.A]
 +
*[https://www.youtube.com/watch?v=7CWI5Rs5Qwk A video of Trojan.DSBrick.B '''(NSFW warning)''']
 +
*[https://www.youtube.com/watch?v=wSIIOAZ-0s0 CrashMe on Nintendo 3DS (Another unknown variant known as "Firmware Programmer")]
 +
*[https://web.archive.org/web/20100807234939/http://www.pocketheaven.com/ph/wiki/DS_Bricker Archived wiki article from PocketHeaven]
 +
*[https://www.gamespot.com/articles/ds-coder-apologizes-for-trojan/1100-6135944/ Gamespot covering DarkFader's appology]
 +
*[https://gbatemp.net/threads/new-crashme-ds-bricker-discovered.305443/ GBAtemp staff "Another World" covers the Mario Party DS bricker]