[CENTRAL] CF-Auto-Root

Status
Not open for further replies.
Search This thread
S

stephymv

Guest
@ShinySide

So basically, all I'm willing to trust is SuperSU. It's that simple.

No, what I actually said has just been quoted above. Super-SUME needs Kingroot so that Kingroot can be replaced by SuperSU, therefore the shady Chinese app is just a mean to an end for me. Unfortunately, this method never worked before for me (Gran Prime and J7, which are rootable with Kingroot), but you never know with Super-SUME Pro, as it seems it works for other people.. So if Kingroot roots the A7 soon, then this method to implement SuperSU will be an option I and others will try.
I never used the word "trust" when referring to Kingroot.

I don't trust brands I have never heard of before, and I don't want to be stuck with them once they have been flashed. That is my right and personal choice, and I'm entitled to them.
 
Last edited:

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,055
9,947
@ShinySide



No, what I actually said has just been quoted above. Super-SUME needs Kingroot so that Kingroot can be replaced by SuperSU, therefore the shady Chinese app is just a mean to an end for me. Unfortunately, this method never worked before for me (Gran Prime and J7, which are rootable with Kingroot), but you never know with Super-SUME Pro, as it seems it works for other people.. So if Kingroot roots the A7 soon, then this method to implement SuperSU will be an option I and others will try.
I never used the word "trust" when referring to Kingroot.

I don't trust brands I have never heard of before, and I don't want to be stuck with them once they have been flashed. That is my right and personal choice, and I'm entitled to them.
Your logic is a little narrow minded and misplaced.
So you trust Supersu and therefore it's author Chainfire? You are aware then that Chainfire has been working with the developer of Magisk and allows Magisksu to work with Flashfire, something that King root isn't?

Also using your terms 'a means to end' then why not flash Magisksu then convert to Supersu with Flashfire?
Simply back up the stock boot image with twrp, look in the twrp backup folder for the image, rename it to boot.img.
Open Flashfire, select Flash Firmware Package, find the boot.img, enable EverRoot and flash.

Finally remove magisk.img and the Magisk folder to completely remove all traces of Magisk.
 

JPCoetzee

Member
Feb 5, 2016
28
1
Samsung Galaxy Tab 3 10.1
Nougat via CF-Auto-Root and Flashfire?

I've just bought a new unlocked S7 with Android 7.0. Can I root stock Android 7.0 with CF-Auto-Root like this:

1. Use CF-Auto-Root and therefore install Android 6.0.1
2. Install FlashFire
3. Install Android 7.0 via Flashfire

?

many thanks
 

cytown

Senior Member
Apr 27, 2009
338
22
SM-9200 newest firmware

@Chainfire,

The newest build number is MMB29K.G9200ZCU2DQC1, do I need to send the newest official recovery to you or I can try use your current MMB29K.G9200ZHU2DPC6 to get root?

If so, will it have change to brick my phone? Or will it wipe all my data?

BTW: will the official update system feature still working after flash auto-root?
 
Last edited:

Mario3D13

Member
Apr 21, 2015
15
0
22
OnePlus 7T Pro 5G McLaren
Hey @Chainfire, I'd like to have CF-Auto-Root for AT&T Galaxy Note Edge (SM-N915A), but I don't know how to extract the recovery.img file from the tar.md5 files provided for the device. Could you please clue me in on how to do so?

-Mario3D13

---------- Post added at 06:48 PM ---------- Previous post was at 06:11 PM ----------

Hey @Chainfire

I've successfully extracted the recovery.img for the AT&T variant of the Galaxy Note Edge (SM-N915A). The build number is MMB29M.N915AUCS2DPK4 and the file can be found at this link: https://drive.google.com/open?id=0B1jBlXhYcgp2ejZheHhybW05Z1U

Looking forward to the CF-A-R file for this device!

- Mario3D13
 

ShinySide

Inactive Recognized Developer
Nov 30, 2013
3,951
4,780
IHB
Hey @Chainfire, I'd like to have CF-Auto-Root for AT&T Galaxy Note Edge (SM-N915A), but I don't know how to extract the recovery.img file from the tar.md5 files provided for the device. Could you please clue me in on how to do so?

-Mario3D13

---------- Post added at 06:48 PM ---------- Previous post was at 06:11 PM ----------

Hey @Chainfire

I've successfully extracted the recovery.img for the AT&T variant of the Galaxy Note Edge (SM-N915A). The build number is MMB29M.N915AUCS2DPK4 and the file can be found at this link: https://drive.google.com/open?id=0B1jBlXhYcgp2ejZheHhybW05Z1U

Looking forward to the CF-A-R file for this device!

- Mario3D13

Att = locked bootloader = no cfauto root
 

tmiket

Member
Sep 17, 2011
20
0
It's just a simple case of flashing the stock firmware to fix.
It could be one of several issues why cf_autoroot hasn't worked. Firmware updates tend to break CFautoroot.
SuperSU is much more on game and keeping up with the changes.
I suggest you flash twrp and then the latest Supersu.
If you do the above you can probably save yourself the hassle of flashing the stock firmware.
I also have a note 4 tmobile. Will auto root work with EQC1 firmware?
Autoroot website has older build.
Mine is totallally stock.
My plan was to root get back deleted photos and unroot.
 

tmiket

Member
Sep 17, 2011
20
0
I also have a note 4 tmobile. Will auto root work with EQC1 firmware?
Autoroot website has older build.
Mine is totallally stock.
My plan was to root get back deleted photos and unroot.
I tried it and now
RECORVERY IS NOT SEANDROID ENFORCING,
How do I fix this? I want to fix this without wiping all data. I hope I'm not screwed.
 

ashyx

Inactive Recognized Contributor
Oct 14, 2012
15,055
9,947
I assume that will root it and fix the boot problem and leave undeleted data.

If data is wiped no point in rooting my moms phone. I'd undo what I did and use diskdigger without root to get thumbnails of pics which is better than nothing.
No data will be wiped.
 

tmiket

Member
Sep 17, 2011
20
0
Cool. Before AF old build I tried kingroot apk. Installed told me it couldn't root phone and to put in request. I uninstalled then but hope it wont screw up SU install somehow.
 
Last edited:

greardon

New member
May 3, 2009
1
0
CF-Auto-Root for Samsung T807P 6.0.1

Auto Root doesn't not work with the latest ROM Release.
Attached is the recovery.img from that version.
 

Attachments

  • recovery.zip
    11 MB · Views: 43

cytown

Senior Member
Apr 27, 2009
338
22
SM-9200 newest firmware

The newest build number is MMB29K.G9200ZCU2DQC1, the attached please find the recovery.img in zip format.
 

Attachments

  • recovery.img.zip
    12.8 MB · Views: 52

MysterySeby

New member
Nov 23, 2011
4
0
To be able to make CF-Auto-Root for a device:

- The device needs to have (and use) separate kernel and recovery partitions
- The kernel and recovery format must be the boot.img standard (no zImage support)
- I need the recovery.img file, so post it in this thread if you need support for a new device :)

Hi, Chainfire,

Today I've decided to upgrade from Android 5.0 to Android 6.0.1. On the old version I had root, but the version I've tried from your website MMB29M.G900FXXS1CQC2 for the new version of android it's not working. After the phone boots back it's still without root and when I restart it in download mode it says that it's a custom version instead of the Official one.
You have a screenshot with my phone details. I don't know if make any difference but in CPU-Z it says that the model is Qualcomm MSM8974PRO-AC.

Please, can you help me with a working version?

Thank you!
 

Attachments

  • Screenshot_2017-05-02-22-08-41.png
    Screenshot_2017-05-02-22-08-41.png
    143.4 KB · Views: 198
  • recovery.zip
    11.8 MB · Views: 8
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 758
    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/
    155
    Requirements and requests

    The the CF-Auto-Root project currently supports the following base boards:

    - Samsung Exynos4
    - Texas Instruments Omap4
    - Qualcomm MSM8660

    Other boards will probably be added soon. Currently only Samsung devices are supported, but I'm looking to expand into other devices soon as well.

    To be able to make CF-Auto-Root for a device:

    - The device needs to have (and use) separate kernel and recovery partitions
    - The kernel and recovery format must be the boot.img standard (no zImage support)
    - I need the recovery.img file, so post it in this thread if you need support for a new device :)
    107
    Devices and threads

    The full list of all supported devices is always available and always current at the CF-Auto-Root homepage.

    Most supported devices have their own threads here on XDA, you can find the thread for your device in the device listing on the CF-Auto-Root homepage as well.

    I will not be maintaining a secondary list in this post, as it would be double work.
    42
    First of all, wasn't sure if it was allowed to post on this thread (it's odd, 4 days old and no post), as I've seen nothing saying I shouldn't, here I go.

    Newbie question here:

    1) Is it possible to flash CWM Recovery with this root?
    2) I'm willing to flash it, should I then just root using CF-Root(non-auto) as it already comes with CWM?
    3) The version of CWM on CF-Root (non-auto) is already outdated, would it be a problem if I just flashed the new version over it with ODIN (download it from clockworkmod.com/rommanager and flash)?


    I ask this because I want to keep my phone as stock as possible, but want to be able to perform a Nandroid backup and flash some ZIPs (if there's a way to perferm/restore Nandroid backups and flash ZIPs w/o CWM please tell me how :) )

    This thread is pretty much quiet because most of the supported devices have their own threads ;)

    (1) Root is a separate thing from CWM. CF-Auto-Root does not include CWM, but if your device has a CWM build you can certainly flash it. The "ROM Manager" app will be able to install it if your device has an "officially" supported CWM build from Koush himself.
    (2) If a CF-Root (non-auto) is available then it's probably outdated. I do not maintain any CWM builds anymore, but others do for most devices, so you should be able to find one.
    (3) You can do that no problem.

    I use Mobile ODIN for flashing ZIPs, but it does not do backup/restores (yet *wink*). For my other backup needs, I use Titanium Backup.

    But to each their own. Some people prefer CWM, some people prefer TWRP, some people like me prefer stock so we can keep the counters at 0/official, etc. CF-Auto-Root keeps all our options open. It doesn't prevent you from anything, though it does also not include anything like that.