Regain root on AT&T Galaxy S4 running I337UCUAMF3 firmware

Finally root has been achieved again on AT&T Galaxy S4 (SGH-I337) running I337UCUAMF3 firmware, thanks to jortex from xda who build a new root exploit for our device. We all know, the most recent OTA update from AT&T and Samsung (Build number: JDQ39.I337UCUAMF3) that we received a few weeks ago contains new security patch, as a result our device are unable to get root access back after installing the update, as the older root method isn’t working anymore.


For those who previously updating their Galaxy S4 firmware to MF3, now you can regain root privileges, although the new method isn’t a one-click solution, but it’s not as difficult as you think. However, an SD card is required to make the rooting process running well.

This method can operate directly on your phone so it does not need the help of any tool, but if you understand the adb (android debug bridge) you can use a PC/Laptop to perform this method. Below is a step by step how to root SGH-I337 running I337UCUAMF3 firmware.

  1. Make sure to backup all the external MicroSD card contents and format it again to exFAT.
  2. Grab a root exploit from jortex’s thread on xda and save the file on the external SD card.
  3. Extract using AndroidZip app or other apps that have the same capability, you will see a new folder “Root_for_ATTSG4_FM3″, open the folder and move all files/folders in it to the root of the external SD card.
  4. Download and install Terminal Emulator app from Play store.
  5. Now open the terminal app then run the following command:
  6. cd /mnt/extSdCard
  7. If the exploit goes well, then you will see a new app installed on the app drawer called SuperSU.
  8. To verify root, now try to install root checker app.
  9. galaxy s4 MF3 root

    Image: Samsung
    Screenshot: rjshenoy @xda

Now root privileges is reclaimed, it is time to freeze some unused bloatware and performing some tweaks. If you don’t want to accidentally accepting an update, you can block future OTA on AT&T Galaxy S4.



Filled Under:Root and Unlock
Related Mods

18 Responses

  1. ShugAugust 6, 2013 at 12:08 AMReply

    This is my first time rooting a device and this method worked PERFECTLY on my Galaxy S4 running MF3!!! THANK YOU Andromods!!!

  2. puv22August 6, 2013 at 9:51 AMReply

    Worked like a charm! Does anyone know how to re-enable tethering? Att seems to have added a check even when rooted.

    • DJLAXLAugust 9, 2013 at 8:00 AMReply

      Check this out: _ Created by Scott Rosler, the developer of CleanROM, worked on my Note 2 and now my S4.

  3. ArmandoAugust 6, 2013 at 2:31 PMReply

    Will I be able to install cyanogenmod 10.1aftrr I root?

    • Author

      FridzaAugust 6, 2013 at 6:33 PMReply

      Nope, there’s no custom recovery yet since the bootloader still locked.

  4. jessAugust 13, 2013 at 9:11 PMReply

    How will we know if a custom recovery becomes available? I’m really looking to flash a custom rom

  5. Trock4uAugust 17, 2013 at 8:41 AMReply

    After the root is done can I reformat my SD card back to the way it was? Sorry if this a stupid? But I new on this.

    • Author

      FridzaAugust 19, 2013 at 12:56 AMReply

      Yes you can.

  6. gwm209August 19, 2013 at 5:45 AMReply

    What am I doing wrong? After the first command it says I don’t have permission.

    • Author

      FridzaAugust 19, 2013 at 12:24 PMReply

      1. Have you mount the external SD card? by running this command -> cd /mnt/extSdCard
      2. Are you sure put everything directly on the microSD card and not in a folder on the microSD card
      3. When you get permission failed, just try to continuing running the root command -> ./ then verify it with root checker.

  7. danielAugust 19, 2013 at 10:50 AMReply

    this did not work i failed to get access after second command some 1 plz help

  8. TonySeptember 2, 2013 at 11:02 AMReply

    Is there sn unroot for this method?

    • Author

      FridzaSeptember 2, 2013 at 7:46 PMReply

      You can try Odin or simply use SuperSU, read it here.

  9. EWAISeptember 12, 2013 at 3:57 PMReply

    After I opened ./, I received messages “No such file or directory” for mnt/extSdCard/gs4ex, system/bin/ .ext, system/xbin/su, system/xbin/daemonsu

    Do you know what I need to do?

  10. kevinSeptember 23, 2013 at 3:11 PMReply

    how will i know if a custom recovery becomes available for this mf3 build?

  11. jc doradoSeptember 24, 2013 at 5:21 PMReply

    follow the instructions exactly the way they are you will have no problems

  12. jc doradoSeptember 24, 2013 at 5:22 PMReply

    make sure u have debugging enabled

  13. ahmedAugust 6, 2014 at 7:32 PMReply

    make sure u have debugging enabled

Leave a Reply