Hey, so I flashed a LOS 17.1 GSI on my SM-T295, and then installed Magisk 21.4 and the latest manager. After enabling MagiskHide and rebooting, my device "bootloops" in a weord way. Turn it on, wait for android to load up, wait a bit, shutdown, reboot. You can use the apps and the Manager, but only until it reboots. Wait a bit, android loads up again, wait for it... Reboot!
I just disable MagiskHide and reboot (or just wait for it to do it by itself), then wait and it's solved! However, I feel like that setting might help me with bypassing the SafetyNet test, and I would like to fix that issue so it doesn't happen again, even with the setting enabled.
I've made a post on this already (let me get the link for it, i'll edit later), but it isn't as clear and my explaination of the issue wasn't accurate. However, I explain some extra stuff that mayyyyyy have influenced on the issue, like how I installed TWRP, LOS, OpenGApps and Magisk, and some issues on the process of installing them (like the encrypted(?) folders and files mentioned on my prevoius post on this, this issue is gone for now), but idk.
Any ideas thanks in advance bye pls reply?????????
Can you tell how did you root your device please
Related
I have read through many messages, but they left me rather confused... What exactly needs to be done for Android Pay to be working on N5 with Lineage 14.1? I have tried locking the boot, switching to untampered, disabling SU, using Magisk, etc. Nothing works...
And additional question: if anyone has that particular combination working, could they describe how it works? In particular, does SU need to be turned off all the time (I use root from time to time, e.g. with Titanium Backup).
Thank you in advance!
I use DU 11.4, franco kernel and magisk v12. It works. All you need to have is to have all 3 chdckboxes green in magiask, to do so, enable magisk hide in settings and select android pay
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
After two years being stuck on an unrooted phone (Huawei), I'm thrilled to have everything working on OP7 x TWRP x Magisk.
On several threads I have read suggestions of Xposed modules that could be interesting, and saw that @topjohnwu published a thread with an Xposed installer apk and Xposed module for Magisk, which sounds amazing.
My question is: on OnePlus, does this work well, or would it be asking for trouble? The last thing I want now that everything is working is to make a wrong move that gets me into boot loops.
Also, if this is confirmed to work well, I see that there are several Xposed modules in the Magisk download section.
Is it "Xposed Framework, v90-beta3 created by rovo89"? Or the Tai Chi one, or the Riru ones?
Thanks for any advice!
Use edxposed, no problems so far for me
My biggest question is with Snapchat. I've read people getting banned because of using Xposed (even if no Snapchat specific module's are used).
Can anyone confirm or deny this? I just want to use it for a couple of modules like Amplify.
Its a bad idea! Snapchat thinks you use 3rd party app... Been locked out 3 times now...
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
who ah way said:
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
Click to expand...
Click to collapse
That isn't edexposed and isn't supported on pie
Arden144 said:
That isn't edexposed and isn't supported on pie
Click to expand...
Click to collapse
Thank you!
Will try edexposed on the next install, after backing up.
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
who ah way said:
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
Click to expand...
Click to collapse
Either. I used YAHFA with no issues for what i needed. Then i tried SandHook out of curiosity and found no difference.
Asking for trouble
Thank you both.
After TWRP backup, installed edexposed which involved three steps:
- riru exexposed core module (in Magisk)
- riru edexposed module by yahfa (Magisk)
- edexposed installer app (from GitHub)
EdXposedInstaller_v2.2.4-release.apk
https://github.com/solohsu/XposedInstaller/releases
System rebooted, SafetyNet status OK in Magisk.
As far as y'all know is this list of modules known to work on OP7?
Wouldn't even know where to start… But curious.
Edit: when I went to do a new Backup, the TWRP menu was unusual (it asked new questions about modifying the system). Decided to backpedal and restore to before exposed installation.
In the end, I just don't know enough to understand what risks I'm taking. In the hands of an expert user, it's probably safe, in mine, it's asking for trouble.
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
You need to install drivers twice.
Mhm, sure.
Though, to be honest, this was among the things I tried before. No difference.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
Uninstall your current Viper and reboot. Sideload Viper 2.7.1.0 apk or use the Magisk module. Install the driver and reboot. Once back in Android, install the driver again. Should work. If not, go into V4A settings and put in compatibility mode.
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
To repeat my question from another thread, i have the same issue and 2.7 only works for me when the "attach audio effects" option is checked and that introduces quite significant audio lag when skipping tracks.
I also can't seem to get rid of the permanent notification without breaking vipers functionality.
Is there any fix for this? Or a way to properly install 2.5.0.5?
Luxor144 said:
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
Click to expand...
Click to collapse
Lol. Forgot to suggest 2.7.1 and then install drivers twice.
Still an issue in 10.3.4
}{Alienz}{ said:
Still an issue in 10.3.4
Click to expand...
Click to collapse
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
GeekMcLeod said:
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
Click to expand...
Click to collapse
Tried to find that one again, too.
I ended up installing the Audio modification library magisk module, rebooting, deactivating (not uninstalling) that module and then installing the current Viper 2.7.1.6 module.
May have rebooted after that before installing drivers and therefore rebooting again, can't remember though.
But it does work perfectly and the guide did go something like this.
Also possible that a Viper update fixed the issue.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.