Database Users

For those with an SCH-R970 from USC stuck on bootloop

I bought a prototype SGS4 SCH-R970 USCellular on ebay a couple weeks ago, flashed a rooted rom, messed up, nandroid wouldnt work, bricked phone :crying:
My phone had been stuck in the samsung logo when starting up the boot sequence, after weeks of reading and searching all the forums I could find, I was able to get it to work. Many phone shops and fellow android developers I know said it was bricked and to give up on it but here's how I got it out of brickmode
I found this epic thread: http://forum.xda-developers.com/showthread.php?t=2295557
First: I cleared the cache and dalvik as usual.
Second: I Flashed a stock cricket system and kernel "CricketME4_Unrooted_System-Kernel" google it.
Third: Flashed that loki zip found on the thread above.
Fourth: Cleared caches again and rebooted.
Edit: I was able to fix wifi loading CM http://get.cm/?device=jflteusc still working on which one has every single feature working, or at least as many as possible xD
Camera does not seem to focus at the moment, I think it might be due to the rom, which is meant to be used with SCH-R970C
Thats it! Took a couple mins to boot up completely but it got it out of brickmode, if anyone knows or has a stock metropcs rom let me know!
I'll check this thread every now and then so if you have questions be patient unless someone else answers, hope this helps anyone else out there :cyclops:

camera
did u fix camera focus?

reason for camera not focusing
reapbooster said:
I bought a prototype SGS4 SCH-R970 USCellular on ebay a couple weeks ago, flashed a rooted rom, messed up, nandroid wouldnt work, bricked phone :crying:
My phone had been stuck in the samsung logo when starting up the boot sequence, after weeks of reading and searching all the forums I could find, I was able to get it to work. Many phone shops and fellow android developers I know said it was bricked and to give up on it but here's how I got it out of brickmode
I found this epic thread: http://forum.xda-developers.com/showthread.php?t=2295557
First: I cleared the cache and dalvik as usual.
Second: I Flashed a stock cricket system and kernel "CricketME4_Unrooted_System-Kernel" google it.
Third: Flashed that loki zip found on the thread above.
Fourth: Cleared caches again and rebooted.
Edit: I was able to fix wifi loading CM http://get.cm/?device=jflteusc still working on which one has every single feature working, or at least as many as possible xD
Camera does not seem to focus at the moment, I think it might be due to the rom, which is meant to be used with SCH-R970C
Thats it! Took a couple mins to boot up completely but it got it out of brickmode, if anyone knows or has a stock metropcs rom let me know!
I'll check this thread every now and then so if you have questions be patient unless someone else answers, hope this helps anyone else out there :cyclops:
Click to expand...
Click to collapse
Hi all I also have this box. Earlier when it is stock 4.2.1 i5s camera was working fine. But when I flash cm11 on it its camera firmware is updated and after that momemt camera is not focusing so. Now camera only work either we have to downgrade the camera firmware to match with phone firmware or somehow have to update the phone firmware.
So
Camera firmware should be <= phone firmware
But our camera firmware is greater that phone firmware
See the attachment

finally after 2 months of research i fixed my camera issue.....if anyone still wants,,tell me...i will upload the solution(nandroid)

reapbooster said:
I bought a prototype SGS4 SCH-R970 USCellular on ebay a couple weeks ago, flashed a rooted rom, messed up, nandroid wouldnt work, bricked phone :crying:
My phone had been stuck in the samsung logo when starting up the boot sequence, after weeks of reading and searching all the forums I could find, I was able to get it to work. Many phone shops and fellow android developers I know said it was bricked and to give up on it but here's how I got it out of brickmode
I found this epic thread: http://forum.xda-developers.com/showthread.php?t=2295557
First: I cleared the cache and dalvik as usual.
Second: I Flashed a stock cricket system and kernel "CricketME4_Unrooted_System-Kernel" google it.
Third: Flashed that loki zip found on the thread above.
Fourth: Cleared caches again and rebooted.
Edit: I was able to fix wifi loading CM http://get.cm/?device=jflteusc still working on which one has every single feature working, or at least as many as possible xD
Camera does not seem to focus at the moment, I think it might be due to the rom, which is meant to be used with SCH-R970C
Thats it! Took a couple mins to boot up completely but it got it out of brickmode, if anyone knows or has a stock metropcs rom let me know!
I'll check this thread every now and then so if you have questions be patient unless someone else answers, hope this helps anyone else out there :cyclops:
Click to expand...
Click to collapse
Which one of the Loki zips did you flash my friend? Thanks a TON for this! EXACT same issue!!!

mayur9890 said:
finally after 2 months of research i fixed my camera issue.....if anyone still wants,,tell me...i will upload the solution(nandroid)
Click to expand...
Click to collapse
I have a prototype of r970,too!
I flashed it with chinese i9505 firmware and it updated my camera firmware. The camera does not focus now.
please help me fix the camera! thanks a lot!
p.s. I can not flash any bootloader and modem in this prototype. Anybody knows is it locked?
p.s.s Is anyone know how to use gsm on this phone? (normal r970 works. prototype can not work may because of the lock of modem?)

Back up
mayur9890 said:
finally after 2 months of research i fixed my camera issue.....if anyone still wants,,tell me...i will upload the solution(nandroid)
Click to expand...
Click to collapse
Friend i suck up with the same camera issue after updating to CM rom,
please could you give your nandroid backup, so that it will be more helpfull for me.
Thanks in Advance

JAIKRISH said:
Friend i suck up with the same camera issue after updating to CM rom,
please could you give your nandroid backup, so that it will be more helpfull for me.
Thanks in Advance
Click to expand...
Click to collapse
hi friends. plz help me. i hve same camera problem now.its not auto focus now. i tryed to install firmware not working bro.. plz what can i do>?
---------- Post added at 11:56 AM ---------- Previous post was at 11:53 AM ----------
sharp(o_-)EyE said:
did u fix camera focus?
Click to expand...
Click to collapse
hye. sir plz help me. i hve same auto focus problm. how can i fix ths??

[Q] Blame Tyler. HELP!

I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.

Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Same.

Same.
:crying:

Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.

ernieb4768 said:
Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.
Click to expand...
Click to collapse
This doesn't work for me... anyone got a solution? That's annoying..

Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Did you try a clean install?
-wipe data/factory reset
-flash ROM
-flash gapps
-restart
no "restore"
If you say you had an "Older" version, does this mean you were on PAC23 (with android version 4.2.2)?
If you are on a pre-android 4.3 version of PAC, you need to do a full wipe. If you are already on a 4.3 version of PAC and you have "blame tyler" issues, try factory reset, if the problem persists, try a different nightly

Just a little curious...is the Blame Tyler error a specific error or set of errors, or does Tyler get blamed for everything?
Also, can we get Tyler's xda username, so he can get the blame he deserves :laugh:

Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
try redownloading the rom zip! and check its md5 code before flashing!!
also do a clean flash! all wipes!
if it doesnt work then even try fix permissions option !
Sent from my C6603 using Tapatalk 4

'Blame Tyler' error is just a generic message displayed when some component crashes/throws an unhandled exception, etc. It's not related to a bad ROM d/l or MD5 code. Telling people to do a full wipe b/c of an undiagnosed error condition doesn't help much. There are far too many little brokens with this ROM that need to be addressed and given more developer support, if this ROM is get more adoption.
Since RC1, nightlies have been dropping for 2 months now - no log of what's fixed or added, unless you are a dev who can wade thru the build change logs and understand what that means. It's ridiculous that we've gone this long since RC1 with a new stable release and documented fixes. Maybe this info is buried somewhere, but it's not in the Spring GS4 forum and the Pac-Man website forum is dead.
These errors are not specific to any one nightly and have been going on for months.

the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...

I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app

experienced the same problem and would be greatful for help

vedhed21 said:
I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yes, if you have the T-Mobile variant of the S4.

keyboard not working.....
Papa Smurf151 said:
the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...
Click to expand...
Click to collapse
i have flashed your pac man rom to my galaxy sl everything went right but its keyborad was not working then i manually flashed another JB keyboard in recovery mode... then it worked ... and i flashed blackgapps(JB 4.2.2) from ENHDROIX developers and it is working quite well...
the only problem i had was keyboard stuff..
so devs should fix that issue...

GUYS THIS IS VERY STRANGE.. The nav bar at the bottom overlaps half of the dock of next launcher which makes the dock completely unusable and ugly.. the same problem persist in 50% of the other apps notably go sms, quick pic, go launchers and many others.. I have tried the milestone releases and a few latest nightlies but its still not fixed..
Its hard to believe there are many discussions of issues about pac rom going on but I didn't find this preety obvious and significant one anywhere..
I have waited like 3 months since I started with pac, updated about 5 nightlies along the way hoping it will be fixed but no luck everytime..
This one is serious.. It has forced me not to use some of my fav apps and use pie navigation at times..
No problem with all the minor bugs but this one is frustrating..
ANY IDEA GUYS??
PS. pac ver 4.3.1 on sg tab p3100 and sg3
Sent from my GT-P3100 using XDA Premium 4 mobile app

Do you know how to enable navigation bar? I saw all the settings in PAC settings>navigation bar but found no option to enable it.
Sent from my GT-P3100 using XDA Premium 4 mobile app

[ROM] CM11 for Otter

Not my work, but I found this when looking for rastakat for my manta.
http://fitsnugly.euroskank.com/?rom=cm11&device=otter
TWRP WILL NOT WORK, AS IT FAILS WHEN FLASHING KITKAT BASED ROMS. TRY COTR INSTEAD, BUT THAT IS STILL NOT GUARANTEED.
The only recovery that worked on manta was CWM, but that's out for the otter obviously...
I would also assume to use Paranoid Android's odexed Gapps(so ART compiler works, and doesn't FC Gapps all the time)
Gapps: http://www.mediafire.com/folder/gxxxpkbcke4yi/PA_GApps_-_Official_Releases
And finally, CM11 might be pre-rooted, but if it isn't here's SuperSU
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Can anyone confirm if it works? I haven't had time to flash yet.

Trying now
---------- Post added at 01:29 AM ---------- Previous post was at 01:04 AM ----------
It won't install with COTR or TWRP. So close ...

Actually, it is saying it is for Blaze devices and not Otter, but it says otter in the build.prop and it looks like a 1st gen to me.

dskrilz said:
Trying now
---------- Post added at 01:29 AM ---------- Previous post was at 01:04 AM ----------
It won't install with COTR or TWRP. So close ...
Click to expand...
Click to collapse
Okay, that's what I feared. Either TWRP or COTR have to be updated before they can flash KitKat ROMS. I am not sure why, but until that happens we can only look on and wait...

Cyan 4.4
Delete

incubus26jc said:
Here you go. I zipped up all 3 files you will need
Do Not flash my zip.
extract the 3 zips out to sd first and then flash.
flash twrp 2.6.3.1 first
Reboot recovery
then rom
then gapps.
no wifi.. Very fast
https://www.dropbox.com/s/sjfg4th2k5izqxb/Cyan-11-Unofficial-otter-11-11-13+gapps+twrp.zip
Click to expand...
Click to collapse
Awesome, thanks. Did you mess with the flashing/installer script? Let's try to get this thread moved to the dev section. Someone might be able to figure out the wifi issue and it might be a good base for others who might be working on a KitKat rom.

dskrilz said:
Awesome, thanks. Did you mess with the flashing/installer script? Let's try to get this thread moved to the dev section. Someone might be able to figure out the wifi issue and it might be a good base for others who might be working on a KitKat rom.
Click to expand...
Click to collapse
Yes i removed the blaze references on the updater script. Flashes and boots fine.

Just installed it. Wifi Doesn't work for now and its some graphical glitches but It hasn't been posted yet so its acceptable.

Just downloaded cm11 for otter from loosethisskin on goo.im. Only been playing with it for an hour. Wifi does work but it does have some graphic hiccups. Seems much faster than 4.3
Sent from my Amazon Kindle Fire using XDA Premium HD app

The ROM over at fitsnugly.euroskank. [com] /?rom=cm11&device=otter has been updated to cm-11-20131117.1708-otter and it is very nice. Just make sure to update latest Recovery version or it won't flash.

Was loving the 20131116 build, wifi worked and everything seemed stable enough to run my apps after I got it all setup. Unfortunately, after updating to the 20131117 build, wifi no longer works (dirty flashed for the 1117 update). And reverting back I still have no wifi. The off/on is disabled. Maybe I will try a factory reset and reinstall...
___
Update: I did a Factory Reset and then flashed both versions, still no wifi. It is still disabled/greyed out. After several attempts I realized I wiped everything but system and sd... *sigh*
Wiped system, all is good...

Anyone know how to get those nifty transparent bars with our build?

[Q] KitKat Rom on T Mobile Lg G2

I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?

Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app

Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?

JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app

Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.

JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app

v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about

batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.

Did anyone out there figure this out?

I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.

I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?

I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...

I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.

Anyone around in this thread with the line problem willing to test a kernel?

mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?

sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.

v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone

frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.

mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!

mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.

Cyanogenmod is officially supporting us!

Finally! Cyanogenmod is officially supporting Kltespr! http://download.cyanogenmod.org/?device=kltespr (sorry if i'm late)

Yup You wanna know what else that means? CUSTOM ROMS

I just read an article online about this a few hours ago, it is about time lol I did stumble onto a youtube video with what looked like a ported CM for the S5, but the user noted some serious bugs. I'm psyched we now have official support for the ROM!

However if you try to flash it gives the error of this is for kltespr. You have klte installation aborted. See website.https://download.cyanogenmod.org/?device=kltespr
I contacted cyangenmod and was told to update recovery. I am using Philz cwm
In another post I came across said t try this recovery. Haven't tried yet though as at work

kmcphee said:
However if you try to flash it gives the error of this is for kltespr. You have klte installation aborted. See website.https://download.cyanogenmod.org/?device=kltespr
I contacted cyangenmod and was told to update recovery. I am using Philz cwm
In another post I came across said t try this recovery. Haven't tried yet though as at work
Click to expand...
Click to collapse
downloading now I will try it with newest philz recovery..I'll let you know if it works.

How do you properly flash this new recovery? I tried just using recovery to install it from the zip but this TWRP wont even let me install any ROMs. Not sure what I'm doing wrong here.

euklid said:
downloading now I will try it with newest philz recovery..I'll let you know if it works.
Click to expand...
Click to collapse
Any luck? About to try myself.

euklid said:
downloading now I will try it with newest philz recovery..I'll let you know if it works.
Click to expand...
Click to collapse
Any luck?

IT WORKS!
The recovery link in one of the comments above (KT ALL IN ONE) worked. It includes a kernel too, but I've spent so much time trying to fix this that I don't even care. I tested it by downloading a kltespr build directly from CyanogenMod and it flashed just fine. No error. Finally...
Sent from my SM-G900P using XDA Free mobile app

abstraction21 said:
Any luck? About to try myself.
Click to expand...
Click to collapse
yeah only the recovery posted above works..neither TWRP or philz (newest ones) work.

In Google play store do you have an option to pay with your Verizon account? I'm on sprint

Thanks for the custom recovery. I'm able to install nightlies now

I can no gps the e gps to work. I have been trying since the first release

AOD_Corwin said:
I can no gps the e gps to work. I have been trying since the first release
Click to expand...
Click to collapse
Is your location on in settings?? Mine is working fine on latest nightly.

Yeap. Also tried turning it off, then back on, restoring efs, flipping it to airplane mode then back and changing my apn then back. Also tried with different kernel .

AOD_Corwin said:
I can no gps the e gps to work. I have been trying since the first release
Click to expand...
Click to collapse
Bummer, this is always an issue with CM builds. I was hoping this time would be different.
A common fix for GPS CM builds On HTC phones was a way to Reset the GPS using ##GPSCLRX# code in the phone pad which requires you use the Native OS to get codes working.

I need my msl for this

AOD_Corwin said:
I need my msl for this
Click to expand...
Click to collapse
Ask sprint for it or download an app that requires root to get it.
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
So how is this running for folks?
Does anyone know if you can tether with it?
Does LTE work Ok?
Can you revert back to Samsung based ROM without issue?

Official CM Thread if anyone was curious.
http://forum.cyanogenmod.org/forum/1118-samsung-galaxy-s5-sprint-kltespr/
Read through the threads and you will see which files need to be edited if you are having issues flashing this

This ROMs been working great for me. The only reoccurring problem I've had so far is random camera errors with google camera, but usually closing/reopening fixes it. LTE to 3g and back is no prob. MMS works. IR works with some apps but not all. GPS wasn't working for the first few builds but around 9/24 I got it working. Don't know if it was the ROM or me. Had to hold quick tile, disable Google location reporting then enable it again. I've been dirty flashing I guess? Wipe cache and dalvik then flash new ROM with gapps. The whole script edit thing is unnecessary if you're using the KT modded twrp. And if you would rather edit the script, do it in winrar on a windows machine and you wont have any problems. Snapshot of battery life after a typical workday. Theme I'm using is MustardSeed by Thyrus, on the play store