I rooted my device using the root specific to this device. Now when I open up Super SU it says the SU binary needs to be updated. How do I go about this?
just go to settings ... is not hard ...
xotz said:
just go to settings ... is not hard ...
Click to expand...
Click to collapse
It doesn't work. Fails, and reboot to twrp does nothing. Im with OP.....how do you update the binary? Im trying to install xposed and I suspect this old binary is the reason it won't install.
carnivalrejectq said:
It doesn't work. Fails, and reboot to twrp does nothing. Im with OP.....how do you update the binary? Im trying to install xposed and I suspect this old binary is the reason it won't install.
Click to expand...
Click to collapse
did you figure it ? im having the same issue
Potatoverlord said:
did you figure it ? im having the same issue
Click to expand...
Click to collapse
I do not remember....sorry lol no longer have the phone.
Maybe flash the latest version of supersu from twrp? I'm just guessing because I run a stock unrooted rom.
Related
Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.
What if you upgrade it using the "normal" method?
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?
brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards
rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.
So I flashed CM 11 and I am really enjoying this ROM. When initially setting up I mistakenly let Google restore my apps. I was not aware that SU was already built into CM 11, so I ended with SuperSU and SU installed at the same time. A few of my rooted apps were allowed root access, but now every time a new app ask for SU permission it is denied.I have deleted SuperSu and rootchecker says I have root.
Does anybody have a suggestion?
Reflash SuperSU from custom recovery.
iBolski said:
Reflash SuperSU from custom recovery.
Click to expand...
Click to collapse
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
blindman75 said:
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
Click to expand...
Click to collapse
Not that I know of. I've been using SuperSu all the time. I prefer it because:
I paid for it, so I want to get my money's worth!
Chainfire seems to always be on top of the latest fixes, including how Lollipop may have to require custom kernels, which means unlocked bootloaders. Uh oh.
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
You might have a system app removed or missing
Or maybe you have done something with the build prop as well if thats messed with that will also throw an error out.
If you read closely it should tell you what the error is
xxbabiboi228xx said:
You might have a system app removed or missing
Click to expand...
Click to collapse
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Bebout said:
I really hope not. How do I go about finding out if I'm missing a system app? I've already done a factory reset along with unrooting via SuperSU's app.
Click to expand...
Click to collapse
It should tell you the error after you try flashing the ota you may have to use the .kdz method
xxbabiboi228xx said:
It should tell you the error after you try flashing the ota you may have to use the .kdz method
Click to expand...
Click to collapse
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.[/QUOTE
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
xxbabiboi228xx said:
Bebout said:
I don't have TWRP installed, either. I've got stock recovery and stock everything. I was going to remove root so I could update and then re-root for v10j and then install the new version of TWRP.
Click to expand...
Click to collapse
Your telling me you removed root ? But you never had twrp as your recovery ?
Click to expand...
Click to collapse
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Bebout said:
I fixed it. I rooted the device and flashed the v10i recovery image for TWRP that I found and I'm now going to update to v10j via the kdz, as you suggested. Thank you.
Click to expand...
Click to collapse
No problem glad i could assist u in your problem
Why not get TWRP again and flash @GameTheory's v10j pre-rooted stock rom, it's not like you're going to see anything special with that update it's the last one before MM:
http://androidcreations.weebly.com/flashable-update-zip.html
Bebout said:
Why would it be doing this? I already removed root via the SuperSU app permanently. What could be causing the error?
Click to expand...
Click to collapse
well even if you Remove root via SuperSU that doesn't mean your SYSTEM is unmodified, the only way to get back to FULL Unmod. software is by following my steps of restoring back to stock, here is the link
http://forum.xda-developers.com/android/development/rom-lg-g-stylo-h631-ms631-v10j-stock-t3211563
P.S. You need to have TWRP for this so Re-Root and Re-Flash TWRP and follow steps
We are now able to root Android 7.0 on the Galaxy S7!!!!!
EDIT: WE HAVE ROOT !!!
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
How do you root with PK1?
KillerClaw321 said:
We are not able to root Android 7.0 on the Galaxy S7. The only thing we can do is let those know who are wanting to update that there is not root.
I do believe it is possible to downgrade back to PK1 from the latest nougat update. Please correct me if I'm wrong. But once you downgrade you should be able to root again.
Click to expand...
Click to collapse
I cannot root with PK1 either. Odin flashes fine, but root script will not work no matter what I do. Any advice?
silversusanoo said:
I cannot root with PK1 either. Odin flashes fine, but root script will not work no matter what I do. Any advice?
Click to expand...
Click to collapse
Copy the directory, then run cmd in administrative mode. Then type "cd (directory)" for example cd C/Users/KillerClaw/Desktop/Root . Then type root.bat, then leave your phone plugged in and watch it restart by itself... done you should be rooted
Still having issues
KillerClaw321 said:
Copy the directory, then run cmd in administrative mode. Then type "cd (directory)" for example cd C/Users/KillerClaw/Desktop/Root . Then type root.bat, then leave your phone plugged in and watch it restart by itself... done you should be rooted
Click to expand...
Click to collapse
I figured out the problem, it was my firewall. SU installed, but is still not working and cannot be updated. I tried but failed installing twrp. I'm out of ideas
silversusanoo said:
I figured out the problem, it was my firewall. SU installed, but is still not working and cannot be updated. I tried but failed installing twrp. I'm out of ideas
Click to expand...
Click to collapse
It is impossible to install twrp on this s7 as we do not have an unlocked bootloader...
LG5
KillerClaw321 said:
It is impossible to install twrp on this s7 as we do not have an unlocked bootloader...
Click to expand...
Click to collapse
Should I just get the LG5 instead? Thank you.
silversusanoo said:
Should I just get the LG5 instead? Thank you.
Click to expand...
Click to collapse
Yeah, if you can install twrp and root on nougat go ahead...
KillerClaw321 said:
Yeah, if you can install twrp and root on nougat go ahead...
Click to expand...
Click to collapse
Thank you. I do not have many options for phones with T mobile. I loved my S5 but I have bad reception on Sprint.
Anyone uses magisk ? Is it worth??
cline2 said:
Anyone uses magisk ? Is it worth??
Click to expand...
Click to collapse
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
Ok. Too much pain to do. I will stay with SuperSU
ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
What are you rooted with now? And what build is your firmware?
ante0 said:
What are you rooted with now? And what build is your firmware?
Click to expand...
Click to collapse
I'm rooted with phh, and I'm on L29-567-190. Thanks a ton for the help.
McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
If you want to root with magisk, just flash the zip and you are done.
Powerlated said:
If you want to root with magisk, just flash the zip and you are done.
Click to expand...
Click to collapse
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
McRoberts said:
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
Click to expand...
Click to collapse
You need to be on recovery 3.0.1-1
albertobom said:
You need to be on recovery 3.0.1-1
Click to expand...
Click to collapse
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
ante0 said:
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
Click to expand...
Click to collapse
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
McRoberts said:
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
Click to expand...
Click to collapse
You need to be on firmware B182+ (which you are)
You need to have twrp 3.1.0+
You need to flash stock boot image before Magisk.
You can get stock boot either from rom zip (boot.img) or stock firmware (update.app) and extract boot using Huawei Update extractor. Then flash boot image manually.