≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
todo [2025/04/26 20:56] – [General improvements] hiccuptodo [2026/04/30 22:19] (current) – [Unsorted] hiccup
Line 19: Line 19:
   * 3DS: Document GodMode9's "last byte in .txt file" feature for 4GB ROMs: https://github.com/d0k3/GodMode9/issues/780   * 3DS: Document GodMode9's "last byte in .txt file" feature for 4GB ROMs: https://github.com/d0k3/GodMode9/issues/780
   * GB/C: this can be used to detect (to some degree) which bootrom your GB/C has https://github.com/nitro2k01/whichboot.gb   * GB/C: this can be used to detect (to some degree) which bootrom your GB/C has https://github.com/nitro2k01/whichboot.gb
-  * [[template:carts_important_notes]]:+  * [[template:dumping_important_notes]]:
     * Add something to about importance of [[submission:general|Gathering and Submitting Dump Info]]     * Add something to about importance of [[submission:general|Gathering and Submitting Dump Info]]
     * Add something here about checking ROMs using emulators/flashcarts and ROM checking tools (like ctrtool signature check for 3DS carts),      * Add something here about checking ROMs using emulators/flashcarts and ROM checking tools (like ctrtool signature check for 3DS carts), 
Line 25: Line 25:
 359c8a37110aa60f87354e603c801982a036d9d39a2869df3b794e9418acb8d4  GM9_ntrboot_CTRDEV.firm 359c8a37110aa60f87354e603c801982a036d9d39a2869df3b794e9418acb8d4  GM9_ntrboot_CTRDEV.firm
 039b84f95dafaf4b103b51a27e6f46b6d1cda8b299e4b72ef53b56d5c725f73b  GM9_ntrboot_TWL.firm 039b84f95dafaf4b103b51a27e6f46b6d1cda8b299e4b72ef53b56d5c725f73b  GM9_ntrboot_TWL.firm
 +  * Vita: look into https://github.com/Prominos/NoGrw0Write and https://github.com/oestriot/GcToolKit 
 +  * Re. GBA dumping: "if you have dirty contacts you end up with address lines not working (mirrored data), or the data lines having a bit stuck high/low [not a single bit flip]". may apply to ROM dumping in general too. 
 +  * 3DS: add something about this tool https://github.com/skawo/GodMode9-with-Cartridge-Fixer
 ===== Add new systems =====  ===== Add new systems ===== 
  
Line 32: Line 34:
   * Atari Lynx - [[https://bennvenn.myshopify.com/products/joeylynx-cart-flasher|Joeylynx]] or [[ https://atarigamer.com/pages/lynx-cart-programmer-pi-hat|lynx pi hat]]   * Atari Lynx - [[https://bennvenn.myshopify.com/products/joeylynx-cart-flasher|Joeylynx]] or [[ https://atarigamer.com/pages/lynx-cart-programmer-pi-hat|lynx pi hat]]
   * Atari Jaguar carts - either desolder ROMs and use ROM programmer, or use a BJL-modded jaguar and the bjl_dump homebrew   * Atari Jaguar carts - either desolder ROMs and use ROM programmer, or use a BJL-modded jaguar and the bjl_dump homebrew
-  * Create GBA e-Reader guide+  * GBA e-Reader - add scanning method with mGBA
   * Create guide for Bandai Wonderswan. OSCR adapter requires [[https://github.com/sanni/cartreader/discussions/545|harvesting cartridge slot]] from a real Wonderswan. There's also a [[https://ayasuke2.exblog.jp/24644202/|Tengu]] cart reader. A flash cart in the early 2000s named WonderMagic could also dump carts, but it's now extremely difficult to find. Carts are secured with two T6 Torx screws. Make sure to not include save data in dumps.   * Create guide for Bandai Wonderswan. OSCR adapter requires [[https://github.com/sanni/cartreader/discussions/545|harvesting cartridge slot]] from a real Wonderswan. There's also a [[https://ayasuke2.exblog.jp/24644202/|Tengu]] cart reader. A flash cart in the early 2000s named WonderMagic could also dump carts, but it's now extremely difficult to find. Carts are secured with two T6 Torx screws. Make sure to not include save data in dumps.
     * This [[https://blog.tauwasser.eu/wonderswan-cartridges/| blog post]] could be useful for decoding game IDs     * This [[https://blog.tauwasser.eu/wonderswan-cartridges/| blog post]] could be useful for decoding game IDs
Line 50: Line 52:
   * Famicom Disk System: [[https://github.com/ClusterM/fdskey|FDSKey]]   * Famicom Disk System: [[https://github.com/ClusterM/fdskey|FDSKey]]
   * GB: https://www.chrismcovell.com/TapeDumpGB.html   * GB: https://www.chrismcovell.com/TapeDumpGB.html
 +  * GB: Dumper for analogue pocket http://mrom.lemouel.io/ 
 +  * GBA: https://github.com/tzlion/vfdump 
 +  * GBA e-Reader: idea - e-card dumper homebrew that is loaded via e-card or link cable - sending card data out via the audio jack (or link cable). 
 +  * GBA e-Reader: idea - add support to GBA cart dumpers to dump e-cards via e-reader cart
 ===== Method development ===== ===== Method development =====
   * General: more "TapeDump"-like homebrew for different systems could be useful. Especially if paired with cheap hardware to allow easy and safe cart swapping.   * General: more "TapeDump"-like homebrew for different systems could be useful. Especially if paired with cheap hardware to allow easy and safe cart swapping.
Line 61: Line 66:
   * Add explanations of why the different pieces of info are useful to record to [[submission:general-detailed|Gathering and Submitting Dump Info (Detailed)]].   * Add explanations of why the different pieces of info are useful to record to [[submission:general-detailed|Gathering and Submitting Dump Info (Detailed)]].
   * Hiccup's notes: https://hiccup.miraheze.org/wiki/Notes_to_assist_with_dumping_guides   * Hiccup's notes: https://hiccup.miraheze.org/wiki/Notes_to_assist_with_dumping_guides
-  * It may be a good idea to overdump (dump past the maximum known capacity) from some carts on some systems, to make sure all the ROM is dumped (even if the capacity is written on the ROM chip), and then analyse the overdump to find the actual size. Maybe this is something that could be done by the dumping hardware itself - maybe make suggestion on OSCR github discussions.+  * It may be a good idea to overdump (dump past the maximum known capacity) from some carts on some systems, to make sure all the ROM is dumped (even if the capacity is written on the ROM chip), and then analyse the overdump to find the actual size - maybe using a script. Maybe this is something that could be done by the dumping hardware itself - maybe make suggestion on OSCR github discussions. Would need to decide how much to dump though.
   * Hardware: integrate Lesserkuma's {{ ::cart_reader_dumping_compatibility_chart.xlsx |}}   * Hardware: integrate Lesserkuma's {{ ::cart_reader_dumping_compatibility_chart.xlsx |}}
   * Some carts may have DLC in the save data. Add a note to the dumping guide pages about this.   * Some carts may have DLC in the save data. Add a note to the dumping guide pages about this.
   * Rewritable Hard Disks and Flash Media: add instructions on how to censor personal information without altering the surrounding data structure (e.g. FF/00-out file contents without modifying the filesystem metadata or shifting data)   * Rewritable Hard Disks and Flash Media: add instructions on how to censor personal information without altering the surrounding data structure (e.g. FF/00-out file contents without modifying the filesystem metadata or shifting data)
   * Full PCB documentation/disassembly guide?   * Full PCB documentation/disassembly guide?