WARNING KNOW WHAT YOU ARE DOING BEFORE ATTEMPTING THIS, IF YOU DON'T UNDERSTAND WHAT IS BEING TALKED ABOUT HERE YOUR BEST TO LEAVE IT ALONE
This is a Vibrant kernel/recovery image that includes EXT2/3/4 support as well as init.d support for user scripts. Everything works as expected Wifi/GPS/BT etc
This eliminates the race condition as the scripts in init.d run before the default Android services.
You can add any user scripts you want by adding them to the /system/etc/init.d folder e.g "05userscript" They are parsed by order 00 then 01 then 02 etc
BEFORE FLASHING THE KERNEL You must flash the init.d update to add the needed folder and files to boot with this kernel. That is because the completion script sets a prop value telling the default Android services to run. If that prop isn't set you will be sitting at the Vibrant screen forever.
The new init.d updates remove any other versions of busybox and install the correct version and symlinks to take care or the issues people have been having with multiple BB installs. There is a version that has no data to SD script for those that want to run other lag fix's. And then there is one with the data to SD script.
Default CPU frequencies and Overclocked versions available.
OCv4
Clock Drift fixed
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
more up/down threshold changes
Wake Lag improvements
Switched back to "CFQ" for perf reasons over deadline and no-op
BB symlinks removed from ramdisk (to avoid conflict with mods that make their own links to BB)
OCv3
NO MORE WAKE LAG!!!!
Reverted back to OC on boot
up/down threshold adjustments again
rebuilt with crosstool-ng 1.8.0 gcc 4.3.4
OCv2
Extra steps are back. [100/200/400/600/800/1000/1200] YOU MUST use setCPU to up it to 1.2Ghz it is set at 1Ghz default for stability reasons,this CPU is very sensitive to voltage/freq changes. Should be more stable overall then prev build. (Thanks Unhelpful)
up/down threshold adjustments
SCv9
No More WAKE LAG!!
Uncommented FM Radio module in init.rc
SCv8
Conservative/Deadline
SCv7
Ondemand/Deadline are default now in
SCv6
ADB issue resolved.
Busybox issues resolved. Can now update through stericson's BB utility from the market.
OC version available with extra 600mhz and 1200mhz step added (you still have 800, 1000 etc) Linpacks in the 10.0's (Thanks to ivanmmj for the help)
SCv5
Volume rocker fixed
cleaned up RAMDISK
reverted to stock recovery (rev1 had clockwork as the recovery but was having a few issues)
added symlinks for busybox applets
Fully compatible with Clockwork (backups/restore from ROM manager) (no more annoying reboot before Clockwork starts)
INSTRUCTIONS
Note:The new init.d updates install BusyBox for you and create the symlinks. They also remove any other prior version before doing so
1.Choose one of the init.d updates that suites you.
A.
Data and Dalvik init.d-busybox with data to SD update.zip
MD5:0317ae432d2db15e51fd0da2c4d53857
B.
Data and Dalvik init.d-busybox without any lagfix scripts update.zip
MD5:9e720b587188676e7fff2f144433bd23
2.Reboot into recovery and flash this. Once booted check your system/etc dir for the init.d folder and scripts inside before moving forward. If they are there we move on.
3.Download the kernel/recovery image
OCv4 1.2 No Wake Lag/No Time drift
Update.zip (flash through clockwork recovery)
www.justanotherdev.slackdev.com/Kernel-Vibrant-OCv4.zip
MD5:33487d4bec50d123d0bb10843d141723
ODIN Image
www.justanotherdev.slackdev.com/kernel-vibrant-OCv4.tar
MD5:5aae7e5ab08227e1fd4c931c24f678ac
OCv3 1.2 No Wake Lag
kernel-vibrant-OCv3-NG.tar
MD5:1e2ddb9bd9fe4adb0ccc73fa818c63be
OCv2 1.2Ghz with extra steps back in. More aggressive up/down thresholds
kernel-vibrant-oc-ng.tar
BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
SCv9 No Wake Lag
kernel-vibrant-SCv9-NG.tar
MD5:0614a8205087a84fe34bbe2c653183a9
SCv8
kernel-vibext4-8.tar.md5
MD5:e9c2a45d89d994c485b8af8e1b1a923c
SCv7
kernel-vibext4-7.tar.md5
MD5:cedbad0273a2dd2a1b2d0a4ed3e89fce
4.Reboot into download mode and use ODIN to flash the kernel. Use the CSC field with no PIT file. This will flash the kernel/recovery
NOTE:You can find ODIN in my other thread here
If you have an EXT2/3/4 partition I used tabbals script (to tired and will be re-writing this shortly) for the mean time to bind your data to the EXT partition or otherwise known as the "EXT hack" for those that want those wondering. If you do not want this script you can remove the 07a2sd script from the init.d folder before flashing the kernel.
Now you can add any user scripts you like to the init.d folder and we dont need to use the "playlogos" hack anymore. This is a work in progress and more tweaks/features will be integrated and updated as they are tested and made available in this thread. I had to give you guys something to mess around with. And a proper way to run user scripts.
Thanks to Unhelpful, supercurio, cyanogen, scepterr, wes garner, Eugene_373 and everyone that helps out in the XDA community!
Sources:
Kernel: T959 source from opensource.samsung.com
Voodoo-fix http://github.com/project-voodoo
OC patch posted below
Enjoy!
Need to revert to the stock kernel??
www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
MD5:9f89f8c5a6c785ff967806a4ca70906f
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
anomalous3 said:
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
Click to expand...
Click to collapse
Agreed. Feel free to use this kernel/recovery in your ROMS just give credit and I'll be more than happy
Also more to come folks just sit tight. This is my hobby and I have to take care of some real life issue ATM...cough ...the woman...cough.
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
Any scripts will work fine just as before. The main difference is that we dont need the "playlogo" hack that was used previously which runs a script called userinit from /system/bin/ now all user scripts will go in /system/etc/init.d/
Now we have this folder (init.d) to store all are user scripts in and gives us the option to choose which runs first according to how they are labeled. Just have a peek inside the init.d folder to see what I'm talking about. Init.d is pretty common on Linux boxes just not Android
Also to be clear this should clear up race conditions as any user scripts in init.d will run before the default Android services.
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" (which I should have names d2sd but whatever lol) in this build. Same script so yes the scripts will work just fine
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
anomalous3 said:
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
Click to expand...
Click to collapse
Exactly.
Have fun I'm off to bed for now. I've been running this for 2 days without issues. Please let me know if you find any bugs. WiFi BT and everything else should be working just like the stock kernel I also haven't had one kernel panic yet.
justanothercrowd said:
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" in this build. Same script so yes the scripts will work just fine
Click to expand...
Click to collapse
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Im definately +1 for getting rid of odin, Jac do you use github at all ?
frank707 said:
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Click to expand...
Click to collapse
This is correct yes.
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
I use git/mercurial but not github. I will be creating an account their to share code as people have been requesting it
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
good to see some Super D/E/F power using this phone. Would I be correct in thinking the main problem with packing the kernel into a boot.img would be the offsets, or do you think we're dealing with something a bit more serious?
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Goog1e Phone said:
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Click to expand...
Click to collapse
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
justanothercrowd said:
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
Click to expand...
Click to collapse
attempted to flash the first zip but init.d folder wasn't created. Wouldn't flash through stock recovery, attempted to flash through cw, will try again and update
The follow error occurs on flash
Code:
E:Can't chown/mod system/etc/init.d/02a2sd
(No such file or directory)
E:Failture at line 7:
set_perm 0 1000 0755 SYSTEM:etc/init.d/02a2sd
Installation aborted.
problem is in script, just edited it, about to try to flash
no dice, no install
davbran said:
no dice, no install
Click to expand...
Click to collapse
EDIT: realized my FTP client wasnt uploading in binary mode which caused some issues.
Re-download the files they have been hashed and double checked.
Enjoy!
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.
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.
--- reserving another post ---
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
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_DX_XSP_KL1-v5.0-CWM5.zip
CF-Root-SGN_XX_DBT_KL7-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_KL8-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA1-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA3-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.zip
CF-Root-SGN_XX_SER_LA6-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LB1-v5.0-CWM5.zip
CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5.zip
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://forum.xda-developers.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://forum.xda-developers.com/showpost.php?p=25966147&postcount=1322 ) !
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
Love u man.....
My note is so dull without ur magic sprinkle....
Cant say how much I can thank you.
A little donation your way.
xxxxxxxxxx894473X
Will buy a note! Thz Chainfire
Sent from my GT-I9100 using xda premium
I'm also glad to see you on this device too. Thanks man!
sent from my Galaxy Note via T*patalk
zomg yay! can't wait
nice to see you here.. short question regardin binary counter, usb jig didnt work, is there a way to flash your kernel whitout affect the binary counter?
Chainfire said:
Should be ready later tonight or early tomorrow. I need the thread URL
(could have posted it days ago, but I'm still fixing minor issues with CWM5)
Usual CF-Root features apply. Root, busybox, CWM, custom bootanimations, custom boot scripts, CWM Manager(tm), etc.
Click to expand...
Click to collapse
fantastic chain
m_adnan said:
nice to see you here.. short question regardin binary counter, usb jig didnt work, is there a way to flash your kernel whitout affect the binary counter?
Click to expand...
Click to collapse
Yes, stay tuned for more info!
Great news! !!!
Sent from my GT-N7000 using XDA App
amazing man!! thanks!!
small donation to you: 81Y69202241504401
Chainfire said:
Yes, stay tuned for more info!
Click to expand...
Click to collapse
I always know when I've bought the right device when I see you pop up the same forum
Sent from my GT-N7000 using Tapatalk
Great news, .
magic Chain !!!
Can't wait for this. Any idea what file system the Note uses?
Sent from my GT-I9000 using xda premium
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678768&postcount=2513
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
STOP PRESS:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Flash the kernel part first and then directly the proprietary binaries part! Flash the appropriate proprietary part on both 1st and 2nd ROM!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2-update
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8), CM 10.1.x and CM 10.2 (since 1.7) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV, CodyF86, poppolo2001
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch 5.08.5: http://forum.xda-developers.com/showthread.php?t=2202667
Todo:
More features in NEXT tool
Special Thanks:
@trssho91, @Caldair, @fast96, @Jellydroidkin, @Android-Andi, @nakbaliNe, @Bhaskara Rao, @tsatomas
Downloads Record:
blackhawk-next-kernel-1.0-p31xx.zip: 316
blackhawk-next-kernel-1.1-p31xx.zip: 87
blackhawk-next-kernel-1.1-addon-nooc-p31xx.zip: 41
blackhawk-next-kernel-1.2-p31xx.zip: 503
blackhawk-next-kernel-1.2-addon-nooc-p31xx.zip: 160
blackhawk-next-kernel-1.3-p31xx.zip: 240
blackhawk-next-kernel-1.3-addon-nooc-p31xx.zip: 112
blackhawk-next-kernel-1.4-p31xx.zip: 583
blackhawk-next-kernel-1.4-nooc-p31xx.zip: 294
blackhawk-next-kernel-1.6-p31xx.zip: 380
blackhawk-next-kernel-1.6-nooc-p31xx.zip: 227
blackhawk-next-kernel-1.6.1-p31xx.zip: 180
blackhawk-next-kernel-1.6.1-nooc-p31xx.zip: 90
blackhawk-next-kernel-1.6.2-p31xx.zip: 151
blackhawk-next-kernel-1.6.2-nooc-p31xx.zip: 81
blackhawk-next-kernel-1.5-p31xx.zip: 600
blackhawk-next-kernel-1.5-nooc-p31xx.zip: 304
blackhawk-next-kernel-1.8.1-p31xx.zip: 222
blackhawk-next-kernel-1.8.1-nooc-p31xx.zip: 99
blackhawk-next-kernel-1.8.2-p31xx.zip: 577
blackhawk-next-kernel-1.8.2-nooc-p31xx.zip 321
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.3
Created 2014-09-21
Last Updated 2014-10-11
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
02/01/2014 2.1.5 -> 2.1.6:
CM 11.0 support
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
20/10/2013 2.1.2 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
28/09/2013 2.1.1 -> 2.1.2:
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
22/09/2013 2.1 -> 2.1.1:
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
18/09/2013 2.0 -> 2.1:
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
02/09/2013 1.8.3 -> 2.0:
Vendor blobs in separated flashable zip, taken from Samsung 4.2.2. Flash proprietary-vendor-samsung.zip directry after flashing NEXT kernel 2.0 on both 1st and 2nd ROM!
Ten seconds boot menu timeout. Boot to the latest booted ROM when timeout periode reached. Finally, my trick works :victory:
Using Samsung P3110 Update1 kernel source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110 . Patched to comply CM/AOSP need and NEXT dual boot, without SELinux and audit support, gcc linaro compiler. Kernel source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
Samsung open source exFAT kernel modules included, source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Without CPU or GPU overclock
Without extended CPU governor or I/O scheduler
Without swap or zram support
AROMA 2.70 beta 6 binary
13/08/2013 1.8.2 -> 1.8.3:
Samsung 4.2.2: The first attemp to reduce battery draining issue, zram service disabled! You can enable zram (not as a service) by issuing "setprop persist.service.zram 25" over Terminal Emulator or "adb shell". Reboot is required.
CM 10.2: Bluetooth tethering fix from upstream CM 10.2
07/08/2013 1.8.1 -> 1.8.2:
The third attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip updated, please re-download it!
06/08/2013 1.8 -> 1.8.1:
The second attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directry after flashing NEXT kernel!
Single channel sound output bug fix
05/08/2013 1.7 -> 1.8:
Initial Samsung 4.2.2 support
Updated to upstream Linux kernel 3.0.41 (incremental patch)
https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk 1-2 Aug 2013
The first kernel utilizing the new ducati firmware, the first kernel preserved 815.8MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk-p31xx.zip if you switch to another kernel
01/08/2013 1.6.3 -> 1.7:
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.6.1 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcache memory corruption problem fixed!
21/07/2013 1.6 -> 1.6.1:
Hotplug CPU governor kernel panic bug fix. This governor not working properly with cleancache enabled, cleancache disabled for now
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 more than previous busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM persist.customboot.zram property changed to persist.service.zram, follow CM's standard
Stock ROM default zRAM size changed to 26% RAM size
Swappiness value changed to 90
18/07/2013 1.5 -> 1.6:
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRam support optimized for Android, utilizing the new lzo library. Set 18% of RAM as zRam swap file. CM user can use CM's Settings - Performance options.
cleancache support with working Zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-18/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
11/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. For dual boot user, you must update both 1st and 2nd ROM to renew both ROM vendor binaries!
Change screen_off_max_freq from 1.008GHz to 800MHz, small changes in init scripts
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
small update to disable swap support by default for my "stock based ROM" included
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
Auto rotate (for both stock and CM) depend on ro.sf.hwrotation value, camera orientation fix included
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
01/06/2013 1.2 -> 1.3:
Updated compiler to the latest linaro gcc 4.7
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P51xx port
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz
1.1 -> 1.2:
Potential bug in sdcard swapper script fixed. Yes, for stock ROM as 1st ROM this kernel still has a script to swap external sdcard - internal media.
SuperSU updated to the latest version (stock ROM).
1.0 -> 1.1:
exFAT filesystem support, stock ROM only for now. I will share separate flashable zip for CM 10.1, when it's ready (broken USB storage support). Please note Dual Boot FAQs #24!
CGROUPS, SLUB, and TRACING support back enabled for exFAT compatibility, Android logger disabled by default to compesated it. You can enable logger by editing /system/etc/init.d/02modules .
No boot menu in single ROM environment.
Change stock ROM init.d script starting point. Earlier than before, same as CM 10.1 now.
Non overclock addon for anyone who is experiencing overheats when using standard NEXT kernel.
Source change: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk, May 24-26, 2013. A lot of undocumented change in ramdisk side.
exFAT support in CM 10.1
Download and flash blackhawk-next-cm-exfat-vold.zip over recovery
fsck.exfat, mkfs.exfat, vold binaries and all needed libraries taken from Samsung JB 4.2.2 included
USB storage support is broken, you need USB OTG Helper from http://forum.xda-developers.com/showthread.php?t=1588940 as 3rd party USB storage mounter
exfat binaries for exfat support in USB OTG Helper included. So, all USB OTG Helper features (FAT, Ext2/3/4, full NTFS, and exFAT support) enabled
To avoid Dual Boot FAQs #24 issue, flash blackhawk-next-cm-exfat-vold.zip and NEXT kernel of course directly after CM update. For CM 10.1 only!
Download Record:
proprietary-vendor-samsung.zip: 4481
proprietary-vendor-samsung-4.1.x.zip: 1478
Dual Boot FAQs
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
Exercise I
An example current facts:
ROM: Samsung stock JB 4.1.2
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Download CM latest nightly + GApps zip
~2GB free on internal storage
Dual boot step:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Flash CM
Flash GApps zip
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
It's always better if you make a backup before performing all above steps. Do it at your own risk!
Exercise II
An example current facts:
ROM: CM 10.1 latest nightly
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Have Samsung stock 4.1.2 nandroid backup
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Nandroid backup your current CM 10.1 ROM
~2GB free on internal storage. I am not sure, depend on your backup data size
CM 10.1 as 2nd ROM:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Restore CM 10.1 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
Samsung 4.1.2 as 1st ROM:
Reboot into primary recovery, make sure you choose "Primary Recovery"! Make sure you really choose "Primary Recovery"!!
Restore Samsung stock 4.1.2 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into primary ROM - Samsung!
Do all above steps at your own risk!
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
08/08/2013: Kernel for stock 4.2.2 Developtment Secret
If you want to build your own kernel for stock 4.2.2, this is the development secrets how to fix CPU frequency jumping to maximum available frequency, how to fix slow graphics issue, how utilize the new ducati firmware and increase the RAM space, how to fix hardware accelerated media problem and how to fix WiFi tethering issue.
Kernel source: http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Samsung kernel update: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110
Samsung exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
How to fix CPU frequency jump to maximum available frequency (1.52GHz, overclock version) on boot
Rename /system/lib/hw/power.default.so to /system/lib/hw/power.default.so.bak, copy power.piranha.so from NEXT kernel 1.8.2 package to /system/lib/hw
How to fix slow graphics issue
This solution authored by @codeworkx 8 moths ago but disabled by default: https://github.com/kumajaya/android...mmit/0c6d1a53f1a51b588786b168a48e2566f8a49065 Enabling both FB_OMAP2_VSYNC_SEND_UEVENTS and FB_OMAP2_VSYNC_SYSFS solve this problem
How utilize the new ducati firmware and increase the RAM space
How to fix hardware accelerated media problem
How to fix WiFi tethering issue
If you use above information, proper credit must be given including a clear text about this solution.
21/09/2013: OMAP PowerVR 3D GPU Control
There some interface inside /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq:
frequency interface to access the current GPU frequency (153600000/307200000/384000000)
frequency_list interface to access supported GPU frequencies (153600000 307200000 384000000)
frequency_limit interface to access the GPU maximum frequency limit (default: 307200000). Writeable mean this code inside the pvrsrvkm kernel module, the GPU maximum frequency controllable
governor interface to access the current GPU governor (userspace/on3demand/activeidle/onoff)
governor_list interface to access supported GPU governor (userspace on3demand activeidle onoff)
The upcoming version of Android Tuner (0.10.2) support OMAP GPU controls.
21/09/2013: NEXT 2.0.1
As I mentioned before, I still continued cm-10.2 branch kernel development. This branch is the source code of NEXT 2.0, I've added overclock support but limited at 1.2GHz CPU and 384MHz GPU. OMAP GPU controls support applied as gpu_oc interface replacement. Kernel attached here as blackhawk-next-kernel-2.0.1-p31xx.zip .
Changelog:
Rewriting overclock code: https://github.com/kumajaya/android...mmit/35e0c0455cb7ae4beb50375c5873b328a76a1087
Add sysfs interface to store GPU frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
Limit GPU frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
Xpad force feedback support disabled
WARNING: This kernel only for device that can handle 1.2GHz CPU and 384MHz GPU frequency.
ketut.kumajaya said:
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
Click to expand...
Click to collapse
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
There is no confusion at all...
Every file you need is in the first post: kernel, tool and Philz. Don't use anything else.
Read the examples. All information is in there...
I don't know about the differences between KK and Philz, but I don't care though... Philz is just great!
Many, many respects to ketut...
Big thanks for your efforts...
Sent from my GT-P3110 using xda app-developers app
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
PhilZ Touch is a recovery image, NEXT kernel is a boot image, KK-Boot discontinued project.
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
god_creature said:
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Yes. Fixed the problem when installed CM 10.1 directly as 2nd ROM. No wipe needed.
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
dimfil said:
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
ketut.kumajaya said:
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
Great!
It's a lot of pages. I can't find it right away, but your answer is enough for me! So, they are compatible.
I will try and report if necessary.
Sent from my GT-P3110 using xda app-developers app
This great work Ketut, thanks for giving us easy way to dual boot. Keep up the good job.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
ketut.kumajaya said:
This is [BOOT IMAGE][GT-P31XX] KK-Boot - Custom boot image for stock 4.1.1/4.1.2 ROM and [KERNEL][GT-P31XX][JB][4.2.2]CyanogenMod 10.1 unofficial kernel 3.0.31 combination, plus cm-10.1-blackhawk commit on github:
Remove Samsung debugging code in ext4 filesystem, inline with omapzoom
Initializing Android USB depending on the rom type, big thanks to gokhanmoral. This is the key of single kernel. Multiboot support not so far, you can reuse my kernel for multiboot (if you can)
Compiler optimizations
Kernel without CGROUPS support
Using SLQB memory allocator
Decrease MPU, IVA, and GPU voltage
Adapt and fix codeworkx's sysfs for controlling pivot mode. This is the key of landscape kernel
Stop the spam from audio driver
An exprimental config, remove a lot of debugging config from kernel: 775MB RAM
Stock JB 4.1.1/4.1.2 ROM: Using a slim version of busybox (from gokhanmoral's ramfs for siyahkernel-sgs3), bash and nano binary, sysrw and sysro script removed. GPU clock @ 384MHz + 2D GPU rendering, stock ROM really need an overclocked GPU.
CM/CM based ROM: As usual, change ro.sf.hwrotation value from 270 to 0 in /system/build.prop will transform your device to landscape mode, a workaround fix for boot animation graphic glitch. GPU clock @ 307MHz + 2D GPU rendering + 16bit transparency + disabled dithering + purging assets allowed
/system/etc/init.post_boot.sh is yours kernel tuning template. But remember, do not force your system too much until you are sure that your device is able to handle it.
Flash this using the latest CWM, CWM Touch, Philz Touch, or TWRP at your own risk!
Click to expand...
Click to collapse
Thank you
distan7 said:
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
Thank you
Click to expand...
Click to collapse
Same kernel, different ramdisk. Thanks for your support :good:
STOP PRESS: Update PhilZ Touch to 5.03.7 http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89!
Oh good news my brother I am happy
Envoyé depuis mon GT-N7100 avec Tapatalk
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Andrev01 said:
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Click to expand...
Click to collapse
1. Yes as covered by Dual Boot FAQs. No.
2. Yes.
3. Can not be, maybe the next version. Reboot to recovery and bootloader may be removed for security reasons.