How to Root and Install ClockworkMod Recovery on Samsung Galaxy Ace Plus S7500

If you have a Samsung Galaxy Ace Plus S7500 smartphone, then you should root it to enjoy a bunch of new apps that work only on rooted phones. Here’s a guide showing you how you can root your Galaxy Ace Plus S7500 smartphone.

I. Before You Begin:

1. Warranty of the phone will be voided once it is rooted. If you need, then you can get back the warranty by installing either stock firmware or unrooting your phone.

2. Make sure your phone has at least 60% of battery life left to last through the process.

II. Downloading Required Files:

1. Download the ClockworkMod Recovery Image from here.

2. Download the Rooting Package from here.

3. Download the Odin Tool from here.

III. Installing ClockworkMod Recovery on your Galaxy Ace Plus:

1. Extract files from the Odin Tool archive and place them on your Desktop.

2. Double-click on Odin3 v1.85.exe file to launch the Odin Tool.

3. Turn OFF your smartphone using the Power key.

4. Put your phone into the download mode. To do that, press and hold Volume DOWN+Home+Power buttons together.

5. Connect your phone to your PC using the USB cable.

6. From the Odin Tool, click on PDA tab and select the CWM Recovery Image file for flashing.

7. Hit the Start button to commence the process.

After the recovery is successfully installed on your phone, it will reboot. Now, move on to the following procedure to root your phone.

IV. Rooting Galaxy Ace Plus:

1. Turn OFF your Galaxy Ace Plus smartphone.

2. Press and hold Volume UP+Volume DOWN+Home+Power buttons together to boot your phone into the recovery mode.

3. Connect your phone to your PC using the USB cable.

4. Extract files from the Rooting Package and place them on your Desktop.

5. Double-click the runme.bat file to start rooting your phone.

6. When the rooting is done, reboot your phone by choosing reboot system now from the recovery menu.

That’s it. You have successfully rooted as well as installed ClockworkMod Recovery on your Galaxy Ace Plus smartphone. Now, you have open gates to the world of custom ROMs and Root-only Apps.

If this procedure helped you, then please head over to the XDA Forum to thank/donate to the original developer of this root method !

If this procedure helped you, please consider donating to the original developer or at least sending them a thank you.

Now that you are rooted, head here to learn some of the fun things you can do!

For all the devices we have rooting procedures for, head here.


Something Wrong? If you notice an issue with the procedure (broken link, steps out of date, etc.), use this form to let us know! Otherwise, if you just are having trouble with the procedure, reach out to us on Twitter, Facebook, or Google+.

  • Mika

    I get an error while i run the runme.bat file…bellow the lines, it’s written “error:device not found”. A little help please?

  • http://www.facebook.com/tny.mergeani Tny Mergeani

    i’m gettin’ an error when i run the file runme.bat…bellow the lines it’s written “error:device not found”. A little help please?

    • Mahesh Makvana

      Hey Tny,

      You must have drivers for your device installed on your PC. “Device Not Found” usually indicates that you do NOT have proper drivers installed. You can head to your manufacturer’s website and download the drivers.

      Hope it helps!

  • http://www.facebook.com/fathi.abushareha.96 Fathi Abushareha

    i got this when i run “runnme” :

    — pushing busybox

    4604 KB/s (1075144 bytes in 0.228s)

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — remounting /system

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — copying busybox to /system/xbin/

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting ownership

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — installing busybox

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — pushing SU binary

    failed to copy ‘filessu’ to ‘/system/bin/su’: No such file or directory

    — correcting ownership

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting symlinks

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — pushing Superuser app

    failed to copy ‘filesSuperuser.apk’ to ‘/system/app/.’: No such file or directo

    ry

    ALL DONE!!!

    Press any key to continue . . .

  • http://www.facebook.com/fathi.abushareha.96 Fathi Abushareha

    WHAT To DO

    — pushing busybox

    * daemon not running. starting it now *

    * daemon started successfully *

    failed to copy ‘filesbusybox’ to ‘/data/local/tmp/.’: Is a directory

    — correcting permissions

    chmod: /data/local/tmp/busybox: No such file or directory

    — remounting /system

    /sbin/sh: /data/local/tmp/busybox: not found

    — copying busybox to /system/xbin/

    dd: can’t open ‘/data/local/tmp/busybox’: No such file or directory

    — correcting ownership

    chown: /system/xbin/busybox: No such file or directory

    — correcting permissions

    chmod: /system/xbin/busybox: No such file or directory

    — installing busybox

    /sbin/sh: /system/xbin/busybox: not found

    rm: can’t remove ‘/data/local/tmp/busybox’: No such file or directory

    — pushing SU binary

    1391 KB/s (22228 bytes in 0.015s)

    — correcting ownership

    — correcting permissions

    — correcting symlinks

    rm: can’t remove ‘/system/xbin/su’: No such file or directory

    ln: /system/xbin/su: No such file or directory

    — pushing Superuser app

    failed to copy ‘filesSuperuser.apk’ to ‘/system/app/.’: Is a directory

    ALL DONE!!!

    Press any key to continue . . .

  • ThEgIGN

    Worked like a charm :P

    • Mahesh Makvana

      Glad we could help you!

      Stay tuned with us for more!

  • ajith

    what are the facts i should know before i start this process……is there any way it can harm my mobile?

  • luksul

    after i rooted my phone, i tried to install jellybean now my phone keeps restarting over and over help

  • dave

    hello but i have a massive issue with rooting my phone its form oz and it’s cwm is installing correctly but it’s not booting in to the program i’m holding all the buttons i need to down but it still won’t boot to it it just restarts it then stats the phone normally there any way around this ?? please help and thanks

    • http://www.techlisten.com Mahesh Makvana

      If you’re having issues getting into Recovery mode, then simply download the Quick Boot app, install it and hit the Recovery button given inside.

      Your device will instantly reboot into the Recovery mode.

      Hope it helps!

  • Zitein

    How long does it take to install recovery ?? Coz for my phone its taking too much time.

  • black_mordon

    plz reply if you really good at rooting

    what i have to do about this ?? i’m sick of this..

    — pushing busybox

    4604 KB/s (1075144 bytes in 0.228s)

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — remounting /system

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — copying busybox to /system/xbin/

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting ownership

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — installing busybox

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — pushing SU binary

    failed to copy ‘filessu’ to ‘/system/bin/su’: No such file or directory

    — correcting ownership

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting permissions

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — correcting symlinks

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    - exec ‘/system/bin/sh’ failed: No such file or directory (2) -

    — pushing Superuser app

    failed to copy ‘filesSuperuser.apk’ to ‘/system/app/.’: No such file or directo

    ry

    ALL DONE!!!

    Press any key to continue . . .

  • black_mordon

    2 comments in the past similar to this are abandoned…

  • sidd

    when i clicked on runme tha is showed system cannot find the path specified…….
    please help me

    • Dax Krishna

      Sidd, are you trying it on a Windows XP or older Windows PC? Did you tr this on Windows 7?

  • Cata

    THIS IS THE CORECT ANSWER!!!!!

    Step1:Mount /system

    Step2:Start runme.bat

    — pushing busybox

    1976 KB/s (1075144 bytes in 0.531s)

    — correcting permissions

    — remounting /system

    — copying busybox to /system/xbin/

    2099+1 records in

    2099+1 records out

    1075144 bytes (1.0MB) copied, 0.114272 seconds, 9.0MB/s

    — correcting ownership

    — correcting permissions

    — installing busybox

    — pushing SU binary

    1389 KB/s (22228 bytes in 0.015s)

    — correcting ownership

    — correcting permissions

    — correcting symlinks

    — pushing Superuser app

    1888 KB/s (785801 bytes in 0.406s)

    ALL DONE!!!

    Press any key to continue . . .

  • motherfucker

    works

  • Unknown

    Why i have already plugged in my device but this came out when run runme.bat what to do?

    — pushing busybox

    error: device not found

    — correcting permissions

    error: device not found

    — remounting /system

    error: device not found

    — copying busybox to /system/xbin/

    error: device not found

    — correcting ownership

    error: device not found

    — correcting permissions

    error: device not found

    — installing busybox

    error: device not found

    error: device not found

    — pushing SU binary

    error: device not found

    — correcting ownership

    error: device not found

    — correcting permissions

    error: device not found

    — correcting symlinks

    error: device not found

    error: device not found

    — pushing Superuser app

    error: device not found

    ALL DONE!!!

    Press any key to continue . . .

  • old father thames genesis

    it appears that this guy did not explain properly enough to do this rooting.
    you do need drivers from samsung on your desktop before you start and must be windows operating system.
    not linux etc.
    may i recommend you read up more on the subject before doing this to your phone

  • Dan

    Hey guys, I was just wondering if there’s any alternative for 5.0.2.8 Cwm. Cause It had bug issue, like, After I rooted my device, I restarted it and I got stuck on the Cwm recovery menu, and can’t past through it, i managed it by updating it to 6.0.4.5, but now the problem is, I can’t go to the recovery menu, white screen comes out, but when i restart it, I could boot normally.
    Please help guys.

  • Dan

    My concern is, I would like to install a newer format of cwm that is compatible with ace plus, cause the 5.0.2.8, it just keeps going to the recovery menu, even though i reboot my phone.