how do I install CWM recovery on att S4?

Search This thread

Gabe3

Senior Member
Sep 9, 2009
180
3
I'm following these instructions: http://wiki.cyanogenmod.org/w/Install_CM_for_jflte

using the "AT&T variant" instructions. I've already done root. I ran the "install-cwm.cmd". just a dos window blinked open and went away. I dont know how to install ClockworkMod Recovery. it just says rename to recovery.img. it doesn't say how to actually install it. when I "hold Volume Up, Home & Power.". the phone goes into android system recovery 3e instead of CWM recovery. I assume CWM recovery is not installed and the instructions don't say how to install it.

thanks.
 

spamtrash

Senior Member
Nov 9, 2008
1,056
251
Krasnoyarsk
I ran the "install-cwm.cmd". just a dos window blinked open and went away. I dont know how....

Ekhm... may I ask one small question?
Of course, while reading the prerequisites, and verifying the tools you are using, you have recognized that Loki uses adb command?
And, knowing that, you of course do know that to do anything via adb from Windows based PC, you need to have the Android SDK installed and working?

EDIT: one more question: just by the accident, have you even though about placing your question in ATT section, or even looking for your solution, for example here???
 
Last edited:
  • Like
Reactions: Fressh1er

Gabe3

Senior Member
Sep 9, 2009
180
3
Ekhm... may I ask one small question?
Of course, while reading the prerequisites, and verifying the tools you are using, you have recognized that Loki uses adb command?
And, knowing that, you of course do know that to do anything via adb from Windows based PC, you need to have the Android SDK installed and working?

EDIT: one more question: just by the accident, have you even though about placing your question in ATT section, or even looking for your solution, for example here???

still lost. I dont see a guide in the att section. where can I get the latest CWM Recovery lok file?
 
Last edited:

spamtrash

Senior Member
Nov 9, 2008
1,056
251
Krasnoyarsk
AT&T Galaxy S4 SGH-i337

I was going to use this guide: http://galaxys4root.com/galaxy-s4-root/how-to-install-cwm-recovery-on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/

but the recovery lok file in the guide is pretty old.

Is it really so hard to go to General section of I337 to find this thread, or, if you'd look deeper, to look into this, where, in section Step 2: Rooting Your Device - you have very specific split what is for which model is what type of custom recovery (and, it seems that CWM is for I337M, a Canadian version ONLY) preferred, at least for rooting.
however, Section 3 provides easy instruction step by step what you shall do...
 

Joku1981

Senior Member
Jun 4, 2012
3,084
912
Last edited:

Gabe3

Senior Member
Sep 9, 2009
180
3
Is it really so hard to go to General section of I337 to find this thread, or, if you'd look deeper, to look into this, where, in section Step 2: Rooting Your Device - you have very specific split what is for which model is what type of custom recovery (and, it seems that CWM is for I337M, a Canadian version ONLY) preferred, at least for rooting.
however, Section 3 provides easy instruction step by step what you shall do...

looks like motochopper root failed. It said failed when I did it but it prompted me to reboot the phone so I thought it worked and superuser app got installed. superuser says "the superuser binary (su) must be updated. please choose an installation method. recovery mode installation is recommended for htc devices."

also, when I use root checker it says I don't have root. looks like back to step 1. I tried motochopper again and it still says failed.
 
Last edited:

Gabe3

Senior Member
Sep 9, 2009
180
3
just used the CASUAL application and checked root checker, still no root.

heres the casual log:

[*] Waiting for device...
Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything.
[*] Device found.
[*] Pushing exploit...
2816 KB/s (1283460 bytes in 0.445s)
[*] Pushing root tools...
3916 KB/s (96260 bytes in 0.024s)
4132 KB/s (1578585 bytes in 0.373s)
[*] Pushing recovery to device...
4225 KB/s (10484224 bytes in 2.423s)
[*] Rooting phone...
[+] This may take a few minutes.

[-] Failure.

installing superuser to system partition
/system/bin/sh: su: not found

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=KOT49H

ro.build.display.id=KOT49H.I337UCUFNB1

ro.build.version.incremental=I337UCUFNB1

ro.build.version.sdk=19

ro.build.version.codename=REL

ro.build.version.release=4.4.2

ro.build.date=Tue Feb 11 22:30:13 KST 2014

ro.build.date.utc=1392125413

ro.build.type=user

ro.build.user=dpi

ro.build.host=SWDD5521

ro.build.tags=release-keys

ro.product.model=SAMSUNG-SGH-I337

ro.product.brand=samsung

ro.product.name=jflteuc

ro.product.device=jflteatt

ro.product.board=MSM8960

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=msm8960

# ro.build.product is obsolete; use ro.product.device

ro.build.product=jflteatt

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=jflteuc-user 4.4.2 KOT49H I337UCUFNB1 release-keys

ro.build.fingerprint=samsung/jflteuc/jflteatt:4.4.2/KOT49H/I337UCUFNB1:user/release-keys

ro.build.characteristics=att

# Samsung Specific Properties

ro.build.PDA=I337UCUFNB1

ro.build.hidden_ver=I337UCUFNB1

ro.build.changelist=505595

ro.product_ship=true

ro.chipname=apq8064

# end build properties

#

# from device/samsung/jflteatt/system.prop

#

#

# system.prop for surf

#



ro.sf.lcd_density=480



rild.libpath=/system/lib/libsec-ril.so

rild.libargs=-d /dev/smd0

persist.rild.nitz_plmn=

persist.rild.nitz_long_ons_0=

persist.rild.nitz_long_ons_1=

persist.rild.nitz_long_ons_2=

persist.rild.nitz_long_ons_3=

persist.rild.nitz_short_ons_0=

persist.rild.nitz_short_ons_1=

persist.rild.nitz_short_ons_2=

persist.rild.nitz_short_ons_3=

ril.subscription.types=NV,RUIM

DEVICE_PROVISIONED=1

debug.sf.hw=1

debug.egl.hw=1

debug.composition.type=gpu

dalvik.vm.heapsize=36m

debug.enable.wl_log=1

persist.hwc.mdpcomp.enable=true

debug.mdpcomp.logs=0



#

# system props for the cne module

#

persist.cne.feature=0



lpa.decode=false

tunnel.decode=true

tunnel.audiovideo.decode=false

lpa.use-stagefright=true

qcom.hw.aac.encoder=true



#system props for the MM modules



media.stagefright.enable-player=true

media.stagefright.enable-http=true

media.stagefright.enable-aac=true

media.stagefright.enable-qcp=true

media.stagefright.enable-fma2dp=true

media.stagefright.enable-scan=true

mmp.enable.3g2=true

media.aac_51_output_enabled=true

#33395 is sum of supported format flags in AAL

#Formats: AVI AC3 ASF AAC QCP DTS 3G2

mm.enable.qcom_parser=33395



#

# system props for the data modules

#

ro.use_data_netmgrd=true

persist.data.netmgrd.qos.enable=false



#system props for time-services

persist.timed.enable=true



# System props for audio

persist.audio.fluence.mode=endfire

persist.audio.vr.enable=false

persist.audio.handset.mic=digital

persist.audio.lowlatency.rec=false



# System prop to select audio resampler quality

af.resampler.quality=255

# System prop to select MPQAudioPlayer by default on mpq8064

mpq.audio.decode=true



#

# system prop for opengles version

#

# 196608 is decimal for 0x30000 to report version 3

ro.opengles.version=196608



# system prop for requesting Master role in incoming Bluetooth connection.

#

ro.bluetooth.request.master=true

#

# system prop for Bluetooth Auto connect for remote initated connections

#

ro.bluetooth.remote.autoconnect=true

# system property for Bluetooth discoverability time out in seconds

# 0: Always discoverable

#debug.bt.discoverable_time=0



#system prop for switching gps driver to qmi

persist.gps.qmienabled=true



#System prop to enable ehrpd capability

ro.config.ehrpd=true



# System property for cabl

ro.qualcomm.cabl=0





# System prop for sending transmit power request to RIL during WiFi hotspot on/off

#

ro.ril.transmitpower=true





#Simulate sdcard on /data/media

#

persist.fuse_sdcard=true

ro.hwui.text_cache_width=2048



#

# Supports warmboot capabilities

#

ro.warmboot.capability=1



#

#snapdragon value add features

#

ro.qc.sdk.audio.ssr=false

##fluencetype can be "fluence" or "fluencepro" or "none"

ro.qc.sdk.audio.fluencetype=none

ro.qc.sdk.camera.facialproc=true

ro.qc.sdk.gestures.camera=false

ro.qc.sdk.sensors.gestures=false

#property to check if dynamic resolution change is supported in framework

ro.streaming.video.drs=true

#property to enable user to access Google WFD settings.

persist.debug.wfd.enable=1

#property to choose between virtual/external wfd display

persist.sys.wfd.virtual=0



#system prop for setting rmnet mux mode

persist.rmnet.mux=disabled



#

# System prop for Tvout/HDMI

#

persist.sys.camera.transform=0

persist.sys.camera.connect=0

persist.sys.videomode=0

ro.hdmi.enable=true





# System property for Default Brightness

ro.lcd_min_brightness=10

ro.lcd_brightness=143



# System proverty for sys info indication

persist.radio.add_power_save=1



# Keep SIM state on LPM mode

persist.radio.apm_sim_not_pwdn=1



# use se table when search list

persist.radio.use_se_table_only=1



# System prop for PLMN

persist.radio.fill_eons=1



# System prop for SPN

persist.radio.prefer_spn=0



media.enable-commonsource=true



#

# ADDITIONAL_BUILD_PROPERTIES

#

dalvik.vm.heapstartsize=8m

dalvik.vm.heapgrowthlimit=128m

dalvik.vm.heapsize=512m

dalvik.vm.heaptargetutilization=0.75

dalvik.vm.heapminfree=2m

dalvik.vm.heapmaxfree=8m

keyguard.no_require_sim=true

ro.com.android.dateformat=MM-dd-yyyy

ro.carrier=unknown

ro.vendor.extension_library=/vendor/lib/libqc-opt.so

ro.build.scafe=americano

ro.build.scafe.size=short

ro.build.scafe.shot=single

ro.hdcp2.rx=tz

ro.secwvk=144

ro.securestorage.support=true

security.mdpp=None

ro.security.mdpp.ver=1.0

ro.security.mdpp.release=2

security.mdpp.result=None

ro.sec.fle.encryption=true

ro.hwui.texture_cache_size=48

ro.hwui.layer_cache_size=32

ro.hwui.path_cache_size=8

ro.hwui.shape_cache_size=2

ro.hwui.gradient_cache_size=1

ro.hwui.drop_shadow_cache_size=4

ro.hwui.texture_cache_flush_rate=0.5

ro.hwui.text_small_cache_width=1024

ro.hwui.text_small_cache_height=512

ro.hwui.text_large_cache_width=2048

ro.hwui.text_large_cache_height=1024

ro.error.receiver.default=com.samsung.receiver.error

ro.config.ringtone=ATT_Firefly_Default.ogg

ro.config.notification_sound=Whisper.ogg

ro.config.alarm_alert=Alarm_Morning_flower.ogg

ro.config.media_sound=Media_preview_Touch_the_light.ogg

ro.security.mdpp.ux=Enabled

ro.setupwizard.mode=OPTIONAL

ro.com.google.clientidbase=android-samsung

ro.com.google.clientidbase.ms=android-att-us

ro.com.google.clientidbase.am=android-att-us

ro.com.google.clientidbase.yt=android-samsung

ro.com.google.clientidbase.gmm=android-samsung

ro.com.google.gmsversion=4.4.2_r1

persist.sys.dalvik.vm.lib=libdvm.so

ro.kernel.qemu=0

ro.build.selinux=1

ro.config.knox=1

ro.config.tima=1

ro.config.timaversion=2.0

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.qc.sdk.izat.premium_enabled=1

ro.qc.sdk.izat.service_mask=0x5

persist.gps.qc_nlp_in_use=0

ro.gps.agps_provider=1



[*] Installing Recovery
/system/bin/sh: su: not found

[*] rebooting into recovery. Ensure that you "Install Superuser" in after you reboot into Android for security reasons!
done
Script Complete
 

Joku1981

Senior Member
Jun 4, 2012
3,084
912
looks like motochopper root failed. It said failed when I did it but it prompted me to reboot the phone so I thought it worked and superuser app got installed. superuser says "the superuser binary (su) must be updated. please choose an installation method. recovery mode installation is recommended for htc devices."

also, when I use root checker it says I don't have root. looks like back to step 1. I tried motochopper again and it still says failed.
The thread u created was for install custom recovery or root ur phone? If you want root ur phone too, follow this GUIDE, special for your device model.
 
Last edited:
Aug 21, 2014
8
0
I'm finally able to give an answer instead of reading one.

I sent you a personal message with my post since I can't post links yet, as I've just made an account. Been lurking forever it was time. I will post it here when I can for any future passersby.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I ran the "install-cwm.cmd". just a dos window blinked open and went away. I dont know how....

    Ekhm... may I ask one small question?
    Of course, while reading the prerequisites, and verifying the tools you are using, you have recognized that Loki uses adb command?
    And, knowing that, you of course do know that to do anything via adb from Windows based PC, you need to have the Android SDK installed and working?

    EDIT: one more question: just by the accident, have you even though about placing your question in ATT section, or even looking for your solution, for example here???