Database Users

Stock rom but add Enhanced power menu framework

Hi all,
Is it possible to have a stock rom/locked BL/stock recovery and ADB push framework-res.apk, android.policy.odex, android.policy.jar?
What I really want is to be fully stock for the moment but use Expanded Desktop Mode to hide softkeys, so when I play a games/browse net it is in full screen.
Assuming I was able to get the modded files.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

any ideas?

Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium

zephiK said:
Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
He's right. Why do you want this setup, OP? Surely there is a reason.
Unless I'm mistaken, advanced power menu requires modifying framework-res.apk. Not sure how familiar you are with modifying framework, but it's not fun.

estallings15 said:
He's right. Why do you want this setup, OP? Surely there is a reason.
Unless I'm mistaken, advanced power menu requires modifying framework-res.apk. Not sure how familiar you are with modifying framework, but it's not fun.
Click to expand...
Click to collapse
2 reasons really, 1st is stock rom is stable
2nd is barclays bank app will not work on rooted rom.
zephiK said:
Just like the other threads where op wants features from a custom rom. Just save yourself the time and flash a custom rom.
If you do get it to work, you won't be able to accept further otas because you modified your phone.
Also you will most likely need a rom that's deodexed which the stock rom is not.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Worth a shot.

Ronaldo_9 said:
2 reasons really, 1st is stock rom is stable
2nd is barclays bank app will not work on rooted rom.
Worth a shot.
Click to expand...
Click to collapse
Have you tried a custom rom? All of them are stable, Nexus devices are aosp supported and will work off the bat with no problems.
Stability is a definition of all drivers working (wifi, blue tooth, cellular data, etc) as well as features.
I don't get why you're bringing root into question here. In order to do the tweak you want, it requires root? So either way you'd be rooted in both cases. You may also choose to temporarily un root using the superuser app.
So......
Sent from my Nexus 4 using xda premium

simple answer is, a custom roms with these tweaks have root. The barclays app does not work even if you remove SU and SuperUser.apk

Ronaldo_9 said:
simple answer is, a custom roms with these tweaks have root. The barclays app does not work even if you remove SU and SuperUser.apk
Click to expand...
Click to collapse
You don't need to remove SU and SuperUser to disable root. There is a option implemented within the app in which you can disable root access temporarily until you uncheck the box again.
Your stock ROM with this "enhanced power menu" requires root as well. So your point invalidates yourself? because stock ROM + this tweak you want needs root.
Custom rom = root.
??????????? both requires root. I don't get where you're going at.

incorrect. You are either trying to be helpful and want to understand my point or you are just trying to be smart.
enhanced power menu does not need root access and therefore you can delete SU and Superuser.apk.
You have not used the barclays app so do not comment on how you can disable root access to use it.
I had this issue on Galaxy Nexus but had it working on a custom rom by manually removing all root files from the zip beofre flashing but all other roms Barclays app always detected root even if i removed all root files maybe because the rom had insureboot image.
Anyway I think for me to use a modded framework I would need a deodex, which =custom rom

Ronaldo_9 said:
incorrect. You are either trying to be helpful and want to understand my point or you are just trying to be smart.
enhanced power menu does not need root access and therefore you can delete SU and Superuser.apk.
You have not used the barclays app so do not comment on how you can disable root access to use it.
I had this issue on Galaxy Nexus but had it working on a custom rom by manually removing all root files from the zip beofre flashing but all other roms Barclays app always detected root even if i removed all root files maybe because the rom had insureboot image.
Anyway I think for me to use a modded framework I would need a deodex, which =custom rom
Click to expand...
Click to collapse
Trying to be smart? I am smart. Look at my amount of posts and thanks, I don't get all those points by saying nonsense. I am being helpful but YOU aren't understanding me. I'm saying Superuser can temporarily DISABLE ROOT on the WHOLE PHONE regardless of WHAT APP you use. It's a GLOBAL functionality.
Enhanced Power Menu requires changes in the /system/ so it requires root access. Root access is what allows you to do changes outside of /sdcard/.
That's what I said about barclays app. You can disable root access on the whole phone via SuperUser app. I mentioned this many times. It doesn't matter what app I'm referring to. The superuser app disables root on the WHOLE PHONE regardless of what app it is. So don't comment to me saying I don't know what I'm talking about. Chainfire implemented superuser this way because when you rent/buy movies from Google Videos/Movies it doesn't let you watch them if you are rooted; so a workaround is to temporarily disable root so you can watch them. Then when you are done, you can reactivate root access.
Obviously no one else is here helping you so...... if you're so smart figure it out then. But flashing a custom ROM is the easiest way.
https://play.google.com/store/apps/...51bGwsMSwxLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Always runs in ghost mode
- Wake on prompt
Click to expand...
Click to collapse

So I unlocked BL and flashed custom rom, done the hide SuperSU but barclays app still said phone is rooted, cleared cache and davik still the same. Uninstalled SU same. Deleted files in xbin that relates to busybox and su damn app still says phone is rooted (i did clear it's cache/uninstall/reinstall.
this app has good root protection/detection

Modified Root App (Virus Warning)

I m on cataclysm Rom and Semaphore kernel. I was not sure whether tbis issue was kernel or rom related, so thought to put this question in this thread.
On opening trickstermod app, i m getting the following warning (plz see screenshot):
{
"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"
}
Is this some generic warning? Coz i never got this b4 (or may b didnt notice it). I dint modify any app.
Thanks in advance.
Sent from my Nexus 4 using Tapatalk

Seems only a trickstermod App issue, got my answer here:
http://forum.xda-developers.com/showthread.php?t=1768315&page=89

omer7 said:
Seems only a trickstermod App issue, got my answer here:
http://forum.xda-developers.com/showthread.php?t=1768315&page=89
Click to expand...
Click to collapse
I'm unsure... even though they say that there, I do not get this warning. Do you have a virus scanner? (I know, horrible bloated things for phones) might be worth getting one and having a poke around just to make sure?

Monotoko said:
I'm unsure... even though they say that there, I do not get this warning. Do you have a virus scanner? (I know, horrible bloated things for phones) might be worth getting one and having a poke around just to make sure?
Click to expand...
Click to collapse
No, don't have any anti virus in my phone.
But after restarting my phone and removing Super SU access from SuperSU (app), I'm not getting this warning again.
I also read in some other thread, that this is false positive (but that post was about a year old), so not sure why did i get that error, but now not getting it.
Lets see how it goes now :cyclops:

omer7 said:
No, don't have any anti virus in my phone.
But after restarting my phone and removing Super SU access from SuperSU (app), I'm not getting this warning again.
I also read in some other thread, that this is false positive (but that post was about a year old), so not sure why did i get that error, but now not getting it.
Lets see how it goes now :cyclops:
Click to expand...
Click to collapse
You removed SuperSU access from the SuperSU app? It's the SuperSU app that was generating the warning, warning you of another app that may have been modified. I don't think root access will work without SuperSU having root...

Monotoko said:
You removed SuperSU access from the SuperSU app? It's the SuperSU app that was generating the warning, warning you of another app that may have been modified. I don't think root access will work without SuperSU having root...
Click to expand...
Click to collapse
I didn't know which app (whether ROM/Kernel) was causing this issue, I read in some other thread where someone said, clear data (and cache) of trickstermod app and restart your phone (in addition, I removed trickstermod root access in SuperSU app as well). Restarted my phone, got that warning once or twice again I think, but checked it again, and this warning was no more there. I am still not sure what this warning is. Coz I didn't modify any app.
In that thread (link posted above) someone said, it is just a warning. Hope it is not an issue. . And I'm checking it, not getting this warning again, so could be it was a false positive.
And tell me is this warning given by SuperSU app? I've SuperSU (by ChainFire) app installed in my phone.

omer7 said:
I didn't know which app (whether ROM/Kernel) was causing this issue, I read in some other thread where someone said, clear data (and cache) of trickstermod app and restart your phone (in addition, I removed trickstermod root access in SuperSU app as well). Restarted my phone, got that warning once or twice again I think, but checked it again, and this warning was no more there. I am still not sure what this warning is. Coz I didn't modify any app.
In that thread (link posted above) someone said, it is just a warning. Hope it is not an issue. . And I'm checking it, not getting this warning again, so could be it was a false positive.
And tell me is this warning given by SuperSU app? I've SuperSU (by ChainFire) app installed in my phone.
Click to expand...
Click to collapse
Ah, yes it certainly looked like a regular SuperSU informational (like "root access was granted") and if I was to hazard a guess I would say that SuperSU noticed something had changed and thus gave you the warning. There will be something that triggers the warning, so your next course of action would be to find out what triggered it. It isn't something that will come up randomly or "for everyone"
You can maybe check the SuperSU logs?

Monotoko said:
Ah, yes it certainly looked like a regular SuperSU informational (like "root access was granted") and if I was to hazard a guess I would say that SuperSU noticed something had changed and thus gave you the warning. There will be something that triggers the warning, so your next course of action would be to find out what triggered it.
You can maybe check the SuperSU logs?
Click to expand...
Click to collapse
Yeah checked the Logs, just found info of app(s) which were granted SuperSU app.
ANyway hope it was just a false positive, but searching some other threads as well to find some more info...

If the rom comes rooted with any build in superuser, you don't have to flash SuperSU anymore. It will only create conflicts.

arffrhn said:
If the rom comes rooted with any build in superuser, you don't have to flash SuperSU anymore. It will only create conflicts.
Click to expand...
Click to collapse
Sorry, can't press thanks button, reached limit :fingers-crossed:
ANd I'm on Cataclysm ROM, and it came with SuperSU (app by ChainFire).

omer7 said:
Sorry, can't press thanks button, reached limit :fingers-crossed:
ANd I'm on Cataclysm ROM, and it came with SuperSU (app by ChainFire).
Click to expand...
Click to collapse
Lol, pro-tip here. XDA app has no thanks limit. Btw, it's good if you have solved your problems.

arffrhn said:
Lol, pro-tip here. XDA app has no thanks limit. Btw, it's good if you have solved your problems.
Click to expand...
Click to collapse
Thanks for the tip, and yeah it works. :fingers-crossed:
ANd problem not really solved, just I'm not getting that warning anymore, and I'm assuming it was a false positive or may be something else. I've done some search on google and XDA, i could only found 2 ppl who got the same warning.
I'm glad I'm the 3rd one. Lol ... (I know there wud b many other, didn't search too many pages)

Android O, Busybox, ElementalX, Root, Suhide WORKING!

As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys

{
"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"
}

ne0ns4l4m4nder said:
As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys
Click to expand...
Click to collapse
Glad to hear this is working for you, it's not really anything that hasn't been covered in more depth in other threads / guides...
As a note; You would only lose root, if you flashed a kernel, but didn't flash SuperSU after && or by installing busybox into the wrong location or by replacing the system applets...
Personally, I install busybox into /sbin/supersu/bin because it has the advantage of not touching the /system partition at all - so for example; I can flash a a full factory image (rather than OTA), using flash-all script (removing the -w argument to not wipe data) and retain busybox.
Cheerz

Have you got any advice about viper/arise? I just need it and than I'm good to go :good:

TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Not really, no. I don't use viper or arise. I would say read through the related threads on them. There is bound to be good instructions.... sometimes I read through the comments, in particular; the last couple of pages on a given thread, as sometimes there is useful information.
I pretty much have a similar setup to your device, plus substratum and a few other root apps and tweaks. (Fdroid, adaway, afwall, etc).
Good luck.

Is there a difference in flashing the boot.img versus flashing the image minus the -W? I've been trying and trying but I always end up with boot loops and it going back to stock recovery. Usually the boot Loops start right away when I'm first rebooting the system. Last night I got Elemental and root installed it worked fine for about 30 minutes then started bootlooping and ended up at stock recovery again.

I used Busybox v1.27.2 from osm0sis
What I do:
- Flash the September update (I do a full wipe)
- Boot up, finesh the setup and set a pin
- boot modded twrp
- Enable MTP and copy the Files (BusyBox v1.27.2, EX Kernel 2.0.1, SuperSU v2.82 SR3 & Suhode v1.0.8)
- Flash EX Kernel, SuperSU, Suhide and BusyBox
- reboot and enjoy
PS: passing with Substratum is also no problem

Flash sr4 to prevent bootloop: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Sent from my Pixel using Tapatalk

trying to apply adaway seems to remove root and break twrps ability to mount /data

KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/

Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.

brownkid said:
Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.
Click to expand...
Click to collapse
Use meefix busybox not stericson

Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
This is the best adblocker for android, it uses dns block lists like pi-hole and root isn't needed since it uses the vpn interface:
https://f-droid.org/packages/org.jak_linux.dns66/
Sent from my Pixel using Tapatalk

Stericson Busybox has been updated for Android O.
https://forum.xda-developers.com/pixel-xl/how-to/busybox-oreo-t3672140/page2

Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
Adaway works great if you change the "Target hosts file" to "/data/data/hosts"

I installed the updated Stericson Busybox to /sbin/supersu/xbin and all working great.

KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
I disagree, I dont have a problem with adaway.

TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.

devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
Same here. At least we have something

devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
To which older release of viper4arise are you referring to?

[Q] Safety net issues / temporarily deactivating SU

Hi
Are there any knows workarounds on how to pass safety net? I'm running LineageOS 15.0, and just tried logging into Snapchat - failed. Guess that's the safety net working.. Anyone have any ideas on how to get around this?
Thanks,
- H

hhaznadar85 said:
Hi
Are there any knows workarounds on how to pass safety net? I'm running LineageOS 15.0, and just tried logging into Snapchat - failed. Guess that's the safety net working.. Anyone have any ideas on how to get around this?
Thanks,
- H
Click to expand...
Click to collapse
Always search:
https://forum.xda-developers.com/showthread.php?p=72138574

smitharro said:
Always search:
https://forum.xda-developers.com/showthread.php?p=72138574
Click to expand...
Click to collapse
Thank you for your response. Yes, I should have mentioned that I did do some research prior to posting, but the results I found, all either (as you link to) required Magisk SU, or (official?) CyanogenMod/LineageOS based ROM's (as shown here: https://labs.xda-developers.com/store/app/com.bhb27.isu ).
The reason I posted my question being that I am using SuperSU and the unofficial LineageOS 15.0 by vache (https://forum.xda-developers.com/g5-plus/development/rom-lineageos-15-0-t3673573 ), and therefore - by all definitions - am not eligible for any of those solutions.
But you're right - I should've made that clear. Tho, one could make the argument that you also could've made ur point in a slightly less presumptuous, arrogant and wannabe superior way
- H

hhaznadar85 said:
Thank you for your response. Yes, I should have mentioned that I did do some research prior to posting, but the results I found, all either (as you link to) required Magisk SU, or (official?) CyanogenMod/LineageOS based ROM's (as shown here: https://labs.xda-developers.com/store/app/com.bhb27.isu ).
The reason I posted my question being that I am using SuperSU and the unofficial LineageOS 15.0 by vache (https://forum.xda-developers.com/g5-plus/development/rom-lineageos-15-0-t3673573 ), and therefore - by all definitions - am not eligible for any of those solutions.
But you're right - I should've made that clear. Tho, one could make the argument that you also could've made ur point in a slightly less presumptuous, arrogant and wannabe superior way
- H
Click to expand...
Click to collapse
Didn't intend to be arrogant. Sorry for giving you that impression. I'm using Los 15 by vache too. In 'the old days' I used SuperSU, but, imho, that's outdated. Magisk has become the new standard for me, in combination with the safeteynet fix, it's perfect. It passes the safeteynet and you can download and use all 'root critical' apps like Pokémon Go, Netflix, Snapchat, etc.
{
"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"
}

smitharro said:
Didn't intend to be arrogant. Sorry for giving you that impression. I'm using Los 15 by vache too. In 'the old days' I used SuperSU, but, imho, that's outdated. Magisk has become the new standard for me, in combination with the safeteynet fix, it's perfect. It passes the safeteynet and you can download and use all 'root critical' apps like Pokémon Go, Netflix, Snapchat, etc.
View attachment 4297590
Click to expand...
Click to collapse
No problem
Cool, thanks. I have been away from "the android game" for some years, but have just recently got this Moto G5.. so yea, I don't really know what's "new" in the world of android customization. When I was doing this last time, it was all about Superuser, CM, Xposed framework, and apps like 4ext, a2sd, titanium, etc.. the old times..
Anyways, thank you for the update. A quick question; what would you recommend as the best procedure for switching over to Magisk - can I just flash it over the SuperSU, or would you recommend the whole big backup and clean re-install approach..?
- H

Well, imho you have 2 basic options.
1. Make a Titanium Backup, go to TWRP, wipe cache, dalvik-cache, system and data. Reinstall LOS15, gapps and magisk. After setting up your device reinstall your apps using Titanium Backup. Install the safeteynet fix AFTER the first boot with magisk installed. So basically this is a clean install.
2. Go to TWRP. Wipe just the system partition. Reinstall the rom, gapps, magisk and, after a reboot, the Safetynet fix. All your apps should still be there... No garantee, but it should work.
Good luck!

smitharro said:
Well, imho you have 2 basic options.
1. Make a Titanium Backup, go to TWRP, wipe cache, dalvik-cache, system and data. Reinstall LOS15, gapps and magisk. After setting up your device reinstall your apps using Titanium Backup. Install the safeteynet fix AFTER the first boot with magisk installed. So basically this is a clean install.
2. Go to TWRP. Wipe just the system partition. Reinstall the rom, gapps, magisk and, after a reboot, the Safetynet fix. All your apps should still be there... No garantee, but it should work.
Good luck!
Click to expand...
Click to collapse
Hehe yea, that was pretty much what I was thinking as well.. think I'm gonna go with option 1 - better safe than sorry..
Thanks a lot for your help!
- H

OnePlus 6t root storage full

I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
{
"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"
}

Vinitthacker said:
I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
View attachment 5185617
Click to expand...
Click to collapse
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.

Timmmmaaahh said:
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.
Click to expand...
Click to collapse
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?

Vinitthacker said:
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?
Click to expand...
Click to collapse
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.

Timmmmaaahh said:
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.
Click to expand...
Click to collapse
Thanks a lot for the help brother