Last Updated on September 20, 2024 by Mathew Diekhake

Samsung Galaxy Grand DuosIf you’ve hunted around the Web and found the Android Open Source Project, then you’d likely be in the batch of people who think that Android is indeed based on open source software.

Technically Android is open source, but Google also blocks it off so the official updates you get cannot be further modified.

What can happen though is that developers get their hands on the open source code that is Android’s foundation and then have a play with it.

When the highest quality third-party developers out there do that they can come up with some outstanding custom software, that can be installed as custom ROMs.

Every device out there ships with the Android stock ROM, known as Google Android, and the stock ROM can always be swapped over for a custom ROM, based on the Android Open Source project, if the owner of the device should choose to do so.

The number of custom ROMs available to be flashed varies from device to device, so you’ll need to head to the XDA-Developers thread to check them out to see what’s available for yours. But as a general rule of thumb, if you’re interested in having a device that gets lots of custom ROMs developed for it, the better a device sells, the more likely it is to get plenty of ROMs to choose from.

Details of Note

  • The custom recovery images available in this guide are only to be installed on the Samsung Galaxy Grand Duos smartphone. Most devices have a custom recovery image developed specifically for it, and you shouldn’t install one that is intended for another device unless advised it is okay by a professional.
  • The codename for the Samsung Galaxy Grand Duos TWRP Recovery image is “i9082.” You will see that codename in the TWRP image file path and also from your About Device menu so you know you are flashing the right file on the right device.

Files Required

How to Install TWRP Recovery on Samsung Galaxy J1 Ace (SM-J110)

Note: The Odin flashing tool is really easy to use, but it only works on the Windows operating system. You won’t get the flashing tool to load on a Mac or Linux computer. It doesn’t really matter what version of the Windows operating system that you’re using as long as it is something above Windows XP.

1. Download and install the Samsung USB drivers on the computer if you don’t have them already.

2. Download the firmware (.tar) file from the links above directly to the computer. Extract the file by right-clicking on it and choosing the option to extract. When you do, you’ll see the tar.md5 file inside. That’s the file you’ll be using to do the flashing.

3. Download the Odin flashing tool. It doesn’t really matter what version, but the latest is the most up to date so grab that one. Extract the Odin file and then double-click on the Odin executable file (.exe) that is found from within the Odin folder after extraction. You should now have the Odin interface open on the computer and waiting for you to connect to it.

4. Boot the Samsung mobile device into the Download Mode by first powering it down and then rebooting by holding the Volume Down + Home + Power keys at the same time.

5. A yellow warning triangle will come up on the device’s display. At this time you need to press the Volume Up button. You’ll then see the device getting into the Download Mode. It’s then ready for the flashing.

6. When in Download Mode, connect the Samsung mobile device to the computer with the USB cable.

7. If you have installed the USB drivers correctly, the Odin flashing tool should detect your device. You can tell this by observing the ID: COM port lighting up with a color, usually yellow or blue.

It doesn’t matter what color, it’s the lighting up that counts.

8. After the device is picked up by Odin, click on the PDA or AP button, depending on what button your version of the Odin flashing tool has.

9. Navigate to the stock ROM folder and upload the tar.md5 file to this location in Odin.

10. Without changing any of the default settings, click on the Start button in Odin, and the flashing then begins.

11. Wait until Odin shows a Pass message before disconnecting your device.

You can now close the Odin flashing tool and continue using your computer if you like.

The custom recovery will now have replaced the stock recovery, and you are ready to boot your device into the recovery mode and start using it.

Most of the custom ROMs you’ll find available from the XDA-Developers web forum where each device has its own development section and custom software listed. If you weren’t swapping the recovery partition for ROMs, then you might be thinking about getting root access with SuperSU instead. You flash both ROMs and rooting files the same way, which is by tapping on the “Install” button from the main recovery screen.

Not a lot can go wrong with your time with the custom recovery, although one of the rare things that can happen just might: a message letting you know that “No OS is installed!.” If you see this message, it means that you’ve somehow managed to wipe the system partition, and that’s not ideal if you understand the way a custom recovery works. But it also shouldn’t be the end of the world just yet either, as there are ways you can solve this problem. The first thing you should do if you see it is restore the backup that you’ve taken from the custom recovery image. If you didn’t take any backups, try flashing a stock ROM instead. The sources for official firmware can vary online and not all manufacturers provide direct links. There’s nothing wrong with using a link coming from blogs, but just make sure you scan the files for viruses first.

The reason for a wipe of the system partition never being ideal is that if you do have to flash a stock ROM to get your operating system back, you could experience unexpected behavior on all software that you try running from here on out. When you install OTA updates, as in official software updates, you are installing what is most likely a differential update: one that doesn’t go through the system partition at all and often won’t even completely replace the files either, rather just patching over the top of the existing ones. It’s a good thing for those among you who love to save data, but not if you have installed a custom recovery. Getting root access, installing BusyBox, or removing the stock applications are a few examples of what people do from custom recovery images and that will make modifications to the system partition. Once changes have been made to the system partition, going back to official ROMs that don’t operate through it can be risky, and that’s when the unexpected behavior can happen.

The custom recovery developers suggest that if you want to update your version of Android, and you already have a custom recovery installed, then you should check out custom ROMs to update to instead of official updates. That way you know your device stays safe. The custom ROM updates can often come out for devices before the official versions do, and at worst, it’ll only be a few days later than an official update for the best-served devices.

But if you are hell-bent on settling for nothing less than the stock recovery image back on your device, there are a couple of ways you can go about doing it. And no, it doesn’t necessarily mean there will be anything wrong with your device after doing it; there is just a chance—no one knows really how much—of experiencing unexpected behavior with the software. To just change recoveries and nothing else, find the stock ROM zip file, unpack it and then flash the recovery image file found inside by using the flashing tool made for your manufacturer ((in this case Odin for Samsung devices). If you aren’t fussed, you can also just flash the complete firmware package, because when you do, the custom recovery is replaced by the stock recovery normally anyway.

That’s all.