Related
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
To do that, you must uninstall the Towelroot app (shouldn't be too hard) then, to finish it off, try running these commands in an adb shell:
Code:
su
mount -o rw,remount /system
rm /system/bin/su
rm /system/xbin/su
mount -o ro,remount /system
exit
You are now unrooted!
Sent from my Nexus 7 using Tapatalk
rootnooby said:
What steps should be taken to Un-root the hdx 7 and reset to stock after rooting with the latest Towel root toolbox and firmware?
Click to expand...
Click to collapse
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
blade22 said:
in SuperSu > settings > fullunroot
and it will unroot your Kindle
and then settings > device > restore factory settings
Click to expand...
Click to collapse
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i have done the same steps and factory reset..faced no Issues.
and may be people facing issues might not have uninstalled xposed module and xposed framework
r3pwn said:
He never said he was using SuperSU. And I wouldn't recommend the factory reset as those have caused many people issues around here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
Thanks for all the great feedback. I should have provided more detail to start. I have a follow up question/clarification. This is what did:
1. Run Towel root - success
2. Followed directions to block ota updates and install supersu. - success
3. With root confirmed, Installed exposed frame work and module from here: http://forum.xda-developers.com/showthread.php?t=2618158 (to get play store and other google apps). - success
4. Activate exposed module and update. - success
5. Installed hdxposed.Apk, enabled it, Rebooted, and play store worked. - success
6. In any order, installed the files from the link. - success
Install play services
Install framework
Install Google account manager
7. Overall, all worked well.
Question:
What is the best way to undo everything I did?
Enable OTA updates?
Update to the latest firmware (basically to get prime music and fix wifi issues I'm having)?
Re-root?
conan1600 said:
I factory reset my 8.9 after rooting 2 days ago. No issues at all except YOU MUST ALLOW OTA UPDATES BEFORE YOU RESET OR IT WILL NOT ALLOW YOU TO REGISTER AND YOU WILL KEEP POPPING BACK TO THE LAGUAGE SETTING AT RANDOM TIMES, I had a hassle re enabling ota after the reset, very annoying. As to Xposed .. I would MAKE SURE you uninstall xposed modules and xposed framework before resetting. I would also recommend putting back to rights ANY changes you make in build prop as well as custom disables of the nav bar. I have ran into problems with other tablets when resetting after nav bar changes.
Click to expand...
Click to collapse
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
brooklynstar220 said:
I ran into the problem with the language repeatedly popping back upbecaus I didn't first re-enabe the OTAs. How did you fix thisissue please? Thanks or you help in advance.
Click to expand...
Click to collapse
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Davey126 said:
You need to reverse the method originally used to block OTAs of which there are several. What version of FireOS are you on?
Click to expand...
Click to collapse
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
brooklynstar220 said:
I am version 13.3.2.4. The problem I am running into at this point is that USB debugging is not working. I have even dowloaded seperate debugging apps and they fail to work giving me errors that it has stopped. I am assuming there is something wrong in that script at this point. Is there any way to fix it? I disabled the OTA updates with KFHDX Toolkit v0.95.
Also I can root and unroot with no problem but can't flash anything because even though it says safe strap is installed it won't boot into recovery.
Click to expand...
Click to collapse
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
I was able to get that version of Safestrap installed and was able to flash roms again but ADB is still not connecting when attached to the computer. Do you think a nanroid restore from my original setup could help fix this?
Davey126 said:
Sounds like you have some deeper problems with the ROM on your device. In your shoes I would install Safestrap v3 (not v4) followed by the SS compatible version of Nexus. This will also address the Google Play/Services issues. Others may suggest unlocking your bootloader. I wouldn't go there given current issues ... even if you could somehow reenable OTA. High risk imo.
Click to expand...
Click to collapse
Thank you for your help with this. What is crazy but was probably a driver issue the whole time, I udated my laptop to Windows 10 and somehing told me to try it again and it worked immediately with the Toolkit and re-enabled the OTA updates. Thanks again.
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.
I love RR7.1 ROM. But some apps like IRCTC connect detects as device is rooted. How do I unroot the ROM? I tried megistic still doesn't help. Any help would be appreciated. Thanks in advance.
micoeyes said:
I love RR7.1 ROM. But some apps like IRCTC connect detects as device is rooted. How do I unroot the ROM? I tried megistic still doesn't help. Any help would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Dirty flash your rom again w/o flashing SuperSU
I believe there is unroot option in SuperSU and Superuser but the answer above is sure win
Open the SuperSU App and go to Settings, under settings you'll find a "Full unroot" option. Click it, and follow the instructions further.
Tried all of em. Nothing seems to work. I'm on official build by sanjay varun. It has buildin cm root. After removal in developer page it shows only disabled n adb options for root access. Still application detects as device is rooted
Magisk ahve a miodule to hide root. Maybe you can try it...
Or SuHide?
After installing xposed on b380 settings stop working. Settings just crash. How install xposed and keep settings working
try older versions of xposed
eddydc1 said:
After installing xposed on b380 settings stop working. Settings just crash. How install xposed and keep settings working
Click to expand...
Click to collapse
Xposed with emui is a bad idea. You will always have one or another thing going wrong. My advice after trying Xposed numerous times with emui, stay away.
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.