Samsung recently unveiled its latest flagship device, the Galaxy S6. Having a little flashback, we might notice that Samsung has really done a great job with the Galaxy S series lineup. In this fast-paced world, technology never settles. Day by day, we see the launch of a new Android device. The Samsung Galaxy S4, which was launched way back in April 2013, is still considered to be a high-end Android smartphone even after the launch of its two successors. The reason why many people choose Samsung over any other smartphone manufacturer is primarily because of the fact that Samsung provides the latest Android updates to its smartphones instantaneously.

In the same manner, Samsung recently pushed the Lollipop update to some variants of the Galaxy S4. The specific variant which we are concerned about in this post is the Canadian model (SGH-I337M). As you already might know, upgrading to a newer version of Android might cause in loss of root.

If you had your Galaxy S4 SGH-I337M rooted before the update, then it might have restored back to stock and might have un-rooted itself. But, if you have never rooted your Galaxy S4 SGH-I337M, and want to root it while enjoying Android 5.0.1 Lollipop firmware on it, then follow this simple guide. In today’s guide, we are going to have a look at how to root the Samsung Galaxy S4 SGH-I337M (Canadian) on Android 5.0.1 Lollipop Firmware. In this guide, we’re going to have to use the CF-Auto-Root package.

So, without any further delay, let’s get right into the pre-requisites.

Also see:

Install Android 5.0.1 Lollipop Firmware on Galaxy S4 SGH-I337M (Canadian)


Obviously, you need some downloads and some pre-requisites before actually performing the root process. Make sure you set-up your Galaxy S4 SGH-I337M (Canadian) accordingly as follows.

  • Download the Root package for your Samsung Galaxy S4 SGH-I337M:
  • Download Odin: The application which you require to flash the root file on your Galaxy S4 is Odin.
  • Download and install the latest Samsung USB Drivers on your Windows PC.
  • To let your Computer recognize your Galaxy S4, you first need to enable USB Debugging. In order to do so, navigate to Settings> Developer Options, and enable the option. If you need a detailed guide on how to enable Developer Options on your Android device, just check out this guide : Enable Developer Settings.
  • Last, but certainly not the least, make sure that your Galaxy S4’s battery is more than 60% charged, to prevent any abrupt shutdowns while in the process of rooting.

Root Galaxy S4 SGH-I337M on Lollipop

Once you have all the requirements you need, you may now start the process of rooting your Galaxy S4. Just ensure that you follow all the steps with proper caution.

  1. Switch off your Samsung Galaxy S4, and reboot into the Download mode. In order to do so, press and hold the Volume Down, Home and Power buttons simultaneously while your phone is switched off. Once you come across the warning message, go ahead and press the Volume Up button.
  2. Now, unzip CF-Auto-Root-jfltecan-jfltevl-sghi337m.zipand open up the extracted folder on your PC.
  3. Launch Odin as an administrator.
  4. Connect your Galaxy S4 to your Computer with the USB Data Cable which came with it.
  5. You might now see one of the COM ports light up. This signifies that you Galaxy S4 is successfully connected to your PC. If not, try uninstalling and reinstalling the USB Drivers.
  6. Now click the AP button on Odin and select CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5. 
  7. Lastly, hit the Start button, and wait for a minute or two.
  8. Wait for your Galaxy S4 to reboot.

Voila! You’ve successfully gained root access on your Samsung Galaxy S4 SGH-I337M (Canadian) on Android 5.0.1 Lollipop! You can now enjoy the special privileges which only a rooted Android user can enjoy. To ensure if your Galaxy S4 has successfully been rooted, simply download this application and run it.

Root Check Price: Free


  1. Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5 is valid.
    Checking MD5 finished Sucessfully..
    Leave CS..
    All threads completed. (succeed 0 / failed 0)
    help me

  2. i did every thing bu i got problem with my wifi and speaker is not working pls help me and where did i get 5.0.1 firmware?

  3. you need to make sure you phone matches up with the model, SGH-1337M samsung galaxy s4 rogers, fido, canadian brands, canadian phone if it is american (USA) phone this might not work. this method worked nicley after failed attempt with kinggoroot.

  4. you need to have ODIN opened as ADMIN and have the download screen on your phone open then plug your phone in you should see some of the COM sections might light up, this tells you that your phone is plugged in ready to go, after that click on AP in the right side of ODIN then select the CF-Autoroot file that came in the folder. then wait for it then click start just wait about 30 seconds then you have root. good luck have fun. worked for me.

  5. THANK YOU! this worked great i now have a rooted 5.0.1 lolipop SGH-1337M Samsung Galaxy S4 here is a screenshot link. WORKED LIKE A FREAKING CHARM, PEOPLE WHO MADE THIS ROOT SETUP IS A GOD!

  6. once the root is done, i get the green odin that says Pass, but when the phone boots up all the apps just stop working everything is crashing

  7. so i did all of the above but once every thing is done, odin says Pass, when the phone is started everything has failed to launch. what do i do from here?

  8. Glad to know you managed to log in successfully. As for the Samsung keyboard force close issue, try wiping the keyboard app data from Settings> App, or updating the app via Play store.

  9. Hi!

    The rooting seemed to have worked.

    Unfortunately, I can’t use my phone now, cuz I had it password protected before the rooting and now “Unfortunately, Samsung keyboard has stopped”, so I can’t log in to my phone, but it reboots fine.

    Can anyone please help?

  10. Hi Fuji,

    The method described above has been tested and found working. I agree that the CF-Root file used is meant for KitKat but it worked nicely on Lollipop. Moreover, there are a few confirmations by some users in the comment too. It’s working for some and not for others. We would try to do some research and make the tutorial better.

  11. Enter CS for MD5..

    Binary Check MD5.. Do not unplug the cable..

    Please wait..

    Checking MD5 finished Sucessfully..

    Leave CS..


    Odin engine v(ID:3.1100)..

    File analysis..



    Get PIT for mapping..

    Complete(Write) operation failed.

    All threads completed. (succeed 0 / failed 1)

  12. I am having problems Odin3 doesnt work

    Enter CS for MD5..

    Binary Check MD5.. Do not unplug the cable..

    Please wait..

    Checking MD5 finished Sucessfully..

    Leave CS..


    Odin engine v(ID:3.1100)..

    File analysis..



    Get PIT for mapping.

  13. my play store and all almost all my other apps keep crashing after being rooted
    i cant even check if its rooted because root checker keeps crashing

  14. Worked kinda I think, keep getting unfortunately this and that has stopped can’t text can’t open appstore can’t do anything! I can make a phone call but contacts don’t show up fml

  15. OK, I got to where I wanted to be. I flashed stock FW, rooted, then installed CM12. My first attempt at this had issues with wifi and bluetooth, but at least the crashing was gone. I then noticed that I had to convert the filesystems to F2FS. So I did that, and repeated the rest of the necessary steps. I’m now on CM12 (5.0.1) and very happy with it!
    thanks for the help.
    side note–I’m surprised to notice the phone is no longer ‘rooted’ in this state. I don’t really care, but thought I’d end up being rooted.

  16. I launched root Checker, and it reported “Rooted”. I then installed TWRP to make a backup. It asked–want to reboot into recover to perform this. I said yes. In recovery, there were only about 6 menu options, none were ‘backup …”. I selected “reboot” and now the phone is really screwed up–when it tries to boot, the screen is black except for some popups which say they’re crashing. Media Storage was one of them, Settings, and System UI were others. The phone isn’t usable anymore. I guess I need to Odin back to stock?

  17. I’m very sorry for this distraction–the issue was simply my USB cable. I was using a very long one, so I switched to a short one, and everything works!
    Thanks a lot for your support!!

  18. Under Settings>Security>Find my mobile, I only have three options: Remote controls (off), SIM change alert, and Go to Website ().
    I don’t see any other options called Reactivation lock

  19. OK so my issue may be more basic!! I can’t even write to the phone’s drives from windows–the progress bar doesn’t start. This is probably the same issue that Odin is having. Is there some basic setting I’ve missed?
    I have no issue reading from the internal Flash and SD card, just can’t write to them. USB debugging on/off doesn’t help. I think Lolipop changed the permissions on writing to storage–maybe you know how to get around it?

  20. Questions are welcome–thanks for trying to help!
    I got the very same behaviour on both Odin’s.

  21. I extracted the .zip and got the .md5, and gave that to odin. If I extract that tar file, I see the cache.img and the recovery.img.
    Are you saying that I shouldn’t have supplied the .tar.md5 file to Odin’s AP file box?

  22. I should also say that the file is an .md5, not .zip as given in your instructions. The phone is fully stock 5.0.1

  23. I tried again with Odin3 v3.09. Same thing. Attached the screenshot.
    On the phone’s download screen, I see
    CURRENT BINARY: Samsung Official
    SYSTEM STATUS: Official
    CSB-CONFIG-LSB: 0x30
    EMAC BURST MODE: enabled
    START [224,1440]

    Downloading …
    Do not turn off Target !!
    (the start of a progress bar. just the rounded start of the line)

  24. I also failed with this method. I’m using odin 3.10, and the process sticks with recovery.img being the last status update. There is no error message.
    On the phone, I see the status lines in the upper left, with the last one in red: START [224,1440]. Under the android image, it says downloading, do not turn off target, and what looks like the first few pixels of a status bar.
    I’ve left it over 10 minutes in this state–it’s stuck.

This site uses Akismet to reduce spam. Learn how your comment data is processed.