[ROM][Official] Kali NetHunter for the Huawei Nexus 6P LOS17.1

[UsPdSr]

Hey there,

So for ten i installed ExtendedUI OFFICIAL and PixelDust with the twrp fbe 10, reboot to recovery, rooted with magisk, set all up, install busybox within magisk, reboot to recovery, then installed the nethunter zip, rebooted to recovery,
rooted with magisk, reboot to System.

All is fine, the kernel etc. but no nethunter apps are showing. So i extracted the apps from the zip file, installed all and updated the nethunter app throught fdroid because the nethunter store app isnt working with extensions but fdroid did and the source for the nethunter repo you can copy from the store app.

Then fire up the nethunter up, set up chroot and tata, all is working great.

and btw thanks for the flashable kernel ;o)

Have you tested if the external Wlan adapter are working?

So, you did not have to apply the fstab file in TWRP?

 

[yesimxev]

I can confirm PE10 TWRP with FBE works with both LOS17 & PE10

 

[yesimxev]

I used TWRP provided beside according rom, not the official version. View attachment 4996289

But If you will check the screenshot which I attached, I notice something weird, that in mount TWRP page I see vendor partition twice. Can It be a problem?

Is there any big difference between TWRP provided for LOS17.1 and PE10? Because the last thing I can think of is that I may swap it and use PE10 TWRP for install LOS17.1 rom.

Have you flashed stock vendor before installing any ROM?

 

[Nick_Speed]

Have you tested if the external Wlan adapter are working?

So, you did not have to apply the fstab file in TWRP?

Yes, all of my external Adapters work out of the box.

And no, i dont use the fstab file.

But i dont installed LOS. With pixeldust and ExtendedUI OFFICIAL all went fine.

There is an AOSP Build also, but this one i havent tested yet.

 

[UsPdSr]

Have you flashed stock vendor before installing any ROM?

Even if he has, it is not that big of a deal otherwise.

The duplicated vendor is somehow kind of confusing.

I saw this by another user, who flashed Nethunter on his Nexus device as well.But I think he didn't report back with a solution unfortunately. :/

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

Yes, all of my external Adapters work out of the box.

And no, i dont use the fstab file.

But i dont installed LOS. With pixeldust and ExtendedUI OFFICIAL all went fine.

There is an AOSP Build also, but this one i havent tested yet.

Thanks for the answer.

I downloaded both roms and the necessary recovery.

Perhaps I give it tonight another try, when I have time.

 

[UsPdSr]

Anyway.

ExtendedUi works like a charme.

I had problems after flashing the Nethunter installer and afterward the kernel.
I lost root, but this is most likely caused by the FBE, or perhaps the rom.

It's a threat to see those kernel working so flawlessly.

Again huge compliments to the entire Nethunter team!
@yesimxev @Re4son @kimocoder

 

[boutsism]

when i try to use vnc manager it tells me error launching intent. install android terminal! The problem is that i have terminal. any ideas?

 

[UsPdSr]

I wanted to add 'Pixel Dust' to the compatible roms, which can be used with this kernel.

Though the same issue with the installation of the apps remains.
As well, as the additional installation of Magisk.

I have never used Kex and was wondering, like my previous speaker, how the old, but reliable vnc function can be used.

I didn't found it in the Nethunter app and as I use my own Vnc app, but had problems get it to work. :/

I tried to compile the Pixel Dust kernel for Nethunter, but I have problems with Re4son's kernel builder.

I am used to the build scripts and don't know how I should implement the patches.

Mainly the one for the Realtek ac chipsets.

Sorry, for Ot.

 

[Nick_Speed]

For the kex, you have to start it one time in the Manager, it asks you about a Password and then you can start it. Uncheck the local Button and also set in your chroot per terminal in the vnc.conf localhost Access to false so you can Connect with ultravnc Client Port 5901. IT works great!

 

[Shabbirkt]

can anyone please explain the installation process a bit precise. i'm getting into bootloop after trying for first boot. just Google comes up and again bootloader., Nothing else.

 

[Nick_Speed]

Just Look a little above,i described the Installation for some ten Roms. Did you do this steps? The Rom without nethunter boots fine?

 

[Shabbirkt]

Yes brother, lineage 17.1 is booting up perfect. And as far as your post is concerned about installing on Extended UI and PixelDust, I get to boot after installing Nethunter but apps not appearing and i cannot find any apps.

 

[Nick_Speed]

So you have your Rom with the nethunter ZIP flashed and running? Thats good. Like i wrote then you have to extract the apks manualy from the zip File.

---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------

Bei Sure you have magisk Up and running

 

[Shabbirkt]

yes brother. but what about LOS ??? i'm facing issues with it.

 

[Nick_Speed]

What issues exactly?

 

[UsPdSr]

yes brother. but what about LOS ??? i'm facing issues with it.

Beside the annoying forced encryption and the regarding usage of a compatible FBE recovery build of Twrp, which need endlessly to boot up by the way, couldn't I detect any major or even minor problems with the new release.

I am not a particular fan of LineageOS, never was, but @Re4son hit it with this kernel definitely one wide over the fence. *gg*

For future reference -

Statments like "facing issues'" aren't particular information sources.

I do normally not respond to such posts at all, but _if_ there are actually problems, you should provide logcats, dmesg or adb outputs.

Otherwise nobody can help you.

Many heaps

edit.

I wanted to underline the above message.

I waited a long time and two Nexus 6P for these releases.
In the meantime did I try to help and supported several user all over the Nethunter related kernel releases on XDA over 3 years [no bragging, just fyi!].

It would be a shame to see this thread overrun with statments like above, or dumb talk in which degree whatever.

This phone is an old timer with huge hardware issues and the user who use it, didn't run into Blod/battery or complete meltdown failure yet, or are just Nexus addicts and massive fanbois ^^

With a reference to post from developer like @yesimxev, @Re4son and @kimocoder, who are undoubtedly pros in various areas (kernel development, wireless technology, network, pen-testing..), with limited resources like time, energy and the graciousness of giving a crap^^(scnr), does it go (hopefully) without saying that every user behaves, provides the very easy to obtain, above mentioned, log reports and don't start with such nonsense, if someone "could hack a(sic!) wifi", "my gf's facebook" or any other of these kind of dumb requests.

I hope we can try to treasure this amazing work for some time longer..

With best wishes

UsPdSr

 

[dubedollars]

Does monitor mode work? Couldn't get it running on the nh rom over los17.1 . When I type lsusb it shows my ralink wifi adapter but I get an error with ifconfig and it doesn't show up. Just did a fresh install of pe 10 (amazing rom from the 5 minutes I had setting it up) hoping I'll be able to get my adapter into monitor mode. Is there a repo for the ralink drivers or is the magisk module suffice?

 

[UsPdSr]

Does monitor mode work? Couldn't get it running on the nh rom over los17.1 . When I type lsusb it shows my ralink wifi adapter but I get an error with ifconfig and it doesn't show up. Just did a fresh install of pe 10 (amazing rom from the 5 minutes I had setting it up) hoping I'll be able to get my adapter into monitor mode. Is there a repo for the ralink drivers or is the magisk module suffice?

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 @kalinethunter, 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. ^

 

[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.

 

[UsPdSr]

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.

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.