Database Users

[HELP] How to ROOT multi user

Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks

At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD

Thanks for your answer
waiting for this ...

It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!

Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.

Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!

craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2

djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.

craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app

jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...

drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4

Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10

Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app

Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)

Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf

1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.

KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf

1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.

RRO layers - Systemless root (NOT WORKING)

Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?

I'll give it a try had nothing but issues trying to use layers, currently got busybox on rails installed but as you've mentioned can't get it working, I'll try as you've suggested thanks
Sent from my Nexus 6P using Tapatalk

Spot on
hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
Thank you so much for discovering this, I was going crazy why I couldn't create the overlay folder under vendor, this is the solution, to everyone who sees this, don't listen to whoever says busybox on rails is the way to go...

If you have supersu 2.65 and install busybox to /su/xbin then it will also work.

I have superuser 2.65 and following your instructions finally have layers working, thanks dude
Sent from my Nexus 6P using Tapatalk

Perfect, thank you
Sent from my Nexus 6P using Tapatalk

hutzdani said:
Okay so I have tried all the options on their development page on G+ but there seems to be a lot of arrogance from the devs about users with issues and not doing research even though following the instructions leads to nothing.
- Im rooted via CF's systemless root method
- I have TWRP 2.8.7.2 installed and working
- Busybox is installed in /system/xbin
- I have the correct Vendor image for my device
- Stock ROM 6.0.1
I use busy box on a rail to check its correctly installed and double check with a file explorer but still no themes will apply.
EDIT : Solved it - DON'T USE BUSYBOX ON RAILS ! for some reason it does not work with Layers correctly!
1. Uninstall any busy box installs
2. Reboot
3. Install busybox app from the play store and select /system/binx as the install location
4. Reboot
5. Profit
Anyone have any ideas to get this working ?
Click to expand...
Click to collapse
For me with su 2.65 and busybox on rails, things are working. However, not as expected. Sometime even I change some overlay it won't apply. Sometime the dialer and other fonts won't be visible at all. May be I should try ur method. Thanks.
Sent from my Nexus 6P using Tapatalk

This method will defeat the purpose of systemless root though, right? So Android Pay and Good for Enterprise will cease to work because /system had been edited?

Viper4android

is there someone who succes in the installation of this app?
when i open it,it ask if i want to install the drivers and stuck and after few seconds it crash
someone can help me with this ?

Many guys use this and there already was enough discussions, there are even seperate threads created with tutorials, use search for once[emoji14]

I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.

exad said:
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
Click to expand...
Click to collapse
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think

hinxnz said:
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
Click to expand...
Click to collapse
Yes! Thanks for the corrections! I haven't done it in a while! ?

Xposed for Fire HD 8 (6th) 2016

Edit: confirmed method from post #4 worked
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?

2ig2ag said:
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?
Click to expand...
Click to collapse
I'm new to android, can't help
sit and wait

I have been trying to get xposed working since I acquired root. I believe there is a mismatch between the processor and installed os. The CPU identifies itself as a 64-bit (aarch64) but there is no app_process64 in this OS. I tried touching the file and running the installer but that just soft bricked my tablet. Looking at the spec sheet it seems this CPU does not support 64-bit. The normal 32-bit Arm installer gave me the same results. May be time to ask @rovo89 for some advice.

I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.

can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送

How you guys rooted it ? on 5.3.2.1 - I yet to get the root. Please guide.

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more

nbc12 said:
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios
Click to expand...
Click to collapse
smokejumper76 said:
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more
Click to expand...
Click to collapse
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!

phpbb88 said:
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!
Click to expand...
Click to collapse
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.

smokejumper76 said:
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.
Click to expand...
Click to collapse
will try when I have time to play with my device
but I expect Custom ROMs on fire hd the most important

coltxL2717 said:
I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.
Click to expand...
Click to collapse
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated

ahac85 said:
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated
Click to expand...
Click to collapse
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Code:
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ #

phpbb88 said:
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Click to expand...
Click to collapse
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!

ahac85 said:
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!
Click to expand...
Click to collapse
Glad you got it worked out.

@coltxL2717 which version of the xposed installer did you use?
I downloaded the dvdandroid_26_11_1 and fail to install

@phpbb88, that is the installer I used. The script will error but the framework is still being installed.

coltxL2717 said:
@phpbb88, that is the installer I used. The script will error but the framework is still being installed.
Click to expand...
Click to collapse
I cannot install that apk by using file explorer, keep telling me installation failed....
edit: its working now, thanks!

I had the same issue as @ahac85. The kingoroot method he mentioned worked for me as well. You guys find any good/cool xposed modules that worked?

I was wondering if I changed my supersu gettings from grant to prompt would mess anything up? So far I haven't touched it, but would like the normal pop-up prompt that happens when su is requested. And if it doesn't work, that is just weird.

Magiks on Moto Z play

I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.

Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.

lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.

jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.

Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.

So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.

You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.

Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?

tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.

Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?

I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.

jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.

tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.

jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.