Can't install Kali NetHunter... - OnePlus 3T Questions & Answers

Hello.
I have been trying for the past week to get Kali NetHunter on my OnePlus 3T (using this guide) and it has worked... Somewhat. The issue is when I try to install chroot. The NetHunter app doesn't want to connect to the server. Gives an error that I don't understandt. So I googled it and found out that I can download chroot and install it locally instead. I downloaded it and tried to install. When the install is done it does not give me any errors and just prompts me to install it again. I have tried this 5 times now. Still doesn't work.
ROMs I tried installing chroot on: OxygenOS 5.0.8, LineageOS 14.1 and TugaPower 25.0. All with root access. None worked.
Am I doing something wrong or is it something with my device?
Thanks in advance

Related

Flashing kali nethunter without custom recovery?

Is it possible to install kali nethunter on the AT&T Galaxy S5 without a custom recovery installed? I tried different apps like flashFire, flashGordon but neither worked. FlashFire at least installed the Kali nethunter apps but the kali terminal crashes upon boot. Not sure if anyone else has ran into this issue before.

There is no SU binary installed. Help

My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.
I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.
Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00
Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs

Magisk fails!

Device info: Xiaomi redmi note 4 Qualcomm, arm64,sdk25
1. I have successfully installed lineage OS 14.1 with pico gapps.... Everything looks good.. but the ROM has lots of bugs... Device get hanged, network issue etc...... So i decided to replace it with RR ROM... Now lots of problem occurs...
2. I have successfully installed RR-O-v6.0.0-20180514-mido-Official.zip with stock gapps arm64..... Now it's trun to install Magisk... But the latest redwoolf twrp shows... Failed to install Magisk and Error 1... So the device cannot get rooted
3. So I decided to install updated version of lineage OS with stock gapps.. now Magisk installed without any problems... But the Magisk fails to install BusyBox and xposed framework in it... Why???
First rule of fig... *ahem* posting about issues:
Provide logs.
Installation logs are always good. For example, the "error 1" message in TWRP means absolutely nothing if you don't also provide the recovery log from when it happens.
And saying that installing busybox and Xposed fails, without any further details also makes it quite hard to help. Are you installing them as Magisk modules? If so - provide installation logs. If not, please explain further what fails, and possibly provide a logcat as well.
Edit: and of course, the Magisk log and/or magisk_debug.log are often quite useful as well.

Problem with installing magisk

Really don't know where to post this, so I'm writing it here.
I have problems installing Magisk on Alcatel Pixie 3 4 (4013), phone runs on MediaTek MT6572M and currently operating on CyanogenMod 12.1
stock rom is based on 4.4.2 so I had to upgrade to lollipop based rom.
I'm trying to install magisk with twrp 3.0, but it gives me "unable to unpack boot image".
unninstalled supersu and run unsu script, because rom was pre-rooted.
I have tried Exodus rom, but magisk hide didnt work at all, magisk itself was. So I tried this one. Without success I guess.

[OpenGApps] Getting error 255 when installing OpenGApps 10 Aroma

I wanted to install Aroma because I want the choice of installing whichever app specifically and mainly so that I can replace stock AOSP apps with Google ones. I tried to do that on top of clean flash RR 8.6.2 which does not comes with any pre-built GApps.
But upon installation on OrangeFox it freezes for 2-3 seconds and gives error 255. This is ARM64 Android 10 Aroma so guess I chose the right version but still the error. I can install others like pico, nano, mini and stock just fine but not aroma.
I even tried previous months versions but no luck. Tried installing ROM, set it up and Aroma separately with going to recovery again but still the same error. I am able to flash ANX camera, custom kernel & Fdecrypt just fine but not this one...
If anybody could help what is the issue.
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Skorpyun812 said:
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Click to expand...
Click to collapse
UPDATE: For some reason Aroma wasn't giving me error logs but, after trying "full", I noticed the error message was that my device is ARM64. Then, after trying 9.0 and 10 ARM64, (both full versions, not aroma) I found in the logs that there was insufficient space to install. The log for some reason, claims the full version needs 1.7 TB?! So I grabbed a copy of OpenGApps 10 ARM64 pico and that worked. I got basic play store function, that's all I really needed. . . Do not ask why I didn't think of that sooner. Hope this helps poster or anyone else. \m/

Categories

Resources