offensive-security / nethunter-lrt

The Nethunter Linux Root Toolkit is a collection of bash scripts which install Nethunter onto a supported device.

New repo can be found here: https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-lrt

nethunter-lrt's Issues

openSUSE incompatibility

After installing android-tools, which put adb and fastboot into my path, and running which unzip and which tar to see that they are correct: I'm finding that the stockNexusFlash.sh script still won't do its magic.

Experimenting with individual steps of the script reveal two things:

1. tar is not behaving as expected with the stock image file. It refuses to unzip it saying it's an invalid tar file. It unzips fine if I do it manually with the unzip command.
2. after unzipping manually, the flash-all.sh script is failing. Running its steps manually I can get to the part where it does fastboot -w update image-bullhead-nrd90s.zip, but it seems to have similar troubles unzipping that file. I cannot get around this manually, as I can't see a way to make fastboot -w update work from the unzipped system.img file.

Nexus 6p OEM Flash error

https://github.com/offensive-security/nethunter-LRT/blob/master/stockNexusFlash.sh#L37 attempts to untar the image, however angler (Nexus 6p) is a zip file: https://dl.google.com/dl/android/aosp/angler-ota-mtc20f-5a1e93e9.zip
May need to do an if in there to check that.

Checking for Kali Chroot in installer.. this can take a while

My device is blocking on "Checking for Kali Chroot in installer.. this can take a while 90.0% -
Extract: /data/local/kalifs-full.tar.xz"

Tried 2 times the aroma installer on my nexus 5. After 20+ minutes on this screen, the phone reboot (normally ?) without saying anything. The device and nethunter seems to work.

When I start my device an icon is missing on the dock. I've Phone, ("?"), Chrome, Camera.

Does this mean a successful installation ? Is there something missing ?

EDIT : When my device start the first time, a notification shows "boot ended, all fine, Action performed. Nethunter chroot is not installed. OK"

Console output :
Installing Kali Linux Nethunter
Installing '/sdcard/kaliNethunter.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Starting AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com
Installing Kali Linux Nethunter DONE!
Rebooting into Kali Linux Nethunter
error: no devices found
Everything is installed. Phone should be booting up! Enjoy

Battery stuck on "100% - Charging on AC"

On the OnePlus One (Bacon) 64Gb with:

	File	MD5
Cyanogen OS 13.0.1	cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip	373e43912bf45a2dccdb37db78377b12
TWRP 3.0.2.0	twrp-3.0.2.0-bacon.img	57da36526b6666640317cd5f404717d1
SuperSU 2.67 (Chainfire Beta)	BETA-SuperSU-v2.67-20160121175247.zip	4a620ac84476e8ffe9762ecb18c4e2d5
Nethunter	Built from commit 3734504f4f527e72c7ca8cfa890f205e4a141066 for marshmallow with rootfs full (see below)	41f83d86ae18e812645cb2a79f9a55c9

The battery indicator stays stuck at 100%. The battery applet indicates "100% - Charging on AC" regardless of whether the phone is plugged-in or not and regardless of the actual charge level.
TWRP still tracks charge accurately.

With CM13.0.1 + TWRP + SuperSU (but before installing nethunter), the battery indicator behaves correctly.

To reproduce, download this Dockerfile into an empty directory and run:
docker build -t nethunter-battery-issue .

To run the build image in a container:
docker run -t -i -v $(pwd)/output:/output nethunter-battery-issue /bin/bash

From inside the container, just move whatever file you need to /output and it will be available in the host ./output directory.

OnePlusOne: from cyngn.com Not found 404

where i should find ? i just screw up on my phone.... help me...

Not installing Nethunter

I have followed all of the steps in the documentation but when I run the final command to install Nethunter it however doesn't do as it should do. It outputs this:

NETHUNTER LINUX FLASH (TWRP, SuperSU and Kali Nethunter)

CHECKING PRE-REQUISITES

Checking if adb is installed
adb FOUND
Checking if adb is installed DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed DONE

Adb connection check
ADB device detected.
Adb connection check DONE

Checking TWRP image existence
Dir twrpImage/ has files
Checking TWRP image existence DONE

Checking SuperSu existence
Dir superSu/ has files
Checking SuperSu existence DONE

Checking Kali Nethunter zip existence
Dir kaliNethunter/ has files
Checking Kali Nethunter zip existence DONE

CHECKING PRE-REQUISITES DONE

Sending Kali Nethunter zip to the device
Transferring: 681583778/681583778 (100%)
3385 KB/s (681583778 bytes in 196.577s)
Sending Kali Nethunter zip to the device DONE

Sending SuperSu zip to the device
Transferring: 4217869/4217869 (100%)
3114 KB/s (4217869 bytes in 1.322s)
Sending SuperSu zip to the device DONE

Rebooting into bootloader
Rebooting into bootloader DONE

Flashing TWRP image
target reported max download size of 1073741824 bytes
sending 'recovery' (10180 KB)...
OKAY [ 0.478s]
writing 'recovery'...
OKAY [ 0.174s]
finished. total time: 0.652s
Flashing TWRP image DONE

Booting into TWRP (20 secs dont worry)
downloading 'boot.img'...
OKAY [ 0.415s]
booting...
OKAY [ 0.020s]
finished. total time: 0.435s
Booting into TWRP DONE

Installing SuperSU
error: device not found
Installing SuperSU DONE!

Installing Kali Linux Nethunter
error: device not found
Installing Kali Linux Nethunter DONE!
Rebooting into Kali Linux Nethunter
error: device not found
Everything is installed. Phone should be booting up! Enjoy

However, everything isn't installed as Nethunter isn't on my phone. I was thinking maybe this is because it says "error: device not found" when it is run.
Help would be greatly appreciated.

Inconsistent and confusing install guide ?

So I followed the install guide step by step and that brought me to this
site (offensive-security/nethunter-LRT) and I continued to follow all the steps.

Everything looked totally fine, the terminal output ends with:

"Rebooting into Kali Linux Nethunter

Everything is installed. Phone should be booting up! Enjoy Nethunter
"

Great, I thought, but the phone rebooted and nothing happened. I ended up with a black screen and a white "Google" writing and sadly that's already the end of the story, no Nethunter in sight!?

Any clue what went wrong and what the state of the phone is?

And then I also remembered that on the previous site that brought me here
(offensive-security/kali-nethunter) there in the second step
(2.0 Downloading NetHunter) it says:

"For a fresh install, you will need a nethunter-generic-[arch]-kalifs-.zip as well as a kernel-nethunter-[device]-[os]-.zip. The kernel should be flashed last. The update-nethunter-generic-[arch]-*.zip files are for updating your installation or if you wish to download the Kali rootfs inside the NetHunter app instead."

Ok, I downloaded all of it in that step, but now I realize that I never used them in the following steps, simply because they were not mentioned anymore....!?

Why have I downloaded the "kalifs".zip at all? When there's no step explanation what to do with it. So have I terribly missed something? Or can we call this install guide inconsistent and confusing?

And once again, why do I have the output saying everything is fine but nothing happens?

Can we re-lock the bootloader after flashing Nethunter

Hi,

I am a new user of Nethunter, and I would like to know it it makes sense to re-lock the bootloader after flashing Nethunter.
Actually, when i lock the bootloader i can't boot anymore because of the android security.
this message is prompted : "Your device is corrupt. It can't be trusted and may not work properly"
And if it is possible how can we do that ?
If not what is the risk of letting the bootloader unlocked ?

Thanks

Help!!!, Please!!!

I think I am going to be sick...

I just got a Nexus 7, literally today. I opened the package, set it in Developer Mode, enabled USB Debugging, checked the Android version and ran through the install steps. But, when I ran the script to flash the image to stock it went to the bootloader, refused to boot, then shut down and will not turn on again.

I am afraid I just bricked my brand new tablet : ( Is there anything I can do at this point?

Nexus 7 stuck on fastboot

Looks like the scripts succeed, but Kali doesn't get installed and Nexus 7 gets stuck on fastbook screen.

Output:

NETHUNTER LINUX FLASH (TWRP, SuperSU and Kali Nethunter)

CHECKING PRE-REQUISITES
Checking if adb is installed
adb FOUND
Checking if adb is installed ...DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed ...DONE

Adb connection check
ADB device detected.
Adb connection check ...DONE

Checking TWRP image existence
Dir twrpImage/ has files
Checking TWRP image existence ...DONE

Checking SuperSu existence
Dir superSu/ has files
Checking SuperSu existence ...DONE

Checking Kali Nethunter zip existence
Dir kaliNethunter/ has files
Checking Kali Nethunter zip existence ...DONE

CHECKING PRE-REQUISITES ...DONE

Sending Kali Nethunter zip to the device
Sending Kali Nethunter zip to the device ...DONE

Sending SuperSu zip to the device
Sending SuperSu zip to the device ...DONE

Rebooting into bootloader
Rebooting into bootloader ...DONE

Flashing TWRP image
sending 'recovery' (2703 KB)...
OKAY [ 0.090s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
finished. total time: 0.094s
Flashing TWRP image ...DONE

Booting into TWRP (20 secs dont worry)
creating boot image...
creating boot image - 2770944 bytes
downloading 'boot.img'...
OKAY [ 0.090s]
booting...
OKAY [ 0.364s]
finished. total time: 0.455s
Booting into TWRP ...DONE

Press any key when you're ready...
Installing SuperSU
error: device not found
Installing SuperSU ...DONE

Installing Kali Linux Nethunter
error: device not found
Installing Kali Linux Nethunter ...DONE

Rebooting into Kali Linux Nethunter
error: device not found

Everything is installed. Phone should be booting up! Enjoy Nethunter

flash-all.sh missing?

./stockNexusFlash.sh
NETHUNTER LINUX FLASH (STOCK NEXUS GOOGLE IMAGES)

NOTE: THIS WILL FACTORY RESET THE DEVICE (15 secs to cancel using 'ctrl + c')

CHECKING PRE-REQUISITES

Checking if adb is installed
adb FOUND
Checking if adb is installed ...DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed ...DONE

Adb connection check
ADB device detected.
Adb connection check ...DONE

Checking if unzip is installed
unzip FOUND
Checking if unzip is installed ...DONE

Checking stock image existence
Dir stockImage/ has files
Checking stock image existence ...DONE

CHECKING PRE-REQUISITES ...DONE

Creating tmp dir _extracted
Creating tmp dir _extracted ...DONE

Extracting stockImage/ElementalX-N7-5.16.zip
Archive: stockImage/ElementalX-N7-5.16.zip
creating: _extracted/META-INF/
inflating: _extracted/META-INF/CERT.RSA
inflating: _extracted/META-INF/CERT.SF
inflating: _extracted/META-INF/MANIFEST.MF
creating: _extracted/META-INF/com/
creating: _extracted/META-INF/com/google/
creating: _extracted/META-INF/com/google/android/
creating: _extracted/META-INF/com/google/android/aroma/
inflating: _extracted/META-INF/com/google/android/aroma-config
inflating: _extracted/META-INF/com/google/android/aroma/agreement.txt
inflating: _extracted/META-INF/com/google/android/aroma/changelog.txt
inflating: _extracted/META-INF/com/google/android/aroma/elementalx.png
creating: _extracted/META-INF/com/google/android/aroma/fonts/
inflating: _extracted/META-INF/com/google/android/aroma/fonts/big.png
extracting: _extracted/META-INF/com/google/android/aroma/fonts/small.png
creating: _extracted/META-INF/com/google/android/aroma/icons/
extracting: _extracted/META-INF/com/google/android/aroma/icons/agreement.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/alert.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/apex.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/apps.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/back.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_aosp_blue.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_aosp_green.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_blue.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_blue_no.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_gauge.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_gauge_wide.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/battery_green.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/battery_vertical.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/battery_white.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/battery_white_stock.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/confirm.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/customize.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/default.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/device.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/fbhome.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/finish.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/htc.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/info.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/install.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/installbutton.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/keyb.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/license.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/menu.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/next.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/nova.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/personalize.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/security.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/signal_att.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/signal_highdef.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/signal_stock.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/signal_white.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/update.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/weather_sense4.png
extracting: _extracted/META-INF/com/google/android/aroma/icons/weather_stock.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/weather_thick.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/weather_weezle.png
inflating: _extracted/META-INF/com/google/android/aroma/icons/welcome.png
creating: _extracted/META-INF/com/google/android/aroma/ttf/
inflating: _extracted/META-INF/com/google/android/aroma/ttf/Roboto-Regular.ttf
inflating: _extracted/META-INF/com/google/android/update-binary
inflating: _extracted/META-INF/com/google/android/update-binary-installer
inflating: _extracted/META-INF/com/google/android/updater-script
creating: _extracted/boot/
inflating: _extracted/boot/abootimg
inflating: _extracted/boot/cmdline.cfg
inflating: _extracted/boot/edit_ramdisk.sh
inflating: _extracted/boot/elementalx.sh
inflating: _extracted/boot/elex.zImage
inflating: _extracted/boot/init.elementalx.rc
inflating: _extracted/boot/max_oc.sh
creating: _extracted/config/
inflating: _extracted/config/buildconfig.sh
inflating: _extracted/config/busybox
inflating: _extracted/config/elementalx.conf
inflating: _extracted/config/systemcheck.sh
creating: _extracted/system/
creating: _extracted/system/lib/
creating: _extracted/system/lib/hw/
inflating: _extracted/system/lib/hw/power.msm8960.so
Extracting stockImage/ElementalX-N7-5.16.zip ...DONE

cd to _extracted
cd to _extracted ...DONE

Rebooting into bootloader
Rebooting into bootloader ...DONE

Flashing stock ROM
!!!! DONT UNPLUG THE DEVICE !!!!
./stockNexusFlash.sh: line 50: ./flash-all.sh: No such file or directory
Flashing Stock ROM ...DONE

Deleting tmp dir _extracted
Deleting tmp dir _extracted ...DONE

The device should be rebooting, once it is booted,
do the initial setup, enable developer options and USB debugging again.

Next step is flashing TWRP && superSU && Kali Nethunter using twrpFlash.sh script

upon reboot, no image...

Broke Link in README

The cyngn.com website is down. It should be removed from the README.

stockOpo Fails

At line
fastboot reboot-bootloader
script fails with message

which results in bricked device
tried to rund fastboot with sudo, didi not help

Getting my facts straight about installing Nethunter

So at https://github.com/offensive-security/kali-nethunter/wiki it says "about downloading Nethunter" that you will need nethunter-generic-[arch]-kalifs-.zip as well as a kernel-nethunter-[device]-[os]-.zip. which can both be found in https://build.nethunter.com/nightly/2017.11-18-1618/ but at https://github.com/offensive-security/nethunter-LRT the instructions say to "Put the NetHunter zip image you downloaded or built in the /kaliNethunter folder.". I am assuming the full kalifs generic zip or if a built scipt is used the "--rootfs full" option must be used. So using nethunter-LRT do you put the genric (or built full option) in the kali folder, then later go in with TWRP and flash the kernal for the device secondly? Even so, in a tweet with binkybear he mentioned the when you build... "you add the full fs option but you actually have to include the file. https://build.nethunter.com/kalifs/kalifs-latest/ ". Does that mean the put the latest kalifs in the LRT kali folder then later flash the full option built zip file? My issue is that the LRT steps refer to one zip file, but other people and the nethunter wiki refer to two zip files. The wiki says to flash the full generic rolling zip first and then the kernal zip last but there is no mention about selecting both files in TWRP at the same time or letting TWRP flash the full zip first, then after full reboot go back into recovery reboot with TWRP and flash kernal zip.

In offensive-security/kali-nethunter#836 simonpunk said that the build.py --rootfs full option can only build the flashable zip but not the kernel itself. Does this mean you still must download a correct kernal from the https://build.nethunter.com/nightly/2017.11-18-1618/ area and flash that even after your full fs option build.py zip file? If so, binkybear is saying a built zip with --rootfs full needs to be accompanied by the https://build.nethunter.com/kalifs/kalifs-latest/ kalifs.... then simonpunk is saying you need the kernal from https://build.nethunter.com/nightly/2017.11-18-1618/ as well? Maybe I'm just really confused but some clarification would be nice.

Also, I and a Nexus 9 (flounder) Nougat 7.1.1, kernal 3.10.103-gcbed67d00ed-dirty, build # N9F27M and a Nexus 6 (shamu) Nougat 7.0m kernal 3.10.40-g9f039ba, build # NBD91P.
With the Nexus 9, the nethunter-LRT would stick in fastboot commands (adb would work, but fastboot oem unlock would be waiting on device and device would stay at the white recovery reboot screen with the LOCKED indicated at the top and never go to the black screen comfirming unlock). I had to use wugfresh's Windows Nexus Tool to get me to the point where SuperSU and TWRP were installed and then I flashed a 9.6 MB kernel-nethunter-flounder-nougat-2017.11-18-1618.zip first by mistake and later flashed a "build.py -d founder --nougat --rootfs full" zip file. I sort of seems to work, I have nh-terminal, and nh-app. Has issues where I can't get metapackages, monstart-nh (no bash script found), and I have to run custom commands 4 or 5 times to work (most of the time nh-term just comes up and nothin happens). The Nexus 6, I haven't done anything with yet.

Is there a way to 100% start over with the Nexus 9 if I messed up (apparently I did) with my above process?

I get error "Unfortunately, Nethunter has stopped" after installation completes.

(I also posted this issue here: https://forums.kali.org/showthread.php?31055-After-fresh-install-I-get-error-quot-Unfortunately-Nethunter-has-stopped-quot )

Every time the install completes, I only get the error "Unfortunately, Nethunter has stopped"

I've gone through the steps multiple times. Nethunter 2 was working on this Nexus 10 previously.

I've tried the first release of Android 5.1.1 (LMY47V) and the latest release (LMY49J) with the same results.

Script output:

~/nethunter-LRT on master
$ ./stockNexusFlash.sh
NETHUNTER LINUX FLASH (STOCK NEXUS GOOGLE IMAGES)

NOTE: THIS WILL FACTORY RESET THE DEVICE (15 secs to cancel using 'ctrl + c')

CHECKING PRE-REQUISITES

Checking if adb is installed
adb FOUND
Checking if adb is installed DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed DONE

Adb connection check
ADB device detected.
Adb connection check DONE

Checking if tar is installed
tar FOUND
Checking if tar is installed DONE

Checking stock image existence
Dir stockImage/ has files
Checking stock rom existence DONE

CHECKING PRE-REQUISITES DONE

Creating tmp dir _extracted
Creating tmp dir _extracted DONE

Extracting stockImage/mantaray-lmy47v-factory-91a865a6.tgz
x mantaray-lmy47v/
x mantaray-lmy47v/bootloader-manta-mantamf01.img
x mantaray-lmy47v/image-mantaray-lmy47v.zip
x mantaray-lmy47v/flash-all.bat
x mantaray-lmy47v/flash-all.sh
x mantaray-lmy47v/flash-base.sh
EXTACTING stockImage/mantaray-lmy47v-factory-91a865a6.tgz DONE

cd to _extracted
cd to _extracted DONE

Rebooting into bootloader
Rebooting into bootloader DONE

Flasing Stock Rom
!!!! DONT UNPLUG THE DEVICE !!!!
< waiting for any device >
erasing 'boot'...
OKAY [ 0.024s]
finished. total time: 0.025s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.103s]
finished. total time: 0.103s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.449s]
finished. total time: 0.449s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.428s]
finished. total time: 0.428s
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.108s]
finished. total time: 0.278s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for any device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32--------
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
sending 'boot' (4930 KB)...
OKAY [ 0.643s]
writing 'boot'...
OKAY [ 0.126s]
sending 'recovery' (5496 KB)...
OKAY [ 0.727s]
writing 'recovery'...
OKAY [ 0.126s]
erasing 'system'...
OKAY [ 0.153s]
sending 'system' (656838 KB)...
OKAY [ 85.937s]
writing 'system'...
OKAY [ 16.275s]
erasing 'userdata'...
OKAY [ 0.367s]
sending 'userdata' (139141 KB)...
OKAY [ 18.192s]
writing 'userdata'...
OKAY [ 3.541s]
erasing 'cache'...
OKAY [ 0.095s]
sending 'cache' (10372 KB)...
OKAY [ 1.358s]
writing 'cache'...
OKAY [ 0.280s]
rebooting...

finished. total time: 127.830s
Flasing Stock Rom DONE

Deleting tmp dir _extracted
Deleting _extracted DONE

The device should be rebooting, once it is booted,
do the initial setup, enable developer options and USB debugging again.

Next step is flashing TWRP && superSU && Kali Nethunter using twrpFlash.sh script


~/nethunter-LRT on master
$ ./twrpFlash.sh
NETHUNTER LINUX FLASH (TWRP, SuperSU and Kali Nethunter)

CHECKING PRE-REQUISITES

Checking if adb is installed
adb FOUND
Checking if adb is installed DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed DONE

Adb connection check
ADB device detected.
Adb connection check DONE

Checking TWRP image existence
Dir twrpImage/ has files
Checking TWRP image existence DONE

Checking SuperSu existence
Dir superSu/ has files
Checking SuperSu existence DONE

Checking Kali Nethunter zip existence
Dir kaliNethunter/ has files
Checking Kali Nethunter zip existence DONE

CHECKING PRE-REQUISITES DONE

Sending Kali Nethunter zip to the device
Transferring: 684614479/684614479 (100%)
7566 KB/s (684614479 bytes in 88.354s)
Sending Kali Nethunter zip to the device DONE

Sending SuperSu zip to the device
Transferring: 4288330/4288330 (100%)
5785 KB/s (4288330 bytes in 0.723s)
Sending SuperSu zip to the device DONE

Rebooting into bootloader
Rebooting into bootloader DONE

Flashing TWRP image
< waiting for any device >
sending 'recovery' (9296 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.201s]
finished. total time: 1.413s
Flashing TWRP image DONE

Booting into TWRP (20 secs dont worry)
downloading 'boot.img'...
OKAY [ 1.213s]
booting...
OKAY [ 0.513s]
finished. total time: 1.726s
Booting into TWRP DONE

Installing SuperSU
Installing zip file '/sdcard/supersu.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found

*****************
SuperSU installer
*****************
- Mounting /system, /data and rootfs
- Extracting files
- System mode
- Disabling OTA survival
- Removing old files
- Creating space
- Placing files
- Restoring files
- Post-installation script
- Unmounting /system
- Done !
Done processing script file
Installing SuperSU DONE!

Installing Kali Linux Nethunter
Installing zip file '/sdcard/kaliNethunter.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found

Starting AROMA INSTALLER version 3.00
(c) 2013-2015 by amarullz.com

AROMA INSTALLER Finished...

Done processing script file
Installing Kali Linux Nethunter DONE!
Rebooting into Kali Linux Nethunter
error: no devices found
Everything is installed. Phone should be booting up! Enjoy

"We require adb but it's not installed/in path."

i installed adb and fastboot with android sdk on linux with this tutorial https://android.gadgethacks.com/how-to/android-basics-install-adb-fastboot-mac-linux-windows-0164225/ (Method 3)
but i got this "error" (in the title)
but i dont know what is meant with "path" ? i tried this tutorial http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 to do it in the path but the file .bash_profile was empty and it didnt work.....but not only this if i try to execute adb and fastboot with a shell command it is still not working....but i saw both installed in the ./nexustools file? so i dont know what to do? and what is this file: "gitgnore"?

Encryption on OPO 64gb

I encrypt before NH is installed on the device. But it fails after ./twrpFlash.sh command. Please help me how to fix it ? I need to encrypt my device.

Nexus 4 adb push error

Hi,

When installing nethunter on a Nexus 4 with latest android rom (following all steps from : https://github.com/offensive-security/nethunter-LRT) both adb push -p commands fails to run as -p option just bring the help menu of adb.

adb has been installed on a fresh installation of Kubuntu using sudo apt-get install android-tools-adb version being Android Debug Bridge version 1.0.31.

By removing -p it works.

I don't know if this can help other user or if the script should be updated but I considered leaving you a note about it.

Thanks

Cyanogen services shutting down?

Is Cyangen's website down for good? I found a excerpt on Google...

Dec 23, 2016 - As part of the ongoing consolidation of Cyanogen, all services and Cyanogen- supported nightly builds will be discontinued no later than...

Google keywords: "cyngn.com website is down"

target didn't report max-download-size

Hello, I have a Nexus 10.
All steps have been complete to get the stock flash on.

I am now to using ./twrpFlash.sh
I am getting a couple of errors, one is when sending SuperSu to the device. the /sdcard/ directory is invalid for both TwrpImage and SuperSU. I removed the /sdcard/ and that seems to have kept the script going.
However, when the bootloader comes up and the script tries: fastboot flash recovery $twrpImage, I get the message "target didn't report max-download-size"
I searched and tried:
fastboot -S 512M flash recovery $twrpImage

but that did not work either.

Any suggestions appreciated.

-R
Andy

no devices emulators found BUT showing in fastboot devices..

I've been researching for days how to fix this..
adb/fastboot is installed in PATH and working correctly as far as I can tell.
my OPO shows up in devices
I'm using High Sierra OSX.

Terminal Output:

[MY MBP]:nethunter-LRT-master d4m$ ./stockOpoFlash.sh 64gb
NETHUNTER LINUX FLASH (STOCK OPO Fastboot IMAGES)

NOTE: THIS WILL FACTORY RESET THE DEVICE (15 secs to cancel using 'ctrl + c')

CHECKING PRE-REQUISITES

Checking if adb is installed
adb FOUND
Checking if adb is installed ...DONE

Checking if fastboot is installed
fastboot FOUND
Checking if fastboot is installed ...DONE

Adb connection check
error: no devices/emulators found
ADB DEVICE NOT DETECTED!!!
Aborting.
[MY MBP]:nethunter-LRT-master d4m$ fastboot devices
9e653603 fastboot
[MY MBP]:nethunter-LRT-master d4m$

PLEASE HELP. I'm stuck in boot/recovery mode

installing nethunter problem in my oneplus one(A0001)

I am newb. im trying to install nethunter in my oneplus one. i have install twrp 3.0.2.0-bacon. i flash cm 13.0 in it. then download nethunter 3.0 from its official website. but when i try to install it in my phone using twrp it is showing me some error
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram12' (Not a directory)"
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram14' (Not a directory)"
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram16' (Not a directory)"
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram10' (Not a directory)"
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram13' (Not a directory)"
"Error opening : '/data /local/nhsystem/kali-armf/dev/ram15' (Not a directory)"

"Error opening : '/data /local/nhsystem/kali-armf/dev/loop6' (Not a directory)"

and when i click on reboot. it automatically return into twrp. it didn't show me any finished dialog or something.
please help me what to do?
can someone please guide me a full procedure. how can i install it in my mobile. which MOD would be batter for it.thanks

Cant find saved meterpreter

Where to find the generated meter prefer in Kali nethunter? I generated it in nethunter terminal

where is flash-all.sh script?

in the line 50 of the script stockNexusFlash.sh calls the flash-all script and doesnt exist, how is that possible?

Updates

How do you update to the current release?
apt update && apt dist-upgrade throws errors.

Unable to mount /data

Hi,

I recently got a Nexus 7 (2013). I've unlocked and flashed the stock with no problem. However, when I attempt to do the last step (2.3 Custom Recovery (TWRP) + SuperSU (root) + Kali Linux NetHunter), the transferring of files was ok but it seems like it's unable to finish the last two steps.

Here's a section of what it says when I try to run the scrip twrpFlash.sh:

Booting into TWRP (20 secs dont worry)
downloading 'boot.img'...
OKAY [ 0.357s]
booting...
OKAY [ 0.028s]
finished. total time: 0.386s
Booting into TWRP DONE

Installing SuperSU
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
E:Unable to mount '/data'
Unable to locate zip file '/sdcard/supersu.zip'.
Installing '/sdcard/supersu.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Failed to sysMapFile '/sdcard/supersu.zip'
E:Error installing zip file '/sdcard/supersu.zip'
Done processing script file
Installing SuperSU DONE!

Installing Kali Linux Nethunter
E:Unable to mount '/data'
Unable to locate zip file '/sdcard/kaliNethunter.zip'.
Installing '/sdcard/kaliNethunter.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Failed to sysMapFile '/sdcard/kaliNethunter.zip'
E:Error installing zip file '/sdcard/kaliNethunter.zip'
Done processing script file
Installing Kali Linux Nethunter DONE!
Rebooting into Kali Linux Nethunter
Everything is installed. Phone should be booting up! Enjoy

I'm new to all of this, so if I'm missing something, please let me know. I will appreciate any help!

Also, I'm not sure if this has anything to do with it, but I have the Nexus using PTP instead of MTP.

Thanks

NetHunter .zip failing to transfer to SD if MTP is not enabled

Installing Kali Linux Nethunter
Unable to locate zip file '/sdcard/kaliNethunter.zip'.
Installing zip file '/sdcard/kaliNethunter.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Failed to map file '/sdcard/kaliNethunter.zip'
Error installing zip file '/sdcard/kaliNethunter.zip'
Done processing script file
Installing Kali Linux Nethunter DONE!
Rebooting into Kali Linux Nethunter
Everything is installed. Phone should be booting up! Enjoy

MTP was not enabled
I ended up transferring the .zip manually but should add a check to see if file transferred successfully before rebooting to flash.

Nexus 6p OEM unlock failed

oemunlock script fails for me on my Nexus 6p. I ran fastboot flashing unlock instead of fastboot oem unlock and it worked. May need to update the script, or try running both.

Not working for OnePlus one

while running./stockOpoFlash.sh 64gb it reboot and stuck on fastboot screen

unable to get past flash stock

I have tried twice to update my OPO to Nethunter 3.0 using the Linux Root Kit. I have TWRP 3.0, cm 12.1-YAOGDAS2K1-bacon-signed-fastboot.zip, nethunter3.0-oneplus-lollipop.zip, and SuperSU2.46.zip.
both times it stops after EXTACTING stockImage/cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18.zip DONE

cd to _extracted
cd to _extracted DONE

Rebooting into bootloader
Rebooting into bootloader DONE

Flasing Stock Rom
!!!! DONT UNPLUG THE DEVICE !!!!
< waiting for device >

The device is plugged in, adb and fastboot working.

don't use SuperSu from XDA_Chainfire

https://m.reddit.com/r/Android/comments/3mzty9/supersu_a_closed_source_app_with_root_access_to/

Root is an important piece of security, don't play with it. There are good free and open source alterenatives:

https://github.com/phhusson/Superuser

Doesn't seem to work with nightly builds

I began running into problems with the regular NetHunter after trying to update and upgrade packages via apt, apt-get etc. Apparently caused by using super outdated kernel 3.4.0 (Kali Rolling is currently on 4.14.0). They seem to be available, but apt & apt-get seem to be broken. I tried installing the nightly build with this script, but to no avail.
I'm using a Nexus 5 (Hammerhead, running Android OS (Marshmallow):
Official Release:
https://images.offensive-security.com/nethunter-release/nethunter-hammerhead-marshmallow-3.0.zip
Nightly Build:
https://build.nethunter.com/nightly/2017.11-18-1618/kernel-nethunter-hammerhead-marshmallow-2017.11-18-1618.zip

root@kali:~# apt update
Err:1 http://http.kali.org/kali kali-rolling InRelease
  Temporary failure resolving 'http.kali.org'
Reading package lists... Done
Building dependency tree
Reading state information... Done
68 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  Temporary failure resolving 'http.kali.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

root@kali:~# uname -a
Linux kali 3.4.0-gb7558f2 #2 SMP PREEMPT Wed Oct 7 02:16:12 UTC 2015 armv7l GNU/Linux

root@kali:~# cat /etc/apt/sources.list
deb http://http.kali.org/kali kali-rolling main contrib non-free
# deb http://old.kali.org/kali sana main non-free contrib

root@kali:/# apt-cache search linux-image
linux-headers-4.14.0-kali3-armmp - Header files for Linux 4.14.0-kali3-armmp
linux-headers-4.14.0-kali3-armmp-lpae - Header files for Linux 4.14.0-kali3-armmp-lpae
linux-image-4.14.0-kali3-armmp - Linux 4.14 for ARMv7 multiplatform compatible SoCs
linux-image-4.14.0-kali3-armmp-dbg - Debug symbols for linux-image-4.14.0-kali3-armmp
linux-image-4.14.0-kali3-armmp-lpae - Linux 4.14 for ARMv7 multiplatform compatible SoCs supporting LPAE
linux-image-4.14.0-kali3-armmp-lpae-dbg - Debug symbols for linux-image-4.14.0-kali3-armmp-lpae
linux-image-armmp - Linux for ARMv7 multiplatform compatible SoCs (meta-package)
linux-image-armmp-dbg - Debugging symbols for Linux armmp configuration (meta-package)
linux-image-armmp-lpae - Linux for ARMv7 multiplatform compatible SoCs supporting LPAE (meta-package)
linux-image-armmp-lpae-dbg - Debugging symbols for Linux armmp-lpae configuration (meta-package)

Any ideas?

TWRP asks for DECRYPT password that I never set

So the install script isn't working because of some glitch with TWRP it appears.
Device: HTC Nexus 9
OS: Marshmellow 6.0.1
Error:
Everything works fine until the script reboots the device into TWRP. When TWRP loads it asks for a password to DECRYPT the data. I have never set a password on this device. No did I encrypt any data.
I have tried wiping it completely and flashing back to Marshmellow (clean install), then tried again. Same thing occurs. I have read a lot of other people are having the same issue. Is there a fix for this? Why does TWRP think my data is encrypted??