Develop Bugs

[Q] Where to find SU binaries for P600?

Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.

CNemo7539 said:
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Have you tried updating Supersu from play store

lsherif said:
Have you tried updating Supersu from play store
Click to expand...
Click to collapse
Yes, I did. It says that binaries are not found.

CNemo7539 said:
Yes, I did. It says that binaries are not found.
Click to expand...
Click to collapse
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

22sl22 said:
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Click to expand...
Click to collapse
Thank you! Now I'm rooted again!

M8 won't root

I had a rooted M8, however something was going wrong as it constantly rebooted. So I did a factory reset and that fixed the problem. However now it won't root for some reason. I have TWRP recovery and flashed the root file however when I do root checker it stated that I do not have root access. Anyone know what's wrong?

ILowry282 said:
I had a rooted M8, however something was going wrong as it constantly rebooted. So I did a factory reset and that fixed the problem. However now it won't root for some reason. I have TWRP recovery and flashed the root file however when I do root checker it stated that I do not have root access. Anyone know what's wrong?
Click to expand...
Click to collapse
Have you tried flashing a different version of the root program? I assume it's SuperSU (From Chainfire) ? It still gave me root access on 1.94 I saw that he already updated to version 2.00 by now.
Perhaps try a different version and see what it does.
Thread to Chainfire's SuperSU

BerndM14 said:
Have you tried flashing a different version of the root program? I assume it's SuperSU (From Chainfire) ? It still gave me root access on 1.94 I saw that he already updated to version 2.00 by now.
Perhaps try a different version and see what it does.
Thread to Chainfire's SuperSU
Click to expand...
Click to collapse
I used SuperSU. Should I try Super User?

Just use the normal install method from Google play. Twrp auto Installs the su binary the first time it is booted in to. Then just update super su via play store.

ashyx said:
Just use the normal install method from Google play. Twrp auto Installs the su binary the first time it is booted in to. Then just update super su via play store.
Click to expand...
Click to collapse
What is the install method via google play? I've only ever flashed a zip file.

ILowry282 said:
What is the install method via google play? I've only ever flashed a zip file.
Click to expand...
Click to collapse
Once booted into the os you should see the super su app. Go to play store and update it.

Systemless OTA upgrade

I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.

How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse

Updated to NMF26O, Lost Root

Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?

cantsingh said:
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
Click to expand...
Click to collapse
That update permanently block root for your device

cwalker0906 said:
That update permanently block root for your device
Click to expand...
Click to collapse
Even if I have an unlocked bootloader already?

cantsingh said:
Even if I have an unlocked bootloader already?
Click to expand...
Click to collapse
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread

cwalker0906 said:
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
Click to expand...
Click to collapse
Lol you terrified me. What's the fix? I'm looking for the root thread right now..

cantsingh said:
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
Click to expand...
Click to collapse
Fastboot boot twrp alpha 2, flash the su zip, and reboot

cwalker0906 said:
Fastboot boot twrp alpha 2, flash the su zip, and reboot
Click to expand...
Click to collapse
Got it. Thanks, buddy. I'll post back here to confirm.

Confirmed. If you lost root when updating to NMF26O (or after installing TWRP RC1), then hot-boot TWRP Alpha 2 (fastboot boot twrp-alpha-2.img), flash supersu and reboot. Thanks!

confirmed - worked for me!
cantsingh said:
Got it. Thanks, buddy. I'll post back here to confirm.
Click to expand...
Click to collapse
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.

miker2069 said:
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
Click to expand...
Click to collapse
You fastboot twrp rc1 but then flash the twrp rc1 zip and then it should be fine and then flash SuperSU 2.79 sr3.

recovery is not seandroid enforcing

I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.

Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?

audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.

Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.

Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html

So you twrp 3.1.1 and it will work right
I having the same issue
Thank you

so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran

timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself

Trwp
What version of twrp I need to use
Thank you

timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1

Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran

timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.

Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks

timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way

I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you

timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4

Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran