[CENTRAL] CF-Auto-Root

MrMike2182 · May 6, 2017

droidzer1 said:
How are you downgrading? After trying Nougat I found I can't use some of the bloatware disabler and startup managers that were working fine on MM. I tried downgrading to the BPI1 you mentioned, also BQB1, BQA1 and even OJA3 (I knew this one would likely fail from other info you had in another thread). But they all would bootloop or sit on the red VZ screen vibrating every so often. Nougat CQB9 seems to be the only firmware I can use now
Were you using Odin to downgrade or a box like I think you mentioned (Octopus?) ?

Yeah I used octopus box .. After you're done flashing the downgrade are you doing the factory reset right after it's done flashing? If not then stop Odin from auto rebooting the phone and after the flash hold the volume down and power button at the same time until the screen turns off and when it comes back on just select factory reset and let it finish.

droidzer1 · May 6, 2017

MrMike2182 said:
Yeah I used octopus box .. After you're done flashing the downgrade are you doing the factory reset right after it's done flashing? If not then stop Odin from auto rebooting the phone and after the flash hold the volume down and power button at the same time until the screen turns off and when it comes back on just select factory reset and let it finish.

Thanks, I did actually think of doing something like that. I'll give it a try although in the mean time I did find that Package Disabler Pro does take out much of the bloatware and does work with 7.0 Nougat unlike the other two apps I had been using for that purpose.

MrMike2182 · May 6, 2017

droidzer1 said:
Thanks, I did actually think of doing something like that. I'll give it a try although in the mean time I did find that Package Disabler Pro does take out much of the bloatware and does work with 7.0 Nougat unlike the other two apps I had been using for that purpose.

Yeah that Package Disabler Pro is a good app but I wouldn't go crazy killing everything possible with it because it can either end up being detrimental to the battery because I noticed on MM, while using the ENG root kernel when I ran logcat it started flying by the screen so fast that it was impossible to read anything it was saying but after I stopped it I seen an app that was starting up and then Package Disabler was shutting it down so it was basically on, off, on, off but at a speed that was crazy!! Or the other thing that can happen is it won't boot past the Verizon boot screen and there's no way to stop it since you can't even get passed the Verizon boot screen so you'll end up having to reboot in safe mode which isn't fun since it changes everything and then you have to set it all back up again.. Whenever you try to do a downgrade a factory reset is needed to get it to work correctly.

droidzer1 · May 6, 2017

MrMike2182 said:
Yeah that Package Disabler Pro is a good app but I wouldn't go crazy killing everything possible with it because it can either end up being detrimental to the battery because I noticed on MM, while using the ENG root kernel when I ran logcat it started flying by the screen so fast that it was impossible to read anything it was saying but after I stopped it I seen an app that was starting up and then Package Disabler was shutting it down so it was basically on, off, on, off but at a speed that was crazy!! Or the other thing that can happen is it won't boot past the Verizon boot screen and there's no way to stop it since you can't even get passed the Verizon boot screen so you'll end up having to reboot in safe mode which isn't fun since it changes everything and then you have to set it all back up again.. Whenever you try to do a downgrade a factory reset is needed to get it to work correctly.

Thanks for the additional info. I just used that disabler to get rid of a few things I'm fairly sure won't be a problem - mostly VZ apps and junk like 'VZ Protection and Support', CVS Pharmacy, NFL football and a few system apps I've checked out with lists of "ok to disable apps". Interesting thing I noticed about the battery on Nougat. It was still sitting at 100% after a couple hours here on Nougat but the percentage was far higher than it would have been in MM at this voltage (read using androsensor). I've heard people say the Nougat update gave them better battery life. I think Nougat did an Apple trick - calling the battery 100% charged when it's probably a lot closer to 90-95% at most - I've got a lot of background with Li-ion and similar batteries I'll try validating my theory sometime with some same model phones that have different OS versions by battery swapping to see if the percentages change a lot depending on which OS they are running under.

---------- Post added 6th May 2017 at 12:16 AM ---------- Previous post was 5th May 2017 at 11:32 PM ----------

MrMike2182 - Thanks again! That worked doing the factory reset immediately after flashing MM BQB1. :highfive: That is something I missed along the way of all there is to learn here. And now that we know Chainfire's reason that the CF auto root is up on his site I don't feel any need to want Nougat. Last I looked there were over 450 downloads of that CFAR and yet it seems there is no way to unlock the bootloader (yet anyway) and apparently no Developer Editions of this model. Despite his notice on the site that the CFAR's won't work on a bootlocked loader it looks like at least 450+ people have believed there is a reason it's there. Maybe there is still hope the BL will get unlocked sometime.

markmessier8888 · May 6, 2017

ashyx said:
Which twrp did you install?

Hi! I used the TWRP 3.0.2.0
I think i will just install Marshmallow 6.0
If I install Marshmallow 6.0, is the TWRP 3.0.2.0 the correct version for Note 4 N910K korean version?

shiko2007 · May 7, 2017

hello guys ,
can i flash cf-auto root for nougat 7.0 on latest firmware of marshmallow on s6 model :g920f without any problem ?

thx alot

plrodrigo · May 7, 2017

Why the s6 edge plus 928a at&t is impossible to root? Other AT & T phones with bootloader blocked if they can be rooted

force70 · May 7, 2017

plrodrigo said:
Why the s6 edge plus 928a at&t is impossible to root? Other AT & T phones with bootloader blocked if they can be rooted

Not newer samsung devices, no way around the BL lock

Sent from my S8 plus, Note 7, S7 Edge or S6

shiko2007 · May 8, 2017

shiko2007 said:
hello guys ,
can i flash cf-auto root for nougat 7.0 on latest firmware of marshmallow on s6 model :g920f without any problem ?

thx alot

anyone guys ?

droidzer1 · May 9, 2017

shiko2007 said:
anyone guys ?

Yes it's right there on Chainfire's page if you mean the SM-G920F - here is the link to d/l :
https://download.chainfire.eu/733/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip

However you may want to search around here for details on this as I am not familiar with that situation other than seeing the file being available on Chainfire's page. Apparently he is now posting CF auto roots that may or may not work depending on whether the b/l is locked. In my attempt with a locked b/l it didn't work on the VZ Note 5 but it didn't cause any harm either.

breaker911 · May 10, 2017

Does anyone know if this works for sm-g920v (Verizon s6) running stock nougat? I see this is available on Chainfire's page, but with a locked bootloader, I have doubts this will work.

Sent from my SM-G920V using XDA-Developers Legacy app

.::Alien::. · May 10, 2017

Thanks a lot for covering SM-N9208 running android N.... Working Like a charm.... Thanks a million!

rakotonirinaT · May 10, 2017

Hello guys,

I was trying to use the CF-Autoroot method to root mine, since I encounter issues to us f.lux or CF.Lumen on Magisk.
However, attached is the screenshot error I've got when flashing the .tar.md5 file.

What do you think is the reason, and what shall I do?

Thanks,

Chainfire said:
CF-Auto-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root. In essence, it does nothing but install and enable SuperSU on your system, so apps can gain root access.

This thread serves as a central discussion and request thread for CF-Auto-Root. If you have questions about a specific CF-Auto-Root binary for a specific device, please go the relevant thread listed on the CF-Auto-Root homepage.

Donate
CF-Root and CF-Auto-Root have been available for many devices (over 50 different models !) and have clocked over 9 million downloads. This is not even counting custom ROMs that include CF-Root (non-Auto) kernels. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every user had donated me $1...

What's installed
- SuperSU binary and APK
- Stock recovery (note that any other recovery you may have installed will be overwritten !)

What's the difference between CF-Auto-Root and CF-Root, and/or other root solutions ?
CF-Root (non-Auto) are manually built rooted kernels and/or flashables that usually provide more than "just root". CF-Auto-Root is built on an automated system that I am constantly improving that takes a stock recovery image and returns an automated rooting packages. These packages are designed to install and enable SuperSU on your device, so apps can gain root access, and nothing more.

The difference with many other rooting solutions is that those will often install a custom recovery for you (I am personally moving away from custom kernels and recoveries, for various reasons), while with CF-Auto-Root you will end up with a stock recovery again.

Not included - custom recovery
A custom recovery like CWM or TWRP is not included.

Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)

Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)

CF-Auto-Root homepage
http://autoroot.chainfire.eu/

MECH_TECH · May 11, 2017

Is there any plan on root for the SM-G920W8 Canadian now that 7.0 is out?

kakabakk20 · May 12, 2017

rooted my phone through CF auto
can i flash TWRP through flashify now? will it cause bootloops?

ashyx · May 12, 2017

kakabakk20 said:
rooted my phone through CF auto
can i flash TWRP through flashify now? will it cause bootloops?

TWRP app?

kakabakk20 · May 12, 2017

ashyx said:
TWRP app?

no, twrp for my device galaxy s6( i have downloaded just need to flash it)..
that's why i am asking will flashing it cause boot loops?

ashyx · May 12, 2017

kakabakk20 said:
no, twrp for my device galaxy s6( i have downloaded just need to flash it)..
that's why i am asking will flashing it cause boot loops?

Then use the twrp app.

ashyx · May 13, 2017

Chainfire said:
It makes the entire SELinux fake-permissive. Taking sepolicy from a recent CFAR and putting it in your port should work 99 out of 100 times.

If you want to do it manually, you'd take the sepolicy from the device's original boot image, adb push it to /data/local/tmp/sepolicy on a device that has a working SuperSU, and run this command:

Code:

supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_patched "permissive *"

Bit of a problem, I tried this and it worked, however the resulting patched sepolicy is massive compared to the original? Original is 751kb and the patched version is 4.62mb.
I have dumped the patched sepolicy with --dumpav and it shows each entry has been changed to "permissive", but why the massive change in file size?

Thanks.

Chainfire · May 13, 2017

ashyx said:
Bit of a problem, I tried this and it worked, however the resulting patched sepolicy is massive compared to the original? Original is 751kb and the patched version is 4.62mb.
I have dumped the patched sepolicy with --dumpav and it shows each entry has been changed to "permissive", but why the massive change in file size?

Thanks.

Probably a bug in the handling. Two of those have been fixed in the development version since last release. New release should be out soon, try again then. Or attach the file here, maybe I can take a look.

[CENTRAL] CF-Auto-Root

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Inactive Recognized Contributor

Moderator Emeritus / Senior Recognized Developer

Similar threads

Top Liked Posts