Hello
I have a problem with the Wi-Fi on my device (I337 AT&T) kitkat 4.4.4 Firmware NJ4, when you restart the device does not save the Password of Wi-Fi. Is there a solution?
startmsn said:
Hello
I have a problem with the Wi-Fi on my device (I337 AT&T) kitkat 4.4.4 Firmware NJ4, when you restart the device does not save the Password of Wi-Fi. Is there a solution?
Click to expand...
Click to collapse
If you're stock without root, youll have to use ODIN to flash NB1 and update again. If you have root, open up a file manager like ES File, go to /system/build.prop and find the line that says something like ro.securestorage.support and change it from true to false. Reboot and it should work now.
I didn't have this problem until I attempted an upgrade from NB1 to NJ4. Then my i337 S4 started to forget WiFi passwords. So I used ODIN to reinstall NB1, but the problem persists. I am rooted, and I tried the edit of the ro.securestorage.support entry in the build.prop file, but that didn't work for me.
FWIW, the passwords still exist in the wpa_supplicant.conf file but, for whatever reason, the phone isn't reading them and prompts me to enter the password. (This was true before the edit of the build.prop file, as well.)
Does anyone have any other ideas? So annoying.
Related
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:
I have the Samsung Galaxy S4 SGH-I337 Model with AT&T. I've tried some tutorials online and some tutorial threads that I found on here. The problem is Odin it says fail each time I try to flash the AT&T 16 pit file with the MK2 file. I'm putting the MK2 file in the PDA. It's also soft bricking my device each time. When I boot up my device it automatically goes to Odin mode with the smart phone icon with a triangle and the computer icon. Under that it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." To fix this issue I have to use the pit file only in Odin. Everything else fails. The reason I want to downgrade is so I can root my device so I can tether my phone data to my galaxy tab. None of the non-root tether apps works for me in the play store. Any help?
Edit, are you following this
http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
I just helped my friend root is Verizon Samsung Galaxy S4 using towelroot but now that he wiped the cache and factory reseted his phone (running stock) the wifi is greyed out. Any solutions?
Ethansev said:
I just helped my friend root is Verizon Samsung Galaxy S4 using towelroot but now that he wiped the cache and factory reseted his phone (running stock) the wifi is greyed out. Any solutions?
Click to expand...
Click to collapse
WIFI f*cked by towelroot, same thing happened to my friends S4 i95005
We tried everything, from flashing stock FW, modem, bootloader, wifi fix.
This tools should be banned from XDA
It's quite simple to fix it:
1) Install "Build Prop Editor" by "JRummy Apps Inc." from the Play Store
2) Open the app and search for the line "ro.securestorage.support=true", and change "true" to "false"
3) Make sure the change is saved and reboot your device
And that should do it
My wifi was having issues.
I made a backup and removed the following file. After a reboot, everything worked for me again:
/data/misc/wifi/wpa_supplicant.conf
This file stores your wifi settings and network details for each access point, so you will need to re-enter your wifi details again, or edit the file to copy out the old ones to the bottom of the newly and automatically created replacement file after your reboot.
Ethansev said:
I just helped my friend root is Verizon Samsung Galaxy S4 using towelroot but now that he wiped the cache and factory reseted his phone (running stock) the wifi is greyed out. Any solutions?
Click to expand...
Click to collapse
just reflash the stock rom using odin which you can download from http://www.sammobile.com/firmwares/database/
and then root the phone using my method
thread link here http://forum.xda-developers.com/galaxy-s4/i9505-develop/root-samsung-galaxy-s4-i9500-i9505-t2982844
hope this helps.
At wits end, but can't get my WiFi to turn on at all.
The setup l had before was stock Bell 4.4.2 but rooted and TWRP (with backups).
Forgot to turn off (replacement phone, forgot to turn off), auto-updates. Phone tried to update to 5.0.1 but failed, telling me to use Kies. Had to flash in Kies as my phone got stuck in Samsung's boot logo. Before plugging into Kies, l tried wipe cache, battery out, and then wipe/reset, none worked. So l plugged into Kies, it did it's thing. Went smooth. Now, my wireless just won't turn on at all. Rooted it with CF AutoRoot. Went to wpa_supplicant folder, to find l don't have the .conf file. Renamed the folder, power cycles, system created the folder but no file again. Created a file named "wpa_supplicant.conf" and power cycled, renamed it, system didn't create it again. So l think l found the issue but any fix to this? Maybe running the wrong version, even though l have stock Bell apps (how l missed them )
MODEL SGH-I337M
VERSION 5.0.1
BASEBAND I337MVLUFNI2
KERNEL 3.4.0-4508315 [email protected] #1
BUILD LRX22C.I337MVLUGOC4
KNOX 2.3 (TRIPPED)
Side note: I do get a WiFi MAC address that appears valid (haven't compared to my router logs) under status.
=================
Update I FIXED IT! YAY!
For those who are having the same issue. Do the following steps:
Download Odin 3 - Make sure Kies isn't running
Verify ID COM has a number like COM0 or something.
Leave everything else alone.
Download ROM from SamMobile or another ROM site Link (filtered to Bell)
Unplug phone
Place phone into download mode (Vol Down, Home, Power)
Using Odin, hit PDA and put the ROM in, give it some time
Plug phone in, and verify COM and message saying ADDED!!
Start it, then give it some time.
If you want to root it, do the same procedures but grab CF-Auto-Root and repeat it. Easy root.
Optional stepsbut l did it anyways:
Before doing this, l rooted it with CF Chain, and installed TWRP. Wiped Cache, Dalvik, System.
Hello dear friend
i wanted to thank you for your solution and specially download links, had the exact same issue which was resolved by the solution you provided.
I recommend flashing with Odin and a stock ROM from Sam mobile.com. kies has never worked for me so no now stick with Odin.