Develop Bugs

Install Xposed Framework to LG Spirit without recovery

This is method of installing Xposed Framework which is made by @rovo89 to use some tweaks without needing to modify system files (like SystemUI).
Original post was made in General Thread by @polfrank but I need to edit it with some new things which he is missing.
Code:
I'm in no way responsible for whatever happens to your device if things go wrong.
Your device is your responsibility, proceed with caution and only if you know what you're doing.
Apps and stuff which is needed to install Xposed Framework
* Root
* BusyBox - IMPORTANT, script don't work properly without BusyBox installed
* Terminal Emulator
* adb if you don't wanna to use Terminal Emulator - use this version of adb -> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
* Installer script - Updated to work with latest version of Xposed Framework zip files. It shows some minor problems which doesn't make installer not working. Translated from Spanish to English by @midzan21 aka myself.
* Xposed Framework zip file - IMPORTANT, download SDK21-ARM variant, not ARM64 or SDK22-ARM variant, because stock ROMs are compiled with 32-bit version, not 64-bit. Also SDK21 is for Lollipop 5.0.x and SDK22 is for Lollipop 5.1.x
* Xposed Installer apk - download latest version and install it
* Brain.apk - just in case, but still important
Installation process for Terminal Emulator:
1.) Put Xposed Framework zip, Xposed Installer apk and Installer script (extracted) on Internal memory of device (Internal SD Card, not your real SD card if you have it)
2.) Install BusyBox
3.) Open Terminal Emulator and enter this commands
3.1.) Gain Root Permissions after entering su command
Code:
su
sh /storage/emulated/legacy/installer
4.) Enter once 1 to continue installation
5.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
6.) Install Xposed Installer apk
7.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
8.) Install module which you want and after enabling it reboot phone
9.) Enjoy
Installation process for adb:
1.) Extract adb setup of provided adb
2.) Install BusyBox
3.) Go to adb folder
4.) Press Shift and Right Mouse Click and in context menu select Open command windows here
5.) Now copy Xposed zip file and installer file in adb folder
6.) Use this commands to do check if you Enabled Debugging in Developers options
Code:
adb devices
And after that you should see LG and some numbers with enabled right after that (this LG cripple is your Android Phone name for adb and fastboot)
7.) Copy files to internal SD card with this commands
Code:
adb push xposed-v80-sdk21-arm /sdcard/
adb push installer /sdcard/
Please note: always copy with latest vXX number Xposed zip
8.) Now it is easy stuff done, now it is time to do work which is hard part - doing commands to install Xposed
Commands are:
Code:
adb shell
su
mount -o remount, rw /system/
sh /storage/emulated/legacy/installer
9.) Enter once 1 to continue installation
10.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
11.) Install Xposed Installer apk
12.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
13.) Install module which you want and after enabling it reboot phone
14.) Enjoy
Problems, bugs and issues:
Currently none, added to script to remove LG QuickCover which make Force Close
Old bugs, problems and issues:
Weather FC (Fixed with never versions of Xposed Framework)
Tethering and networks in Settings FC (Fixed with never versions of Xposed Framework)
After every boot you have Android is upgrading screen (fixed with never versions of Xposed Framework)
To do list:
* Nothing at this point
Credits:
@rovo89 for Xposed Framework and Installer
@polfrank for original post in General Thread
Unknown person for creating original installer script

Changelog
Update #1 - 16.10.2015 @ 19:43
* Thread created
* Added link to this thread in General Thread for LG Spirit to @polfrank update thread post #1

There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it

andrekeys1 said:
There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it
Click to expand...
Click to collapse
There is no way to use QuickCircle cover because it is problematic with Xposed Framework for now. I tried before updating script with QC and it just got Force Close from booting up device.
Also I'm not sure would it work, but here is link to all LG V10 apps and there is QuickCircle app. Before testing make a a backup of stock apps just to be sure that it works and there is no problems.
https://mega.nz/#F!bpQGBbLQ!Q3eTeYxe5fIBLegkQjiI6A

Changelog
Update #2 - 7. 11. 2015 (0:12 @ CET)
* Updated installer script so it automatically remove /cache and /data/dalvik-cache (created back in end of October, tested and it works)
* Updated tutorial (shortened for few lines, but still it is way easier right now)
To-do list:
* Automatic installer without first confirmation and with automated reboot ( ETA: few days after this posting, need neighbours phone without Xposed to check it and test )
* Porting script to Android app ( early ETA: mid to end of December this year )

Is it possible to uninstall xposed?

Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
{
"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"
}

xyster13 said:
Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
View attachment 3539627
Click to expand...
Click to collapse
Missing BusyBox, need to install that first before doing anything.

midzan21 said:
Missing BusyBox, need to install that first before doing anything.
Click to expand...
Click to collapse
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?

xyster13 said:
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?
Click to expand...
Click to collapse
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)

midzan21 said:
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)
Click to expand...
Click to collapse
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!

xyster13 said:
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!
Click to expand...
Click to collapse
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)

midzan21 said:
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)
Click to expand...
Click to collapse
Oops yeah my mistake. I was confused a little by the program list and names on google play. You are right about ES File Explorer

@midzan21
I'm wondering why do you need to further improve your method? It works perfectly fine for me, without any issues. I'm just curious.

there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.

fliperpl said:
there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.
Click to expand...
Click to collapse
How did you uninstall it ?

BrosseLi said:
How did you uninstall it ?
Click to expand...
Click to collapse
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire

fliperpl said:
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire
Click to expand...
Click to collapse
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD

BrosseLi said:
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD
Click to expand...
Click to collapse
i did.

fliperpl said:
i did.
Click to expand...
Click to collapse
Thanks a last question: which uninstaller did you download ?
The arm ,arm64 or armx86 ?
EDIT: flashed the arm version, it worked well

[Root Question] How to I Install Xposed on Rooted Amazon Fire TV 2? (Guide Please)

How to I Install Xposed on Rooted Amazon Fire TV 2? (Guide Please)
Do I download XposedInstaller_3.0_alpha4.apk? and xposed-v78-sdk21-arm64.zip?
Please Help
Could I Use Flashfire?

You can't install xposed since there is no custom recovery

Tried with Flashfire where no custom recovery is needed ? what version of xposed should i try?

No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix

yeah I've had no luck, just have to wait I guess

ians325 said:
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
Click to expand...
Click to collapse
Did you encounter boot loop or soft-brick when you attempted this?

z_thompsonpa said:
Did you encounter boot loop or soft-brick when you attempted this?
Click to expand...
Click to collapse
No

ians325 said:
No
Click to expand...
Click to collapse
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
I couldn't run this command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
[*]SELinux enforces more policies when Busybox is installed
[*]Setting SELinux to Permissive has no effect
EDIT: **Details in my next post**

z_thompsonpa said:
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
SELinux enforces more policies when Busybox is installed
Setting SELinux to Permissive has no effect
Click to expand...
Click to collapse
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8

fldash said:
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
Click to expand...
Click to collapse
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.

keep up the good work

z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?

fldash said:
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
Click to expand...
Click to collapse
I haven't had to break out the USB A-A cable yet... thankfully (except for root of course).
I used Flashfire to backup my /system partition as RAW backup before I started all of this experimentation. I have just been restoring back to this known good state using Flashfire after each time I corrupt the system partition.
I intended on trying this method, and if it didn't work to fall back to the method mentioned in the root thread. I checked the logs last night and Flashfire seems to be succeeding at this task, at least.
Right now, I am picking through the Xposed installer script source and using the Flashfire logs to debug why it is failing. It appears to be a permissions issue, but a lot of the stdout/stderr is suppressed so its hard to tell exactly where. When I get home today, I am going to try to modify the installer script to produce more output so I can debug the issue further. If I cant figure it out, I'll post my findings either way.

I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.

z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
z_thompsonpa said:
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
Click to expand...
Click to collapse
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.

fldash said:
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
Click to expand...
Click to collapse
I think so... I am pretty sure its a dead end. I also tested using adb to write the files and it failed on /system/lib/libart.so, as well. It's, I believe, because the object is loaded in memory?? don't quote me on that... but loading through preloader, I think, would avoid this limitation as ART is not running.

So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.

sconnyuk said:
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
Click to expand...
Click to collapse
Use this method, I've slightly modified the text from another post & added it into a text file for you, this works a 100% but as usual I take no responsibility if you do any thing wrong & brick the Fire Tv2.
Enjoy & press that thanks button If this helped you

Thanks for this. I will try it shortly and report back if it works for me. I have stumbled upon another thread that the guys seem to be working on playstore issues, http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974

Made a guide here if anyone wants to install
http://forum.xda-developers.com/fire-tv/general/installing-xposed-fire-tv-2-guide-t3314142

[Kernel][Exynos][BROKEN] Kali NetHunter for the Galaxy S7

OKAY SO
Currently, I am unable to get even stock kernel sources to boot. I'm not sure what to do to at this point. Waiting on someone else that actually has the device to get this figured out - DO NOT FLASH!
WARNING: This is completely untested, highly theoretical, and possibly dangerous. Flash at your own risk.
Back up your original boot image in TWRP before attempting to flash this! If it doesn't boot, you can simply restore your previous boot image.
This is Kali NetHunter 3.0.5 for the Galaxy S7.
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 ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
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.0.5 (beta, 2016-03-11)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930X, SM-G930W8: herolte
SM-G935F, SM-G935FD, SM-G935X, SM-G935W8: See proper forum.
All others be sad.
Download is available at: https://idlekernel.com/nethunter/herolte/
Grab the 700 MB+ zip.
Kernel-only zip is for upgrading your kernel, or just using the NetHunter kernel by itself. (yes, you can do that!)
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
Flash this zip in TWRP to allow system modifications and unencrypted data: https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
Once that is flashed, go to the wipe page and use the [Format Data] button.
This will wipe all your data, including internal storage!
Boot up your system and set up Android.
Now you can go back into TWRP and flash Kali NetHunter.
Currently, Samsung encryption is not supported by TWRP, so we have to disable it.
Sorry security freaks! There's a lot of irony here, isn't there?
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 (2.68) 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.
Also included is an extra Busybox that gives you full large file support and some extra applets.
FULL FRESH INSTALL STEPS
Install Team Win Recovery Project to your recovery partition.
{
"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"
}
If your data partition doesn't mount 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!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
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 you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
Download Kali NetHunter.
Without exiting TWRP, transfer the NetHunter installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
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.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC G930FXXU1APAW kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted system, data, and cache partition support
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption changed from forced to optional (disabled during installation)
Disables dm-verity and allows you to boot modified system partitions
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 not be something other than G900F, dangit!)
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 - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
NetHunter Terminal - It doesn't automatically set the columns/rows, so you need to type "resize" sometimes to fix the display.
DEVELOPMENT
You can see my branch of the installer development here: https://github.com/jcadduono/kali-nethunter
Alternatively, the main branch is also available on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kernel source: https://github.com/jcadduono/nethunter_kernel_herolte
SCREENSHOTS
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.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.0.5
Beta Release Date: 2016-03-11
Created 2016-03-11
Last Updated 2016-04-15

Awesome! I asked if this was possible years ago. Glad someone is actually making it happen!

phone is rebooting now and then after flashing the kernel.. any idea why?

[email protected] said:
phone is rebooting now and then after flashing the kernel.. any idea why?
Click to expand...
Click to collapse
no you will have to wait for someone to try it that can actually provide useful information such as logs

jcadduono said:
no you will have to wait for someone to try it that can actually provide useful information such as logs
Click to expand...
Click to collapse
Not sure how to get logs when the device doesn't boot could you give us a hint so we can provide you with what you need?

finally, did great work there, but how do i download it
ok did manage it some how the IDM was the issue and cant download it

hm cant flash ur kernel and stuck in boot loop, when i try to flash it its says in twrp "unable to mount /data as rw!" any idea?

SELinux ins still enforcing or do you managed to change it?

Activadee said:
SELinux ins still enforcing or do you managed to change it?
Click to expand...
Click to collapse
The new kernel is selinux permissive if you don't mind trying it for me. It would really help if someone could join #nethunter on freenode IRC to get this working with me.
I've removed the full installer until we can get the kernel working without issues.

I installed now your test 2 Kernel zip. But its causing Bootloop - its dont go over the "Samsung Galaxy S7" logo. Its a European s7 with Exynos. If you tell me HOW to provide some logs i would like to help you if i can ;D
Edit// I Managed to upload the log from booting with your kernel. I don't know if it's right but maybe it helps you. I backed up my boot with twrp, flashed your kernel, reboot until the loop and restored the old boot with twrp
https://drive.google.com/file/d/0B9IHgLrX7UgTRThJUEs3RExUR1k/view?usp=docslist_api

Activadee said:
I installed now your test 2 Kernel zip. But its causing Bootloop - its dont go over the "Samsung Galaxy S7" logo. Its a European s7 with Exynos. If you tell me HOW to provide some logs i would like to help you if i can ;D
Edit// I Managed to upload the log from booting with your kernel. I don't know if it's right but maybe it helps you. I backed up my boot with twrp, flashed your kernel, reboot until the loop and restored the old boot with twrp
https://drive.google.com/file/d/0B9IHgLrX7UgTRThJUEs3RExUR1k/view?usp=docslist_api
Click to expand...
Click to collapse
nope need /sys/fs/pstore not recovery.log
i also need a backup of your boot partition after flashing the kernel

I upload the boot partition later. Would you please tell me how to grab the log from /sys/fs/pstore ? Via Adb from twrp?
// Edit
The files from the boot partition are uploaded
https://drive.google.com/folderview?id=0B9IHgLrX7UgTRnlvcWFiRHVwYUE
I just flashed your Kernel and backed up the partition after this. Or do you need one with already tried to boot?

Activadee said:
I upload the boot partition later. Would you please tell me how to grab the log from /sys/fs/pstore ? Via Adb from twrp?
Click to expand...
Click to collapse
yes it should exist for a few minutes after exiting boot loop and entering twrp, adb pull /sys/fs/pstore
it will grab the whole folder for you
in the meantime, i have made a flashable tar for kernel with the boot image you gave me. i trimmed out much of the secure stuff & knox, and enabled adb debugging.
https://idlekernel.com/nethunter/herolte/AP_nethunter_G930F_APB9_test1.tar
you should hopefully be able to adb in and get logcat and /proc/kmsg while it is stuck in samsung logo after flashing it....

jcadduono said:
yes it should exist for a few minutes after exiting boot loop and entering twrp, adb pull /sys/fs/pstore
it will grab the whole folder for you
in the meantime, i have made a flashable tar for kernel with the boot image you gave me. i trimmed out much of the secure stuff & knox, and enabled adb debugging.
https://idlekernel.com/nethunter/herolte/AP_nethunter_kernel_G930F.tar
you should hopefully be able to adb in and get logcat and /proc/kmsg while it is stuck in samsung logo after flashing it....
Click to expand...
Click to collapse
Going to do this later this day.

Activadee said:
Going to do this later this day.
Click to expand...
Click to collapse
Ok, lets begin.
I flashed first the test 2 zip from yesterday to get /sys/fs/pstore
flashed the zip via twrp -> reboot to system -> again it dont go over the FIRST Samsung logo - it shows up for 2 secs and rebooting again. This is the only result i get when i flash the zip. after i rebooted to twrp i connected my phone to my laptop to pull /sys/fs/pstore
So i started adb and typed in: adb pull /sys/fs/pstore
the result is
pull: building file list...
0 files pulled. 0 files skipped.
Click to expand...
Click to collapse
There is no files in the folder.
I restored the original boot partition and flashed your *.tar file via odin 3.10.7.
the result is just the same.
For better undestanding i uploaded a picture with my "high end build in 2MP Tablet Camera" to show you what samsung logo i mean. Its showing up for 2 secs, reboots and showing up again.
https://drive.google.com/open?id=0B9IHgLrX7UgTbkstc0RrOS1zamc
With the original boot partition - there is an other samsung logo after the first one. I uploaded it here :
https://drive.google.com/open?id=0B9IHgLrX7UgTcG1nZ3cyZ3VNbkk
Hope i could help you with this.

Activadee said:
Hope i could help you with this.
Click to expand...
Click to collapse
Thanks for your time and assistance. Would anyone else be willing to come to #nethunter on freenode IRC and flash a few test zips for me?

jcadduono said:
Thanks for your time and assistance. Would anyone else be willing to come to #nethunter on freenode IRC and flash a few test zips for me?
Click to expand...
Click to collapse
I would. I have the G935F so could help with that. Let me know. Everytime I go to #nethunter you're not active. I'm assuming it's due to our different time zones. I was then told I shouldn't be there if it's nothing to do with AOSP, which was rude. but anyway, let me know what I can do to help. I am available anytime after 2pm (GMT)
Sent from my SM-G935F using Tapatalk

Just ordered mine unnfortunately there's a 7 day lead time / back log if you're still stuck then I will be happy to come on IRC and help with the testing

this is kind of irrellevant, but could you please trhy to port it to the s6? it has no problems with the bootloader when loading unofficial files. also, i have not planned on getting the s7

Mgrev said:
this is kind of irrellevant, but could you please trhy to port it to the s6? it has no problems with the bootloader when loading unofficial files. also, i have not planned on getting the s7
Click to expand...
Click to collapse
i'm actually having the exact same problem on Note 5 right now, which will also apply to S6...can't figure out how to boot custom kernels without it rebooting at lock screen. =(
hopefully t-mobile S7/edge will not have these problems since it is qcom...
got to say development would be a million times easier if i had these phones myself ><
update 2016-03-28: try this if you're crazy enough! https://idlekernel.com/nethunter/herolte/ (grab latest)

Q beta 5 is GREAT,but can not mount /system for now

I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)

seardna said:
I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)
Click to expand...
Click to collapse
Happened to me before. I believe I cleared the system partition and it worked.

TechNash said:
Happened to me before. I believe I cleared the system partition and it worked.
Click to expand...
Click to collapse
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .

seardna said:
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .
Click to expand...
Click to collapse
Latest TWRP from website, magisk stable

TechNash said:
Latest TWRP from website, magisk stable
Click to expand...
Click to collapse
Thanks. But can you mount system in the TWRP? While install Magisk , there are some errors failed to mount /system (Invalid argument )

Would this be why titanium backup doesn't open either ??

this happened with beta 4 also. don't know if it's twrp or magisk issue

Q5,same issue here, tried everything, factory reset, format partition, no luck
apart from this, everything works
in root explorer, you can't mount R/W

A latest magisk alpha version maybe solved this problem .
Here is the custom channel :backup up FIRST!
https://raw.githubusercontent.com/yzkpqv68745/magisk/master/alpha.json

solución
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.

ismael47 said:
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.
Click to expand...
Click to collapse
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this

{
"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"
}
[/IMG]
darkoj2007 said:
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this
Click to expand...
Click to collapse
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.

I'm on official release 10.0.0 (QP1A.190711.020, Sep 2019) flashed without "-w" over android 9. Pixel 2.
Flashed latest TWRP (3.3.0-0) and 19.3 Magisk, then latest canary. Nothing helps.
Did you manage to find solution? I would appreciate any help.

ismael47 said:
[/IMG]
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.
Click to expand...
Click to collapse
Dude that does seem to work at least for the magisk install. It doesnt help fix other issues like adaway and titanium backup from not being able to mount system though!
Appreciate your effort anyway

There's a setting in magisk that'll allow you to install adaway. Systemless hosts...tap it then reboot and adaway should install.
That worked for me.

I was able to get /system to mount by going to Advanced Wipe and selecting 'system' and choosing repair -> Change File System - EXT2 then go back and switch it back to EXT4.
I have not been able to get /vendor mounted and I believe it is because the syntax used has changed.
I read that AOS10 uses a form of EXT4 that preserves it as ready only, possibly by filling the used space of the drive preventing any writing.
This explains some of the new obstacles TWRP must compensate for in order to maintain compatibility w/ AOS10
https://source.android.com/devices/architecture/kernel/mounting-partitions-early
I have had luck installing Magisk by enabling USB Debug and typing in ADB shell:
cat /dev/block/sda19 > /sdcard/boot.img
Open Magisk and chose to install to file and select the boot.img.
Replace boot.img in the zip file that contains Android 10 factory firmware.
Current Marlin factory firmware [ https://dl.google.com/dl/android/aosp/marlin-qp1a.191005.007.a1-factory-c27241e0.zip ]
Inside marlin-qp1a.191005.007.a1-factory-c27241e0.zip is another archive: image-marlin-qp1a.191005.007.a1.zip ; inside this archive is boot.img.
Using 7zip you can open this archive and drag / drop boot.img replacing the stock image with the Magisk patched one.
Run Flash-all.bat, note it *WILL Wipe* your device but include a Magisk patched boot.img.
Once you finish initial setup of phone, download magisk manager and when you open it, it will automatically patch and reboot your phone enabling root. (make sure you have internet connection before opening magisk manager)
After you have root enabled phone you can customize /system to your liking and then cat /dev/block/sda33 > /sdcard/system.img to replace the firmware version.
(Still am not able to load /system as RW using FX, so have yet to be able to modify .props)
You can locate the various links and identify if you are using slot a/b by typing in TWRP terminal : ls -la /dev/block/by-name/
Side note:
The wizard himself has delicate and important matters of being a present father and managing the obstacles of keeping the brood happy-content and also providing nurturing support to the new addition and persistent validation for the wifey. [Congrats])
(apologies for improper formatting de-pretyfied by inotoxication)

Question How to install gapps after installing GSI rom?

I have installed Lineage 18.1 GSI and trying to install gapps. I have rooted and using franko to flash opengapps pico and get an error 70 that there is not enough space on /system. What is the way to get this done? Thanks in advance!

I would like to know that as well.
Tried to flash via stock recovery but that aborted because signature verification failed.
Apps like Flashify, Flash Gordon, Flashfire or Rashr didn't work either.
With MagiskGapps-basic-module from wacko1805 the playservice framework always crashed.
I think the easiest and best way would be to flash opengapps via TWRP.
@ada12 seems to have a TWRP build that still has some bugs, but can be used to flash unsigned zip files.
Maybe he can share this with us.

I feel like this should not be a collasal effort, but it has become one. I have spent the whole day trying to figure it out. I want to use Lineage OS 18.1 with gapps from Andyyan, not any other rom.

psychofaktory said:
I think the easiest and best way would be to flash opengapps via TWRP.
Click to expand...
Click to collapse
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.

Thanks @wirespot
The hint with the linked script to create a custom Magisk module on the preferred OpenGapps bundle was worth gold!

Now I have another problem that comes from installing the OpenGapps via Magisk.
For passing SafetyNet I have to add com.google.android.gms and com.google.android.gms.unstable to the deny list.
But when restarting Magisk all modules are reloaded. So also the OpenGapps module.
As a result, the adjustments to the deny list for the Google Play services are discarded again with every restart and the SafetyNet check fails.
How can I prevent that the two entries are no longer removed from the deny list?
Or how can I ensure that the entries are automatically added to the deny list on restart?
Edit:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?

wirespot said:
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Click to expand...
Click to collapse
Yes, but there is an issue with litegapps, the google contacts sync is broken unfortunately...

psychofaktory said:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
Click to expand...
Click to collapse
The deny list only lets you pass Basic check. To also pass CTS you need the USNF module (Universal SafetyNet Fix) and possibly other modules too. More details in this thread (check the end of the post), but try with just deny list and USNF first.

Neither the basic integrity check, nor cts profile match are passed.
Besides the denial list, I tried the modules "Shamiko", "Universal SafetyNet Fix" and "MagiskHide Props Config".
With the latter I have also tried various combinations, unfortunately unsuccessful in each case.
It looks like the deny-list does not work.
I suspect here also a connection with the message together that Magisk displays with each call:
Code:
An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
I have already been able to disable Phh-su with these commands:
Code:
adb shell
phh-su
mount -o remount,rw /
mount -o remount,rw /system
remount
mount -o remount,rw /
mount -o remount,rw /system
/system/bin/phh-securize.sh system.img
But the message in Magisk still appears.

Yeah passing SafetyNet with a custom ROM may be tricky. Didgeridoohan has a few more tips on their website you can try.

OK, I am already a big step closer to the solution.
After installing Magisk regularly, I first installed the Franco Kernel Manager.
Through this I was then able to flash UnSu.zip, which completely removed phh-su.
This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.
Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.
YASNAC now already showed "Basic integrity -> Pass".
But now I have not found a way to pass the CTS-profile match.
Does anyone here know what settings to set via MagiskHideProps Config?
And could someone send me the fingerprint of the stock rom (62.0.A.9.11)?
Code:
getprop ro.build.fingerprint

After some tests I discovered a big disadvantage with the variant to flash OpenGapps via Magisk.
Push notifications do not seem to work.
I use too many services that rely on Google Push notifications, so I can't do without them.
Compared to the "normal" variant of flashing OpenGapps via recovery before the first boot, the Magisk variant seems to be missing important dependencies and permissions that are only set during the first boot of the rom.
Therefore, the only useful variant is to flash GApps via recovery.
I really hope that we will soon have the possibility to flash unsigned zip files here!

Another approach:
Opengapps-zip files cannot be flashed via the stock recovery because it fails signature verfication.
The GSI roms can be flashed via the stock recovery. So they seem to be signed correctly.
Would it be possible to sign the Opengapps-Zip files with the same signature keys as the GSI-Roms to be able to flash them via the stock recovery?

Aren't GSI ROMs flashed through fastboot? Since they're partition images not zip installers like OpenGapps.

Of course. You are right.

Would it be possible to merge a GAPPS zip file into a GSI image and then flash the image with fastboot?