I need help on how to flash "Magisk" to Remix OS - Remix OS for PC

Read the title.
Flashfire can't seem to work.
Hope you can help me.

vinnce143 said:
Read the title.
Flashfire can't seem to work.
Hope you can help me.
Click to expand...
Click to collapse
Obviously you can't use flashfire as RemixOS doesn't have and can't exactly use a recovery.img
What would you need Magisk for? I did try a while ago to install it manually but that didn't work... I might try again as I know slight more about how it works; but can't really see the benefit of it on Remix.

benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.

trevorcobb said:
benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.
Click to expand...
Click to collapse
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet

HypoTurtle said:
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet
Click to expand...
Click to collapse
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.

trevorcobb said:
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.
Click to expand...
Click to collapse
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
Screenshot attached - using stock ro system (system.sfs). Essentially that would be the limit of ro system; I could add a magisk SU and have the magisk app claim proper root installed but all disabling root would do is revert back to the stock com.android.setting su
To use it properly I'd say you would need to unroot system:
boot with REMOUNT_RW=1
Install SuperSU and let it replace com.android.settings su
Unroot with SuperSU
Then probably optionally to convert system_dev.img to system.sfs to make it ro again
@trevorcobb the selinux might be an issue with SafetyNet - see if you can boot without that added to grub {gonna check on mine but doubt it'll boot}
My point about Pokemon Go is that there more/better apps than that if you don't play it properly with GPS; but I guess that's just the orienteer in me...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
UPDATE phh superuser added to magisk which has turned root off {blocks com.android.settings} - but can't seem to install phh's supersu apk; so stuck unrooted {ALT&F1 still has su but it uses phh's su now}. Will need to recheck with the x86 version.
UPDATE2 not going to get anywhere with phh due to the the superuser baked into settings; going with SuperSU should be fine - it just means another .img is needed.
UPDATE3 Having a bit more trouble with this. Tried Magisk; Magisk superSU [essentially just Systemless-SU] and Magisk xposed but can't get xposed to activate. Will try with Magisk, SuperSU and Systemless xposed - but don't know if there is actually any benefit here [would need an updated x86_64 xposed version for suhide to work]

HypoTurtle said:
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
Click to expand...
Click to collapse
holy chit! thanks so much!!

I am jumping in to follow along.....for the record I am using this solely to play Pokemon Go with my son.

I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .

youling257 said:
I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .
Click to expand...
Click to collapse
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
The issue is more with the xposed version. For this to be of any benefit over systemless, you`d need suhide to work, which needs v86.2 and we don`t have a version for x86_64, there is one for x86 so I`ll try and get around to making a x86 magisk.img I already have modified the installer script for it.

HypoTurtle said:
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
Click to expand...
Click to collapse
please see this screenshot,i use f2fs partition

trevorcobb said:
holy chit! thanks so much!!
Click to expand...
Click to collapse
youling257 said:
I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .
Click to expand...
Click to collapse
Mind doing a walk through for the less genisus in the group.

laserspeeddemon said:
Mind doing a walk through for the less genisus in the group.
Click to expand...
Click to collapse
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).

moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img

HypoTurtle said:
This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .

moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
HypoTurtle said:
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
First, I'm not annoyed, I was tickled.
Second you're both are wrong as I simply typo'ed "genius." When I said "less than genius" this was an adjective referring to a group of people using a noun. When applying a adjective-noun to a noun, the adjective-noun is singular.

youling257 said:
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .
Click to expand...
Click to collapse
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post

HypoTurtle said:
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post
Click to expand...
Click to collapse
I modified initrd.img and use su folder ,two month ago,July 22nd ;I first tried magisk link to su ,magisk v2,the first ten days of August .
these two month,I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ,your idea /su/xpo,I modifed rovo89 xposed x86 v86 app_process ; the x86_64 xposed,we only has MIUI x86_64 v85 June,we still use /su/xpo . I didn't know magisk too much,I didn't try magisk in September .
about xposed system less,why we need topjohnwu magisk method ? why we use his ?

youling257 said:
I modified initrd.img and use su folder ,two month ago,July 22nd ;I first tried magisk link to su ,magisk v2,the first ten days of August .
these two month,I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ,your idea /su/xpo,I modifed rovo89 xposed x86 v86 app_process ; the x86_64 xposed,we only has MIUI x86_64 v85 June,we still use /su/xpo . I didn't know magisk too much,I didn't try magisk in September .
about xposed system less,why we need topjohnwu magisk method ? why we use his ?
Click to expand...
Click to collapse
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.

HypoTurtle said:
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.
Click to expand...
Click to collapse
menuentry "6.0.1 (DEBUG mode)" {
set DIR=/6.0.1
search --set=root --file /32/kernel
linuxefi /32/kernel root=/dev/ram0 androidboot.hardware=android_x86 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 i915.enable_psr=0 DEBUG=2
initrdefi /initrd.img
}
menuentry "remixos 64" {
set DIR=/remixos
search --set=root --file /64/kernel
linuxefi /64/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0
initrdefi /initrd.img
}
menuentry "cm13 (DEBUG mode)" {
set DIR=/cm13
search --set=root --file /64/kernel
linuxefi /64/kernel root=/dev/ram0 androidboot.hardware=android_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 DEBUG=2
initrdefi /initrd.img
}
I use the same kernel、modules、initrd.img with 6.0、cm13、remixos ; kernel 、initrd.img on fat32/esp partition .
auto mount f2fs partition on /mnt , auto mount /mnt/modules ; /mnt/6.0.1 , /mnt/cm13 , /mnt/remixos, if ota,just update /mnt/remixos files

Related

Please help for changed SElinux to permissive

Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
ludogaut14 said:
Hi, I'm a beginner and I would like to know how to get SElinux in permissive on my SM-850F. I tried many things without success. Thank you for your help.
Click to expand...
Click to collapse
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
freaksamael said:
It shall be done via kernel re-compilation from sources, ramdisk tweak and build.prop entry. This is the only way till now. As I can tell, there's also a feature in "wanam exposed" - security but I don't think it will work (still in beta). So, watch for a "custom touchwiz kernel" in Android Development section....
EDIT: or flash Eudemony ROM
"Init.d Software Support
Insecure Stock Kernel with Init.d Support"
Click to expand...
Click to collapse
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
ludogaut14 said:
Thanks you for your help.
I have already try the eudomony rom but not find a script that works.
Click to expand...
Click to collapse
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
freaksamael said:
try this content as init.d script; I have-it on a rooted tablet (not alpha) and it works. name of the script - 01disable_selinux.
Before trying, please be sure (mandatory) that:
- the paths for the files are correct (/sys/fs/selinux/enforce) - (I have-it on my unrooted Alpha)
- busybox is installed in /system/xbin
- 01disable_selinux file must be created in Notepad++ ( UNIX Mode)
- proper init.d permissions are applied
- you use a "SELinux disable" Kernel
#!/system/bin/sh
/system/xbin/busybox chmod 777 /sys/fs/selinux/enforce
/system/xbin/echo "0" > /sys/fs/selinux/enforce
Attached you'll find my init.d script (pls remove .txt extension); if you agree with the content :laugh: just put it in your init.d folder and set proper permission for it (777). Reboot & report back.
Click to expand...
Click to collapse
Hi, I did your advice but do not work. 00test init.d ok, 01disable_selinux not work, "getenforce" always "enforcing". I wait a good person makes a kernel with SELinux permissive and KNOX desactived. Thank you very much for your advice and excuse me for my english.

Installation of Viper4android in Remix OS

For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
{
"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"
}
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now).
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor. This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
There are a priv-app and vendor inside the (in my case) leviticus folder
lollyjay said:
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
Click to expand...
Click to collapse
You downloaded leviticus 1.3 guess. It has no customize folder. It's in new Testing Numbers edition. I would suggest Numbers 0.9.8.7 zip. It's fine
Is it possible to make it systemless?
Sent from my Moto G using XDA Labs
OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
lollyjay said:
OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Click to expand...
Click to collapse
OK ANSWERS ARE ENCLOSED BY **
*4)Good point. I'll re-edit in the OP, Leviticus and exodus has 'system' folders that needs to be extracted to /system patition, then no need to extract 'app' from customize as there's already priv-app in that folder. But since Numbers has been officially initial released from today I would rather suggest to try it.*
*5)copy the contents is right, means everything including ARISE version info.text to be copied to /system. It's current version info helpful for future update. Merging means merge the contents of /vendor with the existing system contents. Vendor in /customize is so that /customize/vendor will go to /system/vendor or /vendor depending on the device. As far I know symlink to /system/vendor was written to mitigate the TWRP 7 error but as this is RemixOS I'll take it as optional. :good:*
*6) As I told in exodus and leviticus there's already priv-app in the /system folder. *
Just let me know if everything goes well or not. Enjoy.
Aguys said:
Is it possible to make it systemless?
Click to expand...
Click to collapse
No idea about system less v4a right now. BTW the main difference between system less and system, besides partition, is that thise sound system files will be symlinked (symbolic link) to /system, those are files that don't exist in /system. The only exception being audio_effect.conf, which will be moved to data/media/0 so that the sound system's audio_effect.conf will be symlinked.
BTW IMO /system installation is rather better to enjoy the fuller sound quality.
OP is updated. Symlink and other regular stuffs are clearly explained
I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??
modaifallah said:
I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??
Click to expand...
Click to collapse
Make sure you Remount system RW to RO using step by step jide's guide( link in OP) for Linux and download following ARISE NUMBERS (official stable release from Today). Enjoy :good:
https://www.androidfilehost.com/?w=files&flid=97426
it's possible using viper without set selinux permission?
ulum.misbahul said:
it's possible using viper without set selinux permission?
Click to expand...
Click to collapse
Selinux is disabled for this ROM mate. U may check
Code#
su
#getenforce
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
in the screenshot you posted..
the neon status is not enabled then how you are saying its working
ajaikumarnadar said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
in the screenshot you posted..
the neon status is not enabled then how you are saying its working
Click to expand...
Click to collapse
Neon is a ARM instruction for more efficient processing. It's for x86 architecture so it's not needed.
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
what about dolby atmos or dolby digital for remix os ? any possibilities ?
good work bro.. for bringing viper installation tutorial for remix os..
i just install it, and it sounds not too good. There is no low tons(bass) only high, even if i boost bass to max i hear only small change. I tryed exodus and numbers 3,5 and imhave same problem.
Second thing. Installing this mods corrupting my MBR and i can't boot to windows, only remix os
any ideas how to fix

How to set SELinux to permissive easily on miui 10.2?

Please help me set / change SELinux to permissive on Stock MIUI 10.2 unlocked,rooted with magisk, in desperate need of this. Checked some on the internet but "Universal init.d" app has been removed from play store.
For god's sake, cant it be just simple that add "blah-blah" module in magisk and reboot and u r done!:fingers-crossed:
Flash this in twrp if you want permanent solution https://androidfilehost.com/?fid=3700668719832241024 or you can just set it using kernel manager like smartpack kernel manager or kernel adiutor (in misc section).
I don't like touch on kernel, so I created a file in /data/adb/post-fs-data.d with follow content (permissions: rwxr-xr-x or 755)
Code:
#!/system/bin/sh
setenforce 0
This way I can simply delete the permissiver script whenever I want.
I use CoolTool and to read some battery files, even having root privilegies, SELinux permissive is necessary.
Adriano-A3 said:
I don't like touch on kernel, so I created a file in /data/adb/post-fs-data.d with follow content (permissions: rwxr-xr-x or 755)
Code:
#!/system/bin/sh
setenforce 0
This way I can simply delete the permissiver script whenever I want.
I use CoolTool and to read some battery files, even having root privilegies, SELinux permissive is necessary.
Click to expand...
Click to collapse
So hey, I know this is a really old post and I realize that you might not reply but just trying to reach out anyway and confirm - just creating a script file like "permissiver.sh" in data/adb/post-fs-data.d with the right permissions will do the trick?
---------- Post added at 08:47 PM ---------- Previous post was at 08:08 PM ----------
stonedead said:
Flash this in twrp if you want permanent solution https://androidfilehost.com/?fid=3700668719832241024 or you can just set it using kernel manager like smartpack kernel manager or kernel adiutor (in misc section).
Click to expand...
Click to collapse
How would you uninstall if not needed?

[GUIDE] After Root - EdXposed, SafetyNet, SELinux and more

Hi,
This guide help you to find a correct configuration and make environment for installing EdXposed and pass SafetyNet (and more) on a official Nord rom (tested on my EU 10.5.8)
All apps pass SafetyNet, Xposed and Magisk test (bank app, tv app, pogo, mario kart, ...)
Code:
ADVICE
This method need to put SELinux in permissive mode, it's no safe for your phone security..
But almost years, all my phone is in permissive mode, no problems ever for my.
Use at your risk!
Instructions :
-Install last official android 10 version for you device
-Root your devices (follow this guide)
-(Optional) Flash TWRP Recovery with fastboot in recovery partition
-Install/upgrade Magisk/Magisk Manager in the last stable version
-Reboot
-In Magisk setting tab, disable and enable "magisk hide" switch
-Install busybox app (don't open now) (my app is by Stericson, i suppose work on other busybox app)
-Go to Magisk manager and download following module :
. BusyBox for android NDK
. App Systemizer
. Magisk for recovery (mm) (only if you have flashed TWRP)
. Debloater (only if you need to debloat app per app your phone)
. Active systemless host in Magisk options (if you need AdAway)
. Flash youtube vanced with magisk if you need vanced (install root method doesn't work for me)
-Reboot
-Check if BusyBox (1.31.1. osm0sis) is installed on /system/xbin on your BusyBox app companion
-Open terminal and tip (once at once):
Code:
su
systemize
s
c
-Create a new file called "08setperm" in /data/adb/post-fs-data.d
Put this code inside:
Code:
#!/system/sh
setenforce 0
-Install latest Riru Core in magisk manager.
-Install EdXposed Manager
-Reboot
-Go to EdXposed Manager and install the latest canary Sandhook version
-In options tab, switch on "App List Mode" and "Instant Module List"
-Browse, download and install "HiddenCore Module" on Manager
-Go on module tab and active EdXposed module and HiddenCore module
-Reboot
-Go to Blacklist tab on EdXposed Manager and enable:
. Your apps (like with magisk hide feature)
. Carrier service
. Google framework
. Google game
. Google play store
. Google play service
-Go to Magisk Manager and hide:
. Your apps
. Google play service (uncheck and check again)
-Disable usb debugging in dev options (for full spoof)
-Reboot and done!
My favorites apps/module:
. Battery charge limit (example: stop night charge at 99% and wait to discharge to 90% and charge again to 99% target)
. Migrate (the new best app saver, titanium backup is.. hum..)
. adaway (block ads, add repo on this app for better work)
. Mixplorer (cool file/root explorer)
. Materiel terminal (cool terminal, no superficial tweek)
. AodNotify (the best notification light for me..)
. Wifi Key View (show yours wifi keys)
. Liveboot (watch and save a logcat in place of boot animation)
. Alltrans xposed (translate all your apps)
. Gravitybox xposed (most customisation)
. Minminguard xposed (ad block for apps)
. LuckyPatcher + xposed module
See you!
Thanks! Did exatcly everything right. And Magisk & Xposed are prefectly hidden from my banking app. But the CompleteControl App (for VISA card) is still detecting it. I don't know what I can do to prevent that. I read in an article that "There are many files and packages that MDMs look for when detecting if a device is rooted. " like
"Su Binaries. The following list of Su binaries are often looked for on rooted devices./system/bin/su
/system/xbin/su
/sbin/su
/system/su
/system/bin/.ext/.su
/system/usr/we-need-root/su-backup
/system/xbin/mu"
---> should I therefore uninstall BusyBox? When clicking on "UNINSTALL" in the app, you get a pretty big disclaimer that you might lose funcionality of many rooted apps, so I didn't. After doing all the steps in #1 post, is it safe to disable and uninstall BusyBox? Is there an alternative to hide root from CompleteControl app? THANKS! Great work with the guide btw...
I followed the instructions, and although Magisk Manager itself thinks SafetyNet passes, other SafetyNet checkers still show it fails everything and e.g. I can't update Netflix or find it when searching the Play Store
Would you like this to get proofread to make this article readable by other people?
---------- Post added at 11:46 PM ---------- Previous post was at 11:45 PM ----------
NTWarrior said:
I followed the instructions, and although Magisk Manager itself thinks SafetyNet passes, other SafetyNet checkers still show it fails everything and e.g. I can't update Netflix or find it when searching the Play Store
Click to expand...
Click to collapse
Download an .apk and install it over Netflix. The latest one might not work, so try out a few different versions.
You quote magisk for recovery but to use it you need to access /data partition. How do you decrypt it?
I installed the current (26) Riru, installing edXposed failed (they don’t support it yet). After some searching, I installed LSPosed instead.
Now I’m passing safety net with just hide props config and no HiddenCore needed

[GUIDE] Bromite SystemWebView with OTA Update Survival

Tested with:
Code:
ArrowOS Version: arrow-11.0
ArrowOS Build Type: OFFICIAL
ArrowOS Build Variant: VANILLA
Device Name: POCO X3 NFC (surya)
This modification makes use of the addon.d survival mechanism found in almost all (if not all) custom ROMs, which is leading back to CyanogenMod, and allows the installation of Bromite SystemWebView with automatic reinstatement after a manual or OTA system update.
Create the folder /sdcard/Android/addon.d/webview and download Bromite SystemWebView to that location.
Place the following script with the name 51-webview.sh into /system/addon.d and make it executable (755), which can either be done from a root shell or through recovery after mounting /system with read-write access:
Code:
#!/sbin/sh
#
# ADDOND_VERSION=2
#
################################
# Restore Bromite SystemWeview #
################################
case "$1" in
post-restore)
AD="/sdcard/Android/addon.d"
D="/product/app/webview/webview.apk"
mount /dev/block/mapper/product /product 2> $AD/mount_error.log
[ -f $D ] && cp $AD/webview/arm64_SystemWebView.apk $D 2> $AD/webview_error.log
umount /product
;;
esac
That's it, either reinstall the current version of the used custom ROM through recovery or make an OTA update.
Now the catch with this was, that for some unknown reasons, addon.d scripts see the device mapping different than from a running system or recovery, please see this issue for details.
ArrowOS 11 has webview.apk in /product/app/webview/, but this may be different in other ROMs. In that case, simply have a look and change the destination ($D) in the script accordingly.
The script is safe to use as nothing gets modified if the webview file is not already found at the given destination.
To uninstall this modification, simply remove the file /system/addon.d/51-webview.sh.
You can also temporarily disable this modification by removing/renaming arm64_SystemWebView.apk from/in /sdcard/Android/addon.d/webview and everything gets back to default with the next system update.
BTW @unixandria's Webview Switcher Magisk Module is not working on Android 11 (yet), which is why I was looking into creating this mod in the first place. Please have a look at this issue in the Webview Switcher GitHub Repo.
magisk webview manager for android 11
https://dl.androidacy.com/wp-content/downloads/Magisk-Modules/WebviewSwitcher/WebviewManager_v8_0_1.zip
pan.rozowy said:
magisk webview manager for android 11
https://dl.androidacy.com/wp-content/downloads/Magisk-Modules/WebviewSwitcher/WebviewManager_v8_0_1.zip
Click to expand...
Click to collapse
Yes, already seen, but didn't try (because my method works as well). Any experience with the new Magisk module yet?
Master One said:
Yes, already seen, but didn't try (because my method works as well). Any experience with the new Magisk module yet?
Click to expand...
Click to collapse
it works ok
My "webview.apk" shows up under "/system/product/app/webview" as well as "/product/app/webview". I think "/system/product" is just a link to "/product".
If I can figure out the mount command for "/product", I'm going to try this.
Thanks for this information.
mangokm40 said:
My "webview.apk" shows up under "/system/product/app/webview" as well as "/product/app/webview". I think "/system/product" is just a link to "/product".
If I can figure out the mount command for "/product", I'm going to try this.
Thanks for this information.
Click to expand...
Click to collapse
Indeed, that file system path can be different depending on ROM, but you can easily find out yourself and simply change the location the shown script.
Master One said:
Yes, already seen, but didn't try (because my method works as well). Any experience with the new Magisk module yet?
Click to expand...
Click to collapse
Can we use bromit webview for android 7? After debloat google's.
I installed it but webview implemention in developer option is empty
pan.rozowy said:
it works ok
Click to expand...
Click to collapse
Source? Or, do you mind elaborate the "how to" process?
Before, i use mi8 with pixelexperience pie, which is easy to convert user app to system app. Now, i upgrade it to A11, webview folder scatter all across subfolder. I dont know which one should be replaced by new webview.
At first is good job
I use lineageos official
And is it possible to auto create oat too?
Akbar KanColle said:
And is it possible to auto create oat too?
Click to expand...
Click to collapse
Not sure what you mean, but this method can be adapted to whatever is needed to be restored.

Categories

Resources