yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] UsPdSr:
The support of an external wireless interface works flawless.

At least if you went according to installation instructions and downloaded, in case of LineageOS 17.1, the correct build.

Then you have to copy the fstab over.

Either per Mtp or a flash drive.

The usage of ifconfig to set a interface into a specific mode is deprecated and replaced by 'iw' and 'ip'.

If you're not familiar with the syntax, look through the Nethunter thread's here, or type it into a search engine of your preference.

Ralink chipset's/driver in general, are perhaps the most easiest to build for a kernel.

You don't need any additional firmware modules of the Magisk repo.Just proceed according to the instructions and some of the additional information on the first page and you should be able to get every supported nic working. :)

Annotation

Pixel Experience 10 is working fine with the newly released kernel as well.

Some minor security related installation issues, like the manual re-installing of the Nethunter application.

In some cases did I loose root, but I prefer to flash kernel and chroot/data seperate.

The man with an exemplary track record, Re4son, did update the Nexmon scripts for our kernel, from what I can tell after looking at the changes [MENTION=7983835]kalinethunter[/MENTION], so I am curios if something changed.

After bootstrapping to the latest commit and clone the devices files, I'll give them a try and if anything significant change, do I report back asap. ^
[Nexus 6P Android Development] dubedollars:
Got it working. Only quirk is in order to get monitor mode to work I have to use reinstall the driver every reboot. It's the only way the native Nexus 6p wifi chip will go into monitor mode. My external works flawlessly tho.
[Nexus 6P Android Development] UsPdSr:
Mh, but this was announced beforehand.

The issues with Nexmon will be, according to Re4son, resolved by the official release.

I saw that he updated the kernel, so I updated the device folder until the latest commit, but now 'pip' is giving me some problems.

If I get the Installer to work, will I gladly upload if something is changed.

Edit//

Do you install the firmware with the Nexmon app after the reboot?

As long as the internal chipset is not working with Nexmon, I got more interested in 'Hijacker', which is a formidable app.

I think we have enough options for some time by the Kali Nethunter team, so the Nexmon support, as well our device is supported by them, is rather a microscopic issue in hindsight of these accomplishments. :o
[Nexus 6P Android Development] yesimxev:
Which ralink adapter? What is it's chipset?
[Nexus 6P Android Development] Qazianwar222:
Did yo do fstab command mentioned and after that format data of the phone ?
[Nexus 6P Android Development] Figeko:
Yes, i follow the guide and try different steps for more than 6/7 times but chroot miss every time.
[Nexus 6P Android Development] Qazianwar222:
Oh chroot miss?

That's not a big problem

Did you linked the right chroot directory in Kali nethunter chroot manager?
[Nexus 6P Android Development] Figeko:
No, i didn't .

How can i do it?
[Nexus 6P Android Development] Qazianwar222:
Just change the path or provide me screenshot of your screenshot manager
[Nexus 6P Android Development] Figeko:
Sorry please tell me the steps to link the chroot directory
[Nexus 6P Android Development] Qazianwar222:
There will be a option to edit the path

And set it to the chrootfs

And it isn't rocket science bro you'll figure it out 😂
[Nexus 6P Android Development] yesimxev:
Can you try flashing the latest version? Just pushed recently https://kali.download/nethunter-images/kali-2023.3b/nethunter-2023.3b-angler-los-ten-kalifs-full.zip
[Nexus 6P Android Development] ChaNg1o:
Halo,When I start nexmon concerned apps there is alway error ponit to error " CANNOT LINK EXECUTABLE "/system/bin/imscmservice": library "libart.so" not found " Is this error led by incomplete kernel flash？

[UPDATE]

I have found that the image Vendor.squashfs has been not flash,Then I check df -h,which tell me vendor space is full and I tried manually move those files that unpacked form squashfs to /system_root,shell print no space left on the device.So How can I flash this vendor.squashfs with correct?Is this partition layout was broken? Thanks a lot.

[screenshots]
[Nexus 6P Android Development] Midd741:
@yesimxev - great work, thank you! Finally I have working Nethunter!

Observations:

1. I couldn't get firmware files in /system/etc/firmware folder, not even firmware folder itself after kali-nethunter flash. And after flashing kali-nethunter I couldn't copy firmware files because of the "No space left on device" issue.

Finally what I did:

- just before flashing kali-nethunter, I have extracted "/boot-patcher/system/" folder from kali-nethunter zip and transferred first to /sdcard/ via adb push:

adb push system/. /sdcard/

- inside /system folder you have 4 folders: etc/firmware/, lib/, lib64/ and xbin/

- step by step I have copied all files to right places

- flashed kali-nethunter

- profit

2. External wifi dongle:

Once firmware is in place, right dongle(s) are working.

However:

I wrote python script for monitoring wifi client requests, works as expected but Atheros AR9271 (I have 4 different dongles with that chip) is unstable and script crashes after a short period of time.

Realtek RTL8812AU and RTL8188EUS works like charm.

I'm wondering if this is not an issue with firmware - on my desktop with kali AR9271 chip loads firmware htc_9271-1.4.0.fw, but it is not in nethunter, where this chip loads htc_9271.fw firmware.
[Nexus 6P Android Development] Midd741:
Maybe you will find that useful:

Assuming that you added

export LD_PRELOAD=/system/lib64/kalilibnexmon.so

to /root/.zshrc or /root/.bashrc and not to "Initial command" in NetHunter Terminal..

1. Custom command for enabling wlan0 in monitor mode and booting kali:

Label: START wlan0 monitor mode & boot kali <--- or whatever name you want to give

Command:

/sbin/su -c "ip link set wlan0 down; sleep 1; ip link set wlan0 up; nexutil -m2; /data/data/com.offsec.nethunter/files/scripts/bootkali"

Send to: android

Exec mode: interactive

That will nicely disconnect you from AP, put wlan0 in monitor mode and boot kali

2. Custom command to stop wlan0 monitor mode and go back to normal wifi operation:

/sbin/su -c "ip link set wlan0 down; sleep 1; ip link set wlan0 up; nexutil -m0; sleep 2; scv wifi enable"

Send to: android

Exec mode: background

That will disable monitor mode on wlan0 and reconnect you with AP.
[Nexus 6P Android Development] Midd741:
Unfortunately, if you forgot to flash something before flashing nethunter-kalifs, then you need to repeat a whole process again. For some mysterious reason, after flashing nethunter-kali this is what is happening - no space left on device, even though its not really true.
[Nexus 6P Android Development] ChaNg1o:
Agreed,But I have tried many times follow the instucktions to flash vendors,images,but still not really flash because some reasons.And Now I making a new trying.Hope this time can be finished.Thanks a lot.
[Nexus 6P Android Development] Midd741:
We have 2 vendor files: vendor-angler-opm7.181205.001.img (that goes first) and vendor.squashfs
[Nexus 6P Android Development] ChaNg1o:
Yes,I flash vendor.img before vendor.squash,First time I use the platform tools which is contains bugs to flash them,when flashing squash,alert me there is no space something.And I change the adb and fastboot version tool to re-flash them,No extra messages,It looks like finished but when I enter the nethunter,firmware and others did not work actually,Now unzip /system from nethunter.zip into /system_root/system,Now seems like they have been flashed,BTW how to verify nexmon work successfully?Nexutil commands status?Thank you.
[Nexus 6P Android Development] Midd741:
install android terminal Emulator apk, run it, su to root, make sure you are not connected to AP and run nexutil -m2. Or run the command from post #391. If will not throw errors then you good to go.

If yes then possibly you have problems with nexutils libs, maybe copied to wrong place or not at all.
[Nexus 6P Android Development] ChaNg1o:
What made me feel upset is...Not working.I have check the firmware for BCM4538,installed version is 7.112.300.14 Not Patched 7.112.200.17-sta.Then switching to adb root shell and adb remount to cp or mv but there's always text to me "read-only file system".Other side,found "CANNOT LINK EXECUTABLE "/system/bin/imscmservice": library "libart.so" not found" in logcat still,So I am not sure whether Vendor.squashfs has been flashed or other errors led.All files in note I have done,I don't why.LOL
[Nexus 6P Android Development] ChaNg1o:
Yes,No Errors.But lwconfig or network tools display wlan0 not wlan0mon when I switched monitor mode,wifite2 can't scan and load.
[Nexus 6P Android Development] Midd741:
wlan0 - that's correct, check iwconfig wlan0 if its in monitor mode. Should be.

Then run "wifite -i wlan0"
[Nexus 6P Android Development] ChaNg1o:
Allright,When I keyboard iwconfig returned just "No extension" something,no hints showing wlan0 has been enabled to monitor mode.Then Wifite not working.
[Nexus 6P Android Development] Midd741:
ip link set wlan1 down && iw wlan1 set monitor control && ip link set wlan1 up && sleep 2 && wifite -i wlan1
[Nexus 6P Android Development] ChaNg1o:
In the Command that wlan1 can not been found,so I change wlan1 to wlan0,when I type full command it shows command failed: operation not supported -95.If just type wifite -i wlan0,then error:No targets found.And [!] Exiting.
[Nexus 6P Android Development] ChaNg1o:
And is fw_bcmdhd firmware in nethunter.zip? whether if lineageOS because of system encryption of android 10 made nethunter kernel can not be flash normally?
[Nexus 6P Android Development] Midd741:
have you done this:
[Nexus 6P Android Development] ChaNg1o:
Yeah,I am sure that every times I flash them the wipe and advanced wipe was been done.And later I will record every steps I installing lineageOS and methunter,I have to deal with it! thanks a lot.
[Nexus 6P Android Development] yesimxev:
Thanks for this! Firmwares are being updated. I'm not sure why firmware install fails, and it not happens for all phone variants, we'll try to find the bug patch
[Nexus 6P Android Development] yesimxev:
iwconfig is deprecated, iw will work
[Nexus 6P Android Development] yesimxev:
wlan0 name is fine. As mentioned: run in androidsu

nexutil -m2

, then open nethunter terminal:

export LD_PRELOAD=/system/lib64/kalilibnexmon.so
wifite -i wlan0
[Nexus 6P Android Development] ChaNg1o:
I am a fool.Now it is works.I always thinking maybe Zips have not been flashed because nexmon in NH Store shows firmware is not same as patched version.And Why dose ioctl failed when I use mdk3 wlan0 -c 1,shows Operation not Permitted/Supported
[Nexus 6P Android Development] Midd741:
...or like in post #391 create custom command :

/sbin/su -c "ip link set wlan0 down; sleep 1; ip link set wlan0 up; nexutil -m2; /data/data/com.offsec.nethunter/files/scripts/bootkali"

AND:

Send to: android <--- not kali!

Exec mode: interactive

AND put this in /root/.zshrc or /root/.bashrc

export LD_PRELOAD=/system/lib64/kalilibnexmon.so
[Nexus 6P Android Development] yesimxev:
probably checks for monitor mode in the usual way. Try mdk4
[Nexus 6P Android Development] yesimxev:
I don't think it needs wlan0 down. exporting could work, but it may mess up other things you want to run in terminal?
[Nexus 6P Android Development] Midd741:
wlan0 down is for the case when you are associated with AP, then this will disconnect you, put wlan0 up and before it will associate you will run nexutil -m2 and it will be in monitor mode. It works for me.

There is a possibility that it can mess up other things you want to run in kali terminal, thats why its a custom command only in Nethunter app.
[Nexus 6P Android Development] yesimxev:
Great, that makes sense. O yes I meant adding to zshrc could be risky
[Nexus 6P Android Development] ChaNg1o:
Hmm,Let me put in a word.Any firmware errors if echo "__nex__driver_io:error ret=-1 errorn=4" when I input nexutil -V command?
[Nexus 6P Android Development] Midd741:
Maybe try to flash kernel from post #264 ?
[Nexus 6P Android Development] yesimxev:
Did you flash vendor.squashfs as required? That has the nexmon firmware, otherwise yes lineage17.1 doesn't allow to mount rw /vendor partiton
[Nexus 6P Android Development] Midd741:
Something is missing in kernel angler-los, because bluebinder is not working (throwing errors), /dev/binderfs is empty, there is no hciX interface.

Or bluetooth arsenal should not work with internal bluetooth interface?

Or maybe kernel driver is missing/not added?..

Anyone made this working?
[Nexus 6P Android Development] steso90:
I Have same error with internal Bluetooth
[Nexus 6P Android Development] ChaNg1o:
Yeah.But when I use adb version 34 to flash vendor it will remind me "there is no space" something.So I changed it to adb out dated version to flash vendor.squash.No reminds.Looks like flashing successfully.I will try it again and log details.
[Nexus 6P Android Development] yesimxev:
@Midd741 it should work. What is your kernel version? Which nethunter zip did you install?

Try this kernel, this should be the latest https://www.androidfilehost.com/?fid=4279422670115730196
[Nexus 6P Android Development] Midd741:
Thanks @yesimxev , this is exactly the kernel I've flashed.
[Nexus 6P Android Development] yesimxev:
Can you also run 'setup' from bluetooth arsenal top right corner? I think you had an error during first setup
[Nexus 6P Android Development] Midd741:
yes:
[Nexus 6P Android Development] yesimxev:
Let's try to rebuld libg stuff and also bluebinder

cd /root/libgbinder && make clean; make && make install
cd /root/libglibutil && make clean; make && make install
cd /root/bluebinder && make clean; make && make install
[Nexus 6P Android Development] Midd741:
Unfortunately still the same effect:
[Nexus 6P Android Development] Midd741:
That worries me (logcat in android terminal):
[Nexus 6P Android Development] yesimxev:
Can you try with Bluetooth off and then Bluetooth on too?

Also, are the libs successfully installed?

ls /lib/libgbinder.so*

ls /lib/libglibutil.so*
[Nexus 6P Android Development] Midd741:
Libs seems to be in place:

ls -la /lib/libgbinder.so* /lib/libglibutil.so*
lrwxrwxrwx. 1 root root 15 Oct 17 18:43 /lib/libgbinder.so -> libgbinder.so.1
lrwxrwxrwx. 1 root root 17 Oct 31 13:17 /lib/libgbinder.so.1 -> libgbinder.so.1.1
lrwxrwxrwx. 1 root root 20 Oct 31 13:17 /lib/libgbinder.so.1.1 -> libgbinder.so.1.1.25
-rwxr-xr-x. 1 root root 200792 Oct 31 13:17 /lib/libgbinder.so.1.1.25
lrwxrwxrwx. 1 root root 16 Oct 17 18:43 /lib/libglibutil.so -> libglibutil.so.1
lrwxrwxrwx. 1 root root 18 Oct 31 13:20 /lib/libglibutil.so.1 -> libglibutil.so.1.0
lrwxrwxrwx. 1 root root 21 Oct 31 13:20 /lib/libglibutil.so.1.0 -> libglibutil.so.1.0.67
-rwxr-xr-x. 1 root root 68840 Oct 31 13:20 /lib/libglibutil.so.1.0.67

I started syslog-ng and watched logs, once run bluebinder I've got this:

Oct 31 22:24:35 kali kernel: bluebinder[14272]: syscall 293
Oct 31 22:24:35 kali kernel: Code: d2800401 d2800002 d28024a8 d4000001 (3140041f)
Oct 31 22:24:35 kali kernel: CPU: 1 PID: 14272 Comm: bluebinder Tainted: G W 3.10.108-yesimxev #1
Oct 31 22:24:35 kali kernel: task: ffffffc01a9aeb80 ti: ffffffc0bffcc000 task.ti: ffffffc0bffcc000
Oct 31 22:24:35 kali kernel: PC is at 0x7b9bc53714
Oct 31 22:24:35 kali kernel: LR is at 0x7b9bc536f0
Oct 31 22:24:35 kali kernel: pc : [<0000007b9bc53714>] lr : [<0000007b9bc536f0>] pstate: 40000000
Oct 31 22:24:35 kali kernel: sp : 0000007ffedb51f0
Oct 31 22:24:35 kali kernel: x29: 0000007ffedb51f0 x28: 000000000000fff1
Oct 31 22:24:35 kali kernel: x27: 0000000000000000 x26: 0000000000000000
Oct 31 22:24:35 kali kernel: x25: 0000007b9bc647f0 x24: 0000007b9bc64000
Oct 31 22:24:35 kali kernel: x23: 0000007b9bc83000 x22: 0000000000000000
Oct 31 22:24:35 kali kernel: x21: 0000000000000041 x20: 0000007b9bc3d4e0
Oct 31 22:24:35 kali kernel: x19: 0000007b9bc3dc20 x18: 000000000003f000
Oct 31 22:24:35 kali kernel: x17: fffffffffffff000 x16: 0000007b9bc4caf0
Oct 31 22:24:35 kali kernel: x15: 000000000000ffff x14: 0000007b9bc83008
Oct 31 22:24:35 kali kernel: x13: 0000000000000041 x12: 0000007b9bc3d0c8
Oct 31 22:24:35 kali kernel: x11: 0000000000000008 x10: 0000000000000088
Oct 31 22:24:35 kali kernel: x9 : 0000000000000000 x8 : 0000000000000125
Oct 31 22:24:35 kali kernel: x7 : 00000000000037c0 x6 : ffffffffffffffe0
Oct 31 22:24:35 kali kernel: x5 : 0000000000000004 x4 : 0000007b9bc81e08
Oct 31 22:24:35 kali kernel: x3 : 00000000d428bc00 x2 : 0000000000000000
Oct 31 22:24:35 kali kernel: x1 : 0000000000000020 x0 : 0000007b9bc3dc00
Oct 31 22:24:35 kali kernel:
Oct 31 22:24:35 kali kernel: init: Received control message 'interface_start' for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 378 (/system/bin/hwservicemanager)
Oct 31 22:24:35 kali kernel: init: Could not find 'android.hardware.bluetooth@1.0::IBluetoothHci/default' for ctl.interface_start

Notice the last line: "Could not find 'android.hardware.bluetooth@1.0::IBluetoothHci/default'"

Does it tells you anything?

(I tried all possible combinations of bluetooth and dbus).

Also, not sure about dbus, it throws errors on bluetooth restart, but I don't know enough about dbus .
[Nexus 6P Android Development] yesimxev:
Do you have such service? Maybe 6P has it different.. I added that feature when I didn't own that phone anymore, so I couldn't test x)

But this is the first phone it doesn't work with.

ls /vendor/bin/hw/android.hardware.bluetooth\@1.0-service-*
[Nexus 6P Android Development] Qazianwar222:
Facing the Same Issue as you Do bro

Please let me know If you could make Bluebinder to work

Searching this issue for 3 to 4 months
[Nexus 6P Android Development] Midd741:
There you go, I don't have such service:
[Nexus 6P Android Development] Midd741:
I have unpacked vendor.squashfs, copied android.hardware.bluetooth@1.0-service into bin/hw folder, packed squashfs and flashed in fastboot. Now I do have this service but bluebinder behaves the same way - failing. Syslog shows this info now when running bluebinder:

Nov 2 11:18:03 kali kernel: bluebinder[12282]: syscall 293
Nov 2 11:18:03 kali kernel: Code: d2800401 d2800002 d28024a8 d4000001 (3140041f)
Nov 2 11:18:03 kali kernel: CPU: 2 PID: 12282 Comm: bluebinder Tainted: G W 3.10.108-yesimxev #1
(...snip...)
Nov 2 11:18:03 kali kernel: init: Received control message 'interface_start' for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 377 (/system/bin/hwservicemanager)
Nov 2 11:18:04 kali kernel: timerfd blocking read by tid 377
Nov 2 11:18:04 kali kernel: timerfd blocking read released by tid 377
Nov 2 11:18:06 kali kernel: init: starting service 'imscmservice'...
Nov 2 11:18:06 kali kernel: init: starting service 'vendor.fps_hal'...
Nov 2 11:18:06 kali kernel: init: Service 'imscmservice' (pid 12286) exited with status 1
Nov 2 11:18:06 kali kernel: init: Sending signal 9 to service 'imscmservice' (pid 12286) process group...
Nov 2 11:18:06 kali kernel: libprocessgroup: Successfully killed process cgroup uid 1000 pid 12286 in 0ms

Any idea what would be the next step?
[Nexus 6P Android Development] Qazianwar222:
Can you share me the File?

& tell me from where you've downloaded it?
[Nexus 6P Android Development] Qazianwar222:
The bluetooth file naming android.hardware.bluetooth@1.0-service
[Nexus 6P Android Development] Midd741:
I've copied the file from LOS 18.1 build on Samsung SM-J700H, because that's what I had.

It looks between other files like this:

kali:/vendor/bin/hw # file *
android.hardware.audio@2.0-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
android.hardware.biometrics.fingerprint@2.1-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.bluetooth@1.0-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
android.hardware.camera.provider@2.4-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
android.hardware.cas@1.1-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
android.hardware.configstore@1.1-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.contexthub@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.gatekeeper@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.gnss@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.graphics.allocator@2.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.graphics.composer@2.1-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.health@2.0-service.angler: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.keymaster@3.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.light@2.0-service.angler: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.media.omx@1.0-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
android.hardware.nfc@1.2-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.power@1.2-service-qti: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.thermal@2.0-service.mock: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.usb@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
android.hardware.wifi@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
hostapd: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
rild: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
vendor.lineage.trust@1.0-service: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)
wpa_supplicant: ELF shared object, 64-bit LSB arm64, dynamic (/system/bin/linker64)

It could be wrong file. Attached (unzip it).
[Nexus 6P Android Development] yesimxev:
I don't think copying a service from a different phone could work. Try to find otherwise:

find /vendor -name android.hardware.bluetooth*
[Nexus 6P Android Development] Midd741:
Here it is:

kali:/ # find /vendor -name android.hardware.bluetooth*
/vendor/bin/hw/android.hardware.bluetooth@1.0-service
/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so
/vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so

kali:/ # ls -al /vendor/bin/hw/android.hardware.bluetooth@1.0-service /vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so /vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so
-rw-r--r-- 1 root root 4868 2023-11-02 10:58 /vendor/bin/hw/android.hardware.bluetooth@1.0-service
-rw-r--r-- 1 root root 48588 2020-07-28 20:21 /vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so
-rw-r--r-- 1 root root 61568 2020-07-28 20:21 /vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so

kali:/ # file /vendor/bin/hw/android.hardware.bluetooth@1.0-service /vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so /vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so
/vendor/bin/hw/android.hardware.bluetooth@1.0-service: ELF shared object, 32-bit LSB arm, dynamic (/system/bin/linker)
/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so: ELF shared object, 32-bit LSB arm
/vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so: ELF shared object, 64-bit LSB arm64

Of course first file is the one I've copied into squashfs vendor file.

So we have two files in lib and lib64, but they have '.so' extension

Tomorrow I'll try to replace /vendor/bin/hw/android.hardware.bluetooth@1.0-service with /vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so.

Unless it doesn't make sense. What you think?