yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] UsPdSr:
Hey [MENTION=9969174]kAh00t[/MENTION](D....)!

It's great to hear from you again.

Not to seem too emotional, but I was a bit sad that you didn't get back to me, or write.But nevermind.

I found you on Twitter a couple of Month ago, but I thought you were busy and didn't want to bother you.

I am very, very proud and happy for you.Seeing what you achieved(jobwise in cs, your certificates foremost and the podcast(I am not so in to them, but if you send me a link to one of yours, which is interesting, I would gladly give it a shot...) :)

Re4son achieved quite the unthinkable.

They found a patch to get rid of the nasty external Wifi adapter 'bug'.

Kimocoder added some amazing features with his AC support.

I would recommend to check his github repository out.I think he contributes a great deal of new innovations to the pen-testing scene.

Do you purchased a AC adapter perhaps(Realtek 8814au/8812au/8811..)?

The new kernel supports them as well.

So, what can I do for you? ;)

Best regards,

UsPdSr

Btw:

https://forum.openwrt.org/t/d-link-dir-615-e3-firmware/33254

PPS

VM are vulnerable against other, of course... :)

---------- Post added at 02:29 PM ---------- Previous post was at 02:19 PM ----------

@Re4son How do you come forward with the implementation of Nexmon into this kernel?

I tried it and couldn't get it to work.

Afterwards did I compiled them from Nexmon's repo by myself, but couldn't get it working as well.. :/
[Nexus 6P Android Development] kAh00t:
Sorry for going dark!

The last 10 months of my life have been an absolute whirlwind, I've not had much in the way of time or energy to engage in online forums/community. I should have messaged to say I was dissapearing for a while though, that'd have been less rude. Thanks for kind words re: my progress, it has been so intense yet I have really only scratched the surface! Lots to look forward to.

I wonder how you found me on Twitter! OSINT is a wonderful thing ^_^ [MENTION=1982549]Fuzz_[/MENTION]sh is my handle there, [MENTION=1860105]Weegie[/MENTION]cast is our podcast handle. You should have messaged - I'd have been happy to hear from you!

I actually downloaded your nethunter zip you posted the otherday with worked good! flashed onto a new install of the latest 8.1 stock image.

I was very excited to see there stillis so much effort being put into the development of Nethunter , it is quite the passion project!

I thought I had a variety of wireless cards with different chipset, but having checked them all it seems they are all just AR9271!:

TP-Link TL-WN721N AR9271

DNUA-93F Atheros AR9271

AlfaNetwork AWUS036NHA AR9271

Got any links to some Realtek ones? I'll probably pick up a few to test

Re: What you can do for me - to be honest I just came on to say hey! I had given my Nethunter phone to a colleague to use for their university degree and just got it back, so it is now all up to date again. Unfortunatly I am having some bad issues with apt and nethuner -

"root@kali:~# apt install byobu

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.2.0-21 is to be installed

libgcc-s1 : Breaks: libgcc-8-dev (< 8.3.0-27) but 8.2.0-21 is to be installed

E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages."

Seems to happen when I attempt to download a few packages, and a common issue with Kali, tried the first few Google pages of remediation steps but no joy! Somewhat limits the purposes if using the phone but I bought a nice Thinkpad W540 to handle my Kali stuff, this is just for fun ^_^ If you have any suggestions however I'd be happy to hear them!

When I finally get a moment (new Podcast tonight) I'll have a look at that DLINK thread!

Kind regards,

Fuzz
[Nexus 6P Android Development] UsPdSr:
Absolutely no harmed feelings, mate.

I knew that you going to focus on your work and didn't expect a bunch of flowers. ;)

I am everywhere.

Joke..half a year ago did I saw a post on Re4son's twitter account, in which someone assembled his Nexus 6P with a very neat 3D printed mounting.This person wrote that he just started and I saw on his account were he came from.

That was that.

Yeah, perhaps.

Sure.

I looked up some options.

I give you a short description of what there are..

https://www.ebay.de/itm/173888821040

Here you have a stealthy, inexpensive, but very reliable device, with a Ralink chipset RT5370.This one has no AC capabilities, just fyi.

https://www.ebay.de/itm/293521937779

This is a very affordable generic adapter with AC capabilities.It has a Realtek 8811au chip.

https://www.ebay.de/itm/222964235091

This one did I buy a week ago.

It has the same chipset as the device above, but is apparently from Alfa.

So the quality is definitely better.Although you pay more than double the price.

I have a bunch more suggestions, but I think with the last one you have a good idea, what to buy or not.

https://www.ebay.de/itm/322387070754

This is probably the best adapter respective the one with the best support.

AC, Realtek 8812au chipset.Definitely a good choice, but costlier.

Same here.

It seems to be a problem with gcc, binutils and/or build-essential.

Strangely is no bug report to be found on Nethunter's issue section.

I use my Nexus 6p not that often with Nethunter anymore(it is my second one, the first one bricked end of last year).

For Nethunter did I get a Nexus 5, which works flawless and this consistently..

It's just a customized firmware for your test router.You'll find Openwrt, Luci and Lede there.
[Nexus 6P Android Development] UsPdSr:
[MENTION=9969174]kAh00t[/MENTION]

After looking continously into Nethunter's gitlab issue section over the past week and didn't see anything which remotely matches the package issues you and I encounter, did I found a solution earlier, after trying Re4son's new kernel for the hammerhead and had the same problem after upgrading

It seems to be a temporary fix for the package manager.

[MENTION=4207992]Re4son[/MENTION]

I couldn't get Nexmon to work on the Nexus 5, with your new kernel.

The internal Wifi chipset runs with

, but cannot find any other clients.. :(

The same goes for the Angler with the Oreo kernel, although it can not run any of the wireless tool at all.
[Nexus 6P Android Development] UsPdSr:
[MENTION=8262629]yesimxev[/MENTION] [MENTION=4207992]Re4son[/MENTION] [MENTION=3823682]kimocoder[/MENTION]

It would be much appreciated if you guys could take a look at the Nexmon issues..!?
[Nexus 6P Android Development] yesimxev:
Been a while now, gone busy IRL due to work vs. virus situations.

I've just did a clean flash of 2020.2, to see Nexmon. Package issues have been resolved on kali side with the libgcc-s1, libgcc-9-dev, etc. (after a succesful dist-upgrade)

Nexmon works. I've gone crazy when Re4son told me to make sure you use

source monstart-nh

in NH terminal to start monitor mode. Also, make sure you have the patched firmware from our Gitlab repo.

Copy the fw over the original one in /vendor/firmware/
[Nexus 6P Android Development] Mr.č_1:
hey iam currently using abc rom now . can i using nethunter in this rom ? :D
[Nexus 6P Android Development] TheMarc0:
I tried to solve your problem, I did this.

[MENTION=7758199]UsPdSr[/MENTION]

I used the Factory Images for Nexus 6p!

8.1.0 (OPM7.181205.001, Dec 2018)

https://developers.google.com/android/images#angler

I used the platform-tools_r26.0.2-windows

https://dl.google.com/android/repository/platform-tools_r26.0.2-windows.zip

8.1.0 (OPM7.181205.001, Dec 2018)

angler-opm7.181205.001-factory-b75ce068.zip

1. Start flash-all.bat

Restart

2. Android 8.1 first start, the first standard settings are executed.

Restart / Bootloader

3. Install TWRP twrp-3.4.0-0-angler.img 16.5M 2020-06-21 21:31:58 EDT

Fastboot flash recovery <filename>.img

4. Start TWRP Recovery / Reboot into TWRP, insert USB drive.

- Flash NetHunter image

Nexus 6P Oreo 2020.2 1.3G 01bee92fde6f0afb5afaadcd001433730c1994145d92fb5691427e1c3f36bc5b

https://images.offensive-security.com/nethunter/nethunter-2020.2-angler-oreo-kalifs-full.zip

- nethunter-2020.2-angler-oreo-kalifs-full.zip

4.1 Reboot / Start Android

4.2 Restart / Reboot into TWRP, insert USB drive

- Flash Magisk

Magisk-v20.4.zip

5. Reboot

6. Run NetHunter App + Magisk Root rights!

7. Reboot

8. Run NetHunter Terminal / KALI select!

9. Source monstart-nh

It's not working!

airodump-ng wlan0

wifite -i wlan0

aireplay-ng -9 wlan0

10. Reboot TWRP Recovery

Copy this file

11. fw_bcmdhd.bin.nexmon --> https://gitlab.com/kalilinux/nethun...69/oreo/angler/nexmon-fw/fw_bcmdhd.bin.nexmon

fw_bcmdhd.bin --> /vendor/firmware

Replace!

12. Reboot System

13. Run NetHunter Terminal

source monstart-nh

airodump-ng wlan0 --> Works

wifite -i wlan0 ----> Works

aireplay-ng -9 wlan0 --> works

Unfortunately the whole system is very unstable with Nethunter!

I don't know why that is!
[Nexus 6P Android Development] UsPdSr:
[MENTION=10165945]TheMarc0[/MENTION]

Thank you, that you took the time to look over the issue.

I will give it later definite another try.

Great step-by-step guide..a small mistake, or more likely a oversight.

You wrote that somebody would flash the Nethunter image, or kernel and then the Magisk.zip.

I, personally, always flash Magisk, or SuperSU first and then Nethunter, but perhaps is this not the case anymore.

Maybe you could correct that, provided that I'm not, wrong, accordingly.

What did you mean with instabil system?

I have so far not noticed any major issues or instabilities with Oreo/the Nexus 6P.

PS

I saw that you use Windows, from your plattform-tools recommendation, but I would advice everyone better to do this with fastboot manually, command from command..

Thanks for your contribution & greetings!

---------- Post added at 02:24 PM ---------- Previous post was at 02:06 PM ----------

As almost pure stock rom, would I think so.

I didn't like the last two releases from kantjer, mainly because of the QS bar.

The factory rom is very bloated, although with the right system app removal tools, very usable.

If you are happy with ABC rom and Nethunter runs on it as well, then much better. :)

---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------

Hm, after I compiled a new kernel for the Nexus 5 two days ago, I had the package issue again, even with the temporary solution I found.

Nope.

Myself and many other user here and on reddit and twitter have reported otherwise.

What do you mean?Have I said somewhere I haven't?

I always use another terminal app, because I like neither the NH terminal, nor Termux, but of course have I tried that in NH's terminal. ;)

I clone the entire repo, hmm, every three days, but okay.

First of all thanks, I remember that I tried that before, but this would be a very important annotation for the user, don't you think? ;)

Best regards

UsPdSr
[Nexus 6P Android Development] TheMarc0:
Hello [MENTION=7758199]UsPdSr[/MENTION]

You're right, I did in the Step by Step, Magisk later installed after Nethunter. I changed my step by step!

Yes i used the platform tools that i could run the flash-all.bat, auto script but yes if you do it manually with fastboot it is the same, but i was a bit lazy ;)

For the unstable system I noticed a lot of apps crashing and a slow system, could be because Nethunter 6p has this 4 CPU bug. Maybe I am affected by this!!!

I will do more tests, but you are right the 8.1 stock is full of Googel Spy*** ;)

Currently there are problems with the Hijacker App v1.5-beta.12 https://github.com/chrisk44/Hijacker

LOGCAT:

Line 15388: CANNOT LINK EXECUTABLE "crash_dump64": "/data/data/com.hijacker/files/lib/libnexmon.so" is 32-bit instead of 64-bit

But the way I see it, many people have this problem and #kimocoder also said that it only works on Android 7.1.x! (I will try to use the 64bit libnexmon from Nethunter!)
[Nexus 6P Android Development] UsPdSr:
Thanks for correcting the oversight in your instructions!

It is very well written and foremost understandable for beginner. :)

It would be unfortunate if it not check out because of it.

Hijacker doesn't work under Oreo.

As you saw by yourself has kimo opened a regarding issue, but if you just search for the 6P, you'll find another issue within the OP very detailed and well explained, which and how many attempts he tried to solve this problem.Unfortunately was he not successful.

The/my problem with those batch or bash scripts are not with anyone's possible laziness, because you type like 8 fastboot commands, rather that they often screw installations, because of different reasons (userdebug.img was one of them, as an example).

I wanted to recommend you one of three apps, I regularly use to debloat or simply get rid of unwanted apps on bloated systems.

https://www.apkmirror.com/apk/jumob...tem-app-remover-root-7-1-release/#description

Among other of course 'Titanium Backup' and often are files left, which you can good remove with 'Apps2SD Pro'.

Maybe you can use it, in case you didn't knew it already.

The BLOD problem is annoying.

This is now my second Angler.The first died last year.

But I like that it's very inexpensive.

If you look through eBay for example, even the Nexus 5 cost more.. ^

Perhaps a nostalgic thing.

Let me or the others know, if you come across anything cool or new for this device or solve something. :)

Best regards

UsPdSr

---------- Post added at 06:50 PM ---------- Previous post was at 06:45 PM ----------

[MENTION=10165945]TheMarc0[/MENTION]

PPS

https://github.com/chrisk44/Hijacker/issues/53
[Nexus 6P Android Development] UsPdSr:
So, after finally gettting my hands on a OnePlus 6 I lost the focus on the topic for some time;although I even used the Nexus 6p still in tandem after getting the OnePlus..^^

Android Ten is an incredible pain in the ass.

In addition is the kernel compiling with clang somewhat of a secret in regard of tutorials and YouTube videos, which sucks enormously, after getting a quipped to using one toolchain...

I compiled a new kernel for Android Ten successfully, with the source in this sub-forum here.*

Of course, I didn't test it and forgot I had it, after I received the new phone.

I am very neat with my backups, but I have a modified Chromebook which is currently running Ubuntu(yeah, I am not that keen either..) with just 64GB storage, which I use at the moment for some stuff.

Because the storage is extremely sucky, I somehow deleted it. o/

The good news is, I know that it worked, so if I have the time to compile it again I let you guys know.

I think this is enough for my daily diary entry and back to topic it goes.

I got the 6P with Nexmon finally working, but the system is practically unusable.

I have never experienced this device so unstable and before something happend, I will wipe the system asap.

If the dev's have no idea, eventually we have to get used to the thought that a stable usage of the chipset's internal monitor mode is only possible with Android 7.

I hope you guys are well and your families of course and you behave..

Greetings!

UsPdSr

Annotation

*https://xdaforums.com/nexus-6p/development/kernel-alpha-kernel-v2-0-t4114393
[Nexus 6P Android Development] draco42:
airodump-ng can't change channel

Hello,

Thanks for all the information in this thread. With it I was able to get NetHunter and nexmon installed on my 6P with stock Android 8.1.

I used the nexmon firmware from https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-devices/-/tree/77649717feecda29b7aedd3dd0aa7dd05e398e69/oreo/angler/nexmon-fw"

However, there are a few issues I can't seem to solve.

One is, airodump-ng is unable to change the channel. i have to manually change the channel with:

nexutil -k<chan>

Is this expected behavior? I thought kalilibnexmon.so would intercept and translate those ioctls for us.

Next issue is, I am unable to manage wlan0 purely from within kali chroot environment. To be able to successfully use nexutil, I must first do:

ifconfig wlan0 up

from the BASE android environment.

Trying to do it from within chroot gives me this error:

root@kali:/# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted

root@kali:/# LD_PRELOAD=/system/lib64/kalilibnexmon.so ifconfig wlan0 up
SIOCSIFFLAGS: Operation not permitted

This happens both with or without the preload library. Am I doing something wrong?
[Nexus 6P Android Development] FreshGaro:
I'm having the same issue changing channels.

I installed 8.1 stock, twrp, Magisk, Nexmon firmware/nexutil, NetHunter 2020.3 (kernel and chroot), and this is the closest I've gotten to getting Nexus 6P monitor mode to work completely for the internal wireless chip.

The nexmon installation I'm using I complied myself using kimocoder's nexmon repository, though I've also tried the original repository which had an issue with the channel always being set to -1 or 36, strangely.

I tried a bunch of other variations of android/firmware files/apks and this did get me working monitor mode with frame injection, but the channel of the wireless chip won't change automatically.

nexutil -k<channel> does change the channel *temporarily* but the radio will change instantly back if it's connected to a wireless network.

One circumvention I've tried is:

export LD_PRELOAD=libnexmon.so
nexutil -k1; airodump-ng -c 1 wlan0

# Then in another terminal tab, run aireplay-ng while airodump-ng holds chip on channel 1
aireplay-ng -a <bssid> wlan0 -1 0 # auth test

While this does work to get simple injections like auth/deauth working, the chip will still change channel if connected to a wireless network. Turning WiFi off in Android settings seems to disable monitor mode stuff as well, so that can't be used to circumvent Android's penchant to connect to any network it recognizes.

I can't get reaver to work even with this manual channel management though. It fails trying to associate.

I'm pretty sure the chip's firmware is fine, but either the kernel or library has one or more issues dealing with the chip's channel as draco42 found out. Is this a known issue or a mistake on our part?

In my experience, everything in the chroot behaves identically to inside an adb shell.

By the way this is a really fantastic project and I hope its installation process gets sorted out and streamlined. A few suggestions I have would be:

- Put the "export LD_PRELOAD=libnexmon.so" line of code at least in the .profile of the kali chroot on installation, or in some hook of Android's bash shell launching so that apps like Hijacker work since it doesn't support a prefix for this device. (Can change recompiling the app pretty easily I guess, but that's not in everyone's skill set.)

- Include wifite2's dependency programs into the nethunter zip

- Supply an actual installation script to go from scratch to completed nethunter setup. (I have made a script for myself that is nearly there, but like I said I'm clearly missing something).

Might make a twrp backup and try Android 7 to see if it has more complete support.
[Nexus 6P Android Development] yesimxev:
Android 7 is fully supported, however 8.0-10.0 support is on the way by [MENTION=298251]draco42[/MENTION]

Will post and update links as soon as it's ready! Channel switch looks promising
[Nexus 6P Android Development] UsPdSr:
Hey yesimxev :highfive:

I looked into Nethunter's device repo on gitlab and couldn't verify if the kernel for Android 7 Nexmon supported, as well as the recently implemented ac driver - for example the Realtek RTL8812AU..?

I saw that Re4son reworked some stuff a couple of months ago.

The Nexmon files are not visible and according to the kernel.yml, is the source for the 7'er kernel still the "old" one from jcadduono.

It would be nice if you could give me (us) a short answer to the question.

Best regards!

UsPdSr
[Nexus 6P Android Development] FreshGaro:
So in my testing, with and without kali nethunter 2020.3, I experience the exact same results for the firmware on my device with 7.1.2 as with 8.1 and 8.0.0.

The only difference is that airodump-ng works within Hijacker though its other tools like reaver and mdk3 in it still don't work.

I can still use aireplay-ng to deauth in all these versions if I manually set the channel, but I can't seem to do a deauth *and* capture handshake with airodump-ng because it seems like airodump freezes the second aireplay has control. Is this known? The firmware seems really *close* to fully functional and I can't tell if there's some secret sauce step I'm missing or if this is the current progress.

You had said it was fully supported, is there better functionality dependent on specific versions of something?
[Nexus 6P Android Development] yesimxev:
libnexmon and kalilibnexmon is going to be uploaded soon, but I'm away from PC most of the day. Will inculde both for 8.1 and 10. Will include example for using LD_PRELOAD. Hopefully tonight

For nougat, this was the last working version I'm aware of. Please see installation https://build.nethunter.com/contributors/re4son/angler/
[Nexus 6P Android Development] yesimxev:
10 is done. We'll update this too as soon as it's ready
[Nexus 6P Android Development] FreshGaro:
That's awesome, I'm really excited for your release!

I'll try both that nougat version and version 10 as time and availability opens
[Nexus 6P Android Development] FreshGaro:
So I tested 7.1.2 under a lot of the same nexmon firmware builds and had the exact same channel issues and inability to capture handshakes and properly run most of those binaries like reaver.

Are these known limitations intended to be fixed for the next release? With an external adapter Kali NetHunter is amazing but I guess Nexmon's library or firmware isn't really complete if I'm not I'm making some misstep very consistently.
[Nexus 6P Android Development] yesimxev:
Have you also tried the nougat fw? That driver version is different
[Nexus 6P Android Development] UsPdSr:
Yup, under 7.1.1-7.1.2 does Nexmon perfectly work..
[Nexus 6P Android Development] grajek05:
I have this problem

Do you know how to fix this I have a version of android 8.1.0 This problem Trying broadcast probe requests.
[Nexus 6P Android Development] grajek05:
which version is better. Android 8.1.0 or LineageOS 14.1 for Huawei Nexus 6p

Hi if it is worth changing the system for Huawei Nexus 6p, because I know that developers do not recommend Android 8.1.0 but I found that the author of Re4son nuclei published this NetHunter Documentation, USB problems with anything newer than 7.1.2 Latest supported LOS image available here. Whether or not to change the system
[Nexus 6P Android Development] yesimxev:
External USB adapters issue has been solved. Oreo is the stable recommended version, Lineage17.1 is also available. Internal wireless injection also works
[Nexus 6P Android Development] accedic:
NVM FIXED