Hi
Im trying to root and install custom recovery for my oneplus 7t pro (hd1913, 10.0.7)
1. When i tried to root with magisk i was able to root and flash the modded boot.img, root seems to work only like 20%, tired to install module from magisk like vanced utube and worked
but everything else requires root like ad removing and bloatware removing cannot work.
2. When i tried to install twrp it almost every time failed, i only succeded to get it to boot and not really flash, guess its not available for the device yet.
I dont really mind about the twrp, ill install it if it will ever get out.
But the root, i have to make it work, its only works partially, what can i do?
THANKS AHEAD!
adarabadian said:
Hi
Im trying to root and install custom recovery for my oneplus 7t pro (hd1913, 10.0.7)
1. When i tried to root with magisk i was able to root and flash the modded boot.img, root seems to work only like 20%, tired to install module from magisk like vanced utube and worked
but everything else requires root like ad removing and bloatware removing cannot work.
2. When i tried to install twrp it almost every time failed, i only succeded to get it to boot and not really flash, guess its not available for the device yet.
I dont really mind about the twrp, ill install it if it will ever get out.
But the root, i have to make it work, its only works partially, what can i do?
THANKS AHEAD!
Click to expand...
Click to collapse
TWRP doesn't work which has been stated many times in the thread.
And what do you mean with ad removing and bloatware removing? How and what app?
Sent from my OnePlus7TPro using XDA Labs
adarabadian said:
Hi
Im trying to root and install custom recovery for my oneplus 7t pro (hd1913, 10.0.7)
1. When i tried to root with magisk i was able to root and flash the modded boot.img, root seems to work only like 20%, tired to install module from magisk like vanced utube and worked
but everything else requires root like ad removing and bloatware removing cannot work.
2. When i tried to install twrp it almost every time failed, i only succeded to get it to boot and not really flash, guess its not available for the device yet.
I dont really mind about the twrp, ill install it if it will ever get out.
But the root, i have to make it work, its only works partially, what can i do?
THANKS AHEAD!
Click to expand...
Click to collapse
Every app, tried like 5 different apps that uses root, if u have app that works for u can u tell me so i test it please?
Thanks
adarabadian said:
Every app, tried like 5 different apps that uses root, if u have app that works for u can u tell me so i test it please?
Thanks
Click to expand...
Click to collapse
Go to mag , settings, systemless host then install adaway and your done
and you dont need to flash the magisk patched img. just boot it up in fastboot. then go to magisk and do install direct. then restart and wait to unplug you phone.
Verstuurd vanaf mijn OnePlus 7T Pro met Tapatalk
Related
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Wrong forum. This is a dev forum, not Q&A. Rooting w/out custom recovery is possible with chainfire's autoroot flashable zips. But still you won't receive OTA updates b/c since Lollipop the validation process has changed and you need to be pure stock. This also includes the recovery iirc.
Moved to correct forum
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
giannisgt said:
Hello. I want to root my nexus 9 without installing any custom recovery. I want this because i want to receive google updates...
And sont suggest me about "install custom recovery and when you need flash the stock etc.)
Thanks in advance
Click to expand...
Click to collapse
brownog1 said:
Just root it. You don't need custom. Use the nexus tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
You will not receive OTA updates if you are rooted.
cam30era said:
You will not receive OTA updates if you are rooted.
Click to expand...
Click to collapse
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
HansiHusten said:
Since when does rooting prevent OTA updates? Thats the first time I hear that.
On my N10 I always booted only into TWRP (fastboot boot twrp.img) and flashed from there the supersu.zip and still got OTAs without any issues.
I sold my N10 and my N9 is currently on the way to me so Im preparing everything to unlock and root it as soon as it arrives, thats why I am checking all those threads right now regarding root.
Well, I read only about this root injecting methode which doesnt sound very good to me and the nexus toolkit methode. Isnt it possible to boot into TWRP like I did before? Why shouldnt this work on the N9?
Click to expand...
Click to collapse
My bad. I should have said you will not be able to install OTA if you are rooted. The install script checks system files and if anything has been modified, it aborts installation. Your better option is to fastboot flash the Google factory image.
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
HansiHusten said:
So what is the current working root methode for 5.1.1 without losing OTA or flashing any recovery?
This injecting thing, nexus toolkit or another way?
--edit--
seems like CF-Auto-Root (special version for the N9) works also? Im right now having 40 windows open in chrome, trying to find the best way...
Question is, does it still work for 5.1.1?
Again: Why should not boot into TWRP and then flash the supersu zip not work? Any issues with that?
Please share your experience. Thanks
Click to expand...
Click to collapse
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
cam30era said:
It's a Nexus device. The easiest root method is to fastboot flash TWRP, the download SuperSU and flash it in recovery. Link here > http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Click to expand...
Click to collapse
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
HansiHusten said:
Alright, so the 'usual' way works as always, thanks for clearing this up. Was wondering if there were still some issues with rooting the N9.
So you suggest the beta version of supersu, will give a try first to the stable one, if this doesnt work ill try the beta.
Thanks m8
Click to expand...
Click to collapse
Stable should work for Lollipop. Beta necessary for M. And beta works fine on Lollipop, too, FWIW.
I'm sure everyone has heard of the Tap 10 promotion Google is running.
I'd like to take advantage of this but having BareCee installed on my phone, I cannot get Android Pay to accept my credit cards.
I've done some research and it seems like AP doesn't like root or unlocked bootloaders. I've tried a couple Xposed modules (RootCloak and No Device Check) to try and trick it into working without success.
Anyone have any ideas on how to get it to work?
Thanks!
estockda said:
I'm sure everyone has heard of the Tap 10 promotion Google is running.
I'd like to take advantage of this but having BareCee installed on my phone, I cannot get Android Pay to accept my credit cards.
I've done some research and it seems like AP doesn't like root or unlocked bootloaders. I've tried a couple Xposed modules (RootCloak and No Device Check) to try and trick it into working without success.
Anyone have any ideas on how to get it to work?
Thanks!
Click to expand...
Click to collapse
If you're running V2, try flashing the stock host file in post #2. I left the blocking one in it by mistake.
That might help, but I'm not sure.
estockda said:
I'm sure everyone has heard of the Tap 10 promotion Google is running.
I'd like to take advantage of this but having BareCee installed on my phone, I cannot get Android Pay to accept my credit cards.
I've done some research and it seems like AP doesn't like root or unlocked bootloaders. I've tried a couple Xposed modules (RootCloak and No Device Check) to try and trick it into working without success.
Anyone have any ideas on how to get it to work?
Thanks!
Click to expand...
Click to collapse
you need to uninstall xposed and busybox then go into supersu and unroot then reboot. once rebooted install android pay...make sure it works then you can reinstall supersu, busybox and xposed. i know this method works for sure on barecee.
thegold3nchild said:
you need to uninstall xposed and busybox then go into supersu and unroot then reboot. once rebooted install android pay...make sure it works then you can reinstall supersu, busybox and xposed. i know this method works for sure on barecee.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
thegold3nchild said:
you need to uninstall xposed and busybox then go into supersu and unroot then reboot. once rebooted install android pay...make sure it works then you can reinstall supersu, busybox and xposed. i know this method works for sure on barecee.
Click to expand...
Click to collapse
That worked! Android Pay let me add my cards. I'm going to reinstall everything now.
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.
installed miuimix 12.0.2 but banking apps didnt work, i looked t the info and it seems they root and add magisk within the bootloader i guess? (never used or wanted to use before) so i installed magisk manager to uninstall it completely, and now it is stuck.
what do i need to do from recovery to get workign phone again?
and what rom isnt rooted / magisk installed so i can use banking apps. i dont want to be messing around with "hiding" root as i dont believe it will work consistently or may get patched in near future..
t3rm3y said:
installed miuimix 12.0.2 but banking apps didnt work, i looked t the info and it seems they root and add magisk within the bootloader i guess? (never used or wanted to use before) so i installed magisk manager to uninstall it completely, and now it is stuck.
what do i need to do from recovery to get workign phone again?
and what rom isnt rooted / magisk installed so i can use banking apps. i dont want to be messing around with "hiding" root as i dont believe it will work consistently or may get patched in near future..
Click to expand...
Click to collapse
Use Miui eu. It's a debloated miui that's not rooted by default.
Yep, had to fastboot official ROM first to get phone working then flash miui EU.