[Q] Location of wpa_supplicant.conf on I9000 roms - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi guys,
I've got a customer who is having a problem on my app which has to read wpa_supplicant.conf. Normally this file is located at /data/misc/wifi/wpa_supplicant.conf and requires root to read.
Anyways, according to the errors he's getting and based on his own exploration, his wpa_supplicant.conf file is not located there. I'm not sure which ROM he has (am waiting for a reply to that question now), but does anyone know if this file is normally located in /data/misc/wifi ?
Thanks,
James

Its not there on Darky 7.0 based on latest JPY firmware.
Search in progress ;]
/etc/wifi/wpa_supplicant.conf
and symlink
/system/etc/wifi/wpa_supplicant.conf

Thanks for the tip. On my customer's phone that file is just a template and not actually storing networks. I'll poke around in that ROM though. Thanks again.
Sent from my Nexus One using XDA App

Stock Froyo location is etc/wifi
jje

Looking at /system/etc/wifi/wifi.conf on Darky 7.0 I see the following
Code:
FIRMWARE_LOADER=wlan_loader
DRIVER_PROP_NAME=wlan.driver.status
SUPPLICANT_NAME=wpa_supplicant
SUPP_PROP_NAME=init.svc.wpa_supplicant
MODULE_FILE=/proc/modules
IFACE_DIR=/data/misc/wifi
DRIVER_MODULE_NAME=dhd
DRIVER_MODULE_TAG=dhd
FIRMWARE_LOADER=
[b]SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf[/b]
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
DRIVER_MODULE_PATH=/lib/modules/dhd.ko
MFGDRV_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt
DRV_AP_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_aps.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
DRIVER_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1
DRIVER_APS_FIRMWARE_NAME=bcm4329_aps.bin
DRIVER_STA_FIRMWARE_NAME=bcm4329_sta.bin
INTERFACENAME=eth0
WAPI_SUPPORT=false
[b]SUPP_CONF_FILEPATH=/data/misc/wifi/[/b]
SUPP_WAPI_AS_CERT_FILE_PATH=/data/misc/wifi/cert/as/
SUPP_WAPI_USER_CERT_FILE_PATH=/data/misc/wifi/cert/user/
SUPPLICANT_STATUS=wlan.supplicant.status
This tells me I would expect the conf file to be in /data/misc/wifi and the template to be in /system/etc/wifi.
Argh, this is very frustrating.

Code:
SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf
is what you are after.
-(e)

Sweetlime, would you mind elaborating?
Do you see your networks in that file on your device?
On every device and ROM that I've been able to inspect that file is just the template and contains no specific network information.

Sorry I am an idiot I copied the wrong line, that should have read:
Code:
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf

[null]

Related

[Q] Creating a custom ROM

Hello Everybody!
I'm sure this has been covered but I haven't found a tutorial or guide for the samsung captivate. I had ACL surgery today and I've decided i have the time to invest in creating a rom based on the things I like from other roms. Where do I start this process? Can i just mix files from within the .zips from other roms? or is there a file that tells the rom which files to install/access?
I've really enjoyed a lot of the ROM's that I have been flashing on my phone but I keep running into the same problem on all of them except one. Text messages occasionally go to the wrong person...and this is scary and unacceptable for me.
Some links to other threads or websites would be greatly appreciated.
Thank you for your time.
sdp07d said:
Hello Everybody!
I'm sure this has been covered but I haven't found a tutorial or guide for the samsung captivate. I had ACL surgery today and I've decided i have the time to invest in creating a rom based on the things I like from other roms. Where do I start this process? Can i just mix files from within the .zips from other roms? or is there a file that tells the rom which files to install/access?
I've really enjoyed a lot of the ROM's that I have been flashing on my phone but I keep running into the same problem on all of them except one. Text messages occasionally go to the wrong person...and this is scary and unacceptable for me.
Some links to other threads or websites would be greatly appreciated.
Thank you for your time.
Click to expand...
Click to collapse
Well, rom cooking is pretty easy.
As long as you know that component x is compatible with rom y, all you need to do is open the ROM in winrar/7z and drop the new file in, replacing the old one. No reason to unpack / repack. The only thing that can be a problem is the update-script, which resides in META-INF/com/google/android. It's a script that tells the phone "this is what you're doing with all of the stuff in this zip", if you modify a ROM like Axura or Perception, the update-script shouldn't need to be changed.
If you DO want to unpack and repack it, that's fine. Make sure you don't compress them into a sub directory (Update.zip > update > updates/system/meta-inf). Compress the updates/system/meta-inf/data whatever into it's own folder named whatever.zip, then sign the .zip via SignApk;
Code:
java -jar Signapk.jar certification.pem key.pk8 update.zip updatesigned.zip
Then flash it with CWM. Be aware however that in order for kernels(zImage) and modems(Modem.bin) and SBL(secondary boot loader) to be installed via CWM, the redband_ua exploit must be present in the updates folder; and the necessary commands for red_band must be present in the update-script.

[Q] Upgraded to "Overcome - Gingerbread", /efs folder empty

Hi guys,
Looking for helps here.
First I want to thank the guy created the "Overcome for Gingerbread", it comes w/ a great details instruction and I successfully upgraded.
My tab was original from Bell Canada, the phone feature was locked. I was able to unlock it by modifying the nv_data.bin file...
But now after I upgraded to Gingerbread, my phone feature is disabled again so I suppose I should do the whole unlock process again. However when I looked for the nv_data.bin file, the directory /efs is empty?!?!?!. Can someone help me here?
Thanks,
Edit: I found a nv_data.bin file on my laptop (not sure if it's the orginial one), trying to copy it to the /efs folder on the tablet, but I got error "not enough space"...
What program u using to copy with. Put that file on the SD card first from your PC.
Then get EF File Explorer rooted, and copy that from the SD card to the /efs directory
The nv_data.bin edit unlocks the tablet to allow use on other carriers like rogers, fido etc.
It does not provide phone usage, you need to flash a european rom to enable the phone,
then you need to flash a suitable modem to allow 3G data and phone, then edit your apn info.
Are you sure efs is empty, maybe your no longer rooted and can't see it?
You get the not enough space error because you have most probably renamed the original file and are trying to copy the new one in the directory. Delete the file and also the.md5 correspondent (it will be recreated on reboot.
P
Thanks for all the replies guys, but my problem is still there.
@Sonictab: I'm rooted and I'm sure that my /efs folder is empty.
@StarLog: I'm using Super Manager to copy the file
Now I can't even download files from the browser nor using the market place to download any apps. Something went wrong and I'm not sure what. Should I downgrade?

Wpa_supplicant problem returning to stock

I was trying to get my tab back to stock after messing it up. I was following the instructions off of gizmoninja but it says I have to download and install their wpa_supplicant file so I can flash the update.zip file. I am on DJ11 now. The link is bad that he posted. Does anyone know where to get this file from. This is my second day of searching. Thanks.
Sent from my SCH-I800 using XDA Premium App
I got the same problem,someone please help us with a original wpa_supplicant
why would you want to return to stock if your problem is wpa_supplicant? what has wpa_supplicant got to do with returning to stock?
When I return to stock dj11, the uodate to ec02 fails every time. The intructions I found said that it was a problem with the wpa_supplicant and it said to replace the file so the update would work. The link to the file does not work. Thats why we need it I suppose. Or, is there a better way to fix this?
Sent from my SCH-I800 using XDA Premium App
tombepa said:
When I return to stock dj11, the uodate to ec02 fails every time. The intructions I found said that it was a problem with the wpa_supplicant and it said to replace the file so the update would work. The link to the file does not work. Thats why we need it I suppose. Or, is there a better way to fix this?
Sent from my SCH-I800 using XDA Premium App
Click to expand...
Click to collapse
yes,the modified wpa_supplicant can't pass the update verify.
and hi tombepa,what baseband you're using?could you backup a copy of baseband and upload it here?i flash sprint baseband on mine ,and can't get it back,thanks.
Now I understand- you are on verizon gt .....sorry....
I am on S:I800.0.3V.DL21
And if someone can give instructions on how to back it up I would be glad to.
Sent from my SCH-I800 using XDA Premium App
I made a promise to myself to only lurk here from now on but I can't keep quiet for this one. First, I'm on my tab so I can't upload. Second, I'm sprint so I'm not sure which original wpa you people are asking g for. Third, when you put the modified file into the folder you are told to (did you remember to turn off wifi?), just rename the end of the original file .old or .bak or whatever (after telling file explorer program to go into rw mode of course), so the os won't run it and then just copy the modified file into that folder. Fourth, put the folder back into ro mode and reboot. I used to delete or overwrite files before but decided tacking .old at the end of the filename (works good for stock apks that you want to trial and error disable while testing for fc and stability when trying to lean down the programs loading). It's been much easier putting things back the way they were originally when I do it this way than ripping them out or overwriting them. Deleting or overwriting existing files and not having the original close by can many times come back and bite you in the ass. Flashing back to stock is a time consuming task that gets old really quick when you can't get whatever back into working condition.
Backing up is so simple. Just rename the original file to wpa_supplicant.old and copy over the modified one and reboot. Done. Want to revert? Do the opposite. Delete the modified file and rename the wpa_supplicant.old file to wpa_supplicant and reboot.
http://forum.xda-developers.com/showpost.php? p=7711198&postcount=6
Adb wasn't necessary for me. I got the file out of the 7zip and copied to the folder with root explorer. So easy even a caveman could do it.
Sent from my SPH-P100 using Tapatalk
Thank you for your ever so kind response, my question to you is will this file work on the Verizon tab? That is the one that I have. When I go to that link I can't tell which section that is in so I can read the rest of the posts there to answer this question myself.
I use the same file as shown by oscarthegrouch for sprint SPH-P100 and the file works fine,
but I can not be sure if used in Verizon tab
hopefully can help
Good news guys! I registered on gizmoninja and sent them a request. They fixed the download link. Go here and download it!
http://gizmoninja.com/2011/04/21/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
Sent from my SCH-I800 using XDA Premium App
Edit: and yes it worked!

wpa_supplicant.conf

Hi guys,
I'm having an issue with my wifi/bluetooth not turning on, and I've tried factory reset as well as flashing a bunch of different ROMS.
I went into my data/misc/wifi folder and found that I did not have anything where wpa_supplicant.conf should be
Can someone please upload a wpa_supplicant.conf for me?
Thanks!
You can check out this link
Revontheus said:
You can check out this link
Click to expand...
Click to collapse
thanks for the suggestion
I tried that but the issue I have right now is I simply don't have a wpa_supplicant.conf file
I've tried copying etc. and it says no such file and directory
I figured the easiest would be to get a wpa_supplicant file and flash it to whichever firmware it's from
this is the last thing I can think of before I take it to someone to get it repaired - unfortunately dealing with sony support has been a disappointing experience
(they said they changed their policy 2 weeks ago and no longer service international phones, but more importantly the phone has "physical damage" because I said that the port covers were worn and came off less than a year into using the phone regularly)
any help is appreciated
aama said:
Hi guys,
I'm having an issue with my wifi/bluetooth not turning on, and I've tried factory reset as well as flashing a bunch of different ROMS.
I went into my data/misc/wifi folder and found that I did not have anything where wpa_supplicant.conf should be
Can someone please upload a wpa_supplicant.conf for me?
Thanks!
Click to expand...
Click to collapse
I found the file you were after, but I don't know enough about it to say if it will help you or not.
This isn't a file to flash, I just couldn't upload a .conf file. So unpack it to the correct folder and don't forget to set the permissions.
The thing is you can't just "copy" it and it will work, it has to have the appropriate permissions for the while to be read and executed by the system, If memory serves me right its 0644 or rw-r-r permissions
Thank you all so much for taking the time to help me - I will try out the suggestions sometime next week after my exams and update!

How to fix bluetooth on cm13 (Or any other rom)/ How to fix amazon jem not recognized

Hello guys, I'm here to show you how to fix it without repeatedly turning it on and off. (I provided the stock bluetooth for you guys, that don't have it)
This is only for LTE jem, sorry for any convenience. (For bluetooth.)
1. Download this https://www.dropbox.com/s/29pw4nm27pgl8aj/Bluetooth fix.rar?dl=0
2. Extract it.
3. Replace /System/etc/Bluetooth/bcm2076_20mhz.hcd with BCM2076_26MHZ.HCD
4. Replace /System/vendor/firmware/bcm2076_20mhz.hcd with bcm2076_20mhz.hcd (The one I provided for you)
Then tada! Bluetooth works, you can only connect to compatible devices it seems but bluetooth finally works.
Now onto how to fix amazon jem not being recognized, on your pc/laptop.
I'm going to be honest here, this will be very short lol.
So anyways, go to this link https://windows10skill.com/kindle-fire-not-recognized-on-windows-10/#2 and follow the steps provided. Method 2 helped me, so try that first if you want. (This can work on windows 7 too, I forgot where I found it at but you can try following it still.)
That's all I have, for now. I hope all of you guys get everything fixed! Please let me know if this was helpful for you, I would appreciate it.
This RAR file won't open
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
bapi28 said:
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
Click to expand...
Click to collapse
Oh my god, I'm so sorry I forgot to mention this is only for lte devices. Sorry!
Understood step 4. But on step 3 when it states replace a file with a file having a different name, does that mean 1) delete original file and put new file in that folder, or 2) rename new file to existing files name and copy over top of existing file replacing it?
Ok, answered my own question and figured it out.
I did not have such a file in the /System/etc/Bluetooth folder.
I renamed the 26mhz file to 20mhz and replaced (overwrote) the file in the /System/vendor/firmware folder.
It is working great finally after issues for the past few years. Awesome. Thanks.

Categories

Resources