How To Root Samsung Galaxy S II I9100

The Samsung Galaxy S II I9100 may be old enough to remember when Angry Birds was
cutting-edge gaming, but it’s still a beloved little workhorse. Rooting this device
is like giving it a second (or third) life: you can remove bloatware, install
lightweight custom ROMs, and squeeze out extra performance that Samsung never
intended to give you.

In this in-depth guide, we’ll walk through what rooting actually is, what you need
to prepare, two popular ways to root the Galaxy S II I9100, and what to do once the
magic “root” powers are unlocked. We’ll keep it practical, clear, and just cautious
enough that you don’t turn your vintage phone into a very expensive paperweight.

What Does “Rooting” Your Galaxy S II I9100 Mean?

Android is based on Linux, and “root” is Linux-speak for the superuser account that
can do anything on the system. When your Galaxy S II is unrooted, you’re basically
a guest on your own phone. You can install apps and change settings, but you can’t
touch the system files that control performance, themes, and deep-level behavior.

Rooting your Galaxy S II I9100 gives you superuser access. With the right tools,
you can:

• Remove preinstalled carrier and manufacturer apps (bloatware).
• Install custom ROMs for newer Android versions or lighter UIs.
• Use powerful backup tools that clone your entire system.
• Tweak CPU governors and kernels for better speed or battery life.

Of course, with great power comes great “you can break it if you’re careless.”
Rooting isn’t inherently dangerous, but typing random things into forums and
flashing the wrong files absolutely is.

Important Warnings Before You Root

Let’s get the scary-but-necessary part out of the way:

• You do this at your own risk. Rooting can potentially brick your
  phone if something goes wrong (power loss, wrong file, cable disconnect).
• Warranty. On a Galaxy S II, the official warranty is long gone,
  but rooting still alters the device in a way Samsung never supported.
• Data loss is possible. The methods below don’t usually wipe
  userdata, but any time you flash firmware or kernels, you could trigger
  a reset or bootloop that forces a factory wipe.
• Use files made for the GT-I9100 only. The Galaxy S II family has
  several variants (I9100G, I9100M, etc.). Flashing files for a different model can
  brick your phone.

If you’re still reading after that, congratulations: you probably have the right
level of caution.

Step 1: Prepare Your Galaxy S II I9100 for Rooting

1. Back Up Everything You Care About

Before playing surgeon with system software, back up your data. At minimum:

• Contacts synced to your Google account.
• Photos and videos copied to a PC or cloud storage.
• Important app data backed up with non-root tools (e.g., built-in backups).

Once rooted and running a custom recovery, you can make full “nandroid” backups,
but for now, treat your data like it’s standing near the edge of a cliff.

2. Check Your Exact Model and Firmware

On your Galaxy S II, go to Settings > About phone and note:

• Model number: must be GT-I9100.
• Android version / Build number: usually Gingerbread (2.3.x),
  Ice Cream Sandwich (4.0.x), or Jelly Bean (4.1.2) on this device.

Different rooted kernels and root packages are often built for specific firmware
builds. When you download a CF-Root, Siyah, or PhilZ kernel, make sure the name
matches your firmware base (for example, LPQ, XWLSN, etc. as seen in guides from
Android and Galaxy S II developer communities).

3. Enable USB Debugging

USB debugging lets your PC talk to the phone’s deeper Android tools:

• On Gingerbread: Settings > Applications > Development > USB
  debugging.
• On ICS/Jelly Bean: Settings > Developer options > USB
  debugging.

Check the box and confirm. You can turn this off again after you’re done.

4. Install Samsung USB Drivers and Odin on Your PC

Most classic Galaxy S II rooting methods use a Windows tool called
Odin to flash a rooted kernel or recovery through “Download Mode.”
To prepare:

• Install Samsung USB drivers or Samsung Kies on your PC so the phone is detected
  properly.
• Download a compatible Odin build (many guides use Odin 1.85 or 3.04 for the S2).
• Extract Odin to a convenient folder and run it as an administrator.

Once Odin can see your phone in Download Mode (we’ll get to that in a second),
you’re ready for the main act.

Step 2: Method 1 – Root Galaxy S II I9100 with Odin and a Rooted Kernel

This is one of the most common classic methods: you flash a rooted
kernel (such as CF-Root, Siyah, or PhilZ) through Odin. That kernel boots
Android with root enabled and often includes a custom recovery.

What You’ll Need

• A Windows PC with Odin installed and Samsung drivers working.
• The correct rooted kernel .tar or .tar.md5 file for
  your exact GT-I9100 firmware.
• The original or high-quality USB cable (you’d be surprised how many random
  cables cause problems).

Step-by-Step Odin Rooting Process

1. Extract the rooted kernel package.
   
   If the kernel comes in a .zip, unzip it until you get a
   .tar or .tar.md5 file. This is what Odin will flash in
   the PDA/AP slot.
2. Boot the phone into Download Mode.
   
   Power off the Galaxy S II completely. Then press and hold
   Volume Down + Home + Power together. When the warning screen
   appears, press Volume Up to continue to
   Download Mode.
3. Open Odin on your PC.
   
   Run Odin as administrator. Connect the phone via USB. In Odin, you should see
   one of the ID:COM boxes light up (yellow or blue) once the phone is recognized.
4. Configure Odin safely.
   
   Make sure only “Auto Reboot” and
   “F. Reset Time” are checked. Do NOT check
   “Re-Partition”. Leave PIT alone.
5. Add the rooted kernel file.
   
   Click the PDA or AP button in Odin and select
   the rooted kernel .tar(.md5) file you extracted.
6. Flash the kernel.
   
   Double-check everything, take a deep breath, and click
   Start. Don’t touch the cable, PC, or phone while Odin is
   working. When it’s done, Odin should show a green PASS message,
   and the phone will reboot automatically.
7. Check for root.
   
   After reboot, open your app drawer. You should see a root manager app such as
   SuperSU or Superuser. To be sure, install a
   “root checker” app from Google Play and verify that you have superuser access.

If Odin Gets Stuck or Fails

If Odin shows FAIL or gets stuck mid-flash, don’t panic. Common
fixes include:

• Disconnect the cable and close Odin.
• Force reboot the phone (pull the battery if necessary, then reinsert).
• Boot back into Download Mode and try again using a different USB port.
• Use the original USB cable and avoid USB hubs.

As long as you can still access Download Mode, there’s usually a way back by
reflashing either the rooted kernel or full stock firmware.

Step 3: Method 2 – Root via Stock Recovery and a SuperSU ZIP

Another common method for the Galaxy S II is to keep the stock kernel but flash a
SuperSU (or similar) ZIP through the built-in recovery or a
temporary custom recovery.

What You’ll Need

• A SuperSU (or Magisk-compatible) package designed for older devices, in ZIP form.
• An external microSD card (recommended for reliable access in recovery).

Step-by-Step Recovery Rooting Process

1. Copy the root ZIP to the SD card.
   
   Connect the phone to your PC in file transfer mode and copy the SuperSU ZIP to
   the microSD card. Safely eject the phone.
2. Boot into recovery mode.
   
   Power off the phone. Then press and hold Volume Up + Home + Power
   until the Samsung logo appears and recovery loads.
3. Install the ZIP.
   
   In stock recovery, use the volume keys to navigate to
   “apply update from external storage” or
   “install zip from sdcard” (phrasing can vary), and choose the
   root ZIP file you copied earlier.
4. Flash and reboot.
   
   Confirm the installation. Once it finishes, return to the main recovery menu and
   select “reboot system now”. After booting, look for the SuperSU
   app and verify root with a root checker tool.

This method is especially handy if you already have a custom recovery like
ClockworkMod or PhilZ installed, because they offer a friendlier interface and
better error messages.

After Rooting: What You Can (Safely) Do Next

1. Verify Root Access Properly

Install a reputable root checker from Google Play and run it. When it prompts for
superuser access, you should see a pop-up from SuperSU (or similar) asking whether
to grant permission. If you can grant access and the app confirms root, you’re
done with the hardest part.

2. Install a Custom Recovery and Make a Nandroid Backup

If your rooted kernel didn’t already include a custom recovery, consider flashing
one (such as ClockworkMod or TWRP built for the I9100) using Odin or an existing
recovery. A custom recovery lets you:

• Make full system backups (nandroids).
• Flash custom ROMs and mods.
• Clear caches and fix boot issues.

Your very first move after getting a stable rooted setup should be a full backup.
It’s your “save game” in case a future tweak goes sideways.

3. Gently Remove Bloatware

Root gives you the power to uninstall preloaded apps, but some system apps are
tied into core functionality. Instead of randomly deleting things with a root
file manager, use a known-safe app freezer or system app remover that can back up
each app before disabling it. Remove one or two apps at a time, then use the phone
for a while to be sure nothing broke.

4. Explore Custom ROMs (Carefully)

With root and a custom recovery in place, you can install custom ROMs based on
newer Android versions or lightweight builds optimized for the Galaxy S II. Many
users report big improvements in smoothness and battery life when switching from
old stock TouchWiz firmware to minimal ROMs. Always:

• Read the ROM thread fully before flashing.
• Ensure the ROM is specifically for the GT-I9100.
• Back up your existing setup first.

Remember: “Let’s see what happens” is not a flashing strategy.

Common Questions About Rooting the Galaxy S II I9100

Will Rooting Wipe My Data?

Rooting via a kernel or SuperSU ZIP usually leaves your apps and data intact. That
said, if something goes wrong and you need to factory reset or flash full firmware
to recover, you’ll lose everything not backed up. Treat rooting like surgery:
there’s always some risk.

Can I Unroot Later?

Yes. The cleanest way is to flash official stock firmware for the I9100 via Odin,
which replaces the rooted kernel and removes superuser binaries. Some root
management apps also offer a “full unroot” option that can revert many changes,
but if you’ve installed custom ROMs, you’ll need to go back to stock manually.

Is It Worth Rooting Such an Old Phone?

For a daily driver where security and reliability are critical, probably not. The
Galaxy S II doesn’t receive modern security patches, and many newer apps may not
support its older Android bases. But as a hobby device, backup phone, offline
media player, or tinkering platform, rooting can be huge fun and can make the
device feel surprisingly snappy again.

Real-World Rooting Experiences with the Galaxy S II I9100

Rooting the Galaxy S II I9100 has been almost a rite of passage in the Android
community. Many users started their modding journey on this exact phone, learning
what works, what definitely doesn’t, and how important backups really are.

A common story goes like this: someone gets tired of lag on an old carrier ROM,
follows an Odin-based guide, flashes a rooted kernel, and suddenly discovers that
their “old” phone no longer feels sluggish. Switching to a lightly tuned custom
ROM with a lean launcher often makes menus and home screens glide more smoothly.
Add a sensible CPU governor and you can get better battery life than you’d expect
from such an old battery, at least if it isn’t completely worn out.

Of course, it’s not all sunshine and overclocking. Many Galaxy S II owners have
also experienced the “I flashed something and now it’s stuck on the boot logo”
moment. That’s usually the result of either a mismatched kernel/ROM combination or
skipping a recommended wipe. The good news is that as long as Download Mode still
works, most of these situations can be fixed by reflashing a known-good kernel or
stock firmware and restoring a backup.

Another frequent experience revolves around experimenting with different kernels:
some prioritize battery life, others aim for performance, and a few try to balance
both. Users often report that a modest undervolt and a conservative CPU governor
can keep the phone cooler while still feeling responsive for everyday tasks like
messaging, music, and light browsing. Push too hard with overclocking, however,
and the S II can become unstable, reboot randomly, or heat up more than you’d
like. The lesson: small, incremental changes beat wild jumps.

Custom ROMs bring their own quirks. For example, early builds of newer Android
versions for the S II sometimes had issues with HD video recording, minor camera
bugs, or storage mounting oddities. Many long-time modders treat these as part of
the trade-off: you gain newer features, updated interfaces, and fresher security
patches for a while, but you may lose a bit of the polish of stock firmware.
Carefully reading user feedback on each ROM before flashing helps avoid the worst
surprises.

Perhaps the biggest “aha” moment that Galaxy S II rooters report is the power of
nandroid backups. Once you’ve made a full backup from custom recovery and then
successfully restored it after a bad flash, you truly understand why every guide
screams “backup first!” It turns rooting from a terrifying one-way leap into a
reversible experiment.

Overall, real-world experience with rooting the Galaxy S II I9100 can be summed up
like this: if you read carefully, match files to your exact model, and respect the
backup gods, the process is straightforward and surprisingly forgiving. Treat it
as a tinkering project, not a mission-critical upgrade, and you can squeeze a lot
of extra life and fun out of this classic Android legend.

Conclusion

Rooting the Samsung Galaxy S II I9100 is no longer about eking out survival from a
current flagship; it’s about breathing new life into a classic and learning how
Android really works under the hood. With the right preparation, a careful Odin
flash or recovery ZIP, and a healthy respect for backups, you can unlock root,
clean up the system, and experiment with custom ROMs and kernels without turning
your phone into a brick.

Take it slow, double-check every firmware and kernel name, and make that nandroid
backup as soon as you can. Do that, and your Galaxy S II can move from “old
drawer phone” to “fun weekend project” and maybe even “surprisingly capable spare
device” again.