@tmntturtlguy Yes, I'm sure.

Cool solution ;)

I posted annother small script for such purposes here
This creates a zip file for each rom and takes as backup the same folder as the rom located.

It took annother branch instead of searching all files that "could" be a savestate I said, every file with same name except the ROM-name is a savefile.

Thanks for this small script. I appreciate it :)

@chipsnblip Thank you, that is exactly what I'm looking for.

Just thought I'd throw this out there and mark this as resolved. For anyone looking to do what I did which is fully configure your RetroPie, then remove your controller configuration for a clean backup solution (Where you can then restore and configure whatever controller you want as it came Out of the Box) all you have to do is this.

Configure your Raspberry Pi fully (with RetroPie) Make sure all settings are exactly as you'd like with splash screen, themes, core configs, scrapes, roms Delete any save files for the cleanest backups Go to RetroPie > RetroPie Setup > Manage Configurations > EmulationStation > Clear input Configuration Exit to ES, press start on controller and Shutdown System Remove MicroSD card, and insert in computer Create your backup with your favorite backup software, then "Pi shrink" it

All, finally home from my work trip and I updated the rpi-clone tool and it worked perfectly. Thanks for the tip on the new update.

@RedBatman not much you can do unless you shrink the free space down on your installation. I'm sure there's a Linux command you can run to do that. But then each time you move the image back to your sd card you will have to rememeber to expand the file system again.

Disk drill can help to restore deletes images. For instance, with it help I recover deleted photos on my mac. With step-by-step instruction it's easy to do even for me :)

@DarkWolf I use a bash GUI. It has options for Kodi, RetroPie, PIXEL desktop, MC File Manager, RP SetUp Script, System info, reboot & shutdown. Just pick the option and it launches. Any script could be launched from it, including the type proposed by the OP.

Another, option is for him to create the script and just set up a bash alias. So a special codeword or password could just be entered in the shell and the script would run.

So handy for people not familiar with the system. The Pi is basically the living room home entertainment system. In a computer not much bigger than a credit card. What a time to be alive!

@Freakadude said in Strange cloned RetroPie Image issue!:

This is a self backup and restore issue/question.

Sorry for assuming you were using a 3rd party image. I hope our fellows posts above helped you.

Cheers!

@THRobinson You can play with buttons by shorting pins if you have to.

try recuva

@jesterking said in Backup my retropie error?:

That being said, the best... method of backing up the entire SD card that I could find is in this link

At the end of the day, making an sd backup externally really is the best, most all-encompassing method. The same advice is given in the official RetoPie documentation as well.

https://github.com/retropie/retropie-setup/wiki/updating-retropie#making-a-backup-option-1

Thanks very much - doing a full backup isn't a problem, its just nice to know the options! Will continue to do it this way.

@edmaul69 what's deleted?

@Capt_MorganCreek Ok, I'll give that a try. Thanks.

@msilveira85 your welcome, we are all here to help each other and make this project even better than it all ready is

To create backups for my PI I use Win32 disk imager as I already had it installed from when setting up Retropie on to my SD card.

There are some useful YouTube videos on to how to use the tool but effectively it's just the reverse process of how you got the image of retropie on the SD card but now you are copying an image off and storing it on a PC.

@Dominus said in Backup from Pi3 to Pi2?:

Nope did it myself. Bought a Pi3 for a present, fixed it all up, and I just want to be able to copy that image to my old Pi2. Thanks for the info, I will try updating after I've written the image.

One more thing, if you sent up a Manual overclock on the Pi3, you'll want to probably edit the bood config.txt or it might cause issues on the Pi2 as it can't run at those speeds.

Again, I haven't do it that way, but I dod go from a Pi2 to a Pi3 and it kept my "screaming" 1000 Mhz overclock on the Pi3 until I manually edited the boot config.