Related
I have downloaded Handy Sniffer 1.6 Demo version to my HTC Vox/S710.
The WiFi hardware is: TNETW1251.
The handysniffer website quotes: Promiscuous mode for some TNETW1251 WiFi adapters.
So when i select extended mode it gives me the anomalies error, which seems to mean that the unofficial promiscuous mode is not supported.
When i enable the official promiscuous mode, it only sniffs local packets, not from other pc's. Why is that?
Hi Rubberducky,
I am developer of HS.
// Handy Sniffer
>> So when i select extended mode it gives me the anomalies error,
>> which seems to mean that the unofficial promiscuous mode is not supported
Is not YET supported,
Send your "Windows\tnetw1251.dll" file to me.
Maybe we will have a luck.
// ARP Spoof
Try to send "arp-req.bin"/"arp-reply.bin" (possibly edit some fields) example packets from "Handy Sniffer\raw" folder. Some built-in WiFi adapters permit sending of packets with foreign source MAC address (-> you can configure valid arp packet). On target host run e.g. WireShark sniffer or see current ARP table...
The file tnetw1251.dll doesn't exist in \Windows on my HTC Vox\s710.
It is possible driver has name "tnetwln.dll" but it is a system file (hidden) and I think it has ROM attribute. If you can extract it I'll ready to analyse it...
I would gladly try to extract it, only i have no idea how i would go about doing this...
Try the program from GreateVK:
http://forum.xda-developers.com/showthread.php?p=1571715
If you have success send me file to "[email protected]".
I'm having problems extracting the file. Rom Extractor seems to be developed for Pocket PC, i have a Smartphone.
But i'll keep trying.
If the extended mode would work in my VOX, would that mean that i can intercept all the packets on the network (Like ARP spoofing), or only packets that are sent to my device?
You can capture ALL USER packets an Access Point (re)transmits in network: broadcast, multicast, directed and with foreign DestMacAddr.
I sent you the file, and i'll also attach it here. Maybe other people need it too.
Here is the file
So? Is that all?
Hi,
I tried multiple builds, but wifi didn't work at any of them. I found out that most probable reason is inabilty to get MAC address for wifi.
dmesg:
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
I tired to modify startup.txt, but no results. I found that similar issue was resolved for other htc devices (tilt 2, touch pro 2) by correction of wifi-nvram.txt. I couldn't find that file on builds for hd2.
It would be greate if anyone could you say which file is responsible for setting up MAC address for wifi.. Or what can I try else..
Thanks you!
What radio, wm versions and android versions have you tried? I've tried numerous builds and wifi has worked for almost all of them (if not all). I've had issues with data working but usually not wifi.
Wifi has worked on every build I've used which is 90% of the builds on xda
Sent from my HTC HD2 using XDA App
do u know what a radio is ?? I thought so ... search the forum for it and installl and use the latest then try again.
My hd2 is T-mobile US version
My radio is 2.15.50.14
Android build is MDJ FroYoSense -=Revolution=- 1.6 (tried with built in kernel and hastarin's one)
just in case, ROM build is 3.14.531.1 from T-Mobile, but I also tried Miri_Steve0007_Elegancia_V5.0_FINAL with the same results.
Actually I asked a person who doesn't have wifi problems to give me his firmware versions (rom, radio) and tried them by myself on the same android build he has. Results are the same: wifi doesnt'work.
Under WM wifi works good. Here is a link to the similar problem resolved for touch pro 2, tilt 2 and other devices: http://forum.xda-developers.com/archive/index.php/t-695230.html
Thanks!
az_registration said:
My hd2 is T-mobile US version
My radio is 2.15.50.14
Android build is MDJ FroYoSense -=Revolution=- 1.6 (tried with built in kernel and hastarin's one)
just in case, ROM build is 3.14.531.1 from T-Mobile, but I also tried Miri_Steve0007_Elegancia_V5.0_FINAL with the same results.
Actually I asked a person who doesn't have wifi problems to give me his firmware versions (rom, radio) and tried them by myself on the same android build he has. Results are the same: wifi doesnt'work.
Under WM wifi works good. Here is a link to the similar problem resolved for touch pro 2, tilt 2 and other devices: http://forum.xda-developers.com/archive/index.php/t-695230.html
Thanks!
Click to expand...
Click to collapse
you may have forgotten to copy bcm drivers when you changed kernels and that can kill your wifi.
malaeus said:
you may have forgotten to copy bcm drivers when you changed kernels and that can kill your wifi.
Click to expand...
Click to collapse
No, I have updated bcm4329.ko as described in readme file for kernel. Also I compared dmesg output and adb logcat for different kernels: they look similar.
logcat says: "Failed to disable WPA in the driver" while dmesg says "dhd_preinit_ioctl: Can't get MAC address, errno=-110" for both the kernels..
Thanks!
Just tested with different radios.. Results are still the same..
If wifi wouldn't work in WM, I though that it is a hardware problem.
Any thoughts are welcome!
az_registration said:
There is a file (startup.txt) which allows to specify mac adderss in 'Android' folder. Did you mean that one, or mac address might be specified in some other way?
Click to expand...
Click to collapse
Yes, but that's only there if you are using MAC filtering in your access point, or you're using multiple Smartphones with the same Android Build.
Just as a test to determine if it's in any way related to security settings in your Access Point, you could try to make your access point unprotected.....so NO WEP or WPA protection, SSID visible, etc.
If that doesn't work either, then I'm lost
Are you using MAC Filtering in your Access Point/Router ??
First time I tried to connect to my Access Point with Android, it didn't work either....untill I realised that the MAC Address on Adroid is NOT the MAC Address of the HD2. When I allowed the MAC Address of the Android Build on my Access Point I had no more trouble connecting, and my WIFI has worked ever since......
Be carefull however, different Android Builds use different MAC Addresses, so when you try a new Android Build you might experience the same issue.
Newer Kernels have an option to specify your own MAC Address during startup of Android.
Hope this helps.
Thank you for answering!
Pappagallo said:
Are you using MAC Filtering in your Access Point/Router ??
Click to expand...
Click to collapse
No, MAC filtering is not used. At least at one access point.
Pappagallo said:
Newer Kernels have an option to specify your own MAC Address during startup of Android.
Click to expand...
Click to collapse
There is a file (startup.txt) which allows to specify mac adderss in 'Android' folder. Did you mean that one, or mac address might be specified in some other way?
I did some more investigations and it seems that the problem might potentially be in wifi timeout settings, because there is a message in log (dmesg).
wlan: dhd_bus_rxctl: resumed on timeout
I downloaded kernel's sources to find out if this is the reason. Again, it is very weird, because wifi works in windows mobile.. Perhaps WM uses longer timeouts..
Another strange dmesg line is
wlan: firmware version: ver
perhaps wifi hardware has not been initialized correctly.. Just in case, below is related set of dmesg lines:
<4>[ 320.937774] wlan: wifi_set_power = 1
<4>[ 320.937835] htcleo_wifi_power: 1
<4>[ 321.236083] wlan: wifi_set_carddetect = 1
<6>[ 321.236114] htcleo_wifi_set_carddetect: 1
<7>[ 321.236145] mmc0: card_present 1
<6>[ 321.236145] mmc0: Slot status change detected (0 -> 1)
<4>[ 321.239715] wlan: Dongle Host Driver, version 4.218.204.2
<7>[ 323.794219] mmc0: queuing CIS tuple 0x91 length 3
<6>[ 323.794372] mmc0: new high speed SDIO card at address 0001
<4>[ 323.810180] wlan: DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 326.055175] wlan: dhd_bus_rxctl: resumed on timeout
<4>[ 326.055297] wlan: firmware version: ver
<4>[ 326.066162] wlan: Return_dpc value is : 0
<4>[ 326.066314] wlan: stop poll
<4>[ 328.065277] wlan: dhd_bus_rxctl: resumed on timeout
<4>[ 328.065399] wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
<4>[ 328.065490] wlan: dhdsdio_probe: failed
Thanks again.
Something went wrong when quoting a part of your question concerning the startup.txt file, so for some strange reason my reply is on the 1st page...(at least when I'm looking at your thread).....
Anyway, the MAC Address you can specify in the startup.txt file can be used when you ARE using MAC filtering and/or you have multiple smartphones using the same Android Build.....so you don't have duplicate MAC Addresses on your network.....
As I'm not a developer, I'm not able to help you with your debugging lines....however, if you want to be sure that it's not some kind of security setting, you could try to remove all security from your Access Point, so NO WEP or WPA, SSID visible etc.
If that doesn't work either, then I'm lost
Only time I didn't get a WIFI connection was because of the MAC Filtering in my Access Point. When that was corrected I never had problems getting a connection on WIFI.
Good luck.
Pappagallo,
I tried to turn off all security, but no effect. Anyway, thank you for the advice I just don't know to to try else...
Another suspicious line in dmesg is wlan: firmware version: ver.
It seems that wifi is not initialized correctly in Android... It would be interesting to see this line for devices with working wifi.. But to do that terminal emulator or android sdk are needed..
Can anybody show dmesg and logcat when wifi is turned on? I would be very appreciated.
Thank you in advance!
the same problem
Exactly the same problem, and I've experienced most Roms and when I return to the Windows system, the Wi-Fi works.
We need a real expert.
any help
I noticed that this problem devices in T-Mobile (TMOUS - PB81120 SS-B3)
Hi, guys
After flashing NAND Android, I found that the wifi mac address is : 00:11:22:33:44:55, and the BT mac address is :50:C3:00:00:00:00, any one can tell me how to change them ?
thx.
I've seen these possible answers:
Try changing the startup.txt from
Code:
set cmdline "nand_boot=0"
set cmdline "bt.mac=00:11:22:33:44:55 wifi.mac=00:12:23:34:45:56"
boot
To
set cmdline "rel_path=Android nand_boot=0"
boot
and
Code:
#Mdeejay FroYo Revolution v. 1.7
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "wifi.mac=00:11:22:33:44:55 bt.mac=00:11:22:33:44:55 nand_boot=0"
boot
NOTE: You need to repalce the 00:11:22:33:44:55 with the real MAC address or any of your choice...but if you're like me that have *ALL* security features turned on on your wireless router (MAC FILTERING, HIDE SSID, WPA2, 802.1X) then you need to use the real MAC address..
Click to expand...
Click to collapse
Problem is, both solutions mention startup.txt, which I simply do not see in the NAND setup folder...
Both are found in the MDJ FroYo Revolution v.2.1 threat...
I have not tested them, I would like someone to confirm this is working, someone who knows more than me...
Any help and opinion on this topic welcome...
The post above only applies to SD, NOT NAND. I want to know how to change these too
bump
Thanks
I want to find out too!
How can I spoof my mac address?
some bloke has the same mac addr as me @ the uni so I need this or I can't get online.
The uni defined that you have to REG your MAC first;
so that f¨¨king idot regged first, and now I am cut off because of him.
Anyone an idea where in nand the BT & MAC settings are stored? can this be changed with root explorer? or with cmd line?
HectiQ said:
I want to find out too!
How can I spoof my mac address?
some bloke has the same mac addr as me @ the uni so I need this or I can't get online.
The uni defined that you have to REG your MAC first;
so that f¨¨king idot regged first, and now I am cut off because of him.
Anyone an idea where in nand the BT & MAC settings are stored? can this be changed with root explorer? or with cmd line?
Click to expand...
Click to collapse
download the terminal emulator free from the android market.
-go to your setting and find out what your mac address is. write it down.
-open it
-if theres a question mark at the left of the cmd line write "su", if theres a # you can skip it
-write "ip link show"
-search for the expression having your mac address. at my phone it was eth0
-write "ip link set eth0 address 11:22:33:44:55:66" or any other mac
-write "ip link set eth0 broadcast 11:22:33:44:55:66" or any other mac
now your mac should be changed. remember that this method doesnt work at every phone, at mine it didnt work.
i read some about linux terminals to find that out, pls dont post things like "you stole it blabla".
hope that it works for you,
sallal
Correct me if I'm wrong but the Wifi Mac address has been fixed long ago, I have (I suspect) my real mac address on my phone no matter what rom I use, its the BT that I cant find how to change, even though I have a kernel with the solution but no one willing to help.
And in NAND versions of Android, you change your WIFI Mac address by changing the value in the calibration file, open it as text and change to what you need.
modules name changed. Now run stable
Awesome
I will merge this in and if all goes well, will start gutting the areas I could not before.
Ill report back.
Great work!
pershoot said:
Awesome
I will merge this in and if all goes well, will start gutting the areas I could not before.
Ill report back.
Great work!
Click to expand...
Click to collapse
dhd.ko filename modified to bcm4329.ko
put in /system/lib/hw/wlan
I tried many ways, last modified module name, unexpectedly successful, it is funny.
Chenglu said:
I tried many ways, last modified module name, unexpectedly successful, it is funny.
Click to expand...
Click to collapse
it appears to be working well from initial observation.
i too outputted the module as dhd, but it still froze up, no matter which method i took.
can you please share the other changes that you have made from the last posting?
ill diff things out now, upgrade to the latest and commit.
thx. great work!
pershoot said:
it appears to be working well from initial observation.
i too outputted the module as dhd, but it still froze up, no matter which method i took.
can you please share the other changes that you have made from the last posting?
ill diff things out now, upgrade to the latest and commit.
thx. great work!
Click to expand...
Click to collapse
i did notice it disconnect while being idle for a while. but that's ok.. that could be coincidence and/or an isolated case with my setup.
I use a new version of the driver code, modify and compiled, try several Dflags, the result is the timeout or hardlock, so I deleted all code.
Then, I started from scratch,redownload code from http://nv-tegra.nvidia.com/gitweb/?p=android/platform/system/wlan/broadcom.git, Made a small change, even successful.........
upgrade complete.
<4>[ 3654.777016] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 3654.979564] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223
.1
<4>[ 3655.177291] wlan0: Broadcom Dongle Host Driver mac=--:--:--:--:--:--
<4>[ 3655.187516]
<4>[ 3655.187527] Dongle Host Driver, version 4.218.248.18
<4>[ 3657.545885] STA connect received 1
it was the combination of your makefile flags.
let me monitor this some more, and if all holds stable, ill post src to my git.
then ill work towards bringing this section (removing pullup, keeping sdio lines high, and possibly going towards wifi abstraction and not gpio reset) forward.
the upgrade seems stable to me!
https://github.com/pershoot/gtab-2632/commit/c7ba24f773539dc986b0a0b532e83d1272fd66b4
pershoot said:
the upgrade seems stable to me!
https://github.com/pershoot/gtab-2632/commit/c7ba24f773539dc986b0a0b532e83d1272fd66b4
Click to expand...
Click to collapse
good work...
Chenglu said:
good work...
Click to expand...
Click to collapse
you as well
Is possible to make this file able to be flash? Prefer to do it that way so I can make sure I don't mess up nothing
lilgotti56 said:
Is possible to make this file able to be flash? Prefer to do it that way so I can make sure I don't mess up nothing
Click to expand...
Click to collapse
yes. flash my kernel.
Thanks, worked great for my kernel as well (2.6.32.9) but still can't enable IPv6. It would just give me an error on wifi. Any ideas?
http://nv-tegra.nvidia.com/gitweb/?...9;hb=900f1defbe1f39ca6af8356521961c249174f304
Update to FW version 4.218.248.6
Code:
<4>[ 403.288667] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 403.466861] Firmware version = wl0: Sep 15 2010 14:22:42 version 4.218.248.6
<4>[ 403.671056] wlan0: Broadcom Dongle Host Driver mac=00:27:13:f7:c6:58
<4>[ 403.679611]
<4>[ 403.679621] Dongle Host Driver, version 4.218.248.18
<4>[ 405.984640] STA connect received 1
<7>[ 414.933316] wlan0: no IPv6 routers present
Chenglu said:
http://nv-tegra.nvidia.com/gitweb/?...9;hb=900f1defbe1f39ca6af8356521961c249174f304
Update to FW version 4.218.248.6
Code:
<4>[ 403.288667] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 403.466861] Firmware version = wl0: Sep 15 2010 14:22:42 version 4.218.248.6
<4>[ 403.671056] wlan0: Broadcom Dongle Host Driver mac=00:27:13:f7:c6:58
<4>[ 403.679611]
<4>[ 403.679621] Dongle Host Driver, version 4.218.248.18
<4>[ 405.984640] STA connect received 1
<7>[ 414.933316] wlan0: no IPv6 routers present
Click to expand...
Click to collapse
Hi, pushed fw_bcm4329.bin and fw_bcm4329_apasta.bin to /system/lib/hw/wlan but I still end up with 4.218.233.1 any ideas?
If your using what's at nvidia for. 32 line for broadcom, that's the version you'll be on (what shipped with our tabs (233.1)). So that is correct what you have.
If your using my source (which I modified from AOSP; check git for mods/details done for our specific platform; check vision-2632 repo for further changes done to AOSP src), then you will get the latest version published to date (248.18).
You can test both sets of firmware independently to see which plays better with our specific tabs and specific use case(s).
Chenglu, all is well with FW update so far?
Plays ok with our specific hardware?
Ill play as well when I get a free minute and report back of any anomalies.
Good team work!
pershoot said:
If your using what's at nvidia for. 32 line for broadcom, that's the version you'll be on (what shipped with our tabs (233.1)). So that is correct what you have.
If your using my source (which I modified from AOSP; check git for mods/details done for our specific platform; check vision-2632 repo for further changes done to AOSP src), then you will get the latest version published to date (248.18).
You can test both sets of firmware independently to see which plays better with our specific tabs and specific use case(s).
Click to expand...
Click to collapse
Thanks, that cleared it up Looks like I got my Firmware up to 248.6 but my dongle driver is stuck at 233.1. I'll try IPv6 with this and see how it goes.
GOT IT!! Working IPv6 with good range
For a month I've been having issues with my phone, because the wifi stopped working. It wouldn't turn on (turning dark green, then off again). Since I didn't want to root my phone, I was waiting on the new Samsung update (4.4.2), hoping that it would fix the problem. Yesterday the update went online and I was able to complete it, but the wifi remained off.
In the meantime I was looking for ideas on how to solve the issue (turning on and taking out the battery, taking out the battery for a longer time, etc.) but nothing helped. I saw a post (http://forums.androidcentral.com/sa...-my-galaxy-s4-wont-let-me-enable-wi-fi-4.html), that seemed to be plausible and I thought I would give it a try.
Yesterday I rooted my phone (with Odin and CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5), loaded the newest SuperSU-app and was able to actually see, what the problem was. Logcat showed this, when turning wifi on:
03-05 21:52:36.347 I/WifiManager(1215): setWifiEnabled : true
03-05 21:52:36.347 I/WifiService(830): setWifiEnabled: true pid=1215, uid=10266
03-05 21:52:36.357 E/WifiHW (830): ##################### set firmware type 0 #####################
03-05 21:52:36.357 I/WifiHW (830): module is murata FEM1
03-05 21:52:36.357 E/WifiHW (830): ==========[WIFI] Station firmware load ===========
03-05 21:52:36.357 E/WifiHW (830): ==========[WIFI] MURATA FEM1 MODULE ===========
03-05 21:52:57.207 E/WifiHW (830): return of insmod : ret = -1, No such device
03-05 21:52:57.207 E/WifiStateMachine(830): Failed to load driver
03-05 21:52:57.247 E/WifiStateMachine(830): sendErrorBroadcast code:10
03-05 21:52:57.247 D/STATUSBAR-NetworkController(1215): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
03-05 21:52:57.257 E/WifiController(830): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
03-05 21:52:57.267 I/WFMonitorService(4771): WIFI_STATE_UNKNOWN
This happened also after deleting or renaming the wpa_supplicant.conf (both in system/etc/wifi and in data/misc/wifi) and restarting the phone. I also tried deleting or renaming the whole wifi-folder (in both directories), without success. Renaming the file worked, but it wasn't recreated upon restart, which seemed pretty strange. Upon renaming the wifi-folders only one was recreated (the one under data/), but the .conf-file was still missing. I continued getting the error message cited above.
I searched for the "device not found" issue and found the following thread (http://forum.xda-developers.com/showthread.php?p=50535766), but this didn't help either. Even setting permissions for the files and folders that I thought would be important didn't help.
Today I wiped my phone clean in recovery and tried flashing the stock firmware I9505XXUFNB8_I9505OXAFNB8_I9505XXUFNB8_HOME.tar.md5 on, but wifi was the same. I even tried flashing only the modem with files I found here: http://d-h.st/users/DjeMBeY/?fld_id=15780#files. Something changed, because when I turned wifi on it turned itself off right away, so it didn't last in the dark green status for a few seconds as it used to. I also recall seeing this error message, as opposed to the one above and it was running slow with different other errors (no sound, apps crashing, etc.):
E/WifiHW ( 793): return of insmod : ret = -1, Exec format error
I really don't know what to do with it anymore. Since bluetooth is working I don't think it is a hardware issue and I should be able to resolve it somehow. Since I rooted it I don't know if I can use the warranty and I didn't want to send it in for 2 weeks.
I would be very happy about any ideas on how to resolve this issue. I hope there enough information. Thanks in advance!
Hi, a have some problem...
Flash latest bootloader and modem, that should solve your problem, worked out on my case, but KNOX will be triggered
qtwrk said:
Flash latest bootloader and modem, that should solve your problem, worked out on my case, but KNOX will be triggered
Click to expand...
Click to collapse
Could you be a bit more specific, please? Maybe a link?
Thanks
MisterXtm said:
Could you be a bit more specific, please? Maybe a link?
Thanks
Click to expand...
Click to collapse
first try this: flash KT kernel and follow the instruction about TW version
and in general section , find the latest modem , XXUFNB8 in my case.
qtwrk said:
first try this: flash KT kernel and follow the instruction about TW version
and in general section , find the latest modem , XXUFNB8 in my case.
Click to expand...
Click to collapse
Unfortunately it seems I have the new bootloader (with Knox) installed and it doesn't let me install any custom kernel: it gets stuck on "..warranty bit: kernel" and doesn't boot. Prior to that I installed the stock ROM 4.4.2 and rooted it, removing Knox afterwards. I am not able to bypass the kernel warranty bit message.
Any idea on how to fix it for the stock ROM?
EDIT:
There are some updates regarding this issue. I managed to install a custom rom (Omega V24 for 4.4.2) on the rooted installation. Everything seems to work fine, except for the "warranty bit: kernel" that now is bypassed on startup and the wifi issue. This time I get other errors, though:
03-07 11:06:46.772 E/WifiHW (846): ##################### set firmware type 0 #####################
03-07 11:06:46.772 E/WifiHW (846): Cannot open "/data/.cid.info": No such file or directory
03-07 11:06:46.772 E/WifiHW (846): ==========[WIFI] Station firmware load ===========
03-07 11:06:46.902 E/WifiHW (846): return of insmod : ret = -1, Exec format error
03-07 11:06:46.902 E/WifiStateMachine(846): Failed to load driver
03-07 11:06:46.912 D/STATUSBAR-NetworkController(1062): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
03-07 11:06:46.912 E/WifiStateMachine(846): sendErrorBroadcast code:10
03-07 11:06:46.922 E/WifiController(846): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I have searched for this issue, but couldn't find anything helpful. As I understand it the file should be created automatically, but that obviously doesn't happen. Furthermore the wpa-supplicant.conf, that should be under data/misc/wifi/ is not there either.
At the moment I have following versions running:
AP: I9505XXUFNB8
CP: I9505XXUFNB9
CSC: I9505OXAFNB8
I reverted to XXUFNB8 (modem) and flashed it successfully, just to get some new errors:
First:
03-07 11:41:25.940 E/WifiHW (839): Supplicant not running, cannot connect
03-07 11:41:26.941 E/WifiHW (839): Supplicant not running, cannot connect
03-07 11:41:27.932 E/WifiHW (839): Supplicant not running, cannot connect
03-07 11:41:28.002 D/WifiDisplayAdapter(839): getWifiDisplayStatusLocked: result=WifiDisplayStatus{featureState=1, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo: Client/Owner: Client GroupId: Passphrase: SessionId: 0 IP Address: , connectedState=-1, networkQoS=0}
03-07 11:41:28.123 D/WifiDisplayAdapter(839): getWifiDisplayStatusLocked: result=WifiDisplayStatus{featureState=1, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo: Client/Owner: Client GroupId: Passphrase: SessionId: 0 IP Address: , connectedState=-1, networkQoS=0}
03-07 11:41:28.243 D/WifiDisplayAdapter(839): getWifiDisplayStatusLocked: result=WifiDisplayStatus{featureState=1, scanState=0, activeDisplayState=0, activeDisplay=null, displays=[], sessionInfo=WifiDisplaySessionInfo: Client/Owner: Client GroupId: Passphrase: SessionId: 0 IP Address: , connectedState=-1, networkQoS=0}
03-07 11:41:28.933 E/WifiHW (839): Supplicant not running, cannot connect
03-07 11:41:28.933 E/WifiMonitor(839): startMonitoring(wlan0) failed!
03-07 11:41:28.933 E/WifiStateMachine(839): Failed to setup control channel, restart supplicant
03-07 11:41:29.134 D/WifiHW (839): Unable to unload driver module "dhd": Device or resource busy
03-07 11:41:29.134 E/WifiHW (839): ##################### set firmware type 0 #####################
03-07 11:41:29.134 E/WifiHW (839): is_wifi_driver_loaded() is true !!!
03-07 11:41:29.134 I/WifiHW (266): wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
03-07 11:41:29.194 E/WifiStateMachine(839): Unable to change interface settings: java.lang.IllegalStateException: command '24 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 24 Failed to set address (No such device)'
03-07 11:41:29.194 E/WifiHW (839): supplicant_name : p2p_supplicant
03-07 11:41:29.214 D/WifiMonitor(839): startMonitoring(wlan0) with mConnected = false
Then again:
03-07 11:41:44.228 E/WifiHW (839): Supplicant not running, cannot connect
03-07 11:41:44.228 E/WifiMonitor(839): startMonitoring(wlan0) failed!
03-07 11:41:44.228 E/WifiStateMachine(839): Failed to setup control channel, restart supplicant
03-07 11:41:44.428 D/WifiHW (839): Unable to unload driver module "dhd": No such file or directory
03-07 11:41:44.428 E/WifiHW (839): ##################### set firmware type 0 #####################
03-07 11:41:44.428 E/WifiHW (839): Cannot open "/data/.cid.info": No such file or directory
03-07 11:41:44.428 E/WifiHW (839): ==========[WIFI] Station firmware load ===========
03-07 11:41:47.912 D/Finsky (5732): [1] CheckWifiAndAutoUpdate.cancelCheck: Cancelling auto-update wifi check.
03-07 11:41:48.913 D/Finsky (5732): [1] CheckWifiAndAutoUpdate.scheduleCheck: Scheduling auto-update wifi check.
03-07 11:41:59.483 E/WifiHW (839): return of insmod : ret = -1, No such device
03-07 11:41:59.483 E/WifiStateMachine(839): Failed to load driver
03-07 11:41:59.483 E/WifiStateMachine(839): sendErrorBroadcast code:10
I am starting to believe this issue is incidentally caused by the information provided in the .cid.info-file. I don't really understand why, like the wpa_supplicant.conf, this file is not being created or why it contains false information, but the device information is not provided.
Strangely, after doing a factory reset yet again and flashing with stock rom the file is also not there.
Can anyone provide the correct contents of a .cid.info for a I9505 (German)? I found one example online (content: "murata"), but that didn't work.
Thanks!
Similiar problem but no solution
Hi,
I have nearly same problem about my galaxy s4 GT-I9505
First i want to write all the information in my "about device" page to here (since i am new about this deep tech and i dont know wihch one is useful for you while you are replying my answer)
Model Number
GT-I9505
Android version
4,3
Baseband version
I9505XXUAMDE
Kernel version
3.4.0-2869009
[email protected]#1
Sun Oct 13 18:47:33 KST 2013
Build number
JSS15J.I9505XXUEMJ5
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
---------------------
Secondly, i want to tell the story of my problem. I bought my device from Iraq (i am from Turkey by the way). At first there was no problem. About one an half month ago, i came from there to my homeland, Turkey. I went to a local phoneshop and did that imei registration thing.
I cant recall the date of 4.3 update, thats why i cant make any connection about that. But at least for 20 days i was using android 4.3.
And there was a problem about my wifi. When i touch the button, it becomes light green (not normal bright green, as if it will be open soon) and there is nothing for a long time like an hour etc.
After that, i started to digging over the web about my problem. Yesterday i did exact that: And nothing changed.
Pre-requisites
1) Install USB Driver for Samsung Galaxy S4 to transfer files between the Android device and the computer.
2) Enable USB Debugging Mode on phone to connect it with computer and use Android SDK with it. [Press Menu>> Settings>> Applications. From there navigate and click on Development option and check USB Debugging Mode.]
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having any custom recoveries such as ClockworkMod/TWRP already installed, backup data using the recovery.
4) The Galaxy S4 should have above 80% battery charge.
5) The phone should be factory unlocked and not locked to any particular carrier.
6) The device will lose manufacturer's warranty once it is rooted. However, users can reclaim the warranty back by unrooting the handset later.
7) The CF-Auto-Root files work only on Samsung Galaxy S4 GT-I9500 and GT-I9505. As applying these to any incorrect variant might brick the device, verify the model number of Galaxy S4 by navigating to Settings>> About phone>> Model number and install the root package accordingly.
Steps to root Samsung Galaxy S4 I9500/I9505 on Android 4.3 Jelly Bean
Step-1: Download CF-Auto-Root file for Galaxy S4 to computer
Download links
For GT-I9500- CF-Auto-Root-ja3g-ja3gxx-gti9500.zip
For GT-I9505- CF-Auto-Root-jflte-jfltexx-gti9505.zip
Step-2: Extract the downloaded root zip using Winzip, 7zip, winrar or any other extracting tool to get a file with .tar.md5 extension
CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
Step-3: Download Odin3_v3.07. Extract the Odin zip to get Odin3 v3.07.exe file
Step-4: Switch off Galaxy S4 and wait for five to six seconds for vibration to confirm complete power off
Step-5: Place the phone in Download Mode by pressing and holding Volume Down, Home and Power buttons together until the construction Android robot icon with a warning triangle appears on the phone's screen. Then press the Volume Up button to enter Download Mode
Step-6: Run Odin3 v3.07.exe as Administrator
Step-7: Connect the phone to the computer using USB cable while it is in Download Mode. Wait for some time until Odin detects the device. When the phone is connected successfully, an Added message will appear under Odin message box. Additionally, the ID: COM box in Odin will turn blue with the COM port number indicating successful connection
Note: If the Added message does not appear, then try another USB port, try the one located at the back side of the computer. In case Odin still fails to recognise the device then reinstall USB driver.
Step-8: In Odin, click the PDA button and select CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5 or CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 file according to the variants
Step-9: Ensure Auto-Reboot and F.Reset Time checkboxes are selected in Odin
Step-10: Click the Start button in Odin. The installation process should begin now and would take few minutes to complete
Step-11: When the installation process is completed, the phone will restart and soon a PASS message with a green background in the extreme left box at the very top of Odin. Once the home screen appears, unplug the USB cable from the phone to disconnect it from computer
Samsung Galaxy S4 I9500/I9505 running Android 4.3 should now be rooted successfully. You can now install any app that requires root permission. To verify the root method is installed and working properly, install Root Checker app from Google Play Sore.
Then i did this: (from a post)
"1. Root your phone
2. Download Root Explorer.apk, put it on your phone via USB, install it
3. navigate to either /data/misc/wifi or /system/etc/wifi
4. rename or delete wpa_supplicant.conf
4.5. reboot
5. ???
6. PROFIT!"
Actually i choose deleting both file, now i think that was one of my wrong choice. Becouse after that something has changed.
When i touch the wifi button, it turns open sıtuatıon (grey) for a while, for an half second, and turn itself off again immediately.
Then i did something written at this site (now i couldnt find the url). It was about root and unroot. i downloaded two zip file named "unroot.zip & update.zip". And did the recovery root with volume up home and power. Select both and checked if anything changed about wifi.
All these happens after 2 am at last night. I can remember and i dont know what to do.
I wısh ı had written here before doing all these things but unfortunately, this is it.
Sorry for my language, English is not my own. I will be very happy if anyone can solve my problem. Thank you very much.
Selin
Selin G�ng�r said:
Hi,
I have nearly same problem about my galaxy s4 GT-I9505
First i want to write all the information in my "about device" page to here (since i am new about this deep tech and i dont know wihch one is useful for you while you are replying my answer)
Model Number
GT-I9505
Android version
4,3
Baseband version
I9505XXUAMDE
Kernel version
3.4.0-2869009
[email protected]#1
Sun Oct 13 18:47:33 KST 2013
Build number
JSS15J.I9505XXUEMJ5
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
---------------------
Secondly, i want to tell the story of my problem. I bought my device from Iraq (i am from Turkey by the way). At first there was no problem. About one an half month ago, i came from there to my homeland, Turkey. I went to a local phoneshop and did that imei registration thing.
I cant recall the date of 4.3 update, thats why i cant make any connection about that. But at least for 20 days i was using android 4.3.
And there was a problem about my wifi. When i touch the button, it becomes light green (not normal bright green, as if it will be open soon) and there is nothing for a long time like an hour etc.
After that, i started to digging over the web about my problem. Yesterday i did exact that: And nothing changed.
Pre-requisites
1) Install USB Driver for Samsung Galaxy S4 to transfer files between the Android device and the computer.
2) Enable USB Debugging Mode on phone to connect it with computer and use Android SDK with it. [Press Menu>> Settings>> Applications. From there navigate and click on Development option and check USB Debugging Mode.]
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having any custom recoveries such as ClockworkMod/TWRP already installed, backup data using the recovery.
4) The Galaxy S4 should have above 80% battery charge.
5) The phone should be factory unlocked and not locked to any particular carrier.
6) The device will lose manufacturer's warranty once it is rooted. However, users can reclaim the warranty back by unrooting the handset later.
7) The CF-Auto-Root files work only on Samsung Galaxy S4 GT-I9500 and GT-I9505. As applying these to any incorrect variant might brick the device, verify the model number of Galaxy S4 by navigating to Settings>> About phone>> Model number and install the root package accordingly.
Steps to root Samsung Galaxy S4 I9500/I9505 on Android 4.3 Jelly Bean
Step-1: Download CF-Auto-Root file for Galaxy S4 to computer
Download links
For GT-I9500- CF-Auto-Root-ja3g-ja3gxx-gti9500.zip
For GT-I9505- CF-Auto-Root-jflte-jfltexx-gti9505.zip
Step-2: Extract the downloaded root zip using Winzip, 7zip, winrar or any other extracting tool to get a file with .tar.md5 extension
CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
Step-3: Download Odin3_v3.07. Extract the Odin zip to get Odin3 v3.07.exe file
Step-4: Switch off Galaxy S4 and wait for five to six seconds for vibration to confirm complete power off
Step-5: Place the phone in Download Mode by pressing and holding Volume Down, Home and Power buttons together until the construction Android robot icon with a warning triangle appears on the phone's screen. Then press the Volume Up button to enter Download Mode
Step-6: Run Odin3 v3.07.exe as Administrator
Step-7: Connect the phone to the computer using USB cable while it is in Download Mode. Wait for some time until Odin detects the device. When the phone is connected successfully, an Added message will appear under Odin message box. Additionally, the ID: COM box in Odin will turn blue with the COM port number indicating successful connection
Note: If the Added message does not appear, then try another USB port, try the one located at the back side of the computer. In case Odin still fails to recognise the device then reinstall USB driver.
Step-8: In Odin, click the PDA button and select CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5 or CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 file according to the variants
Step-9: Ensure Auto-Reboot and F.Reset Time checkboxes are selected in Odin
Step-10: Click the Start button in Odin. The installation process should begin now and would take few minutes to complete
Step-11: When the installation process is completed, the phone will restart and soon a PASS message with a green background in the extreme left box at the very top of Odin. Once the home screen appears, unplug the USB cable from the phone to disconnect it from computer
Samsung Galaxy S4 I9500/I9505 running Android 4.3 should now be rooted successfully. You can now install any app that requires root permission. To verify the root method is installed and working properly, install Root Checker app from Google Play Sore.
Then i did this: (from a post)
"1. Root your phone
2. Download Root Explorer.apk, put it on your phone via USB, install it
3. navigate to either /data/misc/wifi or /system/etc/wifi
4. rename or delete wpa_supplicant.conf
4.5. reboot
5. ???
6. PROFIT!"
Actually i choose deleting both file, now i think that was one of my wrong choice. Becouse after that something has changed.
When i touch the wifi button, it turns open sıtuatıon (grey) for a while, for an half second, and turn itself off again immediately.
Then i did something written at this site (now i couldnt find the url). It was about root and unroot. i downloaded two zip file named "unroot.zip & update.zip". And did the recovery root with volume up home and power. Select both and checked if anything changed about wifi.
All these happens after 2 am at last night. I can remember and i dont know what to do.
I wısh ı had written here before doing all these things but unfortunately, this is it.
Sorry for my language, English is not my own. I will be very happy if anyone can solve my problem. Thank you very much.
Selin
Click to expand...
Click to collapse
you try this, 100% working
1->>rooted device >>
2->>install root browser >>
3->>with root explorer edit "system/build.prop" (text editor)
4->serch this line ro.securestorage.support=true change ro.securestorage.support=false
basheermp1 said:
you try this, 100% working
1->>rooted device >>
2->>install root browser >>
3->>with root explorer edit "system/build.prop" (text editor)
4->serch this line ro.securestorage.support=true change ro.securestorage.support=false
Click to expand...
Click to collapse
Hi everyone, and basheermp1..
I did exactly what you wrote here but nothing changed
I installed root browser and found the line and changed the true word to false. but
Do you have any other ideas?
Thank you
Selin G�ng�r said:
Hi everyone, and basheermp1..
I did exactly what you wrote here but nothing changed
I installed root browser and found the line and changed the true word to false. but
Do you have any other ideas?
Thank you
Click to expand...
Click to collapse
after you saved ?
or
try again this method after full wipe and root
basheermp1 said:
after you saved ?
or
try again this method after full wipe and root
Click to expand...
Click to collapse
Been there, done that.. no fix!
It would be very helpful, if somebody bothered to answer my original posts..
basheermp1 said:
after you saved ?
or
try again this method after full wipe and root
Click to expand...
Click to collapse
i am sure that i click the next button but nothing changed
True low-level dev attention needed - WiFi driver failing
Selin G�ng�r said:
i am sure that i click the next button but nothing changed
Click to expand...
Click to collapse
Hi, I believe we all having this issue tried almost everything found on the internet... Is there somebody who really know something about the BCM broadcom wifi chip drivers for linux?
From the logs I believe there was a incorrect operation done during OTA or any other update from 4.2.2 to 4.3 and now we are not able to load the driver. Is there any true developer who can take a closer look onto this? I have found source code of android for i9505 with sources of the BCM drivers.
Thanks a lot for your help!
P.
hey guy i had the same problem, dont no if you want to try or not but this is how i did it, i rember the same thing happened on my note 2.
so alls i did was you get the 4.3 , 4.4.2 firmware or what ever you flashed via odin but this time instead of putting it in to pda put it in to phone press start cross your fingers and pray to who ever lol.
thats all i did and it solved the problem for me, hope it helps you
Had same problem now solved
I had the same problem got resolved by watchin this video on youtube .. hope this helps...
https://www.youtube.com/watch?v=26kFIPQ_WMY
MisterXtm said:
For a month I've been having issues with my phone, because the wifi stopped working. It wouldn't turn on (turning dark green, then off again). Since I didn't want to root my phone, I was waiting on the new Samsung update (4.4.2), hoping that it would fix the problem. Yesterday the update went online and I was able to complete it, but the wifi remained off.
In the meantime I was looking for ideas on how to solve the issue (turning on and taking out the battery, taking out the battery for a longer time, etc.) but nothing helped. I saw a post (http://forums.androidcentral.com/sa...-my-galaxy-s4-wont-let-me-enable-wi-fi-4.html), that seemed to be plausible and I thought I would give it a try.
Yesterday I rooted my phone (with Odin and CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5), loaded the newest SuperSU-app and was able to actually see, what the problem was. Logcat showed this, when turning wifi on:
03-05 21:52:36.347 I/WifiManager(1215): setWifiEnabled : true
03-05 21:52:36.347 I/WifiService(830): setWifiEnabled: true pid=1215, uid=10266
03-05 21:52:36.357 E/WifiHW (830): ##################### set firmware type 0 #####################
03-05 21:52:36.357 I/WifiHW (830): module is murata FEM1
03-05 21:52:36.357 E/WifiHW (830): ==========[WIFI] Station firmware load ===========
03-05 21:52:36.357 E/WifiHW (830): ==========[WIFI] MURATA FEM1 MODULE ===========
03-05 21:52:57.207 E/WifiHW (830): return of insmod : ret = -1, No such device
03-05 21:52:57.207 E/WifiStateMachine(830): Failed to load driver
03-05 21:52:57.247 E/WifiStateMachine(830): sendErrorBroadcast code:10
03-05 21:52:57.247 D/STATUSBAR-NetworkController(1215): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
03-05 21:52:57.257 E/WifiController(830): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
03-05 21:52:57.267 I/WFMonitorService(4771): WIFI_STATE_UNKNOWN
This happened also after deleting or renaming the wpa_supplicant.conf (both in system/etc/wifi and in data/misc/wifi) and restarting the phone. I also tried deleting or renaming the whole wifi-folder (in both directories), without success. Renaming the file worked, but it wasn't recreated upon restart, which seemed pretty strange. Upon renaming the wifi-folders only one was recreated (the one under data/), but the .conf-file was still missing. I continued getting the error message cited above.
I searched for the "device not found" issue and found the following thread (http://forum.xda-developers.com/showthread.php?p=50535766), but this didn't help either. Even setting permissions for the files and folders that I thought would be important didn't help.
Today I wiped my phone clean in recovery and tried flashing the stock firmware I9505XXUFNB8_I9505OXAFNB8_I9505XXUFNB8_HOME.tar.md5 on, but wifi was the same. I even tried flashing only the modem with files I found here: http://d-h.st/users/DjeMBeY/?fld_id=15780#files. Something changed, because when I turned wifi on it turned itself off right away, so it didn't last in the dark green status for a few seconds as it used to. I also recall seeing this error message, as opposed to the one above and it was running slow with different other errors (no sound, apps crashing, etc.):
E/WifiHW ( 793): return of insmod : ret = -1, Exec format error
I really don't know what to do with it anymore. Since bluetooth is working I don't think it is a hardware issue and I should be able to resolve it somehow. Since I rooted it I don't know if I can use the warranty and I didn't want to send it in for 2 weeks.
I would be very happy about any ideas on how to resolve this issue. I hope there enough information. Thanks in advance!
Click to expand...
Click to collapse
Hello!
The solution for this problem:
1. Open/extract your rom archive with WinRAR (or something), for example:
2. Again, open/extract the file with the .md5 extension (mine is I9505XXUFNC4_I9505XEOFNC1_I9505XXUFNC4_HOME.tar.md5 )
3. Copy modem.bin and NON-HLOS.bin into your ext-SD card.
5. Run Terminal Emulator (any) and start this:
su
cd mnt/sdcard/
dd if=NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=modem.bin of=/dev/block/mmcblk0p2
reboot
Click to expand...
Click to collapse
Done, it will work.
Samsung doesn't allow to flash those files by odin, and that's the problem why wi-fi (sometimes bluetooth) is not working.
Good luck.
basheermp1 said:
you try this, 100% working
1->>rooted device >>
2->>install root browser >>
3->>with root explorer edit "system/build.prop" (text editor)
4->serch this line ro.securestorage.support=true change ro.securestorage.support=false
Click to expand...
Click to collapse
why this fix is needed (it works for me but why) ? We are talking about stock firmware here.
Is smth. broken with the device ? /efs partition or maybe hardware issue ?
Thanks!