[CENTRAL] CF-Auto-Root

Status
Not open for further replies.
Search This thread

E:V:A

Inactive Recognized Developer
Dec 6, 2011
1,447
2,222
-∇ϕ
If you post up the latest (stock!) recovery.img I can give it a shot, but you'll have to test that it works, as this device is significantly different from the models currently supported. Worst case it doesn't work and you'll have to reflash full stock.

Ok, so let me see if I can do this right.
I downloaded the FW from HERE, and marked as:
"Galaxy S4 Mini LTE GT-I9195 SEB I9195XXUBML4 Android 4.2.2 20.12.2013 2340422"
==> SEB-I9195XXUBML4-20140212115313.zip
After unzip, I got: I9195XXUBML4_I9195SEBBNA1_I9195XXUBML4_HOME.tar.md5
+ the odin file SS_DL.dll

Checked MD5 with check_tar_md5, and got this recovery.img.

recovery -> /dev/block/mmcblk0p14

That was the one closest to match what I think I have. I think it's the right one, but how can I easily check and verify if this is the same as what I have on the phone? (I'm not allowed to read /dev/block/platform/msm_sdcc.1/by-name/recovery with dd, but perhaps I'm doing it wrong, since I'm not yet rooted.)

BTW.
Code:
[SIZE=2]$ tar -tvf I9195XXUBML4_I9195SEBBNA1_I9195XXUBML4_HOME.tar.md5
-rw-r--r-- dpi/dpi      106412 2013-12-20 19:59 sbl1.mbn
-rw-r--r-- dpi/dpi      133068 2013-12-20 19:59 sbl2.mbn
-rw-r--r-- dpi/dpi      311316 2013-12-20 19:59 sbl3.mbn
-rw-r--r-- dpi/dpi      144388 2013-12-20 20:00 rpm.mbn
-rw-r--r-- dpi/dpi      779832 2013-12-20 20:00 aboot.mbn
-rw-r--r-- dpi/dpi      200052 2013-12-20 20:00 tz.mbn
-rw-r--r-- dpi/dpi     7520528 2013-12-20 20:00 boot.img
-rw-r--r-- dpi/dpi     8433936 2013-12-20 20:00 recovery.img
-rw-r--r-- dpi/dpi  1511099056 2013-12-20 20:00 system.img.ext4
-rw-r--r-- dpi/dpi    50169600 2013-12-20 20:00 NON-HLOS.bin
-rw-r--r-- dpi/dpi    12259536 [COLOR=Red][B]2014-01-07[/B][/COLOR] 13:50 cache.img.ext4
-rw-r--r-- dpi/dpi     7901368 [COLOR=Red][B]2014-01-07[/B][/COLOR] 13:50 hidden.img.ext4[/SIZE]
 
Last edited:

TweakerL

Senior Member
Oct 6, 2010
280
364
37
Rosedale, MD
Recovery for SM-T900

I pulled this recovery.img from T900XXUANB5, I imagine it should work. I'll gladly test it. It's the UK version, but I imagine the recovery is the same.
 

Attachments

  • recovery.zip
    7 MB · Views: 58
Last edited:

fightincowboy

New member
Mar 17, 2009
3
0
Milwaukee, WI
Verizon Galaxy S4 NCF Root?

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/



Can you add support for the VZW 4.4.2 upgrade Please?
 

bozob

Member
Dec 29, 2007
15
2
ATT GAlaxy S3 SGH-I747

I had done this successfully on a previous version of this phone just a month ago. But I had to have that phone replaced under insurance (took a swim with it) and the new phone won't root using this method.

I've enabled USB debugging, run Odin3-V1.85, loaded the ATT-sgh-i747 tar.md5. It loads, reboots to recovery, I see that it's loading into recovery mode and running the necessary processes before rebooting. But SuperSU doesn't get loaded on, and when I try to use the store to load it, it says that it can't find the SuperSU binary.

I've loading TRWP(?), but it won't see any files on the SD card and won't mount the card.

Any suggestions on what's going wrong and how I can fix it?

NOTE: I just found out that every time I try to do a recovery reboot (volume-up/home/power) it loads the red log and does a CF-auto-root. It's as if the efforts to write the SuperSU binary and copy back in the standard recovery don't work. I don't know what could be causing this.

Thanks

Baseband version: I747UCUEMJB
Kernel version: 3.0.31-2024954
se.infra@R0210-11#1
Oct 31 01:05:53 KST 2013
Build #: JSS15J.I747UCUEMJB

SE for Android status:
enforcing
SEPF_SAMSUNG-SGH-I747_4.3_0010
 
Last edited:

10amla

Senior Member
May 2, 2013
118
28
Glendale
Samsung Galaxy Camera 2

Chainfire,

Could you please create a CF-Auto-Root for the Samsung Galaxy Camera 2(EK-GC200). There is one for the Galaxy Camera(EK-GC100) but that was an earlier version of Android(4.1) as opposed to 4.3 on the Galaxy Camera 2. I've attached the recovery.img(hopefully I've both extracted it and attached it correctly).
 

Attachments

  • recovery.img
    6.8 MB · Views: 39
  • Like
Reactions: R.Leonardo

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
I pulled this recovery.img from T900XXUANB5, I imagine it should work. I'll gladly test it. It's the UK version, but I imagine the recovery is the same.

http://download.chainfire.eu/413/CF-Root/CF-Auto-Root/CF-Auto-Root-v2wifi-v2wifixx-smt900.zip

Chainfire,

Could you please create a CF-Auto-Root for the Samsung Galaxy Camera 2(EK-GC200). There is one for the Galaxy Camera(EK-GC100) but that was an earlier version of Android(4.1) as opposed to 4.3 on the Galaxy Camera 2. I've attached the recovery.img(hopefully I've both extracted it and attached it correctly).

http://download.chainfire.eu/414/CF-Root/CF-Auto-Root/CF-Auto-Root-sf2wifi-sf2wifixx-ekgc200.zip
 

cantenna

Senior Member
Aug 5, 2012
2,349
566
Newcastle
Chainfire,

Thanks for the root for the Galaxy Cam 2. Works great. I owe you the beverage of your choice.

Wow, thanks Chainfire! Can't wait to try. Will also send you a beer! Cheer!

---------- Post added at 09:04 AM ---------- Previous post was at 08:55 AM ----------

Chainfire,

Thanks for the root for the Galaxy Cam 2. Works great. I owe you the beverage of your choice.

Will this work for all galaxy camera 2 models? I just did a samsung update on my camera a few days ago. Its an ek-200 Australia. Thanks
 

cantenna

Senior Member
Aug 5, 2012
2,349
566
Newcastle
Is there a way to apply this root from another rooted device? Don have access to PC atm

Sent from my GT-I9505G using XDA Premium 4 mobile app
 
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.