New Clean DS and DSi BIOS
Recently, was added new DS and DSi BIOS to the no-intro database, dumps which were made with proper tools plus the console-unique information deleted (trusted modification). Probably wise to replace the current bios hashes with the proper ones from the BizHawk firmware section.
Dumping the DSi boot ROMs presentation by PoroCYon: https://www.youtube.com/watch?v=l0eCcwRNS1s
DS:
DS ARM7: https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB01 DS ARM7 (GBA Mode): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB03 DS ARM9: https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB02 Nintendo DS Firmware (World) (En,Ja,Fr,De,Es,It) (2004-10-05 11-07): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB11 Nintendo DS Firmware (World) (En,Ja,Fr,De,Es,It) (2004-11-26 09-51): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB12 Nintendo DS Firmware (World) (En,Ja,Fr,De,Es,It) (2005-02-28 08-51): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB13 Nintendo DS Firmware (World) (En,Ja,Fr,De,Es,It) (2005-06-06 14-48): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB14 Nintendo DS Firmware (World) (En,Ja,Fr,De,Es,It) (2005-12-07 14-45): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB09 Nintendo DS Lite Firmware (Korea) (En,Ja,Fr,De,Es,Ko) (2006-11-09 21-30): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB10 Nintendo DS Lite Firmware (World) (En,Ja,Fr,De,Es,It) (2006-02-05 21-33): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB07 Nintendo DS Lite Firmware (World) (En,Ja,Fr,De,Es,It) (2006-03-08 11-19): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB15
iQue DS:
iQue DS ARM7 (GBA Mode): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB05 iQue DS ARM9: https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB06 iQue DS Firmware (China) (En,Fr,De,Es,It,Zh) (2005-06-09 21-15): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB16 iQue DS Lite Firmware (China) (En,Fr,De,Es,It,Zh) (2006-04-26 15-35): https://datomatic.no-intro.org/index.php?page=show_record&s=28&n=xB08
DSi:
DSi ARM7: https://datomatic.no-intro.org/index.php?page=show_record&s=54&n=z005 DSi ARM9: https://datomatic.no-intro.org/index.php?page=show_record&s=54&n=z010
the console-unique information deleted (trusted modification).
I'm assuming this statement of console unique info deleted only applies to DS firmware files and not the DSi ones, considering the inconsistencies between the sources. Also I'm somewhat skeptical of these hashes considering the clear copy pasting of the console unique hash between two entries, along with the second entry only being a link to someone dumping the ARM9 bios and no report of the ARM7 bios (at least within that discord convo).
Also, melonDS currently doesn't support the "full" DSi BIOS files, we're waiting for melonDS updates for that. We shouldn't exactly be saying "this is the ideal hash" to a BIOS file the emulator will not work with.
Is this still relevant?
The full DSi BIOS hashes have been added, but I don't think the others have been added yet iirc
is there any way for NAND and firmware to be dumped (clean) for DSi?
The full DSi BIOS hashes have been added, but I don't think the others have been added yet iirc
is it possible for a clean NAND and firmware to be dumped?
NAND and firmware can be dumped from the DSi. They won't match any kind of DB hash, especially the NAND which is intrinsically unique to the console. BizHawk has internal handling to sanitize the firmware and NAND to avoid desyncs.
Is it possible to get hashes to match by hashing a sanitized version of the file? I haven't looked at how exactly this works for current melonDS implementation, but that's what I had done (or attempted to do) with my original version of melonDS, for the firmware file.
Probably not for the NAND, but I don't know much about that or if there's anything to verify there in term of it being a "good dump".
NAND and firmware can be dumped from the DSi. They won't match any kind of DB hash, especially the NAND which is intrinsically unique to the console. BizHawk has internal handling to sanitize the firmware and NAND to avoid desyncs.
Is it possible for the firmware to be dumped with a DB hash?
NAND and firmware can be dumped from the DSi. They won't match any kind of DB hash, especially the NAND which is intrinsically unique to the console. BizHawk has internal handling to sanitize the firmware and NAND to avoid desyncs.
Off topic but do you know where the WFC ID is in hex in firmware? im trying to remove/delete my WFC ID (not sure if you would know, just asking if you do)
Is it possible to get hashes to match by hashing a sanitized version of the file? I haven't looked at how exactly this works for current melonDS implementation, but that's what I had done (or attempted to do) with my original version of melonDS, for the firmware file.
Probably not for the NAND, but I don't know much about that or if there's anything to verify there in term of it being a "good dump".
yeaa would be cool to have a hash of it