Database Users

How to Install/Remove System Apps on Android [MUST HAVE ROOT]

########## IMPORTANT UPDATE ##########
There is an APP available that makes this much simpler
* No Console Commands Needed
* You still MUST HAVE ROOT
* It must be installed on internal memory to work correctly
* Be sure you know what a system app does before you remove it.
* If you remove a vital app you could mess up your system completely.
The APP is Called: "System APP Remover"
Here's a Link to Download it: http://www.megaupload.com/?d=ZFC2C1R7
Mirror Download Link: http://www.mediafire.com/?h3n3ftbwilshcvn
######################################
Here are the console commands for installing/removing system apps in android console emulator, very easy ; )
You must have ROOT and console emulator, I found this very helpful, so I hope it helps others as well...
_____________________________________________________________________________________
Install App to System:
Place APK file in the root folder on your sd card.
Open terminal and enter these commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /sdcard/filename.apk > /system/app/filename.apk
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# reboot
_____________________________________________________________________________________
Remove App from System (Be careful what you remove):
# mount -o remount,rw /system
# rm /system/app/Filename.apk
[Optional, to make read-only again]
# mount -o remount,r /system
[When Finished]
# reboot
_____________________________________________________________________________________
****KEY****
"#" means root command will follow
[Notes are in these brackets and aren't commands]
- ENJOY
ALSO...
**** I'm new to Android APP creation, but if anyone can automate this script to make a simple One-Click GUI APP that would be awesome, all I ask is that you put my name in the co-dev/"Thanks to" list for the app, just so I can say I helped ;-) ****
- CuriousAndroid

I am trying to reinstall some files I uninstalled. I went to the following link on this site and found some apps that people said could be removed - http://forum.xda-developers.com/showthread.php?t=773142
however, my Act1 video player now quits whenever I receive an incoming text, so I need to reinstall some programs and see which one is causing the problem
I downloaded an app called Android Terminal Emulator by Jack Palevich. I tried a "reboot" command (without the #) but it said reboot operation not permitted. Is this the Emulator I need to reinstall files? Am I doing something wrong?
--------------
EDITED:
ok nevermind, i realized the "su" command gives superuser access needed for the reboot....going to try to install files now

yeah, to use any root commands "su" must be used first otherwise the shell will think your just some generic user with limited privileges and nothing will work.
It's very important to identify any apps you plan on removing before you attempt it to make sure it isn't needed by another process.
You got lucky, some apps once removed can cause the whole rom to fail, so be careful!
- CuriousAndroid

well i think i messed something up...is there a way to recover back to stock after using the sdx stock app remover? i removed the video player but tried reinstalling it...when i uninstalled it from sdx, i noticed my other video player (Act1) would quit whenever i'd get an incoming text
i have all the .apks backed up, but after attempting to reinstall the stock video player, it hangs in MyFiles...then i reset back to factory (no Act1), and it can't play my videos, i get the error "No applications can perform this action"
Is there a way to recovery back to stock with all applications installed and in tact? i have all the .apks, but this video player won't work, after following your instructions above
thanks

It will work. Check the following:
* All shell commands are CASE-sensitive, so if the app is called Vending.apk you can't type vending.apk
* for the command to work you must have the apk on the root of your SDcard, not in sub-directories.
* if you have a copy of the rom you installed you can unzip it on your PC and find the system app folder, which you can use to cross-refference with the system/app folder on your phone to see if your missing something else.
in terminal you can list system apps like this:
# su
# cd /system/app/
# ls | more
[that will allow you hit space bar to navigate through app list if it's longer than a page,press ESC when done to go back to prompt]
* If all else fails you can backup your settings to your sd card and re-install your rom (as a last resort)
-Good Luck

curiousandroid said:
Install App to System:
Place APK file in the root folder on your sd card.
Open terminal and enter these commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /sdcard/filename.apk > /system/app/filename.apk
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# reboot
_____________________________________________________________________________________
Remove App from System (Be careful what you remove):
# mount -o remount,rw /system
# rm /system/app/Filename.apk
[Optional, to make read-only again]
# mount -o remount,r /system
[When Finished]
# reboot
_____________________________________________________________________________________
****KEY****
"#" means root command will follow
[Notes are in these brackets and aren't commands]
- ENJOY
ALSO...
**** I'm new to Android APP creation, but if anyone can automate this script to make a simple One-Click GUI APP that would be awesome, all I ask is that you put my name in the co-dev/"Thanks to" list for the app, just so I can say I helped ;-) ****
- CuriousAndroid
Click to expand...
Click to collapse
When I am doing the first part here of installing app to system I dont just simply do that first I can already have an app ready to go that I want to move to sd card right? I am just making sure I didnt have to do that simply first before I even start moving the apps. This site has be great and thanks for everybody help. Wish I would have known have this site way back when.

What is "yaffs2" standing for? I type "yaffs" instead of "yaffs2". What has this done to my system? Do I have to expect any "side-effects"?
When I call # ls | more to list the directories content, the apk is listed but it is not installed yet. Is there anything else i have to do?

yaffs is nand flash filesystem
yaffs2 is more elaborate updated version
yaff2 has greater support
so if your device isnt supported by yaffs1, it may not work.
it's best to follow the commands as they're written.
apps still appear as apks in system/apps folder after installation.

Haha thats funny!! I downloaded this app.. put it on my sdcard.. installed it and when i tried to open it it said " Shame on you for trying to pirate a 1.00 app "

If you have Applanet just go there and look for Systemapp Remover - it's a bit older version but seems to do the job.

By mistake my contacts.apk is removed. Above trick also not worked. my phone is LG GT540. Pl suggest any other way.

rajhan9412 said:
By mistake my contacts.apk is removed. Above trick also not worked. my phone is LG GT540. Pl suggest any other way.
Click to expand...
Click to collapse
Grab the contacts.apk from the rom you're running and push it back in. Btw titanium backup removes system/apps without terminal commands while allowing to to make a backup first in case u want. it back or for little hickups such as this.
Sent from transparent xda app by theimpaler747

I did everything right, and the apps that I removed disappeared from the app drawer. But, after I reboot my phone, they show up again.
What can I do?

In terminal type
ls system/app
Hit enter and see if said apps are in the list
Sent from my HTC Sensation 4G using XDA App

i got a better method.
app is called app quarantine
it need root and is totally free
it can quaratine every app including rom apps and system apps
really that thing awesome. no manuall backup needed anymore and as long you dont brick the os you can easy try and error - but of course still be carefull and login and activate com.brain.logic.provider lol

Hi there i use root explorer and that is the easiest way i think to remove system apps on android phones [root required] you can download root explorer from the market or get it from 4shared just search for root explorer.apk install it and navigate to /system/apps/ and the app you wish to delete long press the app and delete make sure you mount as read/write instead of read only.
Hope this helps 
@0mpranav

actually its not and actually you didnt read my post
i advertise this little peace of freeware because it really made my day (im not related in anyway to the developer)
the quarantine removes it but store it automatically in another directory
just multiselect and press one button DONE
no need to single delete something because you always should backup first
for example turns out on samsungs device EMAIl application is also related to exchange sync - huh i was happy to restore it
really take a look -
btw i hate the root explorer - for some taksts might be usefull but fileexpert is way better in that and its free as the quaratine app is too

bofh999 said:
actually its not and actually you didnt read my post
i advertise this little peace of freeware because it really made my day (im not related in anyway to the developer)
the quarantine removes it but store it automatically in another directory
just multiselect and press one button DONE
no need to single delete something because you always should backup first
for example turns out on samsungs device EMAIl application is also related to exchange sync - huh i was happy to restore it
really take a look -
btw i hate the root explorer - for some taksts might be usefull but fileexpert is way better in that and its free as the quaratine app is too
Click to expand...
Click to collapse
You were right mate got problems in upgrading my nexus one coz i deleted the .odex system apps directly without any backup but upgraded to 2.3.6 with some trial and error method but lost root access any help would be appriciated 
@0mpranav

Installing system app
Hi, i have the same problem. I tried Root Explorer, and the Shell Commands method (with Cat command), the files i copy are in there, with all the permissions and everything, but when i reboot, none of them are installed, and my "contacts" app is still broken. Can anyone help please?

Nevermind, found the problem. I needed the exact files for my Atrix 4G with the same android version.

Just rooted - unable to backup

Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.

cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)

bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer

cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.

bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again

I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.

cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.

lost all permissions after messing with platform.xml

Hello,
I have SM-N9005 variant and recently I updated to the latest android 4.4.2 leaked version with Odin, and then rooted with CF-Auto-Root.
After that, I lost the permission to write to external sdcard.
I searched and found this: http://forum.xda-developers.com/showthread.php?p=49603814
I backed up /system/etc/permissions/platform.xml and then I followed the instructions there.
After restart, a lot of app stopping messages showed and I had no access to file system or network anymore.
I used adb shell to restore the original platform.xml but it didn't helped in any way.
It seems that all mounts and networks are working, but none of the applications has permission to use any of them.
How do I resolve this, without wiping all my data?
Thank you!

You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)

radicalisto said:
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
Click to expand...
Click to collapse
I tried 644 and 777 but the problem persists.

rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.

radicalisto said:
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
Click to expand...
Click to collapse
The problem still persist

DxCK said:
The problem still persist
Click to expand...
Click to collapse
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.

A.N.Droid said:
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
Click to expand...
Click to collapse
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...

DxCK said:
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
Click to expand...
Click to collapse
just type sh kn0x0ut.sh to get all commands.
if you dont get this working, you can do it from twrp (i think cwm too)if you have it.
tap on "advanced" and then on "fix permissions".

Please Upload your Perfectly working ROOTED Z5 Kernels for NOUGAT [E6653,33,83....]

Everyone please share your modified stock kernel for your Z5 series models with specifics here ...........
- Model
- ROOT working
- TWRP
- SuperSU
- Busybox
and so on....
As there is way to much ambiguous information out there right now for perfectly rooting the nougat on Z5 series and even one can achieve root with DRM fix there seems to be no R/W permission on SYSTEM partition !!!!
So please the people here who have successfully achieve ROOT with W/R SYSTEM, SU , DRM and other capabilities and are happy with them , please do upload your kernels here mentioning proper model and other things mentioned above.
Its for general good

try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.

L33Tgod said:
try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.
Click to expand...
Click to collapse
I did try that.
And all the other methods currently available to this point.
Created / patched several kernels and the best I could achieve is a fully rooted kernel with DRM and SU.
The only problem is when I delete some thing inside the system folder, it comes back after 1 sec like nothing ever happened to it in the first place.
Searched for the issue a bit more , find 2 possible cures and tried them too but no luck---- so I am now asking people to upload their kernel here so that I can find out which is which and so on............

I'm on the Au firmware on E6653. Used rootkernel and answered yes to all questions except for Su and xposed. Then I installed phh's superuser from recovery and the app from the play store. Everything is working fine.

I shared weeks ago..
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry

@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?

Gezzaman8 said:
@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?
Click to expand...
Click to collapse
If you use AndroPlusKernel kernel, then you are not in stock.
Check a root browser "/sys/kernel/security/sony_ric/" folder is exist or not?

Edit libnfc-nxp.conf in /vendor

Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.

laocheebye said:
Hi Guys,
I am no developer but I need to edit the libnfc-nxp.conf in /system/vendor/etc to use nfc-sim.
I guess I need to unlock bootloader, flash the working twrp, get root and just use root explorer to edit the file?
Will it reset back to original file bcos of A/B partition thing when reboot?
Thanks if any android expert can let me know.
Click to expand...
Click to collapse
Yes, you need to be rooted.
It will not alter the file on reboot.

I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.

Well if you still have a locked Bootloader and unrooted, why would you need to edit that file for? If Google Pay, there is no reason why it wouldn't work. Those that are unlocked and rooted a little research the latest Magisk Canary(18.2) fixes Google Pay not working.

acuma14 said:
I tried to edit libnfc-nxp.conf in /system/vendor/etc, but it resset to default after phone reboot.
Also, i can's repair my gpay with free bootloader and magisk intalled. So i deside to return device to closed one.
Click to expand...
Click to collapse
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.

sandix said:
You will need to mount "/" as read-write, in a terminal emulator (or adb shell):
Code:
$ su
# mount -o rw,remount /system
**NOTE: The above syntax might be different depending on ROM is use. Please use at your own risk.
Click to expand...
Click to collapse
Root explorer offer me to mount directory aftomatically, and successfully save my config, but after reboot it returns to default values. I found information about to create a magisk patch for usefully edit config at all, but not sure it's the simpliest solution for me, and i can find step-by-step instruction...
I need this to use my nfc-transport sim card, here's the discussion https://forum.xda-developers.com/oneplus-5/themes/mod-nfc-swp-sim-enabler-oneplus-3-3t-t3650482
Do i need to set NXP_DEFAULT_SE as 0x02 instead 0x07 (should 07 implement UICC correctly)?
Idk how, but after reinstall magisk gpay starts working fine