Posting here because new account can't post in Goldeneye Rom thread. My wifi is disabled and won't turn on. I installed the jflteatt Faux 005m kernel, have no idea if that's the problem or not-- and I can't find the original Goldeneye kernel without flashing the entire rom. I've tried different modems, and un-doing all of the Nottouch Xposed stuff, and un-doing every other tweak or addition I've made on it. I have no idea what the problem is. Has anybody else had these issues? Do you know what the fix is?
I'm having a similar issue, wifi was working fine and now it WILL NOT turn on, no matter the rom or kernel
Hmm what version are you running of goldeneye? I have the 3.0 installed and then I flashed the GOLDENEYE-i337m-FiX-XXUBMF8 and it screwed my wifi up. Honestly idk what that was for but after reflashing without it made my wifi work.
Sent from my SAMSUNG-SGH-I337 using xda premium
kL7GtEd said:
Posting here because new account can't post in Goldeneye Rom thread. My wifi is disabled and won't turn on. I installed the jflteatt Faux 005m kernel, have no idea if that's the problem or not-- and I can't find the original Goldeneye kernel without flashing the entire rom. I've tried different modems, and un-doing all of the Nottouch Xposed stuff, and un-doing every other tweak or addition I've made on it. I have no idea what the problem is. Has anybody else had these issues? Do you know what the fix is?
Click to expand...
Click to collapse
if youre on att, flash this and try to see if it fixes your issue, its a stock kernel
http://www.androidfilehost.com/?fid=13858085825318748360
Try an different kernel, that will fix the wifi.
Good luck.
any follow up on this? does a new kernel work? i thought i was already on the stock kernel, but i am not entirely sure.
It is the correct fix.
Sent from my GT-I9505 using xda premium
Related
Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104
Theshawty said:
Over in the Omega thread for the I9505, I've been having a discussion with a few people regarding why the wifi breaks when you flash say an MF4 based rom from an older base (like if you're on stock MEA or something) however all I got in response was to flash an MF4 modem package and wifi will start working.
Wifi, as we all know, is handled by the kernel and not the modem, so why does wifi start working when you flash the modem for the base you're on if you're using a stock kernel? Are the stock kernels dependent of a certain modem? Because when I flashed Wanam's Adam kernel (source-built) straight over Omega 6 (MF4), wifi started working.
Why is it like this, you think?
Click to expand...
Click to collapse
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
Ya even though the WiFi module is in the kernel it would seem that Samsung have put some sort of dependency in there that relies on a particular modem. (Maybe it is just that particular modem and all other modems from the MF4 one on will work with whatever new kernel you use, it could just be something big they changed in MF4 compared to MEA)
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
From what I can gather, it's always been like this. Check this thread (last pages) and see that they are being highly ignorant. http://forum.xda-developers.com/showthread.php?t=2253528&page=410
It's basically this: "flash the latest modem or sod off" but used with kinder words. I refuse to flash the MF4 modem just to fix the wifi when I know that flashing a source-built kernel fixes it just as well. Besides, a newer modem doesn't mean a better modem. The problem needs to be fixed, not circumvented.
Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
Don't forget that people do stupid things just because they have heard that's what to do, need I mention the 'calibrating' the battery situation! If you can get it working with a custom kernel built from source then that is the way it should be done as it isn't a modem issue, it is a kernel issue, obviously Sammy put something in there that changed how it works in the last code drop.
On the other hand, maybe they did that to force people to use only the new modem, maybe the old one uses too much power, has bugs etc. God only knows why they do what they do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think we'd need the help of some very experienced kernel devs. Maybe @AndreiLux can share his knowledge?
That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta
nodstuff said:
That's probably the best option, get a definitive answer from someone that understands this stuff better than we do.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I bet Samsung has placed some sort of dependency in the kernel (like you said) that when it doesn't find the right modem, it crap out and destroys wifi.
Djembey had an interesting reply: http://forum.xda-developers.com/showpost.php?p=42806026&postcount=4104
Thread closed at OP's request.
Hello All,
My setup... ATT S4 MF3 - Rooted - safestrap v3.6 installed and working.
Flashed the ViSX.MF3.Blue.Ice ROM. Flash went well and everything seems to be working EXCEPT the wireless. (wireless wont turn on) Cell modem working and so is Bluetooth. I have flashed several ROMs and get the same issue. The only one that has worked is Deadly_Venom_v8.1.0. and everything is working. I have tried diff. kernals and still no luck. (ausdim, Knootz, etc.)Have also tried loki patch. What am I doing wrong? Please help. I really like that VisionX ROM and want it to work.
THANKS!
Equiptech66 said:
Hello All,
My setup... ATT S4 MF3 - Rooted - safestrap v3.6 installed and working.
Flashed the ViSX.MF3.Blue.Ice ROM. Flash went well and everything seems to be working EXCEPT the wireless. (wireless wont turn on) Cell modem working and so is Bluetooth. I have flashed several ROMs and get the same issue. The only one that has worked is Deadly_Venom_v8.1.0. and everything is working. I have tried diff. kernals and still no luck. (ausdim, Knootz, etc.)Have also tried loki patch. What am I doing wrong? Please help. I really like that VisionX ROM and want it to work.
THANKS!
Click to expand...
Click to collapse
are you flashing the mf3 modules after each rom you install? you can't flash different kernels. and I'm pretty sure the loki patch is not needed when using safestrap.
Just need to flash the modules. I downloaded my first ROMs and didnt choose the stock kernel and had the same issue. I did however read through all the topics as anyone should and already had the module flashable on hand so it was a simple matter of flashing in Safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Feel Dumb
TY guys! I am feeling dumb. I too had that module on my SD card but hadn't used since first flash (over week ago) and forgot about it. Now all working good. Again, Thanks.
I've been messing around with gpe roms since safestrap was released and yesterday I started having a problem. when I rebooted my phone I lost service. I've been using the same roms. deleted the rom slot and reflashed everything and still having the problem. I don't understand what's going on because this wasn't happening a few days ago
edit: on reboot my lockscreen says: roaming indicator off. and in settings under mobile networks, access points is missing. there's no apn settings and no option to add any
deadenz said:
I've been messing around with gpe roms since safestrap was released and yesterday I started having a problem. when I rebooted my phone I lost service. I've been using the same roms. deleted the rom slot and reflashed everything and still having the problem. I don't understand what's going on because this wasn't happening a few days ago
edit: on reboot my lockscreen says: roaming indicator off. and in settings under mobile networks, access points is missing. there's no apn settings and no option to add any
Click to expand...
Click to collapse
Which GPE rom have you flashed? 4.2.2 or 4.3? did you flash your kernel after you flashed the ROM?
If you read the OP it says to do so, this typically fixes cell service and wifi issues.
http://forum.xda-developers.com/showthread.php?t=2448925
FourPointedFreak said:
Which GPE rom have you flashed? 4.2.2 or 4.3? did you flash your kernel after you flashed the ROM?
If you read the OP it says to do so, this typically fixes cell service and wifi issues.
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I've flashed quite a few. both here in the att forum and virginrom from tmobile. they all worked fine up until a few days ago. yes they are 4.2.2 and yes I flashed the mf3 modules.
btw, this isn't happening when I flash a stock touchwiz rom. running shostock right now with no problems
deadenz said:
I've flashed quite a few. both here in the att forum and virginrom from tmobile. they all worked fine up until a few days ago. yes they are 4.2.2 and yes I flashed the mf3 modules.
btw, this isn't happening when I flash a stock touchwiz rom. running shostock right now with no problems
Click to expand...
Click to collapse
From my understanding, SafeStrap only supports TouchWiz roms and that's why you would or would not be seeing these problems.
FourPointedFreak said:
From my understanding, SafeStrap only supports TouchWiz roms and that's why you would or would not be seeing these problems.
Click to expand...
Click to collapse
yeah I know that already..
deadenz said:
yeah I know that already..
Click to expand...
Click to collapse
Then you would know that as of now there won't be a fix for these issues you're having on non-tw roms using SafeStrap. I'm now confused on why you've even posted at all if you had known that.
FourPointedFreak said:
Then you would know that as of now there won't be a fix for these issues you're having on non-tw roms using SafeStrap. I'm now confused on why you've even posted at all if you had known that.
Click to expand...
Click to collapse
I'm confused as to why you posted. I told you these roms were all working fine for me and only recently have I had this problem. the gpe roms I'm using ARE tw based
deadenz said:
I'm confused as to why you posted. I told you these roms were all working fine for me and only recently have I had this problem. the gpe roms I'm using ARE tw based
Click to expand...
Click to collapse
You're talking about two different things here now - if you've cleared everything correctly, including dalvik cache, flashed your rom and the kernel then it should be fine. If it's not, I would find another download of your GPE 4.2.2 rom and ensure it's not your ROM that's causing problems. Just because there aren't immediate problems, doesn't mean problems can't occur later on - as you've noticed.
Or perhaps try all of the appropriate steps on another ROM slot for troubleshooting purposes.
FourPointedFreak said:
You're talking about two different things here now - if you've cleared everything correctly, including dalvik cache, flashed your rom and the kernel then it should be fine. If it's not, I would find another download of your GPE 4.2.2 rom and ensure it's not your ROM that's causing problems. Just because there aren't immediate problems, doesn't mean problems can't occur later on - as you've noticed.
Or perhaps try all of the appropriate steps on another ROM slot for troubleshooting purposes.
Click to expand...
Click to collapse
I've done all that. I've deleted and recreated the rom slot and flashed 4 different gpe roms to see if it was a certain rom causing the problem but no it was all of them.. that's why I'm so confused because these roms worked perfectly up until a few days ago. and like I said I just flashed shostock last night and I haven't had the problem. when you say flash my kernel you're talking about the mf3 zip that hashcode provided correct?
deadenz said:
I've done all that. I've deleted and recreated the rom slot and flashed 4 different gpe roms to see if it was a certain rom causing the problem but no it was all of them.. that's why I'm so confused because these roms worked perfectly up until a few days ago. and like I said I just flashed shostock last night and I haven't had the problem. when you say flash my kernel you're talking about the mf3 zip that hashcode provided correct?
Click to expand...
Click to collapse
Yes, that's correct. If you've done that - then it makes no sense. Seems you have done it all in order, accordingly. Hopefully Shostock doesn't fail on you also.
FourPointedFreak said:
Yes, that's correct. If you've done that - then it makes no sense. Seems you have done it all in order, accordingly. Hopefully Shostock doesn't fail on you also.
Click to expand...
Click to collapse
exactly! it makes no sense! I'm hoping someone can help out though..
with virginrom, there was a at&t csc file to flash after the rom. other than apn settings what is this file for?
deadenz said:
exactly! it makes no sense! I'm hoping someone can help out though..
with virginrom, there was a at&t csc file to flash after the rom. other than apn settings what is this file for?
Click to expand...
Click to collapse
I'm not familiar with the Virginrom, but I know that CSC files are written scripts, usually for automation. They work with with programs that support OLE. Seeing that it was carrier specific, I'd think that was used along the lines of APN settings within the ROM to some degree.
FourPointedFreak said:
I'm not familiar with the Virginrom, but I know that CSC files are written scripts, usually for automation. They work with with programs that support OLE. Seeing that it was carrier specific, I'd think that was used along the lines of APN settings within the ROM to some degree.
Click to expand...
Click to collapse
I even had a backup of one of the gpe roms that I had been running for almost a week with no problem and after restoring it to a completely new rom slot I still have the problem..
deadenz said:
I even had a backup of one of the gpe roms that I had been running for almost a week with no problem and after restoring it to a completely new rom slot I still have the problem..
Click to expand...
Click to collapse
That's bizarre. I would also suggest manually uninstalling SafeStrap and re-installing it but your Shostock hasn't had any problems yet. I couldn't think of anything else that would be posing a problem.
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
TweeXta said:
Hey guys.
I flashed the ktoonz kernel about a week ago and it works just fine except one thing: after a reboot my phone has forgotten my wifi password and i have to connect it again.
every time i restart the phone it's the same. it worked on stock kernel.
does anyone know this problem? it's quite annoying..
--edit--
i forgot to mention that i'm on stock samsung rom android 4.3 with touchwiz
and it's the international s4 (i9505).
Click to expand...
Click to collapse
I make the same mistake
Originally Posted by monkteo View Post
Hi,I just install the (I9505 XXUEMKE JB 4.3 Pre-Rooted STOCK ROM's) great rom and I thanks you for bring it here.
Question; after installed I try to flash a custom kernel (AOSP/TW/GE - 4.2/4.3 KT-SGS4 - MFD - KTweaker) and everything started to work wrong (no wifi,net fc,and many others)please tel my what kernel it's perfect for your rom and also if it's realy ned to flash a custom kernel ?
10X
A custom kernel is not required for these ROMs as they include the stock Samsung TouchWiz kernel which I'd say is probably the best kernel for the stock ROMs.
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
TweeXta said:
Isn't there a way to get WiFi working without flashing a new rom? I don't want to wipe the phone actually and the kernel is pretty nice I think.
It's pretty konservative with the battery and gives me extra power when I need it.
Isn't there a WiFi-fix or something like that?
Click to expand...
Click to collapse
WiFi-fix
Regards
Got the same issue with 4.4.2 and newest kernel version...
Tried changing build.prop line but with no success.
Is there any kind of help or a adequate wifi fix for kitkat?
Solved: wiped cache and dalvik and fixed permissions couple of times. Now it works
Sent from my GT-I9505 using xda app-developers app
I'm using GT-I9505 "international" with Paranoid Android 4.45 and successfully installed Ktoonsez kernel (3.4.94) with flashify app using Philztouch cwm recovery.
No problems at all, everything works, not tweaking by KTweaker, just raised 2.2GHz from PA's processor settings, ondemand as processor governor and Noop on i/o scheduler.
Tried few KTweaker profiles first but didn't find any good what understands to drop processor on deep sleep mode, almost all keeps it running all the time, PA's own handling with freshly installed KT-SGS4 kernel did best job for me.
Testing with profiles was frustrating thing, there wasn't way back to same situation what I got on fresh install.. few PA flashes later stand on "default".
Props to KToonsez (kernel), Christian Göllner (Flashify) and Paranoid Android.
I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
co.purp said:
I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
Click to expand...
Click to collapse
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
FingerBlastJ said:
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
Click to expand...
Click to collapse
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
elliwigy said:
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
Click to expand...
Click to collapse
Just giving help to those that need it based on my experiences. It just so happens that ive been on ricks rom and i had that issue. Nothing against rick and his rom but thats the situation and thats how i fixed my issues.
I believe when you are using safestrap you are supposed to flash the kernel modules to get Wi-Fi to work. Or am I mistaken about that?
Thanks guys, but I got it working by factory resetting from stock recovery.