Database Info

[Q] SuperSU "No binary installed..."

I rooted my SGS4 Active a while back. Had SuperSU and everything was working fine. But now a message pops up saying: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
I disabled & re-installed SuperSU, and still the same problem.
1) Is it safe to re-root my device when it's already rooted, or will I have to unroot before I root again.
2) I've read that the SuperSU version on PlayStore isn't the right one, is there a link to the latest version?
Device specs:
(AT&T) Samsung Galaxy S4 Active
SAMSUNG-SGH-I537
Version 4.4.2
I have a link for rooting my version already, but I figured I should ask before I risk bricking my phone hahah.
My thanks for any assistance.

Yes its safe to re-root, just follow the same method you used to root it in the fist place and it should work. its happened to me a couple times and all i did was re-root following the original method used
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app

This happened to me also when installing aosp rom... All I did was install superSU from play store and ran it when it was installed. It asked me to root the phone and after reboot all was fixed..

Your device is KK(4.4),so It's a ric problem,I think.
Please install the recovery(like CWM,TWRP) and install a zip file from developer page.
http://download.chainfire.eu/282/SuperSU/

[Q] Help. not sure what I am doing wrong.

So I have the wife's new d850, which we will be suing over straight talk.
- not able to get the OTA updates
- at KK and she wants to be on LP
So far, I've done:
- rooted with towelroot
- loaded TWRP from the playstore
- loaded Superuser from the playstore
- loaded Busybox from the playstore
- loaded Flashify from the playstore
I have tried to flash these 2 roms will no luck.
[ROM][Stock][Rooted] D850 20f Stock ROM Debloated
http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610
Stock LG D850 20F Lollipop 5.0.1
http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041
So using Flashify or TWRP I have been unable to see the ROMs to flash and I have been getting the unable to mount external sd card.
I've gone through the forum several times trying to figure out what I am doing incorrectly and I haven't been able to figure it out.
All I wanted to do was debloat the phone and get it on LP.
thanks for any assistance.

Are you on 10d? Are you sure that root was successful? Does SU install properly? If so then are you able to grant Flashify SU permission? If so then you want TWRP from this thread, http://forum.xda-developers.com/att...recovery-twrp-touch-recovery-2-8-3-0-t2981108, by 777Jon. Follow his instructions for flashing TWRP through Flashify.
If root was not successful try Stumproot also here on XDA.

Are you on 10d? Yes
Are you sure that root was successful? It says I am rooted, so I assume yes.
Does SU install properly? Yes
If so then are you able to grant Flashify SU permission? Yes.
That TWRP did it. The flash worked and its on LP. The only thing is that the debloat didn't seem to work and I still have the carrier apps, which is easy to correct.
Thanks for the help. It's much appreciated.

Glad to help. Titanium backup will get rid of most of those carrier apps. Some you can simply freeze... Good luck.

On H83010i, bootloader unlocked not rooted. Want H83020f rooted

I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.

buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.

Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.

buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root

Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?

buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.

Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?

buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.

Samsung Galaxy S8 unroot

Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?

minalm said:
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
Click to expand...
Click to collapse
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
you have given a very detailed explanation and i fell like a simple thank you would be enough. you helped me out now and i feel somewhat obliged to thank you this way.
cheers

Is the things still the same... namely unrooting will not return KNOX and can not use Samsung warranty?

hi
i have a rotted phone s8..i flashed a stock rom, but phone is still rooted. Some apps like us google pay,mcdonalds tell me that phone is rooted..What i can do?

Verified root but after flashing stock rom, "Sorry! Root access is not properly installed on this device."

Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!

As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.

jwoegerbauer said:
As soon as you re-flash a ROM all modifications you applied to existing ROM are gone.
Click to expand...
Click to collapse
So where do I go from here? (I edited my main message with a little more info).

Yesi Trotamundos said:
Hey guys, had a little problem pop while while setting up my moto 9 g plus.
I have already successfully rooted and verified it on my phone once, and after flashing stock rom, it says in Root Checker App it says "Sorry! Root access is not properly installed on this device.
I thought once successfully rooted, you did not have to worry. I flashed the stock rom, used adb to remove some basic bloatware, and started installing some apps. I already flashed magisk and it shows it is installed successfully, as well as xposed framework, but when I tried to give root access to youtube vanced, it wouldn't let me. That's when I downloaded the root checker again and seen this message.
Anyone have any idea why this happened and how I can fix it? If I need to root my phone again, it's just that I don't know where to begin because I've done it all once. I already have done all the steps to have twrp and magisk. Where do I go from here to get the root verified again?
Thanks!
Click to expand...
Click to collapse
Already solved...I did verify root after flash and installing magisk, but I did not realize that the security patches would cause screw up root. Just had to reflash magisk and root verification works again.