Mainly looking to change / take charge of the boot animation.
.
Yes, foolish me . . . I was nostalgically looking over my old ( backed up ) apps on my old rooted phones . . . and ran into 3C All-in-One toolbox. And 3C is still around unlike others.
I don't we can yet. Build.prop is RO at the moment from what I've been seeing.
If you have Magisk installed you can use resetprop to change any property, ro. or not.
Why do you need to change a property for bootanimation? Just use a Magisk module to shadow your own bootanimation.zip
Related
Any way to run pokemon go on rooted devices cm14.1, RR :fingers-crossed:
Past Solution
When i tried to use pokemon go on cyanogen mod 13, i had to download smanager (I'm new, so I couldn´t post the link, search it on google play), went to bin and xbin folder and changed the name of the root folder for .root in both folders and it worked, I don't know if this works now ´cause I'm not playing anymore
I hope this work
No... Pokemon Go uses the SafetyNet API, which on custom ROMs there is no way around (read up on the SafetyNet API and you will understand why pretty quick). On stock rooted there are some exploits but they seem to get patched almost as fast as they are put into place.
krisbeowolf said:
Any way to run pokemon go on rooted devices cm14.1, RR :fingers-crossed:
Click to expand...
Click to collapse
delete "su" file from system/bin and system/xbin, then reboot.
tested on RR. it works
but you'll lose root access after restart
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
I have tested myself the old ways to put an app as system app on Oneplus 6, but I didn't know that with new Android patches there are some new issues and permissions required (like you can still use lucky patcher, link2sd, es file explorer,..., but you have to add some xml manually, depends on the specific app).
You still need root (magisk) with this method.
The best and the easier way I have found is to use a magisk module: App Systemizer (maybe you can find it as an app or not, idk).
Search in dowload section, in magisk manager, install it, then install a terminal emulator.
Write and enter:
su
systemize
choose 1 and it will provide you a numbered list of your installed apps
choose the correspective number
choose 2 to move to system/priv-app
It will provide the additional xml that are needed now to move an app to system; then reboot and the app will be properly moved to system.
[MOD EDIT]Do not ask for donations.[/MOD EDIT]
Link2sd
Hi, thanks for this info, i have a question
This whole process you explained here, it has to be done without revert the process done with link2sd or it has to be done fresh with link2sd not installed.
Thanks
I have tested myself the old ways to put an app as system app on Oneplus 6, but I didn't know that with new Android patches there are some new issues and permissions required (like you can still use ..., link2sd, es file explorer,..., but you have to add some xml manually, depends on the specific app).
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)
You still need root (magisk) with this method.
The best and the easier way I have found is to use a magisk module: App Systemizer (maybe you can find it as an app or not, idk).
Search in dowload section, in magisk manager, install it, then install a terminal emulator.
Write and enter:
su
systemize
choose 1 and it will provide you a numbered list of your installed apps
choose the correspective number
choose 2 to move to system/priv-app
It will provide the additional xml that are needed now to move an app to system; then reboot and the app will be properly moved to system.
Think this might need moved to guides section mate
Nameless said:
Think this might need moved to guides section mate
Click to expand...
Click to collapse
Yeah, someone has already done it. Sorry
Fivegates said:
I have tested myself the old ways to put an app as system app on Oneplus 6, but I didn't know that with new Android patches there are some new issues and permissions required (like you can still use ..., link2sd, es file explorer,..., but you have to add some xml manually, depends on the specific app).
(Moderator Edit: reference to Warez removed - as per XDA's Forum Rules)
You still need root (magisk) with this method.
The best and the easier way I have found is to use a magisk module: App Systemizer (maybe you can find it as an app or not, idk).
Search in dowload section, in magisk manager, install it, then install a terminal emulator.
Write and enter:
su
systemize
choose 1 and it will provide you a numbered list of your installed apps
choose the correspective number
choose 2 to move to system/priv-app
It will provide the additional xml that are needed now to move an app to system; then reboot and the app will be properly moved to system.
Click to expand...
Click to collapse
What about if u do a factory reset? i tried this way but, when i do the factory reset the app is erased, dont make sense if dont survive a FR, you know how solve this?
Thanks for share!
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access.
Did i miss something when i rooted with Magisk? I dont remember anything setting root to read only.
Anyone can help id appreciate any help.
Details on my root process...
Google Pixel 7 Pro, Factory Unlocked,
Android 13
Rooted using init.boot.img & magiskpatched.img
LSPosed 1.8.6 (6712) zygisk running, Magisk 26.1 with the following modules:
1. app systemizer
2. magiskhide props config
3. system apps (lucky patcher module)
4. systemless hosts
5. universal safetynet fix
6. zygisk LSPosed
Im not sure how to configure superuser in Magisk other than default settings such as mount namespace mode...Should any of this matter?
1st: props config is not needed. USF is good enough.
2nd: ofc you can't just edit any system file. The /system partition is RO by default to protect itself from idiots. For you to write anything to it, you need to enable root access (in the upgrade FX menu, swipe all the way to the right)
using root mode, you can now mount system RW temporarily, remember to mount it back to RO after you're done messing with it, a RW /system will not boot.
I thought magisk will just allow a remote link to a /system file, not actually write on it. It replaces via link, it does not actually change the file.