Welcome to the thread on Kali NetHunter for the nVidia SHIELD tablet and SHIELD tablet K1.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
The installer zip will add a few files (including busybox) to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
These Kali NetHunter builds are designed and tested for nVidia's Marshmallow release & CyanogenMod 13.0.
In theory, they should work fine on -all- Marshmallow SHIELD ROMs.
DOWNLOAD
Current version: 3.15.2 (testing, 2016-10-13)
Download here: https://build.nethunter.com/nightly
Your device is: shieldtablet
Recommended install method: Use TWRP 3.0.2-2 or newer for shieldtablet
Install kernel-nethunter-shieldtablet and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Kernel only installers are in the kernel-only directory inside each build directory. It might be a better idea to try and install that first and see if you can boot before flashing the entire NetHunter.
You can actually only install the kernel if you want to take advantage of its features without having to install the rest of NetHunter!
BEFORE INSTALLING
Do not flash the NetHunter update zip with a fresh data partition!
Most ROMs will wipe it clean on the first boot if you haven't completed the Android Setup Wizard yet, there's no need to wipe your ROM or data to try it out. I do advise backing up your data partition before flashing the zip though.
(this should no longer be possible now with added installation checks)
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist in CyanogenMod by itself.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
FULL INSTALL STEPS
Boot into TWRP
Flash kernel-only/kernel-nethunter-shieldtablet and chroot-full/nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Reboot into device
Open the NetHunter app
Let the NetHunter app finish setting everything up
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery. On some ROMs you may need to wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the new ~60 MB nethunter-generic-armhf zip and kernel-nethunter-shieldtablet zip in TWRP.
RUNNING WIFI PENETRATION TESTS
The internal WiFi chipset of the SHIELD tablet is not capable of running services which use monitor mode such as Wifite. For this, you will need to use a monitor mode capable WiFi adapter through a microUSB OTG adapter.
As for compatible adapters, I highly recommend the Alfa Networks AWUS036NEH (eBay) which uses the Ralink RT3070 chipset. There are currently no monitor mode supported Wireless-AC adapters available.
Once plugged in, you can run the command from Kali terminal to turn on your adapter:
[email protected]:~# ip link set wlan1 up
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better be shieldtablet)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard & VNC - Google Keyboard, AOSP Keyboard, CM Keyboard do not work due to a depth bug, use Hacker's Keyboard as a workaround.
Terminal App - Full screen programs like nano or vi are unusable unless you use the resize command. (always type resize when opening a new terminal window)
THE KERNEL
The NetHunter kernel for the nVidia SHIELD tablet is based on nVidia's rel-24-sb-r1-2 kernel sources.
It has the following changes:
F2FS added using Jaeguek Kim's latest kernel.org:f2fs-stable sources (available on data partition)
Cortex-A15 & Neon-VFPv4 + -O2 compiler optimizations
NEON-asm kernel & SHA/AES NEON support
Compiled with Linaro's branch of GCC 4.9 (2016.02)
Simple IO (SIO) scheduler as default IO scheduler (updated)
USB HID Gadget keyboard support
mac80211 packet injection support
Updated mac80211 and USB WiFi drivers
TCP congestion control updates and fixes
Westwood, HTCP, or Cubic (default) TCP congestion algorithms
DriveDroid compatibility
Steel01's KEXEC hardboot support for Multi-ROM
Additional drivers built in for the full Kali NetHunter experience
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the nVidia SHIELD tablet, you can find the sources here: https://github.com/jcadduono/android_kernel_nvidia_shield
See the Kali NetHunter installer source here: https://github.com/offensive-security/kali-nethunter
See the Kali NetHunter app source here: https://github.com/offensive-security/nethunter-app
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
XDA:DevDB Information
Kali NetHunter for the nVidia SHIELD Tablet, Device Specific App for the Nvidia Shield Tablet
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Version Information
Status: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-10-13
Created 2016-04-11
Last Updated 2016-10-14
Yay!
fattire said:
Yay!
Click to expand...
Click to collapse
Big thanks to this guy for doing all the testing, it's been a pleasure going in blind!
This is awesome to see. I'm going to have to load this up over one of my cm-13.0 builds and see how it goes. A few of us local devs considered porting it a time or two, but never got around to it. Many thanks to both of you for getting it working.
jcadduono said:
THE KERNEL
The NetHunter kernel for the nVidia SHIELD tablet is based on nVidia's rel-24-sb-r1-1 kernel sources.
It has the following changes:
KEXEC hardboot support for Multi-ROM
Click to expand...
Click to collapse
So, those kexec patches aren't needed unless you're expecting to be running as the primary ROM. Which I guess is possible. But also note that those are in flux... I haven't got multirom officially working for M yet. I might have just cracked it tonight, but it isn't released yet. Also, the arm64 kexec patch set isn't needed for this device, they're there because the kernel also works for Tegra X1 devices, aka the Shield TV.
Steel01 said:
This is awesome to see. I'm going to have to load this up over one of my cm-13.0 builds and see how it goes. A few of us local devs considered porting it a time or two, but never got around to it. Many thanks to both of you for getting it working.
So, those kexec patches aren't needed unless you're expecting to be running as the primary ROM. Which I guess is possible. But also note that those are in flux... I haven't got multirom officially working for M yet. I might have just cracked it tonight, but it isn't released yet. Also, the arm64 kexec patch set isn't needed for this device, they're there because the kernel also works for Tegra X1 devices, aka the Shield TV.
Click to expand...
Click to collapse
Hey, alright, thanks! I kind of just saw the patches there and figured "may as well grab em so people aren't complaining it won't boot" (this happens a lot on devices with multirom support!)
Good to know who to credit them to now. I'll update it again when you've got it all working then.
I've got a shield TV myself which is why I cherry picked the X1 parts. Figured I'd try it out on there eventually for the the chroot and a few services anyway. <.<
hi only see 1 zip in the downloads section?
Sorry dev but am lost here a can only find the kernel zio??
skooter32 said:
Sorry dev but am lost here a can only find the kernel zio??
Click to expand...
Click to collapse
yep you're lost i concur 100%, go back and read the instructions again
I tested the kernel with the Vulkan OTA. On point. Perfect.
JCAdduono this is awesome! I installed it and was able to successfully add my external wireless card (Alfa AWUS051) with a quick "ifconfig wlan1 up". Thanks for the time put on it just to give us new functionality! I will put it to the test through my class and give you feed back! Thanks!!
Am I the only one unable to access adopted storage using this twrp?
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
Am I the only one unable to access adopted storage using this twrp?
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
probably not, i have no idea how to get adopted storage working in TWRP
i wonder if it's because it's built in 6.0 branch instead of 5.1
jcadduono said:
probably not, i have no idea how to get adopted storage working in TWRP
i wonder if it's because it's built in 6.0 branch instead of 5.1
Click to expand...
Click to collapse
I was using the 3.0.0 twrp with the Vulcan update prior to this, even tho it lagged the adoptable storage was available. Maybe this could point you in the right direction. Thanks for the quick response.
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
I was using the 3.0.0 twrp with the Vulcan update prior to this, even tho it lagged the adoptable storage was available. Maybe this could point you in the right direction. Thanks for the quick response.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
well, no, it doesn't point me in any direction as i have no idea what you are talking about or where to find this, or even if the developer made his sources available (unlikely)
but you know what else could point me in the right direction? a recovery.log
jcadduono said:
well, no, it doesn't point me in any direction as i have no idea what you are talking about or where to find this, or even if the developer made his sources available (unlikely)
but you know what else could point me in the right direction? a recovery.log
Click to expand...
Click to collapse
Well, the twrp I was referring to is this one by @Steel01
http://forum.xda-developers.com/showthread.php?p=64520513
However the unofficial twrp 3.0.2 by @romracer also works. I'm not sure if the source is available for the 3.0.2, but steel01 has stated his source is available. I'll reflash yours and pull some logs in a little bit. Thanks again
Edit: oh, the Vulcan update I was talking about was the 6.0.1 ota from Nvidia, not the borked 6.0 update
Edit 2: I guess I wasn't using the twrp I thought I was. The steel01 versions don't actually let you access adopted storage. But the other by romracer does
Sent from my SHIELD Tablet K1 using Tapatalk
Got that recovery log
https://drive.google.com/file/d/0B44pUMrBECEWVVZienBYOGxOYzA/view?usp=docslist_api
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
Got that recovery log
https://drive.google.com/file/d/0B44pUMrBECEWVVZienBYOGxOYzA/view?usp=docslist_api
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
hmm invalid usb mass storage lun too...would be nice if i could get someone to work with me in #twrp channel on freenode irc to fix issues
the touchscreen is laggy and buggy too right?
jcadduono said:
hmm invalid usb mass storage lun too...would be nice if i could get someone to work with me in #twrp channel on freenode irc to fix issues
the touchscreen is laggy and buggy too right?
Click to expand...
Click to collapse
I'll find you ol. Dees_troy is usually the one to talk to...
I guess my first dumb question is why is a ROM maintaining a separate version of twrp and not just using the ones already built?
Then what tree was it built against? I assume USB is working on mine (see here, yes it's the multirom edition, but all the standard twrp 3.0 functions are the same). I can't test that right now, though. Can someone with the problems see if they happen there too?
The touchscreen (technically screen refresh) issue is the same both here and on the shield tv. No idea what's going on. Tried toggling double buffering off, but no dice. lj50043 (iirc on the numbers) is the official twrp maintainer for the tablet. He'd be the one to talk to. But he hasn't made any progress last I checked either.
Just about to give this a go!
Kudos to you guys for finally giving me a nerd outlet on the go
Related
Kali NetHunter for the Galaxy Note 3 (3.1.0)
Welcome to the thread on Kali NetHunter for the Samsung Galaxy Note 3.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most AOSP based ROMs should be supported!
The updater zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
DOWNLOAD
Current version: 3.15.3 (stable, 2016-12-17)
Please be careful to download the right version based on this table:
N9005: hlteeur
N900W8 & N900T: hltecan
N900P: hltespr
N900K, N900L, & N900S: hltekor
SC-01F: hltedcm
SCL22: hltekdi
CyanogenMod 12.1 & SlimRom 5.1: lollipop
CyanogenMod 13.0 & SlimRom 6.0: marshmallow
Nightly TWRP flashable zips are located at: https://build.nethunter.com/nightly/
BEFORE INSTALLING
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist in CyanogenMod by itself.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
FULL FRESH INSTALL STEPS
Optional: Flash CyanogenMod/SlimRom installer zip
Optional: Flash Gapps if you want them (preferably OpenGapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash kernel-nethunter-hlte* and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Boot into device
Open the NetHunter app
Use the Kali Chroot Manager to finish the installation
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~60 MB update-nethunter-* zip again.
RUNNING WIFI PENETRATION TESTS
The internal WiFi chipset of the Galaxy Note 3 is not capable of running services which use monitor mode such as Wifite. For this, you will need to use a monitor mode capable WiFi adapter through a microUSB OTG adapter.
As for compatible adapters, I highly recommend the Alfa Networks AWUS036NEH (eBay) which uses the Ralink RT3070 chipset. There are currently no monitor mode supported Wireless-AC adapters available.
Once plugged in, you can run the command from Kali terminal to turn on your adapter:
[email protected]:~# ip link set wlan1 up
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (hlte, hltecan, hltesovietrussia, etc.)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
You may be able to fix some bugs by updating to the latest bootloader and modem for your device.
See: (Direct Download) Latest Bootloaders & Modems
KNOWN ISSUES
USB Keyboard & VNC - Google Keyboard, AOSP Keyboard, CM Keyboard do not work due to a depth bug, use Hacker's Keyboard as a workaround.
Terminal App - Full screen programs like nano or vi are unusable unless you use the resize command. (always type resize when opening a new terminal window)
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the Samsung Galaxy Note 3, you can find the sources here: https://github.com/jcadduono/idleKernel-note3
See the Kali NetHunter installer source here: https://github.com/offensive-security/kali-nethunter
See the Kali NetHunter app source here: https://github.com/offensive-security/nethunter-app
It is powered by idleKernel, however none of the idleKernel scripts (ikconfig, usb control, kernel tweaks) are available by default. I recommend installing idleKernel zip (non-NetHunter) from the idleKernel thread and then flashing the NetHunter updater or kernel installer over idleKernel. You will then have all of idleKernel and Kali NetHunter's features at your disposal.
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
XDA:DevDB Information
Kali NetHunter for the Galaxy Note 3, Device Specific App for the Samsung Galaxy Note 3
Contributors
jcadduono, the Kali NetHunter team
Source Code: https://github.com/jcadduono/kali-nethunter
Version Information
Status: Stable
Current Stable Version: 3.15.3
Stable Release Date: 2016-12-17
Created 2016-01-07
Last Updated 2016-12-21
Reserved
first
great cant wait to try it out
What solution are you offering for Wifi devices, Are you going to compile kernel for compatable devices?
Or is this something the user is going to have to do.
I only mention this, as i have a Working version of Nethunter and have for over a year, But i refused to post release information due to the support required to get various wifi devices to work.
I did not want to get involved so the release never happened, Am happy compliling my own kernel for supported drivers, But i dont see your average joe doing this.
Also another snag i found was you can only have the one wifi device enabled at one time, so disabling the onboard to enable the external.
All issues by commands, but am just questioning if you have considered this or have support for this?
dave7802 said:
What solution are you offering for Wifi devices, Are you going to compile kernel for compatable devices?
Or is this something the user is going to have to do.
I only mention this, as i have a Working version of Nethunter and have for over a year, But i refused to post release information due to the support required to get various wifi devices to work.
I did not want to get involved so the release never happened, Am happy compliling my own kernel for supported drivers, But i dont see your average joe doing this.
Also another snag i found was you can only have the one wifi device enabled at one time, so disabling the onboard to enable the external.
All issues by commands, but am just questioning if you have considered this or have support for this?
Click to expand...
Click to collapse
I suppose multiple WiFi devices would be in the realm of Kali rather than the kernel. I can't imagine it being harder than using a powered USB hub to connect multiple radios and configure each of them using one of the network managers available in the Kali repository, while leaving your native Broadcom WiFi to Android to handle. All the popular / mac80211 injection capable WiFi drivers are compiled right into the kernel and enabled - not as modules. The Nethunter installer takes care of installing all the necessary firmware binaries to your system partition as well.
The compatible USB WiFi dongles should just be plug and play at this point.
I'm still waiting on my TP TL-WN822N to arrive from Amazon for testing.
Btw have you tried the Nethunter 3.0 app? It really is designed to make everything quick and easy, 1 step for whatever you're trying to do.
Considering swinging by the #nethunter room on freenode to ask questions and/or suggest ideas to make things easier.
I have not tried 3.0
Am still talking about 2.0 seems like they have added some additional support like network manager.
This was not present in my build so i just use a few bash scripts to enable and disable.
But ill give this version 3.0 a try thanks
dave7802 said:
I have not tried 3.0
Am still talking about 2.0 seems like they have added some additional support like network manager.
This was not present in my build so i just use a few bash scripts to enable and disable.
But ill give this version 3.0 a try thanks
Click to expand...
Click to collapse
Not a network manager in nethunter app, I mean install one in Kali chroot the same way you would on a Debian server.
Version 3.0.1 is now up and the changes are:
Tell SuperSU to install in system mode (not systemless)
Update SuperSU to version 2.66
Use SuperSU's supolicy binary to patch the sepolicy during install (fixes Marshmallow/CM13.0 unable to boot)
Inject init.superuser.rc into the ramdisk if it's not there already
SuperSU should no longer be broken with non-gzip compressed ramdisks
Find commits here: https://github.com/jcadduono/kali-nethunter/commits/master
Please note that it is still Kali Nethunter 3.0, and the .1 is just an update that improves flashing compatibility.
Y'know, I really thought you guys would be eating this stuff right up. <_<
please include flashing instructions - do we need to also flash gapps...which ones should we use. Thank you.
comptonhubbard said:
please include flashing instructions - do we need to also flash gapps...which ones should we use. Thank you.
Click to expand...
Click to collapse
It's not a ROM, it's an app, kernel, and environment. You have to flash it on an already set up CyanogenMod ROM from TWRP.
jcadduono said:
It's not a ROM, it's an app, kernel, and environment. You have to flash it on an already set up CyanogenMod ROM from TWRP.
Click to expand...
Click to collapse
After IdleKernel 6.6.5?
Gandicela said:
After IdleKernel 6.6.5?
Click to expand...
Click to collapse
Doesn't matter. If you flash idleKernel after, make sure it's the -kali version though. The only thing flashing idleKernel does is add ikconfig, /sbin/usb, and a few small kernel tweaks in the ramdisk.
jcadduono said:
Doesn't matter. If you flash idleKernel after, make sure it's the -kali version though. The only thing flashing idleKernel does is add ikconfig, /sbin/usb, and a few small kernel tweaks in the ramdisk.
Click to expand...
Click to collapse
I see. It's therefore like this: Running CM>>Kali Hunter>>Kali Hunter Kernel. Cheers, Mate!
I need to format SD-card?
amazing work.
tnx
Mx WaR HaBiB said:
I need to format SD-card?
amazing work.
tnx
Click to expand...
Click to collapse
No you dont have to format it
Sent from my SM-N9005 using Tapatalk
Gandicela said:
I see. It's therefore like this: Running CM>>Kali Hunter>>Kali Hunter Kernel. Cheers, Mate!
Click to expand...
Click to collapse
So, do we need to use version for CM 12.1 for OnePlus from here?
https://www.offensive-security.com/kali-linux-nethunter-download/
Ps
It works
First install kali kernel, after download Kali for oneplusone, reboot into recovery, install kali zip, and aftet again idle kali kernel.
I am on CM 12.1 nightly...
eseregin said:
So, do we need to use version for CM 12.1 for OnePlus from here?
https://www.offensive-security.com/kali-linux-nethunter-download/
Ps
It works
First install kali kernel, after download Kali for oneplusone, reboot into recovery, install kali zip, and aftet again idle kali kernel.
I am on CM 12.1 nightly...
Click to expand...
Click to collapse
Why are you doing this!!! You're bound to end up breaking something.
All you do is flash this after completing CM setup wizard and you're done. There's absolutely no reason to download any other Kali installer. This is the full version 3.0! Nethunter app now sets up your chroot for you.
Full steps:
Flash CyanogenMod installer zip
Flash Gapps (preferably opengapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Galaxy Note 3 Kali Nethunter installer zip from this thread
Boot into device
You're done!
If you absolutely need ikconfig or /sbin/usb, then you can install idleKernel-kali zip from the idleKernel thread later.
3.0.1_2016_01_10 build uploaded. Just a bug fix for Nethunter app.
Installation query
I have CM13 set up with superSU 2.46 and idleKernel 6.5.5 installed.
Do I have to install CM all over again? And follow your steps, or is there a way for me to keep my data and just flash it as is?
UnbracedTundra said:
I have CM13 set up with superSU 2.46 and idleKernel 6.5.5 installed.
Do I have to install CM all over again? And follow your steps, or is there a way for me to keep my data and just flash it as is?
Click to expand...
Click to collapse
Make a full backup in twrp first.
Wipe /system and dalvik and /cache. Install latest CM13 (or CM12.1 if thats what you meant) zip and gapps, then boot into system. Once boot is complete, reboot into recovery and flash nethunter then boot and you should be good to go without deleting your data.
jcadduono said:
Why are you doing this!!! You're bound to end up breaking something.
All you do is flash this after completing CM setup wizard and you're done. There's absolutely no reason to download any other Kali installer. This is the full version 3.0! Nethunter app now sets up your chroot for you.
Full steps:
Flash CyanogenMod installer zip
Flash Gapps (preferably opengapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Galaxy Note 3 Kali Nethunter installer zip from this thread
Boot into device
You're done!
If you absolutely need ikconfig or /sbin/usb, then you can install idleKernel-kali zip from the idleKernel thread later.
3.0.1_2016_01_10 build uploaded. Just a bug fix for Nethunter app.
Click to expand...
Click to collapse
Wow...
I am idiot!
Completely ignored the main link I needed -
https://idlekernel.com/nethunter/cm12.1
Now I understand that went dangerous way, lucky still with working phone
Tbh, most all utilities in Kali for now behind my knowlage of Linux so far
PS
I can see some scripts somehow survived even with full wipe, now my recovery provide some red lines doing job, something path missing in /data/...something/something
Though do the job.
I thought nothing can survive after full wipe...
Welcome to the thread on Kali NetHunter for the LG G5.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
The installer zip will add a few files (including busybox) to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
These Kali NetHunter builds are designed and tested for LG G5 stock 6.0.1 firmware.
DOWNLOAD
Current version: 3.1.0 (stable, 2016-04-29)
Download here: https://idlekernel.com/nethunter/nightly
Your device is: h830 (T-Mobile) / h850 (International)
Recommended install method: Use TWRP 3 for H830 or TWRP 3 for H850
Install kernel-nethunter-[h830|h850] and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
You can actually only install the kernel if you want to take advantage of its features without having to install the rest of NetHunter!
BEFORE INSTALLING
Do not flash the NetHunter update zip with a fresh data partition!
Most ROMs will wipe it clean on the first boot if you haven't completed the Android Setup Wizard yet, there's no need to wipe your ROM or data to try it out. I do advise backing up your data partition before flashing the zip though.
(this should no longer be possible now with added installation checks)
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist due to other factors unrelated to NetHunter.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
If you would like to use another root method, or prefer systemless SuperSU, then simply remove the supersu folder from the installer zip and it will proceed without it.
FULL INSTALL STEPS
Follow the instructions on setting up working data and internal storage in TWRP.
Flash kernel-nethunter-[h830|h850] and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Reboot into device
Open the NetHunter app
Let the NetHunter app finish setting everything up
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery. On some ROMs you may need to wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just reflash the kernel-nethunter-[h830|h850] zip and the ~60 MB update-nethunter-generic-armhf zip in TWRP.
RUNNING WIFI PENETRATION TESTS
The internal WiFi chipset of the G5 is not capable of running services which use monitor mode such as Wifite. For this, you will need to use a monitor mode capable WiFi adapter through a USB-C host adapter.
As for compatible adapters, I highly recommend the Alfa Networks AWUS036NEH (eBay) which uses the Ralink RT3070 chipset. There are currently no monitor mode supported Wireless-AC adapters available.
Once plugged in, you can run the command from Kali terminal to turn on your adapter:
[email protected]:~# ip link set wlan1 up
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better be h830/h850)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard & VNC - Google Keyboard, AOSP Keyboard, CM Keyboard do not work due to a depth bug, use Hacker's Keyboard as a workaround.
Terminal App - Full screen programs like nano or vi are unusable unless you use the resize command. (type resize when opening a new terminal window)
Sound - There is no sound when using the NetHunter kernel. Well, the Kali slogan...you know. Just kidding, this needs urgent fixing!
THE KERNEL
The NetHunter kernel for the LG G5 is based on LG's H850 v10a kernel sources.
It has the following changes:
Updated to Linux 3.18.31 (security fixes & more)
F2FS added using Jaeguek Kim's latest kernel.org:f2fs-stable sources (available on system/data/cache!)
UKSM - Ultra Kernel Same-page Merging support
Compiled with -O2 optimizations using GCC Linaro 5.3 aarch64 toolchain
Simple IO (SIO) scheduler as default IO scheduler (updated for modern kernels)
USB HID Gadget keyboard support
mac80211 packet injection support
Westwood, HTCP, or Cubic (default) TCP congestion algorithms
savoca's KCAL display color calibration driver
RTL-SDR, BT RFCOMM, and various WiFi OTG drivers enabled
NFS and CIFS client support with file caching
Additional drivers built in for the full Kali NetHunter experience
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the LG G5, you can find the sources here: https://github.com/jcadduono/nethunter_kernel_g5
See the Kali NetHunter installer source here: https://github.com/offensive-security/kali-nethunter
See the Kali NetHunter app source here: https://github.com/offensive-security/nethunter-app
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
XDA:DevDB Information
Kali NetHunter for the LG G5, Kernel for the LG G5
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/jcadduono/nethunter_kernel_g5
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.1.0
Stable Release Date: 2016-04-29
Created 2016-04-23
Last Updated 2016-06-07
I am confused, is this a rom, kernel or performance boost mod ? please Eli5...
_ray_ said:
I am confused, is this a rom, kernel or performance boost mod ? please Eli5...
Click to expand...
Click to collapse
It's a kit ROM so to speak. It's for penetration testing so if you don't know what it is then you don't need it.
ChongoDroid said:
It's a kit ROM so to speak. It's for penetration testing so if you don't know what it is then you don't need it.
Click to expand...
Click to collapse
Kool, cheers
Up and runing. Bootanimation is not fullscreen, and it looks like wifite does not find any internal wifi (Not that internal will be of any use, but it was shown on my other android device). Need to get a usb-c otg cable now to get my alfa rocking again.
This are just things i find, should not be in a offended way.
Awesome that it came to h850 so fast, thanks.
Pinu'u said:
Up and runing. Bootanimation is not fullscreen, and it looks like wifite does not find any internal wifi (Not that internal will be of any use, but it was shown on my other android device). Need to get a usb-c otg cable now to get my alfa rocking again.
This are just things i find, should not be in a offended way.
Awesome that it came to h850 so fast, thanks.
Click to expand...
Click to collapse
Yup added a note in the middle of my first post about the internal WiFi. Unfortunately the boot animation was made for us in 1080p and while we could resize it to other resolutions, it wouldn't look very nice stretched out. :x I guess it wouldn't be terrible on 2560x1440, but we can't really be bothered to create multiple boot animation zips right now unless someone wants to help us!
I'm just glad it worked first try, I made a ton of changes in the kernel and was expecting it to crash or not boot. It's nice to have a reliable device to maintain without owning it once in a while, Samsung's S7 is certainly the opposite where compiling even the stock kernel sources results in boot loops.
Also really glad OEMs are including full armhf binary support on their aarch64 devices! We've yet to port NetHunter fully to aarch64, though the installer is ready, the chroot isn't.
Could someone please gather a recovery.log from TWRP after flashing the two zips? Advanced -> Copy log to SDcard, copy it off your sdcard and preferably upload it in your reply. Thanks!
(I'm ensuring that everything is installing correctly with no silent errors)
If you've already installed NetHunter, it's safe to flash the zips again as much as you want!
nice to see this, current have it running one my oneplus one, will try it on my g5 soon
It would be very interesting to see a modular bottom modded to support an OTG interface and the insides of a USB wifi dongle...
Anybody having problems with adb and bluetooth not working ? Just want to be sure it's me.
Pinu'u said:
Anybody having problems with adb and bluetooth not working ? Just want to be sure it's me.
Click to expand...
Click to collapse
same here, and on top of that... No Sound at all. System wide. All Sources... Freaky :cyclops:
Thx, hopefully after a few updates all is fine .
Miustone said:
same here, and on top of that... No Sound at all. System wide. All Sources... Freaky :cyclops:
Click to expand...
Click to collapse
hmm those are both things that were modules that i turned to builtin, maybe i need to make them back into modules, perhaps LG is using closed source kernel module versions? :S
jcadduono said:
hmm those are both things that were modules that i turned to builtin, maybe i need to make them back into modules, perhaps LG is using closed source kernel module versions? :S
Click to expand...
Click to collapse
Strange, hope you can fix it... Can't help you with that. But if you need more infos or a Log. Just say something! Really want to use this Kernel... Great work at all. Thanks!:good:
All connections are working Now with latest Version of this Kernel. But the Sound is still missing. None of the Outputs is working. Bootsound is also not hearable... ?
Hi can you work on having NTFS support via otg. Thanks.
I have no sound and sd card not reading on H30.
Sent from my LG-H830 using Tapatalk
Has the sound issues and stuff been fixed:fingers-crossed:? I'm planning to get the G5 and this kind of a deal breaker between it and the HTC 10
(BTW, I'm planning on getting the H830)
This looks pretty awesome but I wouldn't install it on my G5. I think I'd get a OnePlus Two or something for this.
No sound and SD Card can not be read.My Phone is H850,V10c.I flash latest Version of this Kernel(kernel-nethunter-h850-marshmallow-3.1.0-20160524-1936)
I wonder if the dev would be better off compiling the kernel from source once more then adding in the modules one by one testing to see which one breaks it then just removes it until a future release.
This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.
Working:
Phone
Mobile data in dual-sim configuration
Wifi
GPS
Bluetooth
Audio
Known Bugs:
Torch tile in the status bar is not available
Haptic feedback on soft buttons
XDA:DevDB Information
CM13 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
ottmi, siljaer
Source Code: https://github.com/ottmi/android_device_elephone_trunk
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20160902
Beta Release Date: 2016-09-02
Created 2016-06-07
Last Updated 2016-09-02
Changelog
20160902
First try to fix sdcard issues, will need more testing
Fix thermal-engine to actually start
Fix audio_effects.conf
Tweak auto-brightness
Enable OTA updates
Use Wileyfox Swift blobs for everything but camera
Update to latest CM13 source
20160816
Enable thermal-engine to fix overheating emergency shutdowns
Update kernel to latest MSM8916 to fix Quadrooter vulnerabilities
Re-enable AEC audio effects
Update to latest CM13 source
20160811
Revert changes to mixer_paths.xml and audio_effects.conf to fix echo problems
Update to latest CM13 source
20160803
Update to latest CM13 source to fix surfaceflinger crashes
20160803
Tweak GPS settings to obtain faster locks
Enable input event for headphone jack
Use ACDB libraries from Wileyfox swift, fix some ACDB-related settings
Update to latest CM13 source
20160722
Incorporate @siljaer's modifications to mixer_paths.xml to fix echoes and low volume audio recordings
Pull in additional permissions to reflect actual hardware of the phone (light & proximity sensor)
Change screen density to 300dpi
Backport LZ4 compression from Linux 3.12 for use in ZRAM
Try to fix Torch problems by restarting media service after full boot
Update to latest CM13 source
20160708
Fix wpa_supplicant crashes
Update to latest CM13 source
20160706
Switch to generic CyanogenMod MSM8916 kernel
Use Wileyfox Swift kernel configuration as template
Increase partition sizes of system and data to 1.8GB and 12GB
Update to latest CM13 source
20160630
Fix bug in libstagefright properly
Fix sensor glue code to only show actually existing sensors
Fix device permissions
Use own key to sign code instead of testkeys
Set selinux to enforce
Update to latest CM13 source
20160616
Fix mediaserver crashes to a bug in libstagefright (roll back to commit 8f270dc)
Use Adreno binary blobs from Wileyfox Swift (which are more complete)
Update to latest CM13 source
20160614
Enabling of Qualcomm Fluence as suggested by @Bingo Bronson
Backport of the F2FS driver from Linux 3.12
Enabling of LTE as preferred network on 2nd SIM card as well
Some changes to the auto brightness thresholds
Update to latest CM13 source
20160611
Enable haptic feedback on soft keys
Change default device name for wifi direct and hotspot to "Trunk" (not Benefit!)
Update to latest CM13 source
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Flashing Instructions
You will have to disable the bootloader lock first:
Enable developer options in Android by tapping the Build version in Settings > About 7 times
Check "Enable OEM unlock"
Next you will have to boot into TWRP, use @hisname's TWRP:
http://forum.xda-developers.com/gen...410-5-inch-t3177753/post66208281#post66208281
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash recovery twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Installation Xposed Rom Ottmi
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
josoft86 said:
Installation Xposed Rom Ottmi
@ottmi
Which version of Xposed install since I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64 can give me advice and thank you for your work
Click to expand...
Click to collapse
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
josoft86 said:
I can not use: - cm-13.0-20160515-UNOFFICIAL-trunk - trunk1-TWRP-3.0.2.x- Xposed-v85-sdk23-arm64
ottmi said:
Sorry, I don't use Xposed, so I don't have any idea. arm64 and sdk23 sounds about right, though. What's the problem?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
ottmi said:
20160606
Use mixer_paths.xml file by Wenderer7755 to fix low volume on mic recordings
Update to latest CM13 source
Click to expand...
Click to collapse
Great, so many thanks, but, the link?
marcachas said:
Great, so many thanks, but, the link?
Click to expand...
Click to collapse
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Bingo Bronson said:
You have to use the download tab on the top of the thread since this is a DevDB supported thread...
http://forum.xda-developers.com/devdb/project/?id=15607#downloads
Example:
Visit xda with your browser if you are currently on xda labs or some kind of forum app.
Click to expand...
Click to collapse
Oh, thanks, you are the best, this rom is so table and smooth, your job is awesome, a hug.
Thank you. I decided to buy the Elephone Trunk because I was interested in a economic phone that could 'easily' be upgraded with non stock ROM (preferably CM 13).
I have gone through the previous conversation and I must admit I'm impressed with your progress so far. Congratulations and a big thank you!
I will definitely flash your build as soon as I receive the phone.
Enviado desde mi Nexus 5 mediante Tapatalk
Great job!
Great job and super useful guide @ottmi.
Thank you!
I am currently running your previous release (cm-13.0-20160515-UNOFFICIAL-trunk) and have no issues to report at all!
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
Thank you for the excellent work.
Kind regards.
P.S. I have downloaded and installed GAPPS (Google Apps) from CM portal and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
kbezerianos said:
In order to upgrade to the latest one, do I need to delete everything and start from scratch or is there an upgrade process?
[...] and found that the "nano" package has everything I need, while anything larger (e.g. full package) can't find enough space on system partition - no big deal though.
Click to expand...
Click to collapse
Dirty flash is enough, no need to clean everything. Just install the new build, wipe the caches afterwards like it is suggested by TWRP recovery.
Some of your apps may have a survival script, others need to be reflashed (this is just the case for special tools, like Xposed, etc.)
Nano Gapps is a smart choice either way, because all the pre-installed Gapps will be outdated soon enough, so why bother to install a "huge" Gapps pack...
I use microG and have roughly 260 MB left on the system partition.
Bingo Bronson said:
v84 works (used it for at least 3 weeks), updated to v85 yesterday: also working.
edit: Updated to 20160606 build, framework still active, all good.
Since no further details were provided, it would be nice if josoft86 could describe what happens during the "attempted" installation.
Click to expand...
Click to collapse
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
But, but... I'm also on 3.0.2-0 and the Xposed zips & ROMs, for example, are processed without error, Aroma installer is also supported...
Who compiled / ported your TWRP version? I used only @hisname releases and they never let me down. ?
ottmi said:
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
Click to expand...
Click to collapse
I didn't even consider that possibility, since it has been mentioned numerous times in the old thread, ignorance is bliss (on my side), ahem...
I'm out of "thanks" to give, so I'll "upvote for awareness" later...
josoft86 said:
Evidently use TWRP 3.0.2.0 not compatible but I works fine with other rom CM13 who have tried. I will try to install TWRP-05042016 to check. Thank you
Click to expand...
Click to collapse
If you're using a TWRP image that has been built for the Ark Benefit, it won't work with my ROM as TWRP will report the device as Ark Benefit and not as Elephone Trunk.
ottmi said:
You can boot TWRP either by flashing it to the recovery partition or by booting it directly via fastboot if you don't want to overwrite the stock recovery, i.e.:
Code:
fastboot flash boot twrp-05042016.img
or
Code:
fastboot boot twrp-05042016.img
Make a backup of the stock ROM and then do a factory reset. You can then flash the CM13 image from sdcard or via adb sideload.
Click to expand...
Click to collapse
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Enviado desde mi Nexus 5 mediante Tapatalk
21prods said:
Sorry, but I think there is an error. If you want to flash a recovery the code would be "flash recovery" instead of "flash boot".
Code:
fastboot flash recovery twrp-05042016.img
Appart from that (and the silly minute I've suffered because I did not understand at first what had gone wrong) everything is perfect :good:
Thank you, great job!
Click to expand...
Click to collapse
Bummer. You're right, I've fixed the instructions accordingly. Sorry for that!
21prods said:
One question, have any of you got to use a SD memory card as internal memory?
I have tried to do so but it gives me an error message when moving apps and pictures, as if there was not enough space (when the fact is that there is more than enough by far - 32 Gb).
Thanks in advance
Click to expand...
Click to collapse
I'm using a 32GB microsdhc to store music and pictures, no issues at all. I've also used 64GB mirosdxc without problems. I've never tried moving apps though.. How does it show in Settings->Storage & USB?
Yes, that's it. There you have the possibility of formatting the SD card to use it as (more) internal memory.
Enviado desde mi Nexus 5 mediante Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kali Nethunter for Motorola Moto G 2015[osprey] with wireless attacks workingINTRODUCTION:
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, Wireless Attack and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
Note:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this Kernel before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
802.11 Wireless Injection and AP mode support with supported USB wifi card such as TP-Link 722N V 1.0.
Supports BadUSB MITM attacks. Plug in your Nethunter to a victim PC, and have your traffic relayed though it.
Contains a full Kali Linux toolset, with many tools available via a simple menu system.
USB Y-cable support in the Nethunter kernel – use your OTG cable while still charging your Device!
Software Defined Radio support. Use Kali Nethunter with your HackRF to explore the wireless radio space.
SUPPORTED ROMs:
LineageOS 14.1 Based Custom ROM's
Now also supporting LineageOS 15.1 based custom ROM's
Bugs:
Phone Reboots when the Wireless Adapter is Removed.(Making a Permanent Fix for this) !
Fixed for Oreo ROM's
DOWNLOAD KERNEL FROM UPDATE SECTION AND FLASH IT VIA TWRP
SCREENSHOTS:
All Screenshots are given Below
Root Access Is required so root your device before flashing nethunter zip.
INSTALLATION INSTRUCTIONS:
Download the Latest Build From the Links Below
Install The Official TWRP Recovery From Here or use any other Supported Recovery that you currently have installed.
Take a Backup of your Current ROM.
Flash the NetHunter zip File.
Reboot.!
Enjoy!
Post Installation
After Flashing ZIP files, reboot your device
1. Open the NetHunter App and start the Kali Chroot Manager.
2. You might want to download the real packages which might be around 400-500 MB in size.
3. Set up Hacker Keyboard.
4. Set up custom commands.
Extra Information Regarding Wireless Attacks
1. To Enable Monitor Mode, type this cmd in the nethunter terminal - [sudo airmon-ng start wlan1]
2. to use Wifite V1, type this cmd in the nethunter terminal - [wifite --mon-iface wlan1mon]
3. to use Wifite V2, type this cmd in the nethunter terminal - [wifite -i wlan1mon]
Download Links
Nethunter ZIP
GitHub Source Codes:
Kali Nethunter Source Code
Kernel Source Code
CREDITS:
Kali NetHunter Whole Team for the source code and guide!
LineageOS team for the kernel source
XDA:DevDB Information
Kali Nethunter, Tool/Utility for the Moto G 2015
Contributors
rajeshdubey293
Source Code: https://github.com/rajeshdubey293/kali-nethunter.git
Version Information
Status: Stable
Stable Release Date: 2018-07-12
Created 2018-07-12
Last Updated 2018-07-12
If you like my work please consider thanks.
ENJOY!
Wow.. Nice
Update for LineageOS 15.1 Support
Now Kali Nethunter for Moto G 2015 is supporting Oreo ROMs.
Download Link:
Nethunter ZIP for Oreo custum ROMs
Support forecast for Merlin?
gambiarraweb1 said:
Support forecast for Merlin?
Click to expand...
Click to collapse
since turbo edition has different chipset and i do not own that devices so i can not test after building.
gambiarraweb1 said:
Support forecast for Merlin?
Click to expand...
Click to collapse
or one more thing can be happen, i will build kernel for you but you have to test it at your own risk.
Update V 1.3 - Fixed Rebooting
Fixed Rebooting after removing wireless adaptor
Download KERNEL below and flash it.
Download Kernel for Oreo ROM's
Earphones don't work with kernel
Thank you so much for porting nethunter, but the kernel has bug that makes earphones not work
FariosK said:
Thank you so much for porting nethunter, but the kernel has bug that makes earphones not work
Click to expand...
Click to collapse
For my device it works perfect.you just check with another kernel if it works or not.
can u upload net-hunter for android 6.0.1 moto g3 2015or osprey -nougat version will work ?
moto g5 plus
could create a kernel for moto g5 plus, to support external adapter?
can anyone help me I have flashed this on my moto g3 which has cm 13 installed[6.0.1] but after flashing i cant turn on wifi, it dosnt allow me to switch to wifi on. please help me, thanks in advanced
Narrize said:
can anyone help me I have flashed this on my moto g3 which has cm 13 installed[6.0.1] but after flashing i cant turn on wifi, it dosnt allow me to switch to wifi on. please help me, thanks in advanced
Click to expand...
Click to collapse
Your WLAN drivers are encompassed within your boot image. If you have a TWRP backup of your CM boot image, restore it. If you do not, extract the boot.img from the CM13 ROM build you are using. You can install it via TWRP or fastboot. Of course, if you are running systemless root (Magisk, pHH, SuperSU, etc) you will lose root unless you have an addon.d script installed. If you are using a CM based system-wide root, superuser access should not be affected at all. On reboot, your WiFi should be functioning normal. From this point, make a full TWRP backup of your device partitions and try the install from the OP again, taking care to fully follow OP's instructions.
Viva La Android said:
Your WLAN drivers are encompassed within your boot image. If you have a TWRP backup of your CM boot image, restore it. If you do not, extract the boot.img from the CM13 ROM build you are using. You can install it via TWRP or fastboot. Of course, if you are running systemless root (Magisk, pHH, SuperSU, etc) you will lose root unless you have an addon.d script installed. If you are using a CM based system-wide root, superuser access should not be affected at all. On reboot, your WiFi should be functioning normal. From this point, make a full TWRP backup of your device partitions and try the install from the OP again, taking care to fully follow OP's instructions.
Click to expand...
Click to collapse
so i basically go to twrp recovery, locate the boot.img and than install/flash it via twrp, than wifi should be working?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
Narrize said:
so i basically go to twrp recovery, locate the boot.img and than install/flash it via twrp, than wifi should be working?
Click to expand...
Click to collapse
and where can i find the boot.img, do i have to find a file on the internet specific to my ROM, or is it available within the phone itself..?
Narrize said:
so i basically go to twrp recovery, locate the boot.img and than install/flash it via twrp, than wifi should be working?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
and where can i find the boot.img, do i have to find a file on the internet specific to my ROM, or is it available within the phone itself..?
Click to expand...
Click to collapse
It is available within the ROM package you originally installed using TWRP. The CM ROM itself will be a zip archive. Extract the contents of that zip archive using WinZip, WinRAR, etc. One of the files inside will be the boot.img. Alternatively, you can reinstall the entire ROM without wiping userdata, known as a "dirty flash." But, all that should be needed to get your WiFi working is the boot.img.
rajeshdubey293 said:
For my device it works perfect.you just check with another kernel if it works or not.
Click to expand...
Click to collapse
may I ask how to install it properly becouse my kernel dosnt change after flashing t`the zip with twrp (i am a total noob so forgive me if the question is stupid)
should I creat a .img out of the files that are in the zip?
ok got the kernel running but know I flashed nethunter it worked and wallpper and boot screen changed but non of the apps are showing
rajeshdubey293 said:
Update V 1.3 - Fixed Rebooting
Fixed Rebooting after removing wireless adaptor
Download KERNEL below and flash it.
Download Kernel for Oreo ROM's
Click to expand...
Click to collapse
Thx for kali rom. But there is wifi turn on issue. Any solution !??
Only one issue :-. Wifi not turning on. Any solution plzzzz
Narrize said:
can anyone help me I have flashed this on my moto g3 which has cm 13 installed[6.0.1] but after flashing i cant turn on wifi, it dosnt allow me to switch to wifi on. please help me, thanks in advanced
Click to expand...
Click to collapse
Same bug in my moto G3 osprey :-(.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_nvidia_device_shield-common
https://github.com/Scavenger-87/android_device_nvidia_shieldtablet
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.10.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 18.10.2021
Scavenger87 said:
View attachment 5308899
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_device_nvidia
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.5.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 14.05.2021
Click to expand...
Click to collapse
Thank You for breathing new life into this great little tablet!
Thanks for keep this device alive!
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Thank you very much and nice job Scavenger for keeping our tablet up and running!
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
marrol said:
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
Click to expand...
Click to collapse
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
ogremalfeitor said:
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
Click to expand...
Click to collapse
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
summerstyle said:
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
Click to expand...
Click to collapse
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
ogremalfeitor said:
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Click to expand...
Click to collapse
Maybe we have to patch boot.img from NVidia Stock Recovery 5.2 and flash this one?
ogremalfeitor said:
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
Click to expand...
Click to collapse
This is a separate blob update. What for do we need this?
marrol said:
Maybe we have to patch boot.img from NVidia Stock Firmware 5.2 and flash this one?
Click to expand...
Click to collapse
That's not it. The boot.img is unique to every ROM. It contains the kernel and the initial ramdisk (initrd, if you're interested in details search for that and there are a lot of interesting articles explaining the boot process of Linux and derivates like Android).
I know magisk modifies the initrd to sort of "inject" itself during that early boot process, but it doesn't make the system hang with other ROMs, hence before assuming it's a bug in magisk I'd like to know if anyone has any idea or if the ROM is missing anything that could cause this?
marrol said:
This is a separate blob update. What for do we need this?
Click to expand...
Click to collapse
I believe it has to do with outdated bootloaders, which will be the case for people who never used recent stock firmwares, and it's there should you have problems (but don't confuse bootloader with boot partition or boot.img that I mentioned in another post). I think the script in the Zip detects it when you flash in twrp and gives an error if necessary but please correct me if I'm wrong.
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Hi everyone after a little vacation and some testing out of your reported issues this is what i found out so far:
Hworangg said:
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Click to expand...
Click to collapse
I installed that game on a Tablet with LOS 14.1 and LOS 15.1 and in both cases the Game crashes because it run out of memory. I did a quick test on my Rom with adding ro.config.low_ram=true to the build.prop which activate the Go Version of Android and decreased the usage of Ram this way .
The Game runs but it started to get really sluggish after around 30 seconds.
It seems this Game just needs more than the 2GB Ram this device can offer.
ogremalfeitor said:
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
Click to expand...
Click to collapse
After trying to flash many Versions of Magisk starting by 21.4 over 22.0 and the actual 23.0 via the TWRP Recovery Version (9.5.0_9-0) i mentioned in the Start Thread and trying to flash it with the Magisk App i also wasnt able to install Sucessfully Magisk without running into a Bootlop which is really a Bummer.
I dont know why this happends and i check my Kernel Logs i pulled with TWRP but for the moment we have to use the SU Addon by LOS.
Maybe it has something to do with that my build is signed with a personal key i will check that out.
summerstyle said:
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Click to expand...
Click to collapse
Thats just the Blob File that needs to be flashed when the Bootloader isnt updated to the latest Version (4.00.2016.04)
ogremalfeitor said:
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Click to expand...
Click to collapse
On some rare ocassions you get those same green artefacts on videos like you get with the LOS 16.0 Rom but at least in my case it happends once a week or so and it seems it have something to do with memory managment again.
My guess is that the tegra drivers arent working really well with Android Versions above Nougat (7.0) and this leads to a memory leak but like i said its just a guess by me maybe @Steel01 can say more about that.
I try to optimize the memory management in the future builds if possible.
Hi Everybody
I think its time to give you a little update of my work on this build
After i got a good example of the problems with the ram management of this device i was looking for a solution last few days and i began testing with the Android Go Settings as i mentioned in the last Thread.
With that settings i was able to start that Game mentioned by @Hworangg and i even was able to play it a bit as you can see on one of the added Screenshots below. But you could also see this Game is a real RAM Hog with needing up to 484MB at the last session i played but it is kinda playable you just have to stay in that Game and turn off every notification as it might crashes otherwise. Speaking of crashes while the GO Settings really helping on reduce the usage of Ram by the System itself and let the device take more Memory Pressure it also leads to freezes where you often have to Hard Reset the Tablet because it seems to not close the Main App when its in a Out of Memory Situation. This is something i have to invest more time and research even after i played a lot with the Dalvik VM Settings.
I also found out that my Personal Key Signature is the reason that the install of Magisk is leading to a Bootloop. Here i also have to figure out why this is happen and if its even possible to install Magisk on a Signed Custom Rom as you change out the BOOT.img on this Device to achieve that and it seems the Magisk installer isnt able to resign the File with my Key.
TLDR:
I was able to set up my Build to use the optimized Android GO Settings to withstand more Memory Pressure so that Games like COC and heavy Browsing Sessions with lots of Tabs and Sites with a lot of Pictures doesn't crash that soon but it lead in both cases to a freeze of the whole Device.
The Magisk installer does not work when i sign my build with my own key.
For this Reason i decided to release a another Build for you to test with this Settings as a Nightly Release before i release my next Regular Build when the next Security Patch is out
You find it here : Nightly Build and i´m curious about your opinion.
Flashed the nightly onto a freshly wiped K1 along with opengapps and Magisk 23 using patched boot, no problems there. Video playback - Netflix played about as well as it could with level 3 widevine, with Jellyfin no obvious visual problems streaming 1080p over lan. Got hard freezes when running memory heavy apps (firefox, manga reader, 3d unity games) but it was expected.
Ended up downgrading back to factory stock Lollipop as the memory management is best there, even better than stock Nougat. But will keep an eye on your builds because the K1 could still be a great little tablet if the memory issues in newer versions of Android was fixed. Thank you for your hard work