Related
Paladin CUSTOM ROM 0.5
Since i got my tablet i started developing some stuff for it, in the past i have been workin on some ROMS for various phones, so i decided to make one for our nice tablet.
It should be compatible with Basic but im not 80% shure
Some Feutures:
Compatible with 4.0.1 & 4.0.3 and MagicCode!!!
SuperUser
BusyBox + symlinks (No Need To run "busybox cp ..." just "cp ...")
Original DalvikVM (Game Compatibility)
DalvikVM Memory Tweaks
SWAP Support (Auto 128mb swap on /data look on swap info bellow for more info)
Init.d Support
EXT4 mount improvements (IO Boost)
File scheduler set to CFQ
DNS Set to Google DNS
APN List (for 3G)
Network Tweaks
CFQ Tweaks
Mount system with noatime (speed boost)
AdBlocker
Android [GEARS] v.2 Bootanimation thanks to Grael
IMPORTANT:
* First install ClockworkMod Recovery
* Put the zip on sdcard
* Apply the Update in ClockworkMod Recovery
SWAP:
Our device is really limited on memory, we can fake adding more memory by adding a disk swap file
If you have a class 6+ sdcard you can use a secondary SWAP partition on it and the swap script will automaticaly detect it.
The default is using 128mb of swap on the /data partition so you will have a bitt less space for the apps
THIS IS JUST A UPDATE FOR THE SYSTEM. YOU NEED TO HAVE A FULLY WORKIN SYSTEM!!!
here are some recomended apps for those that want to use them:
Nova Launcher
XDA information thread here
DOWNLOAD
Instructions: Flash aply the update in CWM recovery
Hackers Keyboard MIPS
(install language packs from market)
hackers keyboard is a full qwerty keyboard for those tha like to have their keyboard as on their pc. its compiled for mips and really fast
DOWNLOAD
TitaniumBackup MIPS
Backup/restore program
DOWNLOAD
Android Terminal Emulator MIPS
Terminal for accessing adb localy from your phone
DOWNLOAD
MobileManager
stock ingenic mobile manager
DOWNLOAD
DOWNLOAD
Hi, I'd use your update but I'm stuck in bootloop please help
I'm downloading 0.8 now (from your post on another forum) . Can't wait to give it a whirl! Thanks for making our little tablets mighty!
Sent from my SAMSUNG-SGH-I997 using xda premium
I don´t understand, your post in other forum is 0.8 version but you post this version 0.5 after. There is a problem with 0.8 version? I need a firmware with bluetooth drivers for use with usb external.
Always was amazed by the mips platform when I first saw the paladin I was just amazed they got it running on mips
How did you got the init.d working? I never got able to understand the kernel tweaking to get it working (trying to get it working on my MTK6573 HDC A9100 phone)
Any help or tutorial for getting that to work would be very appreciated since I want to get a working app2sd (using now link2sd)
Copied From ChainFire's Post
Click to expand...
Click to collapse
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 (CWM4/5) recovery. For Galaxy Fit You Need To Flash Clockwork Mod Separately. The Kernel is Custom Supporting Ext4 FS, OC, UV and other Features
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 THIS ENTIRE POST!
Donate
Please Donate to Chainfire or Press Thanks button Here
Click to expand...
Click to collapse
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...
Features
- Root
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 4.0.0.2
- Integrated Tweaks Manager
- Running All Scripts in /system/etc/init.d
- Custom Bootanimation Workin on All Roms
CF-Root v4.1 and older
- Superuser 2.3.6.1
- In-Secure mode
Instructions - CWM
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Flash CWM Recovery.
- Download the File To Your Sd-Card
- Flash via CWM Recovery
- No Need to Data Wipe
- Initial/First Boot May Take Long Time,Very Long Maybe .
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. For Galaxy Fit CWM Recovery Wont Go Flashing Other Kernels
CF-Root/CWM4 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
CWM Manager
Because of incompatibility 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 CWM
- Backup firmware
- Restore backups (CF-Root v5.0: 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
--- without changing warning triangle status or increasing flash counter
- CF-Root v5.0: 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. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Downloads (Will Work On Every GB Rom Formatted to Ext4 Partition)
Initial Release-http://www.mediafire.com/?y8242yhozcgvok6 (Flash via CWM Recovery)
Credits
-Chainfire (Please Donate Him or Press Thanks)
-Special Thanks To Ketut.Kumajaya
-zcop
What is that supposed to mean?
Sent from my GT-S5670 using XDA
Great Job Mr. Creed
CF Root kernel is very popular, now come to FIT device ^^
Congratulatioonnn
Hehe im a noob and i dont get it ... This will work on custom and stock roms or only on custom with ext4 support?
Sent from my GT-S5670L using xda premium
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Mr.Oug said:
Can't you guys read its all described in the op
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I read it ... But creed put something that made me confuse ... He put will work on every gb ext4 partition ... And the original post says its for stock ... So u tell me works on both or just in ext4 partition gb?
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
I add this one nice job Thanks. it works nice
Sent from my GT-S5670 using xda premium
pratyush.creed said:
nt stock for us , because our stock kernel dosnt support ext4 ,which is required by the CWM,CWM app and tweaks manager !!! i will soon add a way to make stock roms cf-root and cwm supported !!
Click to expand...
Click to collapse
that would be nice, thanks Creed
Jus tell guys if the bootanim is working/
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Deshabilitado said:
I hope u do something to make stock kernel ext4 support and that way use this
Sent from my GT-S5670L using xda premium
Click to expand...
Click to collapse
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Thanks waiting for it...
pratyush.creed said:
if i mod the stock kernel to add ext4 support it will be called custom kernel, kernels cant be modified they cn be built only !!
Click to expand...
Click to collapse
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Delanoister said:
What kernel base for is it?
for CM?
I think it works on Rom using ext4 fstype.
If there ppl.using stock.
Just format em to ext4, and flash a kernel.
Kernel base CM can be used on GB ROM (not CM), too.
I jst share my opinion n my experiences
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
not fr CM.
i usd chainfire's Ext4 convert app bt it didnt workd, i will try with cwm flashable scripts...do u have one ??
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
pratyush.creed said:
Just Refreshed this Cf-root ..
*Removed that Boot Splash of Creed(i forgot to remove it before )
*New Kernel
*OC upto 870Mhz
*New Shedulers
I havnt tested it, cuz my phone has gone for repairing ...
someone pls test if this is stable or not..so that i can add this to the main thread!!
Flash via CWM ...working on all roms
Click to expand...
Click to collapse
870 Is it a good idea.... o_0
Hi all,
To stop confusion and mixed messages, I've decided to start a new thread.
This thread will be dedicated to :
A) GT-S5300 Kernel development based on official Samsung sources
B) Clockworkmod recovery for GT-S5300
22-nov-2012 : Sources...see 2nd post
ATTENTION : I assume no responsability for any problems you might encounter. I've only be able to test these on my GT-S5300 (Europe version).
If you use the kernel update zip's, just make sure your Kernel resides in /dev/block/mmcblk0p5. You can check this with the following command:
hexdump -e \"%_c\" -n 8 /dev/block/mmcblk0p5
Your output should be something like this: ANDROID!#
General info:
- vM00Kernelv0.2m.zip minimal kernel (Droidwall support + insecure adbd)
- XXLF5KernelStock.zip / stock kernel XXLF5 update zip
- vM00CWM.zip Non permanent Clockworkmod recovery zip
- vM00CWMv2.zip Non permanent improved Clockworkmod recovery zip
- vM00Kernelv0.22ba.zip update zip with (Droidwall support, governors and insecure adbd + re-enabled bootanimation/sound)
- vM00Kernelv0.29.zip (Droidwall support, governors, integrated CWM,insecure adbd + re-enabled bootanimation/sound)
- XXLF5StockODIN.tar / Odin flashable stock kernel
- vM00Kernelv0.31.zip (Droidwall support, governors, integrated CWM,insecure adbd, deadline scheduler + re-enabled bootanimation/sound)
- vM00CWMv3.zip Replaced by vM00CWMv3f (bugfix, see changelog)
- vM00CWMv3f.zip Non permanent re-improved v3 Clockworkmod recovery zip, see changelog below
- vM00Kernelv1.00.zip Official Kernel release, see changelog below
- vM00Kernelv1.10.zip see changelog below
Instructions :
1) Copy the chosen kernel zip file to your sdcard (and vM00CWM if your current kernel hasn't integrated CWM)
2) boot your phone into recovery by holding VOL_UP,POWER and HOME
3) choose apply update from sdcard and select vM00CWM.zip
4) once your in CWM, select install zip from sdcard
5) choose zip from sdcard and select the appropriate Kernel update zip
vM00
RESERVED FOR ANNOUNCEMENTS
22-nov-2012
Hi all, unfortunately I haven't had a lot of time lately to continue ....I'm in the process of uploading sources so that anyone can benefit from my work.
On a sidenote, last progress was quite promising as I was able to run CM7. I still have 2 weeks holiday left before the end of 2012, can't say when exactly but I'll try to resume previous work during that time.
https://github.com/vM00
vM00
Changelog 06-nov-2012 vM00Kernelv1.10 :
- Adb now works in recovery mode.
- All files in init.d get rwx permissions during bootup
- vM00CWMf integrated
Changelog 06-nov-2012 vM00CWMv3f :
- Bug fix : backup to external sd
Changelog 05-nov-2012 vM00Kernelv1.00 :
- init.d support
- CIFS support
- Optimized Aroma File Manager 1.8 included : Fonts are bigger to improve readability on 240x320 screens, no theming due to size
CREDIT and big thanks to XDA member amarullz
http://forum.xda-developers.com/showthread.php?t=1646108
- Switched to lzma compression
- vM00CWMv3 integrated
Changelog 05-nov-2012 vM00CWMv3 :
- Optimized Aroma File Manager 1.80 full version included CREDIT and big thanks to XDA member amarullz
http://forum.xda-developers.com/showthread.php?t=1646108
- Proper handling of external sd
- Minor fixes
Changelog 03-nov-2012 vM00Kernelv0.31 :
- Added deadline scheduler
- New vM00CWMv2 recovery integrated
- Proper kernel version string formatting
- /system and / mounted by default
- Regression : removed ondemand and conservative governors until properly working
Changelog 03-nov-2012 vM00CWMv2 :
Following features have been added/fixed:
- Fully working external sd functionality (usb mass storage inclusive)
- Permissions Fix menu
- Easier menu confirmation/navigation (only once UP or DOWN required)
- Changed coloring scheme
- Partitioning menu
- **** BONUS ***** Option to reset custom binary flash counter
hello buddy
are you also custom rom developer?
thanks for ur effort sir
keep it up
very nice kernel
Sent from my GT-S5300 using xda premium
---------- Post added at 01:24 PM ---------- Previous post was at 01:05 PM ----------
vM00 said:
Hi all,
To stop confusion and mixed messages, I've decided to start a new thread.
This thread will be dedicated to :
A) GT-S5300 Kernel development based on official Samsung sources
B) Clockworkmod recovery for GT-S5300
02-nov-2012 : NEW ZIP ADDED
ATTENTION : I assume no responsability for any problems you might encounter. I've only be able to test these on my GT-S5300 (Europe version).
If you use the kernel update zip's, just make sure your Kernel resides in /dev/block/mmcblk0p5. You can check this with the following command:
hexdump -e \"%_c\" -n 8 /dev/block/mmcblk0p5
Your output should be something like this :
ANDROID!#
- vM00Kernelv0.2m.zip minimal kernel (Droidwall support + insecure adbd)
- XXLF5KernelStock.zip / stock kernel XXLF5 update zip
- vM00CWM.zip Non permanent Clockworkmod recovery zip
- vM00Kernelv0.22ba.zip update zip with (Droidwall support, governors and insecure adbd + re-enabled bootanimation/sound)
vM00Kernelv0.29.zip (Droidwall support, governors, integrated CWM,insecure adbd + re-enabled bootanimation/sound)
Instructions :
1) Copy the zip files to your sdcard
2) boot your phone into recovery by holding VOL_UP,POWER and HOME
3) choose apply update from sdcard and select vM00CWM.zip
4) once your in CWM, select install zip from sdcard
5) choose zip from sdcard and select the appropriate Kernel update zip
I've fixed kernel 0.28 and replaced it with 0.29. This kernel should be fully working.
vM00
Click to expand...
Click to collapse
is this kernels support INIT.D?
Sent from my GT-S5300 using xda premium
babyyeobo14 said:
hello buddy
is this kernels support INIT.D?
Sent from my GT-S5300 using xda premium
Click to expand...
Click to collapse
Hi, good that you mention it...atm no, but this should be relatively easy to implement. I'ill try to integrate init.d support in the upcoming releases.
vM00
vM00: big thanks for your works and this thread , i'm using your kernel v29 no problem so far except for governor ondemand not working
Originally Posted by babyyeobo14
hello buddy
is this kernels support INIT.D?
Sent from my GT-S5300 using xda premium
Click to expand...
Click to collapse
Hi, good that you mention it...atm no, but this should be relatively easy to implement. I'ill try to integrate init.d support in the upcoming releases.
vM00
Click to expand...
Click to collapse
woooowww !!
thank you so much
Sent from my GT-S5300 using xda premium
this kernel already have support to cifs? because in the original stock rom i cant use the cifs manager...
To me cifs is the most important file system because its possible to mount my hd storage from the router like /mnt/smb instead of smb://192.168.1.1/Storage
I've yet to find bug in your v0.29, working reboot, backup and restore. I can't confirm the governors since I'm not using any cpu apps. All in all, thanks for awesome kernel. However won't you change the kernel name [email protected] to vM00Kernel or something nicer?
Edit: Shutdown just reboot in CWM
DarkEyes23 said:
I've yet to find bug in your v0.29, working reboot, backup and restore. I can't confirm the governors since I'm not using any cpu apps. All in all, thanks for awesome kernel. However won't you change the kernel name [email protected] to vM00Kernel or something nicer?
Edit: Shutdown just reboot in CWM
Click to expand...
Click to collapse
Thank you all for the positive comments.
Yes it's normal that if you press shutdown from CWM, the next powerup will be in CWM. just press reboot then. I followed the logic that if you shutdown from CWM it's good that you reboot in CWM in case you need to finish/resume previous recovery actions.
And yes, from now on kernel releases will have proper version string formatting...something like:
[email protected]
Thank you very much vM00. We can't wait for your next update.
Sent from my Pocket
Mak droid v2
vm00 kernel
fbs777 said:
this kernel already have support to cifs? because in the original stock rom i cant use the cifs manager...
To me cifs is the most important file system because its possible to mount my hd storage from the router like /mnt/smb instead of smb://192.168.1.1/Storage
Click to expand...
Click to collapse
Hi, not yet....next release should have basic CIFS support.
vM00.
vM00 said:
Hi, not yet....next release should have basic CIFS support.
vM00.
Click to expand...
Click to collapse
wow, great! i will be able to play all movies, musics, roms etc directly from the router's HD with any app! :good:
CIFS support is for ?????
Sent from my GT-S5300 using xda premium
babyyeobo14 said:
CIFS support is for ?????
Sent from my GT-S5300 using xda premium
Click to expand...
Click to collapse
if you want to see a file in the network you can use samba to share the file in the network. the problem is that most of apps for android can't access the smb:// protocol, so most of the video players can't play videos from the network, emulators can't open roms/ISOs/save-states in the network, etc.
with cifs you can mount a samba share inside a normal directory, like /mnt/smb, so any app can see the content of the network, because the content is inside a normal path like /mnt/smb/storage instead a protocol like smb://192.168.1.1/storage.
in my case i have a router (tp-link wr1043nd) w/ usb for HD with openwrt firmware, so i have a router w/ a mini linux distro w/ samba server and a usb HD storage conected, then the desktop (ubuntu 12.10), netbook (ubuntu 12.10) and tablet (android 4.1.2) can access the same files in the same directory with cifs (in my case /mnt/smb/Storage), and i hope the sg pocket very soon :laugh:
[/COLOR]E: can't mount/emmc/
when i select (choose zip from external)
same in backup and restore
why??
Sent from my GT-S5300 using xda premium
@babyyeobo14:
Can you tell me which partition format your external sd card has? Currently only fat partitions are supported.
Plz provide the output you have from the following command:
cat /proc/mounts
vM00
@babyyeobo14:
Can you tell me which partition format your external sd card has? Currently only fat partitions are supported.
Plz provide the output you have from the following command:
cat /proc/mounts
vM00
Click to expand...
Click to collapse
sorry i cant get u..
i dont know what is partition format... i dont have knowledge about that sorry for being noob...
Sent from my GT-S5300 using xda premium
---------- Post added at 01:02 PM ---------- Previous post was at 01:01 PM ----------
vM00 said:
@babyyeobo14:
Can you tell me which partition format your external sd card has? Currently only fat partitions are supported.
Plz provide the output you have from the following command:
cat /proc/mounts
vM00
Click to expand...
Click to collapse
sorry sir i cant get u
i dont know what is partition format ..
i dont have knowledge about that...
sorry for being noob sir :sad:
Sent from my GT-S5300 using xda premium
That's no problem...just type:
adb shell cat /proc/mounts
and copy/paste the output you have here.
vM00
babyyeobo14 said:
[/COLOR]E: can't mount/emmc/
when i select (choose zip from external)
same in backup and restore
why??
Sent from my GT-S5300 using xda premium
Click to expand...
Click to collapse
vM00 said:
@babyyeobo14:
Can you tell me which partition format your external sd card has? Currently only fat partitions are supported.
Plz provide the output you have from the following command:
cat /proc/mounts
vM00
Click to expand...
Click to collapse
Same problem Occurred,
external memory format: FAT32
---------- Post added at 09:21 PM ---------- Previous post was at 09:13 PM ----------
Links updated to direct this Thread!
I am working on a custom jb4.2.2 rom for the A13 SOC and wanted to add some features, ROOT By default - I added the su Binary and the SuperSU.apk however it does not work by default. If you boot into CWM Recovery then Reboot the device it offers to fix Root, when I select yes it proceeds and works fine... I would Rather make the ROM Rooted without having to do that any Ideas On what Im doing wrong ?
I am also interested in adding features to the ROM automatic Zipalign would be desirable as well as the ability to use a swap / zram. I am using a Stock JB 3.0.8+ Kernel and in at least one prior iteration I could use zram and activate swap... I would Like to make those features user selectable.
I currently have init.d working in the rom set in the init.rc using busybox run-parts. I do not have run-parts installed by default, is there a simple way to include the full busybox install as well ?
Assistance on any of these questions is appreciated.
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. 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!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) 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, P31xx only: 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
brolee93 for latest P51xx Samsung stock boot image
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 blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
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.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
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
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
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
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).
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
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
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
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
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
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.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new 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 default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
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.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/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. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
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
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)
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
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
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 P31xx, that's way this port version directly jump to 1.3
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. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
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
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?