I337UCUFMLD 4.4.2 KitKat Leak
- Thread starter designgears
- Start date
Nvm. I figured it out.
There's a One Click file and there's a file with the info for Odin.
Thank you DesignGears for keeping us on the bleeding edge! Although I'm hesitant to flash before knowing for sure if root is possible on this build.
Were you able to extract system.img by chance? I keep trying with ext4_unpacker (Windows) and it just hangs for me.
If you downloaded the second zip (non oneclick) them there is no need to extract.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I did and they are in raw img form still. I downloaded it last night. Did it change since then?
Attachments
Last edited:
Sir ,
Please Tell Me ... How To Install .. I Want To Install 4.4.2 Kitkat Update:angel:
This is not the Kitkat update this is a leak there is no telling if you flash this that you will be able to receive the OTA. The same thing happened with the S4 active the only unbrick method is DG's oneclick but it is MF1 a prerelease version that the OTA won't work on. So just be prepared to be going to a Best buy and maybe the Samsung Rep will flash the OTA.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Oh okay... I thought you were talking about extracting system from the One Clock.
From there I use dsixda's kitchen. But there are other methods as well. Searching should give you plenty of results.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
No I'm trying to crank open the system img so I can make a flashable zip. I don't that kitchen extracts ext4 files but I'll give it a go.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Well upload and share that ish and save me the trouble
Sent from my SGH-I337 using XDA Premium 4 mobile app
Well upload and share that ish and save me the trouble
Sent from my SGH-I337 using XDA Premium 4 mobile app
I haven't fully packaged it or make a script for it. I'm using the NA5 international leak right now to get a start on porting the mods over to 4.4. From this leak I've only flashed the modem.
I know my buddy @muniz_ri is working on it ...... spoke with him last night. ... give him a day or two or maybe today...
:good:muniz_ri said:
Swyped from MK2 Dark Venomous X1
Last edited:
I took the plunge and flashed the leak using the following Odin tar I put together from all the contents, including bootloader, in the second file in the OP:
https://mega.co.nz/#!9pF0DZDA!nkZYmEN6aE2K_ZSMRmerksdqx9S8kwlQY4UnG3BDQ_c
MD5: D5C7470C240A9A74A6365C5575D78597
So far everything seems to be working just as well as stock MK2 and the leak is definitely stable enough to be a daily driver. No major performance improvements(maybe just slightly) and a few minor UI changes, e.g camera widget in lockscreen.
I had the same concern but now that we have the full MK2 tar files we can create a work-around to sideload the next OTA following the same methodology that gtj0 used to get from the MJ6 leak to MJ9(http://xdaforums.com/showthread.php?t=2526964). I can create the files once the next ota is released unless someone beats me to it.
Many Thanks to the OP for sharing this leak!
EDIT 1/27/2014: It has been confirmed that the leak's aboot has the same qfuse counter(4) as MK2. This means that you are able to flash back to MK2 after flashing MLD.
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
I tried Kingo but it didn't work. Hope to get root soon.
https://mega.co.nz/#!9pF0DZDA!nkZYmEN6aE2K_ZSMRmerksdqx9S8kwlQY4UnG3BDQ_c
MD5: D5C7470C240A9A74A6365C5575D78597
So far everything seems to be working just as well as stock MK2 and the leak is definitely stable enough to be a daily driver. No major performance improvements(maybe just slightly) and a few minor UI changes, e.g camera widget in lockscreen.
I had the same concern but now that we have the full MK2 tar files we can create a work-around to sideload the next OTA following the same methodology that gtj0 used to get from the MJ6 leak to MJ9(http://xdaforums.com/showthread.php?t=2526964). I can create the files once the next ota is released unless someone beats me to it.
Many Thanks to the OP for sharing this leak!
EDIT 1/27/2014: It has been confirmed that the leak's aboot has the same qfuse counter(4) as MK2. This means that you are able to flash back to MK2 after flashing MLD.
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
I tried Kingo but it didn't work. Hope to get root soon.
Last edited:
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
51!!! WARNING !!! These both contain bootloaders!
If you don't know what these are, or how to use them, or want to keep root, I would suggest hitting the back button.
As usual, thanks to my anonymous source!
I337UCUFMLD_OneClick.zip (I337UCUFMLD_OneClick.exe)
Download: http://www.androidfilehost.com/?fid=23329332407566813
MD5: AD1150D2F94852912249F9D8476D461A
SIZE: 1.51GB
I337UCUFMLD.zip
Download: http://www.androidfilehost.com/?fid=23329332407566810
MD5: B3E3C180DC8128D4532E39CD29950BB5
SIZE: 1.51GB
Known Issues:
Sporadic device reboot is observed when using video codec related function. This is due to an issue related to video codec.
Code:# begin build properties # autogenerated by buildinfo.sh ro.build.id=KOT49H ro.build.display.id=KOT49H.I337UCUFMLD ro.build.version.incremental=I337UCUFMLD ro.build.version.sdk=19 ro.build.version.codename=REL ro.build.version.release=4.4.2 ro.build.date=Thu Jan 2 17:30:32 KST 2014 ro.build.date.utc=1388651432 ro.build.type=user ro.build.user=dpi ro.build.host=SWDC3404 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 I337UCUFMLD release-keys ro.build.fingerprint=samsung/jflteuc/jflteatt:4.4.2/KOT49H/I337UCUFMLD:user/release-keys ro.build.characteristics=att # Samsung Specific Properties ro.build.PDA=I337UCUFMLD ro.build.hidden_ver=I337UCUFMLD ro.build.changelist=232901 ro.product_ship=false 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 # Boot animation fps boot.fps=25 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 persist.log.seclevel=1 persist.translation.assistant=0 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=1 security.mdpp.result=None ro.security.mdpp.ux=Enabled 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.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.setupwizard.mode=OPTIONAL ro.com.google.apphider=on 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_r1 persist.sys.dalvik.vm.lib=libdvm.so ro.kernel.qemu=0 ro.build.selinux=1 ro.config.knox=1 ro.config.tima=1 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=114I took the plunge and flashed the leak using the following Odin tar I put together from all the contents, including bootloader, in the second file in the OP:
https://mega.co.nz/#!9pF0DZDA!nkZYmEN6aE2K_ZSMRmerksdqx9S8kwlQY4UnG3BDQ_c
MD5: D5C7470C240A9A74A6365C5575D78597
So far everything seems to be working just as well as stock MK2 and the leak is definitely stable enough to be a daily driver. No major performance improvements(maybe just slightly) and a few minor UI changes, e.g camera widget in lockscreen.
I had the same concern but now that we have the full MK2 tar files we can create a work-around to sideload the next OTA following the same methodology that gtj0 used to get from the MJ6 leak to MJ9(http://xdaforums.com/showthread.php?t=2526964). I can create the files once the next ota is released unless someone beats me to it.
Many Thanks to the OP for sharing this leak!
EDIT 1/27/2014: It has been confirmed that the leak's aboot has the same qfuse counter(4) as MK2. This means that you are able to flash back to MK2 after flashing MLD.
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
I tried Kingo but it didn't work. Hope to get root soon.138Please, do not ask for instructions. Seriously, if you do not know how to do this, then you probably shouldn't be trying.
You can seriously mess up your phone. Please read anything and everywhere on how to flash a rom. Before you attempt something like this, read how to back up your device.
As with any flashing, it is done at your own risk and believe me, there is risk involved.
You need to come to a thread like this packed with knowledge. Please do not come to a thread like this, looking for knowledge.
