Database Info

[SOLVED] How to connect to an Ad-Hoc (IBSS) network?

I've been using for years a laptop with usb broadband device, and sharing it through an ad hoc network to mobile devices.
My last two Android Devices (HTC Magic and Samsung Galaxy Spica) never had problems connecting to that network - altough they always had custom roms and custom kernels, YoshiMod and SpicagenMod, both CyanogenMod based - (don't remember trying with stock roms).
Two days ago I bought a Nexus S, flashed the Air Kernel, and now I became confused that the ad hoc network didnt appear on the scanned networks (on the nexus) but it appears on the Wifi Analyser App (and still, on other two android phones)
So I installed Wifi Manager and I get the information "standard android does not support connecting to ibss (ad-hoc) networks".
So my question is: what the f***? Any workaround for this issue? Because, if it was possible to those two android phones I used, I suppose it's possible too for Nexus.
I read here a suggestion to use Connectify, but still the problem.
I have a stock 4.0.4 (with Air Kernel "wifi fix version").
Thanks in advance.
SOLUTION: This method. Shortly:
1. root is required - make sure you have your file system app (like Root Explorer) set to make files R/W so you can edit/rename/set permissions
2. turn off wifi
3. go into system/bin and rename wpa_supplicant to wpa_supplicant_backup
3. download the wpa_supplicant file found here
4. unzip it
5. move it to system/bin and paste it
7. set permissions to xxx, x, xxx (columns) - see more details in original thread
8. go back and start up wifi (no reboot needed)
9. click to connect
Credits to Lock-N-Load.
Use it at your own risk.

i've tried with your method but it won't work on s3 ics 4.0.4 stock rom

fantastic
Maxxd01 said:
I've been using for years a laptop with usb broadband device, and sharing it through an ad hoc network to mobile devices.
My last two Android Devices (HTC Magic and Samsung Galaxy Spica) never had problems connecting to that network - altough they always had custom roms and custom kernels, YoshiMod and SpicagenMod, both CyanogenMod based - (don't remember trying with stock roms).
Two days ago I bought a Nexus S, flashed the Air Kernel, and now I became confused that the ad hoc network didnt appear on the scanned networks (on the nexus) but it appears on the Wifi Analyser App (and still, on other two android phones)
So I installed Wifi Manager and I get the information "standard android does not support connecting to ibss (ad-hoc) networks".
So my question is: what the f***? Any workaround for this issue? Because, if it was possible to those two android phones I used, I suppose it's possible too for Nexus.
I read here a suggestion to use Connectify, but still the problem.
I have a stock 4.0.4 (with Air Kernel "wifi fix version").
Thanks in advance.
SOLUTION: This method. Shortly:
1. root is required - make sure you have your file system app (like Root Explorer) set to make files R/W so you can edit/rename/set permissions
2. turn off wifi
3. go into system/bin and rename wpa_supplicant to wpa_supplicant_backup
3. download the wpa_supplicant file found here
4. unzip it
5. move it to system/bin and paste it
7. set permissions to xxx, x, xxx (columns) - see more details in original thread
8. go back and start up wifi (no reboot needed)
9. click to connect
Credits to Lock-N-Load.
Use it at your own risk.
Click to expand...
Click to collapse
thank you very much...i have looked around and got a wpa file and it worked but i had to change between the original and this wpa if i wanted to connect to various wifi...
and your method worked but i changed the wpa_supplicant as wpa_supplicant was not working, and the permission i left it to be xxx xx xxx....
it is working perfectly... thank you for that wpa file....

No need to modify wpa_supplicant
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=50
mode=1
It'd be better if you delete all other network={} blocks.
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.

Help
I followed the steps but its not working on my device xperia neo 4.0.4
any help
note :that I'm using my Nokia n8 for tethering through ezspot application

Root Access Needed
nariman1980 said:
I followed the steps but its not working on my device xperia neo 4.0.4
any help
note :that I'm using my Nokia n8 for tethering through ezspot application
Click to expand...
Click to collapse
is your Xperia rooted? Connect it to pc and open adb. If you get # as the prompt, you have root access from adb. If not type su on adb. Then you may get # prompt.
If you're having root access you could do the above steps and get it working.

HEXcube said:
is your Xperia rooted? Connect it to pc and open adb. If you get # as the prompt, you have root access from adb. If not type su on adb. Then you may get # prompt.
If you're having root access you could do the above steps and get it working.
Click to expand...
Click to collapse
yes i have a rooted device .i followed the steps and copied wpa-supplicant and the result was that my wireless not working at all .

Modify wpa_supplicant.conf
Note that the method mentioned by Maxxd01 is different from the one i suggest. In Maxxd01's method you'll need to change /system/bin/wpa_supplicant. You'll have to find one for your specific device and platform or compile from source. Your Xperia will need a wpa_supplicant binary compiled for it. If you can find it follow the first method.
For my method, edit /data/misc/wifi/wpa_supplicant.conf as i said in the previous post. It seems you didn't do the chown properly.

HEXcube said:
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=1
mode=1
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
Click to expand...
Click to collapse
Thank you and I'm sorry cause i didn't read your previous reply .
As i understand that no need to copy wpa-supplicant anymore . And should edit the other wpa file .but i didn't understand what do you mean by adb emulater ? I'm new in Android and have no experience with it before so please don't feel boring from me if i ask any question .
I'm glad cause you're helping me thanks

I did as you mentioned
and for the first time i see the Wifi name of my Nokia n8 in Wifi scan
note :when i was scanning for Wifi spot before ,my Wifi didn't show the name at all .
But now after the scanning shows the name of the Wifi spot ,it couldn't connect and this is an image from my device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then i go back to wpa-supplicant.conf and realized that all data which i add has gone and new data has been written
note :"nariman"is the new Wifi spot and the other one is neighbor's Wifi spot .
what should i do next ?

Use this wpa_supplicant.conf
Content of modified wpa_supplicant.conf(changes in bold)
ctrl_interface=wlan0
update_config=1
device_type=0-00000000-0
ap_scan=2
network={
ssid="nariman"
scan_ssid=1
key_mgmt=NONE
group=WEP104 WEP40
auth_alg=OPEN SHARED
wep_key0="09674"
mode=1
priority=1
}
After pushing the modded wpa_supplicant.conf don,t forget to change ownership and group back to original ones by doing
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
or else wifi'll show error.
remember, don't scan for networks after turning on wifi. Keep the adhoc network ready and turn on wifi. It'll automatically connect. I hope you didn't change the name and password of adhoc network.I've included modded wpa_supplicant.conf along with an explanation wpa_supplicant.conf(in case you were wondering what this stuff is all about).
---------- Post added at 12:27 AM ---------- Previous post was at 12:01 AM ----------
If you find it difficult try first with open adhoc. In which case your wpa_supplicant.conf would look like
ctrl_interface=wlan0
update_config=1
device_type=0-00000000-0
ap_scan=2
network={
ssid="your_adhoc_name"
scan_ssid=1
key_mgmt=NONE
mode=1
priority=1
}

Hi and Thank you again
i follow the steps
then i turned my Wifi on and didn't scan ,the name of my adhoc was there but no connection done. Only "not in range"is written under it and i don't know what does it mean
i press on adhoc nariman and this image shows the result
i think there's something stuck but i don't know what it is and what to do
waiting your opinion to solve this problem

I have Wifi manager ,does it help ?

nariman1980 said:
I have Wifi manager ,does it help ?
Click to expand...
Click to collapse
Wifi Manager is of great use. It show/lists adhoc networks,but does'nt connect to it.It causes the name of adhic networks to appear in wpa_supplicant.conf-that's great help coz u don't have to manually edit wpa_supplicant.conf to add the network name. But you still have to add the lines which i mentioned in the previous post(the bold ones).

I add the bold lines but after turning the Wifi off they disappear !shall i edit anything in permissions of wpa_supplicant_info ?ex :xxx.x.xxx

wpa_supplicant_info?
wpa_supplicant_info? Where did you find that file? Don't your fone have wpa_supplicant.conf?You should edit wpa_supplicant.conf in /data/misc/wifi. If there's any change in the files your fone have please tell me.
Don't edit the file while wifi is on. Turn wifi off and edit.
And after pushing the modified file you should change the ownership back to original, not the permissions.
Do the following using adb or Terminal Emulator as su
#chown system.wifi /data/misc/wifi/wpa_supplicant.conf
after doing this check the properties of file and make sure ownership is system wifi and not root root.

Interesting post about adhoc wifi
Hey guys,interesting news!
A Senior xda member spirosbond had figured out Connect to Adhoc by modding wpa_supplicant.conf long before i even became an xda member. He's given a detailed explanation of this method.
Visit his website
http://grdroid.info (not english)
OR
his xda thread
http://forum.xda-developers.com/showthread.php?t=1511544

Tested on Xperia Mini
An XDA member Dilushan( http://forum.xda-developers.com/member.php?u=4606137 ) has tested this method on his rooted Xperia Mini. So, this must work in nariman's Xperia Mini Pro too.

Thanks!!!
HEXcube said:
I changed data/misc/wifi/wpa_supplicant.conf instead of /system/bin/wpa_supplicant.
Step1:First i scanned my adhoc network using Wifi Manager. It shows adhoc networks. I ignored it's warning and tried to connect. It'll fail.No problem! We now have the adhoc network listed in wpa_supplicant.conf.
Note: you can skip this step if you know how to edit wpa_supplicant.conf manually or if your device already lists adhoc networks on scanning.
Step2: You'll need to root your device if you're doing this through your device itself. If you use adb you may not need to root your device.(I had root access by default through adb. So rooting the device wasn't necessary for me). If you're using pc(windows or linux), i recommend Android Commander. If you're doing this from device itself, use some Root Explorer and Terminal Emulator.
Pull and/or edit data/misc/wifi/wpa_supplicant.conf. Add the following line
ap_scan=2
Find line like
network={
ssid="your adhoc name"
bssid=*some value*
.
.
}
Delete bssid line.
Add/Change the following
scan_ssid=1
priority=50
mode=1
It'd be better if you delete all other network={} blocks.
Push back/save the modified file.
chown ownership back to system.wifi. Type the following in adb/Terminal Emulator
#chown system.wifi data/misc/wifi/wpa_supplicant.conf
Ok, done! Now you can turn on wifi and if the specified adhoc network is nearby, your device'll automatically connect to it. Don't scan for new networks. If you do, adhoc support will be lost and you'll have to start over again!
Advantage: Safer than modifying system/etc/wifi/wpa_supplicant binary. Saves you the trouble of compiling modified wpa_supplicant or finding a compiled one for your platform.
Drawback: This is just a temporary solution.You'll have to repeat this process for every new adhoc network as it doesn't enable adhoc forever. It is good for connecting to your home network or other known networks, but if you want to connect to any adhoc network you scan,then this is not your method. Because, wpa_supplicant.conf will be overwritten every time you scan a new network.
Click to expand...
Click to collapse
Only want to say you THANKS THANKS THANKS!!! I have a china mobile Start W008+ and conect to my wifi adhoc perectly!!!! Thanks again!!!

connectify ..the wpa_supplicant route...opps
well I did exactly what i read......and it returned alot of ehh
"settings not working android-ishhh" ...messages...everysingle time..so i just back tracked.....and fixed it..
still cant see the connectify hotspot...thanks anyway
Sent from galaxy ace GT5830

[Tutorial] How To Logcat

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
Moscow Desire said:
Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
Edit: For phones/tablets with internal storage & external sd:
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
MD
Click to expand...
Click to collapse
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
FuzzyMeep Two said:
I have made a tool to simplify this for people. I will send you the .bat version, to see the validity of the file, and post the .exe for everyone else.
http://logcat-tool.googlecode.com/files/logcatHELPER.exe
I made this in about a half hour, so if you fnd any issues let me know. I believe i worked out all functionality issues, and do plan on expanding functionality in the future.
Click to expand...
Click to collapse
(If you used his tool, here's his post, thank him for his work!)

Very nicely done, now i have something i can refer people to

Perfect tutorial. Well done. ... I'll translate your tutorial into my language to share it other people.

pRo_lama said:
Perfect tutorial. Well done. ... I'll translate your tutorial into my language to share it other people.
Click to expand...
Click to collapse
Thank you! And thanks for taking your time to translate it!
If you need me to clarify anything shoot me a PM, and I'll help! (Same goes for anybody else interested in porting to their language)
Pax

Very nice, but I do have a question (and I started programming for Android recently): What do you do when the system reboots while debugging (in my case musb_hdrc.ko)? I tried catlog, but the logs are empty... Is there another way to do that?
Thank you in advance

Krain said:
Very nice, but I do have a question (and I started programming for Android recently): What do you do when the system reboots while debugging (in my case musb_hdrc.ko)? I tried catlog, but the logs are empty... Is there another way to do that?
Thank you in advance
Click to expand...
Click to collapse
Use adb instead of an in-android method to capture the logs, you can start when the boot animation starts (note: Not when the kernel splash screen appears) and when it reboots, it'll automatically end. (i.e. run the following in command prompt:
Code:
adb logcat *:E > oh_nos_it_crashed.txt
)
If you're not getting to the boot animation (keeps cycling on the Kernel splash screen) then you have kernel issues, and you need a kernel that has integrated last_kmsg (a whole different ball of wax that I'm still learning about) to figure out what's going on. (kmesg's are direct kernel output)
Maybe if someone like AdamOutler (or any other Dev who has a much better handle on them than myself) were to explain them, it'd help
Pax

Hey man regarding your guide .
I was testing a built of cm9 from my htc one v and it wasnt booting so the dev told me to do a logcat for it .
Just wondering what the process and commands would be?
Thanks.

Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
But what if you can't connect ADB to your device? You can do this
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
Nice definition of the display terminology
MD

tranceph0rmer said:
Hey man regarding your guide .
I was testing a built of cm9 from my htc one v and it wasnt booting so the dev told me to do a logcat for it .
Just wondering what the process and commands would be?
Thanks.
Click to expand...
Click to collapse
What you'll wanna do is run the following,
Code:
adb logcat *:E > crash.txt
And look at the output file specifically for lines that say 0x0deadbaad (if you see that, that means there's a problem with the Java libraries it references above it) otherwise look for other F/ lines, that'll point you in the right direction.
If you're having issues where and is not accessible for to buy having USB debugging turned off because of doing a /data wipe (factory data reset) first install a similar Rom (in your case, a prior, stable CM9, boot into it, turn on usb debugging, reboot into recovery & only write /cache & dalvik cache before installing the offending Rom & getting your logcat (sorry if I rambled, just got done working a double )
Pax
Sent from my R800x using Tapatalk 2

Moscow Desire said:
Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
But what if you can't connect ADB to your device? You can do this
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
Nice definition of the display terminology
MD
Click to expand...
Click to collapse
Thanks, MD!
The problem is when you can't access terminal (bootloops, fc'ing like it's going out of style, etc.) that adb is really useful. Sometimes to trick the system into working, you can (esp with AOSP based roms) install a same version of android (I.e. 4.0.4) & not wipe /data (after turning on usb debugging) & still have an access (I learned this after spending about 2-3 months crack flashing my own builds & getting tired of titanium restoring all my apps)
Pax
Sent from my R800x using Tapatalk 2

Great guide, thanks! Found it through the portal. I just added to my sig so maybe it will help stop some of those questions.

paxChristos said:
What you'll wanna do is run the following,
Code:
adb logcat *:E > crash.txt
And look at the output file specifically for lines that say 0x0deadbaad (if you see that, that means there's a problem with the Java libraries it references above it) otherwise look for other F/ lines, that'll point you in the right direction.
If you're having issues where and is not accessible for to buy having USB debugging turned off because of doing a /data wipe (factory data reset) first install a similar Rom (in your case, a prior, stable CM9, boot into it, turn on usb debugging, reboot into recovery & only write /cache & dalvik cache before installing the offending Rom & getting your logcat (sorry if I rambled, just got done working a double )
Pax
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the info.
Will do that the next time i get stuck at the boot animation

can anyone tell me how to clear / reset logcat?
Thanks in advance

riteshbendre said:
can anyone tell me how to clear / reset logcat?
Thanks in advance
Click to expand...
Click to collapse
Why would you want to do that?
To my knowledge, the only way logcat is reset is if you reboot your phone.
That's why filtering your results is very helpful, because no matter how long it's been running, you can get the info that you want without extraneous information
Pax

Thanks for the clarifications

Man thank you so much for the awesome guide!
Now I can actually filter out my logcat results instead of searching through the entire log.
Sent using Tapatalk

Helpful Tool
paxChristos said:
Here's how to use logcat.....
Click to expand...
Click to collapse
I have made a tool to simplify this for people. I will send you the .bat version, to see the validity of the file, and post the .exe for everyone else.
FIXED HUGE ISSUE CAUSING EMPTY FILES
DOWNLOAD
PM or post here if you run into any issues. They WILL be addressed.
I have made a tool to simplify Logcat creation for people. The creation of this tool was inspired, and guided, by the thread started HERE by paxChristos.
UPDATE 4.1
Corrected an issue causing empty files.
apparently, if the process id contained a space ( 1234) the file would parse correctly, but if the numbers came up to the parenthesis (12345) it would output an empty file named ACTIVITY(12345) with no extension.
This was a huge issue, and i apologize for not seeing it sooner. It has been corrected, and the logcat tool works better than ever. I just ran through a 20,000 line logcat without any empty files appearing.
a couple more things to help with stability.
Underscores (_) will be replaced by dashes (-)
Brackets ([]) and arrows (<>) will be replaced with paranthesis(())
-------------------------------------------------------------------------------------------------------------
HUGE UPDATE
Added the ability to "SUPER PARSE" Files, which separates files into folders by log level and creates a TXT file for each activity
Super parse DOES NOT Work with LONG format Logs.
SUPER PARSE is in its infancy I do expect errors, please let me know if you run into anything.
OLD STUFF
EDIT V3.6 DONE
Added ability to filter logcats by activity name. (logcat -s "FILTER")
Fixed Log Level Setting
EDIT V3.5 DONE
NOW PROPERLY PARSES "LONG" FORMAT LOGCATS.
Thank you to Senior Member jes0411 for pointing out the issues that lead me to create V3.4 and 3.5. If any of you have an issue please let me know. It could be hours before i get to it or weeks, but i will get to fixing it.
EDIT V3.4 DONE
Changed the way the date variable was handled to hopefully fix issues experienced by users of non-English versions of windows.
EDIT V3.3 DONE
EDIT V 3.2 Finished
Google code won't allow any new uploads, so i uploaded the new update to XDA in a ZIP file.
Fixed ADB Location settings, some users were having trouble if they input the ADB folder with any quotation marks in the path name, it will now automatically remove quotation marks to ensure correct syntax.
Fixed issue with ADB Location setting not exiting to previous menu.
Fixed issue with Log Level setting not exiting to previous menu.
Capitalized some stuff
Added a feature that will automatically create the selected folder if no output folder exists and the user attempts to run a log.
Added a check when selecting an output folder that will ask if you want the folder created if it does not exist
EDIT V3.1 DONE
FIXED OPTIONS 7 & 8, URLS WERE MISSING A "?"
CHANGELOG EDITS
SAVES AND PARSES FILES IN TO DIFFERENT OUPUT FILES BASED ON LOG LEVEL (E , I , D , W , ETC)
LOGCAT TOOL v1.1 by FuzzyMeep TWO
I made this in about a half hour, so if you fnd any issues let me know. I believe i worked out all functionality issues, and do plan on expanding functionality in the future.
reposted HERE
Edit: source here.
Batch Source
EDIT: UPDATED TO V1.1
added the framework to add filtering to your logcat, it is in the exe, but not utilized yet (still bugy). i have also worked out a few minor bugs in this release.

Very nice tut. Will try

thanks a ton for the in depth guide. I was always fairly confused on how to approach this, so now I'll have something to refer to in order to help all of the awesome devs here.

mcmb03 said:
thanks a ton for the in depth guide. I was always fairly confused on how to approach this, so now I'll have something to refer to in order to help all of the awesome devs here.
Click to expand...
Click to collapse
+1

[Q]Spoofing MAC on Galaxy Ace [Details&attempts listed]

Hey all,
I'm trying to spoof my MAC address on the Galaxy Ace, though nothing seems to be working. [Details and attempts listed below]
Phone Details:
Samsung Galaxy Ace GT-S5830
OS: Stock Gingerbread 2.3.5
Rooted
Installed Software:
Superuser
ES File Explorer (with show hidden (. prefix) files turned on & up to root enabled, root R/W)
Busybox (Free)
Android Terminal Emulator
(all with Superuser permissions)
What I've tried:
First I cleared the phone's IP DCHP lease in the router.
In Terminal on the phone whist not connected to a network, but wifi turned on I:
su
ifconfig wlan0 down
ifconfig wlan0 hw ether 112233445566
ifconfig wlan0 up
iplink show wlan0
Click to expand...
Click to collapse
also tried
su
ifconfig wlan0 down
iplink set wlan0 address 11:22:33:44:55:66
-->At which point I get (even with busybox prefixed)
iplink: SIOCSIFHWADDR: Operation not supported
Click to expand...
Click to collapse
The first code I quoted gave me no errors and appeared to execute successfully, but iplink show wlan0, the router (once the phone had connected), and several other tools (to see if ANY could see the change) also displayed the phone's default MAC.
(I also tired: ifconfig wlan0 hw link 112233445566, offsetting the existing MAC by only 1, and prefixing commands with busybox - busybox ifconfig wlan0 hw ether 112233445566 -resulted in ifconfig: SIOCSIFHWADDR: Operation not supported)
Looking for /data/misc/wifi/nvram.txt. Can see /data/misc/wifi/nvram.info containing my MAC. Have edited this and tried joining network again, but no MAC change is showing. Have read it's a rather bad idea to restart the phone before changing the MAC in files back, [Why?] so am yet to do a restart to test the file change...
Various apk tools (preceded by clearing DHCP lease for phone's IP & proceeded by checking router & iplink show wlan0) including:
Wireless MAC Changer - Osama Abukmail
Mac Address Ghost - diewland
MAC Spoofer for HD2 - Ian Kim (as the description stated although for a HD2, there was a change it may work for other types [later found out mine doesn't use/have /system/etc/calibration])
(all with super permissions)
Does anyone know of, or have any other ideas that may work?
Is this possible with only Custom ROM's?
Much thanks in advance,
Blue

MAC address spoofing is a type of discussion that XDA does not allow. For that reason, thread closed.

[APP][2.2+][ROOT][WiFi] Reaver-GUI for Android

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reaver for Android v1.30
Reaver-WPS GUI for rooted devices with bcm4329/4330 wifi chipset or working external wifi card.
INFO:
Reaver for Android, short RfA, is a simple-to-use Reaver-GUI for Android devices with monitor-mode support.
It has some very cool features:
Detects automatically WPS-enabled routers.
All Reaver-Settings are accessible from a simple-to-use GUI.
Activates and deactivates Monitor-Mode automatically when needed.
Provides a simple way to connect when Reaver finds the WPA-Key.
External script support
Project status: PRE-FINAL
What does this mean?
There are some features which are not implemented yet.
Developement will continue very soon.​
Installation
Download/install bcmon.apk from HERE and RfA.apk from the bottom of this post. RfA may also download bcmon automatically.
Run bcmon, if it crashes try a second time.
If all runs fine, start RfA. If not, your device may be not bcmon compatible. Please see second post.
After selecting an WPS-enabled router, click on "Test Monitor-Mode".
Now you can use RfA, don't uninstall bcmon.
Steps 1 - 4 are only for the installation, they don't have to be repeated once done.
FAQ:
What is this awesome app actually usefull for?
Well, RfA is able to unveil the actual WPA(2)-Key of many routers within 2 - 10 hours.
WHAT?! I though WPA(2) is safe?
It used to be, but then many router models got WiFi Protected Setup, short WPS, implemeted, which is pretty vulnerable. (Details)
Basically it's a Brute-Force attack with Reaver against a 8 digit pin with 10^4 + 10^3 possibilities.
What is Reaver?
Reaver-WPS is a pentesting tool developed by Tactical Network Solutions.
It attacks WPS-enabled routers and after the WPS-Pin is cracked, it retrieves the actual WPA-key.
Reaver provides only a terminal interface, which is ok for notebooks etc., however it's a pain on Android devices.
Because of this I developed RfA.
Doesn't Reaver requires monitor-mode and so can't work on Android?
Yes, Reaver needs monitor-mode, but thanks to bcmon (or external wifi cards) some Android devices are now monitor-mode capable.​
bcmon compatibility
Developed and tested on: Nexus 7 2012 (Stock 4.3)
RfA *should* work on all devices with bcmon support (Broadcom bcm4329/bcm4330 chipsets)
Simply try by installing bcmon. Don't worry, if something goes wrong a simple reboot should fix everything.
For external wifi cards please see second post.
Tested & works on:
Nexus 7 2012 (Stock 4.3, Cyanogen 9)
Huawei Honour (Cyanogen Mod based ROM)
bcmon does NOT work on:
Samsung Galaxy S3/4/5
HTC One
LG G2
Nexus 4/5
Nexus 7 (2013)​
Credits & used tools:
Monitor-Mode over bcmon.apk:
Omri Ildis, Ruby Feinstein & Yuval Ofir
See: bcmon.blogspot.com
Reaver-WPS:
Tactical Network Solutions
See: code.google.com/p/reaver-wps/​
Disclaimer
Attention: Hacking of networks is illegal without having the permission of the owner! The developer is not responsible for any damage etc. this app could cause.
This software is only intended to show a big security hole, not to be able to surf in the neighbours Wifi​
XDA:DevDB Information
Reaver-GUI for Android, App for all devices (see above for details)
Contributors
SOEDI, bcmon team & Tactical Network Solutions
Version Information
Status: Stable
Current Stable Version: 1.30
Stable Release Date: 2014-07-01
Beta Release Date: 2013-11-04
Created 2013-09-24
Last Updated 2014-09-27

Second Post
If anyone has working Andorid drivers for external Wifi cards, please let me know,
If the layout looks strange on your phone, please send me a screenshot, so I can fix it
I have only a tablet and HD phone (emulator works to slow), so can't test the layout properly.
Usage of custom-scripts
To make RfA less dependent from bcmon, which seems to be dicontinued, I introduced custom monitor-mode-activation scripts.
Please note that those scripts only have sense for you, if you are already able to use monitor-mode on your device. Ether via special firmware for the internel wifi card or a kernel, which properly supports external wifi cards. Those scripts serve only as a "connector" between your wifi interface and RfA.
In order to enable this function you need to open RfA settings, tap on "Monitor-Mode settings" and disable the "Use bcmon" checkbox.
There are 3 different scripts you can specify:
Activation script
This script will be executed in it's own directory.
It should enable monitor-mode and exit.
Example:
Code:
#!/bin/bash
svc wifi disable
LD_LIBRARY_PATH=/data/data/com.bcmon.bcmon/files/libs
LD_PRELOAD=/data/data/com.bcmon.bcmon/files/libs/libfake_driver.so sh
cd /data/data/com.bcmon.bcmon/files/tools
./enable_bcmon
echo "rfasuccess"
exit
Click to expand...
Click to collapse
Warm-up script
RfA will read in this script as textfile and execute the commands internally. This is needed to execute reaver in the same terminal session as the script.
It should do all prepartions before Reaver is started. At least it has to cd into the directory where the reaver binary is.
Example:
Code:
#!/bin/bash
LD_LIBRARY_PATH=/data/data/com.bcmon.bcmon/files/libs
LD_PRELOAD=/data/data/com.bcmon.bcmon/files/libs/libfake_driver.so sh
cd /data/data/com.bcmon.bcmon/files/tools
Click to expand...
Click to collapse
Stop script
This script will be executed in it's own directory.
It should disable monitor-mode and exit.
Code:
#!/bin/bash
svc wifi enable
echo "rfasuccess"
Click to expand...
Click to collapse
Additional Information
You have also to specify your wifi-interface.
The given examples are those scripts, which RfA uses by default when you enable the "Use bcmon" checkbox.
The activation and stop script have to echo "rfasuccess" in order to tell RfA that they were executed properly. With this method you can also implement a sort of error-checking, by returning "rfasuccess" only when everything went fine.
Click to expand...
Click to collapse

Interesting.... nice job.
But better not let this get into the wrong hands, with these Admin Password hacking apps going on, anyone can take over someones router.
Sent from my super rare, old Scroll Excel running Android 2.3 using the offical app.
DOES DAT APP RUN ON DEVICES STILL ROCKIN 2.3?

Great job folks.
But for some reason user mode bcmode do not work well on HTC HD2 and my custom firmware, so I am using system module bcmon which create eth0 monitor interface instead of wlan0 (wifi0).
Can you please add interface selection or auto-detect interface in monitor mode ?
Tnx !

interface support
Hi,
RfA supports wlan0 and eth0 interface.
The problem seems to be the startup script and location of the Reaver binary, which seems to be different on your HD2.
Please describe exactly how you start monitor-mode, so I can update RfA
regards,
SOEDI

SOEDI said:
Please describe exactly how you start monitor-mode, so I can update RfA
Click to expand...
Click to collapse
Ok.
I have downloaded module src code from https://code.google.com/p/bcmon/source/browse/#svn/trunk/bcm4329/driver/src/bcm4329
Compile for my kernel and use with script that switch drivers with:
Code:
insmod bcm4329.ko firmware_path=fw_bcm4329.bcmon.bin
Firmware version is from https://code.google.com/p/bcmon/source/browse/#svn/trunk/bcm4329/fw
After that I can use sniffer like airodump (airodump -i eth0) and aireplay without need to switch monitor mode with airmon.
---------- Post added at 08:01 AM ---------- Previous post was at 07:11 AM ----------
Ahh, I have just researched the problem.
Problem is at enable_bcmon
Code:
./enable_bcmon
error: SIOCGIFFLAGS (No such device)
error: SIOCGIFFLAGS (No such device)
Couldn't find device index: No such device
I have also tried to start reaver with ./reaver -i eth0 -b 90:F6:52:C0:22:9C -c 1 -a -vv -w -S, but old problem with this drivers occurred, failed to associate to AP (it is not range problem, it is old known inject problem with kernel module driver)
Just have to find a way to make new bcmon working.

[/COLOR]Ahh, I have just researched the problem.
Problem is at enable_bcmon
Code:
./enable_bcmon
error: SIOCGIFFLAGS (No such device)
error: SIOCGIFFLAGS (No such device)
Couldn't find device index: No such device
I have also tried to start reaver with ./reaver -i eth0 -b 90:F6:52:C0:22:9C -c 1 -a -vv -w -S, but old problem with this drivers occurred, failed to associate to AP (it is not range problem, it is old known inject problem with kernel module driver)
Just have to find a way to make new bcmon working.
Click to expand...
Click to collapse
Ok, I see where the problem is....
The method to activate Monitor-Mode over bcmon.apk is:
Code:
define some paths
./enable_bcmon
But if you have self compiled modules:
Code:
sh setup.sh
?define tools path?.
Also on the bcmon website they said they fixed injection. Have you installed the newest firmware files and modules?
If you want to use bcmon.apk instead, maybe try to reinstall BusyBox. Some users reported this fixed their problems.
After you got your Monitor-Mode working, post it and I will update RfA.
reagrds,
SOEDI

First of all thank You SOEDI
Finally someone did it.. reaver is on android...
However i find the job of making it functional only half done...
as i understood from reaver forums it works best with wireless cards based on RTL8187 chipsets
in addition on the site of those modded bcmon drivers there is a statement that it doesn't support radiotap (be it mode or whatever) wich reaver seems to require..
so my idea is why not expanding Your application by adding linux kernel driver to support usb OTG (on the go) plugged in the android device's usb port...
search for phrase "android pcap" in google and You'll find it on kismet wireless
sorry for lack of link.. aperently i'd have to write 9 additional posts to post one
there is a source code down on that site too.. and it's monitor mode with no root priviledges..
plus additionally You also could add a functionality to Your gui to choose between built-in card and the one plugged in via USB-OTG to select wich one the gui is going to use..
So.. how about it? it could be mindblowing if You'd suceed
I'd bet You'd probably make a lot of peapole happy out there
sorry 4 my eventual spelling mistakes engilsh is not my native though..
regards
GusT.

Radiotap Headers
Hi,
The new bcmon.apk method supports radiotap headers, tested and worked At least with bcm4330 on Nexus7.
Monitor-Mode over USB-OTG would be cool, but I'm working on 3 other projects, so this will take some time...
At least it's working pretty good for a beta release

For me, the precess stops at "Switching wlan0 to channel 6".
I have a Galaxy S2 (i think it has a bcm4330 chipset) and android 4.2.2

I got stuck on "Waiting for bacon from etc etc.." is it normal?

ElmirBuljubasic said:
I got stuck on "Waiting for bacon from etc etc.." is it normal?
Click to expand...
Click to collapse
typically that means nobody is using the AP at that time

Reaver
Stuck on waiting for beacon:
Usually this is a range problem.
Try to start another attack, maybe on a different router.
Stuck on switching wlan0 to channel....:
The only solution I have is to simply restart the attack.
Usually this fixes the problem...

Hey great job on getting this working! Been waiting for this for a while, the aircrack solutions out there just take too long for a phone to crack through wpa/wpa2.
I'm having some issues though btw im on samsung galazy s2x which has the bcm4330. First off the bcmon starts up and enables monitor mode just fine but when I come to scan networks in reaver it nevers successfully finds any. I've tried to increase scan time and i've enables scan fix but nothing seems to work. I know my device is in monitor mode since i can scan for networks on another app, I can also reveice data packets but it's just not working on here any ideas? thanks awesome work!

The solution is pretty simple:
RfA scans in Managed-Mode, then enables Monitor-Mode and passes the data to Reaver.
So RfA can handle the Monitor-Mode on it’s own, no need to start bcmon first
Simply start RfA with wifi on
regards,
SOEDI

Thanks for the clarification now once I've scanned for networks connections come up like it should but i'm getting a new problem when testing monitoring mode it fails. I believe that this could be because of bcmon since the app doesn't seem to properly install the modded drivers. I could be wrong. I think i'm running into compatibility issues with my rom. I'm using MIUI I'm gonna try cyanogenmod to see if it helps anything.

hi
great work but im having a problem i have a htc wildfire s
evry time i start cracking a network i get (illigal instruction ./reaver wlan....)
and then nothing i think this is from my rom mostly but im not sure
my phone is fully rooted thx in advance

Alright well guess mini was causing problems with it so I guess that's not compatible working great on 4.3
Sent from my SGH-T989 using XDA Premium 4 mobile app

I'm on 09/26 cm 10.2 nightly and using galaxy s2, router is Linksys wrt110. First I wasn't able to get past "switching wlan0 to channel 1"
And if I enabled monitor mode in bcmon before scanning in rfa no router is found. how I got it to work was to scan first and once I found my router i tested for monitor mode. Before starting attack i used home button and then open bcmon and enabled monitor mode ( I had already said yes to install tool on first run), press and held home button and went back to rfa and started attack.
This was the result.
I do have a question though.. This was tested on my own router and my password is set to 0123456789 on the router. So what exactly do I have to enter from the result to connect?
I tried this on Kali as well and I got similar result, can remember if it was exact same.
I tried the WPA psk and the pin as passwords and was not able to connect to router. And my router is set to wpa2. Is that why? I kno this is off topic but I'm curious
Sent from my GT-I9100 using Tapatalk 4 Beta

Wow, seems like RfA has some problems with the S2.
Cool workaround!
Regarding your problem:
The shown WPA PSK is the hash of your real WPA Key.
Sometimes Reaver fails to get the plaintext Key and shows instead the hash.
However, if you use the hash as WPA Key it should work. Had tried this a few times and worked fine
regards,
SOEDI
EDIT:
Of course, you have to use the hash withoud the ' ' as key. Wanted only to mention this
RfA should have shown a Dialog with the Key and a connect button. Did it?

Android M with WPA-Enterprise ssl problem

I just upgrade my nexus to marshmallow and have a trouble to connecting my device to my collage wifi. It tell me that there are authentication problem on wifi setting. I try to catch some log from logcat and get this message:
wwpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:100c1069:SSL routines:ssl3_get_server_key_exchange:BAD_DH_P_LENGTHpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:100c1069:SSL routines:ssl3_get_server_key_exchange:BAD_DH_P_LENGTH
Who have the same problem withe, any solution to fix these?
Thank you.

I have same problem here, My university uses eduroam, which is wpa enterprise. and I can not connect to wifi after 6.0 upgrade. There must be some problem with wpa_supplicant had same problem with my Linux laptop and fixed the problem after downgrading the wpa_supplicant
Code:
[ 10-14 09:39:43.666 17159:17159 I/wpa_supplicant ]
wlan0: Trying to associate with 20:bb:c0:f8:e4:75 (SSID='eduroam' freq=2412 MHz)
[ 10-14 09:39:43.834 17159:17159 I/wpa_supplicant ]
wlan0: Associated with 20:bb:c0:f8:e4:75
[ 10-14 09:39:43.834 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
[ 10-14 09:39:43.841 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
[ 10-14 09:39:43.842 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
[ 10-14 09:39:43.872 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root' hash=687fa451382278fff0c8b11f8d43d576671c6eb2bceab413fb83d965d06d2ff2
[ 10-14 09:39:43.873 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root' hash=687fa451382278fff0c8b11f8d43d576671c6eb2bceab413fb83d965d06d2ff2
[ 10-14 09:39:43.885 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=US/O=Internet2/OU=InCommon/CN=InCommon Server CA' hash=623727ec472644a6bb70d240565c24223fdb0f2f5ac698027e3012489c70e817
[ 10-14 09:39:43.890 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=US/postalCode=70803/ST=Louisiana/L=Baton Rouge/street=110 Thomas Boyd/O=Louisiana State University/OU=LSU A & M/CN=acs-wlan.lsu.edu' hash=3b1214222f27c029417be13e02a6a422f958d470e88300f81716bc04663ae790
[ 10-14 09:39:43.892 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:acs-wlan.lsu.edu
[ 10-14 09:39:43.930 17159:17159 I/wpa_supplicant ]
EAP-MSCHAPV2: Authentication succeeded
[ 10-14 09:39:43.940 17159:17159 I/wpa_supplicant ]
EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
[ 10-14 09:39:43.950 17159:17159 I/wpa_supplicant ]
wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
[ 10-14 09:40:53.840 17159:17159 I/wpa_supplicant ]
wlan0: Authentication with 20:bb:c0:f8:e4:75 timed out.

Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}

it works!!
after countless hours of researching, adding the line onto the wpa_supplicamt.conf works. thanks bro!!
slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}
Click to expand...
Click to collapse

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Click to expand...
Click to collapse
Just to confirm that this is working for me too - thanks very much! :good:

al3co said:
Just to confirm that this is working for me too - thanks very much! :good:
Click to expand...
Click to collapse
That didnt seem to work for me. Are you guys doing anything else like clicking the Dev options to use legacy lollipop DHCP? or disabling the google connectivity services? or just simply rebooting?

Nope, nothing else - I just added the line to wpa_supplicant.
I've not rooted my phone, so did it a slightly different way via adb, but I made sure that the permissions (chmod) and group/owner (chown) were both set to the original settings. Have you checked to see if changing that fixes it for you?

how did you do it without rooting your phone
al3co said:
Nope, nothing else - I just added the line to wpa_supplicant.
I've not rooted my phone, so did it a slightly different way via adb, but I made sure that the permissions (chmod) and group/owner (chown) were both set to the original settings. Have you checked to see if changing that fixes it for you?
Click to expand...
Click to collapse

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
}
Click to expand...
Click to collapse
something strange is happening when i try this. once i edited the wpa_supplicant.conf file and tried to connect to my work network a 'wpa_supplicant.conf.tmp' file is created which effectively deletes the added line.
the only difference i can see is that the network requires mschapv2 so my (edited) wpa_supplicant.conf. files reads:
network={
ssid="D Wireless"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="####"
password="#####"
phase1="tls_disable_tlsv1_2=1"
phase2="auth=MSCHAPV2"
priority=3
proactive_key_caching=1
disabled=5
Any ideas?

Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.

slackhouse said:
Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.
Click to expand...
Click to collapse
thanks for such a swift reply.
Any chance you could post the command to use in the terminal to set the permissions (i suspect this is the issue).
at the moment the wpa_supplicant.conf file is showing permissions of:
-rw-rw---- wifi wifi 566
is this correct?
Despite using linux for the last 10 years i'm useless at getting this right!
many thanks

westy123 said:
thanks for such a swift reply.
Any chance you could post the command to use in the terminal to set the permissions (i suspect this is the issue).
at the moment the wpa_supplicant.conf file is showing permissions of:
-rw-rw---- wifi wifi 566
is this correct?
Despite using linux for the last 10 years i'm useless at getting this right!
many thanks
Click to expand...
Click to collapse
i just used "ls -la" to see the permissions. and if the rw, rw, isn't right, you'd use a chmod and if the owner or group wasn't right you'd use a chown. My organization has updated our radius servers, so I don't have to do this anymore. Here's what mine looks like without making any changes to it:"
-rw-r--r-- root root
To change owner:group, you'd do this: "chown root:root wpa_supplicant.conf"
To change permissions, you'd use: "chmod wpa_supplicant.conf 644"
Just make sure you have WiFi disabled, and once you save the file, reboot prior to enabling WiFi.

Wow, that's great, I'll try it first thing tomorrow (as son as I get back to work)
Thanks very much
update: unfortunately i still can't get it to work, despite setting permissions etc. either the file become corrupted and wifi doesn't work, or a new .tmp file is created.
Anyway, the IT people got back to me today, and assured me that they'd be updating the university servers etc. in the very near future, so it shouldn't be an issue for much longer.
But thanks for the help anyway, it's been a useful learning experience.

slackhouse said:
Your enterprise needs to update their radius servers and openssl software to fix this issue. A work around, if you are rooted, you can go to \data\misc\wifi\ and edit wpa_supplicant.conf. You need to add this line to your eduroam or wpa-eap network:
phase1="tls_disable_tlsv1_2=1"
Someone has already opened a ticket with Google: https://code.google.com/p/android/issues/detail?id=188867
Here's what my wpa_supplicant.conf looks like and I can connect to eduroam now:
disable_scan_offload=1
update_config=1
device_name=hammerhead
manufacturer=LGE
model_name=Nexus 5
model_number=Nexus 5
serial_number=066450ff0060c4a1
device_type=10-0050F204-5
config_methods=physical_display virtual_push_button
p2p_disabled=1
external_sim=1
wowlan_triggers=any
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password="mypassword"
phase1="tls_disable_tlsv1_2=1"
priority=14
proactive_key_caching=1
}
Click to expand...
Click to collapse
Didn't work for me. This issue is making me crazy

slackhouse said:
Here's the steps I took, though I am rooted:
1. Disabled WiFi.
2. Edited the wpa_supplicant.conf file via using ES File Explorer.
3. Verified permissions on .conf file were correct using Terminal Emulator.
4. Rebooted phone.
5. Enabled WiFi and connected.
If I enabled WiFi with incorrect permissions or prior to rebooting, the conf file reverted to its original state.
Click to expand...
Click to collapse
Doesn't work for me. Once rebooted It tries to connect automatically without success and then appears a pop up that wants me to enter the password again

For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.

MaKTaiL said:
For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.
Click to expand...
Click to collapse
Same issue for me, it made me crazy! finally i solved it... thanks thanks thanks!

doesn't work for me :crying:
Moto G2 xt1068 with cm13.. any work around?

Summary: what worked for me
I have a Motorola Moto E (condor) that I've just updated to LineageOS 14.1 (Nougat). Here's what I had to do, partly for my own reference and hopefully this will help others with the same problem. I couldn't connect to eduroam at my workplace due to a faulty RADIUS server that doesn't handshake correctly with TLS 1.2.
First, install ADB & Fastboot. Make sure USB debugging is enabled on your device, and allow root as ADB (Developer Options > Android debugging, and Root access: ADB only).
With your device plugged in to your PC, open an ADB command prompt on your PC (Start > Minimal ADB and Fastboot). Type:
Code:
adb root
adb pull /data/misc/wifi/wpa_supplicant.conf
This will put the wpa_supplicant.conf file on your computer (on my PC, it's located in "%localappdata%\VirtualStore\Program Files (x86)\Minimal ADB and Fastboot\wpa_supplicant.conf"). Edit it with your favourite text editor (NOT Notepad, as it won't recognise the Linux newline format. I prefer metapad). Find the configuration section for your WiFi network. Mine looks like this:
Code:
network={
ssid="eduroam"
bssid=<deleted>
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="[email protected]"
password=<deleted>
[B] phase1="tls_disable_tlsv1_2=1"
[/B] ca_cert="keystore://CACERT_stfc"
phase2="auth=MSCHAPV2"
priority=51
proactive_key_caching=1
id_str="%7B%22creatorUid%22%3A%221000%22%2C%22configKey%22%3A%22%5C%22eduroam%5C%22WPA_EAP%22%7D"
}
To disable TLS v2.1 and get the connection working, you'll need to insert the highlighted line. Save the file in the same location.
Now turn off wifi on your device, go back to your ADB shell and type:
Code:
adb push wpa_supplicant.conf /data/misc/wpa_supplicant_new.conf
adb shell
This will open a debug prompt for your device. You're now altering files on your device as root, so be careful! Type
Code:
cd /data/misc/wifi
ls -la
You should see a directory listing, including wpa_supplicant.conf and wpa_supplicant_new.conf:
Code:
-rw-rw---- 1 wifi wifi 5412 2017-03-07 08:30 wpa_supplicant.conf
-rw-rw-rw- 1 root root 5432 2017-03-07 08:18 wpa_supplicant_new.conf
You need to overwrite the old version with the new. First make a copy of the old file:
Code:
cp wpa_supplicant.conf wpa_supplicant_old.conf
Now we need to ensure the new file has the same permissions as the old. Type:
Code:
chmod 660 wpa_supplicant_new.conf
chown wifi wpa_supplicant_new.conf
chgrp wifi wpa_supplicant_new.conf
Now to overwrite the old version:
Code:
rm wpa_supplicant.conf
mv wpa_supplicant_new.conf wpa_supplicant.conf
Type ls -la again to check the permissions are correct. You should see something like:
Code:
-rw-rw---- 1 wifi wifi 5412 2017-03-07 08:30 wpa_supplicant.conf
Finally, exit from the ADB prompt (just type exit), reboot your device, enable wifi, and try to connect again.
I hope that helps!

MaKTaiL said:
For those still with problems, I found the solution on another website. Apparently the line you must add to the config file is a little bigger, here it is:
phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
It finally worked for me.
Click to expand...
Click to collapse
Am on Lineage 15.1 and want to add it, but under Oreo Android is using WifiConfigStore.xml to store the config. How must the line look like in my case?