[Kernel/Tool] Boot Manager for X10 {v2.0}[Dt:10/Jan][FOR UNLOCKED BOOTLOADERS ONLY] - XPERIA X10 Android Development

This is a Boot Manager for Xperia X10 based on ClockworkMod recovery source.​Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!​
{
"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"
}
[ info ]
The bootmanager will reside on the main kernel of the device and will provide u with access to multiple recoveries and kernel management!
ONLY FOR UNLOCKED BOOTLOADERS
[ credits / special thanks ]
the_laser - to openly release this unlock for X10 bootloader
Koush - for the brilliant work & coding on CWM recovery
Napstar - for doing most of the work on Touch capabilities for CWM recovery
zdzihu - for xRecovery-0.3GBready & xRecovery v1.0.0 sources! (this is based on modified xRecovery v1.0.0 sources)
jerpelea and FreeXperia Team - for CWM4/5 Recovery
Androxyde - awesome shell scripting which powers the recovery triggers (for keypress) and recovery switching
soheil_rf - for background image & signature/banner
pvyParts - for kernel bootscreen
Frosty666 for the LED triggers
thanks to smartgardens and My_Immortal for internal testing!
thank you guys for ur kind donation!
Notopic1
HunteronX
gordonx10i
[email protected]
MrKingLouie
hasei
zdzihu
Dormidont
maciupeq
Zocker Tko
Vinkel
LJE
mylovelyhorse
The Gingerbread Man
themis123
TangVLD
[ features ]
[v2.0 onwards] now has TouchBased navigation buttons!
[v2.0 onwards] updated my modified recovery to v04 (details here)
[v1.4 onwards] updated CWM5 to latest one from FXP
[v1.4 onwards] replaced CWM4 with my own modified version of CWM5 (details of changes can be found here)
[v1.3 onwards] FIXED THIS ISSUE for Execute Custom Script ability
[v1.3 onwards] Theme support! - I know that most of u like to theme every aspect of the device, so I thought why not have this for BootManager! [ MORE INFO HERE ]
[v1.2 onwards] LED notification for triggering input events - when u see the BLUE LED light up keep pressing MENU key & u will enter BootManager (should avoid additional spamming of keys )
[v1.2 onwards] Battery percentage shown in BootManager - this should helpful for users
[v1.2 onwards] Execute Custom Script ability - this will allow devs/modders/users to execute custom scripts right from BootManager [ MORE INFO HERE ]
[v1.0.1 onwards] Stock X10 GB Kernel - so as to maintain compatibility with splboot, i.e. older bootloader bypass kernels
[v1.0.1 onwards] adb is active in BootManager and sdcard is automounted at /sdcard
[v1.0.1 onwards] AutoRooting - will install the newest Superuser 3.0 binary and app. If ur device is already rooted u can just use this file to install newest SU 3.0
[v1.0.1 onwards] Busybox v1.19.1-cm71 - newest busybox integrated in kernel ramdisk
[v1.0.1 onwards] Multiple recoveries - xRecovery-0.3GBready + CWM4 + CWM5!!! enjoy whichever recovery suits ur needs
[v1.0.1 onwards] Kernel Management - ability to boot into which ever kernel u want! (using older bootloader bypass methods), provided that u use the kernel packages provided here [ MORE INFO HERE ]
[v1.0.1 onwards] Keypress based entry - based on the keypress u can select which recovery u want to boot into [ MORE INFO HERE ]
Our app xCharge (on the market) has been updated to support these features , so those of u who bought it get the latest 1.6 update
[ requirements ]
UNLOCKED BOOTLOADER
new 2.3.3 GB firmware
ROMs based on 2.3.3 SE firmware
Flashtool
[ WARNING ]
PLEASE TAKE BACKUP OF SDCARD BEFORE TESTING
[ LIMITATIONS ]
currently we CANNOT flash FTF OR kernel.sin using any recovery, only option is to use FLASHTOOL
[ how to install? ]
download the bootmanager FTF
flash using FLASHTOOL
power on device
[ how to use? ]
[NEW] when u see the BLUE LED light up keep pressing MENU key & u will enter BootManager
controls:
VOL UP/VOL DOWN key to move Up/Down in menu
HOME key to select item
[ sources ]
Xperia X10 Boot Manager @ GITHUB
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ downloads ]
KINDLY DO NOT MIRROR MY FILES
BootManager v2.0
[ MD5HASH: 294c3c8130c15ea3e08c13499c16d0da ]
x10 2.3.3 GB Stock WiFi modules
please test it out and report back!
OLDER RELEASES
[ DooMKernel Signature banners!!! ]
If you like to use my kernels and u want to show the world that u use it/love it , then you can add this banner to you signature!!!
Just copy the following code and paste it in you USER CP under "Edit Signature":
HTML:
[URL="http://forum.xda-developers.com/showthread.php?t=1278318"][IMG]http://icxperia.com/doomlord/doomkernel-sig.png[/IMG][/URL]
ENJOY!!

[ Kernel Management ]
so guys for the kernel management i have provided two options in BootManager
Boot Custom Kernel (last selected)
Custom Kernel Selection Menu
here is some info on what each option does
Boot Custom Kernel (last selected)
this will basically execute an internal script which will boot the bootloader bypassed kernels (using splboot & miniloader)
some files are required for this to work correctly else u will get error in the BootManager:
/system/kernel/boot.img
/system/kernel/miniloader
/system/kernel/splboot.ko
if there are currently none present no worries use the next menu to install compatible kernel
Custom Kernel Selection Menu
this will allow u to select a compatible custom kernel package
these custom kernel package will essentially be CWM compatible (edify syntax) update.zip packages [i will be providing a few test packages]
the custom kernel packages will have to be stored in the folder /sdcard/kernels/ for them to be visible in this menu
when a custom kernel package is selected it will be installed (like an update.zip installation) and if everything is in order the kernel will automatically be booted (splboot will be executed)
List of available kernel packages
Note to Kernel Devs
i request the kernel developers (who wish to provide older bootloader bypass based kernels) [boot.imgs] to provide these packages so that users, who are using this BootManager can use ur kernels
also you are most welcome to use the test kernel packages posted here as a template for ur kernel packages
remember the kernel packages must be in EDIFY syntax
u can include whtever u want in that kernel package (e.g. additional modules/binaries etc)

[ kernel packages ]
PLEASE SAVE THESE KERNEL PACKAGES TO /sdcard/kernels/ ELSE THEY WONT BE VISIBLE IN SELECTION MENU
Back to Stock Kernel Package (some info on how this works)
DooMKernel v04-FS
DooMKernel v04b
zKernel 19082011
2.3Th kernel 028d
FreeKernel-mod405N.7 SE 2.3.3
FreeKernel-mod405.2 SE 2.3.3
i will keep adding more kernel packages as and when some kernel devs post them...

Older Releases
[ Older Releases ]
downloads links
KINDLY DO NOT MIRROR MY FILES
BootManager v1.4
[ MD5HASH: 69806ecf062f30cf53a7ab0379fb39e5 ]
BootManager v1.3 ( mirror )
[ MD5HASH: 9ea673a2ec85e384ef5cb446671ac4fd ]
BootManager v1.2 ( mirror )
[ MD5HASH: ae490119f7e32b2b9e6f423644f9b1ee ]
BootManager v1.0.1 ( mirror )
[ MD5HASH: 5c8f2438a07dd9e9fcd44406f0cae29c ]
x10 2.3.3 GB Stock WiFi modules
ENJOY!!

How to run a specific version of recovery at boot :
Here are affected keys you can press at boot :
back : xRecovery 0.3GB Ready
voldown : CWM 4.0.1.5
volup : CWM 5.0.2.3
menu : Bootmenu
How to reboot into recovery from OS :
GScript is required.
Here are gscript scripts for each function :
Bootmenu :
Code:
cp /system/recovery/KernelDefaultMenu/recovery.desc /data/local/tmp/recovery
touch /cache/recovery/boot
reboot
xRecovery 0.3GBReady :
Code:
cp /system/recovery/KernelDefaultxRec/recovery.desc /data/local/tmp/recovery
touch /cache/recovery/boot
reboot
CWM 4.0.1.5 :
Code:
cp /system/recovery/KernelDefaultCWM4/recovery.desc /data/local/tmp/recovery
touch /cache/recovery/boot
reboot
CWM 5.0.2.3 :
Code:
cp /system/recovery/KernelDefaultCWM5/recovery.desc /data/local/tmp/recovery
touch /cache/recovery/boot
reboot
Here is a xRecovery package for all above scritps :
Download scripts
Once installed, you will be able to load them from inside gscript.

Awesome work guys!!
Sent from my X10i using xda premium

No words, good work like always, our population is the best . Cheers.

Are you integrating the bootmenu into your doomkernel, too?

FXP028 is CM based but not SE, not supported?

Tony_C said:
FXP028 is CM based but not SE, not supported?
Click to expand...
Click to collapse
It will be done need different ramdisk I think
And can be released with doomkernel...
Let doom have some rest its 2:00 AM IST
Sent from my X10i using xda premium

Very nice.
Could do with freekernel on here or (Sorry for saying this) a doomkernel with max 1113 mhz.
I look forward to testing, just waiting for your upload to finish

Hi, can I flash this on Sku's MIUI, and I can flash Custom kernals on this rather than Flashtool? Also What are the advantages if I get this. Really Excited of hearing what This does !

smoke_weed said:
Hi, can I flash this on Sku's MIUI, and I can flash Custom kernals on this rather than Flashtool? Also What are the advantages if I get this. Really Excited of hearing what This does !
Click to expand...
Click to collapse
Ok, it is for all SE X10 based roms with unlocked bootloader, you can flash kernels with this instead of flashtool, my initial testing i managed to flash 3 different kernels about 2 minutes, boot manager will just make the whole process of choosing kernels and different recoveries alot easier.
As usual Awsome work Doom.

Booting into all recoverys works.
Xperia reboot into recovery goes to boots into CMW v5 recovery(any chance for a reboot into boot menu option?)
On first reboot phone took a while to grant SU privalages to apps.
Using boot manager to install and reboot into Doomkernel v40b FS...SUCESS!!!
For some reason, after install my market changed from pendos blue transparent back to the latest green one..not sure why but no great shakes.

[ Execute Custom Script ]
So this option will allow the user to execute a custom script:
/system/recovery/customscript.sh
That shell script MUST have all execute permissions (777)
This will be useful as modders/devs/cooks/users can now execute special scripts right from BootManager
Scenarios where this can be useful:
execute code to boot OS off SDCARD
execute code to boot custom kernel
use ur imagination

Xperia reboot now says...
Warning, recovery not found....
Maybe because i was last in cmw v5....
I would like any of your doomkernel x series....only with max 1113 mhz.
I know have asked before, and you must be tired after workign hard on this...I dont mind waiting for a bit
PS, I rebooted into 0.3 recovery and rebooted but xperia reboot options still says it cant find recovery

[ Theme Support! ]
I know that most of u like to theme every aspect of the device, so I thought why not have this for BootManager!
The user can now customize the following in BootManager (v1.3 onwards):
background image
menu color
text color
for this u will need to create the following folder structure on SDCARD: /sdcard/00_bm/res/images/ (those are double zeros in 00_bm)
for customizing do the following
background image
image should be PNG format and of size (480x854)
it should have the file name: bootmenu_bgk.png
save it in the folder /sdcard/00_bm/res/images/
so the complete path of this file should be /sdcard/00_bm/res/images/bootmenu_bgk.png
menu color
u will need to create a comma delimited file which will contain the integer values to control the RED, GREEN, BLUE, ALPHA
limit is from 0 to 255
example:
if u want the menu color to be RED the following should be content of the file:
Code:
255, 0, 0, 255
if u want the menu color to be GREEN the following should be content of the file:
Code:
0, 255, 0, 255
it should have the file name: menu-text-color (no extension)
save it in the folder /sdcard/00_bm/res/
so the complete path of this file should be /sdcard/00_bm/res/menu-text-color
text color
same as above EXCEPT it should have the file name: normal-text-color (no extension)
save it in the folder /sdcard/00_bm/res/
so the complete path of this file should be /sdcard/00_bm/res/normal-text-color
WARNING
for these customization to work the files SHOULD BE IN THE CORRECT PATH AND WITH CORRECT FILE NAMEs
each of these customization are independent of each other, meaning if u want u can change only one, or both or all of them
BootManager will check if each of those files are there, if it find them then it will use those, else BootManager will use the default values/image

since Z is missing in action i am posting his kernel here...
zKernel 19082011 kernel package posted!

Fantastic work, Testing it
Booting into all recoveries with boot manager & also with pressing keys work as it should
I was trying custom kernel selection menu, first I tried Doomkernel 4 fs but when it booted the phone got stuck at a black screen with a hardly seen free xperia logo, had to take the battery out & then it booted fine with Doomkernel 4 fs, then I tried back to stock kernel package but it doesn't work & when it tries to boot it gives "there was a problem booting custom kernel", I tried the doomkernel 4 fs again & it works fine but no luck with the back to stock one
Edit: it just gives that error but when I reboot the phone it boots up with stock kernel

DooMLoRD said:
select Xperia Arc as device....
Click to expand...
Click to collapse
Done that, it works now.
However, Vo.3 recovery now no longer flashes zips that it has done before I had the boot manager (pendos transparent market for one)
Also, super user got messed up and I had to give su rights to a load of apps.
Also, set CPU defaulted to min and max speed if 245, it took a while for my phone to do anything.
Finally, I have not had any deep sleep yet, I had my screen off for a couple of minutes (unplugged) and normally that would register deep sleep in CPU spy.
Anyway, I need sleep now, will continue testing in the morning.
Edit, deep sleep is working
Sent from my X10i using xda premium

Related

[KERNEL][MINI] DooMKernel [NO LONGER MAINTAINED]

hi i will soon be discontinuing support and closing down my (DooMKernel) threads for the following devices:
Xperia Ray
Xperia Mini
Xperia Mini Pro
Xperia Neo
RIGHT NOW I AM CLOSING DOWN THIS THREAD
since i only have the Xperia ARC with me, its becoming difficult for me to manage so many devices, especially since CM7 kernel will require different kernel sources (even MiUI), the task is going to get tougher for me... also I am getting busy with some personal work so wont be able to dedicate a lot of time for the devices which i dont even have...
i have asked the Xperia Play users to think abt donating a device to me...
if they want then they can do so, then i will continue work on PLAY too... but if they are not willing, then even that kernel will be closed down...
currently hartej has Xperia Ray and will be working on the kernel for that device (i will help him get started and working )...
another thing, my dear friend Napstar is an awesome dev, he is currently working on Ideos X6 kernel/recovery/other stuff, i keep helping him out when ever he needs help ... he is willing to help me out but we will need that device with us to continue work... so if for any of the above devices you guys are willing to donate a device to him/us, i am sure he/we will continue work on kernel and much much more
i invite advanced users who have knowledge abt compiling kernels to contact me... i can help them out to keep the kernels up for that device...
for technical queries u can always send p.m. to me
hope u guys understand this...
regards,
DooMLoRD
---------------------------
hello guys!
i am new to kernel development but i think this kernel would be useful for a lot of ppl using stock SE 4.0.A.2.368 FW...
I DONT HAVE THE DEVICE SO NEED SOMEONE TO TEST IT!
[ special thanks to ]
Blagus
zdzihu
aZuZu
jerpelea
Thank you guys for ur help! this would not have been possible without ur help!
[ screenshots ]
(screenshots are from Arc)
{
"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"
}
[ disclaimer ]
OVERCLOCKING CAN BE DANGEROUS! U RISK THE HARDWARE GETTING DAMAGED!
PROCEED WITH CAUTION! U HAVE BEEN WARNED!
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
[ features ]
[v01 onwards] added new logo!! Thanks to soheil_rf
[v01 onwards] added I/O Schedulers:
V(R)
BFQ
[v01 onwards] added CPU Governors:
Smartass
Scary
MinMax
Interactive
[v01 onwards] enabled NLS_UTF8
[v01 onwards] added user-level/runtime CPU voltage control [VDD control "sysfs interface"] (for more info keep checking this post: http://forum.xda-developers.com/showpost.php?p=16610299&postcount=362)
[v01 onwards] added Max frequency: 1.9Ghz (for sake of safe booting the device will always boot at min 245Mhz / max 1024Mhz)
[v01 onwards] added lots of intermediate frequencies (from 122Mhz to 1.9Ghz for almost every 100/120Mhz there is a select-able frequency)
[v01 onwards] added cpu freq thresholds to throttle CPU speeds to stock values when inside recovery
[v01 onwards] added recovery CWM v4.0.1.4 FreeXperia Team (to access recovery follow the instructions here)
[v01 onwards] {ramdisk tweak} /sd-ext also symlinked to /mnt/sd-ext
[v01 onwards] enabled SWAP support
[v01 onwards] enabled CDROM filesystem support in kernel (now u can mount ISO files)
[v01 onwards] enabled a few I/O Schedulers
noop
Anticipatory
Deadline (default)
CFQ
[v01 onwards] enabled ARM THUMBEE extensions
[v01 onwards] init.d scripts/binaries execution support
[v01 onwards] enabled support (in kernel) for many file systems
EXT2
EXT3
EXT4
NTFS (Read & Write)
[v01 onwards] enabled NFS (client & server) support in kernel
[v01 onwards] enabled CIFS support in kernel
[v01 onwards] enabled access to kernel .config (can be pulled from /proc/config.gz)
[v01 onwards] enabled TUN/TAP driver support (integrated in kernel) [VPN support]
[v01 onwards] USB-OTG support (already enabled in SE FW)
[v01 onwards] autorooting (prerooted)
kernel is insecure (ro.secure=0)
su binary & superuser.apk will automatically be installed by kernel (thanks to Bin4ry for posting the file RootXperia.zip; i have used the superuser files from his zip)
busybox already installed in /sbin/
busybox will get copied to /system/xbin/ if its not present there
adb server is persistent
usb debugging enabled
rootfs and /system mounted as rw (thank you Blagus for the tip )
enabled IPTABLES/NETFILTER support
[ credits for features ]
BFQ I/O Scheduler ported from richardtrip's Kernel sources for Bravo by richardtrip
V(R) I/O Scheduler ported from LeeDroid Kernel sources for Ace by LeeDroid
Smartass CPU Governor ported from UmaroKernel sources by umaro (original posted by erasmux) [Fixed/modified for SEMC Devices]
Scary CPU Governor ported from UmaroKernel sources by umaro (original posted by scaryghoul)
MinMax CPU Governor ported from UmaroKernel sources by umaro
NEW LOGO Thanks to soheil_rf
Interactive CPU Governor ported from UmaroKernel sources by umaro & from Bukington gaosp Kernel sources
VDD control "sysfs" interface ported from UmaroKernel sources by umaro (original posted by snq- here)
CWM Recovery FreeXperia Team
{OLD} initial freq-Overclock table if2
{OLD} bootscreen/bootlogo/bootimage used from http://forum.xda-developers.com/showthread.php?t=928352 with permissions of Sentinel196
original RootXperia.zip file Bin4ry
autorooting inspired from CF-Root for SGS2 (Chainfire)
and finally ME for getting this all together for u guys
thank you all for ur work!
[ requirements ]
stock SE 4.0.A.2.368 FW (available from here: http://forum.xda-developers.com/showthread.php?t=1227149 )
bootloader unlocked
working fastboot
u have read this: [How-To] Safely test custom kernels / custom ROMs and get back to stock SE 2.3 ROM
android app for overclocking like SetCPU (paid) or NoFrills CPU Control (free)
NoFrills CPU Control (free) to select I/O scheduler
VDD control app: IncrediControl
[OPTIONAL] CIFS Manager (free)
[OPTIONAL] Swapper 2 (free)
[ additional info ]
ok time for some gyan!
see each cpu/chip is different
each is unique and has different tolerances
slowly keep increasing the frequency
check its stability for 5-10 hrs
check for random reboots
check which one is best suitable for ur device
if u start getting reboots/freezes then throttle back and use lower frequencies
remember just because someone elses device was able to work at that frequency/voltage doesnt mean that ur phone can support/handle that frequency/voltage
i would recommend that u DO NOT use high frequencies for long time! this may damage ur device!
[*]the high frequencies are just for temporary boost/benchmarks/showoff
[*]you have been warned!
[ how to install ]
download the boot.img
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot flash boot boot.img
reboot phone and enjoy the kernel
FOR OVERCLOCKING
start SetCPU/NoFrills CPU Control app on ur Mini (or any other app which supports overclocking) (u may get a popup asking for SuperUser permissions, click ok/yes/allow)
now slowly increase the MAX slider to the right (one notch at a time) to increase the maximum frequency limit
DO NOT JUMP TO THE LAST POSSIBLE FREQUENCY
SLOWLY increase the frequency one notch at a time and do stability/testing for few hours
[ my kernel sources ]
https://github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
FreeXperia PROJECT: if you want to support FreeXperia PROJECT (creators of working recovery) you can donate
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YJ7AK6HLAVNHU
[ downloads ]
[MINI] DooMKernel (v01) (FW: 4.0.A.2.368) ( mirror )
[MD5HASH: 4476015d23f788b2529b671e9ec23b75]
[ for modders/themers/others ]
hey guys here i am attaching a template update.zip which has been tested to work on the recovery provided here... u can add ur stuff to that file and edit the updater-script so that the u can flash ur files via this recovery...
basically it contains the correct combination of update-binary & mounting syntax...
this file is NOT required for normal/general users
TEMPLATE UPDATE.ZIP (v1)
cheers!
is this same thing with previous one? i see it has same version, or maybe i missed somethin?
code28h4p said:
is this same thing with previous one? i see it has same version, or maybe i missed somethin?
Click to expand...
Click to collapse
This is for Xperia Mini! not mini pro
Sent from my LT15i using XDA App
Going to test it on Monday i think..Not sure about taking that phone, but I really like that.
is there any app or method to root sk17i without unlocking bootloader?
shravanchoudhary9 said:
is there any app or method to root sk17i without unlocking bootloader?
Click to expand...
Click to collapse
nope... no known exploits work
Is it okay that my boot.img file size is about 6MB ?
Or it should be 4 ?
Oops I was thinking that im writing in Mini Pro kernel...
Will it be included in future CM7 port ? Since it seems you're part of freeXperia team...
Sakem said:
Will it be included in future CM7 port ? Since it seems you're part of freeXperia team...
Click to expand...
Click to collapse
yes... most features will be...
may i have ur attention!
Custom kernel boot screen submissions for DooMKernel
Nvm it all, I finally installed it, gonna tinker with recovery >_<
anyone try doomkernel?
is it safe to install on .377 fw?
thanks
may i have ur attention!
Custom kernel boot screen submissions for DooMKernel
VOTING BEGINS!!!
thanks to all who contributed!!!
i have selected some final entries which i personally liked...
now the time comes to decide the final one...
a poll has been created in this thread... multiple selections are allowed...
so guys select the best one which u want as bootlogo on the next DooMKernel!!!
hi doom, to send my phone to service center, I just have to relock the bootloader and flash the rom generic, or do I also flash the stock kernel? where can I find?
thanks
ginepraio said:
hi doom, to send my phone to service center, I just have to relock the bootloader and flash the rom generic, or do I also flash the stock kernel? where can I find?
thanks
Click to expand...
Click to collapse
Relock bootloader and flash stock FTF...
Sent from my GT-I9100 using XDA App
DooMLoRD said:
Relock bootloader and flash stock FTF...
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thank you very much!
After installing the device DooMKernel problems with the buttons. Buttons "volume" does not work, the button "Home" became "volume" button, "Back" button is not lit. Can this be fixed? Thank you.
stehn said:
After installing the device DooMKernel problems with the buttons. Buttons "volume" does not work, the button "Home" became "volume" button, "Back" button is not lit. Can this be fixed? Thank you.
Click to expand...
Click to collapse
The kernel in this thread is for xperia MINI... I am guessing that ur device is MINI PRO!!!
Sent from my GT-I9100 using XDA App
DooMLoRD, Yesterday I installed your kernel and works great until today when it reboot 2 times.
first time it happened when I watched the wallpaper in zedge.
second time happened when I started to call and while he gave the signal of the call phone yust reboots.
wifi tether app from market cant work, shos error.
wucinac said:
DooMLoRD, Yesterday I installed your kernel and works great until today when it reboot 2 times.
first time it happened when I watched the wallpaper in zedge.
second time happened when I started to call and while he gave the signal of the call phone yust reboots.
wifi tether app from market cant work, shos error.
Click to expand...
Click to collapse
Hi since my kernels are highly configurable it would be easier to bug hunt if
Sent from my GT-I9100 using XDA App

[FAQ] >> RBAP for miniCM10 by nAa, nAa's kernel X10mini/X8/x10miniPRO .:08/07/2013:.

[FAQ] >> RBAP for miniCM10 by nAa, nAa's kernel X10mini/X8/x10miniPRO .:08/07/2013:.
Read Before Asking Please
FAQ for MiniCM10, and nAa kernel
reading may answer to lots of your questions !
for X10mini, X8 & x10miniPRO
{
"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"
}
i decided to create a new thread dedicated to Q&A about miniCM10
this thread is the place of your questions, answers, tips about miniCM10 and nAa ics kernel
so please, as usual, read FAQ, use search option or anything else before asking commonly answered questions
the FAQ will be incremented when needed
the Q&A is written as Q are asked
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the JBnAa kernel
Instructions:
paste miniCM10-4.X.X on the root of your SDcard
backup
flash JB kernel
get in recevery and format /system ; /data ; /cache
flash rom
flash gapps
wait for the very long first boot
enjoy
Please make sure you followed the above steps before reporting any issues, especially 'wipe data/factory reset'
something else that is useful to read before asking :
Here we (nearly all? XDA members, regardless of being devs or only users [like me], me at least ) don't care about your good/bad English the important is trying to be understood and to understand the content of the threads
only ask things you can't find, or you don't understand, please if you don't understand something in any process tell us exactly where is your problem : it will optimize the answer
sometime rephrasing things can make you understand better, feel free to help us for making the most understandable sentence for anybody
i'm always trying to use a proper English (not so easy for a non native English ^^)
but if there's something misunderstood because of my English your are welcome to correct me
BUT if you don't make the effort to read, I won't make the effort to answer (ok, you can't read everything... but read the minimum )
that's it
miniCM website is now available (http://minicm.dyndns.org/site/Chat/ for chatroom)
clic on the red text above ​
register, and then enjoy
________________________________
bug tracking template :
twins.7 said:
#BUG Report
DO
Reboot - Recovery
BUG
the screen stuck in rebooting dialog. It should just rebooting
ACTION
press home key (or any key maybe) to make it reboot
Click to expand...
Click to collapse
________________________________
we seek for you, TESTERS, go there for helping : [DEV] miniCM10 debug only thread (shakira, robyn and mimmi)​
2nd part of FAQ
FAQ :
for miniCM7 refer to THIS THREAD PLEASE
for miniCM9 refer to THIS THREAD PLEASE​
for quick search, use ctrl+f and enter keyword, you should find an answer to your question
ok, let's start with some fun :
how to understand FAQ :
0/ question(which build(s) is(are) concerned with q/
answer to the question
old, wrong or obsolete answer
additionnal comments if needed​
__________________________________________________
nobodyAtall said:
about nAa JB kernel :
Preface:
Read through [that] post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Click to expand...
Click to collapse
1/ any problem with display overridding?( ? ; ? )
in settings > development settings :
_____________________
2/ wanna go back to a non jelly bean based rom?( all builds ; all devices )
go to CWM > mount&storage and format :
/system
/data
/cache
then flash the kernel you want, (press flash on flashtool, plug the phone to pc, force reboot by pressing home+power, press and hold back button)
==> you can now restore a backup of the old rom you were previously using or install another non JB based rom
_____________________
3/ hard/software keyboard isn't working properly??( ? ; mimmi )
x10man said:
Quick fix for the soft keyboard:
On the select input method screen turn the hardware keyboard to off like so:
The software keyboard will now appear but the hardware keyboard still works.
Basically this needs to auto-switch when the hw keyboard opens and closes.
X10man
Sent from my U20i using xda premium
Click to expand...
Click to collapse
DanielFran said:
Power off, then remove sim card. Reboot and select language, change keyboard layout in advanced definitions (mimmiparts). Then put again sim.
Sent from my U20i using Tapatalk 2
Click to expand...
Click to collapse
4/ why my wifi can't load? ( all builds ; all devices )
you may have that kind of logcat:
Code:
D/WifiService( 1694): setWifiEnabled: true pid=2095, uid=1000
E/WifiStateMachine( 1694): Failed to load driver!
E/WifiStateMachine( 1694): DriverFailedState
open terminal emulator :
Code:
lsmod
if it doesn't answer anything, maybe /system is out of space and kernel fails to copy wifi modules at boot (note that undervolt module wont work either)
try the following :
open any file explorer that is root capable,
go to /system/media/audio/ringtones
delete some ringtones (at least to recover about 3 or 4 MB free, the more is safer) [1.5 MB seems to be enough though ]
reboot
try lsmod and see, if the kernel succeeded to copy modules at boot it's ok and and lsmod outputs what you are waiting for, if not reflash kernel and/or try to install a reduced miniCM10 zip (by deleting ringtones as for the previous way, but in a zip editor)
hoping it will solve your problem
5/ you have various problems with wifi ? ( all builds ; all devices )
refer to miniCM7 and miniCM9 miniFAQs !!!
6/ what are I/O schedulers ? ( all builds ; all devices )
a kind of answer here
7/ i updated from miniCM10-4.0.0 to 4.0.1 and after updating the gapps to 20120923 i've lost the camera ? (miniCM10-4.0.1 ; all devices)
go to mount&storage
format /system (NO data lost )
install miniCM4.0.1 again
install gapps 20120923
reboot&wait
all should be back to normal : fast and feature full
8/ how can i set keyboard shortcuts on my hardware keyboard? (all builds ; mimmi)
just edit azerty.xml or qwerty.xml in system\usr\keyboard-config\layouts
9/ how can i fix my azerty/qwerty/qwertz... HardWare keyboard? (miniCM10-4.0.2+ ; mimmi)
first flash this : from here
and then the zip corresponding to your specific language : look here
/!\ choose "default input method" so that the KB works correctly, if you don't it will behaves strangely
/!\ do not modify keyboard_layouts and keyprints in any way if you want the above to work, edit: seems you can edit the xml finally
/!\ do not modify advanced>mimmiperts, make sure you have not touched it before processing the installs. it is recommended to start from a "fresh build" i.e. to wipe all user data, and so on.
defauld input and sym button should be back
/!\here is another way to fix it : follow allesand's instructions
10/ i wanna use a2sd, what is it and how to make it work? (all builds ; all devices)
refer to that short tuto & infos here by drfr
11/ my LED is not blinking properly is there any way to change that? (all builds ; all devices)
You must delete /system/lib/hw/lights.msm7x27.so with rootexplorer or any other file manager that allows you to explore and modify root files
handcent led settings does not work properly with lights.robyn.so
of course, you need to reboot your phone after that.
REDELETE AFTER EACH UPDATE if you have the same problem SINCE THE FILE IS REWRITTEN
12/ why flastool doesn't flash the kernel i choose? (any version)
when there are lots of kernel builds in flashtool firmware folder, flashed kernel might not be the right one,
to void this, create a folder in it, cut/paste all your previous kernel there
and only keep the one you want to flash in the firmware folder
then, start flastool and process flashing operations
13/ i'have some problem for sending mms (all builds until miniCM10-4.0.2+ ; all devices)
--> with CM7/9/10 you just CANT send mms without data enabled
if you can't even with data enabled:
DaRk_dOg said:
I think that this is a common issue with CM7 and not just MiniCM7 (I experienced it on my DHD too).
Here is a small workaround for now:
Before sending the mms, disable data traffic, then enable it again and then send your mms.
You have to do it every time, before an mms but it is working for me.
Regards, D_d
Click to expand...
Click to collapse
--> seems now, mms can be sent without enabling data or anything, just need to have correct APN set up
14/ CM file manager doesn't work well for no (not at all in fact) (all builds? ; all devices?)
see details here.
15/concerning brightness on MiniCM10-4.0.2 nightly 20130119 and higher, (MiniCM10-4.0.2-nightlies ; shakira, robyn, mimmi?
to get compatibility with .32 kernel, nAa needed to change some things related to brightness monitoring
and that's why some issues appeared with .29 kernel, and then were fixed, but with the drawback of light being at max for a short time before dimming when turning the screen on.
using .32 kernel solves this issue
with old .29 kernel, use MiniCM10-4.0.2-stable or nightlies until 20130114
for newer nightlies (especially 20130207+) prefer .32 kernel
16/ concerning Undervolting and newer .32 kernels : (MiniCM10-4.0.2+ and nAa .32-03+ ; all devices)
NobodyAtall said:
VDD levels
From 03 onwards, I've ported the vddlevels functionality from msm7x30
so that we can variably change the voltage level of the frequency we
want without the need for external modules.
The current voltage information is available at:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
E.g. the defaults after flashing the kernel should be:
Code:
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
122880: 3
245760: 4
320000: 5
480000: 6
604800: 7
614400: 7
633600: 7
652800: 7
672000: 7
691200: 7
710400: 7
729600: 7
748800: 7
768000: 7
787200: 7
806400: 7
825600: 7
844800: 7
864000: 7
To change for example the voltage level of the 122880 frequency, you could do:
Code:
echo '122880 0' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
If you cat this file again, you should see that the voltage level is
picked up. The new voltage level is picked up when the CPU will scale
to the particular frequency level.
The undervolting tickbox in the 'Performance Settings' of the latest
MiniCM10 nightlies already uses the new interface. The values that are
set there are the same ones as those passed by the old undervolting
module:
Code:
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
122880: 0
245760: 2
320000: 3
480000: 5
604800: 6
614400: 7
633600: 7
652800: 7
672000: 7
691200: 7
710400: 7
729600: 7
748800: 7
768000: 7
787200: 7
806400: 7
825600: 7
844800: 7
864000: 7
Do I need undervolting?
You dont NEED undervolting. It can save though hours of some battery
life during the day.
Overvolting?
Even though the interface allows you to overvolt, I don't suggest
doing so. It will result to instabilities or crashes and is totally
unsupported.
Performance?
Undervolting decreases the performance results - this is to be expected.
Click to expand...
Click to collapse
17/ why can't i connect my device to USB on PC ? (MiniCM10-4.1.0+ & nAa05+ ; all devices)
SmG67 said:
That's because MTP (Media Transfer Protocol) is default now, so it gets connected as a media device. If you want Mass Storage, go into Settings-Storage on your ROM and press the menu-button, you can select USB-storage from there.
Click to expand...
Click to collapse
18/ where is my dualtouch?? (MiniCM10-4.1.0+ &nAa05+ ; all devices)
this is a copy of kernel OP, that you should have read before
nobodyAtall said:
Dualtouch (for synaptics):
By default dual touch is disabled for improved touch accuracy and avoidance of the 'ghost touch' side-effect.
If you want to enable the fake DT by andrej456, you have to insert the following line in the /system/etc/hw_config.sh file:
Code:
echo "1" > /sys/module/synaptics_i2c_rmi4/parameters/cfg_dt
If you want to enable the fake DT by dx, you have to insert the following line in the /system/etc/hw_config.sh file:
Code:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Dualtouch (for cypress):
Cypress supports dualtouch, so this is enabled by default
Click to expand...
Click to collapse
19/ why do i get a kernel version error (installation abort, status 7) while installing MiniCM10? (MiniCM10-4.1.0 up to 20130518-NIGHTLY &nAa06 ; all devices)
matmutant said:
change in rom zip to *.61 for kernel version if you want the installation to complete (in META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
3rd part
3rd part
usefull links and performance tricks
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
what CPU governors, and how do they work?
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other​
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST​
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish​
for both :
to see if your swap works, open terminal, and type the following :
Code:
free
to see the swapiness :
drfr said:
To check in terminal:
Code:
cat /proc/sys/vm/swappiness
Default value is 30 if you have zram and swap enabled, or 60 if only swap without zram.
To change it TILL NEXT REBOOT:
Code:
echo X > /proc/sys/vm/swappiness
where X is your desired value
To change it PERMANENTLY:
add the above line to the end of your hw_config.sh (you can find it in /sýstem/etc)
Note: it is always way easier to type those things on PC keyboard, so you´d better do it in adb shell.
Click to expand...
Click to collapse
__________________
some usefull lines of commands for any user wanting to know what's going on :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to siplay the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know how much swap there is (total and free are what you want to know), use the following command since the way using menu is broken :
Code:
free
to know if KSM is really turned on :
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb pm install /home/user/app1.apk
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
Benchmarks, screenshots and thklist
to start with, some screenshots
MiniCM10 theme:
MiniCM10 Crystal2:
benchmarks :
MiniCM10-4.0.2-nightly, using .32 kernel :
all has been done at 729MHz, on robyn
on .32-02:
antutu : fps2D:​
I/O performance on miniCM10-4.0.2-20130120/nAaJB03 (2.6.29.6) :
conclude what you want
NOOP:- The NOOP scheduler inserts all incoming I/O requests into a simple, unordered FIFO queue and implements request merging.
The scheduler assumes I/O performance optimization will be handled at some other layer of the I/O hierarchy; e.g., at the block device; by an intelligent HBA such as a Serial Attached SCSI (SAS) RAID controller or by an externally attached controller such as a storage subsystem accessed through a switched Storage Area Network.​
ANTICIPATORY:- Anticipatory scheduling is an algorithm for scheduling hard disk input/output.
It seeks to increase the efficiency of disk utilization by "anticipating" synchronous read operations.​
CFQ:-CFQ, also known as "Completely Fair Queuing", is an I/O scheduler for the
Linux kernel which was written in 2003 by Jens Axboe.
CFQ works by placing synchronous requests submitted by processes into a number of per-process queues and then allocating timeslices for each of the queues to access the disk. The length of the time slice and the number of requests a queue is allowed to submit depends on the IO priority of the given process. Asynchronous requests for all processes are batched together in fewer queues, one per priority.​
BFQ:- BFQ is a proportional share disk scheduling algorithm based on the slice-by-slice service scheme of CFQ. But BFQ assigns budgets, measured in number of sectors, to tasks instead of time slices. The disk is not granted to the active task for a given time slice, but until it has exahusted its assigned budget. This change from the time to the service domain allows BFQ to distribute the disk bandwidth among tasks as desired, without any distortion due to ZBR, workload fluctuations or other factors. BFQ uses an ad hoc internal scheduler, called B-WF2Q , to schedule tasks according to their budgets. Thanks to this accurate scheduler, BFQ can afford to assign high budgets to disk-bound non-seeky tasks (to boost the throughput), and yet guarantee low latencies to interactive and soft real-time applications.​
I/O performances on MiniCM10-4.1.0 /w 2.6.32.60 nAa-JB-05 :
here is a chart showing scheduler specific results,
the benchmarks were based on Antutu, regarding IO and SDcard R/W
my settings are :
122~729MHz
smartassH3
undervolted
KSM
zram 18%
swap file 128MB​
all i can say for now, is that SIO is the more balanced scheduler, and CFQ/VR are the worst
here are the results
what does the chart shows us?
SIO is the more balanced scheduler, it has a good IO, and a good read/write
Anticipatory has the best IO, but a bad SDwrite
Deadline has the best SDwrite, but is quite average for IO and SDread
NOOP, CFQ and VR are a bit behind
for people using swap, i would say that they should use SIO or deadline, for others, Anticipatory or BFQ might be better
i ran the benchmark 4 times for each scheduler.​
source
Benchmarks history since stock rom here
MORE BENCHMARKS HERE
thanks to Heronger and some others helping to build this FAQ
are the reserved threads in x8 development for JB?
hetunandu said:
are the reserved threads in x8 development for JB?
Click to expand...
Click to collapse
where are the reserved threads you are talking about?
matmutant said:
where are the reserved threads you are talking about?
Click to expand...
Click to collapse
in x8 android development section
http://forum.xda-developers.com/forumdisplay.php?f=1704
hetunandu said:
in x8 android development section
http://forum.xda-developers.com/forumdisplay.php?f=1704
Click to expand...
Click to collapse
maybe
matmutant said:
maybe
Click to expand...
Click to collapse
arghhhh!! cant wait!!
BTW do u need testers? im in. I have an X8. PM me
Great job matmutant!:good:
I have questions/suggestion request about minicm 10 for xperia x8, i have a very little space to store applications, any suggestions? With GB I can use a lot of apps moving its in SD but with MiniCM 10 also moving apps I can install all the apps that I use before.
Use an ext partition for example it would be useful?
Another thing is the automatic conversion trom SMS to MMS when it exceeds a page in length. Only using another app for messages it wont be this way but i thing it would be great if we can use the stock app that I think is great!
A q aswell(actually I'm not sure of something)
nAa said it will repartition our space and said to uninstall we need to flash using seus or flashtool so that means to go back to stock partition we need to flash good ol eclair or any other kernel(eg. nAa gb) will get back our partition?
Sent from my heart™ using Xperia X8
X8invisible13 said:
A q aswell(actually I'm not sure of something)
nAa said it will repartition our space and said to uninstall we need to flash using seus or flashtool so that means to go back to stock partition we need to flash good ol eclair or any other kernel(eg. nAa gb) will get back our partition?
Sent from my heart™ using Xperia X8
Click to expand...
Click to collapse
I think he means that if we want move to another kernel we have to use seus or flashtool the way we always flash new kernel, for example flashing again naa-13 over jb kernel using flashtool without going back to eclair first.
I tried to make an ext partition in my sd card with CWM, now I have more memory to store my apps and system is so fast! This rom is great!
I only have sometimes random reboots and sometimes the screen crashes but now this is my daily rom!
Does swap partition works in MiniCM10 ?
I still don't quite understand about the meaning of clearing data, cache, etc...
Currently, I'm still at MiniCM 2.2, with a swap partition, EXT 4 partition, and FAT partition...
What is the correct sequence to run JB for the first time ?
Do I have to :
1. Reformat my MMC first + deleting the partition, go to recovery, format data, cache, etc, then make new partition (Swap, EXT4, and FAT)
OR
2. Format data, cache, etc, then reformat my MMC (as Swap partition gets changed to EXT3 automatically when doing factory reset), then make new partition.
Can somebody help ? Thank you in advance
StardustGeass said:
Does swap partition works in MiniCM10 ?
I still don't quite understand about the meaning of clearing data, cache, etc...
Currently, I'm still at MiniCM 2.2, with a swap partition, EXT 4 partition, and FAT partition...
What is the correct sequence to run JB for the first time ?
Do I have to :
1. Reformat my MMC first + deleting the partition, go to recovery, format data, cache, etc, then make new partition (Swap, EXT4, and FAT)
OR
2. Format data, cache, etc, then reformat my MMC (as Swap partition gets changed to EXT3 automatically when doing factory reset), then make new partition.
Can somebody help ? Thank you in advance
Click to expand...
Click to collapse
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size)
then set up your swap
and install the rom
swap partition should work
what doesn't work is the swap info menu
_______________________
benchmark of the day :
matmutant said:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size)
then set up your swap
and install the rom
swap partition should work
what doesn't work is the swap info menu
_______________________
benchmark of the day :
Click to expand...
Click to collapse
Please show your settings.MATMUTANT
Sent from my U20i using xda premium
benchmark :
[/QUOTE]
SERIOUSLY. I haven't had a high score on my mimmi with my MiniCM7 with most of apps I need and apps for UI improvements(themes/widgets/etc). I also use v6 SuperCharger of zepplinerox. I only had a 1853 score. but this score is higher. does this have potential to overthrow the speed and performance of MiniCM7?
minicm10 doesn't have as much features as minicm7 or 9 but is much smoother and more powerful right now .
my settings are simple:
ksm on, disable hardware override on, swap file 128 , uv on, else: default
note that this screen shot was taken on a private nightly of the next release :

[ROM]★[TF201 KitKat 4.4.4][ZOMBi-X OMNI KANG B5[Oct 30]★

{
"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"
}
YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1 AND TWRP 2.6.3.1+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM base. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD/DATA2sd/F2FS support
Remixed _thatv10 kernel with OMNI ramdisk - repacked by sbdags
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 213 (TF700 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-X, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Asus Apps: Compiled by kansasboy001; Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
Tweaks: File system and performance optimised, Init.d support!, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
[*]Tip 2: In Dev Settings, enable advanced reboot & change window animation,
transition animation & animator scales down to 0.2x for extra snappiness
[*]Tip 3: FLOATING WINDOWS: Settings - Interface - more... - Omni Switch
Bug List
[*] Dock works as do most special keys - just no battery available in the system bar
Change Log
20141002 Beta 3 changes</#></b>
- Added thatv11 to installer
- Added Grimlockv4 to installer
- Fixed BT not turning on without rebooot
- Fixed Bluethooth Share crash on first boot
- Fixed Dock battery reporting (needs an app/widget to work)
- updated dolphin browser to version 11.2.3
- updated google tts to 3.2.12
- updated google music to version 5.6.1523p
- updated google mail to version 4.9
- updated google search to version 3.6.14.1337016
- updated google talkback to version 3.5.2
- updated google play store to version 4.9.13
- updated google core services to version 5.0.89
- updated youtube to version 5.10.1.5
- updated apex launcher to version 2.6.0
- updated adaway to version 2.9.1
20140829 Beta 2 changes
- Fixed issues with Root being lost - reverted to cm11 ramdisks rather than omni as this was causing the issue
- SuperUser and SU Binary updated to version 2.0.2
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
20140826 Beta 1 changes
- New Base - Rebuilt from latest source which has updated bluetooth config - thanks lj50036
- 90% of dock should be working - battery display is not
- Added CM11 Kernel as option in installer - runs well
- Themed framework with a splash of RED
- Final Tweaks to Aroma Theme
- Updated GravityBox to version 3.3.3
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Small changed to aroma themes to fix dark text on dark backgrounds
- Changed the transition config in aroma to see if it fixes screen freezes
- Fixed installer script to allow rom2sd on grimlock kernel install
- Fixed aroma freezes - or reduced them
- Re-themed Zombi-X aroma theme
- Updated performance switch for CPU to allow OC to 1800 on _that's kernel
- Fixed correct rom version in the build.prop
- Updated SU Binary to latest version
- Updated Chrome, Gmail, Google Now, YouTube
- Added Android Terminal to ROM
- New Red Aroma Theme for Zombi-X - requires less memory
- Initial release - omni cromified after source build
- Added SuperUSer and su binary for root capability
- Browser tweaked for speed and touch smoothness
- Added all the CROMBi/CROMi goodness to the base rom
- Aroma tuned for ZOMBi-X
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk ROMS)
@lj50036 - Source Guy (From CROMBi-kk ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : BxMxK, canito10, duckredbeard, mikew29, nameneeded, cgf, cyberknight2001, Mikey1969, Ozark_8125, tiernan22, boldnuts, tonyh51, Vathan, erisi, Thibor69
To Do
[*]Fix Buetooth and other little bugs
XDA:DevDB Information
ZOMBI-X, ROM for the Asus Eee Pad Transformer Prime
Contributors
lj50036, sbdags, hardslog, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: bootloader ending in 27.1
Based On: OMNI AOSP
Version Information
Status: Beta
Current Beta Version: 20140827
Beta Release Date: 2014-08-27
Created 2014-10-27
Last Updated 2014-10-27
How to Upgrade and Downloads
UPGRADE INSTRUCTIONS
REFER TO POST #5 FOR UPGRADE INSTRUCTIONS​
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-X ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not
ZOMBi-X Beta 3 Full Mirror 1
ZOMBi-X Beta 3 Full Mirror 2
ZOMBi-X Beta 3 Full Mirror 3
BOTH FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ASUS APPS DOWNLOAD - Flash from Recovery : Compiled by kansasboy001
Don't forget ROM2SD1.zip / DATA2SD1.zip first if you are not running an internal setup
Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-X to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-X and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-X zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD support
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-X but this time choose the ROM2SD / DATA2SD option
Reserved
@spudsmac
@miduku
@robbie888
@lightiv
@Bigred007
@Waldo_
@emfanitek
@rlanza1054
@Unidave199
@Lock-N-Load
@Fear Knot
@lvrijn
@mitsublw
@scouzers
@zdebel
@jhr5474
@Eddie Hicks
@smchadwell
@dladz
@eRPeeX
@LocusofZen
Thx everyone that has donated, if you do not see your user name here and have donated, shoot me an PM and I will add you....
Thx Josh
TWRP
UNOFFICIAL TWRP [email protected]_V1.0​
Contributors:
The Crombi Team ....
Credits:
TEAMWIN - Thx guys for all the help ...
_that - All the many hours and late nights....
Sources:
Device tree:
omni_android_device_asus_transformer-common
omni_android_device_asus_tf300t
Kernel:
grimlock_kernel_asus_tegra3_unified
CHANGELOG
- Made it possible to mount all 3 partitions on the external_sdcard from within TWRP ....
- Added 'reboot recovery' & 'reboot bootloader' as options in REBOOT
- These partitions will show up as ......
external_sdcard = User storage space, should be formatted vfat
external_data = Will become /data for ROM2SD or DATA2SD, can be formatted either EXT4 or f2fs both can now be done from within TWRP ...
external_system = Will become /system for ROM2SD, should be formatted EXT4 can also be done from with in TWRP ....
This should make it very nice to make backups and restore without the need for the rom2sd1.zip or the data2sd.zip ......
Click to expand...
Click to collapse
BLOB DOWNLOAD MIRRORS
UNOFFICIAL TWRP MIRROR 1
- md5 d4effaf97a51674bac04c6ccbf4fd892
UPGRADE INSTRUCTIONS, STEP BY STEP​
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Kernel Sources
All Kernels included in this ROM package are unofficial, as they are complied from source, thay may not match the source that they were forked from. I will be linking the kernel source code as per the GNU GPL License.
Unofficial @hardslog Grimlock Kernel Source CLICK ME@-V1.0.0
Unofficial CM-11.0 Kernel Source CLICK ME@-V1.0.0
Unofficial @_that Kernel Source CLICK ME @-V1.0.0
Official @hardslog Grimlock Kernel Source CLICK ME
Official CM-11.0 Kernel Source CLICK ME
Official @_that's Kernel Source CLICK ME @-V11
Snagged like a Snagglepuss!
So much love for the Prime users
Hi Guys,
Thanks for providing the Omni experience for our tablets:good:
I have the Crombi-x on board now, but will flash soon.
As for TWRP, I'm running Neozone's one (also 2.8), do You recommend switching to the recovery used by Your Team?
I've seen the thread in TF300 forum and my opinion is: it's not a beta, rather stable from what I've read...
GibonXL said:
Hi Guys,
Thanks for providing the Omni experience for our tablets:good:
I have the Crombi-x on board now, but will flash soon.
As for TWRP, I'm running Neozone's one (also 2.8), do You recommend switching to the recovery used by Your Team?
I've seen the thread in TF300 forum and my opinion is: it's not a beta, rather stable from what I've read...
Click to expand...
Click to collapse
They are both very good recoveries, really its an end-user choose here, I do like my TWRP as you can do some nice things with the EXT-SDcard....
Thx Josh
Wowwwww... Long time without playing with my prime! Have been with haribean for a while!!!
Is the rom stable?
Which kernel do you recommend for the best battery saving a stable experience!
Thanks
Regards!
been running this for 24 hrs now on my prime, using the f2fs file system and _thats11 kernel, running very well, thanks Josh
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
sauliiin said:
Wowwwww... Long time without playing with my prime! Have been with haribean for a while!!!
Is the rom stable?
Which kernel do you recommend for the best battery saving a stable experience!
Thanks
Regards!
Click to expand...
Click to collapse
I dont know about stable, we are still in BETA testing. There is no reason i can see why it could not be ran as a daily driver .....
The betas are going to be coming a bit faster then RC or R releases which sometimes people dont like.. ...
I prefer grimlocks kernel for the best out of your 201 ......
Thx Josh
boldnuts said:
been running this for 24 hrs now on my prime, using the f2fs file system and _thats11 kernel, running very well, thanks Josh
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
Great to see you up and running, let use know if there is anything we can do along the way ..... :laugh:
Thx Josh
B5 !!!!
UPLOADING B5 NOW ....
20141030 Beta 5 changes
- Merged tinted status bar into ZOMBi
- Tweeked muti-window [issues with tinted window]
- Added SU as a prebuit [updateable from the playstore]
Click to expand...
Click to collapse
Better than CM
Hi, flashed B4 today and want to provide some feedback:
- had a system FC after rom instalation, when the setup wizzard started, but continued without problems
- my Prime worked best with Slim ports, but Omni base sets the stanards even higher
- running Grimlock kernel.
So far, so good, missing the dock battery indicator, but can live with widgets.
Right now I'm streaming radio and plugged external spekers, having some good time here:good:
My old Prime is loaded with upstream kernel and Omni goodies
As for B5, do You recommend a clear or dirty flash?
lj50036 said:
UPLOADING B5 NOW ....
20141030 Beta 5 changes
Click to expand...
Click to collapse
Thanks for not let ours Prime todie! Any chance to include a Axis Reverse Fix? Just asking...:good:
Beta5 goes pretty stable on my Prime :good:
I was curious of the lags in menu and slow showing floating Omniswitch. Pretty strange, as I,m on F2FS and using Grimlock kernel (good experience with this one on Slim ports).
Does it happen to anyone else? Well, there's a fix.
I highly recommend switching the minimum CPU frequency to 370 in preformance.
Beta4 was running smoother and faster, but above trick does the job.
The tinted feature is just awesome
Another pro is well working dock keyboard.
Okies, now for the browsers testing
How do you get F2FS on the Transformer Prime TF201? Or is that function something for the other devices that was carried over? I dont see any recoveries here supporting it...
raylgo said:
How do you get F2FS on the Transformer Prime TF201? Or is that function something for the other devices that was carried over? I dont see any recoveries here supporting it...
Click to expand...
Click to collapse
The official TWRP 2.8.1.0 supports it ... http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.8.1.0-tf300t.blob
You do have to be in the HariyBean bootloader but I would guess you are .....
Thx Josh
Call me stupid, but where is 'upgrade_tf201_to_tf300t.zip'?
I have little experience with custom roms, only installed CM11 on my phone recently and decided to try putting something else on my tablet.
****
Edit: Don't worry, found it in the CROMBi-kk-R1 thread.
******
Edit again: trying to flash the recovery and it gives me "failed (remote: (invalidstate))". I can't even get into recovery, just get the alien with a red ! and it eventually reboots into android.
Any ideas?
*************
Triple edit: I forgot to unlock the bootloader downloaded the apk, just didn't run it.

[Kernel] [S7262] [22/05/2015] Beast™ Kernel v2.1

{
"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"
}
FOR UPDATE, GO HERE
Beast™ Kernel v2.1
For Samsung Galaxy Star Pro S7262 (logan2g)
#StarProBeast
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD Cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this kernel before following it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
"It takes days to make a kernel but it doesn't even take few seconds to press the Thanks Button" - arpith.fbi (XDA Recognized Contributor)
Click to expand...
Click to collapse
Compiled from Official Linaro Toolchain 4.6.4
[*]Compiled With Official Source Provided by Samsung
[*]Compiled With Latest Samsung Source
[*]Smoother than butter
[*]Speed Of Phone is Increased Drastically
[*]Most of Lag is Fixed
[*]Swap Partition Support
[*]Init.d Support
[*]Nano Text Editor Support
[*]App2SD Support (May Need Compatible ROM)
[*]Insecure boot image (Easy Root)
[*]Allowed Mock Locations From Kernel
[*]Allowed Kernel Debugging
[*]Insecure ADB Support
[*]Can Take Logcat from Bootsplash
[*]Can Use ADB Commands before phone fully starts up
[*]Added Kernel Linaro Patch
[*]Added Various Governors
[*]Added Custom Governors: SmartassV2, Lagfree, Lazy, InteractiveX, Lionheart.
[*]Made Powersave Default Governor New
[*]Added Various I/O Schedulers
[*]Added Custom I/O Schedulers: Deadline, SIO.
[*]Made Noop Default I/O Scheduler New
[*]Added USB Fastcharge Support
[*]Added USB Keyboard Support
[*]Added NTFS (R/W), MSDOS, VFAT, FAT Filesystems Support
[*]Battery Life Increased
[*]Compatible SuperSU Binary And App
[*]Added Busybox binary
[*]Added sysro and sysrw binaries
THE FOLLOWING STEPS SHOULD ONLY BE PERFORMED ON A SAMSUNG GALAXY STAR PRO/PLUS (GT-S7262)
Steps:
1] Download Beast™ Kernel's Latest Module's Zip From the Download Section of the thread
2] Transfer it (without extracting) to your phone's External SD Card
3] Download Beast™ Kernel's Latest BOOT-IMAGE.tar.md5 From the Download Section of the thread
4] Switch off your phone
5] Put your phone in Download Mode (Volume down + Home + Power buttons simultaneously)
6] Press Volume Up to continue when asked
7] Download Odin.zip on your PC
8] Extract Odin.zip with Winrar and open Odin.exe file (the file with a blue icon)
9] Connect Phone to PC with USB Cable
10] Wait for some 15 seconds and see if COM(number) port has come in Blue colour <If it does not appear, read FAQ>
11] Select PDA and browse to Beast™ Kernel's Latest BOOT-IMAGE.tar.md5
12] Click the Flash button
13] Wait for it to show RESET in blue colour
14] After it shows Reset Disconnect phone from PC by removing USB Cable
15] Remove Battery of Phone
16] Insert Battery of phone
17] Put your phone in Recovery Mode (Volume Up + Power + Home buttons simultaneously)
Now use Volume buttons to navigate Up and Down (To go up, press Volume Up button Once. To go down, press Volume Down button Once) And To select an option, use the Power Button
18] Go to Install Zip From SD Card Select it
19] Go to Choose Zip From SD Card Select it
20] Now browse to Beast Kernel's Latest Module's Zip where you had transferred it to your external SD Card
21] Select It
22] Go to Yes by pressing Volume Down button. Select it
23] After the process completes, you have successfully flashed The Beast™ Kernel!
24] Now Go Back And Select Reboot Phone
25] Enjoy!
Beast™ Kernel v1
Beast™ Kernel v2
Beast™ Kernel v2.1 Modules Zip | Beast™ Kernel v2.1 BOOT-IMAGE.tar.md5
Beast™ Kernel
Beast™ Kernel Ramdisk
Please press the Thanks Button guys! It means a lot to us devs
"Code Wins Arguments" - regalstreak (XDA Senior Member)
Click to expand...
Click to collapse
XDA:DevDB Information
Beast™ Kernel, Kernel for Samsung Galaxy Star Pro
Contributors
regalstreak
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2015-05-22
Created 2015-05-20
Last Updated 2015-05-22
FAQ
Q1) Will it work on my ROM?
Ans: Yes! It works on all the ROMs available for our device. (Custom/Stock)
Q2) The phone is lagging!
Short Answer:It will ofcourse lag in the beginning for a minute. See the phone speed up after that!
Long Answer:The phone builds the cache and dalvik cache required to run the programs and apps for the device. So it takes around one or two minutes for the device to start-up completely. So just wait for that duration. Then enjoy my kernel
Even then, if it is lagging. it is because of your phone. Try clearing cache from recovery and uninstall some unnecessary apps.
Q3) When will you add feature X?
Ans: Ill add them as soon as possible. If you need a feature, you can post that in the feature requests section, or even quote me here! But due to studies, it would require some time.
Q4) Can I use this kernel in my custom ROM?
Ans: You should seek my permission for that. Ask me on Facebook. I may reply fast. Here is my Facebook account: Neil Agarwal
Q5) I am facing white screen! Please help!
Ans: If you face the white screen error, update to latest version of the stock ROM. Then flash the kernel. If you have any other problems, you can quote me here!
Q6) I am not able to connect to my PC! Gimme a solution
Ans: These are the steps to solve the problem:
Open your Dialer App
[*]Enter: *#0808#
[*]A menu will now pop up
[*]Select MTP+ADB And Select OK!
Q7) I am not getting signal! I just can see Emergency calls only! Please help!
Ans: This is because you have lost your EFS folder. Your Internal SD Card might not work. Your Lock Screen might not work. When you press the power button for a short time, your phone may turn off directly. You may view yellow text on your screen. OK. Enough of info. Now, The Fix:
Go Here
Enjoy!
If it still does not work, Feel free to contact me!
Q8) My Lockscreen is not working!
Ans: Read FAQ Question 7
Q9) There is Yellow Text on my screen!
Ans: Read FAQ Question 7
Now You Are Good To Go!
Code:
[B]v2.1 - 22 May 2015[/B]
-Fixed Date/Time Reset Bug
-Made Powersave Default Governor
-Made Noop Default I/O Scheduler
-Fixed Phone not connecting to PC
[B]v2.0 - 19 May 2015[/B]
-Compiled from Official Linaro Toolchain 4.6.4
-Compiled With Newest Source
-Speed Of Phone Increased
-Increased Battery Life
-Added Swap Partition Support
-Added Init.d Support
-Added Nano Text Editor Support
-Added App2SD Support [Experimental]
-Added Insecure ADB Support
-Added Busybox binary
-Added sysro and sysrw binaries
-Added Kernel Linaro Patch
-Added Various Governors
-Added Various I/O Schedulers
-Added USB Fastcharge Support
-Added USB Keyboard Support
-Added Compatible SuperSU Binary And App
-Added NTFS (R/W), MSDOS, VFAT, FAT Filesystems Support
-Made Boot Image Insecure
-Allowed Mock Locations From Kernel
-Allowed Kernel Debugging
-Allowed Use ADB Commands before phone fully starts up
-Allowed Take of Logcat from Bootsplash
[B]v1.0 - 31 October 2014[/B]
-Initial release.
Swap Memory Support:
You can now increase your handset RAM size (virtually) using third party app or init.d script!
Use any Ram Expanding application or init.d script for Swap Memory. Make sure you have enough free space in External SD-Card to be used as Virtual Ram.
Make sure you select External SD-Card as swap partition before applying changes in your favorite ram expanding app/script.
Init.d support:
This feature allows users to install scripts and mods to be run at boot. Everything from battery tweaks to performance tweaks. It essentially opens the door to a world of mods, only possible through the Init.d process.
Make sure you have busybox in your xbin folder with run-parts enabled before trying out this feature.
Add any scripts you like to run at boot at /system/etc/init.d/ folder.
Nano Text Editor:
Nano is a text editor for Linux OS using a command line interface. It emulates the Pico text editor and also provides additional functionality.
To use it to edit a file, In Adb shell, get access to superuser permissions and then type "nano (filename.txt)
It is useful to unbrick the device in certain conditions.
App2SD Support: (EXPERIMENTAL)
Are you running out of application storage? Do you need the feature that can move apps to your SD Card? You have come to the right place!
This component streamlines the movement of apps to on your device's external or internal storage through your device's Settings.
With this, you'll have more control over your ever expanding collection of apps. This is crucial to anyone who has memory management issues.
Required App: AppMgr III
Governors:
Different kernels can support different CPU Governors, which manage the way your phone ramps up or down its clock speeds as you use it.
There are a few different kinds of Governors.
To Change an I/O Scheduler, You need an App. The Best One is: No-frills CPU Control
Go Here For More Reference
I/O Schedulers
Input/output (I/O) scheduling is a term used to describe the method computer operating systems decide the order that block I/O operations will be submitted to storage volumes.
I/O schedulers can have many purposes depending on the goal of the I/O scheduler, some common goals are:
To minimize time wasted by hard disk seeks.
To prioritize a certain processes' I/O requests.
To guarantee that certain requests will be issued before a particular deadline.
To Change an I/O Scheduler, You need an App. The Best One is: No-frills CPU Control
Go Here For More Reference
USB Force Fast Charge Support:
USB Fast Charge allows you to charge battery faster when connected to a PC/Laptop via USB using Fast Charge App. Very useful in certain situations.
Increases input current limit to 1000mA when charging via USB.
Required App: Fast Charge
USB Keyboard Support:
Turn your Android device into USB keyboard/mouse for your PC/Laptop. Very useful in certain situations.
Steps:
Start ADB Debugging
Start app
Connect device to system via USB cable
Required app: USB Keyboard
Beast™ Kernel v2.1 - Verified Working
.--== This is a complete break down of what was done. ==--.
USB Driver: SAMSUNG_USB_Driver_for_Mobile_Phones
Odin: Odin3 v3.10.6
Firmware: S7262XXUAOB2_S7262ODDAOB2_S7262XXUANI1_HOME.tar.md5
Kernel: Beast-v2.1-regalstreak-BOOT-IMAGE.tar.md5
Recovery: CWM-based Recovery v6.0.3.6
Kernel Modules: Beast-Kernel-v2.1-Modules-regalstreak.zip
SU: SuperSU (free) v2.46
1) Install Samsung USB Driver if not needed.
2) Start Odin, right click - 'Run as administrator'. Auto Reboot and F. Reset Time are CHECKED.
3) Boot device into Download Mode by holding Volume Down + Home + Power, press Volume Up when prompted.
4) While in Download Mode plug in your device.
5) Wait for drivers to complete and ODIN to indicate device was added.
6) Load files as noted, in the following order. Do not touch or mess with phone until ODIN is finished and states PASS, and phone has completed rebooted.
a) Select PDA/AP and browse to firmware's tar.md5 file
- S7262XXUAOB2_S7262ODDAOB2_S7262XXUANI1_HOME.tar.md5
- Wait for PASS in ODIN and for phone to reboot.
- Remove battery and reboot phone.
b) Select PDA/AP and browse to boot's tar.md5 file
- Beast-v2.1-regalstreak-BOOT-IMAGE.tar.md5
- Wait for PASS in ODIN and for phone to reboot.
- Remove battery and reboot phone.
c) Select PDA/AP and browse to recovery's tar.md5 file
- recovery.tar.md5
- Wait for PASS in ODIN and for phone to reboot.
- Remove battery and reboot phone.
7) Phone is rooted, with cutom kernel and custom CWM recovery.
8) Copy SuperSU to micro SD card. Boot phone into CWM by pressing Volume Up + Home + Power.
9) In CWM: Select 'install zip' - 'choose zip from sdcard' - 'SuperSU.zip' - 'Yes -Install SuperSU.zip'.
10) In CWM: Select 'install zip' - 'choose zip from sdcard' - 'Beast-Kernel-v2.1-Modules-regalstreak.zip' - 'Beast-Kernel-v2.1-Modules-regalstreak.zip'.
11) In CWM: wipe cache partition and wipe dalvik cache.
The following system apps can be removed with no system issues. Removal of apps is optional. After all the initial modifications for ROM, kernel / modules and recovery have been made, install a root file manager - ES File Explorer, Root Explorer, etc. Navigate to /system/app. Take a moment if needed to know what apps are needed or not - do not accidentally remove an app that may be needed later. Instead of completely deleting apps, it may be better to temporarily store apps to SD card.
Apps For Removal
AccuWeatherWidget_Main.apk
AccuWeatherWidget_Main.odex
AccuweatherWidget.apk
AccuweatherWidget.odex
Books.apk
ChatOn_MARKET.apk
ChatOn_MARKET.odex
Chrome.apk
Chrome.odex
Dropbox.apk
Dropbox.odex
DropboxOOBE.apk
DropboxOOBE.odex
FactoryTest.apk
GoogleDrive.apk
GoogleDrive.odex
GoogleSearchWidget.apk
GoogleSearchWidget.odex
Hangouts.apk
Hangouts.odex
Kies.apk
Kies.odex
MediaUploader.apk
MediaUploader.odex
MobileTrackerEngineTwo.apk
MobileTrackerEngineTwo.odex
Music2.apk
Music2.odex
Newsstand.apk
Newsstand.odex
PlayGames.apk
PlayGames.odex
SamsungApps.apk
SamsungApps.odex
SamsungAppsUNA3.apk
SamsungAppsUNA3.odex
Samsungservice.apk
Samsungservice.odex
SecEmail.apk
SecEmail.odex
SecExchange.apk
SecExchange.odex
SecLiveWallpaperPicker.apk
SecLiveWallpaperPicker.odex
SecMemo.apk
SecMemo.odex
SecNoteMyFiles.apk
SecNoteMyFiles.odex
Stk.apk
Stk.odex
Stk2.apk
Stk2.odex
Street.apk
Street.odex
talkback.apk
talkback.odex
Velvet.apk
VideoPlayer.apk
VideoPlayer.odex
Videos.apk
VoiceRecorder.apk
VoiceRecorder.odex
VoiceSearchStub.apk
VoiceSearchStub.odex
wssyncmlnps.apk
wssyncmlnps.odex
~zynperor
Do not remove !
Do not remove the following from /system/app.
These files are for the SIM Tool Kit
Stk.apk
Stk.odex
Stk2.apk
Stk2.odex
Glad you enjoyed the kernel bro
I will be releasing beast v3 soon. Please quote me the features you would like to have
Features...
Not really sure. Is there any way to get OTG working on the S7262?
After flashing - Update Device Information Information staying on home screen
I have updated CWM to 6.0.3.7.
Before all this, i have CWM 6.0.1.1. and have updated the Rom to Sweet Kit Kat rom v 4.4.2. After flashing a message like below is staying on home screen and if i am calling a no, then message is comming "Not registred on network".
If i am restarting to recovery, it is not going to the same and rebooting to normal phone mode and during boot in "SAMSUNG Logo screen i am getting a small RED line, which i have viewed when previously i enter to Recovery Mode. Please HELP me what to do and How to solve the problem. I am a software professional and can get your instructions very easily. Please help me.
The message showing on the Home screen is like this:
Update Device Information
PDA : S7262XXUAND5
PHONE : S7262XXUANI1
CSC : UNKNOWN
H/W :
RF Cal Date: Unknown
SMD : 01N, PBA:04N, CAL:07N, FINAL:11N
UN : CN50AD19B8697C0
Rear CAM: SR200PC20M NA
TSP : ZI212207 ZI212207
TSK : ZI212207 ZI212207
CH : NA
UART : NA , USB: NA
---------- Post added at 03:17 PM ---------- Previous post was at 02:32 PM ----------
Sir,
from previous post i felt that, my EFS folder is deleted. Please instruct me "How to restore it:. Please Help me.... .
rkpatra.pc said:
I have updated CWM to 6.0.3.7.
Before all this, i have CWM 6.0.1.1. and have updated the Rom to Sweet Kit Kat rom v 4.4.2. After flashing a message like below is staying on home screen and if i am calling a no, then message is comming "Not registred on network".
If i am restarting to recovery, it is not going to the same and rebooting to normal phone mode and during boot in "SAMSUNG Logo screen i am getting a small RED line, which i have viewed when previously i enter to Recovery Mode. Please HELP me what to do and How to solve the problem. I am a software professional and can get your instructions very easily. Please help me.
The message showing on the Home screen is like this:
Update Device Information
PDA : S7262XXUAND5
PHONE : S7262XXUANI1
CSC : UNKNOWN
H/W :
RF Cal Date: Unknown
SMD : 01N, PBA:04N, CAL:07N, FINAL:11N
UN : CN50AD19B8697C0
Rear CAM: SR200PC20M NA
TSP : ZI212207 ZI212207
TSK : ZI212207 ZI212207
CH : NA
UART : NA , USB: NA
Click to expand...
Click to collapse
rkpatra.pc said:
I have updated CWM to 6.0.3.7.
Before all this, i have CWM 6.0.1.1. and have updated the Rom to Sweet Kit Kat rom v 4.4.2. After flashing a message like below is staying on home screen and if i am calling a no, then message is comming "Not registred on network".
If i am restarting to recovery, it is not going to the same and rebooting to normal phone mode and during boot in "SAMSUNG Logo screen i am getting a small RED line, which i have viewed when previously i enter to Recovery Mode. Please HELP me what to do and How to solve the problem. I am a software professional and can get your instructions very easily. Please help me.
The message showing on the Home screen is like this:
Update Device Information
PDA : S7262XXUAND5
PHONE : S7262XXUANI1
CSC : UNKNOWN
H/W :
RF Cal Date: Unknown
SMD : 01N, PBA:04N, CAL:07N, FINAL:11N
UN : CN50AD19B8697C0
Rear CAM: SR200PC20M NA
TSP : ZI212207 ZI212207
TSK : ZI212207 ZI212207
CH : NA
UART : NA , USB: NA
---------- Post added at 03:17 PM ---------- Previous post was at 02:32 PM ----------
Sir,
from previous post i felt that, my EFS folder is deleted. Please instruct me "How to restore it:. Please Help me.... .
Click to expand...
Click to collapse
Your answer is in the FAQ. Please read question 7. Press the thanks button if i helped
zynperor said:
Not really sure. Is there any way to get OTG working on the S7262?
Click to expand...
Click to collapse
No bro! unfortunately samsung touchwiz ROMs dont support OTG. So, we cant have that lovely feature. But it is already present in the kernel. If any1 finds a way to use, pm me
regalstreak said:
... unfortunately samsung touchwiz ROMs dont support OTG. So, we cant have that lovely feature. But it is already present in the kernel. If any1 finds a way to use, pm me
Click to expand...
Click to collapse
Since it seems to be an issue with the ROM, are there currently any available and stable ROMs having the OTG function?
Above not worked for me. But managed to get back to previous.
regalstreak said:
Your answer is in the FAQ. Please read question 7. Press the thanks button if i helped
Sir, your efs restore didn't worked for me. So, i rolled back to previous stock rom backup through CWM recovery. Then i restored efs from -- EFS image created by Neil Agarwal) -- and then again upgraded my rom to kitkat. After that i restored my Original efs partion through EFS Professional. But i have 02 nos of questions.
(1). Whether Beast Kernel 2.1 is only for stock rom not for any other custom rom, as in my case Kitkat rom by LogansDroids. It's compatibillity ?
(2). I have successfully flashed the Beast Kernel but lost my efs partion. During that period... Why EFS Professional didn't recognize my phone as rooted and the program exited and i am unable to restore my original backed up efs partion.
Please answer... Thanks a lot.
No bro! unfortunately samsung touchwiz ROMs dont support OTG. So, we cant have that lovely feature. But it is already present in the kernel. If any1 finds a way to use, pm me
Click to expand...
Click to collapse
Please answer... Thanks a lot.
zynperor said:
Since it seems to be an issue with the ROM, are there currently any available and stable ROMs having the OTG function?
Click to expand...
Click to collapse
No There are not any other ROMs available for our device
rkpatra.pc said:
Please answer... Thanks a lot.
Click to expand...
Click to collapse
A1) The Kernel is compatible with other ROMs too. It might not be working for that rom because the ROM may be based on older firmware version.
A2) I dont know you sholud root ur device again after flashing the kernel.
good job neil.hope you will add some new features in next version.thanks for kernal
probleme with the link of download correction pleas....................and thank you
regalstreak said:
FOR UPDATE, GO HERE
Beast™ Kernel v2.1
For Samsung Galaxy Star Pro S7262 (logan2g)
#StarProBeast
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD Cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this kernel before following it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Compiled from Official Linaro Toolchain 4.6.4
[*]Compiled With Official Source Provided by Samsung
[*]Compiled With Latest Samsung Source
[*]Smoother than butter
[*]Speed Of Phone is Increased Drastically
[*]Most of Lag is Fixed
[*]Swap Partition Support
[*]Init.d Support
[*]Nano Text Editor Support
[*]App2SD Support (May Need Compatible ROM)
[*]Insecure boot image (Easy Root)
[*]Allowed Mock Locations From Kernel
[*]Allowed Kernel Debugging
[*]Insecure ADB Support
[*]Can Take Logcat from Bootsplash
[*]Can Use ADB Commands before phone fully starts up
[*]Added Kernel Linaro Patch
[*]Added Various Governors
[*]Added Custom Governors: SmartassV2, Lagfree, Lazy, InteractiveX, Lionheart.
[*]Made Powersave Default Governor New
[*]Added Various I/O Schedulers
[*]Added Custom I/O Schedulers: Deadline, SIO.
[*]Made Noop Default I/O Scheduler New
[*]Added USB Fastcharge Support
[*]Added USB Keyboard Support
[*]Added NTFS (R/W), MSDOS, VFAT, FAT Filesystems Support
[*]Battery Life Increased
[*]Compatible SuperSU Binary And App
[*]Added Busybox binary
[*]Added sysro and sysrw binaries
THE FOLLOWING STEPS SHOULD ONLY BE PERFORMED ON A SAMSUNG GALAXY STAR PRO/PLUS (GT-S7262)
Steps:
1] Download Beast™ Kernel's Latest Module's Zip From the Download Section of the thread
2] Transfer it (without extracting) to your phone's External SD Card
3] Download Beast™ Kernel's Latest BOOT-IMAGE.tar.md5 From the Download Section of the thread
4] Switch off your phone
5] Put your phone in Download Mode (Volume down + Home + Power buttons simultaneously)
6] Press Volume Up to continue when asked
7] Download Odin.zip on your PC
8] Extract Odin.zip with Winrar and open Odin.exe file (the file with a blue icon)
9] Connect Phone to PC with USB Cable
10] Wait for some 15 seconds and see if COM(number) port has come in Blue colour <If it does not appear, read FAQ>
11] Select PDA and browse to Beast™ Kernel's Latest BOOT-IMAGE.tar.md5
12] Click the Flash button
13] Wait for it to show RESET in blue colour
14] After it shows Reset Disconnect phone from PC by removing USB Cable
15] Remove Battery of Phone
16] Insert Battery of phone
17] Put your phone in Recovery Mode (Volume Up + Power + Home buttons simultaneously)
Now use Volume buttons to navigate Up and Down (To go up, press Volume Up button Once. To go down, press Volume Down button Once) And To select an option, use the Power Button
18] Go to Install Zip From SD Card Select it
19] Go to Choose Zip From SD Card Select it
20] Now browse to Beast Kernel's Latest Module's Zip where you had transferred it to your external SD Card
21] Select It
22] Go to Yes by pressing Volume Down button. Select it
23] After the process completes, you have successfully flashed The Beast™ Kernel!
24] Now Go Back And Select Reboot Phone
25] Enjoy!
Beast™ Kernel v1
Beast™ Kernel v2
Beast™ Kernel v2.1 Modules Zip | Beast™ Kernel v2.1 BOOT-IMAGE.tar.md5
Beast™ Kernel
Beast™ Kernel Ramdisk
Please press the Thanks Button guys! It means a lot to us devs
XDA:DevDB Information
Beast™ Kernel, Kernel for Samsung Galaxy Star Pro
Contributors
regalstreak
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2015-05-22
Created 2015-05-20
Last Updated 2015-05-22
Click to expand...
Click to collapse
meha2016 said:
Click to expand...
Click to collapse
I didnt get you.
best kerne evwe
Good
Need help, in My HH why this kernel make the signal of sim is gone:crying::crying:
not good at all
it makes lag with lolipop 2 custom rom... stock kernel was better.
respect to your hard works. but not worked for me,
now im going to find stock kernel again
Hey regalstreak I successfully flashed your kernel on my S7262 and I thank you for this, but im facing some issues with this kernel. It did not happen before when I'm using stock kernel.
1.) When I mount the sd card in my phone or if I restart/reboot/open the phone with sd card inserted, some of the files inside (eg. videos, musics) becomes 0bytes and corrupted. It did not happen if I greenify all my apps (including system apps) before I insert my sd card.
2.) Sometimes the touch of my phone freezes on boot even I'm opening only light apps like Opera Mini but the app is still running. I observed this because I am using "Show touches" in debug mode. And when I open heavy apps like Clash of Clans, the touch pointer freezes but the app is running, so when I try to attack a village, yipee "I lost" haha...
I hope you understand this coz I'm a Filipino and literally poor in English haha. I hope you give me an advice for this issue and it will be fixed soon. Thanks again for the kernel.

Development [KERNEL] CleanSlate T 2.4.0/S 1.4.2 |AdBlock|SafetyNet|BatterySaver [Oct 28]

tbalden's
CleanSlate kernel
for Asus ZenFone 9
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"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"
}
As always tbalden is here to bring you authentic new features first in line, this year Asus ZF9.
No root elevation (magisk) needed for all functions and preference switches through CS Config App
​
Release Calendar
Version 2.4.0 - 13 of Dec 2022
Version 1.4.2 - 28 of Oct 2022
Version 1.0.0 - 29 of Aug 2022
Should work on official ROM bases 32.2050.2050.x+.
Features:
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Haptic Type Tweak change haptic feedback waveform types
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass passes if using without Magisk/Rooting, flashing the boot img only, Google Pay should work
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Face down screen off - put phone face down to turn screen off
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by ASUS, 5.10.x
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Requirements
- Unlocked ZF 9, stock or with magisk root
- BACKUP: make sure you have a stock image (boot img) from asus before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion apps on your phone (both found down below in Download section). (On play store version: with Android 12 you need to join the Beta program for the correct app versions.) Set them up initially.
- Non-rooted method: 0. download the non-rooted boot img.zip, UNZIP it first!
Reboot to bootloader, and flash the images with these commands:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
.. reboot, enjoy
- Rooted method: 0. download the rooted installer zip
1. install magisk
2. use a Kernel Flasher to flash the installer zip
- For SafetyNet, Adblocking, after flashing you might need to restart the phone after the first boot, otherwise it might not work.
- For adblocking KAdaway switching on and off, you will need to Force Close browser app like Chrome to let it work in the given browser.
- For Play Integrity (with SafetyNet passing) you might need to Clean App Data in Google Play Store app to make it reevaluate Integrity
--- If you have magisk installed Play Integrity might be tripped. I only tested without Magisk, flashing CleanSlate 1.0.0 bootimage.
- If using Companion App for notification / gesture etc features, there's a setting in the app to Switch off Proximity sensor while Screen is on. This will prevent the flickering, but Face down screen off feature won't work
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
Download
Android 13
Non rooted, Android 13 images
ZF9 non rooted installer images zipped - 33.2060.2060.65 WW - CS 1.4.2: https://forum.xda-developers.com/attachments/fastboot_cleanslate_s_zf9_240_imgs-zip.5784177/
Rooted installer zip, Android 13 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 2.4.0: https://forum.xda-developers.com/attachments/cleanslate_s_zf9_240-zip.5784179/
Android 12
Non rooted, Android 12 images
ZF9 non rooted installer images zipped - 32.2050.2050.29 WW - CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Rooted installer zip, Android 12 images
ZF9 to flash from rooted phone with Kernel Flasher: CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android 12 image
ZF9 boot image zipped - 32.2030.2030.26 WW - CS 1.0.0: https://www.androidfilehost.com/?fid=14871746926876840958
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore:
You need to join the BETA program to get the working version for the kernel!
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.2.x -- Donation premium on playstore:
You need to join the Beta program to get the working version for the kernel!
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
How to join beta program: https://forum.xda-developers.com/t/...ashlight-s2s-vib-dec-22.4281807/post-86171493
Android 12:
Companion App 3.3.9 -- Normal free download:
https://www.androidfilehost.com/?fid=15664248565197208875
Configuration App 3.2.11 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876820727
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Special thanks to AnyKernel installer developer: osm0sis
To @Freak07 for all his work on XDA and help
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
Source Code: https://github.com/tbalden/android_kernel_asus_zf9_common-kernel
Readme's and howtos
Changelogs come here later
Be aware that in Battery Saver feature, there's CURRENTLY NO CAMERA APP FOREGROUND DETECTION! Please disable this feature when you use Camera apps (otherwise slow camera, video recording)!
Hopefully camera detection can come later, as still working on more features.
nice work!
great to see you here
Great develop
Thanks for sharing! If I have the patience to get the C version when it eventually releases, I'll give this kernel a try!
- Update Android 12 Stable - 1.4.0 -
Major CleanSlate feature update
​
- Build and repack to QGKI2 kernel format (boot, vendor_boot, vendor_dlkm, dtbo images) with new scripts
--- Thanks go to @Freak07 for the teamwork of many hours in getting to the bottom of this crooked path to build Qualcomm's new modular kernel format and make it work on the ZenFone 9
--- Thanks go to ASUS for providing the most complete sources zip for Qualcomm based QGKI kernels up to date by ANY vendor/OEM.
--- Thanks go to @osm0sis for his AK3 installer and @capntrips for his excellent tooling in AK3 and the tips help he lended in the process of getting things rolling
- Now all features possible to implement added to drivers
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
-- Updates
-- Hosts file for KAdaway
-- Safetynet + Play integrity still passes without Magisk
-- All features work with or without Magisk (tho flashing magisk will break safetynet until you use SafetyNet fix magisk modules)
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.0 Downloads:
Rooted installer zip:
CleanSlate S 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820728
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2030.2030.26)
fastboot image zip CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876820729
Cleanslate config app version 3.2.11 needed for new features:
Free version download: https://www.androidfilehost.com/?fid=14871746926876820727
Premium version: https://play.google.com/store/apps/details?id=org.cleanslate.csconfig&hl=hu&gl=US
- rolled out to playstore Beta program
Read first post in thread for installation details.
Will it run with the latest fw update?
NisseGurra said:
Will it run with the latest fw update?
Click to expand...
Click to collapse
It actually runs, but new sources are up, and I'm updating the installers soon.
- Update Android 12 Stable - 1.4.1 -​
CleanSlate asus sources update
-- sources updated to 2040.23
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.1 Downloads:
Rooted installer zip:
CleanSlate S 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834460
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2040.2040.23)
fastboot image zip CS 1.4.1: https://www.androidfilehost.com/?fid=14871746926876834462
Read first post in thread for installation details.
Installed, seems flawless
2040.28 update is up, with sources. The new sources has no changes, tested, I'm using the .23 based cs kernel without issues.
- Update Android 12 Stable - 1.4.2 -​
CleanSlate asus sources update
-- sources updated to 2050.29
-- Hosts file for KAdaway
Two types of installation methods provided.
- One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM)
- One fastboot ZIP for solely fastboot based from command line with an example linux script to flash, for those who don't want to use Magisk. Be aware that if you flash by this fastboot method, vendor_dlkm flashing works, but will downsize the vendor_dlkm partition. So if you want to flash other kernels in rooted kernel flasher apps, you need to go to fastbootd, flash a stock vendor_dlkm.img (and then also flash in fastboot stock boot/vendor_boot/dtbo for a bootable state) to get back to the stock sized partition and then only after that you can flash AK3 installer zips.
CleanSlate S 1.4.2 Downloads:
Rooted installer zip:
CleanSlate S 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840957
Non rooted, Android S images for fastboot based flashing (firmware wwe 31.2050.2050.29)
fastboot image zip CS 1.4.2: https://www.androidfilehost.com/?fid=14871746926876840958
Read first post in thread for installation details.
Is there any way to add vowifi or volte without rooting with a kernel like this?
Hello,
I recently buy this phone and wanted to increase the battery life of this phone.
This seem to be an good option, but have you information about battery life with this kernel ?
Thanks you.
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
dragonii said:
Hi,
I don't know what I'm doing wrong but got into quite a bit of bootloops trying to install it, the non-rooted version.
Started by installing the files in the last post directly when in fastboot. This resulted in this message, followed by a bootloop at the ASUS logo :
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
Then, to get out of it, downloaded the ASUS official image, uncompressed the individual files and flashed some of them according to an Internet post, which solved my problem and then the phone could boot again normally.
Then, I decided to flash the cleanstate img file in the first post, followed by the files in the last post, using the sequence described in the bash file. Again, bootloop! Resolved it this time by flashing the same cleanstate img file only and leave at that.
After OS booting, I see that the kernel is definetly there and it seems that ads are being blocked (my main reason to install it).
The kernel version is 5.10.81-cleanstate-100-android12-9.
So, my question is : what did I do wrong and what is the purpose of the new files since they no longer contain a cleanstate img file in the zip file?
Thanks in advance,
Click to expand...
Click to collapse
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
tbalden said:
Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img.
Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there.
The commands to do are:
Code:
adb reboot-bootloader
fastboot flash boot full_img/boot.img
fastboot flash vendor_boot full_img/vendor_boot.img
fastboot flash dtbo full_img/dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm full_img/vendor_dlkm.img
fastboot reboot
Click to expand...
Click to collapse
So, according to you, I should just take the latest zip file and run the commands in fastboot mode even if I flashed already the cleanstate img file in the first post?
EDIT: did it already and no more error messages with version 1.4.2. Thanks !
Hi again,
How can I access these features? There are not showing up in the CleanSlate Configuration tool.
-- New:
---- Flashlight notifications
---- Vibrating Notifications reminder
---- Gestures Features: Sweep/Tap in corner gestures added
---- Fingerpint customization added:
----- FP: Possibility to let 4 types of Fingerpint event types to be mapped by third party mapper apps like Button Mapper
----- FP Possibility to set a Double tap to sleep mode on Fingerpint sensor (with possibility of keeping swipe up / down stock feature enabled/working)
---- Double Vibration feature on Phone Calls in DND or Silent mode
Thanks in advance,

Categories

Resources