Related
USE WITH CAUTION!
I not fully tested yet...so do a NANDROID Backup before modding anything!
1) GUIDE for Manual Installation
-Download Files Pack: HERE
-Extract files on phone and put they in the various directory like in the .rar:
Code:
[B]/system/...[/B]
-Open /system/build.prop with a text editor (like RootExplorer)
and add these lines at the end:
Code:
#Additional Tweaks by XxXPachaXxX
#Xloud Engine Service
nro.semc.sound_effects_enabled=true
nro.semc.xloud.supported=true
npersist.service.xloud.enable=1
-Then, Save the file and Exit
-Now, set the right permissions or open a terminal emulator and execute:
Code:
su
busybox chmod 0771 /system/framework/semc_audioeffectif.jar
busybox chown 1000.1000 /system/framework/semc_audioeffectif.jar
-Fully Reboot the device and enjoy
How To ROLLBACK to stock:
- DELETE ALL files, LISTED in FilePack.rar
- Erase lines for xLoud in Build.prop
- Put libaudioeffect_jni.so from your ROM to /system/lib/ (set permissions rw-r--r--)
- Full Reboot
DOWNLOADS:::INFO:::SUPPORT
Good work
great job thanks
nice. posted the hack at galaxy note forums, credits to you.
REPORT HERE TESTS and ISSUES
Youve missed the 1 at the end of enable= on the last line
I will have a try
thx
Does this work on AOSP ROMs?
giving it a try .. will give my verdict later
In build.prop i see required string, and sound seems much louder, but no quality...Any chance make Beats Profile for all sounds on device??
Apparently it screws your speakers....
http://forum.xda-developers.com/showpost.php?p=20067773&postcount=1
http://forum.xda-developers.com/showthread.php?t=1271446
Cheers for the warning...I was seconds away from installing it!!
Need rollback zip (back to stock).....ARHD 6.3.1
Or erasing lines in build.prop resolves problem>????
I have also lyapota audio runny on: can I flash this one also?
Thanks all for replies...
diegocapassi said:
I have also lyapota audio runny on: can I flash this one also?
Thanks all for replies...
Click to expand...
Click to collapse
Please read the thread!, IT DAMAGES YOUR SPEAKERS I think this should be closed, unless someone improves it and stops it from damaging the speakers
My volume with CM 7.1 is unbelievably low. I can't imagine this Audio Hack could damage my speakers even if it tripled the volume of the speakers (that would just probably take it back to the volume levels I had with Sense).
i installed it and it makes it a lot louder and i think it will kill the speakers
the only why to go back is Nandroid backup?
MaorHassan said:
i installed it and it makes it a lot louder and i think it will kill the speakers
the only why to go back is Nandroid backup?
Click to expand...
Click to collapse
unfortunately yes !
To get back:
- DELETE ALL files, LISTED in FilePack.rar
- Erase lines for xLoud in Build.prop
- Put libaudioeffect_jni.so from your ROM to /system/lib/ (set permissions rw-r--r--)
- Full Reboot
Already done on ARHD using Root Explorer. Stock sound returned
TAGTRAUM said:
To get back, DELETE ALL files, LISTED in FilePack.rar, and erase lines in Build.prop, already done on ARHD using Root Explorer. Stock sound returned...Don't forget reboot after deleting
Click to expand...
Click to collapse
Is impossible, the file libaudioeffect_jni.so is overwritten !!
The only way is to restore...
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!
C A O S [UNOFFICIAL]
Your warranty is now void!
We're not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you
CAOS (Custom AOSP OS) is a project which based on phhuson's Treble GSI AOSP 11. CAOS is a modified AOSP by eretemin which I modified to be compatible with Huawei hi6250 phones. I also provided several patches
Changelog :
CAOS 316 March 2022 version
March 2022 SPL
CAOS 315+ Febrary 2022 version
Febrary 2022 SPL
CAOS 315 January 2022 version
January 2022 SPL
Fix all storage/permission in social apps like instagram, messenger.
implemented Huawei IMS patches
added Seedvault app and option in Treble app for activating it
full fixes access for media files from some apps like WhatsApp or Telegram
backported changes from v400h device_phh_treble: All devices support unprocessed audio source
patch for gsicharger removed, should fix offline charger animation for some devices (need test)
volume dialog UI now follows rounded corners
added CAOS logo image
CAOS 314 December 2021 version
Initial build
Decembre 2021 SPL
Integrate NFC, Miracast/cast , Live Display patches
Add media patch (Fix "Error loading media" in social apps like instagram, messenger..)
Pre-requisite :
You must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! ).
Installation :
Download this file caos-v316-220321-arm64-iceows-huawei.7z:
go to TWRP
flash this file Huawei-Decrypt-Emui_8.zip to change mount data partition (disable FBE : FileBaseEncryption)
format data
reboot to TWRP again
do a full wipe (system, data, cache, dalvik/art cache) !
reboot to bootloader
extract the img from caos-v316-220321-arm64-iceows-huawei.7z
run: fastboot flash system <drag system.img here>
reboot to TWRP
resize system
(optional) flash patches :
1 - Google Apps lite : [RECOVERY]LiteGapps_arm64_11.0_v2.6_official.zip
2 - Enable AGPS : 7-AGPS-FIX-AltairVendor-v3.6-signed.zip
3 - If you are on EMUI 8.0.0.408 or sup : 8-Huawei-PRA-FixPreav-A-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most
reboot to System
(optional) install GCamGo (GoogleCamera_2.12.413042791.apk)
Enjoy !!!
Not Working :
Nothing
ROM OS Version: Android 11
ROM Kernel: Linux 4.4.x (stock 4.4.26 or Siberia_4.4.302-1.1.zip)
ROM Firmware Required: EMUI 8.0.0.360 ---> 8.0.0.402
Based On: Caos (eremitein)
Credits:
eremitein
And all the others who tested my patches and helped me improve this ROM
CAOS11 Project
GSI Treble patches. Included Phh, Andy Yan and my personal Treble works. You can using patches/solutions from here and from linked manifests (all or few my own) in none-commercial usage only and yo...
github.com
Support Group
reserved
Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?
Hykosit said:
Is there any specificity to this ROM ? I mean, compared to Lir and LeaOS you posted recently, or DotOS which is more about performance ?
Click to expand...
Click to collapse
CAOS , LiR, DotOS, crDRom etc. are AOSP GSI ROMs based on 'phhusson' sources, so the difference in performance, battery life, etc. is minimal. And all have some common bugs- VoLTE, native call recording, offline charging etc. If you like to take pictures, you will be disappointed with the camera...(btw, Footej camera 2-premium is a good enough replacement for gcam).
The main differences between these ROMs are in the customization options.
In my experience CAOS is faster, crDRom is customization monster, LiR is a perfect balance between battery efficiency, performance and the customization. As for DotOS, the previous version 5.1.3 was better.
hi Alf.
Indeed it is a good comparison of the different ROMs. For charging go to PHH trebble option and enable fastcharging to 4000ma. For the Volte it is in progress..., and for the camera I provide GCAM in addition
AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma.
Click to expand...
Click to collapse
-Alf- said:
offline charging
Click to expand...
Click to collapse
AltairFR said:
I provide GCAM
Click to expand...
Click to collapse
try Footej 2-premium and you'll see what I'm talking about...
Thanks you two ! That's good stuff to know
AltairFR said:
For charging go to PHH trebble option and enable fastcharging to 4000ma
Click to expand...
Click to collapse
But won't this one harm the battery ?
-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?
moriel5 said:
Disclaimer: I am a simple user, and am not affiliated with Semaphore or ZipoApps.
Recently, Footej Camera (or officially, Footej Camera 2) was bought by ZipoApps.
After seeing things like the buyouts of software like QuickPic or certain (legacy) parts of Nano Defender and the resulting consequences, naturally I was concerned with this, especially when ZipoApps's line of business is buying existing apps and monetizing them.
After some sleuthing, I managed to get the personal cellular number of ZipoApps's CEO, Alik Hochner (I am not going to divulge any more information about how and what was needed for this, to preserve his and other involved people's privacy), and I just spoke with him a few minutes ago.
While I am not completely reassured, due to not having experience with ZipoApps's history, he did strike me as someone who does want to be able to monetize apps while protecting user's privacy to the best of his abilities, though understandably limited by the tools the current market offers without being independent of the mass market.
Make of that what you will, I will continue to keep an eye on the matter, to see whether this turns out to be a turning point for such buyouts for the better or not.
Click to expand...
Click to collapse
from :
[Android 5.0+] Footej Camera 2 2021.5.6
Get it on Google Play A brand new, fascinating, user-friendly and robust camera app is here, ready to capture, orchestrate and give a new life to your best moments… *** If you have any problem or if you can't find manual controls, before give...
forum.xda-developers.com
Hykosit said:
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Yes, look here
-Alf- said:
try Footej 2-premium and you'll see what I'm talking about...
Click to expand...
Click to collapse
For my part I have no problem with offline charging. Can you describe the problem?
AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
I suppose it was a question for me.
I was wondering if changing initial charging values could be harmful to the longevity of the battery as those are (i think) calibrated for specific values
AltairFR said:
For my part I have no problem with offline charging. Can you describe the problem?
Click to expand...
Click to collapse
On A/B GSI doesn't work at all (Kirin-devices).
-Alf- said:
On A/B GSI doesn't work at all (Kirin-devices).
Click to expand...
Click to collapse
Ok
Hykosit said:
So I looked for this one, unfortunately the app was sell to an other company (ZipoApp), and seeing the recent opinions on google play the app was just monetized and the premium is now 10€ by damn week, and people fear for user privacy ... Smell like a bad story to me
Do you have any old apk, from before the acquisition ?
Click to expand...
Click to collapse
Here is install this apk, it is modified:
- cleaned resources,
- disable wakelock,
- disable loging and analitics,
- enable premium version
AltairFRGOOD work !!!
AltairFRHi Master. Please make ROM with all patches for a variety...
Nusantara_v3.2-11-arm64_avN-29082021-OFFICIAL-0849.img.xz
NusantaraROM - GSI
NusantaraProject ROM GSI (Generic system image ROM) For all devices with supported project treble.
www.pling.com
I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.
I don't have a solution but LiR build doesn't seem to have that problem. I could reboot many times on a hi3650 P9
huuhaa_tm said:
I have flashed this to Honor 8 frd-l19 (emui 8 device). Some problems have been tackled down now with help of dev, thanks to that. Apparently only things to do for now would be able to create misc folder at /data/misc and also credstore at /data/misc/credstore to be able to boot now.*1
Any ideas how to get those folders done? atm. I can access to phone via adb while phone stays at CAOS logo screen, maybe between 10-15mins.
I've tried to:
sudo adb root
adb remount rw, /data
which succees
then
sudo adb shell
cd data
mkdir misc
but get error
mkdir: '/data/misc': Read-only file system
I've also tried to install busybox at twrp*2, but using it via twrp terminal doesn't give su or sudo. When trying without su and just busybox mkdir /data/misc/ it seems to create one and I can even cd to it and create subfolder. After changing right permissions and using chown to those folders everytjing seems to be good. Sure twr doesn't show misc_ce and misc_de etc under data which were tegere when using adb.
Well no surprise that reboot habgs to CAOS logo and when xhecking via adb shell thete's no misc folder under data.
Can anyone give some tips how to be able to create those folders since I can't use adb via twrp or stock recovery. Also strange that when remounting /system as rw I can push & echo changes to there, but not able to create directories to /data after doing the same.
If someone can help, I will shere needed steps to get this running at Honor 8 frd, unless that will just revel next layer of problems.
*1 Device will boot to OS at first boot, won't boot after restart. So after logs there could b found reasons and now tried to fix those with help of dev and might be at the stage that to create folders just once again will be fix.
*2 I have found only 2 different twrp images, both at version 3.2.1-0 which are suitable for this device, others haven't work at all.
Click to expand...
Click to collapse
I have tried several roms on my honor 8 but It gets stuck with the logo ( Waiting for solutions