I have developed an issue where a (seemingly random amount of time, can be over 24 hours, can be less than 12) after I boot my phone, I loose my mobile connection and GPS. I still have my WiFi. I have no way of knowing that this has happened until I look at the phone. This has been going on for a couple months now and is driving me insane. I have tried everything I can think of to fix it and I have posted in the Sprint specific Galaxy S4 forum, but I have yet to find an answer. I am hoping that posting to a wider audience may find some cure for my problem. I will post some very specific details about my phone, but any suggestions are welcome, even if the specifics are not familiar to you.
I have a Sprint Samsung Galaxy S4 (non-Spark, SPH-L720), rooted stock TouchWiz rom, Android 4.4.2 NAE (with MF9 bootloader, so no Knox), KT-SGS4 7/12/14 kernel, Philz Touch 6.48.4 recovery, SuperSU v2.01.
The following are frozen or deleted on my system (not listing items I consider irrelevant):
AllShare
CloudAgent
ELM Agent
Face Unlock
Knox (everything related)
Samsung Hub Updater
Samsung Link
Samsung Push Service
Security Policy Update
Sprint ID
Sprint Installer
Sprint Worldwide
TalkBack
My problem started after upgrading from system MF9 to NAE. For a while, NAE was the most stable operating system I had ever had on a phone. Then at an unknown point in time after upgrading, I began loosing my mobile connection and GPS a while after booting the phone. If I reboot the phone, I will immediately get the mobile connection and GPS back, until I loose it again and I always do.
I will point out that I recently discovered the app No Signal Alert and installed it, thinking that at least I would know when I loose my mobile connection. However, No Signal Alert does not detect a loss of signal when I loose my mobile connection, and still shows a good signal strength... this certainly confuses me.
Because system NAE was working perfectly for a while, I tend to think the problem does not specifically lie with the upgrade, something had to have changed in my phone to have caused the issue, as I see it.
I had messed with the APNs on my phone in an attempt to get MMS working, and in the process, through a misunderstanding of the app APN Backup & Restore, I had ended up with a massive APN file. I got this fixed, but it did not correct the issue. Also did a ##72786# reset. All during this time, I was also unable to update my PRL or Profile, as I would get an error. Eventually, for some reason, I got my PRL and Profile updated, but that did not fix my issue. I even Nandroided back to before I had messed with the APNs, still no luck.
Based on things I read, or on my on intuition, I tried going back to a prior kernel version, no help. I removed the ViPER4Android sound mod, no help. I use XPrivacy, but I monitor the restrictions closely and nothing is occurring there that should cause an issue. I seem to have battery overcharging issues with my phone and I have read a post by one user relating battery issues to connection issues, but since restarting my phone solves the issue, I don't see this being related.
I have attached a LogCat recording using CatLog (set to Warn or higher) of an attempt to place a call while my mobile connection was lost... I am personally unable to tell if this shows anything useful or not.
What is so frustrating to me about this is WHY does the mobile connection and GPS work perfectly fine for a while after booting, then stop? Obviously, something is occurring and I don't know how to find out what it is...
So... ANY ideas, wild conjectures or knowledgeable help would be GREATLY appreciated! :fingers-crossed:
Let me define a little better what I mean when I say that I loose my mobile connection and GPS...
When this happens, I can receive no phone calls. I can make no phone calls. I can receive no text messages. I can send no text messages. I have no 3G or 4G internet connection. I am also unable to connect to GPS. I can still connect to the internet through WiFi perfectly fine. Basically, when this occurs, I no longer have a phone, I have a WiFi enabled internet device .
Something I question is how is the mobile connection related to the GPS in a way that it is NOT related to the WiFi? Why should I loose my GPS if I loose my mobile connection? And why don't I loose my WiFi then? Is this a modem issue?
Why does No Signal Alert not detect that I have no mobile connection and continue to report a good signal strength? Is it incorrect, or am I still getting the signal but my phone otherwise thinks for some reason that I am not... when this occurs, the signal level in the notification bar shows no bars and an 'x'.
Why does rebooting the phone regain the mobile connection and GPS? Why do I always eventually loose it again? It OBVIOUSLY WORKS, why does it STOP working? Something must cause this to happen but figuring out what that is has been beyond my capabilities (it may well be in the logcat, but I just can't understand it well enough, despite the headaches I have gotten trying to).
I have never heard of anyone else with an issue similar to mine (I seem to specialize in these sorts of issues). The above are the sort of questions that I hope can lead to an answer for me, I need a phone again! :fingers-crossed:
(ADDITION): Here is a bit of another logcat I ran today when my mobile connection and GPS was lost. The first thing listed is an Adreno-ES20 error and I was getting a TON of those for some reason, though I think from my research that is related to the GPU, so should not be related to this issue?
The next section listed is something I wonder about, since it references 'call' a couple times. This section of error was repeated several times in the logcat. Does this indicate a issue being caused by the XposedBridge (I do have Xposed installed). I tried to research the "asks to run as user -2 but is calling from user 0" part of the message and from what I can tell, that is prone to happen on Samsung phones and that error should not cause an app to stop working (though my understanding could OF COURSE be totally incorrect).
Code:
08-24 11:36:00.577 E/Adreno-ES20( 1432): <process_gl_state_enables:519>: Invalid enum – 0xde1
08-24 11:36:10.307 W/ActivityManager( 877): Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
08-24 11:36:10.317 E/DatabaseUtils( 877): Writing exception to parcel
08-24 11:36:10.317 E/DatabaseUtils( 877): java.lang.SecurityException: Permission Denial: get/set setting for user asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
08-24 11:36:10.317 E/DatabaseUtils( 877): at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:14620)
08-24 11:36:10.317 E/DatabaseUtils( 877): at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:2258)
08-24 11:36:10.317 E/DatabaseUtils( 877): at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:663)
08-24 11:36:10.317 E/DatabaseUtils( 877): at android.content.ContentProvider$Transport.call(ContentProvider.java:325)
08-24 11:36:10.317 E/DatabaseUtils( 877): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:275)
08-24 11:36:10.317 E/DatabaseUtils( 877): at android.os.Binder.execTransact(Binder.java:404)
08-24 11:36:10.317 E/DatabaseUtils( 877): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
08-24 11:36:10.317 E/DatabaseUtils( 877): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
08-24 11:36:10.317 E/DatabaseUtils( 877): at android.os.Binder.execTransact(Native Method)
08-24 11:36:10.317 E/DatabaseUtils( 877): at dalvik.system.NativeStart.run(Native Method)
08-24 11:36:10.317 W/qdhwcomposer( 298): Excessive delay reading vsync: took 681 ms
This is the forum for your device:
http://forum.xda-developers.com/galaxy-s4-sprint
What I would do in your case:
Start from scratch. Just do a full wipe from the recovery and flash a new rom. You modded so much that's it's best to start over.
From my experience it's hard to find the cause when you did a lot of modding. Starting from scratch would be the fastest route.
You can either flash a custom rom or again the stock rom. That's up to you.
Thanks for the response!
Lennyz1988 said:
This is the forum for your device:
http://forum.xda-developers.com/galaxy-s4-sprint
What I would do in your case:
Start from scratch. Just do a full wipe from the recovery and flash a new rom. You modded so much that's it's best to start over.
From my experience it's hard to find the cause when you did a lot of modding. Starting from scratch would be the fastest route.
You can either flash a custom rom or again the stock rom. That's up to you.
Click to expand...
Click to collapse
An answer from an actual living human being... you don't know HOW MUCH I appreciate it! :highfive:
I already tried the Sprint Galaxy S4 forum, as I said, and did not get anywhere. My IMPRESSION is that THIS is the GENERAL Galaxy S4 forum, PLEASE correct me if I am wrong about that, I find the phone specific forum structure somewhat confusing. I had planned to jump straight to the General Android Q&A and Troubleshooting Forum, but decided it was better to try here first... maybe that was incorrect?
You make a VALID point about starting from scratch, I will certainly admit, but comparatively, I don't believe my phone is THAT modded, it is relatively stock compared to what a lot of users do with their phone here. There are many things I could try and haven't, such as trying a pre-NAE modem, but since the NAE modem WAS working, my expectations are that that would not help. While not starting from scratch, I have regressed CONSIDERABLY I feel, by Nandroiding back to the point before I believe I had the issue (although admittedly, I then reinstalled pretty much everything, possibly including whatever is causing my issue). I can Nandroid back to MF9, which I have NOT done, and see if the problem still exists, which would certainly seem worthwhile and something I SHOULD do.
One thing I will mention is that I haven't is that this thread Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc makes me fear (very possibly incorrectly) that my issue may be caused by my MDN, MIN, Profile 0 and Profile 1 being incorrect (thinking I corrupted them while messing with the APNs), but the ability to fix them as described in the thread is a bit beyond my capability AND if this was the issue, again, I don't think the mobile connection should be working at all, not just stop working after a while.
Also, just for the sake clarity I should mention this: when my phone looses the mobile connection, if I try to make a phone call, it just dials and will not stop dialing (though not actual 'dialing' can be heard). Attempting to end the call accomplishes nothing. If I force close the Phone app, the notification bar turns green. I just tried the app Disable Service today while my mobile connection was lost. I disabled any service I found running that I thought MIGHT end the Phone running (green notification bar and unable to end call). Numerous service that I ended would not end. Nothing I ended ended the Phone running and I ended up rebooting and re-enabling everything (except for com.sec.enterprise.mdm.services.vpn.knoxvpn.KnoxVpnEngine, which was running under Enterprise VPN Service, while com.sec.enterprise.mdm.services.vpn.old.EnterpriseVpnAnyconnect was NOT running... I believed I had deleted ALL Knox files from my phone, but I am unable to find where the 'KnoxVpnEngine' is located, both of these appear to be in the same Lib file to my limited understanding, in data/data/com.sec.enterprise.mdm.services.vpn/lib, which is a symbolic link to data/app-lib. If they are BOTH in this same lib file, then I do not know how to remove the Knox portion... and I may sometimes sound like I know more than I do I should point out, I just try my best.)
I WOULD greatly appreciate if ANYONE would let me know if I am correct in my belief that this is the GENERAL Galaxy S4 forum, or I am incorrect about this.
Lennyz1988, I have recently been becoming very disillusioned here, I spend a great deal of time here answering other users questions, but seem to have great difficulty getting anyone to answer the rare questions that I have. Just finally receiving A RESPONSE to this thread has made my day and I GREATLY appreciate your input! :highfive: :good:
As much as I want to help you. My knowledge of the Sprint version of the S4 is limited. It's a completely different phone.
The reason why I suggest to start from scratch is because this is a strange problem. If you continue to work on a non standard android version, then chances are solutions will not not work properly or not work at all. Because it's possible that some frozen or deleted app (of deleted file) is causing this. A factory reset will not help then because it will only wipe /data and not /system.
What if you make a nandroid backup of your current setup and then just start from scratch. That way we can try to solve it from a fresh start and you can always revert.
You have to guide me a little because i'm not that familiar with the Sprint. From what I understand is that you are running the NAE version on the old bootloader (correct me if i'm wrong).
Is it possible that you do a complete wipe from the custom recovery (the option prepare for a new rom) and flash a clean custom 4.4.2 TW based rom? The reason why I would suggest using a custom rom is because all the Knox apps will already be deleted already. Then after you have flashed the rom, don't install any apps that could interfere and don't delete/freeze any app. You can of course install apps like Facebook/Whatsapp, but don't use any Xposed modules etc.
I don't know how it is on the Sprint version, but on our version, if you are on the old bootloader, then you need to have a specific modem to work with the 4.4.2 rom. Make sure you got the proper modem on your device.
Thanks!
Lennyz1988 said:
As much as I want to help you. My knowledge of the Sprint version of the S4 is limited. It's a completely different phone.
Click to expand...
Click to collapse
First of all, I seriously cannot express how grateful I am to you for your ATTEMPT to help me! I completely understand your knowledge of the Sprint version of my phone is limited, but you have already provided me MUCH more assistance than anyone in the Sprint specific forum. While I would love for someone to to tell me do "x" and then "y" and your phone will be fixed, when I came to THIS forum, I was only really hoping for general ideas that would help me think about my issue and you have certainly provided them! :highfive:
(IMPORTANT NOTE): When I 'dispute or disagree' with what you say in the following, I AM NOT SAYING YOU ARE INCORRECT IN ANY WAY, I am just expressing my PERSONAL current understanding of my situation, which I feel helps me to think these things through and might or might not make things clearer for you. I will also provide MUCH MORE information than I'm expecting YOU to think about or respond to, I'm really just recording it, which also assists ME thinking about it.
The reason why I suggest to start from scratch is because this is a strange problem. If you continue to work on a non standard android version, then chances are solutions will not not work properly or not work at all. Because it's possible that some frozen or deleted app (of deleted file) is causing this. A factory reset will not help then because it will only wipe /data and not /system.
Click to expand...
Click to collapse
You are very much correct about it being a strange problem! What I find MOST STRANGE about is that it occurs at some point, usually at least about 12 hours after booting my phone. IF I never had a mobile connection and GPS, it would MUCH less strange. I recently helped another Sprint user who had installed a non-Sprint specific Google ROM (a mistake in the first place, no doubt) ►►[AOSP] Official 4.4.4 - S4 Google Edition - Stable-R2 - Feel the Experience of Nexus◄◄ which worked fine, but he had NO mobile connection. ROMs are CERTAINLY not my area of expertise, having only ever been stock-rooted, but I took it upon myself to assist this user because he was new and the KT-SGS4 kernel he was using with this ROM, I noticed, appeared to me to be the KitKat version, and I believed from the ROM that it should be the AOSP version. Had him flash the AOSP version of the kernel, which resulted in bootloops. Then I discovered that there are Google versions of the KT-SGS4 4.4.4 kernel for other carriers, but not for Sprint, which is the kernel he had in the first place, which comes with the ROM. Apparently, it all works fine on the Sprint phone, but unsurprisingly to me, you get no Sprint mobile connection. I was able to find a similar Sprint specific ROM, which he flashed and it completely solved his issues. But I digress...
What if you make a nandroid backup of your current setup and then just start from scratch. That way we can try to solve it from a fresh start and you can always revert.
You have to guide me a little because i'm not that familiar with the Sprint. From what I understand is that you are running the NAE version on the old bootloader (correct me if i'm wrong).
Click to expand...
Click to collapse
Yes, I am running NAE with MF9 bootloader. This is because I started on MF9 without Knox. If I upgraded to the NAE bootloader, I would never be able to go back to MF9, because of Knox. Numerous people have told me Knox does not matter because I am out of warranty anyway, however I PREFER to have the option to go back to MF9 if I should need to, which is why I upgraded in this way. I followed an established upgrade path to achieve this and have seen nobody else who has has used that upgrade method develop this issue.
Is it possible that you do a complete wipe from the custom recovery (the option prepare for a new rom) and flash a clean custom 4.4.2 TW based rom? The reason why I would suggest using a custom rom is because all the Knox apps will already be deleted already. Then after you have flashed the rom, don't install any apps that could interfere and don't delete/freeze any app. You can of course install apps like Facebook/Whatsapp, but don't use any Xposed modules etc.
Click to expand...
Click to collapse
I think this is probably the best suggestion I have received so far. I have NEVER not used a stock rooted ROM, because my main desire is stability and that is where I have believed I would find it. However, I think it is time for me to investigate a custom ROM, at least try one, and I have posted a thread in the Sprint forum for recommendations (and I'll certainly do some research myself). You are really pushing me in a direction that I NEED TO BE PUSHED because it is obviously a direction I need to go but have been avoiding, for some reason. Either custom ROM, or even back to MF9 and then upgrading again. I'm not sure WHY I haven't tried it yet. Honestly, assuming the issue goes away, I hate the idea of SLOWLY adding things back in until the issue occurs again (IF it does)... I don't know if I am to impatient for that or what it is. I don't know if I am impatient if I can deal with having a phone that continually looses the mobile connection and GPS for two months, so its a bit of a contradiction! :silly:
I don't know how it is on the Sprint version, but on our version, if you are on the old bootloader, then you need to have a specific modem to work with the 4.4.2 rom. Make sure you got the proper modem on your device.
Click to expand...
Click to collapse
I'm actually a bit familiar with the modem issues on your phones from attempting to help a user in this thread: [REF] GALAXY S4 (I9500/I9505) GSM / NON-HLOS - MODEM'S Collection (Odin/CWM/TWRP) who was getting the unhelpful "read the op" replies (in a circle) which WHERE NOT answering his question! But these issues do not exist on the Sprint version. I COULD try going back to a modem version prior to NAE, but SINCE the NAE modem WAS working in the beginning all the time and because it works FOR A WHILE now, I don't see that being the problem.
So, as it stands, my next step seems likely to be a ROM flash. I'm grateful for all your time and assistance! :good:
rsngfrce said:
First of all, I seriously cannot express how grateful I am to you for your ATTEMPT to help me! I completely understand your knowledge of the Sprint version of my phone is limited, but you have already provided me MUCH more assistance than anyone in the Sprint specific forum. While I would love for someone to to tell me do "x" and then "y" and your phone will be fixed, when I came to THIS forum, I was only really hoping for general ideas that would help me think about my issue and you have certainly provided them! :highfive:
(IMPORTANT NOTE): When I 'dispute or disagree' with what you say in the following, I AM NOT SAYING YOU ARE INCORRECT IN ANY WAY, I am just expressing my PERSONAL current understanding of my situation, which I feel helps me to think these things through and might or might not make things clearer for you. I will also provide MUCH MORE information than I'm expecting YOU to think about or respond to, I'm really just recording it, which also assists ME thinking about it.
You are very much correct about it being a strange problem! What I find MOST STRANGE about is that it occurs at some point, usually at least about 12 hours after booting my phone. IF I never had a mobile connection and GPS, it would MUCH less strange. I recently helped another Sprint user who had installed a non-Sprint specific Google ROM (a mistake in the first place, no doubt) ►►[AOSP] Official 4.4.4 - S4 Google Edition - Stable-R2 - Feel the Experience of Nexus◄◄ which worked fine, but he had NO mobile connection. ROMs are CERTAINLY not my area of expertise, having only ever been stock-rooted, but I took it upon myself to assist this user because he was new and the KT-SGS4 kernel he was using with this ROM, I noticed, appeared to me to be the KitKat version, and I believed from the ROM that it should be the AOSP version. Had him flash the AOSP version of the kernel, which resulted in bootloops. Then I discovered that there are Google versions of the KT-SGS4 4.4.4 kernel for other carriers, but not for Sprint, which is the kernel he had in the first place, which comes with the ROM. Apparently, it all works fine on the Sprint phone, but unsurprisingly to me, you get no Sprint mobile connection. I was able to find a similar Sprint specific ROM, which he flashed and it completely solved his issues. But I digress...
Yes, I am running NAE with MF9 bootloader. This is because I started on MF9 without Knox. If I upgraded to the NAE bootloader, I would never be able to go back to MF9, because of Knox. Numerous people have told me Knox does not matter because I am out of warranty anyway, however I PREFER to have the option to go back to MF9 if I should need to, which is why I upgraded in this way. I followed an established upgrade path to achieve this and have seen nobody else who has has used that upgrade method develop this issue.
I think this is probably the best suggestion I have received so far. I have NEVER not used a stock rooted ROM, because my main desire is stability and that is where I have believed I would find it. However, I think it is time for me to investigate a custom ROM, at least try one, and I have posted a thread in the Sprint forum for recommendations (and I'll certainly do some research myself). You are really pushing me in a direction that I NEED TO BE PUSHED because it is obviously a direction I need to go but have been avoiding, for some reason. Either custom ROM, or even back to MF9 and then upgrading again. I'm not sure WHY I haven't tried it yet. Honestly, assuming the issue goes away, I hate the idea of SLOWLY adding things back in until the issue occurs again (IF it does)... I don't know if I am to impatient for that or what it is. I don't know if I am impatient if I can deal with having a phone that continually looses the mobile connection and GPS for two months, so its a bit of a contradiction! :silly:
I'm actually a bit familiar with the modem issues on your phones from attempting to help a user in this thread: [REF] GALAXY S4 (I9500/I9505) GSM / NON-HLOS - MODEM'S Collection (Odin/CWM/TWRP) who was getting the unhelpful "read the op" replies (in a circle) which WHERE NOT answering his question! But these issues do not exist on the Sprint version. I COULD try going back to a modem version prior to NAE, but SINCE the NAE modem WAS working in the beginning all the time and because it works FOR A WHILE now, I don't see that being the problem.
So, as it stands, my next step seems likely to be a ROM flash. I'm grateful for all your time and assistance! :good:
Click to expand...
Click to collapse
Your welcome Did you make any progress?
Lennyz1988 said:
Your welcome Did you make any progress?
Click to expand...
Click to collapse
I'm working on deciding on a custom ROM to try currently, as I want a 4.4.2 NAE ROM, and most have gone on to 4.4.2 NG2, which makes it a bit more difficult (also, most are AOSP, and I'd prefer TouchWiz)... but I do have a short list. Just need to make the leap!
I'm close to flashing a ROM, but OF COURSE my phone has currently gone 2 days and 10 hours (and counting) without loosing the mobile connection/GPS, which is a record I believe, so I better Nandroid again in case something fixed itself somehow...
UPDATE: Haven't flashed a ROM yet, actually got a recommendation for CyanogenMod M "stable" release channel, which I wasn't aware of, which I am seriously considering now. I came across an unrelated thread that where a two user's basically described having my issue and another user said it is caused by the KT-SGS4 kernel. I contacted Ktoonsez, the author of the kernel, he says this is not true, though I am not sure he can be sure that is the case with our phones (he does not own one). While this does not make sense to me, since switching to the Interactive governor, I have NOT had the issue (KNOCK ON WOOD), and the user who mentioned this being a kernel issue did mention possible governor related problems, but I'm not SURE I have had the phone on long enough without rebooting to confirm that the issue is gone with this governor.
Related
Hi there. Very sorry to post about this - I've tried my best to solve the issue on my own and doing various searches, here and elsewhere, but to no avail. Long and short of it is that WiFi and Bluetooth both seem to have died on me.
I have a Canadian Bell Samsung Galaxy S4 (SGH-I337M). I have been installing Danvdh's Google Edition ROM for some time now, and so far, it's been great. After installing 4.4.4 (clean, after a full wipe), it seemed to work, but my phone froze up - completely unresponsive, including the power switch. Pulled the battery but then afterwards could not turn on WiFi or BT - just says "Turning Wifi On" but nothing ever happens - the message just stays there perpetually. Bluetooth same thing, except the message goes away after a few seconds.
I've tried all of the following to try to restore WiFi, none of which has worked:
- Odin reflash of modem.bin and NON-HLOS.bin, multiple times (from the most recent stock ROM for my device - I337MVLUFNE1, 4.4.2)
- Complete reversion to stock (I337MVLUFNE1, 4.4.2) using Odin - neither WiFi nor BT worked under stock either
- Factory reset while in stock
- After rooting stock, using an SQL editor to check the value of wifi_display_on - it was 0 but just to make sure I set it to 0 again
- After rooting stock, deleting wpa_supplicant.conf in both /data/misc/wifi/ and /etc/wifi/
- Reinstalling Danvdh 4.4.4 (clean), but this time with the Googy kernel rather than the KT kernel (in both cases it was the customized version, not the pure Nexus one)
- Also tried, just for the heck of it, switching to ART to see if that might make a difference - it didn't
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Please note - I originally posted this in the thread for Danvdh's ROM. I didn't get any feedback there, so suspect I perhaps might be posting the question in the wrong place, so am trying here, in addition to the thread for Canadian S4s. I trust such cross-posting is OK (but if not please let me know).
not_su said:
Hi there. .....
- Ringing a bell, opening a book and lighting a candle
In other words, I am at my wits' end. If anyone might have any suggestions - even just a link to some other possible solution I would be most grateful. I have tried searching, both in XDA and elsewhere, for a possible solution and have tried everything I've found, but so far, nothing has worked. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
To be honest, I have no idea if that could be related... on one of my I9300, directly after OTA, I lost the WiFi and BT. Problem was WiFi or/and BT, when I pressed to switch it on, was turning on, for maybe 0.5 sec, and then was turning itself off.
now the funny story: because I unrooted it and cleaned prior to OTA, it was immaculate, so I took it to Sammys hiTech local specialists.
They two times were returning phone to me, stating that they are unable to repeat the problem. So, I asked them to not send it back, and that I'll pick it from Service Centre. I used that opportunity, and asked another local master to show me how to use the WiFi on my 100% working phone. He itself packed it into same envelope and disappeard for half a time, after that itme I was informed that my phone will be sent to me after motherboard replacement.
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.
spamtrash said:
now, the correlation: no (in theory) action which could affect hardware, obviously CAUSED damage. If I'd be you, I'd try to restore the clean condition, and I'd go to service centre.
Click to expand...
Click to collapse
Thanks very much - appreciate the suggestion, but the warranty on my phone ended last month, so I'd get hit for a bill for the repair.
You raise a good point - it may well be a simple hardware failure that happened, coincidentally, when I updated. Alas, I wouldn't know where to begin to try to figure out whether or not it is a hardware failure...
I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)
Tsuushin said:
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Click to expand...
Click to collapse
here....
Tsuushin said:
I have the same problem with WiFi (bluetooth works though) after upgrading to 4.4.2 today.
The only modification I had done before were CF-AutoRoot and TWR.
I unrooted from SuperSU's menu prior to upgrading to stock 4.4.2 with KIES, everything seemed to work, except now I can't turn on wifi.
Where can I get the modem.bin for a Canadian Bell Samsung Galaxy S4 (SGH-I337M)?
Thanks for any help!
Here's the about screen: (Shouldn't the Baseband version be the same as the build? What gives?)
Click to expand...
Click to collapse
I don't remember where I got mine but it was extracted from the latest stock rom. Googling the build led me to this page, which seems to have links to download the most recent stock for the S4.
Not sure about your other question. I know when I update a new custom rom, the baseband version doesn't change - that only changes when I update the modem or flash an updated stock rom using Odin. You might also want to try flashing the NON-HLOS.bin file - I read elsewhere that that has helped others. Of course, feel free to also try all the other options I've noted above.
In case it helps other people with the same problem, here's what I did that fixed the WiFi issue:
I flashed the latest modem.bin (twice) and NON-HLOS.bin, but it didn't fix the WiFi.
I flashed the latest stock ROM, and now WiFi works.
Cheers.
RELEVANT DATA: Sprint Samsung Galaxy S4, Software version: NAE, Android version: 4.4.2, Baseband version: NAE, Kernel: KT-SGS4 4.4, Recovery: PhilZ Touch 6.48.4, SuperSU. Stock Rooted. Upgraded to NAE from MF9 with the method in this link: [HOW TO]Update to 4.4.2 NAE w/Root while Keeping MF9 Bootloader w/ Lock Screen Fix, so no Knox.
Upgrade went great, it was actually the most stable phone I have ever had. Then, all of a sudden, I started loosing my mobile connection and GPS a while after booting the phone.If I reboot the phone, they start working fine again, but after an unknown amount of time, they both stop working again. WIFI never stops working. I have no idea what caused this to start happening and it REALLY SUCKS!
I did edit my APN, trying to fix an issue I was having with sending MMS's, but I'm pretty sure I restored the NAE stock version, which didn't help.
I have attach a logcat filtered at warn and higher and I tried to make a call during this logcat and was told I had no mobile connection. I really can't read these things, so I don't know if there is anything useful in there.
If anyone has any idea what might be causing my problem, I would be eternally grateful for some assistance!
I'm becoming convincinced that I must hold some sort of record on XDA for having the greatest number of issues that nobody else has ever experienced...
rsngfrce said:
I'm becoming convincinced that I must hold some sort of record on XDA for having the greatest number of issues that nobody else has ever experienced...
Click to expand...
Click to collapse
Sound odd. Sorry I can't help you directly.
I would suggest using Odin to flash NAE firmware only tar again.
I'm assuming you've updated PRL and Profile?
I think you need to go full NAE tar file to fix your problems. When you do partial upgrades like you did they result in nothing but problems. If you want your phone to work everytime you use it. Flash the full NAE tar to bring your phone up to date, root it with cf autoroot, install your mods and enjoy a trouble free phone. There is nothing to worry about knox. It doesn't hamper your phone at all. Your warranty is already expired if you have a phone that has MF9 on it so update your phone and you won't have any of these problems.
I appreciate both your suggestions and will consider them. What I don't understand though would be why it would be working perfectly for a month or two and then suddenly develop the issues out of the blue? Also, I haven't seen anyone else who upgraded with this method mentioning this problem. This tends to make me think the problem lies elsewhere... possibly related, but elsewhere.
(By the way, I raised the question of why I would care about Knox if I was out of warranty and it was pointed out that once you have Knox, you can never go back to MF9... and who knows if I might decide I need to do that for some reason... I prefer to have the option at least.)
I'll tell you what is really STRANGE... right now my phone has been 17 hours since boot and both the mobile data and GPS are working... I can't remember the last time it has gone that long! Maybe my random twiddling finally fixed it...
WELL... of course, I spoke too soon, the issue has now returned. I'm at 22 hours after boot, but I don't know when it started and I did reboot since I said it was working after 17 hours...:banghead:
Hi all, I apologize for my low level of English. I want to tell that to write this report use the google translator.
I also thank in advance the help that you can give me.
Acontinuacion expose my problem:
I followed the steps in a tutorial, to release my samsung i9505 galaxy s4, exposed one of the most important forums, Htcmania.com my country, Spain.
By exposing my problem in the same forum that supra and receiving no response clarification about my problem, I turn to the more important to try to find a solution forum. I go to XDA-Developers.
I do a copy and paste of the report I wrote on the forum that I quoted earlier as I explained my problem well:
My s4 with Android 4.4.2 was completely "virgin" had installed the rom Stock samsung, was not released, was "Yoigo" any advanced recovery had not installed, and had no permits super user "root".
I wanted to release it (Unlocksim) seeking information HTCMania, and I found the following topic "Free S4 I9505 (Unlocksim) in 4.4.2" I followed all the steps in the tutorial. One of the "requirements" was to be root to do a backup of the EFS before touching anything, and to use the application "Region lock away"
So no, I did root, flashing by odin CF-Auto-Root 4.4.2 package.
Being root installed the advanced recovery "CWM" philz touch. And I found myself at this point I made a backup of the EFS system being completely "virgin" that is, with stock rom samsung and android 4.4.2. I followed the steps in the tutorial that I have made previously to unlocksim. One of the requirements to release the phone was change the modem to modem I9505_DXUAME2_MODEM, so I changed the phone modem and followed the guidelines set by the tutorial,
Region to use the application could lock away briefly display an error is possibly to blame for me as I'm seeing. This error could display for two seconds, but from that moment everything seemed to work well, the phone was released. So I changed the modem again for mine.
At this point I decided to choose to install a cooked rom based on stock, namely Omega rom v38.1 for s4 I9505.
And at this point is when my headaches begin to appear. I have experienced problems with the release ... see, the issue is that when the network coverage data is in H + the phone works perfectly, but only if H is not able to load websites etc. This has led me to the edge as I can not be aware every moment of the type of data coverage.
My questions are:
1. Is there a way to stop the phone as he was before unlocksim, ie leave it as it was originally being from Yoigo? (Remember to keep a copy of SAI realized when the system was completely untouched.)
2. How I can solve this problem with the network coverage data?
3. What do you advise me to do?
Please help. Greetings.
you might want to try searching sammobile to see there is a ROM you can download and flash that's for your country and ideally for your phone provider as well. I've run into issues like this on a couple of occasions. One was indeed that the country's ROM I flashed uses differant frequencies and I had the same mobile data connectivity issues you're talking about. This is rare for the international Samsung phones but it does happen. The other scenario I ran into was after flashing a port of the Google Play Edition onto tit, which gave it extended network options, and everything worked quite well but when I restored to stock from a backup on my sdcard I had connectivity issues, once again just like you're describing. In this scenario flashing a fresh stock ROM entirely solved the problem.
Note that in the second scenario I didn't redo the data partition. Presumably flashing the system fixed it or reflashing the firmware partition reinitialized things the way they are meant to work for me.
search for I9505 (or whatever the model of your phone is) where it says search for your device http://www.sammobile.com/firmwares/
Google around the codes if the results aren't revailing enough for what's stock for you and try reflashing in odin. If it persists then backup your apps, wipe the data partition, possibly backup your internal storage as well if you have a stock recover, and try again. Beyond that I haven't had to deal with further problems than that yet but I saw that no one else had responded...
Hey folks, hope I`m not coming off as one of the "hey, I broke my stuff, how can I fix it without anyone knowing I broke it" types LOL. I`ve actually been modding Android devices since my Droid X what seems like ages ago, and have done a few along the way so it`s not new in theory. So....I`ve got an I337 S4. It appeared with 4.4.4 on it, and you can imagine how that went when I started modding. My ultimate goal was/is simply to have the native tether app working (and it was, very briefly). Long story short, I bricked it, and brought it back with 4.3 on Odin. It functions fine with the exception of Wifi. It won`t activate wifi, a very, very common problem I`m reading. I`m totally comfortable doing the mods to get it going, I just don`t know what I need. It`s rooted. (here`s where I`m lost): Baseband version is FNJ4, bootloader is FNJ4, but the BUILD number is MK2. Tried the BypassLKM method, no dice. So my question is this: What is the simplest way to get WiFi access back so I can get the Native Tether function going again? If everything was FNJ4 or MK2 I`d be able to make something happen, but several approaches have gotten me bootlooped and I`1m just ready to get it right (safestrap has saved my a$$).
Thanks for any help!!
update
See, a studious and persistent student of modding gets the worm LOL. I got my WiFi back with this procedure right here http://forum.xda-developers.com/galaxy-s4-att/general/how-to-root-i337ucufni1-t2881298
I used the safestrap method without a hitch. Hope it helps someone else out there
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Hey folks,
I'm having the exact same issue as the OP. Odin does a successful install on the phone but I get the unauthorized reset message and then Wifi does not work when prompted on the next screen.
Is there a tracfone version of the rom or a fix that anyone here knows of? Thanks!
@drasnah
I have yet to get any kind of reply from anyone on this. Either now one knows, and is not stating so, or doesn't care.
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
20eyes said:
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
Click to expand...
Click to collapse
First this is not a wi-fi problem it is a re-flashing of the rom problem.
Second, I do not have access, root or otherwise, to any of the system files on the phone.
Third, with the first two in mind this possible solution is of no help.
Fourth, Re-read my original post. I have given complete detailed information as to what I have access to and what I have done.
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Curtis1973 said:
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Click to expand...
Click to collapse
Not sure if that's correct? It depends on the firmware and odin version being used.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Nate1k904 said:
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
Click to expand...
Click to collapse
Post more details on the error, screenshots, firmware and odin version used.
Need to know if works. Or if needing to settle for a different route.
The_WABBIT said:
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Click to expand...
Click to collapse
J3 sm s320vl... tracfone root availability? Just bought phone hopefully got a good one to root? Or maybe someone knows who maybe be able to... please help
No updates? Interested, I have the same phone.
There is no solution for this phone. It will forever be a Trac-phone.
Yes, it nice to imagine what could had been. If there was a fix for the locked bootloader. Its encrypted, and is highly unlikely to be broken by anyone.
Do not flash the boot.image that some people have suggested
Although that method works on some devices such as the AT&T Samsung Galaxy S5. In this case flashing the boot.image from an unlocked device does nothing but places the phone into an even more precarious situation, that makes it unusable even as a Trac phone.
While its true that this very low budget phone could had been decent with a custom Rom ,
You will not be able to get it working.
I have one that belonged to my daughter a couple of years ago and I managed to get it boot into the system again.
Its only function is as a calculator, or preschool game, the cellular reception and Wifi connections are highly unstable and will not stay connected.
Now it serves as my nieces play toy. I would donate to some poor person at the Salvation Army it if it was useable.
By the way, for anyone reading this.
If you have an old phone that is useable. You could dramatically help a Homeless people, by gifting them with a phone especially, if it has some minutes on it.
This gift will help them schedule job interviews, doctors appointments , etc and you will feel good knowing that you helped someone in need.
I have done this before, and will be dropping off a Blu phone, and Kindle Tablet this week.
tsongming said:
There is no solution for this phone. It will forever be a Trac-phone..
Click to expand...
Click to collapse
It is possible to gain root on this device.
ashyx said:
It is possible to gain root on this device.
Click to expand...
Click to collapse
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
tsongming said:
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
Click to expand...
Click to collapse
See the thread below. Root was gained, albeit temporary. However I believe this is due to kernel panics which may be solved by a few build.prop edits. We had to do the same on the J327T1.
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-galaxy-j3-sm-s320vl-rooted-t3561762
Also if you firmware S320VUDU1APG2 then why not just update it to the firmware that has been reported to work?
I have found one these phones left on a table of a food truck area, screen was cracked - the device was only getting the android guy with triangle on it, I done some research and found the stock rom and flashed it with odin; as some have mentioned in comments above I also experienced wifi issue, so I thought I had installed incorrect rom - downloaded a different one this was a combination file that was the factory repair rom used for testing the device, but wifi worked - it wasn't a fully working telephone it didnt have the app store, well it really didnt have any apps, but I found I could copy over apk files from my PC to the device and then install them, so the phones not completely useless or junk --- it could be used for something. I myself am using that device as a security camera using IP CAM app works great. I was actually using this device for quiet some time as my roku tv remote, because my actual roku remote grown legs and walked off... i havent tried this, but I am sure you could install a launcher apk such as "apex launcher"
well i wasted enough of your time today...