[Script] Kernel Manager for X10 {NO LONGER SUPPORTED} - XPERIA X10 Android Development

< ANNOUNCEMENTS >
these scripts are no longer supported as we plan to make app for this
</ ANNOUNCEMENTS >
PLEASE DO NOT RUSH TO TEST THIS,
PLEASE READ THIS COMPLETE POST TILL THE END AND ONLY THEN USE THE FILES PROVIDED IN 2ND POST.
PLEASE MAKE A NANDROID/RECOVERY BACKUP OF UR CURRENT ROM. AND MAKE SURE THAT U CAN USE FLASHTOOL TO FLASH STOCK SE FW IF THE OS FAILS TO BOOT (IF U R STUCK AT SE TEXT LOGO)
PLEASE READ THE WARNING POSTED TOWARDS THE END OF THIS POST
This Kernel Manager will provide a slight easier way to test/use/switch between custom kernels available for X10... This is as of now its based off GScript (need help from others if it has to become an app)... its basically a bunch of shell scripts... which can be executed to get the desired Kernel Manager
MANY thanks to jerpelea, zdzihu, Bin4ry, Androxyde & others involved in creating custom recovery for X10, FreeXperia Project & developing custom kernels
Thank you anantshri for helping out during testing phase.
Thanks to everyone who tested out v1.0 and provided invaluable feedback/comments/suggestion... Thank you very much...
DIFFICULTY: MEDIUM
Requirements
for using custom kernels u will need to be on baseband 2.0.xx (2.0.52 preferred)... you can download it from BaseBand Collection...
froyo users (who have roms ment for basebands 2.1.5x) can use Base Band Patch for 2.2 roms...
Any working recovery
Features:
Single chargemon script for:
Reboot into recovery
Boot custom kernel at next bootup
Boot stock/custom kernel as default
Slightly elegant way (in my opinion) of selecting custom kernels
Tried my best to keep it as backward compatible with existing scripts as possible
Ability to take backup of stock modules of current ROM
All files will be having LOTS of log capability so that error/bug hunting can be easier
System mounts will be handled more securely and after required operations are complete the system will be remounted to original state
Backup of current chargemon will be taken which can be restored later so as to not disturb current recovery
Included FreeXperia recovery into the kernelmanager package (Thank you jerpelea & zdzihu for ur work on custom recovery)
Some Busybox binaries included in kernelmanager package (this will not interfere with the current busybox on ur current ROM)
This is currently based on shell scripts. There are three types of scripts which are executed:
[Type 1] Some scripts are executed during flashing update.zip
[Type 2] Some shell scripts are executed during bootup (by chargemon)
[Type 3] Others will have to be executed by user.
U will need GScript to be able to use user-executable Kernel Manager scripts. I have not included GScript in package because I found that there can be an issue if GScript gets overwritten. So u can install GScript Lite from market (or download from here). The scripts which require user-interaction and the files which need to be run from OS will be saved in /sdcard/gscript folder.
The files which need to be run from android OS:
backup_stock.sh
DEPRECATED FUNCTION. NO NEED TO RUN THIS.
restore_stock.sh
This program restores the stock modules of current rom. Before running this script make sure that u switch off WIFI/BT. Once restore is complete reboot the device to see if changes worked.
set_default_stock.sh
This sets a flag (/system/kernel/defaultstock) so that STOCK kernel is booted by default and all custom kernel flags are removed.
set_default_custom.sh
This sets a flag (/data/local/tmp/defaultcustom) so that CUSTOM kernel is booted by default and all other flags are removed.
set_test_custom.sh
This sets a flag (/data/local/tmp/kexecboot & /data/local/tmp/defaultcustom) so that CUSTOM kernel is booted ONLY ONCE during NEXT bootup and all other flags are removed. After subsequent reboots the stock kernel will be selected by default.
select_KERNELNAME.sh
This file will be provided in each custom kernel package and will write the name of the folder containing the custom kernel files to /data/local/tmp/selectedkernel
There will also be a “identifier” file in each kernel package which will be displayed to the user.
check_current_kernel.sh
This program is ment to show the currently selected kernel. But for some odd reason it doesn’t show the intended info.
reboot_recovery.sh
This program is ment to reboot the device into recovery.
uninstall_km.sh
This program marks a flag "/data/local/tmp/uninstall_km" which will be read by kernelmanager on next reboot and will restores the stock modules & original chargemon of current rom. Once restore is complete during next bootup the device will automatically reboot (this is expected). Then please see if everything is restored back to stock. For now this will NOT DELETE KERNELMANAGER files.
Add these files into GScript:
just launch the app
click on "Load File" and select each script, all the contents will load automatically
u need to make sure that the option "Need SU?" is checked (ticked)
now save
if u try running the script a popup for SU permissions might come up, this will only come the first time its run, select "Allow"
Short HOW-TO:
Reboot into recovery
Flash KM_v1.1_install.zip
Reboot device
Add all the files into GScript as mentioned above
NOW select the kernel u want to test select_KERNELNAME. the device wont reboot.
U can now select if u want to just test the custom kernel out set_test_custom.sh or want to set custom kernel as default set_default_custom.sh. the device wont reboot.
Once these programs are executed now u can reboot device and enjoy custom kernels
If u want to go back to stock kernel for the current ROM u can just select set_default_custom.sh and stock kernel for the current ROM will be booted on next reboot
If u want to switch kernels just select the kernel u want to use select_KERNELNAME
U can always flash KM_v1.1_restoremodules.zip if u face any problems like installer update.zip did not flash properly / u are stuck at SE text logo (ramdisk related) / facing contant system FC/crashes (ramdisk related)
If u had any problems using kernel manager just pull the log files via ADB shell:
Code:
adb pull /system/kernelmanager/log/ .
adb pull /data/local/tmp/km_log/ .
after which u can flash uninstaller update.zip to return to ur default chargemon & recovery... also it would be helpful if u can post the log files here so that i can look into wht the problem was exactly...
Logs saved at:
/system/kernelmanager/log/ for [Type 1]
/data/local/tmp/km_log/ for [Type 2] & [Type 3]
All filenames of logs will start with km_log_
So if u run into any problems please get the log files from the above directory and post them here.
WARNINGS:
Only those files which are provided here (including kernel packages) will be supported
I have used the miniloader provided in the latest kernels, this version does not print out any on screen text. I am aware that some users are having an issue with using this version of miniloader. A hotfix package released check POST #2.
If ur current rom does not require default custom kernel then please delete /system/kernel folder before flashing installer update.zip
IMPORTANT for CM7 users / users who have ROMs which uses custom kernel as default booting option. PLEASE use v1.1 which is compatible for u guys. also NO NEED TO DELETE /system/kernel/
To-do:
move kernel files to SDCARD
Md5 checker for files before copying to /system
Ideas for future:
Create some sort of framework which will allow to store all currently available custom kernels centrally (may be on some central server), so that the users can download them to their devices as required
APP for this
If we can integrate it into Recovery as an option
Or can be launched (some sort of text interface) via Recovery as an update.zip (something like the interface used by OpenRecovery available for Moto Droid/Milestone)
PLANNED FUTURE WORK
also at this point i would like to disclose some interesting news to everyone...
we.. DooMLoRD, MrHassell, Chumby_666, kxhawkins are working to create an amazing thing for our X10 based on this... basically we are planning to create an APP for this AND CUSTOMIZED RECOVERY WITH KERNEL MANAGER INTEGRATED so that u can select custom kernels right from recovery [no need to keep flashing zips ]
THANK YOU ZDZIHU FOR RELEASING THE XRECOVERY SOURCES
MrHassell is planning to work out android APP related aspects
Chumby_666 & kxhawkins are planning to work out recovery menu integration aspects...
i will help them out whichever way i can...
Downloads are provided in POST #2 (below)...

---

Release & sources / codes
Releases:
[14-May-2011] Kernel Manager v1.1 additional kernels set2 released
[13-May-2011] Kernel Manager v1.1 released
[11-May-2011] Kernel Manager v1.0 additional kernels set2 released
[09-May-2011] Kernel Manager v1.0 released
[30-Apr-2011] test release v0.1 (with required folder structure) [FOR DEVS ONLY] (check attachment)
Kernel Manager v1.1 additional kernels set2
Release Notes:
There is one update.zip
KM_v1.1_kernels_set2.zip
For additional testing I am providing 2 more kernels:
FreeXperia Kernel-007 / beta7 [FXK_K007_J]
FreeXperia Kernel-009 / beta9 [FXK_K009_J]
FreeXperia Kernel-010 / beta10 [FXK_K010_J]
The associated modules (wifi.ko / ar6000.ko) are also provided in the included package
Downloads (check Post #2)
Kernel Manager v1.1
Release Notes:
There are three update.zips which are provided
KM_v1.1_install.zip (installer update.zip)
KM_v1.1_restoremodules.zip (emergency restore update.zip)
KM_v1.1_uninstall.zip (un-installer update.zip)
For the sake of testing I will be providing only 3 kernels:
FreeXperia Kernel-001 [FXK_K001_J]
FreeXperia Kernel-006 / beta6 [FXK_K006_J]
TripNKernel Modified FreeKernel-03 based on zdzihu's FreeKernel [TK_FK_B3_Z_T]
The associated modules (wifi.ko / ar6000.ko) are also provided in the included package
This version should be compatible with all roms
no more mounting/remounting for user-executed scripts (gscripts)
if u have used v1.0 before flashing u will have to manually remove each script which u had initially loaded from v1.0 in GScript
If ur current rom does not require default custom kernel then please delete /system/kernel folder before flashing installer update.zip
u can always flash KM_v1.1_restoremodules.zip if u face any problems like installer update.zip did not flash properly / u are stuck at SE text logo (ramdisk related) / facing contant system FC/crashes (ramdisk related)
Details (check 1st post)
Kernel Manager v1.0
Release Notes:
There are two update.zips which are included
KM_v1.0_install.zip (installer update.zip)
KM_v1.0_uninstall.zip (un-installer update.zip)
For the sake of testing I will be providing only 3 kernels for testing:
FreeXperia Kernel-001 [FXK_K001_J]
FreeXperia Kernel-006 / beta6 [FXK_K006_J]
TripNKernel Modified FreeKernel-03 based on zdzihu's FreeKernel [TK_FK_B3_Z_T]
The associated modules (wifi.ko / ar6000.ko) are also provided in the included package
Details (check 1st post)
Kernel Manager v1.0 additional kernels set2
Release Notes:
There is one update.zip
KM_v1.0_kernels_set2.zip
For additional testing I am providing 2 more kernels:
FreeXperia Kernel-007 / beta7 [FXK_K007_J]
FreeXperia Kernel-009 / beta9 [FXK_K009_J]
The associated modules (wifi.ko / ar6000.ko) are also provided in the included package
Downloads (check Post #2)
DOWNLOADS
RELEASES
Kernel Manager v1.0
KM_v1.0_install.zip
KM_v1.0_uninstall.zip
Kernel Manager v1.1
KM_v1.1_install.zip
KM_v1.1_restoremodules.zip
KM_v1.1_uninstall.zip
ADDITIONAL KERNELS
Kernel Manager v1.0 Kernels Set 2
KM_v1.0_kernels_set2.zip
Kernel Manager v1.1 Kernels Set 2
KM_v1.1_kernels_set2.zip
HOTFIX
miniloader version issue:
There seems to be some issues face by some users, where in using an older version of miniloader helped them sort out the issues. So I will provide here both versions.
Flashable update.zip via recovery, contains miniloader & splboot.ko:
bootloader_bypass_files_v1.zip [newest miniloader] (recommended)
bootloader_bypass_files_v2.zip [older miniloader] (testing only)
WiFi fix for Froyo
on Froyo ROM if u are getting wifi error on kernel 009/010 then u can use the wifi_bt_fix-fxk_froyo_v01.1.zip : patch module from: [PATCH] Fix WiFi and BT for FreeXperia Kernel (froyo)
U NEED TO FLASH wifi_bt_fix-fxk_froyo_v01.1.zip ONLY

---

here it is

---

nicework buddy...
however i would stilll like to have some kind of grub like interface..
i.e a interface with some kind of a timer and when timer reached load default option whatever that may be othewise use up and down vol key for navigation or any other key and allow user to select kernel or recovery etc options

---

anantshri said:
nicework buddy...
however i would stilll like to have some kind of grub like interface..
i.e a interface with some kind of a timer and when timer reached load default option whatever that may be othewise use up and down vol key for navigation or any other key and allow user to select kernel or recovery etc options
Click to expand...
Click to collapse
I second the grub dos interface.
Still very awesome work dude.

---

anantshri said:
nicework buddy...
however i would stilll like to have some kind of grub like interface..
i.e a interface with some kind of a timer and when timer reached load default option whatever that may be othewise use up and down vol key for navigation or any other key and allow user to select kernel or recovery etc options
Click to expand...
Click to collapse
hey buddy that wht i am thinking of exactly!!
>>
If we can integrate it into Recovery as an option
Or can be launched (some sort of text interface) via Recovery as an update.zip (something like the interface used by OpenRecovery available for Moto Droid/Milestone)
<<

---

UPDATE
Sources & codes released in 2nd post
test release v0.1 (FOR DEVS ONLY)

---

Excellent!
I've got an X10 again So.. now I'm ready when you are, should we integrate with xCharge?

---

Hey bro, not sure if you knew this already or if it works the same way but there is already a kernel manager app out there that relies on user/dev uploaded kernels and populates the app off a web server (similar to ROM Manager, i believe its the same dev?)..
take a look, maybe it will help your progress?...
https://market.android.com/details?id=com.teamwin.kernelmanager&feature=search_result
Theres also a free version.

---

BULL3TPR00F said:
Hey bro, not sure if you knew this already or if it works the same way but there is already a kernel manager app out there that relies on user/dev uploaded kernels and populates the app off a web server (similar to ROM Manager, i believe its the same dev?)..
take a look, maybe it will help your progress?...
https://market.android.com/details?id=com.teamwin.kernelmanager&feature=search_result
Theres also a free version.
Click to expand...
Click to collapse
hey BULL3TPR00F,
those apps are ment for users who have unlocked/cracked bootloaders... X10 uses a unique way to load custom kernels (kexec/splboot) so those apps wont be of any use to us...

---

yeah im aware that the x10 has to bypass the bootloader, but i didnt know that app requires a cracked bootloader.
thanks for the info. keep up the great work

---

BULL3TPR00F said:
yeah im aware that the x10 has to bypass the bootloader, but i didnt know that app requires a cracked bootloader.
thanks for the info. keep up the great work
Click to expand...
Click to collapse
well actually most of these app write the boot.img to boot partition...
this is from one of the custom kernels ment for Nexus One [i was trying to make it run for our devices but thats a story for some other time.... ]
Code:
write_raw_image("/tmp/boot.img", "boot");
since we are not able to write to that boot partition (yet) we cant use them...

---

i love how you devs always say: we're unable to (yet), gives me great hope keep up the good work!

---

THANK YOU anantshri
guys we were finally able to figure out wht the issue was...
it was all related to using a wrong windows text editor (difference between WIN/LINUX characters)
finally got the problematic scripts to work....
i will be able to complete these scripts soon...
once again THANK YOU anantshri

---

Doom, any news here?
Sent from my X10i using XDA Premium App

---

Doom just wanted to let you know in public venue that your work... threads ... and help to others is well above most...
Thanks
Sent from my X10project using XDA App

---

anders260 said:
Doom, any news here?
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
hi anders260... v0.2 is ready and is being tested by me... will release it soon for public testing...
will provide 3 custom kernels (Z's FreeKernel, J's FreeXperia Kernel k006, T's modified kernel) for this phase of testing...
all files will be having LOTS of log capability so that error/bug hunting can be easier...
system mounts will be handled more securely and after required operations are complete the system will be remounted to original state...
will be including FreeXperia recovery into the kernelmanager package so as to not disturb current recovery...
backup of current chargemon will be taken which can be restored later...
option to take backup of current ROMs stock modules...
a little glimpse of wht to expect...
Code:
#
# DooMLoRD: Kernel Manager for X10 (v0.2)
# FILE: activate_kernel.sh
#
echo
echo "---[START PROGRAM]---"
# defining VARS
KERNELNAME="FK_A1_Z"
PROGNAME="activate_kernel"
LOGFILENAME="km_log_$PROGNAME_$KERNELNAME.txt"
LOGFILEPATH="/data/local/tmp/$LOGFILENAME"
KMPATH="/system/kernelmanager"
KERNELPATH="$KMPATH/kernel_files/$KERNELNAME"
# removing log file
if [ -e $LOGFILEPATH ]
then
rm $LOGFILEPATH
fi
echo
echo "PROGRAM NAME: $PROGNAME"
echo "-----[START LOG]-----" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "PROGRAM NAME: $PROGNAME" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
date >> $LOGFILEPATH 2>> $LOGFILEPATH
# mount/remount commands
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< MOUNT / REMOUNT >>"
echo "<< MOUNT / REMOUNT >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
CURMNT=`mount | busybox grep /system | busybox awk '{print $4}'`
# Checking current system mount mode and remounting as RW if required
echo "Checking current system mount mode and remounting as RW if required" >> $LOGFILEPATH 2>> $LOGFILEPATH
case $CURMNT in
rw*)
echo "System mounted as RW" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
ro*)
echo "System mounted as RO" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "then system will be remounted as RW" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount -o remount,rw -t yaffs2 `mount | busybox grep /system | busybox awk '{print $1}'` /system >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
esac
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# DOING SOME WORK
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< ACTIVATING CUSTOM KERNEL: $KERNELNAME >>"
echo "<< ACTIVATING CUSTOM KERNEL: $KERNELNAME >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING FILES TO SYSTEM"
echo "COPYING FILES TO SYSTEM" >> $LOGFILEPATH 2>> $LOGFILEPATH
#echo "COPYING ALL FILES" >> $LOGFILEPATH 2>> $LOGFILEPATH
#cp -r -p $KERNELPATH/system/* /system/. >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING boot.img" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/system/kernel/boot.img /system/kernel/boot.img >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING wifi.ko" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/system/lib/modules/wifi.ko /system/lib/modules/wifi.ko >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Fixing permissions" >> $LOGFILEPATH 2>> $LOGFILEPATH
busybox chmod 644 /system/lib/modules/wifi.ko >> $LOGFILEPATH 2>> $LOGFILEPATH
busybox chmod 644 /system/kernel/boot.img >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING IDENTIFIER"
echo "COPYING IDENTIFIER" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/identifier /system/kernel/identifier >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# mount/remount commands
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< MOUNT / REMOUNT >>"
echo "<< MOUNT / REMOUNT >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# remounting system to ORIGINAL mount mode
echo "remounting system to ORIGINAL mount mode" >> $LOGFILEPATH 2>> $LOGFILEPATH
case $CURMNT in
rw*)
echo "System was already mounted as RW... Nothing to do..." >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
ro*)
echo "Remounting system as RO" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Remounting System" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount -o remount,ro -t yaffs2 `mount | busybox grep /system | busybox awk '{print $1}'` /system >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
esac
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "-----[DONE LOG]-----" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "---[DONE PROGRAM]---"
echo
echo "LOG file at: $LOGFILEPATH"
echo
echo
echo "DISPLAYING LOG"
echo
cat $LOGFILEPATH
echo
rdannar said:
Doom just wanted to let you know in public venue that your work... threads ... and help to others is well above most...
Thanks
Sent from my X10project using XDA App
Click to expand...
Click to collapse
thank you rdannar!

---

Hi DooM,
One simple trick which i was trying to remember nothing big but will save some time and space too.
echo "Hello" >> $LOG 2>&1
this will log both stdout and stderr on same file. $LOG.
hope this helps.
and ya i am also waiting to test this kernel manager.
EDIT : Sorry for top post
DooMLoRD said:
hi anders260... v0.2 is ready and is being tested by me... will release it soon for public testing...
will provide 3 custom kernels (Z's FreeKernel, J's FreeXperia Kernel k006, T's modified kernel) for this phase of testing...
all files will be having LOTS of log capability so that error/bug hunting can be easier...
system mounts will be handled more securely and after required operations are complete the system will be remounted to original state...
will be including FreeXperia recovery into the kernelmanager package so as to not disturb current recovery...
backup of current chargemon will be taken which can be restored later...
option to take backup of current ROMs stock modules...
a little glimpse of wht to expect...
Code:
#
# DooMLoRD: Kernel Manager for X10 (v0.2)
# FILE: activate_kernel.sh
#
echo
echo "---[START PROGRAM]---"
# defining VARS
KERNELNAME="FK_A1_Z"
PROGNAME="activate_kernel"
LOGFILENAME="km_log_$PROGNAME_$KERNELNAME.txt"
LOGFILEPATH="/data/local/tmp/$LOGFILENAME"
KMPATH="/system/kernelmanager"
KERNELPATH="$KMPATH/kernel_files/$KERNELNAME"
# removing log file
if [ -e $LOGFILEPATH ]
then
rm $LOGFILEPATH
fi
echo
echo "PROGRAM NAME: $PROGNAME"
echo "-----[START LOG]-----" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "PROGRAM NAME: $PROGNAME" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
date >> $LOGFILEPATH 2>> $LOGFILEPATH
# mount/remount commands
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< MOUNT / REMOUNT >>"
echo "<< MOUNT / REMOUNT >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
CURMNT=`mount | busybox grep /system | busybox awk '{print $4}'`
# Checking current system mount mode and remounting as RW if required
echo "Checking current system mount mode and remounting as RW if required" >> $LOGFILEPATH 2>> $LOGFILEPATH
case $CURMNT in
rw*)
echo "System mounted as RW" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
ro*)
echo "System mounted as RO" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "then system will be remounted as RW" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount -o remount,rw -t yaffs2 `mount | busybox grep /system | busybox awk '{print $1}'` /system >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
esac
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# DOING SOME WORK
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< ACTIVATING CUSTOM KERNEL: $KERNELNAME >>"
echo "<< ACTIVATING CUSTOM KERNEL: $KERNELNAME >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING FILES TO SYSTEM"
echo "COPYING FILES TO SYSTEM" >> $LOGFILEPATH 2>> $LOGFILEPATH
#echo "COPYING ALL FILES" >> $LOGFILEPATH 2>> $LOGFILEPATH
#cp -r -p $KERNELPATH/system/* /system/. >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING boot.img" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/system/kernel/boot.img /system/kernel/boot.img >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING wifi.ko" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/system/lib/modules/wifi.ko /system/lib/modules/wifi.ko >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Fixing permissions" >> $LOGFILEPATH 2>> $LOGFILEPATH
busybox chmod 644 /system/lib/modules/wifi.ko >> $LOGFILEPATH 2>> $LOGFILEPATH
busybox chmod 644 /system/kernel/boot.img >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "COPYING IDENTIFIER"
echo "COPYING IDENTIFIER" >> $LOGFILEPATH 2>> $LOGFILEPATH
cp -p $KERNELPATH/identifier /system/kernel/identifier >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# mount/remount commands
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "<< MOUNT / REMOUNT >>"
echo "<< MOUNT / REMOUNT >>" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
# remounting system to ORIGINAL mount mode
echo "remounting system to ORIGINAL mount mode" >> $LOGFILEPATH 2>> $LOGFILEPATH
case $CURMNT in
rw*)
echo "System was already mounted as RW... Nothing to do..." >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
ro*)
echo "Remounting system as RO" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Remounting System" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount -o remount,ro -t yaffs2 `mount | busybox grep /system | busybox awk '{print $1}'` /system >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "Checking System mount state" >> $LOGFILEPATH 2>> $LOGFILEPATH
mount | busybox grep /system | busybox awk '{print $4}' >> $LOGFILEPATH 2>> $LOGFILEPATH
;;
esac
echo >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "-----[DONE LOG]-----" >> $LOGFILEPATH 2>> $LOGFILEPATH
echo "---[DONE PROGRAM]---"
echo
echo "LOG file at: $LOGFILEPATH"
echo
echo
echo "DISPLAYING LOG"
echo
cat $LOGFILEPATH
echo
thank you rdannar!
Click to expand...
Click to collapse

---

anantshri said:
Hi DooM,
One simple trick which i was trying to remember nothing big but will save some time and space too.
echo "Hello" >> $LOG 2>&1
this will log both stdout and stderr on same file. $LOG.
hope this helps.
and ya i am also waiting to test this kernel manager.
EDIT : Sorry for top post
Click to expand...
Click to collapse
hey thanx Anant...
i will include that in future versions...
right now busy testing v0.2

---

Great news!!!
GREAT NEWS!!!
hello my friends i have some great news for eveyone!!!!
Kernel Manager for X10 is v1.0 NOW and will be RELEASED SHORTLY
after 15 days of trying to make this work i am proud to say that its finally complete!!!
i have personally tested this over the weekend and let me tell u this is going to make our lives so easy for changing custom kernels/associated files!!!
i will be releasing this soon... have been awake all night, need some sleep, and have to prepare "readme"
PLANNED FUTURE WORK
also at this point i would like to disclose some interesting news to everyone...
we.. DooMLoRD, MrHassell, Chumby_666, kxhawkins are working to create an amazing thing for our X10 based on this... basically we are planning to create an APP for this AND CUSTOMIZED RECOVERY WITH KERNEL MANAGER INTEGRATED so that u can select custom kernels right from recovery [no need to keep flashing zips ]
THANK YOU ZDZIHU FOR RELEASING THE XRECOVERY SOURCES
MrHassell is planning to work out android APP related aspects
Chumby_666 & kxhawkins are planning to work out recovery menu integration aspects...
i will help them out whichever way i can...