Related
I am on ARHD 10.1, it keeps telling me there is a SU Binary update but if I tell it to install it just reboots to recovery and does nothing.
What is the correct method to update the Binary on the One?
Which Super User you have?
SU or SuperSU by Chainfire?
SuperSU - Same issue
Guich said:
Which Super User you have?
SU or SuperSU by Chainfire?
Click to expand...
Click to collapse
I am having this same issue: I have SuperSU. I just finished unlocking bootloader and flashing TWRP. Everything else remains stock.
I get a "The SU binary needs to be updated. Contine?". When i continue i get "If you have custom recovery like TWRP or CWM, that can be used to (try to) install the SU Binary. This is recommended for HTC devices. How would you like to install the SU Binary?"
When i select use TWRP/CWM it boots into recovery but i have no binary file (or i don't know where to find it). if i try the normal way it doesn't work.
(Cancel that!) it worked on the third try ... ? not sure what was different but it rebooted into recovery and updated fine. That inadvertently, it seems, fixed my wifi tether problem as well.
Emh, however...
Here there is the flashable zip of SuperSU...
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
kargy said:
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
Click to expand...
Click to collapse
Download the zip for superuser or flash the SuperSU
I'm also having an issue with the update, although i've managed to install v1.75 of SuperSU through TWRM, but now the handset force reboots about 10-15 seconds after booting up, every time. Any ideas?
kargy said:
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
Click to expand...
Click to collapse
When you are into twrp.
You go to the path /data/data/com.koushikdutta.superuser/files
There is a supersuer.zip, you flash these file and you have the su updated
wingnutz said:
I'm also having an issue with the update, although i've managed to install v1.75 of SuperSU through TWRM, but now the handset force reboots about 10-15 seconds after booting up, every time. Any ideas?
Click to expand...
Click to collapse
Can anyone shed any light on this? I ended up factory resetting the handset just so it was usable, so had a fresh rom installed, and now ive tried to update the binaries again, its still happening. Constant reboot loop, from the time the OS loads to reboot is ~20 seconds.
Any ideas would be greatly appreciated.
I am also stuck on this. Have just changed to ViperRom from Android Revolution and now when I try to back up using Titanium it states I am not rooted. Go into SuperSU and it states the binary SU needs to be updated. I am not getting a boot loop and I have followed all the steps but am not getting anywhere. Am I going to have to re-root?
Have got it working. Researched the problem seemed to be an an app called one tap cleaner. I granted it root access which what was causing the problem. Stopped giving it root access and went into TWRP and deleted all the SuperSU file and reinstalled SuperSU and all is good. Posted incase anyone else was having a similar issue.
I had the same issue. I tried it with the phone plugged into a charger and somehow that made it work.
I was having all the same problems with supersu. Once I had it plugged in and charging the install worked throught "normal" and my tether problem was fixed.:good:
mmm286 said:
When you are into twrp.
You go to the path /data/data/com.koushikdutta.superuser/files
There is a supersuer.zip, you flash these file and you have the su updated
Click to expand...
Click to collapse
I believe this is the right answer. Worked for me.
Thanks
Using the newest SuperSU ( not Superuser ) solve this problem for me.
Flash SuperSU using Recovery
Plugged In
Plugged In to charger and it worked, weird...but I'll take it
im actually having this same issue. ive got an LG G2 AND i just rooted it but for some reason when i go to start TWRP the android icone pops up then it just boots up again with out the issue being fixed. could someone possibly help. =(
Guich said:
Emh, however...
Here there is the flashable zip of SuperSU...
Click to expand...
Click to collapse
I've tried this before but it would just keep on saying "Installation Aborted."
ChristianAvi said:
I've tried this before but it would just keep on saying "Installation Aborted."
Click to expand...
Click to collapse
Strange.
If recovery will say installation aborted there is also a code error.
However, have you flashed latest, right?
Guich said:
Strange.
If recovery will say installation aborted there is also a code error.
However, have you flashed latest, right?
Click to expand...
Click to collapse
I dont know. I used Kingo App. Sometimes I also get this response: There is no SU binary installed. SuperSU cannot install it. This is a problem!
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
What version of SuperSU are you using? Older versions will cause you to get stuck on the boot animation.
Try v2.79. It should reboot once or twice during first boot after flashing.
Alternatively, you can also root by flashing Magisk v11.1.
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
First, reflash OS to get a stable starting point. Then use the unofficial beta release of twrp to flash. I have heard of success with a fork ( blu something) but basically he merged the same patches.
Check the dm-verity thread for more details
Sent from my ONEPLUS A3000 using Tapatalk
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
Follow this guide:
https://www.youtube.com/watch?v=wwd31NU7VC0&t=4s
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
sguy156 said:
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
Click to expand...
Click to collapse
U can't get rid of this msg.
Navi44 said:
U can't get rid of this msg.
Click to expand...
Click to collapse
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
damiensturdy said:
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
Click to expand...
Click to collapse
Have you tried that personally?
Which version of SU is the system version 2.79 ? First thing is to get the phone to boot first
Navi44 said:
Have you tried that personally?
Click to expand...
Click to collapse
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
damiensturdy said:
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
Click to expand...
Click to collapse
Thank you for telling this.
This was a normal thing in rn3 thread.
Where even we flashed roms with locked bootloader. And whatever we can do through recovery we did with locked bootloader.
Didn't try it here though.
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
sguy156 said:
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
Click to expand...
Click to collapse
Someone said to use system root.
And then lock the bootloader. Since the su is in system, it won't be wiped.
Haven't tried it but should work THEORETICALLY
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
sguy156 said:
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
Click to expand...
Click to collapse
Regular su.
Earlier su used to be system root.
The systemless root started quite recently.
So do I need to use seamless root or SU for 7.0
On using systemless root it will be deleted when you lock bootloader.
You need to use system root for naught
Keep in mind that if you update OOS after locking the bootloader,you'll lose root. Afterwards, you'll have to unlocked the bootloader again - and wiping your device in the process - to reroot.
Just successfully installed Supersu 2.81 (2.81 because the guide I used said it's the most stable version) when my phone rebooted the playstore promted me to update Supersu so. being the clueless noob that I am I updated it. Now it keeps failing when it's trying to update binaries. I can still use supersu and still have root access though. It's just annoying seeing that message to update binaries.
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
fajner said:
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
Click to expand...
Click to collapse
I already fixed mine.
blitzball said:
I already fixed mine.
Click to expand...
Click to collapse
How did you fix it?
fajner said:
How did you fix it?
Click to expand...
Click to collapse
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
blitzball said:
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Sorry for late reply, I've tried uninstalling supersu/unrooting but neither did work or help. I finally ended up rebranding my phone to AL10 and installing the Chinese Oreo rom which works great.
After installing TWRP and rooting my device on the latest firmware N950FXXU5CRHA,
I get an error message when I power on the device and it won't boot up
(Only official released binaries are allowed to be flashed)
I got root working but when I try to restart it, I always ended up getting that message and I need to flash again the official firmware and losing my root again
any solutions for this? :crying:
upbeatwrench said:
After installing TWRP and rooting my device on the latest firmware N950FXXU5CRHA,
I get an error message when I power on the device and it won't boot up
(Only official released binaries are allowed to be flashed)
I got root working but when I try to restart it, I always ended up getting that message and I need to flash again the official firmware and losing my root again
any solutions for this? :crying:
Click to expand...
Click to collapse
After flashing TWRP and rebooting you have to delete "securitylogagent" in system/app before rebooting again.
stonedpsycho said:
After flashing TWRP and rebooting you have to delete "securitylogagent" in system/app before rebooting again.
Click to expand...
Click to collapse
I deleted "securitylogagent in system/app but when I restarted my phone, I still got that errror. But anyways, I did install a custom rom on my phone to obtain root without any problems
Sent from my SM-N950F using Tapatalk