|ROM| KitKat 4.4 ★|★ Let's Play v2.1 ★|★ S4 Google Play Edition | 1 Dec 2013 |

Status
Not open for further replies.
Search This thread

wcoast

Senior Member
Jul 20, 2011
2,091
611
Los Angeles
well I was back to stock rom with MDB baseband. And I root it with motochopper and install the TWRP recovery. Then I install this rom, and flash the loki file that shows on the first page of this thread. and reboot, baseband unknown. I tried to baseband thread on the general section by using recovery to flash the those zip. none of those works.

ODIN is the best way to flash modem
 

PterGriffin

Member
Sep 16, 2010
39
7
ROM has nothing to do with baseband, Baseband is something you flash separately,go to general section and you will find solution to your issue. Good luck

---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------



Faux stock mod kernel is awesome with super battery life but doesn't support FauxSound

ROM has nothing to do with baseband??? is that a serious statement?
 
G

GuestX0019

Guest
Those are ATT modems and I am on Rogers

---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------


I could not find latest modem (for Rogers) in zip format.

I thought I saw a flashable one in 2Tone5's radio thread--:good:
 

shopkins82

Member
Jan 17, 2012
33
5
Any plans to bring this up to 4.4.2? I had been running this at 4.3 and 4.4, but went to Dandroid for 4.4.2. I'm having a few issues with Dandroid and some of the default GB mods are a bit heavy-handed for my tastes. I'm considering coming back to Let's Play, especially if it moves up to 4.4.2.
 

upndwn4par

Inactive Recognized Developer
Jan 22, 2012
3,640
10,375
New Jersey
Any plans to bring this up to 4.4.2? I had been running this at 4.3 and 4.4, but went to Dandroid for 4.4.2. I'm having a few issues with Dandroid and some of the default GB mods are a bit heavy-handed for my tastes. I'm considering coming back to Let's Play, especially if it moves up to 4.4.2.

I haven't decided yet. TBH, I've been thinking of closing this thread since there seems to be little interest in this ROM.
 

Danvdh

Senior Member
Sep 5, 2012
6,143
19,870
Toronto, Canada
I haven't decided yet. TBH, I've been thinking of closing this thread since there seems to be little interest in this ROM.

ugh oh, someone I know isn't going to be happy

she doesn't use my ROM for 2 reasons

1) OTF Battery mod
2) because it's my ROM

hopefully you change you're mind, I have a feeling 4.4.2 is sticking around for a while so it would be nice to see you update

best of luck on whatever you decide to do mate
 
  • Like
Reactions: haet

jjwatmyself

Senior Member
Feb 7, 2009
1,549
1,232
Well, I stumbled upon a MDL motherboard so did what any normal person would do and flashed a custom recovery. Ahhhhhhhhhh... such a relief to make it onto this side of the fence. And TWRP seems to like 64 GB SanDisk.

Interestingly, after installing this ROM and giving it some wifi, it wanted to update itself, but upon it it attempting to apply the /cache/cc80dccc7febf9b7685d56ac5c1094f3e9eaa023.SS-I9505GUEUCMKG-to-UCML4_Update_FWD.zip (4.4.2 I believe) it complains.

Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/jgedlteue/jgedlte:4.4/KRT16S.S005/131116:user/release-keys" ||
       file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/jgedlteue/jgedlte:4.4.2/KOT49H.S001/131204:user/release-keys");
assert(getprop("ro.product.device") == "jgedlte" ||
       getprop("ro.build.product") == "jgedlte");
ui_print("Verifying current system...");

Results in this:

Code:
assert failed: getprop("ro.product.device") = "jgedlte" || getprop("ro.build.product") = "jgedlte"

I had a quick look at /system/build.prop and it looks "ok"... :confused:

I have the zip if it's needed.
 

upndwn4par

Inactive Recognized Developer
Jan 22, 2012
3,640
10,375
New Jersey
Well, I stumbled upon a MDL motherboard so did what any normal person would do and flashed a custom recovery. Ahhhhhhhhhh... such a relief to make it onto this side of the fence. And TWRP seems to like 64 GB SanDisk.

Interestingly, after installing this ROM and giving it some wifi, it wanted to update itself, but upon it it attempting to apply the /cache/cc80dccc7febf9b7685d56ac5c1094f3e9eaa023.SS-I9505GUEUCMKG-to-UCML4_Update_FWD.zip (4.4.2 I believe) it complains.

Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/jgedlteue/jgedlte:4.4/KRT16S.S005/131116:user/release-keys" ||
       file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/jgedlteue/jgedlte:4.4.2/KOT49H.S001/131204:user/release-keys");
assert(getprop("ro.product.device") == "jgedlte" ||
       getprop("ro.build.product") == "jgedlte");
ui_print("Verifying current system...");

Results in this:

Code:
assert failed: getprop("ro.product.device") = "jgedlte" || getprop("ro.build.product") = "jgedlte"

I had a quick look at /system/build.prop and it looks "ok"... :confused:

I have the zip if it's needed.

Hey jj. You are the only person I am aware of that has made that jump without switching devices. Nice work.

And be happy the OTA failed (as it should have). You wouldn't want your SGH-I337 bootloader getting a GT-I9505G patch. :)

The update from 4.4 to 4.4.2 is incremental, so you're not missing much. I'll probably update the ROM when I find some time.
 

webbie2

Senior Member
Jul 17, 2012
201
24
Cleveland
Hey jj. You are the only person I am aware of that has made that jump without switching devices. Nice work.

And be happy the OTA failed (as it should have). You wouldn't want your SGH-I337 bootloader getting a GT-I9505G patch. :)

The update from 4.4 to 4.4.2 is incremental, so you're not missing much. I'll probably update the ROM when I find some time.

Thank you!. I am looking foward to your update. I'm trying to find a kit kat rom that is almost complete stock. 1 want pure google edition that is stable and great for a daily driver. I can't wait for the 4.4.2 build.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    |ROM| KitKat 4.4 ★|★ Let's Play v2.1 ★|★ S4 Google Play Edition | 1 Dec 2013 |

    letsplay_ss2.jpg


    Let's Play is a S4 Google Play Edition ROM I built for When I need a break from TouchWiz. It's nice and stable with a few extra tweaks, so I thought I'd share it with everyone.


    Features
    KitKat 4.4 GE Firmware (KRT16S) (odex)
    Stock insecure kernel
    cLock widget
    Xposed framework
    GravityBox
    Per App Settings
    New Google Launcher
    Notification Toogle app
    AdAway
    AOSP Browser
    Over 90 wallpapers
    MMS with Quick Reply
    Custom Settings:
    -On-the-Fly battery mod
    -Battery Bar
    -cLock widget


    Issues
    Do Not Use ART



    Credits and Thanks:
    attn1, C3C076, Chainfire, Didact74, dsixda, djrbliss, faux123, j4velin, ktoonsez, loserskater, pulser_g2, rovo89, sphinx02, xperiacle
    Samsung, CyanogenMod, AOKP, xda

    11
    Please do not use any part of this ROM without permission.

    Please do not PM me with ROM questions or for tech support.
    Post your question on one of my threads and I will do my best to help you.

    Download
    MD5: 56878d272b6782965760be0910abaff6
    Lets-Play_S4_GPE_v2.1


    Install
    Flash at your own risk!!!
    First install:
    Check MD5
    Nandroid backup
    Factory reset
    Flash ROM
    Reboot

    Update:
    Check MD5
    Nandroid backup
    Flash ROM
    Reboot

    This kernel is not loki-patched, so AT&T users must be sure to flash loki-doki.

    You may have issues using CWM based recoveries with this ROM. If so, try TWRP (it's what I use).



    Useful Tools
    MD5 check utility
    Wiping Tools
    Chainfire's SuperSU (flash this if you ever lose root)



    Extras


    *****
    7
    Changelog

    Code:
    v2.1
    Stock kernel (insecure)
    MMS with quick reply
    Alternate keymaster hack (no init.d script)
    Cleaned up some code & apps
    
    
    v2.0
    Initial release - Kit Kat 4.4
    
    
    v1.0
    Initial release - Jellybean 4.3


    About KitKat
    Ars Technica KitKat Review

    Getting to know KitKat

    ART: Part 1 Part 2

    More ART

    ART App Compatibility


    Search before you post, or else...

    search_or_hulk_smash.gif
    [/SIZE]
    6
    Who wants some KitKat?!

    v2.0
    KitKat 4.4 GE Firmware (KRT16S)
    ktoonsez kernel
    cLock widget
    Xposed framework
    GravityBox
    Per App Settings
    New Google Launcher
    Notification Toogle app
    AdAway
    AOSP Browser
    Over 90 wallpapers
    Custom Settings:
    -On-the-Fly battery mod
    -Battery Bar
    -cLock widget


    Issues:
    Do Not use ART


    Please be sure to head over to one of ktoonsez's thread and hit the thanks button. He fixed some pretty irritating issues with GE 4.4.

    Do not try to use ART yet (new Android runtime). GE 4.4 is still having some issues.

    About KitKat:
    Ars Technica KitKat Review

    Getting to know KitKat

    ART: Part 1 Part 2

    More ART

    ART App Compatibility
    3
    v2.1
    Stock kernel (insecure)
    MMS with quick reply
    Alternate keymaster hack (no init.d script)
    Cleaned up some code & apps

    Lets-Play_S4_GPE_KitKat_v2.1


    Do you guys really think this thread deserves 4 stars?

    If not, please consider a 5 star rating. :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone