Database Develop

[cm12.1] [cm13.0] [maybe touchwiz] Kali NetHunter for the Galaxy S5

WARNING: THIS IS A BETA, USB CABLES MAY CATCH FIRE, YOUR CHAIR MAY BREAK, AND TRUMP MAY WIN THE ELECTION!
Welcome to the thread on Kali NetHunter for the Galaxy S5.
These Kali NetHunter builds are designed for CyanogenMod 12.1 and CyanogenMod 13.0.
I have TouchWiz builds as well, but NetHunter has not been tested on TouchWiz.
In theory, they should work fine on all AOSP based ROMs. The TouchWiz might work on most custom TouchWiz 5.0 ROMs too!
I am releasing on a nightly based development schedule similar to CyanogenMod.
Occasionally builds can show up more than once per night. This usually happens when there's a big update like a new device added to the line or an apk update for the NetHunter app.
These builds are NOT Aroma enabled, however, it should be no issue to just drag apps you don't need to the uninstall button in your app drawer.
Aroma support is going to be phased out for a while, especially with new TWRP releases coming out soon that may have newer kernels that aren't compatible with Aroma.
DOWNLOAD
Current version: 3.0.1 (beta, 2016-01-21)
Please be careful to download the right version based on this table:
SM-G900F, SM-G900W8, SM-G900T, SM-G900M, SM-G900A, SM-G900S, SM-G900K: klte
SM-G900I: kltedv
SM-G900P: kltespr
SCL23 kltekdi
CyanogenMod 12.1: lollipop
CyanogenMod 13.0: marshmallow
Nightly TWRP flashable zips are located at: https://idlekernel.com/nethunter/nightly/
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.
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.
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.
If you are already rooted or know you have systemless SuperSU installed, you will need to go into the SuperSU app and do a full unroot then reflash CyanogenMod (for the unmodified boot partition) and Gapps. The NetHunter installer does not play well with systemless SuperSU at this time.
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
Flash CyanogenMod installer zip
Flash Gapps if you want them (preferably OpenGapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Kali NetHunter installer zip from this thread
Boot into device
Open the NetHunter app
Use the Kali Chroot Manager to install Kali on your phone
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.
Upgrading from NetHunter 2.0 is not recommended, and may break the NetHunter app in some cases.
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 (klte, kltecan, kltesovietrussia, 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.
KNOWN ISSUES
F2FS - You need to have an ext4 data partition. I'm not sure why, but having a Kali chroot on your data partition totally breaks booting f2fs /data.
There is currently no fstab modifications in NetHunter, but I do plan on making a zip to automatically modify the fstab for f2fs later.
Marshmallow - New android app permissions API can wreak all sorts of havoc. On first boot, accept all permissions after opening the NetHunter app then reboot your phone. You might need to battery pull if it freezes up completely. Once app permissions are accepted, the next reboot should hopefully not freeze up and allow you to install your chroot normally. (once the NetHunter app has full support for the new Android API this should no longer be an issue)
USB Keyboard - The keyboard is unusable on some devices (ex. the Note 3) due to a depth bug that causes your key presses to go right through the keyboard into the swipe pad.
Terminal App - Full screen programs like nano or vi are unusable because they can't be rendered properly. Learn sed for text file editing. Just kidding that's cruel.
Install OpenSSH server in Kali and use the JuiceSSH app as an alternative to NetHunter Terminal. (it's wayyyy better sorry jmingov)
THE KERNEL
The NetHunter kernel for the Galaxy S5 is based on CyanogenMod 13.0 kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Krait specific Cortex-A15 & Neon-VFPv4 + -O2 compiler optimizations
Compiled with Linaro's branch of GCC 4.9.4
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
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 Galaxy S5, you can find the sources here: https://github.com/jcadduono/nethunter_kernel_klte
You can see my branch of the installer development here: https://github.com/jcadduono/kali-nethunter
Alternatively, but not updated as often, it is also available as another branch on the Offensive Security NetHunter GitHub: https://github.com/offensive-security/kali-nethunter/tree/master-jcadduono
The original branch of development is located here: https://github.com/offensive-security/kali-nethunter
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.

Reserved
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER

Hey Jcadduono, just wanted to say thanks! i was trying to do the same thing but never had enough time to fix all kernel recompile issues i got.
I am going to install this and run it as my daily driver i will let you know if i come up with any issues.
Thanks again and keep up the good work! If you need help anytime just say i am willing to help anytime anyway i can.

What about touchwiz

sielhadi said:
What about touchwiz
Click to expand...
Click to collapse
It's possible I could create a touchwiz branch (forked from my CM13 branch), but it would be unofficial and probably less maintained.
It would have a bunch of hacks to force the kernel to always be permissive to get past some issues, as well as merged latest drivers from touchwiz.
I would like to see if this CyanogenMod kernel works first though.
mixa2038 said:
Hey Jcadduono, just wanted to say thanks! i was trying to do the same thing but never had enough time to fix all kernel recompile issues i got.
I am going to install this and run it as my daily driver i will let you know if i come up with any issues.
Thanks again and keep up the good work! If you need help anytime just say i am willing to help anytime anyway i can.
Click to expand...
Click to collapse
Feel free to clone my nethunter_kernel_klte git branch, it's fully compliant with GCC 4.9.X. If you need any specific features you can send pull requests and it might merge them into main.
You should have no problems building it with build.sh or build_nethunter_images.sh (just edit the path variables in config sections of each file to point to right directory and compiler)
To build for kltecan, for example, just type
Code:
./build.sh can
You will get a zImage and a dtb.img inside ./build/arch/arm/boot folder.
Flashing kernels takes a little bit more work. You have to clone my kali-nethunter branch. Copy the zImage and dtb.img (replace the current ones) in ./nethunter-installer/kernels/androidversion/klteX/.
Then all you have to do is go to the ./nethunter-installer folder and do
Code:
./build.py -d klteX --androidversion -k
The -k flag builds just a kernel flashing zip out of your new zImage and dtb.img. Replace androidversion with marshmallow or lollipop. Replace X with your klte variant, ex. kltecan.
You can then flash that zip in TWRP and it will install your new kernel.

jcadduono said:
It's possible I could create a touchwiz branch (forked from my CM13 branch), but it would be unofficial and probably less maintained.
It would have a bunch of hacks to force the kernel to always be permissive to get past some issues, as well as merged latest drivers from touchwiz.
I would like to see if this CyanogenMod kernel works first though.
Feel free to clone my nethunter_kernel_klte git branch, it's fully compliant with GCC 4.9.X. If you need any specific features you can send pull requests and it might merge them into main.
You should have no problems building it with build.sh or build_nethunter_images.sh (just edit the path variables in config sections of each file to point to right directory and compiler)
To build for kltecan, for example, just type
Code:
./build.sh can
You will get a zImage and a dtb.img inside ./build/arch/arm/boot folder.
Flashing kernels takes a little bit more work. You have to clone my kali-nethunter branch. Copy the zImage and dtb.img (replace the current ones) in ./nethunter-installer/kernels/androidversion/klteX/.
Then all you have to do is go to the ./nethunter-installer folder and do
Code:
./build.py -d klteX --androidversion -k
The -k flag builds just a kernel flashing out of your new zImage and dtb.img. Replace androidversion with marshmallow or lollipop. Replace X with your klte variant, ex. kltecan.
You can then flash that zip in TWRP and it will install your new kernel.
Click to expand...
Click to collapse
You are AWESOME!
Thank you very much. I will try this as soon as i have time.

Got a bootloop on cm12 29.12.15 version. Clean install, no gapps, fully setup before flashing kali zip. Note that the device stays in the starting screen for like half a minute and goes to bootscreen then which it usually doesnt

dr460nf1r3 said:
Got a bootloop on cm12 29.12.15 version. Clean install, no gapps, fully setup before flashing kali zip. Note that the device stays in the starting screen for like half a minute and goes to bootscreen then which it usually doesnt
Click to expand...
Click to collapse
Do you get the same result with kernel-only zip? (if you flashed full zip, you will have to restore system, data, boot backups before trying kernel only)

Sorry for being a bit ignorant, but can someone explain me what is NetHunter? I've seen it for some devices but still have no idea what is it & what does it do...

I cannot, for the life of my get the 19-19 build to boot up, should I try another nightly? I'm flashing the full zip file ontop of a booted cm 13 + gapps install.
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Sorry should of added this, I'm on kltespr, and am flashing the 2nd one that came out.

pro_granade said:
I cannot, for the life of my get the 19-19 build to boot up, should I try another nightly? I'm flashing the full zip file ontop of a booted cm 13 + gapps install.
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Sorry should of added this, I'm on kltespr, and am flashing the 2nd one that came out.
Click to expand...
Click to collapse
sorry I need feedback from people who are just installing the kernel zip right now. I need to pinpoint whether the issue is kernel related or NetHunter script related.
for folks trying the kernel-only zips: Are you stuck on a neverending Kali boot logo, or the black screen with set warranty bit?

jcadduono said:
first
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
Click to expand...
Click to collapse
i am downloading right now this alone convices me

jcadduono said:
sorry I need feedback from people who are just installing the kernel zip right now. I need to pinpoint whether the issue is kernel related or NetHunter script related.
for folks trying the kernel-only zips: Are you stuck on a neverending Kali boot logo, or the black screen with set warranty bit?
Click to expand...
Click to collapse
bootloop

pro_granade said:
bootloop
Click to expand...
Click to collapse
doesn't help, boot loop is not specific
ALSO I really want recovery.log from TWRP with it!! (from when you flashed it)

Stuck at samsung screen

malbert16442 said:
Edit:will update with info starting fresh again
Click to expand...
Click to collapse
I might have found the issue. I was recompressing the ramdisk to the format it came in, rather than recompressing to gzip which is what the NetHunter kernels are set to use. I'm not sure what format CyanogenMod's klte ramdisks come in, but if it was anything other than gzip or xz then it wouldn't boot.
3.0.1-20160119-1913 forces ramdisks to gzip -9 instead. Hopefully that one will fix it. I suggest restoring original boot.img before flashing.
Edit: Your log says the compression was gzip, so I have no clue why it wouldn't boot. Gonna need more infos.
Also your log shows that there was no wallpaper in /data, do you have an empty data partition? It won't boot properly if android is not set up.
Update: 3.0.1-20160119-1944 will check to see if it's okay to install before trying to install.

jcadduono said:
I might have found the issue. I was recompressing the ramdisk to the format it came in, rather than recompressing to gzip which is what the NetHunter kernels are set to use. I'm not sure what format CyanogenMod's klte ramdisks come in, but if it was anything other than gzip or xz then it wouldn't boot.
3.0.1-20160119-1913 forces ramdisks to gzip -9 instead. Hopefully that one will fix it. I suggest restoring original boot.img before flashing.
Edit: Your log says the compression was gzip, so I have no clue why it wouldn't boot. Gonna need more infos.
Also your log shows that there was no wallpaper in /data, do you have an empty data partition? It won't boot properly if android is not set up.
Update: 3.0.1-20160119-1944 will check to see if it's okay to install before trying to install.
Click to expand...
Click to collapse
So this new update should be okay to flash?

pro_granade said:
So this new update should be okay to flash?
Click to expand...
Click to collapse
probably not, I still need someone to get me some form of logs while booting with kernel-only zip. I can't think of anything at all that could be preventing boot. it's even more confusing that you guys aren't even hitting the cyanogenmod boot splash.

jcadduono said:
probably not, I still need someone to get me some form of logs while booting with kernel-only zip. I can't think of anything at all that could be preventing boot. it's even more confusing that you guys aren't even hitting the cyanogenmod boot splash.
Click to expand...
Click to collapse
I dont know why log didn't show it but it did display an error about unpacking boot image. I had data and apps installed.
Are you going to compile from your source again or you want to find a definite answer.
P.s same issue with 12.1 and 13.0 with kernel.
Sent from my Samsung Galaxy S5 using Tapatalk

I think I might have fixed the issue. SELinux related. Will have new builds up soon.
Update:
https://idlekernel.com/nethunter/nightly/3.0.1-20160121-0200/
are these working for you guys?

[Recovery] Official TWRP for Galaxy S6 edge (3.0.2-0)

Team Win Recovery Project 3.0.2-1
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S6 edge (6.0+) stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys6edge.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR ROOTING YOUR DEVICE
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for your device variant.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] + [Power] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 12 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want your internal storage or data partition to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you only want a bootable system partition or readable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
** If your internal storage is encrypted, you will need to use adb sideload instead.
Go to [Reboot] -> [System].
Wait up to 5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 (twrp.me) - same as v3.0.2-1
v3.0.2-1 - New device tree and kernel, support added for Marshmallow, f2fs, and MTP.
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_zerolte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_noblelte (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S6 edge, Tool/Utility for the Samsung Galaxy S6 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/jcadduono/android_device_samsung_zerolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-05-27
Created 2016-04-08
Last Updated 2016-10-02

Builds are coming soon, just putting a thread up for a reference on the device page!

jcadduono said:
Builds are coming soon, just putting a thread up for a reference on the device page!
Click to expand...
Click to collapse
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app

christopherrrg said:
Sweet, stick a mention that G925W8 users flash T-Mobile variant plz. [emoji6] thanks for this! Now my friends can read.
Sent from my SM-G925W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log

I have successfully flashed the latest twrp. Though I had issues with the older one in backup restore area. Does the new do up backup and restore without error?

Nothing for SM-G925I ? zeroltedv

Ognjen123 said:
Nothing for SM-G925I ? zeroltedv
Click to expand...
Click to collapse
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.

jcadduono said:
there won't be a marshmallow G925W8 or G925T build until kernel sources are released. afaik neither of those devices have 6.0 officially yet.
they will still be using lollipop at 3.0.2-0 for now.
for others:
https://idlekernel.com/twrp/zerolte see 3.0.2-1, should be built soon on official, whenever someone confirms that everything is working ok
this includes:
adb shell
brightness slider
installing zips
formatting partitions (as ext4 and f2fs)
not crashing
backup & restore works for each partition
mtp
vibration
otg storage
whatever else you can think of checking
check on both L and M bootloaders, preferably quote my list with Y(working)/N(not working) in front of issues, and give recovery.log
Click to expand...
Click to collapse
G925W8 PC5 sources are up. Nothing for the 920W8 yet.

violin.siva said:
Brother I am using g925i only. Go to arter97 kernel page and download the recovery which he has modded for both and F and I variants.
Click to expand...
Click to collapse
Can you please pm the link ?
---------- Post added at 11:16 PM ---------- Previous post was at 11:06 PM ----------
Can the twrp-3.0.2-1-zerolte.tar.md5 be flashed on the g925i ?

Why aren't the link working?

G925f link?
Inviato dal mio SM-G925F utilizzando Tapatalk

Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?

Ognjen123 said:
Is the topic dead ? Anybody can tell me what recovery they are using on g925i 6.0.1 android ?
Click to expand...
Click to collapse
Twrp 3.0.2 with arter97 kernel. Working flawlessly in my g925i.

This is making me crazy , is there any suport here ? Links not working , where from to dl the 3.0.2-1 ver for g925i ?

OEM Unlock ??
I can't find it in my Developper Menu. I have 6.0.1 !
Help please...

Anyone found a working link for the recovery file?

Questions about TWRP versions found over some threads
I would like to know some things. Firstly say there's still nothing when you open http://teamw.in/devices/samsunggalaxys6edge.html
so, i looked up the link you gave
https://idlekernel.com/twrp/zerolte
but if I don't remember wrong, zerolte is S6 flat.
Does that kernel work anyway?
If that's so, does that mean official http://teamw.in/devices/samsunggalaxys6.html or TWRP S6 Edge Europe Version would also work?
Why wouldn't they?
Also, what's the difference with the twrp from @arter97 found Here
with yours?
Thanks!!
I hope someone could shed some light over those questions.
Sorry for my bad english!

Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .

Ognjen123 said:
Nobody is answering from them here , 0 suport . Kernel from arter97 and twrp recovery from him work fine .
Click to expand...
Click to collapse
See my above post.

Alright, this is what I did for my S6 Edge 925F which works fine so I thought I would share it with you guys:
I flashed the latest TWRP using ODIN from this link:
http://www.arter97.com/browse/S6/ke...r97-recovery-g925fi-13.1-twrp_3.0.2-0.tar.md5
which is the same link given at the bottom of this post along with the instructions as well:
http://forum.xda-developers.com/showpost.php?p=60390986&postcount=5
After rebooting the phone (which looped a couple of times), I flashed the latest SuperSU 2.71 (Beta) from ChainFire in the newly flashed TWRP which is given here:
http://forum.xda-developers.com/showthread.php?t=1538053
And now I have TWRP with SuperSU. I need to mention that I rooted my phone with CF-Auto root previously so it was already rooted, but I just wanted to have custom recovery for flashing other .zip files.
I also tried the latest stable version of SuperSU first, but it had problems finding and installing binaries. But there are no problems with the latest Beta (2.71) so far.

[TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17

Unofficial release -TWRP recovery for the Galaxy Tab S2 - SM-T713/719/813/819, Qualcomm MSM8976
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 1/4/2017
TWRP 3.1.0-1 MM/NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from source
System image backup
F2FS support >> To be added
Twrp app support
Bugs:
Reboot to recovery loop when using reboot utilities. Use hardkeys combo only to boot to recovery POWER + HOME + VOL UP
If you get stuck in a recovery loop reflash TWRP with auto-reboot enabled.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP 3.1.0-1 - Nougat
twrp_3.1.0-1_sm-t713_14417n
twrp_3.1.0-1_sm-t719_13417n
twrp_3.1.0-1_sm-t813_14417n
twrp_3.1.0-1_sm-t819_14417n
TWRP 3.1.0-1 - Lollipop/Marshmallow
twrp_3.1.0-1_sm-t713_1417
twrp_3.1.0-1_sm-t719_1417
twrp_3.1.0-1_sm-t813_1417
twrp_3.1.0-1_sm-t819_1417
TWRP 3.0.2-1
SM-T713/719
twrp_3.0.2-1_sm-t713
SM-T813
twrp_3.0.2-1_sm-t813
SM-T819
twrp_3.0.2-1_sm-t819_31816
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Does rooting require a permissive kernel?

DeeXii said:
Does rooting require a permissive kernel?
Click to expand...
Click to collapse
Rooting doesn't, custom recovery might.
I don't know yet until someone reports.

I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.

dalingrin said:
I was not able to mount /data in TWRP however.
Click to expand...
Click to collapse
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted

dalingrin said:
I was able to both flash TWRP with Odin as well as root the device.
I was not able to mount /data in TWRP however.
I couldn't use adb shell while in recovery due to a libc.so not found error. ADB did work in the Samsung provided Android 6.0.1.
I've attached the recovery log as well as the kernel log.
Click to expand...
Click to collapse
York2k16 said:
I'm not sure, but could this be caused by enabled encryption
As far as I know Android devices which are sold with 6.0.1 by default need to be encrypted
Click to expand...
Click to collapse
Thanks for testing and posting the logs. @York2k16 Correct the error mounting data is because of encryption. Twrp is unable to find the encryption key.
It's true Android 6 devices are encrypted by default, but don't need to be.
Work around for now would be not to use encryption until I find the solution.
The issue with adb is because of Samsungs stock kernel.
I need to recompile it with root protection removed.
Unfortunately no sources are available as yet.
Well at least we have a working recovery and a root solution.
Can you confirm a few things:
UI orientation, portrait or landscape?
UI colour?
All other options and features working correctly?
Thanks, well done for probably being the first in the world to have a rooted S2 VE 8.0

ashyx said:
Work around for now would be not to use encryption until I find the solution.
Click to expand...
Click to collapse
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?

TWRP does not work properly on T813. I am unable to use it because can not click on buttons

York2k16 said:
Few weeks ago I've tested the T813 and returned it back after a few days. I'm going to buy the LTE model soon or when the prices go down a bit.
Checking the security settings menu I've realized that there is no option for enabling/disabling device encryption, only SD encryption.
@dalingrin: Is this the same case on your device?
This "issue" would open up another question: How do I decrypt a device, which is encrypted by factory default, but doesn't offer any options to disable/enable encryption?
Click to expand...
Click to collapse
you need to format the data partition in TWRP to remove encryption.

whynottoday said:
TWRP does not work properly on T813. I am unable to use it because can not click on buttons
Click to expand...
Click to collapse
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?

@dalingrin
Does this at least ask for the encryption password?
https://www.androidfilehost.com/?fid=24572330218881914
Also whilst in the android OS could you post me the output of
ls -l /dev/block/bootdevice/by-name/
Thanks.

ashyx said:
How about a little more constructive detail like I asked for?
What orientation is the GUI, is it landscape or portrait. Are the touches simply misplaced?
Click to expand...
Click to collapse
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app

whynottoday said:
Oh sorry
So it is landscape and yes it seems that touches are misplaced. Thanks
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.

ashyx said:
Does this fix the touch issue?
https://www.androidfilehost.com/?fid=24572330218881937
.
Click to expand...
Click to collapse
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app

whynottoday said:
Yes thanks so much. Root done with my sdcard. Mount issue still here
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
Mount issue, you mean data?
Can you post the recovery.log.
You will find it under Advanced in twrp.

ashyx said:
mount issue, you mean data?
Can you post the recovery.log.
You will find it under advanced in twrp.
Click to expand...
Click to collapse
here attached

whynottoday said:
here attached
Click to expand...
Click to collapse
try this, could you post the log too please.
https://www.androidfilehost.com/?fid=24572330218881937

I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?

DeeXii said:
I now have a T713 if you need anything tested.
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
Anyone here have a link to the T713 stock PD9 firmware?
Click to expand...
Click to collapse
Can you test the link in post #11.
Can you mount data?

ashyx said:
Can you test the link in post #17.
Can you mount data?
Click to expand...
Click to collapse
Give me a few...
I'm finishing up some work things and uploading stock to AFH.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
ashyx said:
Can you test the link in post #11.
Can you mount data?
Click to expand...
Click to collapse
Post #17 says its for T813; Does that matter?

[MOD][D802] MultiRom V33 [WIP]

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for the LG G2. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Click to expand...
Click to collapse
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Click to expand...
Click to collapse
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d802-UNOFFICIAL.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d802_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Click to expand...
Click to collapse
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
Click to expand...
Click to collapse
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Click to expand...
Click to collapse
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Click to expand...
Click to collapse
Source code
https://github.com/multirom-g2
https://gist.github.com/wulsic/dfce9de8983d0a6247350fa2e45c13d4
Thanks to
@Tasssadar
@Eliminater74 - For his previous work on MultiROM for the G3 devices
@nkk71 - For the extra twrp/multirom mods including The kmsg logging options
@z31s1g - For The TWRP Themes (MultiRom)
@Skin1980 - For his previous work on MultiRom and LiveBump
@dadi11 for his modded version of skin1980's script
@blastagator for his TWRP devicetree and base installer zip
@genesixxbf3 && @berryman13 for their previous help on the old multirom
And everyone else I probably forgot.
Click to expand...
Click to collapse

Downloads
Flash Order
MultiRom TWRP
Kexec Hardboot patched kernel (CM-13.0 BASED)
Multirom Installer
Click to expand...
Click to collapse
Downloads
MultiROM Installation Files:D802
Click to expand...
Click to collapse
Attention!
Flashing is at your own risk. You can't blame me if you didn't read everything correctly and or ended up getting softbricked.
Click to expand...
Click to collapse
Release only for D802 yet, Support for all G2 variants incoming soon
Click to expand...
Click to collapse

MultiRom status: it boots the second rom but it will eventually bootloop, could also be that I did something wrong or that I must change some variable still. I am trying to logcat it but can't get logcat to work even after editing ramdisk and last_kmsg is always gone so I gotta think of something for that.
Btw. I don't know how it works with loki and my TWRP MultiRom doesn't have extra temperature control and so on like Blastagators twrp has but I can say it's safe to use as I've used it already for sometime and didn't noticed too high temperatures
If someone has some advice or ideas too then he or she is free to be my guest and reply
Also if someone could acquire an logcat from an secondary rom that's also bootlooping that would be nice.
Files are still uploading
EDIT:
It took a bit longer to upload the files as my computer couldn't handle the my virtual machine anymore
Also Mokee comes to optimizing apps screen but then goes back to the boot animation, so that's an good sign

Thanks for this. I Will definitely try this later.

The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.

Wow! You are an hero!
This was the only regret from my previous nexus device!

jneto3000 said:
The project is great but it didn't work here using crDroid as primary ROM. Don't even show the screen to choose which ROM to boot. Will keep an eye on it for future updates. Sorry I can't help more.
Click to expand...
Click to collapse
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:

Is it stable this version? Or is it as the old multirom?

matteo0026 said:
Is it stable this version? Or is it as the old multirom?
Click to expand...
Click to collapse
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low

wulsic said:
it's a step further then the old multirom as that couldn't like boot properly or the rom had to use the same kernel but I will try to use soon the old kexec patch to see if it works but if it's good then mine adjusted one should've worked better but I'll try to compile it as soon again as I have time. The interest still stays low
Click to expand...
Click to collapse
Thanks! My dream is that i can edit all the partitions size that i can use all the space at the better. (now i can only use adb and edit it with shell)

wulsic said:
Did you properly installed the multirom trampoline afterwards in the multirom twrp? And well I actually hoped that more people would invest in this and also send logcats etc but it seems that or nobody watches original android dev or nobody really can help much with it, I am also trying to finish it further but I don't have much time and I am sure that it's almost to the final part, only some small configuration fixes so I gotta think of an way to logcat as it's also my daily driver. I also hoped that this fundemental base could also inspire other devs by looking again further into it. I can't test 24/7 but thanks for those who even flashed it at all and I hope I can make it soon fully working and if neccesary I will move it to android dev section that it could get perhaps a bit more attention:good:
Click to expand...
Click to collapse
I did as mentioned by you in the OP:
1. MultiROM TWRP
2. Kexec kernel
3. MultiROM zip
Then I reboot recovery and went to MultiROM option to install a secondary ROM, using Krexus and then XOSP. It says the ROM is installed fine but when I reboot device It boots up directly to primary ROM (which is crDroid).
What am I doing wrong?
I guess this topic would have more attention if it were in Android Development section, people might see this MultiROM topic and think this is the same old topic that already exists and is not working anymore.
Also, about the logcat not working, the only thing I know is about enabling adb on ramdisk, which I did here using Android Image Kitchen (the one you posted is not enabled yet) and replaced boot.img by the new one, but I couldn't test since the MultiROM did not work here yet.

I'm very excited about this multirom. The fact is that if anything goes wrong I might lose something. I still use the g2 as primary phone.
Soon or later I'll try also this mod.
Thanks @op for the effort.

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"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"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly