yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] yesimxev:
To add drivers, you have to compile the kernel. Although mediatek is not supported by this kernel unfortunately
[Nexus 6P Android Development] yesimxev:
I'll try to add that driver, seems interesting
[Nexus 6P Android Development] 77Pluto:
Okay, I'm waiting. Thanks. 😁
[Nexus 6P Android Development] Frank_Art:
Hello, I got an old Nexus 6p, I follow all the step from this post, but now that I need to make the external wife adapter work there is something that do not work and I'm a bit confused about what I need to do... from what I understood I need to go via adb shell and replace a firmware file under /vendor/firmware/ ?

Another question, in the steps to install NH on android 8.1 is not necessary to flash "Disable_Dm-Verity_ForceEncript" ?
[Nexus 6P Android Development] yesimxev:
Yes I believe android 8.1 doesn't encrypt by default so it's not needed, and firmwares usually copies fine. Is there any firmware in /vendor/firmware?
[Nexus 6P Android Development] Frank_Art:
Yes I cp /sdcard/ fw_bcmdhd.bin.nexmon fw_bcmdhd.bin but still do not work.

If i run "airodump-ng wlan0" I get

-Warning: Detected you are usign a non-UNICODE terminal character encoding.

-ioctl(SIOCSIWMODE) failed: Operation not supported

-Error setting monitor mode on wlan0

-Failed initialazing wireless card(s): wlan0

I flashed, factory angler-opm7.181205.001than via TWRP 3.3, nh-2022.3-angler-oreo, magisk-v25.2 and copied bcmdhd.bin.nexmon from your "link".

I'm thinking maybe I can re try the process using TWRP 3.6? Not sure if it can make any difference.
[Nexus 6P Android Development] yesimxev:
I see you mean internal wlan. I recommend using the zip from this thread, that has an updated libnexmonkali https://xdaforums.com/t/rom-official-kali-nethunter-for-the-huawei-nexus-6p-los17-1.4079087/

- copy Nexmon libs over to /sdcard, then to /system/lib64/ from the nexmon.zip (not in TWRP):

adb push libnexmon* /sdcard/ && adb push nexutil /sdcard/

- and copy using androidsu terminal:

mount -o rw,remount /system && cp /sdcard/libnexmonkali.so /system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system/lib64/ && cp /sdcard/nexutil /system/xbin/ && chmod a+x /system/xbin/nexutil

Then ready to use. nexutil -m2 in androidSU terminal. then use kali terminal

export LD_PRELOAD=/system/lib64/kalilibnexmon.so
[Nexus 6P Android Development] Frank_Art:
hmmm, interesting It was working for few days then after update & upgrade there are problem to let wlan0 work on monitor mode. Someone is experiancing the same problem? I tried to redo the entire flashing and patching process and the problem it's still there.
[Nexus 6P Android Development] Frank_Art:
At the moment when I try to put in monitor mode wlan0 I get this message " ode; ip link set wlan0 up; svc wifi enable"; exit /system/bin/sh: can't create /sys/module/wlan/parameters/con_mode; No such file or directory"
[Nexus 6P Android Development] yesimxev:
That's not for nexmon. assuming you have the libs and fw in place. To use, do the following I mentioned:

AndroidSU:

nexutil -m2

Then open a kali terminal

export LD_LRELOAD=/root/libnexmonkali.so
airodump-ng wlan0

If you need to open a new kali terminal for eg. deathing, again export because it's needed in each terminal session:

export LD_LRELOAD=/root/libnexmonkali.so
aireplay-ng ..
[Nexus 6P Android Development] Frank_Art:
Very kind for helping me debugging the problem! The file where at the right place (before monitor mode was working fine) I duble check it and I replace them and I was still getting:

"-Warning: Detected you are usign a non-UNICODE terminal character encoding.

-ioctl(SIOCSIWMODE) failed: Operation not supported

-Error setting monitor mode on wlan0

-Failed initialazing wireless card(s): wlan0"

I reformat and redone the hole process, I run: airodump-ng wlan0 it work for few seconds then it crash i get a driver error and it shut down the terminal.

From that crash i keep get

"-Warning: Detected you are usign a non-UNICODE terminal character encoding.

-ioctl(SIOCSIWMODE) failed: Operation not supported

-Error setting monitor mode on wlan0

-Failed initialazing wireless card(s): wlan0"

I may try to run nh on Los17.1 .. I may be more lucky

Forgot to mention, I disassembled the phone in manner to change the battery, is it possible that on the process the heat from the heatgun may have damage the wifi module? (wi fi works fine) Thanks
[Nexus 6P Android Development] yesimxev:
You're welcome!

No, it is definitely just some of the files not what they should be. Are you using this file?https://gitlab.com/kalilinux/nethun...r/nexmon-fw/fw_bcmdhd.bin.nexmon?inline=false

Copy to /vendor/etc/firmware/fw_bcmdhd.bin (if I remember the path correctly)

Also you could use nexutil and libs from here https://www.androidfilehost.com/?fid=8889791610682951480

Nexutil to /system/xbin/ (android)

Libs to /root/ (kali)

Then do nexmon and exports, airodump. The scan should run without any problems. I noticed the crash on hijacker app because those used 32bit (armhf) nexutil, so the one above is arm64. Hopefully fine
[Nexus 6P Android Development] Frank_Art:
O

Oh I see, I was still have the libs files on lib64 folder. How do I copy libs file to /root/? It keep tell me that root is Read-only file system, do I need to: mount -o rw /root/ ?
[Nexus 6P Android Development] yesimxev:
The kali chroot shouldn't be ro. So just do cp /sdcard/libnexmonkali.so /root/ in kali terminal
[Nexus 6P Android Development] Frank_Art:
..e we go now it work! Thanks!
[Nexus 6P Android Development] yesimxev:
Awesome! The only issue on LOS17 is that handshake capture is not guaranteed. It's a thing that need to be patched. In case if you capture and crack an example successfully, please let me know. Aircrack shows no EAPOL in capture. You may also try hijacker but seems airodump is crashing in it https://androidfilehost.com/?fid=10763459528675578971
[Nexus 6P Android Development] Frank_Art:
Wait a minute ^^ I made it work on Android 8.1 oreo, at the end i did not try to install it on LOS17.
[Nexus 6P Android Development] Frank_Art:
I'm setting up a lab to test wifite and see if it can capture, store and crack wpa2 handshake, later i dont mind to try run it on LOS 17.1 and test it with it as well.
[Nexus 6P Android Development] yesimxev:
I'm curious if it works on your oreo actually, don't worry about los17
[Nexus 6P Android Development] Frank_Art:
I tested with 3 different routers on different type of clients ... long story short deauthing work but is not capable to capture the handshake.
[Nexus 6P Android Development] yesimxev:
I see yes the firmware or the kalilibnexmon needs some patching
[Nexus 6P Android Development] futuremeproblems:
First off, thank you for all the work you guys have done here on the 6p. I've fumbled my way to getting nethunter up after about 60 hours of dev and relentless scouring of the internet. But now, I need some help. I can't get the internal GPS to pipe the data in to the "wardriving" app, also it won't work if I run Kismet separately in the kali terminal.

Specs:

Android 8.1 Oreo

Nexus 6p

Nethunter 2022.3

Is the wardriving app using the kismet default port 2947 for gpsd?

Separately, anyone else have issues running the kismet UI in the chrome browser in Oreo? Nothing shows up except a blank kismet screen with no data.
[Nexus 6P Android Development] yesimxev:
Yes can you update the nethunter-utils with apt. After that, you need to enter the sources to /etc/kismet/kismet_site.conf. it will be included automatically in the next release in the next few weeks as wardriving gets an update in NH app and it will utilize kismet_site.conf

log_template=%p/%n
log_prefix=/captures/kismet/
gps=gpsd:host=localhost,port=2947
source=wlan0
source=hci0
[Nexus 6P Android Development] futuremeproblems:
Apologize for the delayed response and thank you for the quick reply!

I applied the above but no change. In the gpsd config file, what device should I have GPSD point to in order to get the GPS data? I'm sure I messed up the code at some point along the way. I'll try reloading everything with the new release once it's out and see if that clears everything up.

Thanks again!
[Nexus 6P Android Development] yesimxev:
/etc/kismet/kismet_site.conf - what do you have in there now?

You should start android gps provider and gpsd in NH App, then press start kismet
[Nexus 6P Android Development] futuremeproblems:
It's working! Mostly...

I put what you mentioned in the kismet_site.conf file, except I fat-fingered the gpsd line and had "gpsd=gpsd..." vice "gps=gpsd..." So that solved that issue. It's still throwing an error with the wlan0 when I initiate kismet in the wardriving app, but it works when I run kismet in the kali CLI:

LD_PRELOAD="/system/lib64/kalilibnexmon.so" kismet

It also gets a little finicky after changing to lock channel and try to go back to hop channel, but I'll take it!

Thanks again!
[Nexus 6P Android Development] yesimxev:
Awesome! Yes LD-PRELOAD is needed in all kali terminal windows. You can do export LD_PRELOAD=kalilibnexmon.so if you need to run multiple commands.

Try this kalilibnexmon. It's better with channel lock https://www.androidfilehost.com/?fid=8889791610682951480
[Nexus 6P Android Development] digiuseppefederico:
Hi guys

I'm trying to install nethunter on stock Oreo after have it used on lineageos for quite a bit.

I've read all the posts on this forum from the beginning but I'm confused about the proper steps to follow.

In the first post it seems that is only necessary to flash NH and magisk to make it works but reading further it seems that also kalilibnexmon.so and other files are necessary to use internal wifi monitor mode like in lineageos.

So I've not understood if I have to follow the same steps I've used flashing over lineageos or just a part of them or not at all...

Is there someone so kind to help me posting a simple up to date installation process to follow to make the last nethunter image work properly on nexus 6p?

I think that it can be useful also for other ones approaching this cool project.

Thanks for the help and thanks all the staff for the good work
[Nexus 6P Android Development] yesimxev:
The steps are created without nexmon somehow. You basically need to copy the nexmon files and firmware which were mentioned. On los17.1 it was flashing vendor because of firmware were on ro partition. Nexmon is a different project, however I preferred to add to my guide so it's all in one place. When you are done with all the installation steps, copy nexutil to /system/xbin as executable, firmware to /vendor/etc/firmware/ and kalilibnexmon.so wherever you need and ready to work in kali terminal, as recommended on the los17.1 thread
[Nexus 6P Android Development] digiuseppefederico:
I see.

Thank you very much.

it's clear now!
[Nexus 6P Android Development] digiuseppefederico:
Hi guys

Here a suggestion to use internal wifi monitor mode in a more comfortable way:

Instead of writing "export LD_PRELOAD......." in each terminal window putting the string at the end of /root/.zshrc just once do the job for each terminal window open so on.

Now you can create just a custom command in nethunter to start wlan0 monitor mode with:

"su -c "nexutil -m2";sleep 2 && exit".
[Nexus 6P Android Development] digiuseppefederico:
I have a problem using wardriving:

I'm using nethunter 2022.4 so the file /etc/kismet/kismet_site.conf is already there with permissions 660.

If I open nethunter app, go to wardriving, set "android gps provider" on, set "gpsd in chroot" on, set the proper wireless interface and click on the button "launch kismet in nh terminal", the app saids:

"kismet will launch after next position received. waiting...." and nothing happens.

Localhost:2501 is unreachable.

If I run kismet from kali terminal it starts, I can go to localhost:2501 but kismet said each 30 second more or less:

"no usable data from gps in over 30 seconds, reconnecting..."

If I run cgps in kali terminal neither there I can see gps data.

If I use android gps with other apps it works properly.

So it seems that the problem is that gps data is not properly communicated to Kali Chroot.

Any suggestion?
[Nexus 6P Android Development] digiuseppefederico:
Ok maybe I've found what was wrong...

After installing nethunter I've disabled all the google app on stock Oreo.

I've tried to use WiGLE WiFi app from nethunter store to test gps in it and the app asked me to update google services.

So I've re-enabled google play and updated google services.

After the update WiGLE WiFi started to work and wardriving in nethunter app started to work too.

Hope this could be useful for someone else!

Cheers
[Nexus 6P Android Development] digiuseppefederico:
hi guys.

Does someone has encountered problem using kex manager?

After setting up the local server when I start the server the phone freeze.

any suggestion?
[Nexus 6P Android Development] digiuseppefederico:
I've found something:

Entering

kex

in kali terminal after the phone boots I receive an error, than I'm asked for a password, then I receive an error again and I am took back to the bash prompt.

But after that kex manager from nethunter app works well till the next reboot.

After a boot, starting kex server from nethunter app without following the previous steps ends with the phone freeze.

At the end I've created a custom command that runs in background on boot with

echo | kex

inside it to make the process simpler, not knowing how to really solve the issue.

This works for me.

I'd be happy if someone would share a better solution!

Again hope this can be useful.

Cheers
[Nexus 6P Android Development] yesimxev:
That's a great discovery. I didn't know Google services does the background job, awesome!
[Nexus 6P Android Development] yesimxev:
That's strange because kex command is not related to vncserver/tigervnc which kex tab uses in NH app. Can you try simply vncserver from kali terminal, see what happens?
[Nexus 6P Android Development] digiuseppefederico:
Disabling my custom command on boot if I run

vncserver in Kali terminal my phone freeze in seconds like enabling kex server in kex tab.

If I run kex in Kali terminal and vncserver after it vncserver seems to start properly.

Yes it's really strange now that you said that the two is not related!
[Nexus 6P Android Development] yesimxev:
Can you show me the output of "which kex"
[Nexus 6P Android Development] digiuseppefederico:
/usr/bin/kex
[Nexus 6P Android Development] yesimxev:
And what's in there? cat /usr/bin/kex
[Nexus 6P Android Development] digiuseppefederico:
Here
[Nexus 6P Android Development] yesimxev:
Would you edit your comment and add

[CODE][/ CODE]

brackets around it, would be easier to review. So that's win-kex package anyway which is definitely for Kali in Windows WSL. Anyway, there must be a command that helps you. Will figure out
[Nexus 6P Android Development] digiuseppefederico:
Sorry here we are
[Nexus 6P Android Development] digiuseppefederico:
Thanks a lot for your teaching and for pointing me in the right direction!

Now i will try to debug the situation and i will let you know!
[Nexus 6P Android Development] yesimxev:
No probs, I will also try and see what could be android/chroot related command that helps.
[Nexus 6P Android Development] digiuseppefederico:
Thanks to your lead I've found how to solve the issue!

Inside kex code I've found a function making kex service in nethunter kex tab working.

It calls /usr/lib/win-kex/xrdp/xrdpservice and inside it another function calls /etc/init.d/dbus start.

So

/etc/init.d/dbus start

Is the solution to make kex server inside kex tab working ;)
[Nexus 6P Android Development] digiuseppefederico:
The strange thing is that dbus is enabled in rc.d but if I run /etc/init.d/dbus status after startup I have

Dbus not running ... Failed!

I've tried to update-rc.d but without success

What I have to do is to start dbus service manually in a Kali terminal or to create a service inside nethunter app
[Nexus 6P Android Development] yesimxev:
Ah no, this is something I discovered on another phone, it solved the soft reboot. But recently I wanted to check and push and it did not help, reboot was there. I'm glad you could confirm that it actually helps!

I'll add a simple service dbus start before executing vncserver with the start kex button.

I also added the start on boot option to kex tab which creates /system/etc/init.d/99kex for kex service to run automatically, but seems like scripts doesn't run in recent android versions
[Nexus 6P Android Development] digiuseppefederico:
Hi yesimxev.

I've a couple of general questions here:

- under my nethunter tabs 'usb arsenal' is missing, is it ok?

- I've read in the first post of this forum that mana has been removed. What this means? Is 'mana evil access point' under nethunter tabs not working at all or is there another way to use it?

- I have Re4s0n kernel installed in my nexus 6P.

If I want to use internal Bluetooth card I have to recompile Re4s0n kernel or is there another kernel compatible with my device that I can directly flash over it?

Hope i'm not bothering you with all my questions.

Thanks for your time.

Greetings
[Nexus 6P Android Development] yesimxev:
Yes that's fine because Arsenal is for 4.x kernels. 3.x i prefer anyway, hid is always enabled, RNDIS BadUSB works out of the box, storage works with drivedroid.

You'd need to. I maintain lineage 17.1 kernel for 6P, you can try that if you don't want to switch, maybe it boots. I need to zip the latest version
[Nexus 6P Android Development] digiuseppefederico:
I see.

Where I can find the kernel you suggested me?

And what about mana?
[Nexus 6P Android Development] yesimxev:
kernel-nethunter-20230301_131424-angler-los-ten.zip | by yesimxev for Nexus 6P

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Mana instructions at the end post https://xdaforums.com/t/rom-official-kali-nethunter-for-the-huawei-nexus-6p-los17-1.4079087/
[Nexus 6P Android Development] digiuseppefederico:
Thanks a lot !

I will give a try
[Nexus 6P Android Development] digiuseppefederico:
Nothing to do.

Los kernel doesn't boot with stock Oreo.

I will try to recompile the Re4s0n one
[Nexus 6P Android Development] yesimxev:
Sure, do the same patches as here. https://github.com/yesimxev/android_kernel_huawei_angler_pixel/commits/nethunter-10.0
[Nexus 6P Android Development] riomenx:
Which bluetooth adapter works in the bluetooth arsenal to attack. I am using RTL8761B. The interface is defined as hci0, but when scanning it does not see the device. Can use sena ud100?
[Nexus 6P Android Development] riomenx:
I downloaded kernel-nethunter-20230301_131424-fisher-los-ten and flashed it via twrp. The system stopped booting. After installing the kernel, I did the formatting on the left. The kernel is not suitable for android 8.1?
[Nexus 6P Android Development] yesimxev:
It's for lineage 17.1. stock oreo is not developed anymore
[Nexus 6P Android Development] riomenx:
You solved the problem of loading the kernel?
[Nexus 6P Android Development] yesimxev:
Just flash the NH patched stock oreo. You need to make a zip, better than flashing 2023.4 which was the last oreo zip on kali website

git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project
cd kali-nethunter-project/nethunter-installer
./bootstrap.py
./build.py -k -d angler --oreo
[Nexus 6P Android Development] riomenx:
Thanks for the answer. Can you describe the solution better. You will help many users. If I understand correctly, then I need to create a zip with the stock Oreo firmware and the NH patch. Where can I download the NH patch. You provided the code. The code is entered into the kali terminal. You have a .zip left. That would make it easier for everyone :)
[Nexus 6P Android Development] yesimxev:
I mean you create a zip with the patched kernel, for Android 8.1 Oreo (stock i mean not lineage OS, sorry my bad 😎) see the features https://nethunter.kali.org/kernels.html

Los17.1 kernel has new drivers, such as internal Bluetooth driver and rlt8xxxu with rtl8188eus. It will be added to the repo soon
[Nexus 6P Android Development] digiuseppefederico:
Sorry I've been away for a while.

No, I've not solved the problem of loading the kernel because I think Los kernel is not working with stock Oreo.

I think I have to recompile the kernel with the patches suggested by yesimxev but I've not tried yet
[Nexus 6P Android Development] digiuseppefederico:
Is the code posted here for downloading and creating the patch to install?

Sorry I have no experiences compiling yet...
[Nexus 6P Android Development] riomenx:
"Mana is being replaced, for now you can downgrade iptables in chroot."

Why downgrade?
[Nexus 6P Android Development] riomenx:
On Android 8.1 Oreo didn't work for me

bluetooth inventory. I have upgraded to LOS17.1. The situation has not changed. Maybe I'm using the app incorrectly or don't understand how it works. I'm using L2ping and I'm trying to mute a Bluetooth speaker that is paired with another device. Nothing comes out. If the bluetooth speaker is paired with another device, then the scanner does not see the bluetooth speaker. If there is no pairing, then I can see the device and send packets using L2ping. Then what's the point of L2ping.

Bluetooth adapter using external UD100-G03
[Nexus 6P Android Development] riomenx:
I uploaded screenshots. Output of bluetooth arsenal and kali terminal:
[Nexus 6P Android Development] yesimxev:
Yes the code above will make a flashable zip for you for oreo
[Nexus 6P Android Development] yesimxev:
You use properly. Did you use the kernel above which supports internal BT? Anyway, l2ping won't be always successful as most devices won't crash or dispair with it. I experienced interference once with Nokia 3.1 + cheap chinese BT headset
[Google Pixel 3 Questions & Answers] krakheadmartha:
Hi,

My Pixel 3 was rooted with Magisk. After uninstalling it, I lost root, tried to re-root with Magisk and ended up stuck in fastboot mode with "error boot prepare" and now can't exit or power down.

I assume I won't be able to save my data, is there any way to reset/flash stock image?

adb fastboot devices show my Pixel 3

adb fastboot reboot works but goes right back to fastboot mode.

If I'm posting in the wrong forum, can you please direct me to the appropriate one.

Thanks

Martha.
[Google Pixel 3 Questions & Answers] jd1639:
I assume your bootloader is unlocked? Have you tried flashing the factory image with fastboot? I'd first try using the flash-all batch file with the -w removed. That way you might be able to save data.
[Google Pixel 3 Questions & Answers] krakheadmartha:
Thanks for your reply.

After countless tries to flash-all with fastboot as well as flashing different options nothing worked...

I originally rooted my phone from a Mac with no issues. I could still run fastboot reboot and other commands but it would revert back to the fastboot mode.

I finally loaded up Parallels and tried fastboot flash-all from Windows and managed to reset on the first try.

Not sure why it didn't work with my Mac... but I'll always use Windows from now on.

***SOLVED!***
[Google Pixel 3 Questions & Answers] jd1639:
I'm not very familiar with mac's. You need to use the .sh file, which I'm pretty sure you know. But you also need to edit the batch file. Command lines that start with / need to be changed to ./ Or something like that. I don't remember exactly.
[P3300, MDA Compact III  upgrading etc.] scaff:
Hi , I've been playing with these roms here for the last few days and before messing around tomtom & gps were all working fine, but @ the moment tomtom will not detect the gps. I think I have the Vanilla 4.02 on @ the mo but I've loaded a few today so I'm not sure but it is the same issue with them all.

Second question which is a little easier do I ned to keep removing the sd card before flashing ?

Cheers & Top site Thnx
[Samsung Galaxy S10e Guides, News, & Discussion] djg269:
Hi all,

I just found out that in the battery settings, now is the option for putting apps to deep sleep, so they will only run if you use them.

I didn't see it before, so to me it's new ;)