I have rooted my mojo with towelroot v1, installed flashify, installed TWRP, flashed CM 12.1, flashed gapps ARM 32 bit 5.1 micro, and rebooted.
The wi-fi won't turn on. It says "Turning on Wi-Fi.." and doesn't do anything. I can skip but I am also unable to turn it on in the settings. It was working before when I was struggling with finding the right gapps.
Anyone encounter this before?
Phoenix4848 said:
I have rooted my mojo with towelroot v1, installed flashify, installed TWRP, flashed CM 12.1, flashed gapps ARM 32 bit 5.1 micro, and rebooted.
The wi-fi won't turn on. It says "Turning on Wi-Fi.." and doesn't do anything. I can skip but I am also unable to turn it on in the settings. It was working before when I was struggling with finding the right gapps.
Anyone encounter this before?
Click to expand...
Click to collapse
Yes, when it happened to me it was caused by another wi-fi device being too close to the MOJO. Seems this cute li'l box is very sensitive to RF interference.
Fixed
kevinthefixer said:
Yes, when it happened to me it was caused by another wi-fi device being too close to the MOJO. Seems this cute li'l box is very sensitive to RF interference.
Click to expand...
Click to collapse
Thank you, I thought I just had flaky hardware.
same issue here seems like a bug in cm12.1, cause I didnt have the issue in stock firmware
phantomette said:
same issue here seems like a bug in cm12.1, cause I didnt have the issue in stock firmware
Click to expand...
Click to collapse
Yes I suspected the same. But I found the problem can be minimized by closing all the apps before you reboot. ES File Explorer seems to be particularly problematic.
Related
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.
Wifi stuck on 'turning on'.. My Galaxy S4 won't let me enable Wi-Fi.
i had been using influes v4.0 rom and everything had been working great like a month until a week ago, when suddenly wifi stopped working
What now?
Using official XXUHOD4 framework.
android 5.0.1 lolipop
what Ive tried:
flashing another roms.
flashing paraman.bin- http://forum.xda-developers.com/showpost.php?p=52989594&postcount=4899
Delete wpa_supplicant.bak.conf via root explorer
Might be that the WiFi antenna got disconnected. Or it completely broke.
GDReaper said:
Might be that the WiFi antenna got disconnected. Or it completely broke.
Click to expand...
Click to collapse
bluetooth and hotspot are fully working
not using the same antenna?
darixtorento1 said:
bluetooth and hotspot are fully working
not using the same antenna?
Click to expand...
Click to collapse
I don't know. But when something worked fine before and then, for no reason, stops working, then it might be the result of a hardware problem.
GDReaper said:
I don't know. But when something worked fine before and then, for no reason, stops working, then it might be the result of a hardware problem.
Click to expand...
Click to collapse
sometimes I click on 'hotspot' and it turns off wifi
so I play with this..
turn on hotspot turn it off, then reboot the device and then wifi is working for like 10min and automatically tuns off and it stars again..
its barely working thats why I thought it might be system error.
darixtorento1 said:
bluetooth and hotspot are fully working
not using the same antenna?
Click to expand...
Click to collapse
darixtorento1 said:
sometimes I click on 'hotspot' and it turns off wifi
so I play with this..
turn on hotspot turn it off, then reboot the device and then wifi is working for like 10min and automatically tuns off and it stars again..
its barely working thats why I thought it might be system error.
Click to expand...
Click to collapse
System error should disappear when you flash another ROM.
Did you clean flash or dirty flash?
Also, if the problem persists I suggest flashing a stock ROM (clean flash) and see if it fixes Wi-Fi.
GDReaper said:
System error should disappear when you flash another ROM.
Did you clean flash or dirty flash?
Also, if the problem persists I suggest flashing a stock ROM (clean flash) and see if it fixes Wi-Fi.
Click to expand...
Click to collapse
when it happened in Influes rom, I tried flashing Ale95 Note5 Port Milestone v5.1
of course deleted cache preload and full wipe.
wifi still didnt work so i flashed official android 5.0.1 via odin- didnt help
flashed again and deleted again cache data everything didnt help
now received official update and installed it too- didnt help
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
Hello there!
My boyfriend is experiencing random reboots on his OnePlus 2. (He doesn't have an account here, so that's why I'm writing instead.)
He is running the latest LineageOS, though has had the reboots since the build from Jan 31st. He has root active and is also running the latest Boeffla Kernel.
Weirdly enough we can't pinpoint what is causing the reboots and they seem to happen more frequently in the mornings (when he's at work) than in the afternoons/evenings (when he's home). This morning alone he had four reboots shortly one after another.
It also seems to happen more frequently when the WiFi is turned on but not connected. When the WiFi is turned off completely it also happens, but not so often. When WiFi is connected, the reboots seem to stop?
He suspects it has something to do with LineageOS, as he was on OxygenOS previously (before the official LOS builds got released) and didn't have any issues. I found in the forums here it could have something to do with the firmware version 3.5.6 and reverting back to 3.1 or something would stop the random rebooting? (Unfortunately I have found nothing on how to determine your firmware version, but his Baseband version is MPSS.BO.2.6.2.c1-00072-M8994FAAAANAZM-1.82470.1, if that helps?)
So I just wanted to ask if anybody is experiencing the same and if you can confirm the firmware change helps or if you found any other solutions for this?
Thanks a bunch!
Confirmed for me! Changing back to 3.1.1 firmware stopped the reboots
foomanjackel said:
Confirmed for me! Changing back to 3.1.1 firmware stopped the reboots
Click to expand...
Click to collapse
Can you just flash the 3.1.1 firmware or do you need to take any precautions? Anything you need to know before flashing?
Inutsume said:
Can you just flash the 3.1.1 firmware or do you need to take any precautions? Anything you need to know before flashing?
Click to expand...
Click to collapse
Yeah just go to twrp and flash the 3.1.1 firmware.
foomanjackel said:
Yeah just go to twrp and flash the 3.1.1 firmware.
Click to expand...
Click to collapse
It seems to have done the trick. Thank you very much!
Glad if I helped. It was bugging me for awhile as well, although I coped with it by turning off WiFi when I was away from home. Never rebooted for me if I turned it off, but this is much better. I have no real need for volte anyways, so no loss here.
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Prob a bug. My n5 had similar issue.... Turned out board was bad. I think the wifi chip had a broken solder joint. Because it would say "turning on" and never complete. I reflashed a hundred ROMs, and other recoveries including CAF. I think this happens to a lot of devices after they've been dropped 30 or 40 times there are small micro fractures each time until it causes a break in the connection somewhere.
But you just gave me a good idea I think I'm going to try to Reflow the board in the old oven
Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.
jhs39 said:
Did you have the problem before flashing Lineage? If not its almost certainly a bug in the rom. If they have a support thread you could try getting help there or you could flash a different rom and see if the problem persists.
Click to expand...
Click to collapse
sorry it took me so long, still having the problem, and no, it was perfectly fine until lineage.
This has happened to me about 7 or 8 times running 7.1.1 lineage. Look and see what your mac address is under configure wifi, mine changes to 02:00:00:00:00:00 when this happens to me. I have found posts about the problem but no real solution. The only way I have gotten it working again is by wiping the data partition and doing a clean flash, or flashing a backup I made while it was working. It drives me mad, I thought it might be a hardware problem at first because it started with a replacement device, but I feel like it must be software as I can fix it with a clean flash.
Sent from my Nexus 6P using Tapatalk
Etheralrealm said:
Hi, I'm running lineage os, I can't turn wifi on, it is just saying "Turning WiFi on"
Click to expand...
Click to collapse
I doubt this is a bug. Are you on the latest nightly? If you are running TWRP, start by wiping both dalvik and cache and reboot. There are LOS dedicated forums here, and this type of Wi-Fi issue would be a complete bust and I just don't see it. It could also be with how you installed LOS. The instructions are clear about fully wiping the device beforehand. I have been running LOS on my N7 for months, updating with weeklies and have never had a WiFi issue. Reddit has some decent forums you could ask around in as well.
ive been running it on my device since about november, worked until about a month ago, just been using data, tried wiping and i did a full wipe when i installed it. I went back to my january 30th build (oldest build i still had on my pc), running fine. No problems.
Here is the January 30th build, ready to flash with TWRP. Hope you have the same luck as me.
https://drive.google.com/file/d/0B9cTDZV2zbsvelUyMHJSXzlSU3c/view?usp=sharing
Cause I'm not taking chances I'm NOT responsible for any damages.