As soon as i use any of the custom boot.img files the wifi stuffes up even with the wifi fix ... depending on what boot.img i flash i either get "obtaining ip address" indefinitely or "error"
The only ones that seem to work are the stock ones ...
Any idea why this is happening?
Thanks
Kris
Related
Edit:
Sigh. I should have seen it sooner... I was letting Kernel Manager download and flash the kernel. When booting into recovery and installing with cm, the kernels do not break the wifi
Hello,
It seems that all roms that I try, I have to use a static ip to connect to wifi... It hangs on "obtaining ip address from xxx" and then fails. Except for this rom.
Basic Debloat
One of the first ROMs released. Very basic with most of the bloat removed except the HTC stuff.
Developer: adrynalyne
http://forum.xda-developers.com/showthread.php?t=1000103
I've tried
1.12.605.6 Deodexed http://forum.xda-developers.com/showthread.php?t=1000448
1.13.605.7 Basic DeBloat,
standard http://forum.xda-developers.com/showthread.php?t=1054239
& deodex http://forum.xda-developers.com/showthread.php?t=1054786
The Perfect Storm http://forum.xda-developers.com/showthread.php?t=1006016
After installing I've tried a new kernel on all of them... Too many to remember. The "error" message goes away after reflashing the kernel but the phone will still not pull an ip from any network.
I've upgraded the fw in my router and extended the ip range. I have also tried 2 other open networks.
The Basic Debloat was the first rom I installed after rooting with this method... [ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
I have gone back to Basic Debloat and the wifi works perfectly again.
What did I miss? Why does my phone wifi hate all roms other than the Basic Debloat?
Ok, I just flashed to The Perfect Storm v1.4 and wifi works perfectly with this. When I try a different kernel (to oc) downloaded from Kernel Manager it stops working... So, it appears to be the kernel but how can I run this rom with an overclocked uv kernel?
Update: It was Kernel Manager that was breaking the wifi. All kernels work fine on wifi when flashed through cmr.
Sent from my ADR6400L using Tapatalk
I have searched all over for an answer to this problem but have not been able to find a solution that works...
I am currently on MIUI 1.7.29 on Verizon Fascinate and whenever I try to connect to my home WiFi, it gets stuck at "Obtaining IP address..." I have tried to odin back to ED05 4 times with a full dalvik/cache wipe and then MIUI flash in CWM 4 and I always get the same problem. The WiFi works fine after an odin back to ED05 and also DL09 stock. But as soon as I try to flash a MIUI rom over top (have tried 1.7.22 and 1.7.29), the WiFi becomes broken.
I also had the same issue when I previously tried out CM7. Also, I have tried FXR WiFi fix and rescue but it has never been able to fix it.
Any suggestions? Greatly appreciated!
It could be an issue with the iptable in the kernel. Try a different kernel and see.
artvandelay440 said:
It could be an issue with the iptable in the kernel. Try a different kernel and see.
Click to expand...
Click to collapse
I had this same issue & changing the kernel fixed it.
I just loaded the IP info(static) manually and it works.
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
sniperkiki said:
It seems I cant start Wifi on my mobilephone Evo 3D GSM
I followed 2 Tutorial, one to boot an boot.img and other to flash with some file bcm4329.
Non of it suceed.
After installing completly new rom, it happens again. LeeDroid
Click to expand...
Click to collapse
The tutorials sound to be on the right track.
Essentially, the bcm4329.ko file is the wifi module (drivers) for Wifi. This module file, bcm4320.ko, stored in /system/lib/modules/ must match the currently flashed kernel. If the wifi module and kernel do not match, you will receive this Wifi error.
Whenever a kernel developer compiles a new kernel, they must also compile the Wifi module, bcm4329.ko. The bcm4329.ko module file must be loaded into /system/lib/modules on the phone along with the custom kernel being flashed to the boot partition. If either of these files mismatch, Wifi will throw the error.
I walked through a lot of the logic in a separate thread troubleshooting this issue: WiFi - Error
Hope that helps!
So I've been on Ineffabilis since just about New Year's. 1.0, and on through 1.3 now.
Wifi Tether has always worked.
I use stock Kernels - always.
I recently got on Ineffabilis 1.3, and did not flash the Kernel (since I was already on the 2.01.605.11 kernel). Wifi tether works great. I use it all of the time.
So I go to turn on Wifi the other day (which I know worked on 1.1)... Error. I turn it on again.... Turns on, but 'Unable to scan for networks'.
Awkward.
So Troubleshooting 1:
Go to the Stock 2.01.605.11 Kernel and Wifi Modules thread. Flash the Wifi Modules. Flash the Kernel (again).
Still Error (won't turn on), then the second attempt, it 'turns on' (or appears to) and 'Unable to scan for networks'.
I say OK.
Troubleshooting 2:
Flashing Ineffabilis 1.3 again, and then letting it go into Bootloader, and flash its own Kernel. The kernel comes with the ROM (even though I think it's that same 2.01.605.11 version kernel - but just for the procedure). So Fresh flash of Ineffabilis 1.3. Then Flashing the kernel that comes with Ineff.
Boot up.
Same problem. Wifi gets 'error'. Then when I try to turn it on again, it's 'Unable to scan for networks'.
Am I stupid?
Should I flash wifi drivers and a kernel from 1.02 (original version, before OTA)?
Is my middle name Suzie?
I'm so confused here.
------------------------------------SOLUTION-------------
I did adb shell and deleted /data/misc and /data/local
then exit
then adb reboot
Problem solved!
I don't know what data in one of those two areas did it, but my wifi works now 100% without issue. I had already tried so much, I don't know which of the two had the problem in it, but neither one seemed to affect the data on my phone enough for me to notice, so I am happy.
You need to do a full wipe and install everything including the kernel. ROM does not like flashover.
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
dottat said:
I had this since the kernel auto-flash in this rom appears broken. You only need to flash the updated kernel with the updated libs for you to get past this.
here's the one you need- http://bit.ly/zCmQGk
flash that zip in recovery. Once it copies the new libs into place it will create a PH image and drop it onto the flash card. Reboot into hboot and allow it to update the kernel itself.
That will set you straight.
Click to expand...
Click to collapse
I appreciate that!
Still 'Unable to Scan for Networks'. I think I need to wipe something.
Upsetting. Time to finally wipe with 112 apps.
This would be the solution though. Installing the libs and kernel should be the fix. I must have some messed up data somewhere.
Turns on, Scans for networks, and says 'Unable to scan for networks' in a toast notification like every 5 seconds, and after a few times, it goes off then on again (unlimited cycle).
I added a network for a known wifi hotspot. Didn't add in the list!
It's my Data. As soon as I restore (just my data) from nandroid, and boot up, wifi is fried.
A completely fresh wipe and flash of ROM works great. I'm trying to wipe
/data/system (didn't work)
/data/data (didn't work - but the 'Weather lockscreen was blank and all kinds of interesting icons and widgets were missing.... yet WiFi still did its thing)
So it's not in /data/data or /data/system..... hhhmmmmmm. still hunting.
and then let the data folders sync back up after the phone boots up. Trying each folder inside /data until I find which one messed up my wifi. I'm determined!!
I get this in DDMS when I try to turn it on.
http://pastebin.com/DYFF0Ft3
FOUND IT!
I deleted (just to try it)
/data/misc
/data/drm/
/data/radio
/data/local
One of those did it. I don't know if I'm going to narrow it down, or just wipe those and leave the rest of my data.
So it was in /data/local or /data/misc
I deleted them both - wifi works! Awkward.
Thanks for the help either way, gentlemen!
so i noticed that my wifi also stopped working (in addition to my bluetooth). so i tried going back to RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe. i thought going back to stock would restore it, but no dice. i'd like to try deleting the folders you mentioned, is there any risk in doing this?
I have a Nexus 9 WiFi. I recently tried installing various custom ROMs but for each one the wifi wouldn't work correctly. It would always just stay "searching for wifi networks". For each of the ROM installs I would wipe all device partitions and then attempt the install using TWRP (3.1.0.0). I've attempted:
SlimRom flounder 6.0.1 2.1,
SlimRom flounder 6.0.1.1.18
SlimRom flounder 7.1.1 0.18.
cm13.0-20161218-nightly
cm14.0 20160910
Each had he same behavior, install went okay, went through setup but wi-fi never got past searching. I could specify one of my own networks SSIDs manually but with no luck. Wondering if perhaps wifi just happened to get hosed while doing all this, I flashed a stock image (volantis-ota-mob30d-1da7c803) and using this I was able to setup and connect to wifi so I know it's not the hardware. I was able to stay connected from various other devices at home with no issues. So it would seem to be an issue with using a custom ROM. With each of the custom installs I was able to turn WiFi on and a Mac address was listed, just didn't get beyond the "searching" step.
I've done searches on this and other forums and see issues with not being able to turn wifi on or connecting but getting dropped but I've not found a thread that has a fix for the device just searching.
Update: I wanted to also add that I've tried booting into safe mode with no effect.
Thanks in advance for any help you might be able to provide.
I'd reboot the router then see what happens.
Sent from my Nexus 9 using XDA-Developers Legacy app
jd1639 said:
I'd reboot the router then see what happens.
Click to expand...
Click to collapse
I've rebooted the router to no effect. There are also several other routers in my neighborhood that will shows up on my other devices but not the Nexus 9. I also don't think it's a router issue because flashed a stock rom back and the Wifi worked again which leads me to a software issue.
Thanks for the reply though. Keep 'em coming.
Fixed wifi with vendor.img
Got it fixed. I'd wiped everything in my various ROM flashes and after some more research found that I needed to reflash the vendor.img.
I downloaded the most recent image from google (developers.google.com/android/images).
I then unzipped that zip file, which contained several items in it.
In that group were a few other files, one of them another zip (image-volantis-n4f26x.zip), which I unzipped
This contained a vendor.img file
I copied that file over to the tablet and booted in TWRP
From TWRP I installed the image. It gave me a few target locations and Vendor was one, which I selected. I then cleared cache and dalvik
Once I booted up I was presented with a message about my vendor image not matching (or something to that effect) but my Wifi was now listing networks and able to connect
To get ride of the matching vendor image message, I booted back into TWRP and installed a zip I had downloaded at some point in the past for this (vendor-build-prop-fix-signed.zip)
Once I rebooted the message was no longer present and the wifi worked.
Hope this helps someone down the line.