How to Install Custom Recovery on Samsung Galaxy Grand Neo

This guide walks you through installing a custom recovery (like TWRP or ClockworkMod) on the Samsung Galaxy Grand Neo (GT-I9060). A custom recovery replaces the stock Android recovery mode, letting you flash custom ROMs, make full system backups (NANDroid), wipe data more thoroughly, and fix boot loops. You will need a Windows PC, a USB cable, and the correct firmware files. The process takes about 15 minutes and carries a small risk of voiding your warranty or, if done incorrectly, soft-bricking the phone.

What You’ll Need

A Samsung Galaxy Grand Neo (verify the model number in Settings > About Phone — it must be GT-I9060, GT-I9060I, or GT-I9060C; other variants use different files).
A Windows PC (the tools below are Windows-only).
A USB data cable (not a charge-only cable).
Odin3 — the flashing tool for Samsung devices. Download a recent version (e.g., 3.13.1) from a reputable source.
Samsung USB drivers installed on the PC (install from Samsung’s site or via the driver package included with Odin).
A custom recovery image file for the Grand Neo — usually named twrp_3.x.x.x_grandneo.tar or recovery.tar.md5. Get it from a trusted XDA-Developers thread for the Grand Neo.
Backup any important data — flashing recovery does not wipe data, but things can go wrong.
Charge the phone to at least 70%.

Step-by-Step

Enable USB debugging and OEM unlock (if available). On the phone, go to Settings > About Phone and tap “Build number” seven times to unlock Developer Options. Then go to Settings > Developer Options and enable “USB Debugging”. If you see “OEM Unlock”, enable it too — this allows the bootloader to accept a custom recovery.
Extract the recovery file. If the recovery you downloaded is a ZIP, extract it to a folder on your desktop. You should now have a file ending in .tar or .tar.md5. Do not extract the .tar itself — Odin needs it as a single archive.
Boot the phone into Download Mode. Power off the phone completely. Then press and hold Volume Down + Home + Power simultaneously for about 5 seconds. When the warning screen appears, press Volume Up to continue into Download Mode. You’ll see a green Android icon and “Downloading…” text.
Open Odin3 as Administrator. Right-click the Odin3.exe file and select “Run as administrator”. A window with several boxes (Odin, PDA, PHONE, CSC) will appear. The “Log” box at the bottom should show “Added!!” once the phone is detected.
Connect the phone to the PC. Plug the USB cable into the phone and the PC. Wait a few seconds. Odin’s ID:COM box (top left) should turn blue or yellow, and the log will say “Added!!”. If it doesn’t, reinstall the Samsung USB drivers and try a different USB port (preferably a rear port on a desktop).
Load the recovery into Odin. Click the AP button (or “PDA” in older Odin versions). Browse to the folder where you extracted the recovery and select the .tar or .tar.md5 file. It will appear in the AP box. Do not touch the PHONE or CSC boxes — leave them empty.
Verify Odin options. Make sure only “Auto Reboot” and “F. Reset Time” are checked. “Re-Partition” must be unchecked — checking it can wipe your partition layout and hard-brick the device.
Start the flash. Click the Start button. The log will scroll with progress. The phone will reboot automatically when done. You’ll see “PASS!” in a green box at the top-left of Odin. This takes about 30 seconds.
Boot into the custom recovery. As soon as the phone reboots, hold Volume Up + Home + Power for about 5 seconds (you may need to release and re-hold if it boots to the system). You should see the TWRP or CWM logo. If you miss it, just power off and try again.
Verify the recovery works. In TWRP, tap “Reboot” then “System” to reboot normally. The phone should boot as usual. Your stock recovery is now replaced.

Common Mistakes

Wrong model variant: Flashing a recovery built for the GT-I9060 onto a GT-I9060I can cause a brick. Double-check your exact model number in Settings > About Phone.
Re-Partition checked: This is the #1 cause of hard bricks. Always leave it unchecked.
Using a charge-only cable: Odin won’t detect the phone. Try a different cable that supports data transfer.
Not running Odin as administrator: On Windows, driver access can fail without admin rights. Always right-click and “Run as administrator”.
Interrupting the flash: Do not unplug the phone or close Odin during the flash. Wait for the “PASS!” message.
Extracting the .tar file: Odin needs the .tar archive, not the individual recovery.img inside it. If you extracted it, re-zip it as a .tar or download the correct file again.

Tips

Before flashing, write down your current baseband version (Settings > About Phone > Baseband). If you ever need to restore stock, you’ll need the matching stock ROM.
After installing TWRP, make a full NANDroid backup (Backup > select all partitions) and store it on an external SD card. This is your safety net for any future flashing.
Keep the same Odin version you used successfully. Different versions can behave differently.
If the phone boots into a boot loop after flashing, don’t panic — boot into recovery (Volume Up + Home + Power) and do a “Wipe cache” and “Wipe dalvik cache”.
Use a USB port directly on the motherboard (not a front-panel hub) for a stable connection.

Troubleshooting

Odin doesn’t detect the phone. Reinstall the Samsung USB drivers, try a different USB port, use a different cable, and ensure you’re in Download Mode (not just powered on). If the phone shows “Downloading…” but Odin still says “Added!!” only after reconnecting, try unplugging and plugging again.

Odin fails with “FAIL!” or “There is no PIT partition”. This usually means the recovery file is corrupt or for the wrong model. Re-download the recovery from a trusted source and verify the filename matches your exact model (GT-I9060 vs GT-I9060I). Do not attempt to fix this by checking Re-Partition.

Phone stuck on the Samsung logo after flashing. This is a soft brick, usually from a mismatched recovery. Boot into recovery (Volume Up + Home + Power) and perform a factory reset (wipe data/factory reset) and wipe cache. If it still won’t boot, flash the stock firmware via Odin (using the AP box with the stock firmware .tar.md5) to restore the phone to factory state, then try again with the correct recovery.

Phone won’t enter Download Mode. Ensure the phone is completely powered off (remove the battery for 10 seconds, then reinsert). Then press Volume Down + Home + Power together. If that fails, try Volume Down + Power only (without Home).

Custom recovery boots but touchscreen doesn’t work. Some early TWRP builds for the Grand Neo had this issue. Re-flash a newer TWRP version (3.2.x or later) using the same Odin steps.

After flashing, the phone boots to recovery every time. This can happen if the recovery image is for a different partition layout. Re-flash the stock recovery via Odin (download the stock recovery .tar.md5) to restore normal boot, then re-flash the custom recovery carefully.

Frequently Asked Questions

Will this void my warranty? Yes, flashing a custom recovery is a modification that typically voids the manufacturer warranty. You can restore the stock recovery and firmware later, but the flash counter (if present) may still show the modification.

Can I uninstall the custom recovery afterward? Yes. Download the stock recovery .tar.md5 for your exact model and flash it via Odin using the same steps (AP box, Re-Partition unchecked). This restores the original recovery.

Do I need root to install a custom recovery? No. Odin flashes the recovery directly to the recovery partition without needing root. However, some custom recoveries (like TWRP) can root the phone from within their menus.

Will this wipe my apps or data? No, flashing recovery alone does not wipe your data. Your apps, photos, and settings remain intact. However, if you use the recovery to wipe data (factory reset) later, that will erase everything.

Is it safe to install a custom recovery on Android 4.2 (Jelly Bean)? Yes, the Grand Neo ships with Android 4.2.2, and custom recoveries are built specifically for this device and firmware. Just ensure you download a recovery that states compatibility with Android 4.2.x.

What if I brick my phone? A soft brick (boot loop) can usually be fixed by flashing stock firmware via Odin. A hard brick (no response to power or Download Mode) requires a JTAG or a service center. Following the steps exactly and never checking Re-Partition greatly reduces this risk.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →