Just got an update for SuperSU and it asked me to update su binary. Update failed and I lost root as a result. Reflashing in TWRP fixes it, but I tried again in case it was a fluke but lost root again. Anyone else with this issue? In case you get the update I'd recommend against it.
32BitWhore said:
Just got an update for SuperSU and it asked me to update su binary. Update failed and I lost root as a result. Reflashing in TWRP fixes it, but I tried again in case it was a fluke but lost root again. Anyone else with this issue? In case you get the update I'd recommend against it.
Click to expand...
Click to collapse
Reflash 2.79, then latest in Flashfire. Worked for me at least.
Or wait until 2.82, the devs said they're working on the issue already.
Related
I am running Timat 2.2.2. My market asked me to update superuser which I did and it worked. However I keep getting a message that my su binary is out of date. It's on v2.3.1-ef. I check for updates and it finds 3.0 however when I go to update it fails on "Gaining root access... fail!"
Why would this be happening if root is working fine on all other apps? I tried the SU Update Fixer app but that didn't help.
I forgot to mention that I also tried to have SuperUser automatically approve new su requests; still no go.
uninstall the update and re update it again and then try...should work
LPHS said:
uninstall the update and re update it again and then try...should work
Click to expand...
Click to collapse
this worked, thanks.
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!
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
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.
Hey, I'm curious how I received the Nougat update if I have TWRP and Super SU root. I've never been able to receive a phone update if I had this setup. Doesn't super su modify the system? If I try installing the update will I brick the phone?
Edit - Sorry, I meant to post in the questions thread. You guys can lock, move our delete this post.
I accidentally updated my phone while having TWRP and SuperSU installed. It does not brick your device, but you lose root access. I'm currently trying to re-root my phone but I'm having some issues. My phone seems to have remained unlocked.
I did the same thing...got worried at first, but everything looked okay so I went ahead and flashed Magisk...seems fine.
Hello!
I have B342 and want to update to B360. My phone is rooted and TWRP works.
When i use the normal way to update, the phone boots to TWRP and an Error message comes during update
How do I do it?
Thanks!