• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY+LOKI][CWM][MDK][VZW] SCH-I545 CWM v1.0

Search This thread

garwynn

Retired Forum Mod / Inactive Recognized Developer
Jul 30, 2011
5,182
8,589
NE Ohio
www.extra-life.org
DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.

CM: CWM Based Recovery for SCH-I545 (jfltevzw)

Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
If modifications deviate from CM source we will set up a new repo.
The recovery image has already been patched using the Loki method.
This also means it is tied to MDK signature and should only be flashed on MDK.

Screenshots: None

Latest Build: v1.1
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)

Flash Instructions - READ THESE CAREFULLY!!!
1) Download Zip
2) Unpack Zip and place items on your phone. Assumes you're doing commands from folder where files were extracted to.
For the sake of testing let's say /data/local/tmp like djrbliss used. (ADB push was used in that example)
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
3) Go to ADB shell, su and flash using following commands: (assumes path is /data/local/tmp for Step 2)
Code:
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
If successful you should see something similar to:
Code:
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Assuming you see the above, you should be ready to boot to recovery.

If you do not see this you should immediately flash the stock recovery by dd.
If you don't know how to do that, stop, ask for help. Let's try not to brick a phone doing this, okay? :)

Summary Changelog:
Code:
v1.1 - Correct typo on device name (in CM device tree).  Repo was still okay.
v1.0 - Initial based on Sprint progress (jf series shares same fstab)
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Verizon GS4 Device Repository

NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.

Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
Djrbliss for the Loki Method. (and for permission to include loki_flash in the zip!)
...and of course! You, the community, for your support as well! Thank you!
 
Last edited:

garwynn

Retired Forum Mod / Inactive Recognized Developer
Jul 30, 2011
5,182
8,589
NE Ohio
www.extra-life.org
OP has been updated with a Loki patched recovery image and flash instructions.

If you run into problems, STOP and post here with the issue.
Let's do this as safely as possible until we confirm some safe flashes.
 
Last edited:

garwynn

Retired Forum Mod / Inactive Recognized Developer
Jul 30, 2011
5,182
8,589
NE Ohio
www.extra-life.org
Again, asking that anyone who flashes this post their results. Obviously a lot of folks watching and although it shouldn't be an issue everyone likes to wait for first outside validation before flashing.
 

NxtGenCowboy

Senior Member
Dec 29, 2007
666
266
Chicago,IL
If it helps at all, I used the same process for the most part. It does indeed work.

1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!

only difference is I used TWRP :p

:cowboy:
 
Last edited:

t3project

Senior Member
Jun 14, 2010
1,732
1,371
If it helps at all, I used the same process for the most part. It does indeed work.

1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
covery /data/local/tmp/twrp.lok <
[+] Loki validation passed, flashing image.
2559+1 records in
2559+1 records out
10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
[+] Loki flashing complete!

only difference is I used TWRP :p

:cowboy:

where'd you get the twrp.lok file? following djrbliss' instructions? :D
 

t3project

Senior Member
Jun 14, 2010
1,732
1,371
im losing my damn mind. someone care to explain this?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #


i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #
 
Last edited:

fallingup

Senior Member
Mar 21, 2006
451
62
New Mexico
im losing my damn mind. someone care to explain this?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #


i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #

Derp. What permissions are you giving it?
 

trvrlol

Senior Member
Jul 27, 2010
77
153
No.
thats what I renamed it to since I used a twrp img

I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.

Here is the link: twrp.lok - 10.00 MB

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------

im losing my damn mind. someone care to explain this?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /adcard/loki_flash: not found
127|[email protected]:/sdcard #


i get this after a chmod of loki_flash. if i dont do chmod on it it says it cannot find the file loki_flash.....wtf?

Code:
[email protected]:/sdcard # /sdcard/loki_flash recovery /sdcard/twrp.lok
/sdcard/loki_flash recovery /sdcard/twrp.lok
sh: /sdcard/loki_flash: can't execute: Permission denied
126|[email protected]:/sdcard #

You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided. (At least that was my understanding when trying to debug the same issue!)
 
Last edited:

t3project

Senior Member
Jun 14, 2010
1,732
1,371
Derp. What permissions are you giving it?

all the good ones. haha 755

I tried just renaming the .img file to .lok, but it gave me a few errors. So using djrbliss's Loki tool (much thanks!) I generated a file for the TWRP recovery.

Here is the link: twrp.lok - 10.00 MB

---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------



You have to put the files in a folder like /data/local/tmp since the sdcard folder does not allow executables contrary to the instructions provided.

lol.....see told you i was losing it
 

joshw0000

Senior Member
Jun 15, 2010
3,984
402
I think I read in the other thread, they had success doing this on the pre-release kernal.

Sent from my SCH-I545 using Xparent Green Tapatalk 2
 

BladeRunner

Senior Member
Jan 15, 2012
1,449
392
It's in /system/etc.
not on my S4 it isn't lol. I get the successful flash, reboot to recovery, get stock recovery, reboot system from there and I then get the Samsung logo with the unlocked padlocked telling me SOMEthing unnoficiall got installed. Phone boots up and I boot back into recovery, still stock recovery, reboot system again and I get normal boot up, no padlock screen. I'm still on the mdk kernel so I will try flashing the pre-release kernel a little later and trying again.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    DISCLAIMER:
    Your device, your responsibility. I am not liable for anything you flash, including this.
    As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
    You've been warned.

    CM: CWM Based Recovery for SCH-I545 (jfltevzw)

    Features:
    This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
    If modifications deviate from CM source we will set up a new repo.
    The recovery image has already been patched using the Loki method.
    This also means it is tied to MDK signature and should only be flashed on MDK.

    Screenshots: None

    Latest Build: v1.1
    Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)

    Flash Instructions - READ THESE CAREFULLY!!!
    1) Download Zip
    2) Unpack Zip and place items on your phone. Assumes you're doing commands from folder where files were extracted to.
    For the sake of testing let's say /data/local/tmp like djrbliss used. (ADB push was used in that example)
    Code:
    adb push recovery.lok /data/local/tmp/
    adb push loki_flash /data/local/tmp/
    3) Go to ADB shell, su and flash using following commands: (assumes path is /data/local/tmp for Step 2)
    Code:
    adb shell
    su
    chmod 755 /data/local/tmp/loki_flash
    /data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
    If successful you should see something similar to:
    Code:
    [+] Loki validation passed, flashing image.
    2253+1 records in
    2253+1 records out
    9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
    [+] Loki flashing complete!
    Assuming you see the above, you should be ready to boot to recovery.

    If you do not see this you should immediately flash the stock recovery by dd.
    If you don't know how to do that, stop, ask for help. Let's try not to brick a phone doing this, okay? :)

    Summary Changelog:
    Code:
    v1.1 - Correct typo on device name (in CM device tree).  Repo was still okay.
    v1.0 - Initial based on Sprint progress (jf series shares same fstab)
    Source:
    CyanogenMod Official Repositories
    Device Dependencies:
    android_device_samsung_jf-common
    android_device_samsung_msm8960-common
    android_device_samsung_qcom-common
    Verizon GS4 Device Repository

    NOTE: Due to potential copyright issues I do not include a vendor repo.
    You can extract the files from the phone or ROM as needed - should you decide to build on your own.

    Credits:
    Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
    Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
    Testers: Mohogalore, robbyamor, crawj and others
    Steve Kondik (Cyanogen) for CM development and jf common work
    The CM maintainters who continue to improve CM along with Mr. Kondik
    The crew that is Paranoid Android - Pure Hybrid!
    Djrbliss for the Loki Method. (and for permission to include loki_flash in the zip!)
    ...and of course! You, the community, for your support as well! Thank you!
    2
    If it helps at all, I used the same process for the most part. It does indeed work.

    1|[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
    covery /data/local/tmp/twrp.lok <
    [+] Loki validation passed, flashing image.
    2559+1 records in
    2559+1 records out
    10484224 bytes transferred in 0.713 secs (14704381 bytes/sec)
    [+] Loki flashing complete!

    only difference is I used TWRP :p

    :cowboy:
    1
    I get a successful flash but still only get stock android recovery. I think it is because I can't find the install reovery.sh to delete it
    1
    Just want to update that the OP instructions do not work at all. After extracting recovery.lok and loki_flash to the same directory as you have adb, you the below code:

    Code:
    adb push recovery.lok /data/local/tmp/
    adb push loki_flash /data/local/tmp/
    adb shell
    su
    chmod 755 /data/local/tmp/loki_flash
    /data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
    1
    It worked fine two days ago, but now I see the instructions have changed and added the line "chmod 755". What is the reason for that? Would I need to do the process over again?

    The instructions I had worked and usually chmod 755 isn't needed.
    It just serves as a "catch-all" to avoid potential issues when trying to flash.
    Since it's clearer than what I wrote before I went ahead and included it.