I recently got my Samsung captivate and whenever i try to open market, gmail etc i need to sign in with my google account. This is fine, however it doesnt let me. I enter all my details correctly and i get "Error Can’t establish a reliable data connection to the server".
Im doing it over wifi and ive tried with my SIM in and out. Ive also tried the youtube workaround but i get "There was a network error while trying to sign in". My phone is parallel imported and has Android 2.2 with lidroid.
I have factory reset 3 times now but nothing has helped, each time i am presented with a chinease setup screen which i cannot understand.
Could someone please help me
- Doc
anyone know what to do?
I read this...
1. adb remount
2. adb shell
3. su
4. rm /data/data/com.android.providers.settings/databases/settings.db
Not good with android, could someone explain if the above would work?
doctorwhobbc said:
anyone know what to do?
I read this...
1. adb remount
2. adb shell
3. su
4. rm /data/data/com.android.providers.settings/databases/settings.db
Not good with android, could someone explain if the above would work?
Click to expand...
Click to collapse
I went to /data/data/com.android.providers.settings/ and there was only a folder called lib and nothing was in it. would this be the problem? does anyone know what the correct files should be in /data/data/com.android.providers.settings/
thanks
call your cellular provider. i had this issue before. it is server issue in my cellular provider
Related
Hello every body...
when I turn on the WI-FI the massage appear Unable to Scan Networks Then the wi-fi turns itself off.
Help me please guys...
i would suggest reflashing the stock firmware with ODIN. I had an issue like this on my Nexus One. Nothing helped. I had to fully wipe the phone and start over.
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
Awesome! Many thanks for the tip! You've made my day! That file's gotta be deleted from time to time, as it can get quite clogged. (And when you think I could've re-flashed my phone as per the previous post...!)
I having the same problem as this. after i removed and re entered my wifi login. also i had been on holiday and logged into a few other wifi routers.
when i re entered my home wifi it just kept turning off and saying "unable to scan networks"
its a vodafone UK contract Galaxy S (if that makes any difference)
I tried to root my phone using
[PROGRAM] One Click Root/UnRoot I9000 (Eclair and Froyo) Mac and PC
it seemed to work . i had an extra app for changing a few settings. but i still couldn't find the wifi file i need to delete? Had it not been rooted properly?
I'd really like to fix this without having to do a master reset every time?
What are my options?
Could i take an image of the mobile and remove the file from the image? then restore the image. A bit crazy if routing is not a possibility?
Can anyone help?
Thank you, unable to scan networks solved
How did you solve it?
with master reset?
Latest update to DI07 fixed this issue for me
The update was DI07 for the Samsung Epic 4G, not the Vibrant.
llamaunix said:
This weekend's update to DI07 from DG27 has fixed my "Unable to scan" Wifi issues. Since a few days ago when I would turn on Wifi it would turn itself off after about 10-20 seconds. It would also show a message saying "unable to scan for networks".. Previously I read that a factory reset would fix this problem but I held out for the new update to be pushed to my phone today (9/19) and indeed it fixed my problem. After the update rebooted, my Wifi turned on with no problem and it showed my previously added networks as well.
Good luck!
Click to expand...
Click to collapse
Is this update for the galaxy S?
or is there going to be a similar update?
I haven't logged onto another WIFI since I had to reset the phone (apart from my home WIFI). so i don't have to go through setting it up again.
cheers for the extra info
quick update
I am backing up with titanium backup manger now (free)
so hopefully it will restore the wifi it goes wrong again
(the phone needs to be ROOTED for the Titanium backup to work)
I rooted my phone with
http://forum.xda-developers.com/showthread.php?t=742403
one click rooter ( i couldn't run the "Galaxy S I9000 One-Click Root" file. i ran "rootme" file for 2.1 android, the rootme2.2 is for 2.2 it says dont run both)
And have 'astro file manager'(Free) and can explore more of my phone by pressing the up button a few times.
in astro file manger I searched for the word 'wifi' and got about 3 results. So its probably one of these.
We'll it working for the moment but I'm posting the more info for anyone else.
(I still don't know which file to delete to reset the wifi though.) but the titanium backup should be able to restore the wifi settings
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
hello alsatea,
I have the wifi problem as well, and my galaxy s is rooted by running rootme but I can't find the bcm_supp.conf file. How do I fix the problem without applying factory reset?
thanks
chanXda said:
hello alsatea,
I have the wifi problem as well, and my galaxy s is rooted by running rootme but I can't find the bcm_supp.conf file. How do I fix the problem without applying factory reset?
thanks
Click to expand...
Click to collapse
Hi,
You have first to open 'adb shell' and in the shell enter 'su' (you must allow superuser access on your phone).
Next execute 'rm /data/wifi/bcm_supp.conf' and finaly 'reboot'
Good luck,
Mark
CommanderTux said:
Hi,
You have first to open 'adb shell' and in the shell enter 'su' (you must allow superuser access on your phone).
Next execute 'rm /data/wifi/bcm_supp.conf' and finaly 'reboot'
Good luck,
Mark
Click to expand...
Click to collapse
THANK YOU SO MUCH.
I spent over an hour on the phone with AT&T and then with Samsung trying to resolve the "unable to scan networks" issue. Absolutely worthless.
I rooted my phone just to try this and avoid doing the factory reset, and it worked!
Now if only I knew how to avoid this in the future...
thanks this actually worked for my fascinate as well.. saved me some hassle!
I had the unable to scan networks problem on my Bell Canada Samsung Galaxy S Vibrant.
Have been attaching to static IP in my house using Wifi Static app. (great app, by the way. stores configurations for multiple static ips and then configures wifi and connects automatically when you're in range of one of them. no more manual fiddling with settings for every static IP)
But I guess this precipitated whatever happens to the "conf" file mentioned above.
Initially installed ES Strong file manager to see if I could see the contents of the /data folder. Showed up as empty. (apparently not a high enough level of access to see if there's anything in there)
So needed to go for "root" access.
Rooted my phone with One Click Root:
http://forum.xda-developers.com/showthread.php?t=742403
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
The terminal procedure could probably be put into a script.
Next time it happens, I'll just do the same.
Once Bell releases Froyo in Mid-dec, maybe this will be solved. But I'll probably hold off and watch the forums for a while before jumping to Froyo just in case it buggers up something else.
Good luck!
dietrite said:
Now if only I knew how to avoid this in the future...
Click to expand...
Click to collapse
android market
titanium backup
free version
paid is very fast
titanium backup
phone menu button
batch
backup all apps and user data (look for the highest number on the right)
it backs up everything
maybe set a schedule to back up
--
if wifi goes wrong
select backup restore tab
and restore wifi settings
--
xdacalfun said:
I had the unable to scan networks problem on my Bell Canada Samsung Galaxy S Vibrant.
Have been attaching to static IP in my house using Wifi Static app. (great app, by the way. stores configurations for multiple static ips and then configures wifi and connects automatically when you're in range of one of them. no more manual fiddling with settings for every static IP)
But I guess this precipitated whatever happens to the "conf" file mentioned above.
Initially installed ES Strong file manager to see if I could see the contents of the /data folder. Showed up as empty. (apparently not a high enough level of access to see if there's anything in there)
So needed to go for "root" access.
Rooted my phone with One Click Root:
http://forum.xda-developers.com/showthread.php?t=742403
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
The terminal procedure could probably be put into a script.
Next time it happens, I'll just do the same.
Once Bell releases Froyo in Mid-dec, maybe this will be solved. But I'll probably hold off and watch the forums for a while before jumping to Froyo just in case it buggers up something else.
Good luck!
Click to expand...
Click to collapse
Had the same problem. Then I was having problems getting Superuser to allow my ADB shell, so I followed the steps above with a terminal emulator and got my Wi-fi on my Captivate back. thx
xdacalfun said:
then installed the "Terminal Emulator" app from Android marketplace.
Ran the terminal emulator to get a command prompt. your soft keyboard should pop up. if not, hit the menu button on your phone and hit "toggle soft keyboard". Then typed in:
'su' and hit 'enter' (do not type quote marks)
to gain superuser access.
The superuser app will pop up to ask you if you want to grant superuser access to the terminal. hit 'yes' or 'ok' or whatever the right button is.
terminal responds with a '#' prompt.
Then I typed in:
'mv /data/wifi/bcm_supp.conf /data/wifi/bcm_supp.bak' and hit 'enter'
to rename the file.
I then typed 'exit' and hit 'enter' to get out of superuser and then I hit the phone's 'back' button to shut down the terminal.
And now my wifi works again!!
Click to expand...
Click to collapse
Beautiful, works great, and I can do this with out a PC, and much more simple. Very nice when you are traveling. Thanks for the tip.
alsatea said:
I found it :
since you're rooted, go to /data/wifi/ and delete bcm_supp.conf (back it up first just in case). Then reboot your phone.
Click to expand...
Click to collapse
Thanks a lot alsatea. Deleting /data/wifi/bcm_supp.conf and rebooting resolved the problem and I got back wi-fi. All the networks remembered previously came back. Thanks mate.
Just in case anyone is reading this topic but is unable to find the bcm_supp.conf file, try this instead:
> adb shell
$ su
# cd /data/misc
# chown wifi.wifi wifi
Then try enabling the wifi again. It should work.
running vegan and i keep getting this message. I think my wife was using it and maybe the battery died? not sure. any thoughts?
thanks
I get this about every 2 weeks. I boot into clockwork, reset to defaults, then restore from backup.
sent from my g-tablet using tapatalk
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Steps
Posting the steps you took might be a little more helpful to anyone reading your thread.....
gpzjack said:
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Click to expand...
Click to collapse
Which data base?
Do you mean perform a clear cache/data?
or are you mentioning the contact database sync from gmail?
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Thank you so much, this worked for me!
gpzjack said:
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Click to expand...
Click to collapse
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
yup the contacts storage got corrupted -> most likely you created an empty contact in the contacts app by mistake. Someone should sticky this - i see one of these threads daily haha. Its a pretty common problem.
many time that error (fc) is due to a contact with blank first and last name as the contact database uses them as index. if you have blanks the probem will keep returning.
thanks for the tip - seems to have helped me out of the
...acore... problem
Mind you, I **Never** touched the contacts app in any
way whatsoever.
The corruption happened "spontaneously"
After playing (it is *only* suitable for play) with android
for a few weeks now, you know what, android is CRAP
Cant get to Manage Apps
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
cassycan said:
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
Click to expand...
Click to collapse
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Norm Minske said:
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
Click to expand...
Click to collapse
I was unable to see the folder described in other peoples solutions, your solution of clearing data through the settings application worked great for me on brilliant corners 1.3.1. Thanks.
simuloid said:
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Click to expand...
Click to collapse
i manage to get tru the issue on adb shell by installing usb deview, n my command bar alrdy shown my device no. after typing adb devices but aft adb shell, came $ and not #, is there any different?
okay i had mine miracle- ly and not realising it done, my force stop no longer appear after downloading the latest busybox apps.=)
Hi - I was getting the acore error too. but I went ahead & did an nvflash. The error is still popping up. Any ideas?
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
superdx said:
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
Click to expand...
Click to collapse
I am not quite sure what your problem is.
Do you mean tethering?
And your phone does not keep the AP name and password for its own WLAN hotspot?
I am sure that there are some tethering apps on the Market.
Maybe one of them can help you to configure a customized AP name and password and saves it for later use.
Yep that's it exactly, tethering. The AP name and password keep resetting!
http://forum.xda-developers.com/showpost.php?p=18711488&postcount=128
clefster said:
This is because the permissions for the wifi settings got messed up so it can't write out your new permissions. The error handling isn't too good so it doesn't tell you about it
To fix, in a rooted terminal run this command:
chmod 770 /data/misc/wifi
Click to expand...
Click to collapse
After struggling with root, I tried your command and it doesn't work, says Operation not permitted
My stupid mates managed to lock my phone under the "too many attempts" thing... I REFUSE to wipe my phone... all im trying to do is turn on either wifi or data connection through adb using key events
i (think) i know the settings bit is
adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
that worked for gingerbread... i dont know if ics has changed
but i need the keyevents for it
i HAVE tried sqlite but i get the responce
"CAnnot update file - read only"
ive tried
chmod777 (whatever...)/settings.db
but it doesnt affect it
Bump.... please help... i want my phone back :/
Boom. done.
So? What was the solution?
mahrud said:
So? What was the solution?
Click to expand...
Click to collapse
Pulled data/data/com.android.providers.settings/databases/settings.db
changed "lock_pattern_autolock" value to 0
Pushed settings.db
allowed me to enter my pattern and unlocked my phone
Another solution to turn on wifi connection through adb when your phone is under the "too many attempts :
-Download on your PC a simple apk that toggle the WiFi (I use "WiFi On/Off Toggle swticher" apk from the Play Store https://play.google.com/store/apps/details?id=jp.ne.neko.freewing.WiFiOnOff)
-Install the apk with the command : adb install jp.ne.neko.freewing.WiFiOnOff.apk
-Start the activity : adb shell am start -n jp.ne.neko.freewing.WiFiOnOff/.WiFiOnOff
I use this method to unlock the Motorola Defy Mini XT320 (2.3.6) of a friend.
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.