Install All Optional Packages From Binary

Updating RetroPie

The conventional way to update RetroPie and install new features is through the setup script.

The setup script can be accessed from the
RetroPie menu
in EmulationStation.

Information technology can also exist accessed from the concluding with
sudo ~/RetroPie-Setup/retropie_setup.sh.

NOTE: any updates require the RetroPie system to be
online, otherwise downloading and installing the files required in the process volition non piece of work.

Before making whatever major updates it is important to make backups just in case (encounter backup options beneath).

Update All Installed Packages

• Basic Install:
  This is intended as a commencement install and is not required if using a pre-built image. eg When installing RetroPie on acme of an existing Os.
• Update:
  This volition update the RetroPie-Setup script and all installed packages.
• Manage Packages:
  This will allow yous to install and update individual emulators, ports, controller drivers (like the ps3 or xboxdrv) other optional packages.
• Configuration / Tools:
  Configuration and tools including BlueTooth and WiFi setup, splashscreens and theme. You tin besides access any packages that have additional configuration here.
• Update RetroPie-Setup Script:
  Updates the RetroPie-Setup script to the latest version.
• Uninstall RetroPie:
  Uninstalls RetroPie from the system.
• Reboot:
  Reboots your arrangement.

Manage Packages

• Core:
  These are essential packages needed for RetroPie to run. Do non remove them.
• Main:
  These are the main emulators that come up installed with the RetroPie SD image.
• Optional:
  These are optional packages that are working but aren’t included with the RetroPie SD image.
• Drivers:
  Here you install gamepad drivers like the PS3 or Xboxdrv.
• Experimental:
  These packages have not been fully tested and may have bugs.

Manage Core Packages

Each department of the manage packages portion of the setup script have the choice to install/update all packages and remove all installed packages. Yous can as well update/install and remove packages individually.

The core components needed for RetroPie to function are:

• RetroArch:
  Frontend for the Libretro api, necessary for most emulators to run.
• EmulationStation:
  Frontend for sorting and launching all of your games.
• RetroPie Menu:
  Menu in EmulationStation for simpler configuration of your system.
• Runcommand:
  The Runcommand launch menu that assists launching your games with proper configurations, meet the related documentation page HERE.

Updating/Installing private packages

You can update/install and remove packages individually.

When selecting a parcel there is also a help guide with extra information specific to that packet:

Bundle Help

The Package Help for each emulator should show you: – The proper noun of the packet – ROM extensions – ROM binder – BIOS filename and folder if applicative

Binary vs Source updates

Binary

Updating from binary gets the pre-compiled version of the bundle(s). Information technology is fast, and will typically be a known-good version. Binaries are typically updated every RetroPie release. It is the suggested method unless you have a specific reason for needing the latest haemorrhage-edge version.
Note:
Binary versions are not bachelor for all platforms/packages.

Source

Updating from source downloads the latest source lawmaking, and builds the binary straight on your arrangement. This takes much longer – hours, even days, depending on the organisation and package(south). It is suggested just if y’all require a specific fix that is not available every bit a binary.

Latest SD prototype

If you are worried about conflicts during an update y’all can e’er just showtime with the latest fresh sd paradigm which can be downloaded
here
and just copy all your files back over onto that instead of updating from an older image.

Making a Fill-in

Backup Option one

You tin can create an sd prototype of your current sd card with win32diskimager (if y’all’re on windows)

• Plug your sd card into your laptop (you will need a sd bill of fare reader for this)
• Open win32diskimager as an administrator (yous tin can correct click on it to run as an administrator)

• make sure you have the correct drive alphabetic character for your SD menu!
• ascertain the file path that you lot want to save your .img fill-in equally

• Click
  read
  to create your backup. (subsequently you’ve backed this epitome up if you spiral something up later on and want to commencement from this image y’all can just click write and it volition write this sd image back to your sd card.)
• notation if you have a 64GB sd card it will create a 64GB backup file fifty-fifty if y’all don’t have it completely filled upwardly. If you lot don’t want a file that large meet the side by side option.

Note: images created this fashion tin only be written to a microSD card of the Verbal same size or bigger. As an case you may not exist able to write an paradigm of a 64GB microSD onto another 64GB menu. That’south because actual existent usable space may vary past manufacturer and in some cases even with the same manufacturer. To avoid this issue you tin can use option 3.

Backup Choice 2

if you lot don’t want to create a sd paradigm you tin just back up your bios, roms, and configuration files from the samba shares

Backup Pick iii (transferring to some other SD)

Y’all tin can use
Rpi-clone, a vanquish script that runs directly on your Raspberry Pi. Requires a USB microSD card reader. Detailed instructions here.

Backup Choice 4 (OS X)

Open a last window and type
diskutil list. A listing of all hard disks and partitions shows up. Find a partition with the name
boot
– it should say (internal,physical) beside the /dev/disk#. Example:

                
                user@host$ diskutil list   /dev/disk0 (internal, physical):   #:                       Blazon NAME                    SIZE       IDENTIFIER   0:      GUID_partition_scheme                        *500.3 GB   disk0   1:                        EFI EFI                     209.7 MB   disk0s1   2:          Apple_CoreStorage Mac Hard disk                  499.4 GB   disk0s2   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3   /dev/disk1 (internal, virtual):   #:                       Type Proper noun                    SIZE       IDENTIFIER   0:                  Apple_HFS Mac HD                 +499.0 GB   disk1                                     Logical Volume on disk0s2                                     3BAC0F9E-19F8-4AAB-8752-6514B573B497                                     Unencrypted   /dev/disk2 (internal, physical):   #:                       Blazon NAME                    SIZE       IDENTIFIER   0:     FDisk_partition_scheme                        *fifteen.9 GB    disk2   1:             Windows_FAT_16 boot                    59.eight MB    disk2s1   ii:                      Linux                         xv.9 GB    disk2s2   user@host$
                
              

In this case /dev/disk2 partition 1 is named
boot. That disk# is the retropie sd bill of fare – in the example information technology is /dev/disk2. Confirm that the size (on the right) matches the size of your SD card.
Type
cd ~ ; sudo dd if=/dev/disk2 of=backup.img bs=1m
to write a disk paradigm to your home directory. Note that you lot need to use the entire disk (/dev/disk2) and not just a partition (/dev/disk2s0).