I might have missed something, I built a kalifs less than a month ago and flashed that, but I don't remember this issue. The thing is, after resolving the conflict with one of the above methods, reinstall of gcc-9-dev succeeds
Last edited:
[ROM][Official] Kali NetHunter for the Huawei Nexus 6P LOS17.1
- Thread starter yesimxev
- Start date
Please help
I have an factory unlocked International nexus 6p model # H1512 it’s running nougut I literally just took it out the box today what do I need to do to get this thing up and running on this?
I have an factory unlocked International nexus 6p model # H1512 it’s running nougut I literally just took it out the box today what do I need to do to get this thing up and running on this?
The best you can do, is to follow the instructions.
Unlock the bootloader (see the link below), then all the steps are provided in the post (above)
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/amp/
[
As the destination is /
Having some difficulties so forgot to edit the main post. Use command
Code:
adb push fstab.angler /sdcard/
adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/fstab.angler /system_root/"
Last edited:
I wanted to give you guys a heads up, that the issue is still on-going.
as well as
isn't doable either.
+
,
+
..again from the beginning until you have updated, upgraded and cleaned up the whole chroot installation.
I had my fair share of many attempts to help in Nethunter github/gitlab repository out and after countless attempts to register in kali's 80's chaos computer club like forum was nearly impossible, do I think that giving notice here fulfills my "due diligence"*.
Many heaps
PS
*Of course will I try to help on Xda out in the according Kali related threads and offer support.
Gladly via PM (as long as the person is polite and don't thinking of making the (very hilarious) mistake asking, if I could "h4xx0r somebody's gf's MySpace site", or such amusing question if I could help out in giving advice regarding carding" won't this change in the near future neither.
Last edited:
For people who whant use it, its like, we flashed android 10 on Toaster, Toaster starts...
but does not heat up, for heating wee need a patch, maybe in the future, but we are not sure.
And now seriously, internal monitor not supported, Usb arsenal not working,installation extreamly bugged,and no patches,
this release destroy the whole point of using Nexus 6p, instead we can use it oneplus it support everyng except of packet injection.
it's not even alpha, it's something earlier than alpha.
Any way thanks to developers, but you should write at the beginning of the topic in red text that a lot of things don't work.
I spent a lot of time installing, and I didn't get what I want, and disappointed.
For users, don't waste your time installing it won't work fine.
but does not heat up, for heating wee need a patch, maybe in the future, but we are not sure.
And now seriously, internal monitor not supported, Usb arsenal not working,installation extreamly bugged,and no patches,
this release destroy the whole point of using Nexus 6p, instead we can use it oneplus it support everyng except of packet injection.
it's not even alpha, it's something earlier than alpha.
Any way thanks to developers, but you should write at the beginning of the topic in red text that a lot of things don't work.
I spent a lot of time installing, and I didn't get what I want, and disappointed.
For users, don't waste your time installing it won't work fine.
Last edited:
I'm sorry to disappoint you. You are right that monitor mode is not mentioned in the first post. Altough it's been patched in the last few days by @draco42. I'll upload that so you can have fun with it. Please note some stuff which is using different ioctl calls might still not work, but I can easily inject and capture a handshake! Other than that, your USB arsenal issue is an RTFM as kernels under 4.x does need patch which enables hidg0 hidg1 and uses DriveDroid for mass storage (all working on 6P). I'll update the whole thing in the following days to clarify the flashing process and monitor mode
Last edited:
HI @yesimxev, i just installed you new update
https://dl.xda-cdn.com/5/1/0/9/4/0/5/Screenshot_2.jpg?key=f4oA4wfpHvjgnYfaF6uutg&ts=1601781137
but noticed some errors, if i run nexutil -m2 i get:
https://dl.xda-cdn.com/5/1/0/9/4/1/5/Screenshot_3.png?key=72wAiviEmqAAv5P7nzVJtg&ts=1601783036
also i looked in /system/lib64/ no kalilibnexmon.so visible.
i have only used external adapter on my oneplus, and have not much experience with nexmon, and i have question, should i manually install nexmon?
also my kali chroot not updated, and used how you provided.
i have looked in to vendor.squashfs, only fw_bcmdhd.bin changed, also no kalilibnexmon.so
Maybe i can use this one? https://gitlab.com/kalilinux/nethun...ices/-/tree/patch-yesimxev/oreo/angler/system
or need a new patched?
also i have noticed possible typo: fastboot flash vendor.squashfs should be: fastboot flash vendor vendor.squashfs right?
Thanks.
https://dl.xda-cdn.com/5/1/0/9/4/0/5/Screenshot_2.jpg?key=f4oA4wfpHvjgnYfaF6uutg&ts=1601781137
but noticed some errors, if i run nexutil -m2 i get:
https://dl.xda-cdn.com/5/1/0/9/4/1/5/Screenshot_3.png?key=72wAiviEmqAAv5P7nzVJtg&ts=1601783036
also i looked in /system/lib64/ no kalilibnexmon.so visible.
i have only used external adapter on my oneplus, and have not much experience with nexmon, and i have question, should i manually install nexmon?
also my kali chroot not updated, and used how you provided.
i have looked in to vendor.squashfs, only fw_bcmdhd.bin changed, also no kalilibnexmon.so
Maybe i can use this one? https://gitlab.com/kalilinux/nethun...ices/-/tree/patch-yesimxev/oreo/angler/system
or need a new patched?
also i have noticed possible typo: fastboot flash vendor.squashfs should be: fastboot flash vendor vendor.squashfs right?
Thanks.
Last edited:
You're right about vendor missing from command. Can't see first pic so please paste text error here.
Oh forgot to mention that libnexmon has to be copied manually to /system/lib64. Use the ones in the zip, I haven't pushed them yet
Oops sorry, on first pic that busybox are from nethunter, and on second nexutil command not found.
Are you running nexutil in androidsu window? If yes, you need to manually copy nexmon too to /system/xbin/
Used to be copied there on Android 8.1 by NH installer.
I'll add the instructions tonight to make the tutorial complete.
I created a custom command for nexutil as it's only needed once, but export in Kali terminal needs to be ran in every newly opened window
Last edited:
i have a noob question, if i do adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/nexmon/kalilibfakeioctl.so /system_root/system/xbin/" i get output that not enough space on device, if i try sudo cp -v i get its read only partition, what do you think is the best copy method?Are you running nexutil in androidsu window? If yes, you need to manually copy nexmon too to /system/xbin/
Used to be copied there on Android 8.1 by NH installer.
I'll add the instructions tonight to make the tutorial complete.
I created a custom command for nexutil as it's only needed once, but export in Kali terminal needs to be ran in every newly opened window
and I have a big request, I completely understand that we have 3.10 kernel, and if the kernel structure hasn't changed much to appy HID patch if its possible,
i love the Usb Arsenal, Some time i even reinstall windows-linux whith it, or use some scripts very comfortably. i know DriveDroid but if we have already built in nethunter app its nice.
Thanks.
Last edited:
lib files has to be copied to (system_root in twrp)/system/lib64 and only nexutil to system/xbin if it's not there by the installeri have a noob question, if i do adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/nexmon/kalilibfakeioctl.so /system_root/system/xbin/" i get output that not enough space on device, if i try sudo cp -v i get its read only partition, what do you think is the best copy method?
and I have a big request, I completely understand that we have 3.10 kernel, and if the kernel structure hasn't changed much to appy HID patch if its possible,
i love the Usb Arsenal, Some time i even reinstall windows-linux whith it, or use some scripts very comfortably. i know DriveDroid but if we have already built in nethunter app its nice.
Thanks.
Forget USB arsenal for 6P. That's been created because Hid patches are not necessary on kernels 4.x< but something is still needed to enable Hid along with mass_stotage. You can do it with drivedroid (only mounting an image is the question). Hid is enabled by default and rndis too if I'm not mistaken
Last edited:
After several attempts and most importantly user reports, I got it working.
I don't know if it's just a slip of the pen on your side, or if you as developer just don't see it in different ways, because the installation tutorial are a mess, @Re4son @yesimxev..
I wanted to share a quick summary of steps you forgot to write down or are wrong, files that missing and what worked in the end..
As custom rom did I try as per recommendation Lineage OS, which didn't worked as well as Pixel Experience.
The solution here is to edit the files which are to be downloaded.Only after looking into Nethunter's issue(ticket) section, after finding a bug report about our device, did I finally got my hands on the Lineage OS build version, which yesimxev posted in said bug report.
I don't know if it is a common step, foremost the modified vendor file, but the archives, have to be unzipped while going to the instructions.
The Twrp Recovery, which is been linked in the OP is wrong and has to be replaced with the FBE, or BLOD one.
https://drive.google.com/file/d/1axm3GVbTKypUdQAuYubNknJX4wKRFIec/view
I don't know if I came across a more complex "tutorial", but let alone the section for the more important information, in this regard Nexmon, is utterly unclear and incredible annoying after the fourth attempt.
All four apk's had to be re-installed.
I saw the sub-clause in brackets about the adb shell commands in AndroidSU much later than I wished.
Nexutil had to be copied over as well, which I only figured out from reading gitlab's issue section.
I wanted to hold this brief, but before I forget to mention this - the iptables couldn't be downloaded for armhf - only arm64.
In the end I got Nexmon to work.
Unfortunately on Lineage OS, which I personally very dislike and then Android 10, which for this device at this state poisonous is.I hoped after the picture of a running Nexmon for Oreo in the other thread, that this would be a realistic accomplishment.Not for nothing has the Oreo kernel been released for a third or fourth(?) time in April now.
I thank the devs for their contribution, but in regard of the support or let me be clear, a understandable and doable tutorial is this a very, very hard deficit in my opinion.
I hope to see better support and of course much more in the near future.
Best regards,
UsPdSr
Last edited:
Sorry I dropped support for PE, it's just not managable in one thread especially with nexmon stuff. Although it's simple have nexmon fw on vendor partition even if it's squashfs. I don't have a 6P in hand for a while. So thank you for noticing the mistakes - patched the TWRP link, nexutil (although might still need chmod a+x), apps instructions
Sorry maybe I am asking a stupid question...but I don't really understand the following step:
May I know where can I find/get the "nexmon.zip"? I just can't find it anywhere on this thread.
Thank you! However I got another problem, when I execute nexutil -m2 it failed. May I know what was going on? (I turned on wifi and not connected to any AP)
Here is the record:
Code:
:/ # mount -o rw,remount /
:/ # cp /sdcard/libnexmonkali.so /system/lib64/kalilibnexmon.so
:/ # cp /sdcard/libnexmon.so /system/lib64/
:/ # cp /sdcard/nexutil /system/xbin/
:/ # nexutil -m2
/system/bin/sh: nexutil: can't execute: Permission denied
126|:/ #
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone