Related
Q&A for [Kernel][23/10/14][D850]Rin Kernel 1.6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Kernel][23/10/14][D850]Rin Kernel 1.6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i tried this method I. my att g3
Tectas said:
RIN Kernel for D850
Close to stock with some sugar added ... delicous!
Hey guys and girls,
you may have seen my unified stock kernel thread already (or may not, but doesn't matter). This kernel is my attempt to build up on the fixed source and add some additional features for us mod lovers to thinker with and to personalize your device to your usage. For now, I'll keep it close to my stock source and just pull some additional features and fixes in, but not to much. That may change in the future (maybe even soon), but for now, I'll stick to that paradigm.
First of, DISCLAIMER, I'm not responsible for bricked devices, dead unicorns, rainbows with missing colors, world war, nose bleed, void warranty (you know that already, don't you? your warranty is void now and it's your fault ) or any other harm happening to your device, you or people around you!
What does it serve?
Built with linaro 4.9.1 cortex-a15 optimized toolchain
IO Schedulers
BFQ
CFQ
DEADLINE
FIFO
FIOPS
NOOP
ROW
SIO
TRIPNDROID
VR (default)
ZEN
Governors
Adaptive
Conservative
DanceDance
IntelliActive
IntelliDemand
Interactive (default)
Lagfree
Lionheart
OnDemand
Performance
Powersave
SmartassV2
Userspace
Wheatley
Smartmax
Voltage control
SoundControl
Intelli-Thermal v2
Many under the hood fixes
Stability
More to come
How to apply it?
IMPORTANT: Read through all the requirements, steps and warnings before you do anything, if any requirement doesn't match or you don't know what one or more of the steps below mean or do, ask before you do any of them, if you don't know how all the steps can be done, let it be and wait for the bootloader unlock, I warned you, if you don't do and something bad happens, I'll just laugh at you!!
Requirements? Yes!
D855/P/K, F400/K/S/L, D850
Root
How to use the command line
PC
working fastboot
working adb
How to boot the kernel?
Plugin your device to the PC
Open a terminal and execute
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/stock-laf.img # backup the stock download mode to your external sd
exit # exit the superuser shell
exit # exit the adb shell
adb pull /storage/external_SD/stock-laf.img . # backup the download mode image from you external sd to the PC
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf # remove the stock download mode
BEWARE, THIS WILL REMOVE YOUR DOWNLOAD MODE!!! YOU WON'T BE ABLE TO FLASH KDZ FILES BEFORE YOU RESTORED IT!!!!
Turn off the device completely, plug in the USB-cable, if you pulled it out and start the device by holding vol up + power till you see some white text on the screen, fastboot should be written somewhere on the screen, afterwards execute the following command on the PC (while in the directory you've downloaded the kernel image to).
D850:
Code:
fastboot boot D850-rin-1.6.img # boot the kernel
BEWARE, NEVER USE FLASH AT FASTBOOT ONLY BOOT, IT WILL TRIGGER SECURITY OF THE LOCKED BOOTLOADER AND YOU WON'T BE ABLE TO BOOT ANYMORE!!!!
You're done now and booted to the custom kernel!
How to make sure you're running the kernel?
To check if you properly booted into the kernel execute this in the command line (terminal emulater or through adb shell):
Code:
cat /proc/version
it should show
Code:
Linux version 3.4.0-rin-g58903a9-dirty ([email protected]) (gcc version 4.9.1 20140710 (prerelease) (crosstool-NG linaro-1.13.1+bzr2673 - Linaro GCC 2014.07 - Cortex-A15) ) #53 SMP PREEMPT Thu Aug 14 13:26:42 CEST 2014
Once more a warning READ IT!!:
BEWARE, when you reboot you'll boot to the stock kernel, you'll have to boot the custom kernel over fastboot every time, when you boot normally, you'll be on the stock kernel, this won't lead to issues, but you'll miss the benefits of this kernel, I know that's not optimal, but the best we can get with the locked bootloader.
How to restore Download mode?
Code:
adb shell # open a shell over adb
su # change to superuser
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf # restore the stock download mode from the backup on your external sd
Changes?
23.10.2014/1.6
D850 support added
Simple GPU Algorithm Support
Overclocking up to 2.76 Ghz
exfat support
intelli-thermal v2 added
smartmax governor added
memutil optimizations
build with NEON kernel mode
2-way call recording patch
DriveDroid cdrom emulation support
Faux SoundControl
Simple-OnDemand fixed
Cpu Freq Limiter
some small fixes and enhancements
14.08.2014/1.0.1
net/ipv4|include/asm-generic: Enhancement of out of bounds fix
14.08.2014
Initial release
Full list of commits can be found here
Where to get it from?
D850-rin-1.6.img: AndroidFileHost | xda | dev host
md5sum: cd843592764abee8cb03dc701612832e
Show me the so(u)rce(ry)!
https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-kitkat
Donators (huge thanks, you're simply great )
@Toneman07
@Helloworld294
@shaarky
Credits
XDA
Google
LG
@HolyAngel
@faux123
@KAsp3rd
myfluxi
If you like my work, please show your appreciation by pressing the thanks button, if you want to do more, i've nothing against a little donation, but I'm as happy when you just thank me by pressing the button
XDA:DevDB Information
Rin Kernel, Kernel for the AT&T LG G3
Contributors
Tectas
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2014-10-23
Created 2014-10-24
Last Updated 2014-10-24
Click to expand...
Click to collapse
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
kpparry0156 said:
phone and on the fastboot screen out it says that the file was to large... What does that mean and where did I go wrong
Click to expand...
Click to collapse
Please don't quote whole OPs...
Are you sure you took the right file? Just from saying "that's the procedure I've used" I can't tell, sorry, if that's exactly how you've done it, it has to work, as for anybody else, if you did something slightly different, you need to tell.
guyd said:
Was wondering if you will bump the kernel now that their site is live?
http://apps.codefi.re/bump/
Click to expand...
Click to collapse
Jup, coming today
bump kernel?
It's coming out today.. So I can bump a custom kernel or the rin 1.6 kernel for the d850 correct
kernel
Nice
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Sinterion said:
Have you tried using any other toolchain? I came from arrrghhh's anykernel, which was built on SaberMod, which was very snappy as compared to Linaro in my testing.
Sent from my LG-D850
Click to expand...
Click to collapse
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Tectas said:
Yes, tried sabermod already, it's just even stricter than linaro at compiling, have to change a bit stuff, to be able to compile with it, but it's already on the schedule.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Cool! Well if you need a tester for the D850, just shoot a PM my way!
Sent from my LG-D850
Curious why some devices get the green screen and some don't. I installed cloudy, then tried installing the kernel zip and same thing. Let me know if you want me to test anything if you get to a point and need someone that's getting the green screen, I'll be more than happy to help
Kernel Version Info
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
What is the most efficient or favorite setup for Kernal
Thanks for getting a flashable zip file out! I was waiting for this because I didn't want to risk messing something up with the original installation method. From what I have read, people really like the kernel. I'm DLing it now!
OP. Any plans to make custom kernel's for AOSP Roms?
Sent from my LG-D850 using XDA Free mobile app
animator776 said:
When I go to "Kernel Version" under "Software Information" it shows the Kernel Version as 3.4.0
Is this normal? Or is it supposed to say "Rin Kernel 1.7.1"?
Click to expand...
Click to collapse
Yes, that's normal. Has something to do with the Linux version.
guyd said:
Yes, that's normal. Has something to do with the Linux version.
Click to expand...
Click to collapse
Ok, thanks. I was wondering because I've flashed kernels in the past that display a custom kernel version i.e. "Dorimanx"
I believe the kernel version that is displayed can be changed in the build.prop
Anyone care to post their stable settings for this kernel? I remember a similar thread for the S4 which really helped guys like me who aren't real familiar with all of the different kernel tune-ables.
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
JediSooner said:
I've searched the dev thread and this one but didn't see any reports about icon themes reseting after reboot. I finally flashed this kernel tonight and each time I've rebooted after tweaking cpu freqs, the icon theme I'd applied using Nova Launcher reverts back to default icons. I've been on stock kernel since July and this has only happened since flashing this kernel a few hours ago. Any ideas?
Click to expand...
Click to collapse
I'm using Nova with some alternate icons without issue. Don't know what to tell you except it's working fine for me.
Problem solved and it wasn't anything kernel related. I forgot that I was playing with moving apps to SD the other day and moved all of my icon packs. Apparently, regardless of the launcher being used, it will load before the SD card initializes, so the icon packs aren't found. I've moved then back to the phone and all is well. Google is definitely my friend.
Good day, Im looking for a kernel with permissive selinux that works with a P900 device running lollipop. Have been reading in the forums but seems like there arent any kernels working at 100% right now so was wondering if any of you could point me in the correct direction.
Trying to run Linux complete installer right now on my device but it doesnt work because of the selinux mode, thanks a lot.
I have the Lollipop ROM from @civato installed (see http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589) and can confirm I have permissive mode for SELinux : infact I have this with Ubuntu running on my P900 but I used Linux Deploy rather than Linux Complete Installer.
The kernel is also available separately (check the author's signature for links).
Good luck.
Thanks a lot friend
Hi, bothering again I installed this kernel separately but in the op says that selinux permissive is set to no.. How would I change it to permissive? Tried with selinux mode changer and didnt work thanks a lot
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
gil80 said:
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
Click to expand...
Click to collapse
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Renosh said:
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Click to expand...
Click to collapse
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
gil80 said:
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
Click to expand...
Click to collapse
Zero changes to the mixer_path.xml
Completely stock except for root, removing ModioFX from system and using a different hosts file (Adaway) and installing V4A.
I haven't had a single issue with calls via speaker phone or handset for the past couple of days on current ROM. I've used a similar set up for months in various ROMs and never noticed or received reports of issues either
can you please see if you can find your 50viper.sh file under system/su.d and post it?
Thanks!
{
"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"
}
I know that there is many tools apps etc to disable or hide SU.
I decide to make this just because those did't work on my device back in 2016 and or CyanogenMod/LineageOS ROM that I use, so I assume this happens to other in CyanogenMod/LineageOS users too, I start this thread and made this app that can help to pass a safety net test on any rooted device (hide SU only when using Lineage add on SU) as it is no longer just a SU hider app is little more.
This is only to CyanogenMod/LineageOS SU binary aka CM-SU, the CM-SU only works with CyanogenMod/LineageOS ROM's and ROM that use they source code as base
That can be Download from Lineageos download page click here to see
No it doesn't work with SUPERSU or any other SU that is not base on CM-SU
No it doesn't support Xposed Hide, if you use Xposed you can't pass safety net with CM-SU.
No it doesn't support AB devices (devices with two system partition) that can't be mounted as rw dynamically in android.
What is iSu?
A simple app to help the user to pass safety net test on CyanogenMod/LineageOS or any CyanogenMod/LineageOS base ROM's.
I personally test this on Marshmallow and Nougat CM base ROM's it works 100%, it also Supports Lollipop but Kit Kat and older OS's are not supported.
How To use it?
read Installation instructions, download Folder with instructions on the bottom of the post
Download and Install the app as a normal app, if you wanna the full app support, use a ROM with the supported SU version (CM-SU), download Folder with instructions on the bottom of the post
if on Marshmallow or Lollipop flash the zip (iSu_kernel_Reboot_Support), download Folder with instructions on the bottom of the post
Learn how to use the app, below instructions
How To pass safety net?
Su deactivated (demanding)
SELinux enforced (demanding)
Android debugging deactivated (not demanding for all devices)
Props known props or special props can't have a red warning (demanding)
Below are some samples of fails or pass:
PASS
*Android debugging only affects some devices, disable if you don't need it.
*In props if there is props with a red warning that may be the reason of the fail if SU and SELinux is set as the above.
If you have SU active you will always fail
FAIL everything
*Fail because SU is Activated
If you have SU deactivate you will not always pass
FAIL everything 2
*Fail because SELinux is in Permissive
If you have SU and SELinux on a correct position you may not always PASS, because some props cause fail of ctsProfile
FAIL ctsProfile
*The above fail because ro.boot.verifiedbootstate
*Some props may or may not cause full FAILS or a FAIL of ctsProfile
Detailed app function description?
The app is divided in 5 tabs (Checks, Controls, Monitor, Props and settings), plus widgets and tiles, bellow a detailed description:
Checks
Basic information about the application, the main start tab if it show a red warning on the SU state options because yours current SU is not supported and the app will work with limited functionality.
SU State, current user SU version and reboot support status
Update, Check for iSu updates
Safety Net test, Let the user try the safety net status, in case of fail it will tell what fail and current SU, SELinux and ADB state as those if on wrong position will cause the fail
Log, Generate a full logs of information about the device and how the app is running, in case of a problem share the log.zip on the thread and explain the problem
Controls
The main control tab, be aware there is extras actions for this controllers in settings tab
SU, Changes and show SU state. This function only works with CM-SU
SELinux, Changes and show SELinux state, plus allow user to fake enforce Selinux for devices that have problems when running with SELinux enforced
Android debugging, Changes and show Android debugging state
Tasker, Info about how to control the app using Tasker
Monitor
This tab only works with CM-SU
A Service to monitor when foreground app starts then, activate or deactivate SU and SELinux or ADB (base on settings options).
App monitor, Status and access to accessibility service.
Don't Care List, Select the apps that will not have effect to App monitor, when a foreground app start.
Deactivate SU, Select the apps that will deactivate SU when started
Automatic Re-Activate SU, If this switch is on, will automatic active SU when leave the app that deactivated SU
Activated SU, Select the apps that will activate SU when started
Automatic Re-Deactivate SU, If this switch is on, will automatic deactivate SU when leave the app that activated SU
Props
A tab to change the value of any ro.prop or read only prop, using the resetprop applets from magisk to make a tool to modify on the go any ro.prop, there is also a list of known props that can cause safety net fail they safe or unsafe value
Read Only editor, List of ro props and the ro props changed by the user
Special Props, Known props that has a complicated value that can't be define as OK or NOK
Known props list, just explanation about safe, unsafe or unknow values
Force set all Known props, Click to force all Known Props to the chosen value
Known props, the real list of known props and they current value click to change
Settings
Basic application setting, extra controls and notifications
Application, Allow to force language to English
SU, Extra SU options allow to deactivate it on boot This function only works with CM-SU
App monitor, Allow delays to app monitor This function only works with CM-SU
Props, Allow to apply props changes on boot
Notifications, Enable disable notifications or toast's of SU state This function only works with CM-SU
SELinux, Extra control of SELinux state base on SU is state changes This function only works with CM-SU
Android debugging, Extra control of Android debugging state base on SU is state changes This function only works with CM-SU
Widgets and tiles
The app has widget and tiles that can be used to control the app Controls
Widgets They only work with CM-SU for SU changes
Mono Widget, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Dual Widget, Allow to change and read SU or SELinux state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Tiles Only visible on Nougat
SU tile, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
iSu tile, Click to open the app
Installation instructions:
Download Folder: Click Here
There is three files, description:
iSu_X_x.apk Install the apk as a normal app.
iSu_kernel_Reboot_Support_V_X_x_and_up.zip Flashable zip, flash only if you are running Marshmallow or Lollipop
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support , this files prevents from losing SU access after a reboot with SU deactivated.
Old reboot support, in case the current fail
Old reboot support download Folder: Click Here[/B]
iSu_kernel_Reboot_Support_V_X_x_and_up_Enforcing.zip Flashable zip, use only one zip, if running Marshmallow or older
iSu_kernel_Reboot_Support_V_X_x_and_up_Permissive.zip Flashable zip, use only one zip, if running Marshmallow or older
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support use only one(enforcing or permissive), this files prevents from losing SU access after a reboot with SU deactivated.
Use the one base on yours current Selinux status to check on your device look in settings > About a phone > SELinux Status if is enforcing or permissive, some CM ROM Run with selinux in Permissive so check yours.
Be aware!!
Updating CM/Los nightly or any ROM update of any CM/Los base ROM will remove the changes made by the zip, so is need to re-flash those .zip after any ROM update, may be need to do it also with some custom kernel from developer that use a boot.img to share the kernel(check yours kernel zip content to know).
If you forget to flash the .zip in a update and have lost ROOT don't worry just go back to recovery and flash it after the reboot all will be good.
The below are obsolete after V3.6 of the app, see old_version folder in main download folder for those files just reference no longer supported
iSu_kernel_cmdline_Patch_V_X_x_and_up.zip
The kernel_cmdline is only need to some devices that after deactivating SU with the app still can't pass the safety check, Google is using kernel and bootloader arguments to determined that the user modify the stock SW(AKA is using custom ROM) and prevent from passing as "safe", this add extra safe arguments to cmline and help to achieve the pass current it only support some device (Nexus and Motorola, maybe other post on the thread device/vendor if the zip help you)
iSu_kernel_defaultprop_Patch_V_X_x_and_up.zip
This is only for those that have apps that use rootbeer SU detection...
explain in this post (Click here).
After flashing defaultprop_Patch zip the user will no longer have access to the option in Settings > Developer options > Root access
But that is not a problem as the same zip will enable root by default so you can use without changing that option.
XDA:DevDB Information
iSu, App for all CyanogenMod/LineageOS devices (see above for details)
Developer donation link:
To donate via paypal click here
No other donation option is available.
Contributors
All Contributors can be see in github click here
fgl27, I use osm0sis Anykernel2 for the kernel zip
App Source Code: https://github.com/fgl27/isu
Extra App credits: iSu readme credits
Version Information
Status: Stable
Current Stable Version: Check latest version in Download folder
Changelog
Created 2016-Oct-03
Last Updated Check latest version
Changelog
Last app version Click to Download
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
blastagator said:
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
Click to expand...
Click to collapse
Thanks. For me was similar, magisk did not support my device so user complain to me about support as I did not manage to make magisk to work on my device I manage to make this that seems to be 100% for the most none rooted app.
regards the RW/RO
Theoretically yes but things was a little odd when I first start test for this... for simple reason if we don't mount system as RW we can "hide" or "un-hide" SU because is need to move it and system boot in RO, and if leave it mounted as RW safety net check will not be successful even if SU is hide, but after some safety net update on the google side mount it as RO at the end was not working in the .sh and the unmout was, maybe was some other related problem but it work so I did not change...
So I keep the unmount did not test any more after, and in the java code every time the switch is use it start with RW and ends with RO and that does the trick...
I have update the reboot support and the app for Nougat, Selinux is a little more restricted on N and I did not had the time to test a universal .zip to support N as the changes I did in the ROM I build are a little more time demanding to make it right, or not I really only have my build to test on my devices as N is just starting there is no other ROM, I really need another ROM that doesn't have any of my changes to test and really make it fully work with a simple .zip
But every things is also fully working on N CM did not change the SU binary, safety net, pokemon and payment app are all good, at least for know...
:good:
I update the project for N but I only manage to fully test on my ROM so if any one try and have problem read #3 post and report on the thread.
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
Shadow646 said:
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Click to expand...
Click to collapse
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
mrkhigh said:
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
Click to expand...
Click to collapse
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Edit
Shadow646 said:
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Click to expand...
Click to collapse
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
I update the app and kernel support to 1.5
Changelog and Download link first page post 2 and 3
In Downloads I add two kernel support one with selinux after boot in Permissive and other with Enforcing just check the zip name and check your device in settings > About a phone SELinux Status is using enforcing or permissive, this is need as some CM ROM Run with selinux in Permissive.
Any problem let me know.
bhb27 said:
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
Click to expand...
Click to collapse
Well, now I reinstalled all just because I messed all up, again.
Turned off the phone with root of and no kernel support, tried to flash kernel support, and that would be ok, if I didn't "flash SuperSu" stuff when rebooting :silly:. That made the switch work, but didn't pass validation when using PoGO.
Then, had to reflash ROM, delete chinese stuff, reinstall all of my apps, and iSu, of course, while noticing that there was an update; installed the app and new permissive kernel, and from now, so far so good
Hope that I will keep it clean and working. Thanks for the suggestions btw
@bhb27 Installed and working on sprint htc m8 cm13. The kernel mod is installed but untested.
Great work! I can confirm it worked in my moto g 2014 running cyanogenmod 14.1 official. Pokémon go worked!
Thanks dev!
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
HC4Life said:
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
Click to expand...
Click to collapse
Now go find that ditto.
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
LJAM96 said:
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
Click to expand...
Click to collapse
:good:
No there isn't yet, is not all that hard to make but is timing I had no time for the last week to start the implementation, but is in my plans, probably still do this year.
BTW is always nice to be remember that the app can be used for other then to catch monsters :laugh:
You might want to consider removing selinux enforce from the kernel service script. If the ROM doesn't have proper SE policy, it could gum things up. I think the switch in the app is probably sufficient in the event user needs to toggle Enforcing to run an app. I don't believe enforcing on boot toggles anything, but I could be wrong since my ROM boots enforcing. Safety Net actually keeps working for me if I toggle to permissive.
Hello,
can anybody help me for my Problem with my Galaxy S4 GT-I9506
i have do the following
1. TWRP install the actual version
2. flash lineage-16.0-20190609-UNOFFICIAL-ks01ltexx https://forum.xda-developers.com/galaxy-s4/i9506-develop/rom-lineageos-16-0-unofficial-galaxy-s4-t3848597
3. flash open_gapps-arm-9.0-pico-20190612 TWRP
4. flash Magisk-v19.3 mit TWRP
But i have problems with them
https://prntscr.com/o7onem
https://prntscr.com/o7oneu
https://prntscr.com/o7oner
i have no idea what i can do can anybody help me please?
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
I had a look at the device tree and I can see a couple of things for your dev @kyasu to possibly add
- we had safetynet start failing a few weeks back on i9505 and these were the fixes I found
- Product_name - Samsung never released a product called full_ks01ltexx - will need to be set to correct product that google recognises by a build_prop_override ("GT-I9506" or similar).
- Change build fingerprints to pixel3 versions.
- hide permissive with init script.
these 2 commits here show what needs done:
https://github.com/JDCTeam/android_...mmit/ea27cf29e4084d860fb8549be2e3cdb1599a6d08
https://github.com/PixelExperience-...mmit/045dc32219172a288c10f503478deb3eb3b2aee5
andrew2432 said:
Does the ROM come rooted? It may have system root inside still, my s5 ROMs always did I think. I always had to use adb shell or flash a zip inside twrp. Usually did both.
Search XDA for osm0sis tool called unsu, it should be a .zip. Flash in twrp after installing gapps and booting once. This should clear system root, and allow you to pass once magisk is installed.
The other issue I can think of is maybe signature verification or something with the playstore. I don't remember what it is, my phones and ROMs have always worked after magisk. If the above steps don't work maybe that's related. We will have to look around if that's the case
Click to expand...
Click to collapse
is this tool correct? https://forum.xda-developers.com/showpost.php?p=63615067
is the rom correct what i use?
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
tuvok1981de said:
OK i have unSu the device and have reinstall Magisk ..
https://prnt.sc/o929eu
but i have the same problem
Click to expand...
Click to collapse
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Buff99 said:
- have you tried changing fingerprint with Magiskhide?
- has it worked previously and just recently stopped working or is this your first attempt?
- do other users on the same ROM have similar results?
I incidentally also checked DT if the ROM is rooted and doesn't look like it. Kernel also has namespace commits too, so it's not that.
Click to expand...
Click to collapse
- yes i have make with MagiskHidePropsConf-v.4.0.3 and terminal props S4 and S4 Active variante but it will not do this
- it will not work all the time where i have flash my S4
- i have no idea iam not the developer from the rom iam only a User
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
Point 1. is on the Phone
ähm where must i make Point 6 ?
andrew2432 said:
1. Flash twrp
2. Full wipe, system data internal
3. Flash ROM, boot
4. Flash gapps, boot
5. Flash magisk, should pass
6. If not, change selinux to enforcing
Let us know?
Click to expand...
Click to collapse
OK i have make flash new all 5 Points
but ctsProfile: false / basicIntegrity: false on Magisk Manager
tuvok1981de said:
-
- i have no idea iam not the developer from the rom iam only a User
Click to expand...
Click to collapse
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Buff99 said:
Yeah, well this is a developer forum. There is a thread for the ROM you use. It is assumed you have already seeked advice there from other users of the same rom...?
Being aware of whether others have this working or not shows whether you are wasting your time or not.
Click to expand...
Click to collapse
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
tuvok1981de said:
in this forum say the users i must go in the Samsung S4 Forum and ask my Question!
Click to expand...
Click to collapse
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
stecko said:
Can you guide me how to switch selinux to enforcing?
Click to expand...
Click to collapse
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
andrew2432 said:
I searched safety net inside the ROM forum, it said to change selinux to enforcing. I am not sure how. Maybe with a magisk module
Edit: credit for these instructions goes to @DiamondJohn
The user only installed magisk and safety net passed. Are you installing xposed or anything?
in a terminal, or part of a boot script
Code:
su;
setenforce 1;
or you could try the app I built, where you will find it under the menu
Code:
Current State>SELinux>Set SELinux Enforcing.
https://forum.xda-developers.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260
Click to expand...
Click to collapse
Very Nice .. this part have help ..
Code:
su;
setenforce 1;
https://prnt.sc/o9gchi
thank you!