Database Users

[ROOT][RECOVERY][ALL IN ONE] Cf-Autoroot-twrp-T700/705/800/805/Tab S- UPDATE 23/4/15

Updated CF-autoroot with latest Supersu binaries and combined TWRP recovery for SM-T800/SM-T805/T700/T705 Exynos only, Lollipop and Kitkat
I've noticed that quite a number of people seeking to root their device also flash TWRP afterwards, seeing as it's unnecessary to do both steps I have made an all in one package to root and install TWRP recovery.
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version (ADB root shell and Download mode fixes).
UPDATE - I have updated all versions with new builds. TWRP is now v2.8.6.2 and now includes the fixes recently pushed to their repo for encrypted backups. I have also addressed the slow wipe issue, cache, system, etc., which some have experienced and should now be much quicker.
Each device now has it's own build, this is to ensure that TWRP recovery build properties reflect the device it's installed on. ROMs such as CM12 should now install without issue.
Feedback is welcome.
Simply flash with ODIN. Odin 10.6
cf-autoroot-twrp-t700
cf-autoroot-twrp-t705
cf-autoroot-twrp-t800
cf-autoroot-twrp-t805
Check root status with ROOT VALIDATOR
Guide how to flash, credit to Usama m.
http://techbeasts.com/2015/05/01/root-twrp-recovery-galaxy-tab-s-84-running-lollipop-502/
UPDATED TWRP:
http://forum.xda-developers.com/showthread.php?t=3074633
NOTE: It is important to boot to recovery after flashing or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Credits to chainfire for his great work.
FEEDBACK PLEASE
AND DONT FORGET THAT THANKS BUTTON :good: HIT AND RUN IS NOT NICE
.

Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks

d3xtr0 said:
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
Click to expand...
Click to collapse
Good stuff. :good:

Just picked up a T800 as a birthday present to my mom.. Its going to be hard to give this thing to her..lol
Anyways.. just used this to root and it worked perfect.. Had already took ota to LP..
Thanks !!

delete post !

tids2k said:
delete post !
Click to expand...
Click to collapse
What?

ashyx said:
What?
Click to expand...
Click to collapse
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.

snapper.fishes said:
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
Click to expand...
Click to collapse
Why the forum doesn't allow users to delete their own posts is beyond me?

In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx

lloydb9382 said:
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
Click to expand...
Click to collapse
Correct.

thanx so much it worked great ,

T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app

almony8 said:
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately AT&T lock the bootloader, so atm you're stuck with a device that cannot be modified in any way.
Sent from my SM-T805 using XDA Free mobile app

After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.

cyaclone said:
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
Click to expand...
Click to collapse
Use Root Validator and post the output. Root checker doesn't give enough information.

ashyx said:
Use Root Validator and post the output. Root checker doesn't give enough information.
Click to expand...
Click to collapse
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive

cyaclone said:
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
Click to expand...
Click to collapse
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.

ashyx said:
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
Click to expand...
Click to collapse
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Thanks

Not sure if it matters but what version of twrp is being installed?

AKfortyseven said:
Not sure if it matters but what version of twrp is being installed?
Click to expand...
Click to collapse
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version.
Click to expand...
Click to collapse
= 2.8.6.1

i have a moto G4 that crashes when i flash supersu on it

So i can unlock my bootloader on the moto G4 and install TWRP but when i flash SuperSU the devices crashes and i have to reflash the stock firmware as you can guess this extremley annoying thanks any help would be very much appreciated.

yes. this behaviour has been confirmed by several moto g4 users, including myself.
unlock bootloader - OK
install TWRP - OK
root with supersu ? - N...............................O!

libralibra said:
yes. this behaviour has been confirmed by several moto g4 users, including myself.
unlock bootloader - OK
install TWRP - OK
root with supersu ? - N...............................O!
Click to expand...
Click to collapse
Have you tried the manual systemless method?
Open TWRP, then go to Advanced -> Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
then flash SuperSU?

acejavelin said:
Have you tried the manual systemless method?
Open TWRP, then go to Advanced -> Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
then flash SuperSU?
Click to expand...
Click to collapse
thanks for the recommendation. saw this method today.
however, i am quite happy with it now. not sure if i'm going to root or not. maybe later.

acejavelin said:
Have you tried the manual systemless method?
Open TWRP, then go to Advanced -> Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
then flash SuperSU?
Click to expand...
Click to collapse
i haven't tried it yet but just about to thanks hope it works

acejavelin said:
Have you tried the manual systemless method?
Open TWRP, then go to Advanced -> Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
then flash SuperSU?
Click to expand...
Click to collapse
Thanks it worked

help
craigwilson9955 said:
Thanks it worked
Click to expand...
Click to collapse
hey sir can u kindly please post a download link for the supersu zip thanks

madscientistdam said:
hey sir can u kindly please post a download link for the supersu zip thanks
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/

acejavelin said:
Have you tried the manual systemless method?
Open TWRP, then go to Advanced -> Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
then flash SuperSU?
Click to expand...
Click to collapse
You should make a new thread with this info, I see a lot of people getting hit with it

altimax98 said:
You should make a new thread with this info, I see a lot of people getting hit with it
Click to expand...
Click to collapse
Lol... I don't even have a G4, I currently have a G3, its the same way on that one, I just came here to check out the community when I saw how cheap they were on Amazon... I will do a quick tutorial making some basic assumptions about the G4 and it's similarity to other handsets
BTW, the systemless method is not new or exclusive to Moto... The info is out there if you know what to look for.
Sent from my MotoG3 using Tapatalk

acejavelin said:
Lol... I don't even have a G4, I currently have a G3, its the same way on that one, I just came here to check out the community when I saw how cheap they were on Amazon... I will do a quick tutorial making some basic assumptions about the G4 and it's similarity to other handsets
BTW, the systemless method is not new or exclusive to Moto... The info is out there if you know what to look for.
Click to expand...
Click to collapse
I know it isn't, but if you don't do systemless on the G4 it fails to boot. I'm seeing a lot of people saying to flash new firmware or a system partition. All you need to do is run your code in the TWRP terminal and reflash superSU and it boots fine.

altimax98 said:
I know it isn't, but if you don't do systemless on the G4 it fails to boot. I'm seeing a lot of people saying to flash new firmware or a system partition. All you need to do is run your code in the TWRP terminal and reflash superSU and it boots fine.
Click to expand...
Click to collapse
Done... Here ya go: http://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592

craigwilson9955 said:
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
will it erase all your data after rooting using this method?
i got twrp recovery, then use it for long time (or long enough to have filled so many files). if the root will erase all internal, i have to think about it. another question is about the OTA. can we get any OTA updates in the future after TWRP/rooting?

moto x pure 6.0 mm ( root )

Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.

Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.

I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.

fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.

OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.

I don't know... it's a puzzler.

2.62-3 and stop using toolkits.

lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.

fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.

fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.

acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..

Deleted.

[GUIDE] Sideload NOF27B/C on Stock, TWRP, Custom Kernel, Mods, Root - Updated 3/6/17

Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.

This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed

bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...

Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse

I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.

Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?

can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.

thank you! worked great!

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:

I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay

rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?

spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.

spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.

Is something up with the OP or is it just my XDA app causing it to show like this..

aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.

rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.

spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update

Can't get rooted....supersu.zip seems to install but binary needs to be updated??

I would pull out my hair if I still had any
I unlocked my Moto Pure "clark" using motorola's unlock code.
Installed TWRP
Installed SuperSU
Installed the latest cm-14.1-20161225-NIGHTLY-clark
and GAPPS for 7.1
All that worked...rebooted, added all my apps....great...but no, not great
I am apparently not rooted.
So...
I installed supersu from playstore..and tried to install it correctly using supersu's install which failed.
I've tried entering the echo ..... command and pushing supersu.zip to twrp and installing...and it looked right, but still not rooted.
I have tried every hint I've found on the internet....but I can't get this baby to root correctly so titanium and other programs will work.
I am using SR2-SuperSU-v2.79-SR2-20170103215521.zip and I am entering the echo SYSTEMLESS=true>>/data/.supersu using TWRP's terminal....
I could use a little help....I'm thinking I missed something obvious.

ghstudio said:
I would pull out my hair if I still had any
I unlocked my Moto Pure "clark" using motorola's unlock code.
Installed TWRP
Installed SuperSU
Installed the latest cm-14.1-20161225-NIGHTLY-clark
and GAPPS for 7.1
All that worked...rebooted, added all my apps....great...but no, not great
I am apparently not rooted.
So...
I installed supersu from playstore..and tried to install it correctly using supersu's install which failed.
I've tried entering the echo ..... command and pushing supersu.zip to twrp and installing...and it looked right, but still not rooted.
I have tried every hint I've found on the internet....but I can't get this baby to root correctly so titanium and other programs will work.
I am using SR2-SuperSU-v2.79-SR2-20170103215521.zip and I am entering the echo SYSTEMLESS=true>>/data/.supersu using TWRP's terminal....
I could use a little help....I'm thinking I missed something obvious.
Click to expand...
Click to collapse
CM is pre-rooted, just go into developer options and turn it on... SuperSU isn't needed at all.

acejavelin said:
CM is pre-rooted, just go into developer options and turn it on... SuperSU isn't needed at all.
Click to expand...
Click to collapse
Thanks....I knew it was obvious