How To Install CWM Recovery on AT&T or Verizon Galaxy S4! [SGH-i337/SCH-i545]

Click on Play button above or Click Here to Download High-Quality HD video to your Smartphone or Computer.

This video was brought to you by AndroidRoot.org. Click Here to See at AndroidRoot.org or Click Here to See on YouTube

There’s some great news for AT&T or Verizon Galaxy S4 users, bootloader is not unlocked BUT we have LOKI method by XDA user DJrbliss that allows developers to bypass bootloader check to enable custom recoveries and custom ROMs.

So, now you can install CWM recovery for AT&T or Verizon Galaxy S4.

Before we begin, you will need a rooted Galaxy S4.  For AT&T, see Motochopper root method and for Verizon, see Verizon root method.

NOTE: This method does NOT WORK on users on latest AT&T Galaxy S4 with MF3 firmware until we find a new method for it, sorry!

Step 1.  Download the two files onto your phone.

Download loki_flash

Download recovery.lok for your Galaxy S4

Use ES File explorer and browse to your Download folder, rename loki_flash.bin to loki_flash.

howto-install-cwm-recovery-on-att-verizon-galaxys4-1

Step 2. Copy both loki_flash and recovery_lok.

howto-install-cwm-recovery-on-att-verizon-galaxys4-2

Step 3. Paste the two files into /data/local/tmp directory.  (You might have to enable Root in ES File Explorer!)

howto-install-cwm-recovery-on-att-verizon-galaxys4-3

Step 4. Download and open Android Terminal Emulator app from Play Store.

howto-install-cwm-recovery-on-att-verizon-galaxys4-4

Step 5. Type:

su

Make sure you hit “Allow” or “Grant” if Superuser permission window pops up.

Then type:

cd /data/local/tmp

chmod 755 *

./lok_flash recovery recovery.lok

If you get successfull message, you can type the following to reboot into recovery:

reboot recovery

howto-install-cwm-recovery-on-att-verizon-galaxys4-5

Step 6. You should now be in CWM recovery.  Try rebooting and make sure you hit “Yes” if it asks you for root fix or recovery fix.  That’s it!  Now, you can backup/restore ROMs and install custom ROMs!howto-install-cwm-recovery-on-att-verizon-galaxys4-6

Credits – Djrbliss! <— Please donate to the developer of LOKI!

Need Help? Follow/add me on Google+, Facebook, or Twitter!
GooglePlus
Facebook
Twitter
Want to stay updated on latest Galaxy S4 Root news?
Sign up for our Galaxy S4 Root Newsletter here so you get ROM of the week and more!
Galaxy S4 Reference
You will need a rooted Galaxy S4 to install all ROM/kernels.
NOTE: THE AUTHOR OF THIS SITE IS NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE, PLEASE READ INSTRUCTIONS TWICE BEFORE TRYING IF THIS IS YOUR FIRST TIME TO ROOTING AND CUSTOM ROMS!

First time to rooting and custom ROMs?

Please see our Galaxy S4 Root FAQ FIRST!!!

Check out other custom ROMs!
Recent Android News from HighOnAndroid.com

138 thoughts on “How To Install CWM Recovery on AT&T or Verizon Galaxy S4! [SGH-i337/SCH-i545]

  1. Kyle

    When I type the ./lok_flash recovery recovery.lok i get can’t execute. permission denied… any ideas?

    Reply
      1. Kris

        Having the same issue …. checked the spelling and doing it correctly, checked SU and its working. Not sure whats going on

        Reply
  2. Kyle

    It even did it though when I spelled it correctly. I just used Motochopper and the install TWRP through Goo manager method.

    Reply
  3. wesley

    how do you expect us to root our AT&T galaxy s4 if you do provide a CWM in .tar format all i have sen are the .lok and when i look at that guide it tells me to use the CWM guide but when i go to download the recovery it says use the LOKI guide so its the never ending loop of neither guides work

    Reply
    1. Max Lee Post author

      You have to enable root access in ES File Explorer, sorry I forgot to put that in the instructions.

      Reply
      1. Mark

        Ok cool thanks, its still safe to do this method while having twrp as current recovery? Just rrying to be safe asking because of the whole bootloader jive

        Reply
        1. ruslanguns

          I used another Root File Manager…. let’s use Root Browser it worked for me…….

          I did the same method but after this comand :

          # ./loki_flash recovery recovery.lok

          I got::::

          sh: ./loki_flash: can’t execute: Permission denied
          #

          PLEASE HELP!!!

          Reply
  4. Todd

    I installed this without any problems on top of TWRP. However, I would like to go back to TWRP and the original method of install for TWRP didn’t work when i tried to change it back. Does anyone have the same problem?

    Reply
      1. Dusty

        The method on this page wouldn’t work for me. Said something like “loki 1.1 wrong version “. The XDA method (linked above) did work.

        Reply
  5. Carlos

    I had done the motochopper method and had twrp once i did this i now have CWM. My question is can is switch between both recoveries or one i installed CWM did that delete my twrp?

    Reply
  6. John

    This worked great thanks to everyone who worked on it! One question, which ROMS does this work with (AT&T model)?

    Reply
  7. luckybun

    worked great for me on ATT S4, but when I go backup on external sdcard, it said can’t find the path for backup, what should I have to do? thanks…

    Reply
  8. Curtis

    Hi

    I have a major problem and need your help, I have an ATT Galaxy S4.

    I rooted my phone through motochopper.

    I followed your instructions and installed CWM recovery on my phone… everything worked until I tried to back it up and a message saying “Error while making a backup image of /data!”

    So after that I went ahead and rebooted the phone…until I found out that the phone was stuck at the ATT boot screen and didn’t advance at all.

    I tried to restore what I had but there was a checking MD5 mismatch and I ended up wiping my data/ factory reset.

    The phone had reset but as I went through the set-up wizard… the phone said there was an problem with the “Settings”… and now I’m stuck.

    Please help, I don’t mind resetting my phone completely and installing everything back myself, but I can’t even get past the set up. Your help is greatly appreciated!

    Reply
  9. George

    In ES File Explorer there is nothing in the data folder when I look to put the recovery.lok and loki_flash files in there. I used Root Explorer and I was in fact able to get into the aforementioned data/local/tmp and I put the files in there. Followed instructions with terminal emulator however this message pops up “unable to chmod recover: no such file or directory. I have tried putting the files in different folders changing the the folder location via cd folder/location/whatever and I still get the same message. I also click root explorer in the options in ES File Explorer and it says superuser rights are given. Please help.

    Reply
  10. Joergen Ask

    Hi ! After ive sucsessfully booted into cwm … i rebooted the phone and switched it off again to turn it back on in cwm mode … but now its just showing odin mode. .. do i have to do the reboot recovery command everytime i want to go into cwm recovery ?

    Reply
  11. sameer somu

    Hi, i recently installed loki and twrp on my att i337 s4. i was wondering if i can perform this method to get CWM or do i need to remove twrp? thanks

    Reply
  12. luis

    Changed 755 to 766

    chmod 766 *

    // then press enter and type below and enter again……

    ./lok_flash recovery recovery.lok

    Reply
  13. Damon2nomaD

    After I type ./lok_flash recovery recovery.lok
    it tells me not found even I was able to complete the steps before.

    Reply
    1. Ryan

      Yea I had the same problem with not being able to chmod 755 * (“no such file or directory found”) and also when trying to do the loki_flash recovery recovery.lok step it says “./loki_flash: not found”.

      I got around the chmod 755 * issue by typing chmod 755 /data/local/tmp but haven’t been able to resolve the second issue…. could it have something to do with the fact that I created the local and tmp directories in the data folder when I originally started this process because I didn’t see them in ES File Explorer?

      Reply
      1. Max Lee Post author

        You are most likely in the wrong directory double-check where you unzipped the files to first.

        Reply
  14. Aimee

    I get to the point where I am almost done and after typing in
    ./loki_flash recovery recovery.lok

    I get the error “input file is not a valid Loki image”

    I am at a loss! I followed everrrrryyyything.

    Reply
  15. Chrys

    I just tried this after watching the video and got a return command that says “Loki aboot version does not match device.” I have tried it start to finish a couple times with the same error.

    I did grab the correct Verizion files too from your website… Any thoughts?

    Reply
          1. Chrys

            mekellly00, did you get this error as well? I have tried many times hoping that it would work one time. Even deleted the files and re-downloaded them a few times. No luck.
            I’m hoping Max can find a fix. I have a couple mods that I want to install.

            Reply
            1. mekelly00

              Yeah I got the same error and actually ended up soft bricking my phone. lucky for my i was able to download an official ME7 Stock firmware and flashed it with ODIN. Not going to root again until we get this bootloader UNLOCKED. i love big red and the reliability of their network, but damn i wish they would let us do what we want with our own devices.

              Reply
      1. A.J. Dixon

        Max,

        Any update on the “Loki aboot version does not match device” error? I have a Verizon GS4 with build number VRUAME7.

        Thanks

        Reply
        1. William

          Any update for “Loki aboot version does not match device” error? I have a Verizon GS4 with build number VRUAME7.

          Reply
  16. Tony

    I’ve got the ME7 update on my S4. I’m stuck in download mode after booting into recovery from TWRP. Any ideas how to get out of that?

    Reply
    1. Robert Messerle

      I ran into this same problem after attempting to use GooManager. Turn off your phone, then turn it back on by holding Volume Down + Power. When prompted, hit Volume DOWN, and it should boot up.

      Reply
  17. Logen

    Has anyone figured out the “Loki aboot version does not match device” problem yet? I keep getting the same message… :(

    Reply
  18. yl

    The loki method worked for me and I was able to install CWM recovery on my i337 S4. Then switched back to stock touchwiz ROM and it got updated to MF3. I was able to root again but now when I try to install CWM recovery using the loki method I get “Loki aboot version does not match device” error like other.

    In short, it seems like the latest update has broke loki method for installing CWM recovery.

    Reply
  19. ka7qqv

    Has anyone figured out the “Loki aboot version does not match device”
    problem yet? I keep getting the same message… :(

    so sad build jdq39.i545vruame7 sch i545

    Reply
  20. ben

    I am getting “Loki aboot versoin does not match device” as well. I am hoping this will get fixed soon. Verizon schi545 with vruame7

    Reply
  21. Yim

    I got the “Loki aboot version does not match device” also on vruame7. I attempted to use Goo manager to flash TWRP and that was a mistake! Now waiting for either TWRP or CWM update as I am currently without a functioning recovery.

    Reply
    1. MaryBeth

      I am in the same boat. My phone is currently stuck in Odin mode from when I tried to load recovery software. Everything say that you can’t do it but the previous one that said you could sent me to this one. Can you please adjust above where it says ATT and maybe put it in bold. Whenever the recovery comes out, you could be the first to feature it. There seem to be a lot of people waiting for it.

      Reply
      1. MastaSe7en

        Hey mary, i had the same issue happen as you, what you have to do is download the Stock ODIN .tar file (google it) depending on what version you were on, for example im on MK2 on my i337, open the tar.md5 file with winrar and extract the recovery.img and download a tool to convert .img to .tar file (again google) and then put your phone in download mode which its probably already in and then flash that recovery file, and your phone will boot up like normal

        Reply
  22. Z-man

    I just picked up my Verizon S4 and it is running vruame7, I’m also getting the Loki aboot version does not match device error.

    Reply
    1. Jdog

      This method will not work on the me7 build. If your phone is running this build then you will have to wait until the bootloader becomes unlockable to install custom recovery.

      Reply
  23. mattj

    Yes it seems if this dont work ……..DO NOT USE Goo Manager to get twrp
    when I did, I lost my recovery I cant even get back stock recovery if anybody
    got any idea let me no lol… But I would like to thank everybody out there for
    all your hard work try to fig this out !! !!

    Reply
    1. ChrisC

      yah goomanager and twrp install messed up mine as well, was stuck on download mode with an error “unable to normal boot”. had to do a hard reboot using the vol/home and power key. when it vibrates, remove you finger from the pwr key keeping it on the vols and home key.. should get you in.. took me a couple of tries to get it right.

      Reply
  24. ChrisC

    Seeing this error as others are , “Loki aboot version does not match device error” saw Max was looking into it ,any fixes yet?

    thanks in advance.

    Reply
  25. g1ova991

    I just rooted with Motochopper and downloaded ROM Manager from the Google Play store. It was pretty straight forward. I already backed up my current ROM, everything went well except I got an error towards the end of my Data back up in /tmp, but it baked it up and rebooted. I can see the back up in my ROM ManagerI’m the process of dowloading some ROMs to flash. I’ll update. I hope this helps!

    Reply
    1. g1ova991

      Worked like a charm. Now I have Google Play ROM and currently running MIUI (#sick, everyone should try it!)

      Reply
  26. melvin c.

    When I try the loki method it always tells me this recovery does not match you phone. I tried both the verizon one and the att and neither worked. I am on verizon me7, sch-i545. Then I tried the goo manager and it does work either. I am rooted, I used loki method to gain root. Can anyone help me.

    Reply
  27. Max

    Same issue here: “Loki aboot version does not match device”

    Any resolution to this?

    Am on Verizon build ME7, ROOTED, SuperSU active

    Reply
  28. sammy

    Nadaaaa…..de nadaaaaaa nothing……in i337 new firmware…shitttt..help…question if put my cell in stock with odin osea downgrade ….ayuda help please

    Reply
  29. Dennis

    I am getting the same message as everyone else… “Loki aboot version does not match device”. I have root and am looking to install customer recovery. Any help available yet, please?

    Reply
  30. Jamie

    Hey Max,
    After doing my research I have found you to be the s4 expert! Have you found anything for installing custom recovery on i337 running MF3, I have been trying with ZERO success. PLEASE HELP!!!!

    Reply
  31. Doug

    I’m confused on what the loki is actually for. I’m on the mdk and rooted with Motochopper. After that I installed rom manager and installed CWM recovery without a problem. Do I still need to use loki to get more features?

    Reply
  32. Stephen

    So I can get all the way to the end and i get a message that the version does not match my device. I’m running SGH 545 verizon. Can someone help?

    Reply
  33. hec143

    So it’s very obvious that most of us have the same message when we are trying to flash the loki hack through the emulator. I just hope that Max can get this fix or get some answers soon. Thank you devs for all your hard work!!!

    Reply
  34. Nick

    I was able to get past the “does not match version” error by downloading the newest loki_flash from the official site. But then I typed “./loki_flash recovery recovery.lok” into the terminal emulator and got this error: “syntax error: ‘newline’ unexpected”

    Any help?

    Reply
  35. Alex E

    Max Lee thank you for all your work and this awesome guide!

    Having some issue “aboot version does not match device”.

    Seems this problem only happens on the Verizon ME7, SCH-I545. (If that helps.) ((If you didn’t already know that lol.))

    I have not seen any updates to solve this yet we are eager. It seems.

    Any update?

    Reply
  36. Spencer

    Works up to ./loki_flash recovery recovery.lok then i get loki abut version does match device when i downloaded the right file from above links

    Reply
  37. cimbus

    I have a Samsung S4 Sch-i545 with build Vruame7; my understanding is that on this particular build their is no way possible to unlock the boot loader? I’ve rooted my phone but I want to flash back to the Mdk build it originally came with when I purchased it so I can then root, unlock the boot loader and then flash a custom ROM. Is this even possible? It is my understanding that once you update to the Vruame7 build via OTA you are basically stuck with it until somebody out there finds a way to unlock the boot loader on this particular build? I’ve also heard of some people complaining to Verizon and asking Verizon to put their phone with the Vruame7 build update back to the Mdk build and Verizon actually doing it; any truth to this? If so, how can I do this? I want to go back to the Mdk build because not only is it rootable but the boot loader can be unlocked to flash custom Roms.

    Reply
  38. dazz1996

    Ok everyone there is still no way to unlock the boot loader but if you go to XDA there is a safe strap method I’m running it now on my SGS4 on ME7 the rom I have installed is the GPI so go there.

    Reply
    1. dazz1996

      Have a look at this link http://forum.xda-developers.com/showthread.php?t=2441441
      I was late to getting the VSGS4 and it came out of the box or maybe the lady at the Verizon store updated it to the ME7 update but now I’m running the GPE rom and I love this phone a lot more, it was hard to work with Samsungs anything because all I have been running for the past 2 years is CM10 I hope this helps you and everyone on this site and happy hacking.

      Reply
  39. servo

    @dazz1996 Could you post a link to the safe strap method? I’m not finding it on XDA.

    And can we update THIS post to mention, at the very beginning, that it DOESN’T work with Verizon ME7??
    I read the first paragraph “There’s some great news for AT&T or Verizon Galaxy S4 users, bootloader is not unlocked BUT we have LOKI method by XDA user DJrbliss that allows developers to bypass bootloader check to enable custom recoveries and custom ROMs” and easily assumed we were talking specifically about ME7, since that’s the only bootloader that hasn’t been unlocked outright, AFAIK. Would’ve been great to know that this isn’t the case, before someone spends 1/2 hour following this great tutorial and ultimately just getting the “aboot version does not match device” error.

    There’s already a notice about it not working with AT&T MF3… just add “or Verizon ME7″.

    Reply
  40. Colvinm57

    I uses the safestrap method and was able to flash synergy rom to my phone. I have Verizon ME7. Here is the Link http://forum.xda-developers.com/showthread.php?t=2441441. After you install it on your phone, Go to page 11 and there is a link that will take to the rooms that work with this recovery. You can only uses those roms or you will brick your phone. Also if you go to youtube and search safestrap for verizon GS4 it shows you how to use it. I plan on flashing the hyperdrive rom in the next couple of days. Make sure you read the whole post, there is an additional download that has has to be flashed after the roms are flashed, or the roms won’t work.

    Reply
  41. Matt

    @Servo

    I’ve been hunting all day as I just got my new S4 as part of last weekends upgrade with unlimited data intact, (finally laid my weary Gnex to rest). I just realized today how much I’m going to miss that rom friendly device…

    Here’s a tutorial on the safe strap method. It’s not exactly what we hope for, but better than nothing for now.

    https://www.google.com/url?sa=t&source=web&cd=2&ved=0CCsQtwIwAQ&url=http%3A%2F%2Fm.youtube.com%2Fwatch%3Fv%3DKAtwt5jWP-Q%26desktop_uri%3D%252Fwatch%253Fv%253DKAtwt5jWP-Q&ei=mQJOUvr1C6PuyAH0koGYBQ&usg=AFQjCNGMdPnLxLDmT16E0COHGMyweuzpIg

    Reply
  42. Tristan D.

    I too have the Verizon i545. Mine is the “aboot version does not match the device” problem. I will be downloading the files from the actual site and posting my findings on here.

    Reply
  43. Brett

    After typing in ./loki_flash recovery recovery.lok it just says
    sh: ./loki_flash: not found
    using att sgh-i337 rooted with motochopper and I also tried chmod 755 * and chmod 766 *
    what do I need to do?

    Reply
    1. dazz1996

      Please people can you all read all the comments before posting, This method will not work if you updated to the newest build. Go to XDA developers and start reading up on your device there. Good luck

      Reply
  44. asukita

    I done everything but when i type ./loki_flash recovery recovery.lok tells me “bus error”, can someone help me?

    Reply
  45. akihiko_51

    hi,all I’m new here

    i hive samsung galaxy S4 i337, my phone is factory unlock. I’m on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself.
    when was on 4.2.2 i was getting the same thing at boot “”the custom screen with the lock that was unlocked showed up”” but was working ok and rooted.
    after the update, i still get the same thing at boot. Now i can’t root my phone on 4.3 because of the security issue to keep blocking. anything i do.

    Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block.

    I appreciate the help.

    Reply
  46. Craig

    I’m running MK2 on Verizon S4. Any way to get this working? Will it work the same as ME7 tutorial? Phone is already rooted.

    Thanks.

    Reply
  47. tutaj

    Hey I know this is off topic but I was wondering if you
    knew of any widgets I could add to my blog that automatically tweet my newest twitter updates.
    I’ve been looking for a plug-in like this for quite some time and was hoping maybe
    you would have some experience with something like this. Please let me know if
    you run into anything. I truly enjoy reading your blog and I look
    forward to your new updates.

    Reply
  48. DAVID_S

    MY FIRST PROBLEM WAS “PERMISSION DENIED” , THEN I CHANGE THE FILE PROPERTIES ON ES FILE EXPLORER (TO WRITE, READ AND EXECUTE, CHECK THE BOX), THEN I STUCK ON THE “VERSION DOES NOT MATCH DEVICE”….. I HOPE CHECK WHAT IS THE PROBLEM…

    Reply
  49. opel sklep

    I have been surfing on-line greater than 3 hours nowadays, yet I never discovered any attention-grabbing
    article like yours. It is lovely value enough
    for me. Personally, if all website owners and bloggers made
    just right content as you did, the internet will likely
    be a lot more useful than ever before.

    Reply
  50. bruce smith

    It’s obvious loki does not work for me7. Please stop trying it and use safestrap. Samsung has the keys to the locked bootloader and never opening it . You feel me people?!

    Reply
  51. Iran

    So, I have tried everything and still haven’t been able to install CWM. In my journey I have brick twice and recover. Bottom line I’m running AT&T SGH I337 on 4.2.2. I was able to root using Kingo app, however, no luck with recovery. I’ve tried ODIN, LOK, direct flash from CWM, and nothing. I’ll take any advise…

    Reply
  52. bruce smith

    Cannot unlock mf3. Samsung has the key and the bootloader will never be unlocked. Ya feel me dawg? Piece yo my bra fra anatha ma!!!

    Reply
  53. Gunner

    Method does not work on my S4 Active i537 AT&T, I have my phone rooted, but can find NO way to to install CWM or TWRP using any meathod here on on XDA’s site.
    Tried to install loki from both my phones card and my ext card. It either says “is a directory can’t execute” or “is a directory” shows the directory address, and them says Killed. Terminal Emulator is running with permission from SU.
    I wanted to install the new CM11 4.4.3 ROM

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>