FORUMS
Remove All Ads from XDA

[CENTRAL] CF-Auto-Root

11,416 posts
Thanks Meter: 88,137
 
By Chainfire, Moderator Emeritus / Senior Recognized Developer - Where is my shirt? on 8th November 2012, 07:19 PM
Thread Closed Email Thread
5th May 2013, 01:36 PM |#101  
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....
5th May 2013, 10:32 PM |#102  
Senior Member
Flag Barcelona
Thanks Meter: 8
 
More
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

Quote:
Originally Posted by libove

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

8th May 2013, 01:08 PM |#103  
Member
Thanks Meter: 10
 
More
hi.. want to request autoroot for I9308 is I9300 compatible?
21st May 2013, 07:24 PM |#104  
darkrance's Avatar
Member
Thanks Meter: 12
 
More
Did someone request for CF-AutoRoot on SHV-E300s (Korean S4 Variant) already? If not... well, requesting then. Nothing wrong with asking. ^_^
The Following User Says Thank You to darkrance For This Useful Post: [ View ] Gift darkrance Ad-Free
24th May 2013, 04:11 AM |#105  
cezeff's Avatar
Senior Member
Flag Okinawa, Japan
Thanks Meter: 138
 
More
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?
25th May 2013, 12:54 AM |#106  
unk2009's Avatar
Senior Member
Flag New York(Hudson Valley)
Thanks Meter: 279
 
More
Quote:
Originally Posted by Chainfire

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
29th May 2013, 11:01 PM |#107  
Junior Member
Thanks Meter: 2
 
More
Sch-r530u amb1
Quote:
Originally Posted by Chainfire

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.
6th June 2013, 04:24 PM |#108  
PiggySmalls's Avatar
Senior Member
Flag Louisville, KY
Thanks Meter: 1,424
 
More
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.
11th June 2013, 08:08 AM |#109  
Member
Thanks Meter: 2
 
More
Can I request root for samsung mega 6.3? GT-I9205

Thanks!
22nd June 2013, 07:01 AM |#110  
Member
Thanks Meter: 12
 
More
galaxy s4 zoom root
requesting root for samsung galaxy s4 zoom

Thanks dude you do great work. will be sure to donate.
22nd June 2013, 09:17 AM |#111  
Senior Member
Flag USA
Thanks Meter: 265
 
Donate to Me
More
Question
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=pdacomp...=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://forum.xda-developers.com/show....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
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes