[CENTRAL] CF-Auto-Root

Status
Not open for further replies.
Search This thread

MotorBoater84

Member
May 26, 2015
14
0
Houston
Request for MetroPcs Galaxy s5 on lollipop 5.1.1

Hello Chainfire
I am requesting an updated root method for the MetroPCS Galaxy s5 sm-g900t1 running on the recent lollipop 5.1.1 update. Attached is a copy of the recovery.img
Thanks in advance for your awesome work Chainfire!
 

avadis99

Senior Member
Dec 19, 2012
104
5
Yerevan
I am not getting a reply to my posts in regard to GT-I9500 Galaxy S4 new update, the last CF-root posted is 5.0.1 and there is no more as 5.1.1 CF-root and for this reason I am not upgrading my phone as I use ODIN method to root it, the new upgrade is PDA: DH7/PHONE: OD4/CSC: OI1 (CAC), that shows, can someone help and guide me?
 

Malvineous

Member
Oct 6, 2015
11
1
Hi @Chainfire,

Thanks for such a fantastic method for doing this!

I also just tried the Nexus 5 (hammerhead) CF-AutoRoot after reflashing with the 6.0.0 factory image released yesterday. Booting CF-AutoRoot (the version for Android 5.0 on your site) went fine, the whole thing ran as per usual without any apparent errors, but when the phone rebooted it got stuck on the booting animation (four animating coloured circles). At this point adb still worked so I could get a shell on the device, but I'm not really sure what to look for - the su binaries were in the expected locations and running them did nothing (they just exited immediately returning 1) which I assumed was because the boot process was still active.

Note that I did all this *after* booting the device with 6.0.0 for the first time, so it wasn't the app cache being rebuilt - that did indeed take a while, but finished successfully before I ran CF-AutoRoot.

In the end I just reflashed the system partition and everything went back to normal and the phone finished booting, but of course without SuperSU installed.

If there's anything I can do to help test or work out what happened, let me know. I'm also happy to beta test any changes if you don't have access to a Nexus 5. You've asked for a recovery image for unsupported devices, so here's the one for Nexus 5 / hammerhead for Android 6.0.0 (9.8MB) in case that helps. But like I say, the install process ran with no errors I could see, so perhaps that won't be so helpful.

Thanks again for your amazing efforts!
 
  • Like
Reactions: Tarcis

marinierb

Senior Member
Mar 23, 2008
1,080
142
Hull, Québec
Google Pixel 7

cronociclope

Senior Member
Sep 30, 2012
245
158
Trujillo
Request for Galaxy A5 A500M on lollipop 5.0.2
Hello @Chainfire
I am requesting an updated root method for the Samsung Galaxy A5 A500M running on Android 5.0.2 Lollipop update. Attached is a copy of the recovery.img
Thanks in advance for your amazing work Master! :good:
 
Last edited:

UPdownLoAD

Senior Member
Feb 4, 2007
319
235
Sprint Galaxy S5 Sport SM-G860P

Any chance of getting an updated root for the Sprint Galaxy S5 Sport SM-G860P please? I have been having lots of crashes since going to L, and I suspect the root/recovery is the problem since I don't have issues when restored to stock; last root created was for 4.4.2, current version is 5.0, OH1.

Attached are recovery and boot from OH1. Please let me know if anything else is needed for an updated root. Thanks!!
 

Attachments

  • boot.zip
    9.9 MB · Views: 9
  • recovery.zip
    10.3 MB · Views: 18
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.