I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
If you didn't say you mounted the partition I can only assume it was not mounted as r/w and still at r/o.
copy/paste - visual representation of cp
push - pushing files from computer to phone
They are not the same.
SiNJiN76 said:
I didn't feel like plugging my phone into the computer so I emailed myself an apk file (arctu's Mms.apk) because for some reason...it seems to revert back to stock every reboot...
Anyway, I didn't have any terminal apps so I used Root Explorer to copy then paste over the existing apk. didn't work. Why not? Is there a something different about copy/paste?
Click to expand...
Click to collapse
Yeah, what didn't work? lol.
djmcnz said:
Yeah, what didn't work? lol.
Click to expand...
Click to collapse
the mms app didn't overwrite. But it could have been user error. I'm using Enom's ROM and didn't have the Community Mms Mod checked...so maybe if I had done that first...it would have worked.
Pushing is taking a file from the computer to copy and paste/overwrite the existing file on the phone. What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
SiNJiN76 said:
Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
k?
I didn't try and explain anything (in this thread at least)?
Either way, yes push literally "pushes" a file to a specified location. However that file needs to be written and if the file system is mounted as read only you will get errors.
If it didn't work you must have received an error message (in root explorer for example), what was that message? If you don't get an error message and the file is still not being written then get a better file manager (ES File Explorer).
The suggestion above by 'evilkorn' was to make sure the file system is in read/write mode before you copy the file over... you can do this in Root Explorer or ES File Explorer.
If your file system is in r/w AND you still don't get an error message AND it still doesn't work then I would try an ADB push as a last resort and if that didn't work, reflash and start from step one I think...
SiNJiN76 said:
What's the difference where the file is being copied over from? Are you sure about what you were trying to explain?
Click to expand...
Click to collapse
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
evilkorn said:
Because that was your question in the title, which I answered, they are different terms for different things. You can't push a file on your phone to your phone, you copy it (cp).
You still didn't answer my question... It's hard to help someone when the suggestions fall on deaf ears and all you get is reverb and static back.
Click to expand...
Click to collapse
LoL. You gotta ask a question first before I can answer it. You made assumptions, didn't ask questions. LoL. Anyway, I wasn't trying to crawl under your skin. But maybe next time you can read the OP in addition to just reading the title of the thread? Usually, details are given to accompany the title of the thread on the first post. Either way, I guess I wasn't detailed enough. Thanks for your feedback, tho, appreciate it.
@djmcnz - Sorry, my error in quoting the wrong person. Thanks for you explanation, also.
So, to summarize...Push and Copy/Paste should produce the same outcome, right? Cool...like I said earlier...it was my error in not knowing that I had to use the Spare Parts option in Enom's ROM to enable Community MMS.
I use root explorer all the time when I can't use a computer to use adb. It works fine. Usually if its the system partition you have to click the icon that says r/o and it changes to r/w. This will allow you to write files to the partition. Then from what I noticed a reboot usually fixes any issues of stuff not working.
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?
Hi, im running JB VSLP9 (Movistar Argentina firmware) and recently i decided i should backup efs and modemfs just in case. I followed the steps in this guide http://forum.xda-developers.com/showthread.php?t=2342100
I don't know if this is related but recently i've been having some problems with 3G connectivity. Sometimes the phone shows good signal but no data connection. You have to restart the phone to correct this. Also, some people have told me that calling me directs them straight to voice mail.
I was looking at my modemfs folder and then discovered that it is empty! 0 files, 0 bytes. So i tried to restore the backup that I made (16mb). But nothing changed, the folder is still empty ....
Is this normal ??? Can my problems be related to the "backup" of efs and modemfs ????
Thanks
Can anyone at least check your modemfs folder and tell me its contents ?
Piachnp said:
Can anyone at least check your modemfs folder and tell me its contents ?
Click to expand...
Click to collapse
Here you go.
But I do not know how to fix yours...
Thanks Shutdown, i tried wiping everything and flash the firmware again, but the modemfs folder is still empty... That crappy backup guide ****ed up everything
Does anyone know if i can ask for someone using the same firmware for the contents of this folder and copy them to my phone ????
Piachnp said:
Thanks Shutdown, i tried wiping everything and flash the firmware again, but the modemfs folder is still empty... That crappy backup guide ****ed up everything
Does anyone know if i can ask for someone using the same firmware for the contents of this folder and copy them to my phone ????
Click to expand...
Click to collapse
Maybe you need to mount modemfs partition before restoring? Look how to do that (trough terminal emulator, or ADB shell).
I have been trying out a few custom roms, and both Slimrom and cyanogenmod both have non-function WiFi and Bluetooth. I have no idea why my Verizon Wireless developer edition Moto x has so many issues with this, while everyone else seems to have functioning WiFi and Bluetooth on different models of the Moto x, such as XT1058, etc. I do not know what is so different on the XT1060 that prevents the WiFi and Bluetooth from working. Both threads for both of those roms on xda have no people complaining about WiFi and Bluetooth that won't even turn on. I have tried like every build, and have done clean wipes every time before, and still nothing. Every time I try to turn on the WiFi on from settings, the switch goes to right to the on position but is always grayed out, and WiFi routers never appear on the list. According to kernel log files, the Bluetooth driver just crashes without warning, and the WiFi driver does not have required firmware to run. So what can I do to solve this problem, and also does anyone else experience this problem? Thanks.
Just for reference, here is part of the log that talks about wlan:
[ 2931.926781,0] wlan: module is from the staging directory, the quality is unknown, you have been warned.
[ 2931.959163,0] wlan: loading driver v3.2.7.47
[ 2931.985685,0] wlan: [1006:E :HDD] hdd_apply_cfg_ini: Reg Parameter gEmptyScanRefreshPeriod < allowed Minimum [0 < 1000]. Enforcing Default= 0
[ 2932.006897,0] wlan: [1006:F :HDD] hdd_request_firmware: nv wlan/prima/WCNSS_qcom_wlan_nv.bin download failed
[ 2932.006988,0] wlan: [1006:F :VOS] vos_nv_open: unable to download NV file wlan/prima/WCNSS_qcom_wlan_nv.bin
[ 2932.007110,0] wlan: [1006:F :VOS] vos_open: Failed to initialize the NV module
[ 2932.065954,1] wlan: [1006:F :HDD] hdd_wlan_startup: vos_open failed
[ 2932.066534,1] wlan: [1006:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[ 2932.066808,1] wlan: driver load failure
FleetPhone said:
Just for reference, here is part of the log that talks about wlan:
[ 2931.926781,0] wlan: module is from the staging directory, the quality is unknown, you have been warned.
[ 2931.959163,0] wlan: loading driver v3.2.7.47
[ 2931.985685,0] wlan: [1006:E :HDD] hdd_apply_cfg_ini: Reg Parameter gEmptyScanRefreshPeriod < allowed Minimum [0 < 1000]. Enforcing Default= 0
[ 2932.006897,0] wlan: [1006:F :HDD] hdd_request_firmware: nv wlan/prima/WCNSS_qcom_wlan_nv.bin download failed
[ 2932.006988,0] wlan: [1006:F :VOS] vos_nv_open: unable to download NV file wlan/prima/WCNSS_qcom_wlan_nv.bin
[ 2932.007110,0] wlan: [1006:F :VOS] vos_open: Failed to initialize the NV module
[ 2932.065954,1] wlan: [1006:F :HDD] hdd_wlan_startup: vos_open failed
[ 2932.066534,1] wlan: [1006:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
[ 2932.066808,1] wlan: driver load failure
Click to expand...
Click to collapse
The problem is highlighted in red. You have somehow erased your WCNSS_qcom_wlan_nv.bin file.
You will need to get these files from another user, and place it in your /persist folder. This is the only way wifi and bluetooth will ever work for you.
samwathegreat said:
The problem is highlighted in red. You have somehow erased your WCNSS_qcom_wlan_nv.bin file. This file contains your WIFI MAC address. You likely somehow also deleted the bluetooth MAC as well.
You will need to get these files from another user, and edit them with YOUR mac address. This is the only way wifi and bluetooth will ever work for you.
Click to expand...
Click to collapse
But I did not do anything other than flash the rom and that's it. It came like that with the rom. So I tried coping the wlan firmware files from stock, and that did not do anything. It still refuses to start. I will try some other things.
FleetPhone said:
But I did not do anything other than flash the rom and that's it. It came like that with the rom. So I tried coping the wlan firmware files from stock, and that did not do anything. It still refuses to start. I will try some other things.
Click to expand...
Click to collapse
It won't do any good. Those files are located in the persist partition.
It is called the persist partition for a reason. When you flash a new rom, persist is unaffected. It is unique to YOUR phone, and your phone only. You can flash the stock rom as many times as you would like but the persist folder stays untouched.
I don't have any idea how this happened to you, but it is most definitely your persist folder. You would HAVE to be rooted/unlocked for this to have happened.... I can only guess that you somehow erased or formatted /persist.
Do you have "Root Browser" installed? If so, browse to the "persist" folder. What files are inside?
See here: http://forum.xda-developers.com/showthread.php?t=2619553
samwathegreat said:
It won't do any good. Those files are located in the persist partition.
It is called the persist partition for a reason. When you flash a new rom, persist is unaffected. It is unique to YOUR phone, and your phone only. You can flash the stock rom as many times as you would like but the persist folder stays untouched.
I don't have any idea how this happened to you, but it is most definitely your persist folder. You would HAVE to be rooted/unlocked for this to have happened.... I can only guess that you somehow erased or formatted /persist.
Do you have "Root Browser" installed? If so, browse to the "persist" folder. What files are inside?
Click to expand...
Click to collapse
Yes I do, and the persist partition has 3 files in it. They are named .bt_nv.bin, WCNSS_qcom_wlan_nv_calibration_persist.bin, and WCNSS_qcom_wlan_nv_regulatory_persist.bin. However, when I restore back to stock rom after I am done testing with the broken rom, the stock WiFi works just fine, even with that same persist folder. So if it has something to do with persist folder, then I have no idea what is wrong. Should I not wipe system before I install my rom?
FleetPhone said:
Yes I do, and the persist partition has 3 files in it. They are named .bt_nv.bin, WCNSS_qcom_wlan_nv_calibration_persist.bin, and WCNSS_qcom_wlan_nv_regulatory_persist.bin. However, when I restore back to stock rom after I am done testing with the broken rom, the stock WiFi works just fine, even with that same persist folder. So if it has something to do with persist folder, then I have no idea what is wrong. Should I not wipe system before I install my rom?
Click to expand...
Click to collapse
You only have 3 files??? Because my X has 4 files:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Just as I had said in my very first reply, you are missing WCNSS_qcom_wlan_nv.bin
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
Here: http://forum.xda-developers.com/attachment.php?attachmentid=2760949&d=1400950032
Download the file, and place JUST the missing file back in /persist
The permissions should be: rw-r--r-- (permissions must be set correctly)
Does WiFi work now??
samwathegreat said:
You only have 3 files??? Because my X has 4 files:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
Click to expand...
Click to collapse
Indeed, there is only 3 files in that folder. However, there is WCNSS_qcom_wlan_nv.bin file in system/etc/firmware/wlan/prima that is system linked to the persist folder. However, that bin file is 0 bytes, which is pretty suspicious. If there is another file suppose to be there, how could I get it back? Do you get a persist folder when you do a factory image restore (such as restoring .img files using fastboot)? I do not think I ever touched the folder, but maybe something went wrong.
FleetPhone said:
Indeed, there is only 3 files in that folder. However, there is WCNSS_qcom_wlan_nv.bin file in system/etc/firmware/wlan/prima that is system linked to the persist folder. However, that bin file is 0 bytes, which is pretty suspicious. If there is another file suppose to be there, how could I get it back? Do you get a persist folder when you do a factory image restore (such as restoring .img files using fastboot)? I do not think I ever touched the folder, but maybe something went wrong.
Click to expand...
Click to collapse
See the edit to my previous post. I linked the file you need. MY WCNSS_qcom_wlan_nv.bin file is 29.08KB.
Please try copying that file into your persist folder, and then changing permissions as I advised in the last post. Reboot and advise if WiFi is working now.
samwathegreat said:
See the edit to my previous post. I linked the file you need. MY WCNSS_qcom_wlan_nv.bin file is 29.08KB.
Please try copying that file into your persist folder, and then changing permissions as I advised in the last post. Reboot and advise if WiFi is working now.
Click to expand...
Click to collapse
Yes WiFi now works, It is just strange that WiFi worked on stock 4.4.2 without that file present in the persist folder. And I just used a Motorola factory image like a day or two ago with fastboot. Strange. Well Bluetooth also works. Thanks, however how do you get a "new" persist folder? Do you get it from the Motorola factory image, or is it impossible.
FleetPhone said:
Yes WiFi now works, It is just strange that WiFi worked on stock 4.4.2 without that file present in the persist folder. And I just used a Motorola factory image like a day or two ago with fastboot. Strange. Well Bluetooth also works. Thanks, however how do you get a "new" persist folder? Do you get it from the Motorola factory image, or is it impossible.
Click to expand...
Click to collapse
It is impossible. Something went wrong and the file got erased at some point. You SHOULD NOT have to do this again. /persist stays untouched between ROM flashes. Not even using RSD Lite to restore back to 100% stock touches the persist folder.
If you leave it alone, it should stay working forever, unless you somehow delete it. You cannot get it from the factory images...fortunately you were lucky enough to have someone willing to help you and "donate" the file from their phone
samwathegreat said:
It is impossible. Something went wrong and the file got erased at some point. You SHOULD NOT have to do this again. /persist stays untouched between ROM flashes. Not even using RSD Lite to restore back to 100% stock touches the persist folder.
If you leave it alone, it should stay working forever, unless you somehow delete it. You cannot get it from the factory images...fortunately you were lucky enough to have someone willing to help you and "donate" the file from their phone
Click to expand...
Click to collapse
So Now I have 4 files, plus that lost+found folder that is always there. The other two files, not the .bt or the wlan_nv, permissions are lrwxrwxrwx and system linked to somewhere. Is that correct, the permissions? And from the log, It seemed that the phone tried to download a new WCNSS_qcom_wlan_nv.bin one from somewhere, but failed to do so. Thanks for your help, now these custom roms will actually operate as they should.
FleetPhone said:
So Now I have 4 files, plus that lost+found folder that is always there. The other two files, not the .bt or the wlan_nv, permissions are lrwxrwxrwx and system linked to somewhere. Is that correct, the permissions? And from the log, It seemed that the phone tried to download a new WCNSS_qcom_wlan_nv.bin one from somewhere, but failed to do so. Thanks for your help, now these custom roms will actually operate as they should.
Click to expand...
Click to collapse
Yes, those are the correct permissions. You are all set!
I AM very confused as to why the stock ROM worked for you without the missing file, but it is supposed to be present on every Moto X.
You should be able to change roms all you like and the WiFi should "Persist" (haha)
Just FYI, my /persist folder has this:
data (folder)
lost+found (folder)
omadm (folder) - I believe this is unique to Sprint devices
omadm_cust_database (folder) - also possibly unique to Sprint devices
omadm_database (folder) - another possible Sprint-only folder
prop (folder)
prov (folder
usf (folder)
and then the 4 files I listed earlier
I wonder if you formatted or erased /persist at some point?? Wonder why you don't have all the folders I have...
As long as everything is working, I guess it isn't a problem...strange though...maybe ALL those folders are unique to Sprint devices?
samwathegreat said:
Yes, those are the correct permissions. You are all set!
I AM very confused as to why the stock ROM worked for you without the missing file, but it is supposed to be present on every Moto X.
You should be able to change roms all you like and the WiFi should "Persist" (haha)
Just FYI, my /persist folder has this:
data (folder)
lost+found (folder)
omadm (folder) - I believe this is unique to Sprint devices
omadm_cust_database (folder) - also possibly unique to Sprint devices
omadm_database (folder) - another possible Sprint-only folder
prop (folder)
prov (folder
usf (folder)
and then the 4 files I listed earlier
I wonder if you formatted or erased /persist at some point?? Wonder why you don't have all the folders I have...
As long as everything is working, I guess it isn't a problem...strange though...maybe ALL those folders are unique to Sprint devices?
Click to expand...
Click to collapse
Mine Is a Verizon phone, so that could be why. Also the early versions of twrp may have wiped everything once as it was not offically supported at the time. Explains all those weird Motorola errors I would get when fastbooting ( I fixed those eventually). I hope I don't need any more files, I would need to hunt them down. And now have an official twrp recovery. But thanks anyway.
Some older Philz & CWMR recoveries let you format persist!!
wifi bluetooth problems!!
I'm having the same issue, but reading the posts is very confusing, if someone can post the step by step to be done I would appreciate it. For months I am with this problem out, what caused me to increase my data plans by not being able to use wifi. PLIS I NEED SOME HELP =(
hannoshi said:
I'm having the same issue, but reading the posts is very confusing, if someone can post the step by step to be done I would appreciate it. For months I am with this problem out, what caused me to increase my data plans by not being able to use wifi. PLIS I NEED SOME HELP =(
Click to expand...
Click to collapse
Well, first you will need to use a file manager to look inside the persist folder, which is located in the root directory. You must have these 4 files:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
If they are there, you should be fine. If you still have a problem, then this solution is not for you.
Help ... I'm having the same problem
samwathegreat said:
See the edit to my previous post. I linked the file you need. MY WCNSS_qcom_wlan_nv.bin file is 29.08KB.
Please try copying that file into your persist folder, and then changing permissions as I advised in the last post. Reboot and advise if WiFi is working now.
Click to expand...
Click to collapse
Hello friend!
I'm new here, I'm having the same problem, however I downloaded files from your MOTO X and put it in my folder PERSIST, then I put the Wi-Fi only worked twice. Do not know if it was something wrong that I did more I changed some files in the folder (/ system / etc / firmware / wlan / prima) I replaced the file with the WCNSS_qcom_wlan_nv.bin has PERSIST in the folder ... directory (/ system / etc / firmware / wlan / prima) got the files (WCNSS_CFG.dat, WCNSS_qcom_cfg.ini, WCNSS_qcom_wlan_nv.bin), you could make available the files in this directory? Or do you have another suggestion?
Note! There are times that the bluetooth connects any device located not more, then it stops working.
Wifi and bluetooth also not work on Moto X XT 1049 - Republic Wireless
All,
I've got the identical problem on a Moto X XT 1049 from Republic Wireless: unable to get wifi and bluetooth to go on.
1) Do you think it is possible that the file provided in this thread, for a 1060, would work on my 1049?
2) How do I put that file in the persist directory? My phone is not currently rooted.
(I'm a relative newbie so spell it out for me, if you don't mind. Much appreciated).
Ernie
Same WiFI Problems
I Have XT 1058 device and I've got same WiFI issues(4.4.2). In my /persist folder have:
Prov(folder)
usf(folder)
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
The problem is, the last 2 files in the list, have a size of 0.00 B
I Have replaced them with the files provided from samwathegreat(and following the -rw-r--r-- permissions), but when i restart or shutdown, the files appears as if i haven´t done any change (0.00 B Size again)
I also replace WCNSS Files(except cfg.dat and cfg.ini) on system/etc/firmware/wlan/prima with the ones provided, 3 of them had 0.00 Size, but fortunately the changes persists after reboots or shuwtdown.
I'll really appreciate your help, sorry for my awfull english
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.