mirrors
/
game-and-watch-backup
mirror of https://github.com/ghidraninja/game-and-watch-backup.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Mirror of ghidraninja/game-and-watch-backup@github.com - Software to back-up the contents of the flash inside a Mario Game-and-Watch
11 Commits 1 Branch 0 Tags 4.8 MiB
Shell 69.8%
Assembly 23.5%
Python 6.7%
Go to file
Thomas Roth 67e8c9cf90 Add prebuilt 2020-11-29 19:30:27 +01:00
firmware Init 2020-11-29 11:58:55 +01:00
openocd Halt in flashdumper 2020-11-29 12:54:59 +01:00
payload Init 2020-11-29 11:58:55 +01:00
prebuilt Add prebuilt 2020-11-29 19:30:27 +01:00
python Init 2020-11-29 11:58:55 +01:00
scripts Add RDP1 script 2020-11-29 12:45:43 +01:00
shasums Init 2020-11-29 11:58:55 +01:00
.gitignore Init 2020-11-29 11:58:55 +01:00
1_sanity_check.sh Init 2020-11-29 11:58:55 +01:00
2_backup_flash.sh Add logs for commands 2020-11-29 12:31:12 +01:00
3_backup_internal_flash.sh Add prebuilt 2020-11-29 19:30:27 +01:00
4_unlock_device.sh Add prebuilt 2020-11-29 19:30:27 +01:00
5_restore.sh Add logs for commands 2020-11-29 12:31:12 +01:00
README.md Update README.md 2020-11-29 13:31:58 +01:00
install_pwnadventure.sh Add prebuilt 2020-11-29 19:30:27 +01:00

README.md

Game and Watch Backup and Restore tools

This repository contains pre-built tools for backing up & restoring the original Game and Watch firmware.

What you'll need:

  • A Game & Watch in original state
  • An ARM debug probe (Tested with J-Link and ST-Link compatible devices)
  • Connections to the debug port - testclips or soldered wires work well!
  • A computer with Ubuntu 20.04 or compatible.

Warnings & disclaimer

The tools in this repository will modify both the internal and the external flash of the Game and Watch. While we tested the scripts to our best ability, we can not guarantee that there won't be failures that will leave your Game & Watch damaged. Use these tools at your own risk. If you feel like you don't understand what you're doing it might be best to let someone with more experience help (and teach) you!

Connecting the debugger

When connecting the debugger ensrue that at least SWDIO, SWDCLK and GND are connected. Do not under any circumstances connect 3.3V to the VDD connection. If your debug probe (for example ST-Link clones) does not have a VTREF connector, just leave VDD unconnected. Connecting 3.3V to VDD will likely destroy your SPI flash.

Ubuntu setup

Install the required tools:

sudo apt-get install gcc-arm-none-eabi binutils-arm-none-eabi gdb-arm-none-eabi openocd python3

Usage

The scripts are split into 5 parts:

  • 1_sanity_check.sh - Performs sanity check and makes sure all required tools are available
  • 2_backup_flash.sh - Backs up the contents of the SPI flash. Does not modify device contents.
  • 3_backup_internal_flash.sh - Backs up the internal flash. To do this the contents of the SPI flash are modified. Your device will stop working until it's restored in step 5.
  • 4_unlock_device.sh - This will disable the active read protection. This will erase the internal flash of the STM32.
  • 5_restore.sh - This will restore the original firmware.

Just run these scripts from the checked out directory one after each other. All scripts are safe to be re-run in case of error.

Ensure that you keep your backup in a safe place so you can always recover. Don't ask us for flash dumps & co, we will not share them.

What if something goes wrong

As long as your electrical connections are right and you didn't short/overvolt anything, chances are high that it's rescuable:

If a script fails and the device does not work after power-cycling, repeat the script. If it fails again, try to hold the power button of the device while executing the script.

Sources for binaries

The binaries in firmware/ are based on: