[CENTRAL] CF-Auto-Root

Status
Not open for further replies.
Search This thread

Mathubala420

Member
Dec 31, 2012
31
3
Colombo
help rooting ...

No developers is coming to give a tutorial for rooting HCL ME U 2 ...pkease give us a tutorial to root that device... Can we root or not? You devs have given many rooting procedure for many devices and its a shame that we cannot root a small budget device...that is Hcl....
 

libove

Senior Member
Jan 25, 2007
251
10
Barcelona
OnePlus One
OnePlus 5T
Tab2 upgraded, major encryption gotcha, Titanium Backup to the rescue, and all's well

To my surprise, connecting the Galaxy Tab 2 via cable to a PC and using Samsung's much improved Kies did permit the upgrade.
And then locked me out of the tablet entirely, demanding a decryption password at bootup ... although the tablet wasn't encrypted. Oops. A left-over, to be sure, from the botched encryption job I did when I first rooted the tablet. Heh heh. Titanium Backup Pro to the rescue!
Now all upgraded, programs and data restored, encryption working quite correctly at last, and Swype not being quite so much of a performance hog as before!
-Jay

I have a Samsung Galaxy Tab 2 (7.0" 3G model) which came with Android 4.0.4 and which I happily and easily CF-Auto-Root'ed right after I got it in January this year.
Yesterday, the Tab downloaded an OTA upgrade to Android 4.1.2, but when I try to apply that upgrade it fails instantly.
I'm guessing that it is the CF-Auto-Root which is causing the upgrade to fail.

What is the process for upgrading a CF-Auto-Root'ed Galaxy Tab 2 7.0" from 4.0.x to 4.1.x?

thanks!
-Jay
 

darkrance

Senior Member
Apr 7, 2012
90
12
Did someone request for CF-AutoRoot on SHV-E300s (Korean S4 Variant) already? If not... well, requesting then. Nothing wrong with asking. ^_^
 
  • Like
Reactions: smidge1064

cezeff

Senior Member
Sep 21, 2009
591
149
Okinawa, Japan
the sc-06d and sc-0ea which are the SGS3 variants on Japan's NTT Docomo are already supported....is it possible to have the newly released SC-04E, the SGS4, supported as well?...the Auto-Root for the i9505 gives a partial root with the SU binary failing to update after being pushed and installed on to the device.....any thoughts?
 

unk2009

Senior Member
Jul 22, 2009
986
278
New York(Hudson Valley)
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/

Thank you Chainfire...Donation forthcoming

Sent from my Galaxy Nexus using xda premium
 

play3r

Member
Jan 21, 2010
22
2
Sch-r530u amb1

CF-Auto-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible.

This tool worked great. It was fast, easy and accurate.

Just for the record (since I couldn't seem to find it elsewhere), CF-Auto-Root worked for a

- GS3
- US Cellular
- Android 4.1.2 (stock)
- build AMB1

Thank you.
 

PiggySmalls

Senior Member
Jun 2, 2013
1,380
1,420
Louisville, KY
You're like a wizard dude. This is amazing. Had my new S4 rooted in seconds. I've donated to you before, and now I will again.
 
Last edited:

pileiba

Senior Member
Aug 8, 2008
60
12
galaxy s4 zoom root

requesting root for samsung galaxy s4 zoom

Thanks dude you do great work. will be sure to donate.
 

DanMc85

Senior Member
Jan 6, 2008
631
264
USA
What do you need me to pull off the AT&T variant of the Note 8.0 LTE (SGH-I467) to add support for root and how would I go about doing so without Root access... I am all ears at this point...



Tablet appears to be the same as the GT-N5120 other than the LTE/GSM Bands
http://pdadb.net/index.php?m=pdacomparer&id1=4589&id2=4462


Model: SGH-I467
Build: JZO54K
Baseband: I461UCAMF1
Android: 4.1.2

I think the bootloader may be locked like the Galaxy S 4 and might need to be patched...
Bootloader Patch for Galaxy S 4: http://xdaforums.com/showthread.php?t=2292157 - May also work for Note 8.0 ?!?

Partition Structure:
Code:
Heimdall v1.4.0  Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
 http://www.glassechidna.com.au/
  This software is provided free of charge. Copying and redistribution is
 encouraged.
  If you appreciate this software and you would like to support future
 development please consider donating:
 http://www.glassechidna.com.au/donate/
  Entry Count: 25
 Unknown 1: 1598902083
 Unknown 2: 844251476
 Unknown 3: 22597
 Unknown 4: 20057
 Unknown 5: 21327
 Unknown 6: 52
 Unknown 7: 0
 Unknown 8: 0
   --- Entry #0 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 80
 Attributes: 2 (STL Read-Only)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 0
 Partition Block Count: 1734
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: BOOTLOADER
 Flash Filename: sboot.bin
 FOTA Filename: 
   --- Entry #1 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 81
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 1734
 Partition Block Count: 312
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: TZSW
 Flash Filename: tz.img
 FOTA Filename: 
   --- Entry #2 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 70
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 34
 Partition Block Count: 16
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: PIT
 Flash Filename: -
 FOTA Filename: 
   --- Entry #3 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 71
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 50
 Partition Block Count: 2048
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: MD5HDR
 Flash Filename: md5.img
 FOTA Filename: 
   --- Entry #4 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 1
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 8192
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: BOTA0
 Flash Filename: -
 FOTA Filename: 
   --- Entry #5 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 2
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 16384
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: BOTA1
 Flash Filename: -
 FOTA Filename: 
   --- Entry #6 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 3
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 24576
 Partition Block Count: 40960
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: EFS
 Flash Filename: efs.img
 FOTA Filename: 
   --- Entry #7 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 4
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 65536
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: m9kefs1
 Flash Filename: m9kefs1.bin
 FOTA Filename: 
   --- Entry #8 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 5
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 73728
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: m9kefs2
 Flash Filename: m9kefs2.bin
 FOTA Filename: 
   --- Entry #9 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 6
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 81920
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: m9kefs3
 Flash Filename: m9kefs3.bin
 FOTA Filename: 
   --- Entry #10 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 7
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 90112
 Partition Block Count: 40960
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: CARRIER
 Flash Filename: carrier.img
 FOTA Filename: 
   --- Entry #11 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 8
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 131072
 Partition Block Count: 16384
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: PARAM
 Flash Filename: param.bin
 FOTA Filename: 
   --- Entry #12 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 9
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 147456
 Partition Block Count: 16384
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: BOOT
 Flash Filename: boot.img
 FOTA Filename: 
   --- Entry #13 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 10
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 163840
 Partition Block Count: 16384
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: RECOVERY
 Flash Filename: recovery.img
 FOTA Filename: 
   --- Entry #14 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 11
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 180224
 Partition Block Count: 16384
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: OTA
 Flash Filename: -
 FOTA Filename: 
   --- Entry #15 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 12
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 196608
 Partition Block Count: 16384
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: CDMA-RADIO
 Flash Filename: modem_cdma.bin
 FOTA Filename: 
   --- Entry #16 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 13
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 212992
 Partition Block Count: 180224
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: RADIO
 Flash Filename: modem.bin
 FOTA Filename: 
   --- Entry #17 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 14
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 393216
 Partition Block Count: 524288
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: TOMBSTONES
 Flash Filename: tombstones.img
 FOTA Filename: 
   --- Entry #18 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 15
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 917504
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: TDATA
 Flash Filename: tdata.img
 FOTA Filename: 
   --- Entry #19 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 16
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 925696
 Partition Block Count: 114688
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: HIDDEN
 Flash Filename: hidden.img
 FOTA Filename: 
   --- Entry #20 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 17
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 1040384
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: RESERVED1
 Flash Filename: -
 FOTA Filename: 
   --- Entry #21 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 18
 Attributes: 5 (Read/Write)
 Update Attributes: 1 (FOTA)
 Partition Block Size/Offset: 1048576
 Partition Block Count: 8192
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: RESERVED2
 Flash Filename: -
 FOTA Filename: 
   --- Entry #22 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 19
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 1056768
 Partition Block Count: 3145728
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: CACHE
 Flash Filename: cache.img
 FOTA Filename: 
   --- Entry #23 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 20
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 4202496
 Partition Block Count: 4194304
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: SYSTEM
 Flash Filename: system.img
 FOTA Filename: 
   --- Entry #24 ---
 Binary Type: 0 (AP)
 Device Type: 2 (MMC)
 Identifier: 21
 Attributes: 5 (Read/Write)
 Update Attributes: 5 (FOTA)
 Partition Block Size/Offset: 8396800
 Partition Block Count: 0
 File Offset (Obsolete): 0
 File Size (Obsolete): 0
 Partition Name: USERDATA
 Flash Filename: userdata.img
 FOTA Filename: remained
Code:
Partition Names:

major minor  #blocks  name

   7        0       4190 loop0
 179        0   15388672 mmcblk0
 179        1       4096 mmcblk0p1
 179        2       4096 mmcblk0p2
 179        3      20480 mmcblk0p3   ----> EFS PARTITION
 179        4       4096 mmcblk0p4
 179        5       4096 mmcblk0p5
 179        6       4096 mmcblk0p6
 179        7      20480 mmcblk0p7
 179        8       8192 mmcblk0p8
 179        9       8192 mmcblk0p9  ----> BOOT PARTITION
 179       10       8192 mmcblk0p10   ----> RECOVERY PARTITION
 179       11       8192 mmcblk0p11
 179       12       8192 mmcblk0p12
 179       13      90112 mmcblk0p13    ----> RADIO PARTITION
 179       14     262144 mmcblk0p14
 179       15       4096 mmcblk0p15
 259        0      57344 mmcblk0p16
 259        1       4096 mmcblk0p17
 259        2       4096 mmcblk0p18
 259        3    1572864 mmcblk0p19   ---> CACHE PARTITION
 259        4    2097152 mmcblk0p20   ----> SYSTEM PARTITION
 259        5   11186176 mmcblk0p21
 254        0       4189 dm-0
- Dan
 

urayy1

Member
Jun 3, 2012
23
2
unroot upgrade then root

So I have a rooted samsung. If I unroot my device and then upgrade the firmware, would I be able to root it again using cf root?

Looking in the other forums, I now know the answer to this. For others that were wondering, the simple answer is "no." However, if you use SuperSU Pro, there is a possibility that you will maintain root.
 
Last edited:

undergrad

Senior Member
Nov 19, 2012
143
24
Toronto
I have been having issues getting this method to work on my S3 for about a week now. The COM port icon stays BLUE and doesn't turn YELLOW, it does however recognize that my phone is connected by saying 'added". If I try and proceed with the root method anyways the program will sit there for about 5 minutes or so once I click start and then I get the FAIL message in red...I have tried doing it on two computers and I have also tried to reinstall the S3 driver as well as download the other two necessary files a few different times.
Does anyone have any suggestions?

Im running 4.1.2 on my SGH-I747M on Fido
 

titaneds73

Senior Member
Sep 22, 2011
475
142
yakima
chainfire first of all i would like to thank you for all your hard work and dedication.
second i would request or ask if you are going to update cf auto root for the samsung galaxy tab i497 at&t variant .since the jb update i dont think cf auto root would work but i could be wrong just havent been able to find anything confirming or denying.thank you for your time
 

xhejtman

Senior Member
Aug 17, 2012
81
13
root for i9195

Any chance for root for S4 mini? Would it be possible to use cf-autoroot fo i9505 instead of native i9195 which does not exist now, as it is the same msm8960 platform.
 
  • Like
Reactions: DKPHA

DopeJam

Senior Member
Apr 17, 2012
76
14
Hi

I have some stupid questions myself.

I got new SGS 3 International version
Updated to 4.1.2 and rooted with this cf-auto-root. Everything works fine so far

1. If I want to install custom Rom now I guess I cant just go into recovery and flash cm10.1 with only cf-auto-root on my phone?

2. I have latest CWM Recovery (CWM Recovery Touch 6.0.1.9) ready to flash with odin, can I just flash over my rooted phone or do I need 1st to remove this cf-auto-root???

thx
 

melvinaury

Senior Member
Jan 11, 2009
863
170
Hatillo
Hi

I have some stupid questions myself.

I got new SGS 3 International version
Updated to 4.1.2 and rooted with this cf-auto-root. Everything works fine so far

1. If I want to install custom Rom now I guess I cant just go into recovery and flash cm10.1 with only cf-auto-root on my phone?

2. I have latest CWM Recovery (CWM Recovery Touch 6.0.1.9) ready to flash with odin, can I just flash over my rooted phone or do I need 1st to remove this cf-auto-root???

thx

You only need to wipe factory reset and then install the ROM for a clean install or dirty flash just wiping dalvik cache and install. It is recommended to wipe factory reset before installing a new ROM. You can backup you're apps and data with Tibu (titanium backup), but only user apps not system apps.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app
 

DopeJam

Senior Member
Apr 17, 2012
76
14
You only need to wipe factory reset and then install the ROM for a clean install or dirty flash just wiping dalvik cache and install. It is recommended to wipe factory reset before installing a new ROM. You can backup you're apps and data with Tibu (titanium backup), but only user apps not system apps.

Sent from my SAMSUNG-SGH-I747 using xda app-developers app

So I dont need CWM recovery...nice :) thx
 
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.