N900AUCUCMLG 4.4.2 KitKat

Search This thread

Anthonok

Senior Member
Talk about a pointless update.

From reading this thread and the threads on the other Note 3 versions, I gather that the best way to describe Kit Kat is... "it feels snappier". That's the only change.

Thanks a ton to DG for bringing us the leak tho, dude is awesome.

Isn't that a good thing?

Sent from my SM-N9005 using XDA Premium 4 mobile app
 

NightHawkUndead

Senior Member
Feb 23, 2012
923
555
Dalton, GA
Google Pixel 6 Pro
The update is great in my opinion. Phone is much more responsive and faster. Usable ram is incrcread. Lockscreen changes. And battery even on the first charge is great.

You guys are complaining about a leak. Just be thankful that DG released this and stop bickering.

Yes this update is minor as far as UI but kitkat itself isn't a drastic update.

If you enjoy being on the latest stock then take the jump and update. If you want root and customizable roms wait. That way the complaining is kept to a minimal level.
 

Crazypinoy9

Senior Member
Jun 19, 2010
331
57
I already understand that if I flash with odin it will wipe the phone but can anybody tell me if the phone gets wiped if I use the oneclick?
 

iteam

Senior Member
Jul 21, 2008
1,262
296
BOSTON
OTA & ART

I already asked and was answered but I want to be completely POSOTIVE that I will receive and be able to install the OTA when it arrives as it should contain ART correct? As that is what I am looking forward to.....

Also does the lock screen have the beautiful brushstrokes option like 4.3?
 
Last edited:

mircury

Senior Member
Jul 18, 2007
548
319
Louisville
I already asked and was answered but I want to be completely POSOTIVE that I will receive and be able to install the OTA when it arrives as it should contain ART correct?

No, Samsung chose to disable ART in the TW roms for the Note 3. The international version of 4.4 has it disabled too and that is the official version not a leak. No ART unless you are on AOSP for the Note 3.

Having said that, you aren't missing much with ART at the moment. There is a little benefit but not much. Some apps are still incompatible.
 
Last edited:
  • Like
Reactions: iteam

iteam

Senior Member
Jul 21, 2008
1,262
296
BOSTON
Does this include the watercolor ink effect lock screen effect? Before I go through with this I'd like to know.
Thanks
 

chrisrotolo

Senior Member
Nov 3, 2010
1,905
462
Corona, CA
Samsung Galaxy S23 Ultra
Can someone on KitKat try this and report back?

"Ok, I NEED somebody on kitkat to extract this and place both folders on the root of your internal memory.This cant cause any harm.Next restart 2 times & check if your rooted
https://mega.co.nz/#!TctXTLCY!JQsCLWJab3iZ233p0L74FxXmbucyIRx8ozhm9PgXb3E "

By @drakeymcmb

has anyone tried flashing any of these in heimdall? I think I will try heimdall first to 'try' to avoid Odin tripping any counters. Also, I'm going to attempt to flash everything except bootloaders. I am in the danger zone.
 

Walter.White

Senior Member
Nov 28, 2013
1,275
2,062
***This is what we know so far***

Version/Builds so far:- MI1 (4.3) MI9 (4.3) MJ5 (4.3) MLG (4.4.2) Future (4.4.2, OTA)

To downgrade back to MJ5..and still have Knox 0x0. Follow this guide

1. No ART support on Official or Leaked TW 4.4.2

2. Unofficial S-View covers don't work anymore. (Workaround for it here.. But it requires ROOT & Xposed Framework)

3. Google Wallet still doesn't do Tap and Pay and host card emulation seems to be disabled entirely.

4. If you Sim-Unlocked before (on MJ5, MI9 or MI1) using RegionAway... You will still be Sim-Unlocked after flashing this 4.4.2.

5. Here are the APN settings that you might have to add in manually after flashing this (For people who can get Mobile data to work). Look here.

6. From reading International N3 thread about 4.4.2.....Leaving out 4.4.2 BL causes bootloop...and the only way to get around that is by flashing 4.4.2 BL

7. Flashing through OneClickBin.exe doesn't trip any flags...but it does upgrade your BL.

8. Flashing 4.4.2 via OneClickBin.exe or via Odin *both* method will completely wipe off your phone. (So make backup first).

9. Exploit that Safestrap Recovery used **probably** doesn't work on 4.4.2 anymore. @Hashcode would have to update the SS.

10. Currently No Root for 4.4.2 (Universal RDLV and Kingoroot don't work). Possible but requires jumping through few hoops. Look here for details.

11. Once you upgrade BL to 4.4.2, you wont be able to downgrade back to 4.3. (You should be able to roll back to MJ5 but not to MI9. (Look above for "Version/Builds so far" for more details)

Why does #9 matter? Well because ..let's say someone in future discovers an exploit in 4.3 bootloader (MI9) that allows us to flash custom kernel/recoveries...people who upgrade now wont be able to downgrade back to 4.3 and they won't be able to use that exploit.

But let's say someone in future discovers an exploit for 4.4.2 BL then people who decide to stay on MI9 right now will still be able to use that exploit since we can upgrade but not downgrade.


So people who decide to upgrade right now are really taking a chance. And also keep in mind that with each update Knox/BL security gets more and more refined/harder to exploit.

@ryanbg and @Surge1223 are currently working on getting MI9 BL unlocked or find an exploit that allows us to flash custom recoveries/kernels.. And @ryanbg has made some pretty good progress so far.

And finally don't forget to Thank @designgears for this awesome leak.
 
Last edited:

ealvinito

Senior Member
Apr 21, 2012
453
52
Chicago, IL
Report back your findings.

As far as I know from reading International N3 thread about 4.4.2.....Leaving out 4.4.2 BL causes bootloop...and the only way to get around that is by flashing 4.4.2 BL

And also flashing through OneClickBin.exe doesn't trip any flags...but it does upgrade your BL.

And as far that root package that @drakeymcmb provided..I don't really know if that rooting method trips any flags. But the root Root de la Vega doesn't work on 4.4.2 anymore..
I wonder if Kingoroot still works (considering the exploit was closed source).

---------- Post added at 12:14 AM ---------- Previous post was at 12:04 AM ----------

By the way..does anyone know if the screen recording is working on 4.4.2 or did sammy left that out too kinda like ART?

Kingoroot confirmed not working.

Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
 

ealvinito

Senior Member
Apr 21, 2012
453
52
Chicago, IL
Only 1hr 14min of screen time but impressive.

Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
 

Attachments

  • 1390434247354.jpg
    1390434247354.jpg
    57.3 KB · Views: 773

chrisrotolo

Senior Member
Nov 3, 2010
1,905
462
Corona, CA
Samsung Galaxy S23 Ultra
Flashing without bootloaders FAILED!

Report back your findings.

As far as I know from reading International N3 thread about 4.4.2.....Leaving out 4.4.2 BL causes bootloop...and the only way to get around that is by flashing 4.4.2 BL

And also flashing through OneClickBin.exe doesn't trip any flags...but it does upgrade your BL.

And as far that root package that @drakeymcmb provided..I don't really know if that rooting method trips any flags. But the root Root de la Vega doesn't work on 4.4.2 anymore..
I wonder if Kingoroot still works (considering the exploit was closed source).

---------- Post added at 12:14 AM ---------- Previous post was at 12:04 AM ----------

By the way..does anyone know if the screen recording is working on 4.4.2 or did sammy left that out too kinda like ART?

Thanks for the heads up, I knew I would be taking a risk. My hope was that I might be able to downgrade to 4.3,etc with old bootloaders. I should have known better. I didnt flash anything that would be in ODIN BL folder, aboot.mbn, NON-HLOS.bin, rpm.mbn, sbl1.mbn, sdi.mbn, and tz.mbn

Output from heimdall fail at system:

Code:
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistrib
encouraged.

If you appreciate this software and you would like to support f
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading BOOT
0%
10%

20%

30%

40%

50%

60%

70%

80%

90%

100%
BOOT upload successful

Uploading RECOVERY
0%
8%

17%

26%

34%

43%

52%

61%

69%

78%

87%

95%

100%
RECOVERY upload successful

Uploading SYSTEM
0%
100%
ERROR: Failed to unpack received packet.

ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!

Ending session...
ERROR: libusb error -7 whilst receiving packet. Retrying...

Rebooting device...
Releasing device interface...

I also didn't flash userdata.img.ext4 in hope of not having to wipe.

Probably should have flashed BOOT last.. Oh welp, here's to hoping I can get into download mode and flash the oneclick.exe

cheers.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    !!! 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 you wait until someone confirms a flashing method that retains root or builds a custom rom.

    As usual, thanks to my anonymous source!

    N900AUCECMLG_OneClickBin.zip (N900AUCECMLG_OneClickBin.exe)
    Download: http://www.androidfilehost.com/?fid=23321874045862490
    MD5: B2BA36D086285DC5C0BCC7FB084D24A4
    SIZE: 1.5GB

    N900AUCECMLG.zip
    Download: http://www.androidfilehost.com/?fid=23321874045862491
    MD5: E92AF038F5259EFA1BEAE0613FC8C614
    SIZE: 1.5GB

    !!! WARNING !!! These both contain bootloaders!

    Code:
    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.id=KOT49H
    ro.build.display.id=KOT49H.N900AUCUCMLG
    ro.build.version.incremental=N900AUCUCMLG
    ro.build.version.sdk=19
    ro.build.version.codename=REL
    ro.build.version.release=4.4.2
    ro.build.date=Sat Jan  4 19:10:49 KST 2014
    ro.build.date.utc=1388830249
    ro.build.type=user
    ro.build.user=dpi
    ro.build.host=SWDC3313
    ro.build.tags=release-keys
    ro.product.model=SAMSUNG-SM-N900A
    ro.product.brand=samsung
    ro.product.name=hlteuc
    ro.product.device=hlteatt
    ro.product.board=MSM8974
    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=msm8974
    # ro.build.product is obsolete; use ro.product.device
    ro.build.product=hlteatt
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=hlteuc-user 4.4.2 KOT49H N900AUCUCMLG release-keys
    ro.build.fingerprint=samsung/hlteuc/hlteatt:4.4.2/KOT49H/N900AUCUCMLG:user/release-keys
    ro.build.characteristics=att
    # Samsung Specific Properties
    ro.build.PDA=N900AUCUCMLG
    ro.build.hidden_ver=N900AUCUCMLG
    ro.build.changelist=257432
    ro.product_ship=true
    ro.chipname=MSM8974
    ro.build.knox.container=
    # end build properties
    #
    # from device/samsung/hlteatt/system.prop
    #
    #
    # system.prop for msm8974
    #
    
    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
    
    # For sys info indication
    persist.radio.add_power_save=1
    
    debug.sf.hw=1
    debug.egl.hw=1
    debug.composition.type=c2d
    persist.hwc.mdpcomp.enable=true
    debug.disable.bwc=1
    debug.mdpcomp.logs=0
    dalvik.vm.heapsize=36m
    dev.pm.dyn_samplingrate=1
    persist.demo.hdmirotationlock=false
    
    ro.hdmi.enable=true
    tunnel.decode=true
    tunnel.audiovideo.decode=true
    lpa.decode=false
    lpa.use-stagefright=true
    persist.speaker.prot.enable=false
    qcom.hw.aac.encoder=true
    #
    # system props for the cne module
    #
    persist.cne.feature=0
    
    #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
    mm.enable.smoothstreaming=true
    media.aac_51_output_enabled=true
    #37491 is decimal sum of supported codecs in AAL
    #codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
    mm.enable.qcom_parser=37491
    
    # VIDC: debug_levels
    # 1:ERROR 2:HIGH 4:LOW 0:NOLOGS 7:AllLOGS
    vidc.debug.level=1
    #
    # system props for the data modules
    #
    ro.use_data_netmgrd=true
    persist.data.netmgrd.qos.enable=true
    ro.data.large_tcp_window_size=true
    
    #system props for time-services
    persist.timed.enable=true
    
    #
    # system prop for opengles version
    #
    # 196608 is decimal for 0x30000 to report version 3
    ro.opengles.version=196608
    
    # System property for cabl
    ro.qualcomm.cabl=1
    
    #
    # System props for telephony
    # System prop to turn on CdmaLTEPhone always
    telephony.lteOnCdmaDevice=0
    
    #Simulate sdcard on /data/media
    #
    persist.fuse_sdcard=true
    
    #
    #snapdragon value add features
    #
    ro.qc.sdk.audio.ssr=false
    ##fluencetype can be "fluence" or "fluencepro" or "none"
    ro.qc.sdk.audio.fluencetype=none
    persist.audio.fluence.voicecall=true
    persist.audio.fluence.voicerec=false
    persist.audio.fluence.speaker=true
    
    ro.qc.sdk.sensors.gestures=true
    ro.qc.sdk.gestures.camera=false
    ro.qc.sdk.camera.facialproc=false
    #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
    tunnel.audio.encode = true
    
    #use VERY_HIGH_QUALITY for audio resampler
    af.resampler.quality=4
    
    #SLook
    ro.slook.ver=1
    
    #
    # ADDITIONAL_BUILD_PROPERTIES
    #
    persist.sys.logkit.ctrlcode=0
    keyguard.no_require_sim=true
    ro.com.android.dateformat=MM-dd-yyyy
    ro.carrier=unknown
    ro.com.google.clientidbase=android-samsung
    ro.vendor.extension_library=/vendor/lib/libqc-opt.so
    persist.radio.apm_sim_not_pwdn=1
    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
    ro.build.scafe=americano
    ro.build.scafe.size=short
    ro.build.scafe.shot=double
    ro.sec.fle.encryption=true
    ro.hdcp2.rx=tz
    media.enable-commonsource=true
    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.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.alarm_alert=Alarm_Morning_flower.ogg
    ro.config.ringtone=ATT_Firefly_Default.ogg
    ro.config.notification_sound=Whisper.ogg
    ro.security.mdpp.ux=Enabled
    ro.setupwizard.mode=OPTIONAL
    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.build.selinux=1
    ro.kernel.qemu=0
    ro.config.tima=1
    ro.config.knox=1
    net.bt.name=Android
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.qc.sdk.izat.premium_enabled=0
    ro.qc.sdk.izat.service_mask=0x0
    persist.gps.qc_nlp_in_use=0
    ro.gps.agps_provider=1
    17
    I don't get it. No UI changes? What's the point. This phone is a beast with 3 gigs of ram how much snappier could it be

    Sent from my SAMSUNG-SM-N900A using xda app-developers app

    I am pretty sure you are in the group that pushes developers to release broken stuff that looks pretty.

    Like all the people *****ing about the no white status bar icons, they could care less about all of the fixes/updates under the hood.

    These people are called ricers in the car world.
    15
    ***This is what we know so far***

    Version/Builds so far:- MI1 (4.3) MI9 (4.3) MJ5 (4.3) MLG (4.4.2) Future (4.4.2, OTA)

    To downgrade back to MJ5..and still have Knox 0x0. Follow this guide

    1. No ART support on Official or Leaked TW 4.4.2

    2. Unofficial S-View covers don't work anymore. (Workaround for it here.. But it requires ROOT & Xposed Framework)

    3. Google Wallet still doesn't do Tap and Pay and host card emulation seems to be disabled entirely.

    4. If you Sim-Unlocked before (on MJ5, MI9 or MI1) using RegionAway... You will still be Sim-Unlocked after flashing this 4.4.2.

    5. Here are the APN settings that you might have to add in manually after flashing this (For people who can get Mobile data to work). Look here.

    6. From reading International N3 thread about 4.4.2.....Leaving out 4.4.2 BL causes bootloop...and the only way to get around that is by flashing 4.4.2 BL

    7. Flashing through OneClickBin.exe doesn't trip any flags...but it does upgrade your BL.

    8. Flashing 4.4.2 via OneClickBin.exe or via Odin *both* method will completely wipe off your phone. (So make backup first).

    9. Exploit that Safestrap Recovery used **probably** doesn't work on 4.4.2 anymore. @Hashcode would have to update the SS.

    10. Currently No Root for 4.4.2 (Universal RDLV and Kingoroot don't work). Possible but requires jumping through few hoops. Look here for details.

    11. Once you upgrade BL to 4.4.2, you wont be able to downgrade back to 4.3. (You should be able to roll back to MJ5 but not to MI9. (Look above for "Version/Builds so far" for more details)

    Why does #9 matter? Well because ..let's say someone in future discovers an exploit in 4.3 bootloader (MI9) that allows us to flash custom kernel/recoveries...people who upgrade now wont be able to downgrade back to 4.3 and they won't be able to use that exploit.

    But let's say someone in future discovers an exploit for 4.4.2 BL then people who decide to stay on MI9 right now will still be able to use that exploit since we can upgrade but not downgrade.


    So people who decide to upgrade right now are really taking a chance. And also keep in mind that with each update Knox/BL security gets more and more refined/harder to exploit.

    @ryanbg and @Surge1223 are currently working on getting MI9 BL unlocked or find an exploit that allows us to flash custom recoveries/kernels.. And @ryanbg has made some pretty good progress so far.

    And finally don't forget to Thank @designgears for this awesome leak.
    12
    just an update, All my testing has been for a loss. Long story short, 4.4.2 breaks root and no current exploit works, including Universal RDLV. I will continue searching for an exploit that may work.

    To those of you that wish to continue custom rom support, DO NOT USE THIS.

    To those who are not concerned with custom rom supprt, This leak is stable and is working fine aside from no working root exploit.

    Thanks to @designgears for this leaked package and everything else he has done for us. Everyone here should consider donating to this man, he has helped all of us in one way or another even if you didnt realize it.

    Well back to trying to find an exploit :)
    9
    So when is the official version coming out from ATT...