Database Info

[Q] Problems rooting. Have s off and unlocked on lollipop.

Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.

DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
Since you have TWRP installed do a android backup and install one of the rooted ROMs. Most will install SuperSu and BusyBox in the installation process.

DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.

dottat said:
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.
Click to expand...
Click to collapse
Sorry I didn't see your response to my post. I only saw the others. Been trying to figure this stuff out since.
I think I flashed the latest version (2.46)? I used windroid. Pushed the file to the phone and installed it from the internal memory. Not sure of what the webview in Android update is or how to uninstall it. I will try the method you gave me in the other post. Thanks!
Update: Disabled webview for Android. Working now. Thanks!

SuperSu needs to be updated!

Hello all, I am facing the "super su binary need to be updated" wherever I try to update it it simply does not. I have the pro version also but nothing happens. The next time phone is restarted it askes me the same. Anyway to update or install another updated version? I also un installed the current version and installed the last one from the Market but nothing.
Thank you in advance!

if you have bootloader unlocked, you can flash a custom recovery, then manually flash the latest supersu.

I have root access but not the bootloader unlocked

The-Vega said:
I have root access but not the bootloader unlocked
Click to expand...
Click to collapse
When I've got this message, I answer "Continue", then "Normal" and Super SU will update...

Possible Solution
How did you root? If you rooted using KingUser, it's interfering with SuperSU.

I do "normal" but it is not possible than it ask me for reboot. And it rebootes but nothing changes.
I have rooted looking at the post "how rooted without bootloader unlock"
I cant flash the update cos I don't have a costum recovery.

SuperSU Update Available in Playstore

In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.

Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.

Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK

TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?

MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.

TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?

MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.

Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.

Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.

MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.

pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.

I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.

pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...

..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.

pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.

Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk

mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.

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.

ota updates with root and a linux host?

Ok,
I have fastboot and adb working on my linux mint host. Can someone explain to me how to install ota updates on a rooted pixel phone? I tried installing it via the zip using twrp and that didn't work. It just unrooted my phone so I had to reroot it. I tried using Flashfire and downloading the ota update and then using flashfire to detect the ota update and flash it and everytime it doesn't work... errors and then unroots my phone.

I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.

bush911 said:
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
Click to expand...
Click to collapse
Ok, I downloaded the ota update via Google's webiste. Flashed it with flashfire. It asked if I would like to overwrite the boot and recovery. (said it would most likely fail if I didn't.) I told it ok. It flashed for a while. Rerooted automatically. It booted back up. It didn't update. Still prompting me to update ota.

I just tried the second method in this article
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.

Which version of SuperSU are you trying to use? Both of the following links discuss verified boot, which is one possible item you could be running into with the latest Pixel updates.
SuperSU v2.82-SR1 is the latest version, and it added boot signing.
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
If you are using an older version of SuperSU, then you will need to sign the boot image. I installed the latest Pixel update before v2.82-SR1 was available, so I just had FlashFire install the OTA, and then I added the following zip to the list of FlashFire actions immediately after it was set to root the phone again. FlashFire worked without issue to update to the latest release for June by adding the following before rebooting when using a version before SuperSU v2.82-SR1.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

I am attempting to flash 2.79. but immediately after, I flash the verifiedbootsignerv3.zip

How to root my phone"
Sent from my itel it1408 using XDA Free mobile app

yared1212 said:
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean here...

dorlow said:
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Click to expand...
Click to collapse
That looks like an April update, and there are newer versions, so I'm not surprised the phone would try to update.
https://developers.google.com/android/ota
Three months ago was the first time I tried FlashFire, and I couldn't get it to use the OTA to the phone at that time. Some of the FlashFire instructions made me think I might need to use the backup option to get the OTA to work, but I was actually able to take the May and June OTAs using FlashFire without the backup option. I'm not sure why FlashFire didn't work for an OTA in April, while it did work with an OTA on the phone the past couple months. I think I may have ended up using a download from the Google site with FlashFire in April, so my only guess was that either using the Google download or a newer version of FlashFire is why I was later able to use the phone OTA with FlashFire for May and June.
SuperSU v2.79 SR3 with either the VerifiedBootSigner v3 or v8 has worked for me in May and June, and then I've taken the Play Store SuperSU update to v2.82. I don't have TWRP installed, and I get the impression there could be some extra steps for FlashFire when TWRP is installed, so I don't have to deal with that. Of course the only reason I switched to using FlashFire is because it seems like the quickest method to just take an OTA and update with SuperSU. If FlashFire didn't work so easily, I'd just go back to sideloading, or using one of the other update methods.