Hello.
I try many rom, but I have the problem with proximity sensor in my galaxy S (i9000).
I change the hardware (proximity sensor with 3.5 audio jack), but problem still.
Then I answer to call the phone freez, and the screen goes black.
I found the file in system/lib/hw/ sensors.default.so
In this file is all information about all sensors, then I delete this file the problem with this sensor is gone, but not work all sensors (rotate, etc).
How I can edit this file to delete information only about proximity sensor?
Maybe somebody can send the file sensors.default.so without proximity sensor information?
Thank You
Mine does exatly the same. I am not sure, but I believe my Galaxy S has sustained salt water damage to the microusb port, and just below that as you know is are the light and proximity sensors. I am pretty sure this is why it's playing up exactly as you describe.
I do flash a fair bit though, so it may simply be firmware related, I am yet to find out, but i doubt it.
Did anyone find fix for this one as mine i9000 does same thing
oxio said:
Did anyone find fix for this one as mine i9000 does same thing
Click to expand...
Click to collapse
The problem in the motherboard.
I change the motherbord of my I9000
poliusss said:
The problem in the motherboard.
I change the motherbord of my I9000
Click to expand...
Click to collapse
Where did you find it, i tried ebay and google without luck.
oxio said:
Where did you find it, i tried ebay and google without luck.
Click to expand...
Click to collapse
I buy other phone with broken screen.
I managed to disable only proximity sensor on my i9000 with cm7.
So here is how to make it if somebody need it.
IMPORTANT: Make backup of your firmware!
Requirements:
Root-ed phone
File manager with acess & permitions to write to system (i used ES File Explorer)
PC with HEX Editor
Steps:
1. With superuser grant acess to ES File Explorer
2. In ES File Explorer go to settings and togle all 3 boxes in category Root settings
3. Navigate to root of your device
4. Go to system/lib/hw/
5. Copy sensor.aries.so to sdcard
6. Transfer on computer and open file sensor.aries.so in HEX editor
7. Find all parts where ProximitySensor is mentioned, do not delete it only replace ProximitySensor to PPPPPPPPPPPPPPP (it can be anything but we must keep number of letters exact like original so anything with 15 characters is ok)
8. Save file sensor.aries.so to sdcard
9. Replace sensor.aries.so on your phone with this modified version
10. Reboot phone
11. Make test call and see only proximity sensor is disabled
In attachment is file i made, please note i made it for my I9000 with CM 7.2 so i dont know will it work for other firmwares.
@ poliusss - thanks for pointing to system/lib/hw/ sensors.default.so it helped me a lot.
oxio said:
I managed to disable only proximity sensor on my i9000 with cm7.
So here is how to make it if somebody need it.
IMPORTANT: Make backup of your firmware!
Requirements:
Root-ed phone
File manager with acess & permitions to write to system (i used ES File Explorer)
PC with HEX Editor
Steps:
1. With superuser grant acess to ES File Explorer
2. In ES File Explorer go to settings and togle all 3 boxes in category Root settings
3. Navigate to root of your device
4. Go to system/lib/hw/
5. Copy sensor.aries.so to sdcard
6. Transfer on computer and open file sensor.aries.so in HEX editor
7. Find all parts where ProximitySensor is mentioned, do not delete it only replace ProximitySensor to PPPPPPPPPPPPPPP (it can be anything but we must keep number of letters exact like original so anything with 15 characters is ok)
8. Save file sensor.aries.so to sdcard
9. Replace sensor.aries.so on your phone with this modified version
10. Reboot phone
11. Make test call and see only proximity sensor is disabled
In attachment is file i made, please note i made it for my I9000 with CM 7.2 so i dont know will it work for other firmwares.
@ poliusss - thanks for pointing to system/lib/hw/ sensors.default.so it helped me a lot.
Click to expand...
Click to collapse
Could you please tell me what Hex Editor did you use and how did you edit it? I have an hardware issue related to compass and I would like to block al readings.
I used HexEdit v1.03 found it online its free tool so i attach it here.
Opened sensors.aries.so with it and searched for proximity sensor and replaced characters by letter P
In find function of program it is important to use big and small caps, so you must search for: CompassSensor
and replace it by: CCCCCCCCCCCCC
I attach you here file with only compass disabled but please make backup before as i didnt test it.
Hope it will solve your problem
oxio said:
I used HexEdit v1.03 found it online its free tool so i attach it here.
Opened sensors.aries.so with it and searched for proximity sensor and replaced characters by letter P
In find function of program it is important to use big and small caps, so you must search for: CompassSensor
and replace it by: CCCCCCCCCCCCC
I attach you here file with only compass disabled but please make backup before as i didnt test it.
Hope it will solve your problem
Click to expand...
Click to collapse
Thank you for your help and for your quick replay
I've tried to edit file using your tutorial but no luck (stuck at boot animation), the good news is that your edited sensors.aries.so it's compatible with aokp i've tested and is working...but proxymity sensor and light sensor are also dead , also my problem remains there even with no proximity and no light sensor because I still get some readings even if my compass won't move (gps status detect activity on mag. field)
Try to delete sensors.aries.so and restart phone it will disable all sensors, if then problem stops than its posible to change sensors.aries.so to correct it, only trick is to find what you must modify.
I modified file you attached also find and changed magnetic sensor in it so disabled it try now
File is in attachment.
oxio said:
Try to delete sensors.aries.so and restart phone it will disable all sensors, if then problem stops than its posible to change sensors.aries.so to correct it, only trick is to find what you must modify.
I modified file you attached also find and changed magnetic sensor in it so disabled it try now
File is in attachment.
Click to expand...
Click to collapse
Thank you, I forgot to mention...I've updated my kernel to semaphore 1.1.0 and since then my phone behaves almost normal (compass show me wrong direction but at least no longer resets itself )
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
Preferably the g900a 4.4.2 version of it, just to be safe?
After messing up the file, i deleted it because i thought it would automatically regenerate (i know, i know...) when i restarted, everything crashed, so i couldnt do anything with the phone... after doing a factory reset that did nothing, i tried reflashing with Odin, it did reflash, but the issue was still there (upon restart every background app crashes and crashes), I used Odin to only reflash the "AP" file... so maybe i have to update a different one? anyway...
I finally fixed it with a platform.xml file that was "reinstalled" as a .zip via recovery... I used the one in this link: http://forum.xda-developers.com/showthread.php?t=2607215
Now the only issue that im apparently having is that i cant use the Fingerprint reader (which worked flawlessly before my screw up) So im guessing it was affected by the "fix"...
Im guessing replacing the file would fix this :/ maybe
This one also has the sdcard permissions added. You could probably swap it with the other platform file in the zip and just reflash it. There are several ways to add that file to the system/etc/permissions folder, but will crash your phone again if done incorrectly. Also, the platform file that you used was for the S4, which does not have a fingerprint scanner, which would explain why yours do not work now.
shortydoggg said:
This one also has the sdcard permissions added. You could probably swap it with the other platform file in the zip and just reflash it. There are several ways to add that file to the system/etc/permissions folder, but will crash your phone again if done incorrectly. Also, the platform file that you used was for the S4, which does not have a fingerprint scanner, which would explain why yours do not work now.
Click to expand...
Click to collapse
Thanks thats what i thought about the fingerprint scanner !
I replaced the platform.xml file in the .zip and updated via recovery, but sadly the fingerprint scanner still doesnt work...
I try the *#0*# and says version: null
badillin said:
Thanks thats what i thought about the fingerprint scanner !
I replaced the platform.xml file in the .zip and updated via recovery, but sadly the fingerprint scanner still doesnt work...
I try the *#0*# and says version: null
Click to expand...
Click to collapse
Yea, the only sure way to fix that is to backup your user apps and data, call logs and messages with Titanium, along with your storage to a computer with a file explorer, and flash the downgrade to NCE file (or the AP, CSC, and maybe CP files files for the NCE downgrade). It'll wipe the phone, but it will fix everything. Or, you'll just be without a fingerprint scanner.
I made a similar error with the same platform.xml file. Seems once it's broke, it's not fixable without reflashing.
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.
I have a Pixel 5.
The stock rom does not have South Korean carrier mbn files.
I managed to source the files from the Internet.
I tried to copy paste it into
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
but it doesn't work (I can't change folder properties to write).
I tried using the volte_switch.zip from this guide
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Update (9 Oct 2022): Upload module here. Update (7 Apr 2021): If you are looking for the manual way to add 5G support besides the magisk module way or the module does not work for you. Please refer to #54 for the detailed steps. Thanks again to...
forum.xda-developers.com
and modified the files to add the mbn files of my choice but flashing the zip deletes all folders under generic/Pixel/ except my country's folder.
Removing the "module" from magisk manager and rebooting brings everything back.
Is it possible to make a flashable zip to add the mbn files?
Or does it require repacking the radio.img?
Or does the volte_switch.zip install the mbn files systemlessly?
If you post your Magisk module it might be easier to say why it doesn't work.
But if the Pixel directory is emptied out it sounds like you have a replace file in there causing issues. Just guessing though...
Didgeridoohan said:
If you post your Magisk module it might be easier to say why it doesn't work.
But if the Pixel directory is emptied out it sounds like you have a replace file in there causing issues. Just guessing though...
Click to expand...
Click to collapse
Thanks for the suggestion. I've uploaded the flash zip file as well. When I went through the install script, I did notice the "replace" code in there. How should I change it to?
Ok after much googling, I figured out.
I added in all my original mbn folders as well and then typed in:
REPLACE="
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/
"
into customize.sh
This Replaced the folder with all the original and new mbn files.
Ok, I thought it worked but it's not actually working.
The new mbn files seems to be there but when I force a mbn reload by changing sim cards, it still loads the "original" files as if the new files aren't actually there.
For countries/carriers that's not listed in google's official supported list, the phone uses a 'generic' carrier mbn which is located in the generic/pixel/common/wildcard/pixel_wildcard/mcfg_sw.mbn.
This wildcard mbn is the generic carrier file that has 5G disabled by default. So in theory, all I need to do is replace the wildcard mbn with a different carrier's mbn which has 5G enabled by default. Then create magisk module and flash it to have it replaced.
My module appears to replace the files but the new files don't actually get loaded. When I change sim cards to force a reloading of mbn file, It still loads the old files.
What can I do to fix this? Any help is appreciated. Thanks.
Attached is my module.
Calling @Didgeridoohan good sir, if you could kindly provide me with knowledge about the post above, if possible. Thanks.
swangjang said:
Calling @Didgeridoohan good sir, if you could kindly provide me with knowledge about the post above, if possible. Thanks.
Click to expand...
Click to collapse
Busy life...
In theory you shouldn't at all need to do that replace function and add back all the stock files with the module. Magisk should take care of mounting or replacing only the files you need, so anything else is just redundant... But if it works, sure.
But it seems like it doesn't.
If you can verify with a file explorer that the files have been replaced with the ones from your module and the values still are taken from the original files that very likely means that there's more to it than just replacing those files.
You could provide the module install log and the Magisk log (Canary release so that it's actually useful) to see if there's anything wrong there.