Database Users

[Q] Wifi broken, can't seem to fix it

Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?

nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
Basically yesterday I had the same problem, flash after flash didn't help. Can tell you exactly, what I did:
Found factory version of my firmware in my region (SEB Baltics for me, MGA). Then I reinstalled TWRP recovery through ODIN, wiped everything I could, after that flashed stock firmware 2 times consecutively (no reboot in odin, reboot manually after first flash and flash again).
After that everything went fine, and Wi-Fi started working again. MH1 custom ROM right now, going ok.

Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?

No. WiFi drivers are in the kernel, not the modem. If you were going to flash anything, you'd flash a kernel/rom.

nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
I suggest you use titanium backup to bakup your apps, it's not a tough job as you thought. that might be the easiest way, although some data can't be backup.

nwsk said:
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
Click to expand...
Click to collapse
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.

Gh0stR1pp3r said:
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Click to expand...
Click to collapse
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar

bofff said:
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
Click to expand...
Click to collapse
Welp, bluetooth had no problems whatsoever. It was only the wifi, which didn't want to turn on. Now everything is ok.

Well, finally got around to reflashing stock as Gh0stR1pp3r suggested, which worked. Thanks
Nandroid, kernel flashing, and modem flashing all didn't work. No clue why. I flashed the ausdim kernel again and it worked this time around, so it's just weird I guess? :S
And unfortunately I seem to have messed up the titanium backup somehow, I can't seem to find any of the stuff I thought I backed up Oh well

MDOB rom messed up S4 (full wipe doesn't wipe everything?)

System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin

Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?

hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.

I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk

Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine

[Q] Help me pls, no phone signal

Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?

foxguard said:
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
Click to expand...
Click to collapse
Sounds like a radio issue. If you are running 3.99, you need the radio for 4.3 which I do believe 3.99 is based on. You need the radio for KitKat when running the new betas.
Sent with my Nexus® 10 minus 3

This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.

I think I basically said that. Sometimes I believe in not holding hands and let the guy/gal do some of the, legwork.
Sent with my Nexus® 10 minus 3

Thank you every one. I have reverted back to my recovery and all is well but I don't understand why when I flash the ROM ad gapps it happens. My recovery is the same ROM and gapps. No idea.
Oh well stuck with the screen delay for now!
Sent from my Nexus 4 using Tapatalk

mrhiab said:
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
Click to expand...
Click to collapse
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.

foxguard said:
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
Click to expand...
Click to collapse
Ohh you are having issues with ur network !! Seen people completely losing their Imei during flashing !! Not to scare you but its better to get the imei files backed up !!
Check my post on the below mentioned link
http://forum.xda-developers.com/showpost.php?p=49753344&postcount=11
Hit the thanks button if you find my post useful

[Q] [AOSP] Broken telephone feature

Guys, everytime I flashed an AOSP based Rom like Carbon on my hltexx, nobody can call me and I also can't call someone else. If I dial a number, the connection seems to break instantly but my mom told me, she got my calls but didn't hear anything. I'm also unable to change or view the access points.
Stock based Roms like Omega work correctly.
WTF am I doing wrong? :crying:
Additional Infos:
>SMS and Internet work.
>3G because my provider (Drei, Austria) is retarded.
>Android 4.4.2
>restoring an old EFS backup didn't solve the problem
>APN seems to be correct

Have you tried a custom kernel like temaseks kernel?
Sent from my SM-N9005 beast of a phone.

Sammath said:
Have you tried a custom kernel like temaseks kernel?
Click to expand...
Click to collapse
Not yet. I'll flash CM now and try a few kernels and will post the results later.
Btw here is one with the same problem.

I tried some kernels for hltexx, but everything I got was bootloops or a starting system with the same problem ;_;

Have you ever Flashed a newer rom(Sammy official) or updated your modem firmware?
Sent from my SM-N9005 beast of a phone.

Sammath said:
Have you ever Flashed a newer rom(Sammy official) or updated your modem firmware?
Sent from my SM-N9005 beast of a phone.
Click to expand...
Click to collapse
Yes, I updated from 4.3 to 4.4.2 via odin and used the stock images for my provider. Everything worked as it should, only aosp roms had problems.
A few days ago I installed PAC again after flashing the newest stock .tar.md5 and tried the whole evening many different configurations in apn and other connection related settings. Nothing worked and i restored them all. On the next day I got a call. I couldn't explain it, but i was able to start phone calls too. With just one problem: When I call someone I lose the control over the whole Touchscreen and the buttons, so the only way to end a conversation is a hard reset via holding the power button.
I'm not sure, but I have the theory that the RIL file isn't compatible to the modem. Where can I find some RILs?
Another strange fact is, that everytime I flashed an AOSP, i formated the device via TWRP to erase all the bloatware and then made a full wipe. But last week I forgot to format the storage. Guys, was I really everytime this stupid and simply wiped the RIL partition away?

Model number?
Firmware you have upgraded to (4.4.2)?
Tried changing recovery, Wipe System, wipe cache, data, then flash the ROM fresh. boot into it, head to Settings > about and check if you have lost Baseband and/or Serial Number/IMEI - then we'll figure it out for you

radicalisto said:
Model number?
Firmware you have upgraded to (4.4.2)?
Tried changing recovery, Wipe System, wipe cache, data, then flash the ROM fresh. boot into it, head to Settings > about and check if you have lost Baseband and/or Serial Number/IMEI - then we'll figure it out for you
Click to expand...
Click to collapse
Sorry for answering so late. Changing every password after heartbleed took much time.
My model number is SM-9005
Even with a CWM based recovery and after a wipe with a complete reinstall I get the same problem.
IMEI and Baseband (N9005XXUENB1) are still here.

[Q] [solved] GPS Not Working After Cyanogen Mod Install

Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.

MikeDacre said:
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
Click to expand...
Click to collapse
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!

MikeDacre said:
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
Click to expand...
Click to collapse
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the confirmation. I did exactly that and I can confirm that it did indeed work.
Thanks so much for the help.

Hi all,
Sorry to resurrect an old thread, but I am having this issue and the stock firmware flash isn't solving the issue. It is all very odd because it doesn't actually retain any kind of lock after flashing. I'm following instruction on here, but after locking gps on stock, then going to CM I cannot get a fix. It either had a massive radius on Maps, or it just locks to my home or work location.
Since trying much more I have managed to get the occasional satellite lock via GPS Locker, but even then as soon as I move from either my house or work, it can't find anything to lock onto and just defaults to a static location.
Is there anything you would recommend? I have 2 Samsung GS4's and they both exhibit the same problem. I have also tried this on an S4 Mini, but that retained lock just fine. I'm really confused as to what to actually try. If you could recommend anything I'd be very grateful.
Again, I'm sorry to res an old thread, but no one has been replying to the one I started for this issue :/

Your problem may be that there is some new issue with the newer firmware. I had success by first flashing the *old* firmware (you can download it from my dropbox here: https://www.dropbox.com/s/o3f3ynyezyy4yw9/L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5?dl=0) and then upgrading to the second to last firmware update for the GS4: which gives you Android 5 but without fixing the MMS bug.
After that I flash TWRP with Odin, and then do a full erase in TWRP followed by flashing the latest CM. That series of steps works for me every time, although I found that large changes to my physical location (e.g. flying to England from California) cause it to break again. I actually had to sit in a cafe in an English airport with my laptop out flashing my phone back to stock just so that I could use Google maps to get to my mother's house. It was pretty ridiculous. Because of that and other issues, I now just use stock. I hate it, but I do it anyway. Good luck.