Root Permission (SU) Required. - LG V20 Questions & Answers

Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82

Alfanizer said:
Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82
Click to expand...
Click to collapse
You should probably ask this in the viper or su threads as your problem has nothing to do with the v20
Sent from my LG-H910 using XDA Labs

Alfanizer said:
Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82
Click to expand...
Click to collapse
As a constant reminder to myself that root likes to be buggy and/or loose itself,
I just use Magisk su v.16 and everything is flawless. Try Magisk instead or if you want this to be done with SuperSU instead, you this (A Uninstaller for SuperSU, use in TWRP)
https://drive.google.com/file/d/16Cs-DjOaG6bPSctB-gHBzUZY3nNGQINH/view?usp=drivesdk
1. Uninstall SuperSU
2. Then Flash the latest zip of SuperSU.
I hope this has helped you out.

ROOT67 said:
As a constant reminder to myself that root likes to be buggy and/or loose itself,
I just use Magisk su v.16 and everything is flawless. Try Magisk instead or if you want this to be done with SuperSU instead, you this (A Uninstaller for SuperSU, use in TWRP)
https://drive.google.com/file/d/16Cs-DjOaG6bPSctB-gHBzUZY3nNGQINH/view?usp=drivesdk
1. Uninstall SuperSU
2. Then Flash the latest zip of SuperSU.
I hope this has helped you out.
Click to expand...
Click to collapse
Bro i tried to instal magisk 16 but error when installing??

Alfanizer said:
Bro i tried to instal magisk 16 but error when installing??
Click to expand...
Click to collapse
What ROM are you using ?, if you're using stock maybe try formatting the Data Partition only and wiping dalvik cache and cache, then reboot to system. Do the setup, make sure to disable the automatic system updates in the setting under the developer options (Go to about phone and tap the build number 7 times, then go to developer options.) Then once done, reboot to TWRP and flash Magisk 16.0 zip and remember to wipe Dalvik cache and cache before rebooting.
If you are using a custom ROM, then just wipe everything in TWRP and flash the ROM zip, wipe dalvik cache and cache, reboot and go through the setup. Once done, go back to TWRP, flash Magisk 16.0 zip and remember to again wipe dalvik cache and cache before rebooting.
Optional: You can use root permissions to let Magisk do a direct install in the Magisk Manager apk.

Related

How to change Developer Options: superuser TO SuperSu app

Okay so I am on a LG G2 LS980 and I finally found a way too install a CM13 ROM which took me hours of bricking my phone and rebuilding using .ToT files, but I installed TWRP and completely wiped the phone (except for the the data part so my zips weren't deleted) then after wiping I flashed an exotic bootstack.zip and rebooted back into recovery, then I wiped everything again except for the data which contained my other zips, after that I flashed my CM13 ROM and Gapps for android 6.0.1 and then I rebooted and finally success, so everything was perfect and working so I flashed the latest closed firmware (after I created a nandroid backup of course) and still I rebooted with success and everything still worked, then I tried to flash SuperSu 2.57.zip and then I bricked my phone once again so I restored using my backup (thank god) and I do know in the developer setting I can enable Super User permissions to APPS/ABD (don't know what ABD does but I chose them both, I opened a terminal emulator and typed SU and it asked to grant permission and all that so it does work, but I don't know how reliable the developer setting SU that's packaged into my ROM is and I'm wondering if their is anyway I could change from using the devolper setting SU to the SuperSu app with SuperSu 2.57.zip? Is the developer settings SU as reliable as SuperSu or is SuperSu better? Those are my two questions, please help, thanks!
Paentherax said:
Okay so I am on a LG G2 LS980 and I finally found a way too install a CM13 ROM which took me hours of bricking my phone and rebuilding using .ToT files, but I installed TWRP and completely wiped the phone (except for the the data part so my zips weren't deleted) then after wiping I flashed an exotic bootstack.zip and rebooted back into recovery, then I wiped everything again except for the data which contained my other zips, after that I flashed my CM13 ROM and Gapps for android 6.0.1 and then I rebooted and finally success, so everything was perfect and working so I flashed the latest closed firmware (after I created a nandroid backup of course) and still I rebooted with success and everything still worked, then I tried to flash SuperSu 2.57.zip and then I bricked my phone once again so I restored using my backup (thank god) and I do know in the developer setting I can enable Super User permissions to APPS/ABD (don't know what ABD does but I chose them both, I opened a terminal emulator and typed SU and it asked to grant permission and all that so it does work, but I don't know how reliable the developer setting SU that's packaged into my ROM is and I'm wondering if their is anyway I could change from using the devolper setting SU to the SuperSu app with SuperSu 2.57.zip? Is the developer settings SU as reliable as SuperSu or is SuperSu better? Those are my two questions, please help, thanks!
Click to expand...
Click to collapse
Well, for Android 6.x.x, always flash the latest SuperSU (Latest BETA) as the boot image is now patched to obtains root access, not the /system.
Concerning builtin su (I think it's Superuser in CM), it does the same as SuperSU, so flashing it isn't mandatory.

Accidentally wiped data, need to RE-Root?

Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
AdrMXP said:
Hi. So, I had TWRP on stock rom and my phone was rooted. was messing around trying to install viper4android and i think i clicked wipe data, etc in recovery mode. Phone rebooted and im un-rooted now with SuperSU installed but it says "there is no binary SU installed and superSU cannot install it. This is a problem! "
What do I do now? I can still boot into recovery.
If I have to flash to a stock firmware, is that easy to do? Thanks in advance
Click to expand...
Click to collapse
1. Flash Rom You Want To use in your Device .
2.Download Supersu Binary Zip File from Here http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash it through TWRP recovery
4.Now reboot your cell phone and install SuperSU.

SuperSU breaks boot?

I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Which recovery ? Which superSu version ?
SuperSU 2.79
TWRP 3.0.2-2
rompup said:
SuperSU 2.79
TWRP 3.0.2-2
Click to expand...
Click to collapse
There shouldn't be a problem as I've used these versions without any problems.
Try a clean flash (wipe data + cache + dalvik cache) with latest superSu beta(2.79 SR1).
Search for supersu in oneplus forums for oxygen 3.1.0 since normal supersu will break boot.
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Scherzengel said:
To succesfully install the newest Versions of SuperSU you have to install it in systemless mode. If you flash the ZIP it will install it in /system mode, so you have to force the systemless install.
Before you flash the newest Beta SuperSU.zip go to the TWRP terminal and write:
echo SYSTEMLESS=true>>/data/.supersu
Then flash the ZIP.
SuperSU will be installed in systemless mode and your Phone will boot up fine.
Click to expand...
Click to collapse
I found this in another thread and it worked for me. all credit goes to Scherzengel

About latest Magisk v13.

Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
EDIT:
Thanks to @seko85, anyone who had this issue disable all substratum themes and also do this:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Clear Data from Settings - Apps - Magisk Manager.
mobidor said:
Clear Data from Settings - Apps - Magisk Manager.
Click to expand...
Click to collapse
I did that, enabled any permissions required as well.
Are you using v13.1?
If you're on B25, MagiskSU force closes when allowing a "new" app root, so that could be behind the crashes
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Cyb3rzombi3 said:
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Click to expand...
Click to collapse
I did yeah, the latest version is 5.0.4?
Yeah got 5.0.4 as well and latest magisk is running fine.
If that is not the problem then I don't know what else it could be
Which rom do you have installed?
nfsmw_gr said:
I did that, enabled any permissions required as well.
Are you using v13.1?
Click to expand...
Click to collapse
Yes, and no problem. Installed with TWRP.
nfsmw_gr said:
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
Click to expand...
Click to collapse
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
seko85 said:
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
Click to expand...
Click to collapse
Alright that advice step by step was great!
Gonna try this once I get home and post back, thanks man!
Update, thanks to @seko85 and disabling any substratum theme (dunno which made it work, could be both together as well) I managed to fix the issue.
Magisk v13.1 is up and running.
Also thanks to everyone who replied.
Peace, out.

[Guide] How to install Magisk 15.2 on kenzo (if having issues)

If you are updating Magisk from 14 and are getting Magisk not installed error then this is what you will need to do,
Note you will probably have to start with a new clean Magisk install.
Only tested with Global Beta MIUI9
1. The main problem is caused by using a old TWRP (for example ZCX), so you will need to update to a more recent TWRP. - After you updated your TWRP follow these steps.
2. Flash the Magisk Uninstaller, if it says "Magisk Not installed" then go to Step 3 otherwise skip to Step 4.
3. Flash Magisk 14.0 after it completes , Re-Flash the Magisk Uninstaller to cleanup all OLD Magisk files.
4. reboot to system, make sure the Magisk Manger is gone, then reboot to recovery again.
5. Flash Magisk 15.2 , reboot, install the Magisk Manager if it's missing.
6. Under settings -> apps -> Magisk Manger, set allow on startup, allow storage permissions, and No Rstrictions for MIUI Battery Saver.
and you should have a fully working Magisk 15.2 now, I suggest rebooting once more to recovery and clearing Dalvik Cache. (Note Clear Dalvik Cache is in the Wipe -> Advanced Wipe -> then only check Dalvik /ART Cache partition, do not select anything else!)
Do all modifications at own risk or devices risk.
nop this did not worked for me on miui 8 global stable redmi note 3 kenzo only magisk 14 works when i try flashing 15.2 it result in bootloop m using latest official twrp 3.2.1.0
Not working. it's still not installed for me. I am using the official TWRP 3.2.1.0
OK I will try looking into it some more, after the latest MIUI9 update same thing happened even with newest twrp, said not installed, but after I rebooted and tried flashing 15.2 again it installed, so very odd why sometimes it works and other times not.
I've miui 10.2.1.0 with zcx recovery can i install magisk with his recovery
hemant114 said:
I've miui 10.2.1.0 with zcx recovery can i install magisk with his recovery
Click to expand...
Click to collapse
Use latest 3.3.1 twrp
will u pls elborate
can i install through zcx or ive to WIPE AND FLASH.....
Update your recovery and flash magisk. No wipes needed
as u saying update recovery as per my search which recovery is good redwolf or twrp off. as I'm on miui 10.2.1.0 stable and zcx recovery is installed & want to add magisk plz need suggestion
hemant114 said:
as u saying update recovery as per my search which recovery is good redwolf or twrp off. as I'm on miui 10.2.1.0 stable and zcx recovery is installed & want to add magisk plz need suggestion
Click to expand...
Click to collapse
Official twrp.
it shows error cant update partition..... something

Categories

Resources