Hmm, strange. What phone?
Type: Posts; User: re4son
Hmm, strange. What phone?
Did you get any error message?
I can have a look at it if you want. Just post the link to the kernel source and to the local.config you are using.
What device are you building for?
It's fixed now
Oops, the URL shortener is down. Sorry for that and thanks for letting us know. I'll look into it.
You can use the long link for now:
...
Maybe the wrong image? Have you tried the download for marshmallow?
https://images.offensive-security.com/nethunter/nethunter-2020.2-oneplus1-marshmallow-kalifs-full.zip
init.nethunter.rc
I had to install a patched boot image to disable DM-Verity and the force-ecryption disabler (together with formatting data) to get rid of the forced encryption.
Here my installation notes:
...
Wow. You're a legend! Thanks heaps :)
You can try removing the init.rc file from your ramdisk and using USB Armory again.
USB Armory has two modes: Trigger pre-defined configfs functions or create them on the fly. Removing the init.rc...
I would hold off on getting the OP7T for now. There is no fully working twrp yet available for it and that'll make it extremely finicky to install NetHunter.
The OP6 is an unofficial build and has yet to be tested. RTL8188EUS support has been reported by the developer but has not been verified.
The OP7 build is the top of the shelf NetHunter device and...
Wow, awesome stuff :)
Let me look into that RNDIS issue.
That kernel looks like a mess to me. Half of it consist of CAF commits that don't talk to the other half.
Not sure we'll ever get mac80211 to work with that. Looking around for a cleaner base now.
Awesome, thanks. Will look into it. Somehow I think I've already written a patch for it but I can't find it.
Sorry for not being clear. I meant could you please add your own "local.config" to the repository for me to use. It won't help you but it'll help me to continue where you left off
Mind adding "kali-nethunter-kernel/local.config" to your repo? Saves me looking for the toolchains you used.
That's what I usually do:...
Look under "4.04"
Had to name it that way to get them listed in ascending order.
Undeclared identifier? Did you get that after enabling ath9k_htc in the kernel config?
Awesome, great to hear :)
Thanks for letting me know.
What you could try is to install the Hasty kernel on its own:
https://forum.xda-developers.com/mi-9t/development/kernel-hasty-t4084863
See if that works.
The NetHunter Kernel is based on this...
And did you upgrade the nethunter-app from the store after flashing? That's required to work around the new scoped storage restrictions in Android 10. It shouldn't cause a reboot but prevents the app...
Did you format your data partition when you flashed "Disable_Dm-Verity_ForceEncrypt"?
That error is caused by an encrypted data partition. Magisk cannot handle user context changes on encrypted data partitions.
Please flash an encryption disabler for your phone and format data....
So you had everything working, encryption gone, rooted, etc. and then you installed nethunter and it broke?
They look ok to me.
What happens when you do it step by step? At what stage does it break?
Oh, and I've got this in my notes after flashing twrp, installing Magisk and when rebooting:
Don't install TWRP app, reboot without ticking "install"
I had to copy the fstab files across to my laptop via a USB stick, edit them to disable DM-Verity& force encryption, and copy them back.
Not sure, sorry. We don't have these issues in Oz.
How about this thread, through:
https://forum.xda-developers.com/oneplus-7-pro/help/oneplus-7-pro-oem-unlock-greyed-t3941623
Does this help?
Did you root it and removed encryption successfully?
Sorry, my bad. That's required for the OP7 not davinci. Should have read:
VBMETA PATCHER
That's the standard Xiaomi message that pops up after a reboot with a custom kernel. Just ignore...
couple of minutes. If that happens try flashing Magisk again and the Disable_Dm-Verity_ForceEncrypt zip
You can flash 2020.2 over the existing one.
@blueghosties
1. Download the NetHunter image for Davinci, twrp, magisk and Disable_Dm-Verity_ForceEncrypt.
2. Copy twrp, magisk, Disable_Dm-Verity_ForceEncrypt & NetHunter image to USB-C drive...
@maninmiddle what does not work? Does the home screen list the HID interfaces under "HID Status" after you enabled HID in the USB Armory?
If your device is on this list, then there is a kernel with full NetHunter support available in our repo
If your device is not on this list than you are the lucky one that can create it.
Just clone...
Should be working out of the box. What bluetooth adapter are you using?
I've just tried a BCM2070 and that's working fine with the OnePlus 7.
You need to create a kernel that enables support for HID attacks.
Let me know if you are interested and we can continue where people before you gave up:
...
No changes to mac80211 as you can see with the following command:
git diff a07c5305b815d9564bb37b870bcb5593d9c9d6e1
diff --git a/arch/arm64/configs/nethunter_defconfig...
Fixed in latest commit.
I think you just have to try harder
Yes. If you want to fix the error then I suppose it is.
I see. What is the purpose of "/usr/lib/aarch64-linux-gnu"? And what is the purpose of "/system/lib64"?
why did you copy files from "/usr/lib/aarch64-linux-gnu" to "/system/lib64"?
What have you done so far to troubleshoot this message?
Did you unencrypt your data partition? Magisk cannot handle user context changes on encrypted data partitions. Hence the error message.
Great idea. Mind raising a feature request in gitlab to keep it on our radar?
Many thanks.
I don't have to build a new library. You will understand that when you continue with your troubleshooting.
Great opportunity to learn about C and to "Try Harder" :)
By troubleshooting i meant what have you done to find the cause of the error?
Not sure. What have you done so far to troubleshoot it?