Database Develop

[Q] How to update SU Binary?

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!

X98 Plus II - TWRP + ROOT v1.2

Hi, with the help of kalijo, I have made an archive to install TWRP and root your X98 Plus II model C2D4.
Reported to also works on C2D6 and C2E3.
Use at your own risk.
You will need an USB mouse to navigate in TWRP.
Instructions are in the archive.
With v1.2, I've added instructions to save the original boot and recovery images, but this will only works with new install, not upgrade.
Download link
MD5: 8634eb14ed5add0c573649aba383daa7.
Version 1.2:
- Added commands to backup boot and recovery images
- Updated SuperSU to v2.79
Version 1.1:
- Updated SuperSU to v2.78
- Added some infos in this file
Version 1.0:
- Initial release

Version 1.1:
Updated SuperSU to v2.78

Thanks! I haven't had a chance to use it yet, but I'm the most recent download.

Here is the new flashable SuperSU:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
You may have to install SuperSU on GooglePlay after.

Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app

CountZer0 said:
Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
It might or might not work.
I have a C2D4, what is the specs of C2E3?

It's android only. 2gb Ram.
Skickat från min SM-G935F via Tapatalk

problem with superSU binaries
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you

Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you

miloucrabe said:
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you
Click to expand...
Click to collapse
See post #4
carlo201983 said:
Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you
Click to expand...
Click to collapse
What have you done before ? more infos needed.

Version 1.1:
Updated SuperSU to v2.78

Did anyone have any success so for on C2E3 (2GB Android only model)?
Or, maybe to the DEVS - as this is for the dual boot version, is there any reason it would definitely not work on the Android only model? Willing to take some amount of risk, but dont want to brick my device...

It should work. Worst case, you have to reinstall Android, so make sure you have the files before trying.
To obtain the files, type your model number here (you can use Chrome for auto translation):
http://www.teclast.com/tools/pad/pad.php?t=p
That will lead you here:
http://pan.baidu.com/s/1nvpQOGx
(Use Jdownloader to download the file).
The dl speed is rather slow, I'm trying to download right now, will update the post with a mirror soon.
Update: here is a mega mirror:
https://mega.nz/#!sFBCDJiJ!7fLWNkmdg0yUH1IgPlerDo_Og0Vw5Ypgnh4rf0ItnVI
Please report your findings, so I can update the first post.

Well bad news, I tried to flash according to the instructions but the whole thing stopped working/responding during the "fastboot boot loader.efi" stage. I tried restarting the process using dnx mode, however in the end I received "corrupt bzimage kernel" error and device would not boot. I then installed phone flash tool and tried restoring the default images, the process completed OK however when booting teclast logo stays on screen for around 10 minutes, then I get this error: "Bootloader error code 06. Multiple crash events have been reported."
I tried flashing both the "blank" and "recovery" profiles, flash completes OK but tablet is unsable
Any ideas how to solve this, or did I just brick it?
Edit: Screenshot
http://i.imgur.com/OmqhH1E.jpg

In my attempts to install xposed module, I destroyed my both boot and system.
Since you have the problems with bootloader, get android files for your tablet (C2D3) unpack and find the boot.img and system.img
First step flahs origin boot.img
fastboot flash boot boot.img
Then try fastboot boot loader.efi
If your tablet is stuck in a bootloop, then also flash the original system
fastboot flash system system.img
Hope it helps
BTW, did somebody succeeded in installing xposed on our tablet?(C2D4)

I got a working factory image up and running, turns out the issue was some kind of driver/USB problem, I reinstalled everything from scratch on a fresh PC and the recovery flash worked flawlessly the first time I ran it. I will try root procedure again on the other machine later today or tomorrow.

Hooray, I got it working on my c2e3 model using the files and instructions in the original post.
However I have to say this was one of the scarier rooting procedures I went through, even using the cleanly installed PC to flash I had to do it multiple times and kept getting various flashing errors, bootloops, TWRP exiting immediately upon launch etc.. But of course this could just be some kind of HW issue with my tablet, would not suprise me at this price.
Thank you all for your support! Now if we could only get Nougat on this baby...

@maxmax0 thanks for the feedback. @veaceslav No wonder you had issues, Xposed for X86-64 don't exist ! which one have you tried ?

@mooms I tried the normal version, which gave me a bootloop and then I tried the magisk version. Actually the magisk version is flashed, but it doesn't show..

You don't get the point, normal or Magisk version, they are not designed for x86-64, only ARM, ARM64, and X86.

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this

Wow and so it begins, great work thanks!

Thanks
Sent from my Pixel using XDA-Developers mobile app

has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well

Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:

Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.

GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...

zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.

Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.

Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.

zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.

rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....

Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?

ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk

Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.

fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off

ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????

BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

OP3 T Root Issue

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.

How do I update supersu binaries?

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.