Related
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
I finally got root to work, but now some apps when requesting root re-boots my phone.
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
In regard to all fo the problems below:
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
wowens0822 said:
I finally got root to work, but now some apps when requesting root re-boots my phone.
Click to expand...
Click to collapse
theguitarhero94 said:
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
Click to expand...
Click to collapse
BigRed35m said:
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
Click to expand...
Click to collapse
eddiecanuck said:
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
Click to expand...
Click to collapse
Listen up guys I'm assuming most of you are bone stock and freshly unlocked the problem is the SuperSU APP it is stated in the OP for the unlock method and most of the root threads around here that currently the binaries we have for supersu that is flashed in recovery during the root process are not compatible with the SuperSU APP from the market. Downloading "superuser" from the market will fix all of your problems.
download this > https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=nav_result#?t=W10.
Until further notice this will be necessary. There are some people that have hacked in different binaries for their updates/roms just make sure you read OP's first before tryingto switch back to the SuperSU app.
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
eddiecanuck said:
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
Click to expand...
Click to collapse
Did you make a NAND b4 supersu app installed? Revert if so if not i recommend UKB in the development sections its a solid rom right now with lots of options. I'd say fix it now so it doesnt bite you later. Also you could try freezing in tibu then using tibu to uninstall SuperSU that is.
I did an uninstall updates for SuperSU to get it back to what was flashed, and I can uninstall Superuser. Haven't done a NAND yet but will. Looking at UKB, was going to stay stock for a while but after looking at that I probably won't.
Most likely flash it tonight, has some nice features. Thanks again for the input.
What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
androidobsessed said:
What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
Click to expand...
Click to collapse
If you have root and the app works dont worry about it.
androidobsessed said:
What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
Click to expand...
Click to collapse
You can always download superSU from play store or from the xda forums and flash it with a customer restore
Sent from my HTC One using xda app-developers app
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
srv2D said:
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
Click to expand...
Click to collapse
Do you have a custom recovery installed? If not, you should. If you do, then you should be able to just install the latest zip from Chainfire to get your binaries up to date and working properly.
Install this via custom recovery (CWM or TWRP) http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
srv2D said:
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
Click to expand...
Click to collapse
UPDATE: Thank you so much! I installed this and now SuperSU works just fine, Titanium Backup works fine, and I can still use GravityBox!:laugh:
:highfive:
Hello everybody,
There has been an confusing about the in-build root of LineAgeOS. Wether is is there or not. Well it's only available for ADB. Anyway, I have been browsing the web for a solution and I've come across this site from the Lineage Team that let you download a add-on for Lineage that enables the built-in root.
NOTE THAT THIS IS NOT CHAINFIRE'S SUPERSU ZIP.
If you want SUPERSU go to this link:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So I'm not gonna hold you any further.
Here is the link to the site.
DOWNLOAD:
https://download.lineageos.org/extras
Have fun with Root on your unofficial Lineage ROMs and Lineage based ROMs:good:
Greetings,
Paulo
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
Thats very true. Thanks for the tip:good:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
Do a full unroot in SuperSU, it will reboot automatically, just in case reboot again, then install the Root add-on with TRWP or any custom recovery.
Report back if it works:good:
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
American_Jesus said:
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
Click to expand...
Click to collapse
This thread is not only for J5. I made this so that everyone could see it.
paulo boë said:
This thread is not only for J5. I made this so that everyone could see it.
Click to expand...
Click to collapse
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Like magisk hide, iSU can disable or hide the cm-su. Should work with app like Snapchat and Pokemon Go.
Why-Fi said:
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Click to expand...
Click to collapse
I guess that is a no that it didnt work Cant you at all boot into recovery?
paulo boë said:
I guess that is a no that it didnt work Cant you at all boot into recovery?
Click to expand...
Click to collapse
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Why-Fi said:
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Click to expand...
Click to collapse
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
paulo boë said:
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
Click to expand...
Click to collapse
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Why-Fi said:
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Click to expand...
Click to collapse
Thanks, you too:good:
paulo boë said:
Thanks, you too:good:
Click to expand...
Click to collapse
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
reversegear said:
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
Click to expand...
Click to collapse
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
paulo boë said:
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
Click to expand...
Click to collapse
I'm using RR nougat
Root options not available in developers option...
Anyway I'll search for something which does the job. I'll let u know if I find something
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
pretty much I get same result on Magisk since if I need to bypass root check I just need to disable in built root or Magisk, since Magisk doesent pass Safety net.
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
ProdigyThirteen said:
So after having a metric f**k ton of issues trying to get a custom recovery to work on 6.0.1, I gave up trying to install a custom rom and eventually went back to stock unrooted. After updating to 7.0 and waiting a bit, I gave it another go and managed to get TWRP to work and rooted my phone. Now I'm looking to install a custom ROM and have a few questions.
Is there anything I should know before going in? Any prerequisites I need to get before/after flashing a custom ROM so certain features will work?
Can I use any custom ROM that is listed as compatible with 7.0/G925F? Or do I have to be more specific as to what version I get?
What should I keep an eye out for? Any features that are good/bad?
Anything else I should know?
As for my choices, it's currently between Nemesis and Noble. Anyone used either and care to share your experience? Any other recommendations?
Click to expand...
Click to collapse
The first and most important thing to do is make a backup. A nandroid backup is fine but make sure you back up your EFS folder. If this gets corrupted you will corrupt your IMEI and have no signal permanently. So backup efs and store somewhere safe like your pc.
I recommend doing full wipe before installing a custom ROM just so it's a clean install.
After that your pretty much good to go.
You can use any ROM that's compatible for your model only. So any G925F ROMs will work fine. Most support a number of models like G925F/I/V etc.
Most s6 edge custom ROMs are stable and have very few issues, and if there are issues then generally there are fixes for them.
Nemesis and Noble are both good stable ROMs. Also Omega ROM is a good choice. But my favourite that I used for over a year is CarHD ROM. It's customisation is endless.
One more is AlexisROM. Good ROM used for a while.
Hope this helps.
callumbr1 said:
snip
Click to expand...
Click to collapse
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Edit: solved the MagiskHide not showing.. I'm an idiot and forgot it was under settings and not enabled by default.
ProdigyThirteen said:
So after a painfully long download, I installed CarHD and I'm liking everything I see. My only issue is trying to get SafetyNet to pass. I've removed SuperSU, installed Magisk and its kernel and now whenever I check SafetyNet, it fails with "CTS profile mismatch". I've looked around on a few different threads about it and everything I've tried hasn't worked. Mostly because they revolve around MagiskHide, which isn't showing up for me.
My first thought is to completely uninstall magisk, go back to a stock kernel and start off fresh, but I'm not going to do that just yet as I wanted your opinion first. Is that the best thing to do or would it cause more harm than good?
And if it wasn't already obvious, yes I'm still pretty damn new to this, but I'm trying not to **** up as I quite like my phone working.
Click to expand...
Click to collapse
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
callumbr1 said:
You don't need any kind of custom kernel to use magisk, or at least you shouldn't. It should work perfectly fine with stock.
Try updating magisk manager app from xda labs and magisk hide should appear.
If it does then just enable magisk hide and hide all apps that require safety net, hide knox also if it's still on the ROM. Then you should pass.
If this fails I recommend to flash the ROM again, no need to wipe data and then choose magisk in aroma installer and flash again.
Let me know if you need help :good:
Click to expand...
Click to collapse
Fixed the MagiskHide issue, but simply enabling hide on the apps that I want to use doesn't work. I tried reinstalling the ROM as you said, but it never gave the option to choose Magisk over SuperSU. Then when I switched from SuperSU to Magisk, SuperSU was removed normally, but Magisk is installed and saying I don't have root access. Flashed Magisk kernel from CarHD as TWRP wasn't allowing install of Magisk with the other that came stock, then flashed Magisk again. Magisk saying I now have root access, but Magisk isn't installed and when I try to install it, the app crashes. Currently checking Magisk threads for a solution for that.
Tried reinstalling Magisk and clearning data/cache to no avail... I still have root access, but can't install Magisk through the manager.
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
ProdigyThirteen said:
Uninstalled Magisk, flashed stock kernel, re flashed magisk and now SafetyNet is passing, but still can't install Magisk through the Manager
Click to expand...
Click to collapse
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
callumbr1 said:
If you have root access and safety net pass then I don't understand what you mean by can't install magisk through the app?
So you have magisk manager app installed?
Click to expand...
Click to collapse
Yeah, the manager is installed, but when I open it, it says there is an update available and under status says Magisk is not installed, v130 is available. There is no option to enable Magisk hide or any other extras available for download.
Screenshot of magisk
ProdigyThirteen said:
Screenshot of magisk
Click to expand...
Click to collapse
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
callumbr1 said:
It's the magisk manager app. You need to install the new one. Delete the one you currently have installed and download latest one from magisk Thread here or from xda labs.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Should look similar to this.
Click to expand...
Click to collapse
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
ProdigyThirteen said:
Tried to uninstall it, no option to. Downloaded something to uninstall system apps, tried to uninstall it, still there. Tried to install a new app over it, gave an error saying app already installed with same name.
Click to expand...
Click to collapse
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
callumbr1 said:
You should be able to uninstall it with titanium backup or any app to remove system app.
Infact you should be able to just remove it as you would remove any other app.
Use what you used before to remove it when it didn't go and then reboot and it should go. If not flash the uninstaller from magisk thread.
Then start again, if you flash the newest magisk from the thread on here then it also should install newest magisk manager app.
Click to expand...
Click to collapse
No app that removes system apps can remove Magisk Manager it seems... TB says "Failed to locate the apk file", NoBloat Free says it removed it, but even after rebooting it's still there. Flashing the uninstall doesn't remove it either. I would manually uninstall through root explorer, but there's a risk I delete the wrong file and screw something else up.
Edit: Found Magisk Manger in root/system/app/magisk, backed it up, deleted it, rebooted, seems to be gone. Will try intalling new APK
Fixed it. Had to manually delete the apk, then installed the updated version and now it's showing as magisk is installed perfectly fine. Thanks for all the help.
Third and hopefully final edit: Getting kernel is not seandroid enforcing. Tried uninstalling magisk, flashing stock kernel, reinstalling magisk and still getting it. But it doesn't seem to be messing with anything, can still boot fine, safetynet is still passing so all looks pretty good.
callumbr1 said:
snip
Click to expand...
Click to collapse
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
ProdigyThirteen said:
No point starting a new thread when I can just ask here as it's a somewhat follow on question. I can't seem to get V4A to work. I've installed the module from Magisk, installed the APK, restarted my phone, loaded up the app and checked the driver just for it to say Status: Abnormal / Audio Format: Unsupported. Can't seem to find anything about a fix for it, been searching for about an hour, so either I'm blind or there's nothing on it (I'm betting it's the former).
When I open the app, I get a message prompting me to update/install the driver, despite it already being installed through Magisk. I've tried both the standard v2.5.0.5 apk and Nougat test fix, standard doesn't do anything and test fix has update/install prompt.
Click to expand...
Click to collapse
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
callumbr1 said:
Good stuff. As for the seandroid message on boot you can just ignore it. It's not an error and will stay but doesn't affect anything.
As for viper first thing to try is remove the currently installed app and remove it from magisk manager modules.
Install busybox.
Freeze sound alive with titanium backup (don't delete just freeze)
Then flash this through TWRP
https://mega.nz/#!CV5wQYSa!i-V1UvJ_Lh9YoZDPN9rUUXuJNgXWcXRlhBE83fYH7e8
After this if it doesn't work let me know and I'll tell you next steps.
Click to expand...
Click to collapse
Tried that, still getting abnormal/unsupported.
ProdigyThirteen said:
Tried that, still getting abnormal/unsupported.
Click to expand...
Click to collapse
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
callumbr1 said:
Now check that magisk module is enabled and the audio modification module is enabled.
You may also need a permissive kernel to get viper to work.
Click to expand...
Click to collapse
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
ProdigyThirteen said:
Googling permissive kernel is just coming back with a bunch of threads saying get a terminal emulator, type su / setenforce 0. Tried that, trips safetynet and doesn't change Viper.
I feel like it's not changing viper because I need it to stick through reboots, enable it, then reboot, but it's not persistent. How would one go about making it stick?
And honestly, is viper really worth all this hassle?
Click to expand...
Click to collapse
You can try Hacker kernel
https://forum.xda-developers.com/ga...l-hacker-kernel-s6-universal-t3254487/page234
Or arter kernel
http://arter97.com/browse/exynos7420/kernel/22.0/g925fi/
As for is it worth it? In my opinion yes 100%.
It depends really if you like the stock effects enough. Personally I love music and love been able to customise it. It sounds 10000x better in my opinion.