Database Users

[Q] My samsung galaxy s4 won't remember my wifi network

Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.

kickstand03 said:
Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.
Click to expand...
Click to collapse
Okay well I fixed it by unrooting and using odin to go back two updates prior to mf9, then did 2 ota's back to mf9 and rooted again. all is working fine, also fixed the phone's getting too hot problem and battery last longer than ever.

it's your kernel that was causing this...for future reference, if you're on mf9 with the stock mf9 kernel and do not want to have to wipe your phone to fix this, you can use ShabbyPenguin's kernel...i had this issue before on my s4 and this worked for me...why the rooted stock rom doesnt like the stock kernel for wifi blows my mind...lol

How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.

yhendra said:
How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.
Click to expand...
Click to collapse
the link you refere to, is not properly linked, can u fix it please? having the same issue

Neikosr0x said:
the link you refere to, is not properly linked, can u fix it please? having the same issue
Click to expand...
Click to collapse
I am sorry for the belated response. I think the link might change to http://forum.xda-developers.com/showthread.php?t=2685519
I do apologize for this inconvenience. Good luck.. :good:

Hotspot will not toggle on! Even after using return to stock tool.

So I unlocked, rooted and flashed my fiancé's moto x pure, and she didn't like the ROM (from 5.1 to 6.0, also flashed modem) She didn't like either of the ROM's so I converted back to stock 5.1 using the the return to stock tool located on the forum. Problem is...
Hotspot is suddenly not working. It doesn't do anything at all. If we click the toggle, it remains grey like it knows we pressed it, but it won't come on. Furthermore, it never checks for permissions. We have Verizon Unlimited so it will usually prompt a permission authentication. This is, only if Verizon patched somewhere along the line because before we could use it without it validating.
If it will help anyone, I'll provide a log cat.

DroidsOnRoids said:
So I unlocked, rooted and flashed my fiancé's moto x pure, and she didn't like the ROM (from 5.1 to 6.0, also flashed modem) She didn't like either of the ROM's so I converted back to stock 5.1 using the the return to stock tool located on the forum. Problem is...
Hotspot is suddenly not working. It doesn't do anything at all. If we click the toggle, it remains grey like it knows we pressed it, but it won't come on. Furthermore, it never checks for permissions. We have Verizon Unlimited so it will usually prompt a permission authentication. This is, only if Verizon patched somewhere along the line because before we could use it without it validating.
If it will help anyone, I'll provide a log cat.
Click to expand...
Click to collapse
I'm having the exact same issue except I am Rooted on 6.0.1
Was just about to flash to stock but won't now seeing it hasn't helped you. I also have verizon unlimited. Not sure there is a connection but it doesn't hurt to mention.
Also, just realized wifi is not working at all.

themufferman said:
I'm having the exact same issue except I am Rooted on 6.0.1
Was just about to flash to stock but won't now seeing it hasn't helped you. I also have verizon unlimited. Not sure there is a connection but it doesn't hurt to mention.
Also, just realized wifi is not working at all.
Click to expand...
Click to collapse
I had this same problem with my Nexus 5x. Check this out and see if it helps. In this guide it is left out that "adb shell settings put global tether_dun_required 0" command must be done after you reboot the phone and have USB debugging enabled.

https://www.androidfilehost.com/?fid=24459283995315346
Link to February's updated modem. Fixed everything!

No more Wi-Fi Calling/VoLTE/RCS after flashing HOME_CSC in Odin

Hey guys,
After discovering the latest root method I was excited to try it out. Unfortunately, I botched it up and had to reflash the stock firmware. I downloaded the T-Mobile PD8 file from Sammobile for the G935T and flashed all the packages. I got root working, and everything seems to be fine except for the absence of these three features. There are no options for any of them in settings or their respective apps. I live in an area with bad coverage so I am pretty dependent of Wi-Fi calling. Even reflashing that HOME_CSC file didn't help. Now I'm not sure what I have to do to get these features back.
Any help would be appreciated.

You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?

Binary100100 said:
You're sure that you used HOME_CSC for T-Mobile? I'm thinking that either you didn't download the correct firmware (example being that you may have downloaded for Cricket or something of that sort) or you could have used the CSC_TMB file by mistake. As far as I know, they should both be the same, only HOME_CSC doesn't wipe the data from your device. Remember seeing an error of any kind after flashing?
Click to expand...
Click to collapse
Yeah I'm pretty sure it's the right file...
HOME_CSC_TMB_G935TTMB3APD8_CL7856276_QB9546824_REV02_user_low_ship_MULTI_CERT.tar.md5
No errors, I also reflashed the BL and CP to no effect... Not gonna do the AP because it will make me lose root.

bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?

TheDoolster said:
bump
I flashed the entire stock firmware and the features are STILL missing. I'm getting tired of reinstalling all my apps. Does anyone have any ideas?
Click to expand...
Click to collapse
Without going through the why or how that all happened and the ways to resolve without reflashing, I'd just recommend that you download the full PD8 firmware from this thread http://forum.xda-developers.com/showthread.php?t=3331528
I would skip the repackaging .tar part to preserve /data. Worked for me and hopefully will for you.
(PROVIDING YOU STILL ARE EXPERIENCING THAT ISSUE)

Before yesterday, I found myself in the exact same situation. I had a rooted device with all of my apps installed - including Xposed modules. But I had lost WiFi Calling. I didn't even see VoLTE settings in the Phone app. So I started from scratch. I wiped out my system. I then used ODIN to flash ADB8 firmware from T-Mo. WiFi Calling was there. I then used ODIN to flash EngBoot. WiFi Calling was still there. I then rebuilt my entire system w/o Xposed. WiFi Calling was still there. I then started to add all of my modules, one at a time. After loading everything, WiFi Calling was still there.
I then started AFWall+. Lo and behold, WiFi Calling completely disappeared. I turned off the firewall. WiFi Calling was there. So I left it turned off and started to configure my modules. WiFi Calling worked - until I loaded the crowd-sourced rules for XPrivacy. I turned of XPrivacy and WiFi Calling returned.
It all makes sense. I know know that the Phone app must connect to a wireless network via TCP/IP. And if it can't, then WiFi Calling is disabled. So I spent several hours working through XPrivacy and AFWall+ rules. And at the end, I now have a fully functional phone.
I don't know if you use AFWall+ or the XPrivacy Xposed module. But you might check any control systems that could limit the connection between the Phone app and the network.

Don't use HOME_CSC. Use CSC. This will wipe data unfortunately, but i had different issues using home. And using the non-home fixed them.

Flashing the July 9th updated firmware from sammobile worked for me. Lost root, but I would rather have these features.

I unrooted my Galaxy s7 edge with Rogers and I am miss the option for volte any ideas on how to get it back?

Not the right csc
The home_csc is not the right one for t mobile. It should be home_tmb_csc

Missing "HotSpot & Tethering" / Hotspot not functioning

So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.

here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"

My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.

I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?

beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.

I was referring to loss of internet connection, not signal related. I thought that was clear, sorry

Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.

sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.

Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.

Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk

No LTE - Issues & Suggestions? Flash radio/modem?

XT1625 (regular G4) here and I've had a weird issue for a while. Got the phone back in February, did a warranty claim a couple months ago for this and another issue. Ever since I got the first phone, continuing onto the replacement, I've never had consistent LTE. The only time I seemed to get it was on the replacement phone right out of the box. Restarted and it disappeared until the next Android update where LTE would appear on the first boot and disappear if I restarted, until the next update. I could get LTE to work and verify proper speeds, then restart and it's back to HSPAP until a wipe or Android update. I made a crappy video about it here: https://www.youtube.com/watch?v=TYl5-Jn8rmU
Yesterday, I got an urge to install LineageOS in hopes that the issue would be permanently fixed on there. Nope. Still no LTE, only HSPAP even after messing with APN settings and radio settings in the service menu. It was a long process and I was busy but I don't think I had LTE on first boot oddly enough.
Also yesterday I fixed a spare G2 that had been having issues receiving MMS and getting Data for weeks (while calls and SMS worked fine), an issue that came up out of nowhere. Contacted provider multiple times, no issue there. Wipe phone, still same issue. Finally had the eureka idea and re-flashed/wiped the bootloader and modem. Data and MMS came back! I bring this up because I'm wondering if maybe my G4 needs the same thing done? It's not a provider issue because LTE does work under certain circumstances and I've called them countless times about it. Not an APN issue because those settings don't change on restart.
Anyone got any ideas? Is this issue seen on other people's phones? Is there a collection of radios/modems/basebands that I can download and flash? I did find a thread with them but they had been removed.

natenkiki2004 said:
Anyone got any ideas? Is this issue seen on other people's phones? Is there a collection of radios/modems/basebands that I can download and flash? I did find a thread with them but they had been removed.
Click to expand...
Click to collapse
You can flash the modem always seperately with the command
fastboot flash modem NON-HLOS.bin
From here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
But make sure you have at least nougat firmware! If not, it's better to flash the whole rom but it will wipe everything on your device.

strongst said:
You can flash the modem always seperately with the command
fastboot flash modem NON-HLOS.bin
From here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
But make sure you have at least nougat firmware! If not, it's better to flash the whole rom but it will wipe everything on your device.
Click to expand...
Click to collapse
YES!!!! THANK YOU!!!!
LTE is now working, even after rebooting. I downloaded that stock ROM file and pulled out fsg.mbn and NON-HLOS.bin then booted into fastboot and entered the following commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I genuinely do not understand how I got 2 factory phones and neither would stick to LTE out of the box. Also odd that installing LineageOS clean didn't work to flash those particular files. Just like the G 2014 model that required just about the same commands to get GPS working again.
Thanks again!

I also want to note that I used this same process to fix data on a Moto G 2014 variant and a Moto E LTE variant. I am doing this again because the G 2014 seems to have lost data again. I wonder if Motorola has issues with it's software corrupting over time or if the chips in these devices share something in common.