Related
Hi there
My knowledge of Android is very limited, I know a little about Linux from Ubuntu at command promt level, but not enough to fix this issue I'm having. Any help would be much appreciated.
I wish to modify a file which Android is telling me is locked. It's \system\etc\bluetooth\audio.config
I have found a modification to this file which may help me in connecting the Tab to a bluetooth peripheral I have.
I have rooted the Tab
I have installed a root file manager
I have installed a terminal app
I have tried to chmod this file when logged in as su, but this refused so still I cannot edit the file.
I read somewhere about mounting the system folder as rw, but this is a bit beyond my knowledge. So if this is necessary I need walking through this step-by-step.
Could someone please help me by posting some instructions to get me to the point where I can edit the file audio.config?
Many thanks
Gary
Sent from my GT-P1000 using XDA App
Is the program that you are using called ROOT EXPLORER? If so make sure that you have slected the MOUNT R/W icon on the top. Gray Colored.
Oh....and get Root explorer. LOL!
Perfect. I'm using root explorer already but as i just installed it i missed the toggle you highlighted.
Thanks for your help. I have now modified the audio.config file and my tab is now connected perfectly to my Creative D100 bluetooth speaker.
Thanks again
Gary
Sent from my GT-P1000 using XDA App
Dear garyj1972,
I recently bought a Samsung Galaxy Tab 10.1 and still getting used to the new settings. However I bought this bluetooth headset from we-com.net and it's model number is H580. I tried connecting it to my Tab but it doesn't even detect the headset when I try to find nearby devices. Well, I googled and googled stuff till I found very few similar queries by others (they're having this problem with few other BT headsets) and turns out that I have to edit some bluetooth config file and enable some things in it so the tab can detect my headset. I saw your post here about editing a config file and hence thought of asking you if you could help me out.
The tab's running on Android version 3.1
I hope you can help me out since am breaking my head on this from past two days. Any help will be much much appreciated.
Much thanks.
Your tab must be rooted to modify system files.
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Hmm. I have a mytouch 4G and the A500 connects to the hotspot easily. No mods, rooting etc. needing.
Is this in relation to phones that are using less than carrier proposed methods for enabling hotspots?
Hi Neo,
According to what I have had known so far, it seems that google blocks this function,
so someone modified the wap_supplicant to enable the hotspot functionality.
franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Solution 2 depends on your specific phone and its implementation. My Droid for instance doesn't support infrastructure hotspot (outbound), so I had to use the "magic wpa_supplicant" approach. Other phones may support infrastructure mode, either directly or through a 3rd-party wifi tether app.
In terms of solution 1 - if you get the wpa_supplicant (apparently a new version has been posted for those of us w/ 3.1 update) you also need to reset the permissions on the file to match that on the original file (which I know you backed up, right? ); easiest way would be through Root Explorer and set Read: (Owner/Group/Others), Write (Owner only) and Execute (Owner/Group). I'm too lazy to remember what the Terminal Emulator chmod command would be
As a reminder to all who do choose to replace wpa_supplicant, keep a copy of the original file, you never know when Acer's going to require a specific original file for any future updates (wpa_supp wasn't needed for the 3.0.1 update but was for 3.1)
Yes I would say do not delete or move the old file just rename by adding old to end of file name. Its how I done it renamed did the update changed back. And now all is well again.I used the same replacement file from before. No need for a new. Version
Hi Vereyn,
Thanks a lot.
Could you please provide the link to download?
Frankly, I have tried all wpa_supplicant in this forume.
None of them works for me.
My version is Android 3.0.1
Acer ICONIA A5011, rather than A500.
Cheers
franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Soo... Which rock have you been hiding under exactly? This is pretty old news, and there are already a few threads detailing exactly what you need to do... Hell, there's one on the first page of this forum section!
Dear Floating,
Could you please send the link to me? or at least give me the title of that article which
you are talking about?
Because it disappeared again now >_<;
Again,
yes there are many ad hoc articles, but none of them work for me....
franva said:
Again,
yes there are many ad hoc articles, but none of them work for me....
Click to expand...
Click to collapse
The links are in the forum, just scroll down a bit.
As for the articles not working... If they're not working for you, maybe you're doing something wrong or missing one of the steps?
Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Alpaca_Bandit said:
Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Click to expand...
Click to collapse
As you said, ifconfig changes it, there are several apps that do it for you as well, chainfire also released a mac randomizer app. You also noted it's hardwired in, so i would just have a startup script that changes it if i were you, there night be a better way to do it though.
Sent from my Tw5ted SM-G900A using Tapatalk
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Alpaca_Bandit said:
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Click to expand...
Click to collapse
You can just use init.d to make the script, shell scripting isnt very hard and i won't give you a tutorial here. Also as noted many places when researchng changing a mac on android, you can't connect to secured APs, or it won't be easy at least. As i said before, there may be a better way to do this, but i do not know it.
Sent from my Tw5ted SM-G900A using Tapatalk
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Alpaca_Bandit said:
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Click to expand...
Click to collapse
I know on for example ddwrr and even some official router firmwares they allow you to spoof your mac, may be worth looking into how they do it, but i have a suspicion it might be done with a script.
Sent from my Tw5ted SM-G900A using Tapatalk
Hard Wired?
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
MAC for bt and wifi reside in the EEPROM or NVRAM. And that is not editable.
To put it simply you can't change it. Only spoof it. And if you know it's not legal you probably shouldn't be asking.
Reported Is different from original
gscripting said:
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
Click to expand...
Click to collapse
More info relative to these 2 phones
I installed an app called Change my Mac.
It Lists:
Original MAC 12:34:56:78:90:ab
Current MAC ff:ee:dd:cc:bb:aa
They Are Different.
I thought the original MAC address it's showing, was the one written in the EEPROM or NVRAM,
but it turns out, after installing Change My MAC on the other phone also, its lists the same Original and Current MAC addresses as the first phone.
The Current MAC address listed is the one reported in settings and my network.
I Use Change My MAC to set the reported MAC to the original every time the phone boots using Tasker on only one of them.
Using Change My MAC, the change lasts til boot.
Just passing it on for those that might be interested.
When I get link privileges, I'll add a screenshot of Change My MAC.
gscripting
Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.
lalontra said:
Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.
Click to expand...
Click to collapse
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.
DEVILOPS 007 said:
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.
Click to expand...
Click to collapse
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.
lalontra said:
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.
Click to expand...
Click to collapse
Have you tried forgetting your WiFi network and connecting again with the psk?
DEVILOPS 007 said:
Have you tried forgetting your WiFi network and connecting again with the psk?
Click to expand...
Click to collapse
If I hit known network in android wifi options I can see all my previously stored wifi. Everything works perfectly. If I add new networks they will be added with no issues and remembered for ever and ever. (and obviously will not be added to the file). It is like this list is just somewhere else now on the phone.
I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.
Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043
dechronic said:
I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.
Click to expand...
Click to collapse
I have created an app that supports both devices below and over the android Orio, give it a try from this thread -
https://forum.xda-developers.com/android/apps-games/app-wifi-password-view-saved-wifi-t3852668
Hotfingers said:
Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043
Click to expand...
Click to collapse
Great App!
They are now stored in:
/data/misc/wifi/WifiConfigStore.xml
Hello, How R U, Hope all are well.
My S7Edge have problem, Bluetooth dont work.
If I touch Bluetooth icon, nothing changes, at all.
I use SuperMan2.8 ROM by (Tkkg1994), used many kernels (NT, SuperStock, SuperMan)
I found some errors regarding it in the log, with Error flag.
I've checked with the ROM developer, and informed me that he didn't modified any of Samsung BT modules.
The problem is increased when I checked the Battery usage, to see that BT in consuming battery (some times same as screen).
1) Is Bluetooth hardware have problem?
2) Any software solution is available? or can be fixed?
3) If there is no solution, is it possible to software-disable Bluetooth chip?
Please, kindly download the log file from here, generated by aLogcat app.
Thanks in advance.
1) Download the correct modem/kernel/bl for that rom if you have not done so.
2) Delete your bluetooth config / pairings file (dont know location or name off top of my head)
Do a hard reset and restore your phone to its original (factory level) settings. This might work.
autonomousperson said:
1) Download the correct modem/kernel/bl for that rom if you have not done so.
2) Delete your bluetooth config / pairings file (dont know location or name off top of my head)
Click to expand...
Click to collapse
1) I've downloaded recent BL and Modem and the kernel with the ROM, and Didn't work,
2) There is NO Bluetooth history .
RossTeagan said:
Do a hard reset and restore your phone to its original (factory level) settings. This might work.
Click to expand...
Click to collapse
How can download the 4-files with recent update, that suits my device?
mohgaza said:
How can download the 4-files with recent update, that suits my device?
Click to expand...
Click to collapse
Why do you need to download them?
Do a factory reset, restore your phone to its initial settings and then perform any update you find necessary. There is no need to copy or downloads extra files.
mohgaza said:
1) I've downloaded recent BL and Modem and the kernel with the ROM, and Didn't work,
2) There is NO Bluetooth history .
Click to expand...
Click to collapse
Delete the pairings configuration + pairing file, its a file......
Sorry dont know it off the top of my head, look in /data its a similar file and structure to/data/misc/wpasupplicant.conf(wifi config and pairings )
this also happened to me .. even after i drop to MM still remain like this..what should i do please help me..battery be wasteful