[07.09.2012][CF-Root 5.6] K**,LA-1346,LB1,LC1,LP-1YF89,LQ-23,LR-GIKQ - su+bb+CWM5

Search This thread
By:
Advanced…
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
I posted this Q in the Q&A thread but didn't get an A, so I'll try rephrasing my question. I hope it doesn't get deleted from this thread by mods, because it's a question relating to the instructions at the beginning of this thread. A response from Chainfire or Dr.Ketan would be wonderful.

Before I follow the instructions in post 2, method 1.3 of this thread (like MiRaCL I can't use 1.1 or 1.2), what can I do to increase my chances of recovery should anything go wrong during the rooting procedure?

The words "BACK UP" appear in big red letters in my mind, but if I understand correctly you have to be root in order to make a backup.
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
39,230
76,795
Gujarat, India
drketanrom.com
Samsung Galaxy Watch 4
Samsung Galaxy S22 Ultra
@syncopath

If you follow instruction to the letter, There is no chances to have anything wrong
What I believe is you have non rootable ROM, you want to downgrade to Modified Factorysys KJ1 ROM from CF. If yes, Here are the steps in short
-Download said ROM (megaupload link are down, use 4th line on my signature to download same)
-Flash using PC Odin (here is guide, how to flash using PC odin)
-After flashin, you will have rooted ROM
-Now get CWM, from main(first few) post
-Here I suggest one thing, You will have kernel KJ1, N theoritically you have to get CWM for KJ1, But I recommend to go for CF Root kernel for your next ROM
e.g. If you finally going to update LC1 ROM, then download, I have CL1 kernel, Not KJ1)
- After this you will have KJ1 ROM + Root + CL1(or any you have selected) Kernel + CWM
- Now you can update to next final ROM with CWM (to keep Root intact)
Hope everything should be clear now.
GudLuck!

And yes b4 rooting, you will have limited option to backup.
 
Last edited:
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
@Dr.Ketan, thank you for your incredibly swift and informative reply.

I have read both your rooting guide and Chainfire's extensively. I do indeed have a non-rootable ROM, version LA6, The Netherlands (Telfort), so I will need to downgrade to Chainfire's KJ1 and then hopefully back up to LA6.

One thing still worries me. If I am rooted OK and back up to LA6, but not the original Netherlands (Telfort) version, will I still be able to get back on to the Telfort 'phone and data network?
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
39,230
76,795
Gujarat, India
drketanrom.com
Samsung Galaxy Watch 4
Samsung Galaxy S22 Ultra
Latest available ROm for netherland is
firmware: N7000XXLA6/N7000XENLA1/N7000XXLA4/N7000XXLA6
Modified: 03/02/2012 5:12:53 PM
Filename: GT-N7000_XEN_1_20120203171232.zip.enc2

Get check fus n download this ROM from here then (post Root) you can flash with CWM

Sent from my GT-N7000 using xda premium
 
Last edited:
  • Like
Reactions: syncopath
M

mykeldrip

Senior Member
Jun 8, 2010
502
29
mykeldrip said:
So i traded my att ver for int ver.

It seems to be rooted with the chainfire i do believe..idk for a fact but it seems if u flash certain roms i can lose root?
Also im sure aosp needs aosp kernal is it safe to just flash kernal over it? This is all so different than im used to which was download rom or kernal flash via cwm!
Alsol i want to flash ics roms etc...

Do i need to root it differently?

Or can i juat follow directions in thread and all will be ok?

Also will i need to really pay attention to different builds etc..or can i just wipe all going from rom to rom like im used to?

Lastly if i get ics running and decide to go back to a stock rom...i.e...gingerbread do i then need to flash a different repack since i odin'd a chinese ics?? so confusing!!

Sorry for noobness but man this is different from what used to!! sorry!!!!

Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse



Sent from my GT-N7000 using XDA

Sent from my GT-N7000 using XDA
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
39,230
76,795
Gujarat, India
drketanrom.com
Samsung Galaxy Watch 4
Samsung Galaxy S22 Ultra
Usually all newer kernel are identical. You can see main post, many kernels sharing just single kernel.like kk1-2-3-4-5 using same.
CF himself said, when no matching kernel available, use near to it.
Myself hardly change kernels, once after 2-3 update. And never face any issue.
So LC1 is best near to LC2, and we can use it, if necessary, CF will release LC2.
Another thing, looking to other custom kernels like abyss/Franco's are not releasing kernel according to each ROM. And same kernel running on many different ROMs.
 
D

DSD99

Senior Member
Mar 31, 2009
104
24
GPRS said:
I used the LC1 ，but the phone can't reboot

I can't find the reason.

I user the LC1 kernel several times,never reboot successful.

somebody can tell me why ?
Click to expand...
Click to collapse

Me either, downloaded several times, checked md5 file is fine it just doesn't work on my phone.

ClockworkMod recovery is loadable if i hold down the buttons but the phone wont boot into android, just get black screen after Samsung logo.
Wanted to flash it again over itself incase something didn't quite flash right but cant because it cant be flashed from recovery only from mobile Odin.Flash franco kernal and boots fine again.
Dont know whats going on with it.
im on rocket rom v23
Any ideas?
 
Klyupp

Klyupp

Senior Member
Nov 28, 2009
252
35
Amsterdam
Got a new white note today, it's running XXKK5 and I can't find in the OP if this can be used with the zergrush exploit? Can anyone confirm?

Send from CM9 powered Galaxy Note :)
 
E

eakvigo

Member
Jul 28, 2008
16
0
I'm update new stock rom N7000DXLC2


I'm unable to root using CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5.zip

--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: permission denied
--- cleaning up
--- rebooting



Help me
 
You must log in or register to reply here.

Similar threads

eybee1970
  • Locked
[ROM] ROCKET ROM - v23 - GB - LC1 [Update 29/03] - JKay Mod 13.6.1 - MIUI Style Theme
Replies
10K
Views
2M
eybee1970
eybee1970
Phil3759
  • Poll
[PhilZ-cwm6][n7000] Stock Kernel+CWM6+Root+exFAT+NTFS-LTA
Replies
4K
Views
2M
nrmldgs
nrmldgs
bauner
[ROM][CM12.1][Lollipop][Android 5.1.1] NightOwl 20180124
Replies
12K
Views
2M
VashlaK Belarus
VashlaK Belarus
maxicet
[ROM] TheMIDTeam 1.6.2 Codename "B&G" LQ3 (07/20/12)
Replies
4K
Views
698K
M
mangesh hotkar
criskelo
[ROM] Criskelo's ICS V11.2 << LRK 4.0.4>> ICS 15 togg TW*S3*-AROM <<<SIM-Lock FIX>>>
Replies
4K
Views
1M
raghav84
raghav84

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 502
    Chainfire
    Chainfire
    This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod recovery

    THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THE ENTIRE FIRST FEW POSTS!

    Donate
    There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1... :)

    Main features
    - The kernel is fully stock and taken from the original firmware, with just the following added:
    - Root
    - Busybox v1.19.2-cm71
    - ClockWorkMod Recovery 5
    - CWM Manager (see below for more detail)
    - Custom boot / init scripts
    - Custom boot animations

    v5.3 and newer
    - SuperSU (replaces Superuser)
    - "Fake-secure" (ro.secure=1, but ADB is patched to run as ro.secure=0)

    v5.5 and newer
    - CWM updated to v5.5

    v5.6 and newer
    - Possible brickbug fix

    Installation instructions
    Please see the next post !

    Other kernels
    Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.

    When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager app may remain, but probably won't do anything useful.

    ClockworkMod
    CF-Root includes a custom version of CWM5. I always make custom versions, as the originals often do not take some Samsung specific things into account.

    CF-Root/CWM5 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root

    - Booting into recovery will immediately give you CWM. The standard recovery will only be started if a Samsung package is detected.
    - ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.

    CWM Manager
    Because of incompatibilities with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011). You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.

    Features:
    - Boot to ClockWorkMod Recovery
    - Boot to Download mode
    - Reboot normally
    - Backup firmware
    - Restore backups (including partition selection)
    - Delete backups
    - Install APKs
    - Flash CWM3/4/5 update.zip's
    - Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
    --- without changing warning triangle status or increasing flash counter
    - Flash complete firmwares (seperate files as well as .tar and .tar.md5 archives, dump files in /sdcard/external_sd/firmware folder)
    --- without changing warning triangle status or increasing flash counter
    --- can pre-root new firmwares during flash

    Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility !

    Custom boot / init scripts
    CF-Root will execute the following scripts if present, in the order listed:

    - /system/etc/init.d/* (there can be many files here, no extensions! use #!)
    - /system/bin/customboot.sh (busybox sh)
    - /system/xbin/customboot.sh (busybox sh)
    - /data/local/customboot.sh (busybox sh)

    Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.

    Custom boot animations and binaries
    CF-Root also supports custom boot animations:

    - /system/media/bootanimation.zip
    - /data/local/bootanimation.zip

    And custom boot binaries:

    - /data/local/bootanimation.bin

    Installing busybox over the included version
    It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.

    How ?
    I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. It is now used to make CF-Root for many devices!

    Help! Which file do I use ?
    Listen closely, for I will say zis only once!

    Go to Settings -> About phone -> Kernel Version. Note the string present there:

    2.6.35.7-N7000XXKJ4-CL641703

    What matters most (KJ4) in this case, is in bold. Try to find the matching file under downloads:

    CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip

    The XX and XEN identifiers are not that important. Usually a "KJ4" kernel is a "KJ4" kernel, and that is that. Sometimes (pretty rare) it happens there will be multiple different kernels with the same name in different firmwares, that are actually different. If this happens, they are usually only very minor changes and you should expect them to still be fully compatible. I include the "XX" and "XEN" identifiers so the very advanced users can deduce from which full firmware I have taken the kernel file.

    Don't worry too much, just find the matching download and use it. What if there is no matching download ? You can ask me to make one, but I can tell you right now, I very very rarely make CF-Root's for kernels on request, unless it is the very latest kernel that has been released by Samsung. In the latter case, be sure to let me know. If there's no match and I'm not making one, try finding the closest match. You should treat "KJ4" as a number, but instead of 1-9, we have 1-9, A-Z (where A would be 10, and Z would be 35). "KJ3" is really close to "KJ4", "KF1" is not close to "KG4" at all. I hope that makes sense.

    @Developers: I have noticed that doing a NANDROID RESTORE while connected to your computer AND Eclipse is running may cause the restore to fail. Eclipse automatically starts logcatting in the background, which will prevent /system from being properly restored.

    Download
    These are general-purpose downloads. See the posts following this one for the kernels.
    View
    188
    Chainfire
    Chainfire
    Installation intructions

    The Samsung Galaxy Note keeps track of the kind of kernel you are running (stock or custom) and how often you have flashed kernels. This is probably for warranty purposes. There is currently no known way to reset this counter on the SGN.

    So, what we want to do is get root, busybox, and CWM, all without getting that ugly yellow triangle or updating the flash counter on our device. Luckily, CF-Root allows for all these things. The new CWM Manager even allows you to flash new firmwares and apply root to them while flashing.

    We need to get rid of ODIN pretty much completely, and we can! The difficult part is getting root the first time, after that, it should be happy camping forever.

    --- Chapter 1: Initial application of root ---

    DO NOT USE ODIN TO FLASH THE KERNEL !

    This is the annoying part. There are three different methods:

    1.1. If you are already rooted

    - Download the attached "InitialRootFlasher.zip" and extract it somewhere
    - Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
    - Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
    - Start "already-rooted.bat" and follow the instructions

    For those needing to do this manually (Linux boxes and such), this is the important command. Place the zImage file on your phone (example: /data/local/zImage) and execute this command in a rooted shell:
    dd if=/data/local/zImage of=/dev/block/mmcblk0p5 bs=4096

    1.2. If you are not rooted yet: Using the zergRush exploit This method no longer works on KL* and newer firmwares!

    (while it still works on our firmwares, this exploit will probably be fixed soon! Known to work on KJ1 and KJ4 firmwares)

    - Download the attached "InitialRootFlasher.zip" and extract it somewhere
    - Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
    - Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
    - Start "not-rooted-yet.bat" and follow the instructions

    1.3. If you are not rooted yet: Flash a modified FACTORYFS

    I am providing this method just this once, for the KJ1 firmware. This is the /system part of the KJ1 firmware, modified so at first boot it will flash the KJ1 CF-Root and reboot, without getting you the yellow triangle or increasing the flash counter.

    Using a newer firmware? Do this operation first, then flash the newer firmware back using CWM Manager. This is explained in Chapter 3 below.

    Download: http://www.multiupload.com/YB9EL8D8O3

    - Optional: flash the full KJ1 firmware first
    - Unzip the file, you should get "SGN_XX_OXA_KJ1_FACTORYFS.tar"
    - Make sure your SGN is NOT connected to your computer
    - Reboot your SGN into "download mode" (see below)
    - Start ODIN
    - Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
    - Connect the SGN to your computer
    - Make sure "repartition" is NOT checked
    - Click the START button
    - Wait for the phone to reboot TWICE
    - Done

    If you do not know how to get into download mode:
    - Turn off the device
    - Count to 10
    - Hold the "home" (the big physical button in the middle) and "volume down" buttons
    - Press and release the power button (keep holding "home" and "volume down" !) to turn the device on
    - You should get a download mode screen
    - If it tells you to press a button to continue, do so

    --- Chapter 2: Getting rid of ODIN ---

    This is easy. Find ODIN, and delete it. In the future you should only need it to flash bootloaders, which probably will only really be needed one time: when upgrading from Gingerbread to Ice Cream Sandwich.

    --- Chapter 3: Upgrading your firmware ---

    My CWM Manager application has a full-fledged firmware flasher built in. Using the flasher from CWM Manager does NOT give you the yellow triangle or increase the flash counter.

    3.1. Flashing a new kernel

    This is easy. CWM Manager can flash zImage files (on any rooted kernel), zImage files inside a .tar file (only on a CF-Root kernel), and zImage files inside a .tar.zip (only on a CF-Root kernel). Note that zImage must be the ONLY file in an archive, if is is inside a tar or zipped tar.

    - Put the zImage (or tar, or zip) file on your SD card
    - Open the CWM Manager app
    - Select "Flash kernel"
    - Select the file you just put on your device
    - CWM Manager will flash the kernel and reboot

    If you flash a non-CF-Root kernel, you will lose a lot of functionality from CWM Manager. However, the app will (likely) still allow you to flash kernels.

    3.2. Flashing a new firmware

    Important: This works ONLY on a CF-Root kernel !

    CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.

    - Download the firmware you want to flash
    - If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
    - Create a folder named 'firmware' on your external SD card
    - Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
    - TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
    - Open the CWM Manager app
    - Select "Flash stock firmware"

    - At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.

    - If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:

    1: Keep CF-Root kernel
    Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.

    2: Pre-root system
    Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.

    3: Flash normally
    Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.

    - CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.
    View
    150
    Chainfire
    Chainfire
    ALL THE KERNELS IN THIS POST ARE OUTDATED AND/OR DANGEROUS, GO TO THE NEXT POST !

    CF-Root-I9220_ZC_OZH_LP1-v5.2-CWM5.zip

    CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5.zip *read before flashing LPY: http://xdaforums.com/showpost.php?p=25966147&postcount=1322* *old*

    CF-Root-SGN_ZS_OZS_LPF-v5.3-CWM5.zip *old*

    CF-Root v5.5:

    CF-Root-SGN_XX_OXA_LPY-v5.5-CWM5.zip
    CF-Root-SGN_ZS_OZS_LPF-v5.5-CWM5.zip
    CF-Root-SGN_DD_ODD_LP8-v5.5-CWM5.zip
    CF-Root-SGN_DX_OLB_LP9-v5.5-CWM5.zip

    Be warned that *all* of the above kernels may be suffering from the superbrick bug ( http://xdaforums.com/showpost.php?p=25966147&postcount=1322 ) !
    View
    140
    Chainfire
    Chainfire
    PLEASE READ THIS POST BEFORE FLASHING !

    CF-Root-SGN_XX_OXA_LPY-v5.6-CWM5.zip
    CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
    CF-Root-SGN_DD_ODD_LP8-v5.6-CWM5.zip
    CF-Root-SGN_DX_OLB_LP9-v5.6-CWM5.zip

    CF-Root-SGN_XX_XEU_LQ2-v5.6-CWM5.zip
    CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5.zip
    CF-Root-SGN_XX_DBT_LRG-v5.6-CWM5.zip
    CF-Root-SGN_XX_OXX_LRI-v5.6-CWM5.zip
    CF-Root-SGN_XX_DBT_LRK-v5.6-CWM5.zip
    CF-Root-SGN_XX_DBT_LRQ-v5.6-CWM5.zip
    View
    135
    Chainfire
    Chainfire
    Downloads

    See the second post of the thread for flashing instructions. If you're thinking about using ODIN to do it, you should probably read that post.

    CF-Root-SGN_XX_OXA_KJ1-v5.0-CWM5.zip
    CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM5.zip
    CF-Root-SGN_ZS_MUL_KJ6-v5.0-CWM5.zip
    CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.zip
    CF-Root-SGN_XX_DBT_KK9-v5.0-CWM5.zip
    CF-Root-SGN_XX_AUT_KKA-v5.0-CWM5.zip
    CF-Root-SGN_XX_ODD_KL3-v5.0-CWM5.zip
    View

New posts