I'd like to get the feedback from XDA masters on this issue I had.
Here's the steps that led to the problem.
Flashed ROM(Dr No V2), Decide i didn't like it after a day, the wifi was orking.
Entered 4ext recovery did a full wipe.
Used restore to flash my previous fully functioning ROM (EnergyROM-RCMIX)
Rebooted.
After reboot received the message in settings>...>Wifi "error"
I went through a bunch of steps, lots of reboots.
Try restore of an earlier backup - no fix
Reflashed from Zip the original RCMIX ROM, and fastboot flashed boot.img - no fix
Went into recovery and factory reset only. - no fix
Restored the last working ROM (RCMIX) and just fastboot reflashed boot.img
Still not fixed
More reading tried rename of the wpa_supplicant file. nope
One more fastboot flash of boot.img --
Then... turned on "Airplane Mode" for a few minutes. After turning it off Wi-fi "error" was gone and was able to turn it on.
The error changed to "unable to scan for networks"
Rebooted
Went back in and renamed wpa_supplicant.conf 1 more time.
reboot
When I enable wifi this time it scanned and connected.
I left some steps out, but they were just repeats of the ones I listed.
My question after all that is what went wrong?
Lots of threads about the problem but solutions seem to vary.
Is there something in there that I did incorrectly?
Aren't the drivers for the hardware located in the boot.img (as it contains kernel)?
Is there a better way to do this?
trying to get better at this; Insights, advice, comments appreciated.
I do need to get familiar with logcat.
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
bananagranola said:
Clean flash a stock-ish ROM like Android Revolution HD. Is the problem still there?
Click to expand...
Click to collapse
Wifi seems to be stable now. Running the restored RCmix. Rebooted a couple times and no issues. I'm interested in gaining some insight into the source and solution of the problem. My next step was to run a stock RUU I have, but your suggesting something close to stock might have worked?
Why didn't a re-flash of the previously functioning ROM (RCmix, zip on sdcard & fastboot boot.img) fix the issue? I did full wipes each and every time. Even full wipes before doing Restores from recovery. Restore should be a straight forward process from recovery, right?
The problem started right after a restore, and I'm not sure what step it was that fixed it. The last thing was renaming the wpa_supplicant.conf file. I left out the part where my restored ROM got stuck in the boot animation. There was something going on with the boot loader. Re-flashing boot.img fixed it.
But the wifi...? Any thoughts.
I'm a little hesitant to flash another ROM for fear of losing wifi again. I use it a lot.
Cremnomaniac said:
I'm looking for some intelligent feedback. Any thoughts on my OP?
Click to expand...
Click to collapse
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
bananagranola said:
I already answered you...and also, why are you renaming wpa_supplicant.conf? Are you making any other changes?
Click to expand...
Click to collapse
Thanks, but your first comment offered a possible solution, and solutions are important, but as indicated in the title it had been solved. There aren't any comments on the questions I specifically asked. At the least, I was hoping that someone with greater experience could provide insight into the possible causes of loss of wifi (steps, incompatibility of ROM, freak thing, etc.) so I can avoid it in the future.
The renaming of wpa_supplicant.conf came from threads in the XDA forums where similar wifi problems had been encountered. It was a solution with zero risk.
Here: http://forum.xda-developers.com/showthread.php?t=1965812&page=3
Here: http://forum.xda-developers.com/showthread.php?t=1662805
Here: http://forum.xda-developers.com/showthread.php?t=1988190&highlight=wifi+error
Here: http://forum.xda-developers.com/showthread.php?t=703105
If I made any other changes I would mention it. I can see that you may be the only one monitoring this forum, which is unfortunate. You exhibit a lot of patience, but unlike some of the questions posted, I do the research and read directions carefully. The reason I ask questions is to learn, not to have my hand held. And someone posting "ddpo" is a waist of bandwidth. If no one has any comments to my questions, we'll leave it at that.
Because stock is most stable, flashing a stock-ish ROM will reveal whether the problem is a hardware one or a software one. If the problem still exists on stock, your hardware is probably messed up. If the problem doesn't exist on stock, something is up with your ROM. That is why flashing stock is still relevant: for the first step in diagnosis. Other than that, you can look into getting S-Off and flashing an updated radio, but that's up to you.
And I already reported the "ddpo."
Hello, I rooted my Nexus 4 as a school course work but encountered a problem that I can't find a fix for. My problem is that when I try to flash a zip file for any kernel, it seems to install it successfully but when the phone reboots, nothing seems to have changed in exception to the screen tearing. What am I doing wrong or not doing?
I've searched, read, downloaded a lot of programs but I have been unable to fix a stupid mistake I made earlier which was flashing the wrong firmware on my MK802iv. As a result the WiFI and Bluetooth switches off immediately after switching on regardless of what ROM I install. I've tried to flash stock and other ROM's but the same problem with WiFi and Bluetooth remain.
I can not get RKAndroidTool to run and I can not set up a custom recovery. I'm really struggling to find a way to flash a custom kernel but I don't think that will fix the problem. I suspect that if I could get into a custom recovery and Fix Permission this could alleviate the issue. I'm running out of ideas and can not find a solution. Any help would be greatly appreciated. Thank you.
Edit: Probably the wrong forum for this question.
JagSem said:
I've searched, read, downloaded a lot of programs but I have been unable to fix a stupid mistake I made earlier which was flashing the wrong firmware on my MK802iv. As a result the WiFI and Bluetooth switches off immediately after switching on regardless of what ROM I install. I've tried to flash stock and other ROM's but the same problem with WiFi and Bluetooth remain.
I can not get RKAndroidTool to run and I can not set up a custom recovery. I'm really struggling to find a way to flash a custom kernel but I don't think that will fix the problem. I suspect that if I could get into a custom recovery and Fix Permission this could alleviate the issue. I'm running out of ideas and can not find a solution. Any help would be greatly appreciated. Thank you.
Edit: Probably the wrong forum for this question.
Click to expand...
Click to collapse
The MK802IV changed wifi chips mid-production. If you go to the official RKM site to their download page check your serial number with the stock ROMs to make sure you get the right one.
I am running CM11s XNPH05Q now after flashing my phone due to a soft bricking issue. However, I do not have bluetooth now at all. It will not turn on. Anything to do with bluetooth in the system apps are gone! I even re-flashed to no avail. Has anyone experienced this? Does anyone have a solution? I would be most grateful. Thanks!
Edit: Nevermind. I just used Heisenberg's guide on how to flash a stock kernel and everything is good!
Hopefully one of you brilliant people can tell me this.
I have a common problem in that when I install custom nougat roms, my wifi starts doing the 'internet not available' and connect/disconnect thing.
I have tried all the methods I've found to resolve this but to no avail.
The interesting thing is there is one set of custom roms that work fine for me. Just one, and I have tried most if not all of them.
Of course the stock rom works, rooted or not. But the strange thing is that the Gensys Experience roms all work fine.
So, my question is what is specifically different about those roms thst make them work? I've tried to delve into various config files to try to identify differences and have just ended up hopelessly baffled.
Anyone know?
Thanks in advance to anyone who can help..