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!
Related
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/
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
pstgh said:
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
Click to expand...
Click to collapse
Boot to twrp and reflash the SU binary.
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Questions go in the "Google Pixel Questions & Answers" section.
Always use the latest of both unless you read otherwise - for example, if you read the TWRP thread, you'll see a lot of people have trouble with RC2, so just stick with RC1.
pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Boot to TWRP RC1, then install SU RC3. Assuming you don't want TWRP permanently installed.
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.
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Crav3 said:
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Click to expand...
Click to collapse
Its been a while since I used Magisk. But at that time, PHH superuser had to be used?? Not sure if that is still the case though. Sorry I could not be more help
Yes it does need to be used and it was already installed. But after rebooting the app was not in my app drawer and i had a notification to install SU through play store. But when i go to play store it says it is installed and needs an update. After updating it tells me su binary occupied and takes me to a page to help fix it but i already tried flashing superuser zip file through recovery and nothing changes
Similar Problem
Have you fixed it already because I am havibf the same problem here. I am usibg Samsung J7 Core
You can do what you said you would do (reinstall stock ROM) and then you can try again. Looks like thats the only thing you can do, unless you can somehow remove the root binary and the app using something like ES File Explorer (but again, it requires root) or you can try another root provider.
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.