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
Related
When installing apps the storage manager is not registering the correct size to start off with. For instance a 1.5gb app is showing as total size of maybe 59mb. Under data for the apps it shows maybe 200kb.
Now the worse part is when uninstslling apps it does not race the data for the app. In order to remove the data and get my space back I have to boot into recovery and wipe cache.
Tried removing external SD card and trying it again and it's th deer same issue.
Also when attempting to move data to SD card it doesn't seem to really move anything but takes at least 30 seconds to do it and still requires the SD in the 0hone to run the app
Does anybody know what's up here and willing to tell me?
Thanks maybe.
Yes I'm about to smash this **** ING thing.
Nickvanexel said:
Yes I'm about to smash this **** ING thing.
Click to expand...
Click to collapse
Try Odining the stock tar from www.sammobile.com
{
"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"
}
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Nickvanexel said:
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Click to expand...
Click to collapse
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
bilgerryan said:
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
Click to expand...
Click to collapse
So that means at this point you wouldn't really need to wipe before installing wicked rom anymore?
Also decided against any over clocking now, changed to performance governors and things are working great now, especially games. No hitching, we're I was getting 10fps or less I cod strike team it's now 30.. so if I install a rom it will be wicked, especially the function on it "fix external SD write" fixes my storage management issues than that alone would be great and the debloat and performance tweaks would be a great bonus.
Thanks.
How to pass SafetyNet on unlocked Bootloader and custom ROMs
in this guide we'll go over how you can pass SafetyNet on custom ROMs, you need to have Magisk installed, check AIO guide for that
you need to pass basic integrity first, this guide will not help you if you broke that
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
if you're on Stock and only have an unlocked bootloader, simply flashing Magisk should be enough to pass SafetyNet, if you're on a custom ROM, you need the following extra steps.
NOTE: if you just need to pass SafetyNet, follow the guide, if you want access to all Google Play apps which you can access on Stock, use this instead
Open Magisk Manager and go to the Downloads section, search for "MagiskHide Props Config" and install it, also search for "Busybox for Android NDK" and install it, then reboot.
{
"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"
}
install Terminal Emulator and open it
type the following commands, grant root access when asked
Code:
su
props
then follow the prompts to edit your device fingerprint by typing the corresponding command shown on screen
Edit device fingerprint
Pick a certified fingerprint
Xiaomi
Xiaomi Mi A2
y
and then reboot
After rebooting, clear data for Google play
You should now pass SafetyNet
--reserved--
Hmm
How about having xposed??
miremo said:
How about having xposed??
Click to expand...
Click to collapse
You'll never pass safetynet with xposed, it's impossible
Nebrassy said:
You'll never pass safetynet with xposed, it's impossible
Click to expand...
Click to collapse
I have friends who was able to do it, but they won't spoil me. I've seen it.. That's why I'm trying to reach xda and read some articles here.
updated to access all google play apps that you can access on Stock (Netflix, Asphalt 9 etc), you'll need to use another module
I did everything but it sill doesn't work here. ?*
malabarth said:
I did everything but it sill doesn't work here. ?*
Click to expand...
Click to collapse
Use SafetyPatcher v3 magisk's module.
Download zip with magisk
Reboot to twrp
Install zip
Not work for me if instal with magisk
alcopsy said:
Use SafetyPatcher v3 magisk's module.
Download zip with magisk
Reboot to twrp
Install zip
Not work for me if instal with magisk
Click to expand...
Click to collapse
doesn't work, after following the OP and your steps using SafetyPatcher V3. I still can't see Netflix on my Play Store eventhough the device now is Certified
Cican49 said:
doesn't work, after following the OP and your steps using SafetyPatcher V3. I still can't see Netflix on my Play Store eventhough the device now is Certified
Click to expand...
Click to collapse
Netflix isn't showing up on any rom anymore, including stock, get it from apkpure
Nebrassy said:
Netflix isn't showing up on any rom anymore, including stock, get it from apkpure
Click to expand...
Click to collapse
but it showed up on stock locked bootloader. makes me wonder
Cican49 said:
but it showed up on stock locked bootloader. makes me wonder
Click to expand...
Click to collapse
Netflix don't show in Play store for unlocked bootloader device
I do not know if anyone here has gone through this .. but when I install OxygenOS in my 6T the system is almost full. In any other ROM the ROOT is normal
I already gave wipe in vendor, system, date by TWRP and did not solve
{
"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"
}
You could always resize your system partition (...apparently)
... You didn't hear it from me
lucas_777 said:
I do not know if anyone here has gone through this .. but when I install OxygenOS in my 6T the system is almost full. In any other ROM the ROOT is normal
I already gave wipe in vendor, system, date by TWRP and did not solve
Click to expand...
Click to collapse
odd. May I ask what application you're using to show the status of your storage so I can try it out myself. I'm rooted running a custom ROM and kernel. Maybe its the app misreading/analyzing your storage?
Pain-N-Panic said:
odd. May I ask what application you're using to show the status of your storage so I can try it out myself. I'm rooted running a custom ROM and kernel. Maybe its the app misreading/analyzing your storage?
Click to expand...
Click to collapse
He's using Solid Explorer, you can see it in the pic where it say rate 5 stars. I'm using Mixplorer and mine is showing 1.13gb free on SkyDragon.
Mines showing fine with that explorer...
lucas_777 said:
I do not know if anyone here has gone through this .. but when I install OxygenOS in my 6T the system is almost full. In any other ROM the ROOT is normal
I already gave wipe in vendor, system, date by TWRP and did not solve
Click to expand...
Click to collapse
Are you on OOS beta 10? If so update to 11 and see if that fixes it.
Some_Random_Username said:
@Funk Wizard
OB11 full zip: https://otafsg1.h2os.com/patch/amaz...6TOxygen_41_OTA_040_all_1905232342_d95410.zip
AFH mirror: https://www.androidfilehost.com/?fid=6006931924117883723
MD5: df54f2b46d94a8d77e61599a9d6cbece
Incremental from OB10: https://otafsg1.h2os.com/patch/amaz...en_41_OTA_038-040_patch_1905232342_897dc6.zip
AFH mirror: https://www.androidfilehost.com/?fid=6006931924117883722
MD5: 10e7e074fffeb5cf8553c9b9db0d7136
Click to expand...
Click to collapse
I am on stock OOS 9.0.13 and only have 80MB free on my /system partition.
Since the /system partition is supposed to be read only then it wouldn't really matter if it is full, nothing will be writing to it anyway.
I have never had issues because of this and I remember even with my 5T the /system partition was always 99% full.
So there's probably nothing to worry about.
ebproject said:
Are you on OOS beta 10? If so update to 11 and see if that fixes it.
Click to expand...
Click to collapse
I'm in beta 11
Jager said:
I am on stock OOS 9.0.13 and only have 80MB free on my /system partition.
Since the /system partition is supposed to be read only then it wouldn't really matter if it is full, nothing will be writing to it anyway.
I have never had issues because of this and I remember even with my 5T the /system partition was always 99% full.
So there's probably nothing to worry about.
Click to expand...
Click to collapse
Apps that need root to modify something, give problems. For example, I use the Switf Installer to change all colors to black and I have problems. It was not like this before.
lucas_777 said:
I'm in beta 11
Click to expand...
Click to collapse
If you look in the OB11 thread there are a lot of people with your same issue. I don't think there's a fix, other than using the MSM tool and going back to stable.
Oh, and FYI, if you use TWRP to extend the storage of your system partition, you'll lose everything.
lucas_777 said:
Apps that need root to modify something, give problems. For example, I use the Switf Installer to change all colors to black and I have problems. It was not like this before.
Click to expand...
Click to collapse
I just checked and it does seem that Swift installer modifies the /system partition. I have never had any issues with it though.
If you need more space in /system delete an app you don't use like Google Movies or Google Duo or something.
Or if you want all the space you can get then use this debloater script from Tomatot ( https://forum.xda-developers.com/on...ol-tomatot-debloater-basic-script-to-t3869427 )
lucas_777 said:
Apps that need root to modify something, give problems. For example, I use the Switf Installer to change all colors to black and I have problems. It was not like this before.
Click to expand...
Click to collapse
It won't be a problem if you use systemless module for it:
https://docs.google.com/spreadsheet...RQCNQG0WyLalp3Py59Dn0J0/pubhtml?gid=28098273#
I'm using systemless substratum themes and have no problem with little space.
Sent from my OnePlus6T using XDA Labs
Hello, I have a new one plus 8 pro and I am rooted. I also have a Galaxy watch and when I install Samsung pay on the watch it says call customer service device has been compromised even though I have magiskhide for all the Samsung modules. Does anyone have any ideas how to get this working?
Thank you in advance...
I have the same problem. Completely stock. So I wonder if it's a Samsung issue. I had the 6t rooted and I was able to use Samsung pay without any problems
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?
Valiante said:
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?
Click to expand...
Click to collapse
Sorry - the Pixel was like 4 phones ago. I dont have any further info for you...
aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
UPDATED Post : see next post for my solution that worked.
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!
plepew said:
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!
Click to expand...
Click to collapse
UPDATE,
Got it all to work!
Preparation:
- Install Galaxy Wearable
- Update Watch to the latest
- Install SP Watch Plugin (do not launch it at all)
Magisk Setup:
- Hide the following apps in MagiskHide: Hit the shield, Hit "MagiskHide" and select the apps:
a) Google Play Services
b) Samsung Health
c) SP Watch Plugin
* You can add banking apps here as well
{
"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"
}
Next, recommend hiding the Magisk App itself for the setup. Here is how to do it:
- Hit "Settings" (within Magisk App)
- Hit "Hide the Magisk App" (I used MGKSettings).
Magisk will accept it and repopulate itself.
For good measure, I rebooted my device to recovery (TWRP in my case) wiped "Dalvik / ART Cache" and rebooted to system.
Once rebooted, go to the SP Watch Plugin App INFO (Do not launch the App), got to Storage & Cache & Clear Storage & Cache (should be 0 on both) for good measure!
Launch Galaxy Wear and (Strongly Recommended) scroll down to setup Samsung Pay and follow the steps. **(I don't recommend doing the SPay setup through the Watch Plugin.)**
If you get a notice within 10 seconds saying that the device is not secure (can't remember the message), you may have missed something and you need to start over with clean install of the SP Watch Plugin (storage & cache cleared).
Worst case they may have updated the Samsung Pay, Samsung Health Apps & OOS and it's been blocked again. Therefore we would need to restart the whole process from scratch or find another workaround.
PS. Some of you would probably like to restore or Un-Hide the Magisk App, so I went ahead and did it....so far SPay seems to be working. I have not reboot my device neither, which I rarely do. (I have rebooted my device several times since this post)
For any reason, in the coming days, there is an issue of any kind, I will report back here. If not, it's all good!
Hopefully this can help some of you out there!
worked for me, thanks a lot
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