yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] Midd741:
Just to add:

kali:/ # find / -name android.hardware.bluetooth* 2>/dev/null
/sbin/.magisk/mirror/vendor/bin/hw/android.hardware.bluetooth@1.0-service
/sbin/.magisk/mirror/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so
/sbin/.magisk/mirror/vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so
/data/local/nhsystem/kali-arm64/system/etc/permissions/android.hardware.bluetooth_le.xml
/data/local/nhsystem/kali-arm64/system/lib/android.hardware.bluetooth.a2dp@1.0.so
/data/local/nhsystem/kali-arm64/system/lib/android.hardware.bluetooth.audio@2.0.so
/data/local/nhsystem/kali-arm64/system/lib/android.hardware.bluetooth@1.0.so
/data/local/nhsystem/kali-arm64/system/lib64/android.hardware.bluetooth.a2dp@1.0.so
/data/local/nhsystem/kali-arm64/system/lib64/android.hardware.bluetooth.audio@2.0.so
/data/local/nhsystem/kali-arm64/system/lib64/android.hardware.bluetooth@1.0.so
/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
/system/etc/permissions/android.hardware.bluetooth_le.xml
/system/lib/android.hardware.bluetooth.a2dp@1.0.so
/system/lib/android.hardware.bluetooth.audio@2.0.so
/system/lib/android.hardware.bluetooth@1.0.so
/system/lib64/android.hardware.bluetooth.a2dp@1.0.so
/system/lib64/android.hardware.bluetooth.audio@2.0.so
/system/lib64/android.hardware.bluetooth@1.0.so
[Nexus 6P Android Development] Qazianwar222:
Why doesn't the vendor has a built-in hardware.Bluetooth file for angler stock?
[Nexus 6P Android Development] yesimxev:
Ok let's ask peeps who have knowledge x)

No android.bluetooth.service · Issue #35 · mer-hybris/bluebinder

Hi, we are struggling with one of the NetHunter supported device: Nexus 6P (oreo, and lineage17.1 too). (VHCI, UART H4, IPC_BINDER enabled) Looks like there are no android.hardware.bluetooth@1.0-se...

github.com
[Nexus 6P Android Development] yesimxev:
@Midd741 @Qazianwar222 can you check the following: You can use binder-list -d /dev/hwbinder from libgbinder to check if there is a binder service, it's possible that it's a different version than bluebinder expects, and that would need changes.

Also find / -name *bluetooth* 2>/dev/null
[Nexus 6P Android Development] Midd741:
binder-list needs to be compiled first, its located in /root/libgbinder/test/binder-list, and then:

./binder-list -d /dev/hwbinder
android.frameworks.cameraservice.service@2.0::ICameraService/default
android.frameworks.displayservice@1.0::IDisplayService/default
android.frameworks.schedulerservice@1.0::ISchedulingPolicyService/default
android.frameworks.sensorservice@1.0::ISensorManager/default
android.frameworks.stats@1.0::IStats/default
android.hardware.audio.effect@2.0::IEffectsFactory/default
android.hardware.audio@2.0::IDevicesFactory/default
android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
android.hardware.cas@1.0::IMediaCasService/default
android.hardware.cas@1.1::IMediaCasService/default
android.hardware.configstore@1.0::ISurfaceFlingerConfigs/default
android.hardware.configstore@1.1::ISurfaceFlingerConfigs/default
android.hardware.contexthub@1.0::IContexthub/default
android.hardware.gatekeeper@1.0::IGatekeeper/default
android.hardware.gnss@1.0::IGnss/default
android.hardware.graphics.allocator@2.0::IAllocator/default
android.hardware.graphics.composer@2.1::IComposer/default
android.hardware.health@2.0::IHealth/default
android.hardware.keymaster@3.0::IKeymasterDevice/default
android.hardware.light@2.0::ILight/default
android.hardware.media.c2@1.0::IComponentStore/software
android.hardware.media.omx@1.0::IOmx/default
android.hardware.media.omx@1.0::IOmxStore/default
android.hardware.nfc@1.0::INfc/default
android.hardware.nfc@1.1::INfc/default
android.hardware.nfc@1.2::INfc/default
android.hardware.power@1.0::IPower/default
android.hardware.power@1.1::IPower/default
android.hardware.power@1.2::IPower/default
android.hardware.radio.deprecated@1.0::IOemHook/slot1
android.hardware.radio@1.0::IRadio/slot1
android.hardware.radio@1.0::ISap/slot1
android.hardware.radio@1.1::IRadio/slot1
android.hardware.radio@1.1::ISap/slot1
android.hardware.soundtrigger@2.0::ISoundTriggerHw/default
android.hardware.thermal@1.0::IThermal/default
android.hardware.thermal@2.0::IThermal/default
android.hardware.usb@1.0::IUsb/default
android.hardware.wifi.supplicant@1.0::ISupplicant/default
android.hardware.wifi.supplicant@1.1::ISupplicant/default
android.hardware.wifi.supplicant@1.2::ISupplicant/default
android.hardware.wifi@1.0::IWifi/default
android.hardware.wifi@1.1::IWifi/default
android.hardware.wifi@1.2::IWifi/default
android.hardware.wifi@1.3::IWifi/default
android.hidl.allocator@1.0::IAllocator/ashmem
android.hidl.base@1.0::IBase/ashmem
android.hidl.base@1.0::IBase/default
android.hidl.base@1.0::IBase/legacy/0
android.hidl.base@1.0::IBase/slot1
android.hidl.base@1.0::IBase/software
android.hidl.manager@1.0::IServiceManager/default
android.hidl.manager@1.1::IServiceManager/default
android.hidl.manager@1.2::IServiceManager/default
android.hidl.token@1.0::ITokenManager/default
android.system.net.netd@1.0::INetd/default
android.system.net.netd@1.1::INetd/default
android.system.suspend@1.0::ISystemSuspend/default
android.system.wifi.keystore@1.0::IKeystore/default
vendor.lineage.power@1.0::ILineagePower/default
vendor.lineage.trust@1.0::IUsbRestrict/default

I can't see running service here....
[Nexus 6P Android Development] Midd741:
...and output of find / -name *bluetooth* 2>/dev/null :

/config/sdcardfs/com.android.bluetooth
/config/sdcardfs/com.android.bluetoothmidiservice
...
/mnt/runtime/full/emulated/0/nethunter_files/etc/firmware/bluetooth_rxtx.bin
/mnt/runtime/write/emulated/0/nethunter_files/etc/firmware/bluetooth_rxtx.bin
/mnt/runtime/read/emulated/0/nethunter_files/etc/firmware/bluetooth_rxtx.bin
/mnt/runtime/default/emulated/0/nethunter_files/etc/firmware/bluetooth_rxtx.bin
/data/misc/bluetooth
/data/misc/profiles/cur/0/com.android.bluetoothmidiservice
/data/misc/profiles/cur/0/com.android.bluetooth
/data/misc/profiles/ref/com.android.bluetoothmidiservice
/data/misc/profiles/ref/com.android.bluetooth
...
/data/data/com.android.bluetoothmidiservice
/data/data/com.android.bluetooth
/data/user_de/0/com.android.bluetoothmidiservice
/data/user_de/0/com.android.bluetooth
/data/user_de/0/com.android.bluetooth/databases/bluetooth_db
/data/user_de/0/com.android.bluetooth/databases/bluetooth_db-wal
/data/user_de/0/com.android.bluetooth/databases/bluetooth_db-shm
/data/user_de/0/com.android.bluetooth/shared_prefs/bluetooth_volume_map.xml
/data/user_de/0/com.android.bluetooth/shared_prefs/com.android.bluetooth_preferences.xml
/data/media/0/nethunter_files/etc/firmware/bluetooth_rxtx.bin
/vendor/lib/hw/android.hardware.bluetooth@1.0-impl.so
/vendor/lib64/hw/android.hardware.bluetooth@1.0-impl.so
/proc/bluetooth
/proc/irq/605/bluetooth hostwake
/system/etc/permissions/android.hardware.bluetooth_le.xml
/system/etc/firmware/bluetooth_rxtx.bin
/system/etc/bluetooth
/system/app/Bluetooth/lib/arm64/libbluetooth_jni.so
/system/lib/android.hardware.bluetooth.a2dp@1.0.so
/system/lib/android.hardware.bluetooth.audio@2.0.so
/system/lib/android.hardware.bluetooth@1.0.so
/system/lib/libbluetooth.so
/system/lib64/android.hardware.bluetooth.a2dp@1.0.so
/system/lib64/android.hardware.bluetooth.audio@2.0.so
/system/lib64/android.hardware.bluetooth@1.0.so
/system/lib64/libbluetooth-binder.so
/system/lib64/libbluetooth.so
/system/lib64/libbluetooth_jni.so
/dev/__properties__/u:object_r:bluetooth_prop:s0
/sys/fs/selinux/class/bluetooth_socket
/sys/class/bluetooth
/sys/kernel/debug/bluetooth
/sys/module/bluetooth_power
/sys/module/bluetooth

skipped /sbin/.magisk/mirror/data/ and /data/local/nhsystem/kali-arm64/ to make it more readable
[Nexus 6P Android Development] yesimxev:
How about

binder-list -d /dev/binder
[Nexus 6P Android Development] Midd741:
The output is empty.

In verbose mode:

binder-list -v -d /dev/binder
[gbinder] Using aidl service manager for /dev/binder
[gbinder] Using aidl protocol for /dev/binder
[gbinder] Opened /dev/binder version 8
[gbinder] Starting looper binder#1
[gbinder] Looper binder#1 running
[gbinder] /dev/binder has service manager
[gbinder] Stopping looper binder#1
[gbinder] Looper binder#1 done
[gbinder] Closing /dev/binder
[Nexus 6P Android Development] yesimxev:
Check if there are any *.rc files containing anything bluetooth related.

Maybe

grep -or bluetooth /vendor
[Nexus 6P Android Development] Midd741:
I've used this:

find /vendor -type f -exec grep -H -i "bluetooth" {} \; 2>/dev/null

and the only interesting file I've found is this:

kali:/ # cat /vendor/etc/selinux/vendor_file_contexts |grep bluetooth
/(vendor|system/vendor)/bin/hw/android\.hardware\.bluetooth@1\.0-service u:object_r:hal_bluetooth_default_exec:s0
/(vendor|system/vendor)/bin/hw/android\.hardware\.bluetooth@1\.0-service\.btlinux u:object_r:hal_bluetooth_btlinux_exec:s0
/sys/devices/bt_bcm4358\.[0-9]+/rfkill/rfkill0/state u:object_r:sysfs_bluetooth_writable:s0
[Nexus 6P Android Development] yesimxev:
Thanks. Can you also check getprop for any bluetooth properties, there should be one indicating the bluetooth service.
[Nexus 6P Android Development] Midd741:
Not sure if that's correct:

kali:/ # getprop|grep blue
[persist.bluetooth.btsnoopdefaultmode]: []
[Nexus 6P Android Development] yesimxev:
Check the /vendor/etc/vintf manifest files.
[Nexus 6P Android Development] Midd741:
1|kali:/ # cd /vendor/etc/vintf/manifest

kali:/vendor/etc/vintf/manifest # ls -la

total 2

drwxr-xr-x 2 root shell 107 2020-07-28 20:21 .

drwxr-xr-x 3 root shell 83 2020-07-28 20:21 ..

-rw-r--r-- 1 root root 323 2020-07-28 20:21 android.hardware.cas@1.1-service.xml

-rw-r--r-- 1 root root 350 2020-07-28 20:21 android.hardware.thermal@2.0-service.xml

kali:/vendor/etc/vintf/manifest # grep bluetooth *

1|kali:/vendor/etc/vintf/manifest #
[Nexus 6P Android Development] yesimxev:
Is there any in here: dmesg | grep bluetooth
[Nexus 6P Android Development] Midd741:
After fresh restart that was empty. Then I have started dbus abd bluetooth and started Android bluetooth and this came out:

kali:/ # dmesg |grep bluetooth
[ 104.418007] bluetooth[7797]: syscall 293
[ 104.418057] CPU: 2 PID: 7797 Comm: bluetooth Not tainted 3.10.108-yesimxev #1
[ 104.429328] bluetooth[7797]: syscall 439
[ 104.429371] CPU: 0 PID: 7797 Comm: bluetooth Not tainted 3.10.108-yesimxev #1
[ 104.430004] bluetooth[7797]: syscall 439
[ 104.430033] CPU: 0 PID: 7797 Comm: bluetooth Not tainted 3.10.108-yesimxev #1
[ 104.431107] bluetooth[7797]: syscall 439
[ 104.431139] CPU: 0 PID: 7797 Comm: bluetooth Not tainted 3.10.108-yesimxev #1
[ 104.535145] type=1400 audit(1699388124.263:300): avc: denied { ioctl } for comm="bluetoothd" path="/proc/7804/mountinfo" dev="proc" ino=51116 ioctlcmd=5401 scontext=u:r:magisk:s0 tcontext=u:r:magisk:s0 tclass=file permissive=1
[ 108.296010] type=1400 audit(1699388124.263:300): avc: denied { ioctl } for comm="bluetoothd" path="/proc/7804/mountinfo" dev="proc" ino=51116 ioctlcmd=5401 scontext=u:r:magisk:s0 tcontext=u:r:magisk:s0 tclass=file permissive=1
[ 147.811195] init: Received control message 'interface_start' for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 377 (/system/bin/hwservicemanager)
[ 147.811283] init: Could not find 'android.hardware.bluetooth@1.0::IBluetoothHci/default' for ctl.interface_start
[Nexus 6P Android Development] yesimxev:
That's odd, even android is looking for the service. Anyway, last to check:

You need to go through all the manifest files (they're might be more elsewhere and there might be one that contains multiple services e.g /vendor/etc/vintf/manifest.xml /odm/etc/manifest.xml or whatnot). One of them should contain the definition. If the definition is not there then i'm pretty sure android would ignore bluetooth.

Manifests | Android Open Source Project

source.android.com
[Nexus 6P Android Development] Midd741:
Nothing there:

1|kali:/ # find / -name manifest.xml 2>/dev/null
/sbin/.magisk/mirror/vendor/etc/vintf/manifest.xml
/sbin/.magisk/mirror/data/local/nhsystem/kali-arm64/usr/share/metasploit-framework/data/exploits/badodt/manifest.xml
/sbin/.magisk/mirror/data/local/nhsystem/kali-arm64/usr/share/metasploit-framework/data/exploits/openoffice_document_macro/META-INF/manifest.xml
/data/local/nhsystem/kali-arm64/usr/share/metasploit-framework/data/exploits/badodt/manifest.xml
/data/local/nhsystem/kali-arm64/usr/share/metasploit-framework/data/exploits/openoffice_document_macro/META-INF/manifest.xml
/data/local/nhsystem/kali-arm64/system/etc/vintf/manifest.xml
/vendor/etc/vintf/manifest.xml
/system/etc/vintf/manifest.xml
1|kali:/ #

1|kali:/ # find / -name manifest.xml -exec grep -H -i "bluetooth" {} \; 2>/dev/null
1|kali:/ #
[Nexus 6P Android Development] Midd741:
PROGRESS!!!

What I've done:

1. flashed lineage-17.0-20191220-UNOFFICIAL-angler.zip,

2. SKIPPED flashing vendor.squashfs,

3. copied fstab.angler

4. Format Data, as in description, setup Android

5. Copied nexmon files and firmware in a right places

6. flashed nethunter-2023.3b-angler-los-ten-kalifs-full.zip

7. flashed Magisk-v25-2.zip

8. flashed kernel-nethunter-20230323_130704-angler-los-ten.zip

9. Boot to system, setup Nethunter, setup 'Bluetooth Arsenal'

10. hci0 appeared!!!

Not sure at this point if the rest is working.

So, the only different thing I did is an older LOS and DID NOT flash vendor.squashfs

I'll keep you updated.

* Update - I had to replace fw_bcmdhd.bin file to get nexmon working.
[Nexus 6P Android Development] yesimxev:
Congratulations, that's an awesome find! Wondering which version I used, but I think it's the same, hence I thought it's impossible. And the fact that oreo does the same.. will need your bt service file(s) for @Qazianwar222 . How did you replace fw, did you unpack and repack squashfs image of vendor, or is there a painless way?
[Nexus 6P Android Development] Midd741:
Thanks!

Quite a journey, extracted 'vendor.new.dat.br' from ROM zip file, unpacked:

brotli --decompress vendor.new.dat.br vendor.new.dat

unsquashed:

sudo unsquashfs vendor.new.dat

replaced squashfs-root/firmware/fw_bcmdhd.bin file (from unsquashed vendor.squashfs to extracted from ROM)

squashed back:

sudo mksquashfs squashfs-root vendorblah.squashfs

flashed 'vendorblah.squashfs' in bootloader

Hope its clear what I did :|

Once I'll have final working version I will post needed files
[Nexus 6P Android Development] yesimxev:
There's the point, I didn't extract from rom, I think I did dd from the phone. That would be awesome, thank you. Get ready for the popular badBT attack, coming soon! It works with internal BT 😎
[Nexus 6P Android Development] Midd741:
I tried other ROM's, only lineage-17.0-20191220-UNOFFICIAL-angler.zip worked for me.

Other ROM's missing files in vendor, copying them over doesn't give anything (couldn't boot, bootloops etc).

So:

Install/flash everything as in post 1 EXCEPT flashing 'vendor.squashfs'.

Update kali chroot (here will be some fun, eg. you have to do 'mkdir -p /data/local/tmp' in kali terminal and other things too ;) ).

Flash attached file (unzip first) from bootloader "fastboot flash vendor vendorblah.squashfs"

Reboot, setup Bluetooth Arsenal, check monitor mode wlan0 and wlan1.

All should work now.
[Nexus 6P Android Development] Qazianwar222:
Waiting for the Bluetooth Arsenal to work For months

Can't thank enough Bro ,You made my day 😍

I tried to make it work like a thousand times reinstalling and debugging my mistakes but always in vain

But now I'll give it a Try on Sunday to let you know if I succeeded in getting hci0 or not @Midd741 Thanks Again for your research

And also thanks to @yesimxev sir , It wouldn't have solved without you
[Nexus 6P Android Development] yesimxev:
Ok so it's lineage 17.0. Would that squashfs work with the lineage 17.1 image?
[Nexus 6P Android Development] Midd741:
Nope. I tried different combinations, only this particular ROM lineage-17.0-20191220-UNOFFICIAL-angler.zip

Not even different 17.0 ROMs.
[Nexus 6P Android Development] yesimxev:
Ok I will use that in this tutorial. Please let me know when you have that vendor uploaded somewhere. If you want, you can upload and replace this https://github.com/yesimxev/nethunter_files/blob/main/angler/vendor.squashfs.zip
[Nexus 6P Android Development] Midd741:
What do you think to wait for Qazianwar222 to confirm that it will work for him too and then to replace it in your github? Please feel free to do push.
[Nexus 6P Android Development] Qazianwar222:
I'll update you on Sunday dear brother

Sorry for the delay I'm far from home so I can't use my PC
[Nexus 6P Android Development] Midd741:
I've found the cause of 'no space left on device' after Nethunter has been flashed. However I do not know (yet) what Nethunter installer is exactly doing causing this. Here is the problem:

└─$ adb shell
angler:/ $ su
angler:/ # df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/root 4224 4224 0 100% /
tmpfs 355215 699 354516 1% /dev
tmpfs 355215 28 355187 1% /mnt
tmpfs 355215 13 355202 1% /apex
tmpfs 355215 389 354826 1% /sbin
/dev/block/mmcblk0p38 6400 17 6383 1% /cache
/dev/block/mmcblk0p32 512 107 405 21% /persist
/dev/block/mmcblk0p1 0 0 0 0% /firmware
/sbin/.magisk/block/vendor 955 955 0 100% /sbin/.magisk/mirror/vendor
/sbin/.magisk/block/data 1676080 352190 1323890 22% /sbin/.magisk/mirror/data
/data/media 1676080 352190 1323890 22% /mnt/runtime/default/emulated

You can see here I've used command 'df -i' which shows inode usage, and /dev/root has used 100% of inodes.

Inodes are created upon first formatting the drive and you can't generate more inodes after that.

So I'm suspecting installer creating a certain number of inodes (4224 ?) hence you can't fit anything more.

...unless you will delete something first.

I managed to do that on LOS 17.0 and charging ogg sound file, for some reason UI crashes when you try to change it from Settings, so I decided to replace 'ChargingStarted.ogg' :

First I pushed my 'ChargingStarted.ogg' file to /sdcard/ and then in adb shell and su:

mount -o remount,rw /
mount -o remount,rw /dev/root
cd /system/product/media/audio/ui
mv ChargingStarted.ogg /sdcard/Download/
cp /sdcard/ChargingStarted.ogg .
chmod 644 ChargingStarted.ogg

***** EDIT *****

Its NOT Nethunter, its LOS ROM.

Right after formatting the data and wiping the system and cache we have this:

~ # df -i
Filesystem Inodes Used Available Use% Mounted on
tmpfs 356257 450 355807 0% /dev
tmpfs 356257 3 356254 0% /tmp
/dev/block/mmcblk0p44 1676080 13 1676067 0% /data
/dev/block/mmcblk0p44 1676080 13 1676067 0% /sdcard
/dev/block/mmcblk0p43 196608 11 196597 0% /system_root
/dev/block/mmcblk0p38 6400 15 6385 0% /cache

It can be seen here that /system_root has 196608 inodes. Once you flash LOS that drops to mentioned 4224 inodes with 3973 inodes in use (251 free inodes).

I do not have experience with cooking ROMs, I tried cook LOS 17.1 for angler but there is no device specific configuration files on LOS github for angler, its not supported anymore. And even then - what causes reformat of system_root with that small amount of inodes?

Any ROM chef here?
[Nexus 6P Android Development] Qazianwar222:
HCI0 appeared 😁

Everything is working but I am getting one issue here

When I try to deauth a network using aireplay-ng it works for only first 10-20 packets for jamming the network

And then the WiFi of my phone turns off automatically causing the script

“__nex_driver_io: error”​

My phone also lags after I turn on my WiFi manually

and another thing us that I can't change WiFi channel in Kali terminal using iw
[Nexus 6P Android Development] Midd741:
yep, there are issues with this early ROM:

1. System UI is unstable (unfortunately)

2. Try to use different external wifi dongle, I had some issues with rtl8188eufw but RTL8812AU works OK
[Nexus 6P Android Development] Midd741:
Also, stock Launcher is buggy, use Nova Launcher for example.

Issues with PIN setup, if you wont be able to unlock, then reboot to TWRP and:

adb shell rm /data/system/locksettings.db
[Nexus 6P Android Development] Midd741:
@yesimxev @Qazianwar222 - I tried harder. And I've found the way to make LOS 17.1 fully working, Bluetooth Arsenal especially.

What I've done is that I've copied android.hardware.bluetooth@1.0-service file from 17.0 ROM to /data folder and simply executed it. When I tried to run it on system boot it causes bootloops, but when executed after the ROM started it works!

So I have created Custom Command in Nethunter to run in android console on boot (Nethunter boot obviously), please see screenshot attached. Don't forget to:

chmod 755 /data/android.hardware.bluetooth@1.0-service

Other observations:

1. As mentioned above there are some issues with system inodes. To make some space delete unneeded .ogg files from /system/product/media/audio/*

2. I have created symlink /system/etc/firmware to /sdcard/firmware and stored firmware files there

3. Before flashing Nethunter flash Magisk zip, reboot to system and install Magisk apk. If you deleted audio files and created firmware symlink there is enough space and flashing Nethinter together with kernel will be successful.

After these operations I still have some free inodes (4224 inodes in total, 4205 used and 19 free).
[Nexus 6P Android Development] steso90:
Working here! THANKS!
[Nexus 6P Android Development] yesimxev:
Nice job! I'll revise this install guide so it will include both your solution and the 17.0 rom way. Can you share tha patched vendor file of los17.0 please? It includes nexmon fw right?
[Nexus 6P Android Development] Midd741:
Thank you.

Yes, fw_bcmdhd.bin has been replaced in this vendor.squashfs and this is for lineage-17.0-20191220-UNOFFICIAL-angler.zip ROM
[Nexus 6P Android Development] Midd741:
@yesimxev As for lineage-17.1-20200819-UNOFFICIAL-angler.zip ROM - everything goes according to your guide.
[Nexus 6P Android Development] klofisch:
Hi,

at the point where i should setup my Phone i am getting this message.

What to do?

thanks
[Nexus 6P Android Development] Midd741:
Did you try LOS 17.1? (this is screenshot from LOS17.0)
[Nexus 6P Android Development] ChaNg1o:
Maybe any new tutorials in the future? Better version is different with that one based on LOS17.1 aye? I'd like re-write installation manual.
[Nexus 6P Android Development] klofisch:
yes,..i followed the instructions. and this is what it is now
[Nexus 6P Android Development] klofisch:
it might be caused my this...

adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/fstab.angler /system_root/"
[Nexus 6P Android Development] Midd741:
The screenshot you've posted, where we can see "Exchange Server", I have observed only during setup LOS17.0, no such screen on LOS17.1.

Please try/double check/make sure that you trying LOS17.1 ROM

I have found LOS17.0 unstable, maybe that's causing this in your case?
[Nexus 6P Android Development] klofisch:
sorry...yes it is indeed "lineage-17.1-20200819-UNOFFICIAL-angler.zip". Well i got over the issue. I just didnt anticipated that it is really required to format the data partition a second time. I skipped this step at the first try but did the last time and now it works generally fine. I just habe the issue that i cant get the internal Wifi in monitor mode. No issues with an external adapter, but this drains the battery of my old 6P really fast.

I searched for solutions but couldn't get it to work.
[Nexus 6P Android Development] Midd741:
Did you run "nexutil -m2" from android root console?

I'm using custom command:

and then you have to run from kali console:

"export LD_PRELOAD=/system/lib64/kalilibnexmon.so"
[Nexus 6P Android Development] klofisch:
it does something, but the output of airmon-ng is the same and nexutil -m2 gives me the Error "command not found". But it is where it should be and it is executable.
[Nexus 6P Android Development] Midd741:
vendor flashed?

fastboot flash vendor vendor.squashfs

"kernel-nethunter-20230323_130704-angler-los-ten.zip" installed?

Firmware in place?

Double check nexutil:
[Nexus 6P Android Development] klofisch:
mhh ineresting.... i did flash everything mentioned. But the Firmware-Dir is not there otherwise autocomplete the path with tab should have worked. and also nexutil is in place but not seen