There are a few recovery tools to use on your Android device that can help restore pictures. Few come any easier than the Dumpster application that is available for people who has access to that root file system. With Dumpster, there is almost nothing you cannot restore, from pictures, video files, music files and other data.

Another application idea to check out after you finish the guide is the Flashify application. The Flashify app can queue up to 10 files to flash for you one after the other so you don’t have to be there. Flashify can flash zip files, boot images, recovery images, custom kernels, new mods and more. Where Flashify really excels is when people don’t like to use ADB and fastboot to use commands from a command line.

Samsung Galaxy A3

Files You Need

  1. The CF-Auto-Root method in this guide is based on LRX22G.A300GXXU1BOG1 which is part of a wider release of Android 5.0.2 Lollipop firmware. It doesn’t really matter what regions that build ID rolled out to because Chainfire tells us that it’s not a requirement to be running that same firmware on your device. As long as you are running on the Android 5.0.2 Lollipop update, the firmware build number or ID should not matter.
  2. Download the CF-Auto-Root for the SM-300G running on Android 5.0.2 (Lollipop) from here.

Rooting the Samsung Galaxy A3 SM-A300G running Android 5.0.2

  1. Enable the USB Debugging Mode on the Galaxy S3 smartphone before you get started with the guide.
  2. Extract the rooting exploit to the desktop of the computer and you will see the Odin executable and the rooting files.
  3. Right-click on the Odin executable file and choose to run it as an administrator.
  4. Leave all the default options from the Odin flashing tool’s user-interface the same when it opens on your desktop.
  5. Turn off the Samsung Galaxy A3 smartphone by long-pressing the Power button or by visiting the Device Options menu by pressing the Power button just once.
  6. Boot the S3 smartphone back up again by holding the hardware button combination for download mode and then connect the A3 device to the computer with the USB cable.
  7. Wait for around 10 seconds and the ID: COM port from the Odin application on the computer should light up with a yellow or blue color. No color coming from your ID: COM port means that your A3 device is not connected because the drivers are not up to date. You can solve that problem by installing Koushik Dutta’s universal Windows ADB driver — and yes, that is the same guy who founded ClockworkMod Recovery.
  8. Click the AP button from the Odin application on the computer and browse the desktop location for the rooting file that popped out onto the desktop after you extracted the file in step two.
  9. Once you can see the file extension is loaded from the AP button, click the Start button and Odin will now flash that file on your A3 device.
  10. Look over at the display of your Samsung Galaxy A3 smartphone and it should say that it is installing the SuperSU cleaning up the cache partition and re-flashing the stock recovery.
  11. Give it a few minutes and then look for a green box with a pass message inside.

In conclusion, that’s all you need to Samsung Galaxy A3 SM-A300G smartphone running the Android 5.0.2 Lollipop software update. Any device that did not get into recovery mode after re-flashing the stock recovery at the end of the guide will not be rooted. You can install the root checker application from the Google Play Store and check if your Galaxy A3 handset is rooted or not. Those who did not get rooted might need to reboot to recovery mode manually at the end instead. Chainfire, the developer of the rooting method, makes it clear that all devices must get into recovery mode for the rooting to have worked.

Anyone who has gotten the rivers working and the Galaxy A3 connected to the Odin application on the computer, but still cannot seem to get the guide working will need to try installing a different version of the Odin flashing application and try again. Sometimes it can take multiple versions on your computer before your device takes a liking to one of them.