Welcome to the Eternity Project's Olympus CWM Kernel Flasher with AUTO Tegrapart recognizer Thread!
What's it?
It is inspired by the idea that koush had with AnyKernel. It is intended for use only for devs. It will copy the CMDLINE of your device and assemble a boot.img with your own cmdline, so you can use the same package for deploying kernels to all different tegrapart devices.
What will it do and how much time will it take
It will take the current device's cmdline and assemble the bootimg. The required files has to be named "eternityImage" (kernel image) and "eternityrd.gz" (ramdisk/initrd).
The process of taking the cmdline and assembling the new bootimg will be done almost instantly. It should take like 0.2 seconds.
What I need
- A PC
- A kernel zImage
- A RamDisk
- Eventually a WiFi module
- A BRAIN
What does it contain:
- Scripts and files that needs to be executed
- Nothing else.
The funny part
Those are the scripts used by the KernelFlasher package. You can modify them (especially the update-script) as you want. Just remember to add credits
Creating the boot image:
Code:
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/eternityImage --ramdisk /tmp/eternityrd.gz --cmdline \"$(cat /proc/cmdline)\" --output /tmp/eternityprj.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Recovery update-script
Code:
ui_print(" ");
ui_print("Eternity Project for Motorola Olympus: ATRIX");
ui_print(" ");
ui_print(" ll ll ll ll ll");
ui_print("E ll ll ll ll ll");
ui_print("T ll ll ll ll ll");
ui_print("E oooooooooooooo ");
ui_print("R lllllloooooooooooooollllll");
ui_print("N lllllloooooooooooooollllll");
ui_print("I oooooAP20ooooo ");
ui_print("T lllllloooooooooooooollllll");
ui_print("Y lllllloooooooooooooollllll");
ui_print("P oooooooooooooo ");
ui_print("R ll ll ll ll ll");
ui_print("J ll ll ll ll ll");
ui_print(" ll ll ll ll ll");
ui_print(" ");
ui_print("Update contains: Kernel+Modules");
ui_print("Developed by kholk");
set_progress(1.000000);
ui_print("Converting SYSTEM to EXT4");
run_program("/sbin/tune2fs" , "-O" , "extents,uninit_bg,dir_index" , "/dev/block/mmcblk0p12");
ui_print("Running FSCK...");
run_program("/sbin/e2fsck" , "-pf" , "/dev/block/mmcblk0p12");
ui_print("Extracting Modules...");
mount("ext4" , "EMMC" , "/dev/block/mmcblk0p12" , "/system");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Extracting Kernel Files...");
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
ui_print("Detecting your ATRIX CMDLINE...");
run_program("/tmp/mkbootimg.sh");
ui_print("Detected! Custom EternityProject Kernel created.");
ui_print("Erasing Boot Partition...");
run_program("/sbin/busybox", "dd", "if=/dev/zero", "of=/dev/block/mmcblk0p11");
ui_print("Writing Boot Image...");
run_program("/sbin/busybox", "dd", "if=/tmp/eternityprj.img", "of=/dev/block/mmcblk0p11");
ui_print("All done.");
ui_print("Remember to check for updates frequently!");
ui_print("Enjoy!");
Download
MegaUpload
The Eternity Project Developer,
-kholk
Cool! Now to find out what it does...
wirednix said:
Cool! Now to find out what it does...
Click to expand...
Click to collapse
According to the Eternity Project Kernel thread this appears to be an automated way to determine the correct kernel for AT&T or international, or other Tegra options. It is intended so that devs can release a single package and take user error out of the equation for some releases.
wirednix said:
Cool! Now to find out what it does...
Click to expand...
Click to collapse
kholk said:
What will it do and how much time will it take
It will take the current device's cmdline and assemble the bootimg. The required files has to be named "eternityImage" (kernel image) and "eternityrd.gz" (ramdisk/initrd).
The process of taking the cmdline and assembling the new bootimg will be done almost instantly. It should take like 0.2 seconds.
Click to expand...
Click to collapse
Emh...........
Related
I'm attempting to make an install script for a couple of mods just as before on the Droid X. Unfortunately I'm getting different errors at different times. One of the errors is (Status 0)... and the other is (Status 6).
Also, Mount says that it expects 4 args, got 3.
What changed?
nitro66215 said:
I'm attempting to make an install script for a couple of mods just as before on the Droid X. Unfortunately I'm getting different errors at different times. One of the errors is (Status 0)... and the other is (Status 6).
Also, Mount says that it expects 4 args, got 3.
What changed?
Click to expand...
Click to collapse
You need to use the right Syntax to mount /system . Best way... Busybox.
run program("/sbin/busybox" , "mount", "/system");
DroidTh3ory said:
You need to use the right Syntax to mount /system . Best way... Busybox.
run program("/sbin/busybox" , "mount", "/system");
Click to expand...
Click to collapse
So... I've tried this.... and I get....
Error in /sdcard/update.zip
(Status 6)
For Shi*s and giggles... I just did a test script.
ui_print(" ");
ui_print("Mount Bionic Script...");
run_program("/sbin/busybox", "mount", "/system");
ui_print("Doing Something.......");
ui_print("Installing Files");
ui_print(" ");
ui_print("** Unmounting System **");
unmount("/system");
This errors out. I have the META-INF folder from another Bionic update that someone else created, so I'm assuming that the files within (other than the script) will work as is.
Here is my mod script and update-binary. Make the appropriate folders for your mod and give it a go.
Case and spacing is essential as I am sure you know.
3G ICON VISUAL FIX
DroidTh3ory said:
Here is my mod script and update-binary. Make the appropriate folders for your mod and give it a go.
Case and spacing is essential as I am sure you know.
3G ICON VISUAL FIX
Click to expand...
Click to collapse
ui_print(" ");
show_progress(0.800000, 35);
ui_print(" ");
ui_print("** Mounting this ***** **");
run_program("/sbin/busybox", "mount", "/system");
ui_print(" ");
ui_print("** Installing Your MOD **");
ui_print(" ");
ui_print("** Unmounting System, Rock Out!! **");
unmount("/system");
show_progress(0.050000,0);
Ugh... same error. I only deleted your package extract. I'm using 7-zip and just doing store. Is that still the preferred method?
nitro66215 said:
ui_print(" ");
show_progress(0.800000, 35);
ui_print(" ");
ui_print("** Mounting this ***** **");
run_program("/sbin/busybox", "mount", "/system");
ui_print(" ");
ui_print("** Installing Your MOD **");
ui_print(" ");
ui_print("** Unmounting System, Rock Out!! **");
unmount("/system");
show_progress(0.050000,0);
Ugh... same error. I only deleted your package extract. I'm using 7-zip and just doing store. Is that still the preferred method?
Click to expand...
Click to collapse
What is it installing if there is no package extract?
I don't use 7zip, I just compress in linux... Couldn't really say in that.
DroidTh3ory said:
What is it installing if there is no package extract?
I don't use 7zip, I just compress in linux... Couldn't really say in that.
Click to expand...
Click to collapse
I plan on doing the install later, but I just wanted to do a test script without install. Just some "Hello World" text to make sure I got something going on.
I even just did that....
ui_print("Hello World");
Gave me the same error!
Ok.... so.... It is now working after a reboot of Recovery. Don't ask me why. And I am using standard windows zipping.
I've created the template needed for Dsixda's kitchen, rename (remove .txt) the attached file to m7wls & place in the \kitchen\tools\edify_defs folder
[KITCHEN] Android Kitchen, v0.223 [Linux / Mac / Windows]
one thing I should point out....using the latest TWRP, a ROM created w/ this kitchen will not flash. You will need to replace the update-binary in \META-INF\com\google\android. See the attached file (remove the .zip).
also, you'll want to update the updater-script to replace the format /system cmd to:
format("ext4", "EMMC", "/dev/block/mmcblk0p37", "0", "/system");
...
FIRST!! Thanks bro
O.M.J said:
I've created the template needed for Dsixda's kitchen, rename (remove .txt) the attached file to m7wls & place in the \kitchen\tools\edify_defs folder
[KITCHEN] Android Kitchen, v0.223 [Linux / Mac / Windows]
...
Click to expand...
Click to collapse
Thank you!
O.M.J said:
I've created the template needed for Dsixda's kitchen, rename (remove .txt) the attached file to m7wls & place in the \kitchen\tools\edify_defs folder
[KITCHEN] Android Kitchen, v0.223 [Linux / Mac / Windows]
...
Click to expand...
Click to collapse
This might be a stupid question... but since i havent used a kitchen since my htc diamond days i figured i would ask. Are kernels compiled from binaries in the kitchen or is it more like the old school kitchens where you just pick the options.
sybe said:
This might be a stupid question... but since i havent used a kitchen since my htc diamond days i figured i would ask. Are kernels compiled from binaries in the kitchen or is it more like the old school kitchens where you just pick the options.
Click to expand...
Click to collapse
You cant compile the kernel with the kitchen, You can make some changes to the ramdisk and swap out the zimage.
Thanks for this man! :thumbup:
Sent from my HTCONE using Tapatalk 2
Hi to ALL
i m yamil
i use dsixda kitchen to cook a rom for one sprint but.. users reported Recovery fail..
i let here my updater script, it has no aroma, if somebody can help me will be great
Here is link of my script http://d-h.st/M0f
Thanks in advance
dragonesdenano said:
Hi to ALL
i m yamil
i use dsixda kitchen to cook a rom for one sprint but.. users reported Recovery fail..
i let here my updater script, it has no aroma, if somebody can help me will be great
Here is link of my script http://d-h.st/M0f
Thanks in advance
Click to expand...
Click to collapse
Have you added the HTC ONE template OMJ posted the the kitchen?
It should look like this
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p39", "/data");
package_extract_dir("data", "/data");
format("ext4", "EMMC", "/dev/block/mmcblk0p37", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
You dont this. Delete that file/folder from the zip
Code:
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
Add these lines to fix the Paid app issue in the playstore
Code:
symlink("/system/lib/modules/moc_crypto.ko.3.4.10","/system/lib/modules/moc_crypto.ko");
symlink("/system/lib/modules/moc_platform_mod.ko.3.4.10","/system/lib/modules/moc_platform_mod.ko");
This will flash the boot.img , No need for the method your using
Code:
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p33");
delete("/tmp/boot.img");
benny3 said:
Have you added the HTC ONE template OMJ posted the the kitchen?
It should look like this
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p39", "/data");
package_extract_dir("data", "/data");
format("ext4", "EMMC", "/dev/block/mmcblk0p37", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system");
delete_recursive("/system");
package_extract_dir("system", "/system");
You dont this. Delete that file/folder from the zip
Code:
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
Add these lines to fix the Paid app issue in the playstore
Code:
symlink("/system/lib/modules/moc_crypto.ko.3.4.10","/system/lib/modules/moc_crypto.ko");
symlink("/system/lib/modules/moc_platform_mod.ko.3.4.10","/system/lib/modules/moc_platform_mod.ko");
This will flash the boot.img , No need for the method your using
Code:
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/sbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p33");
delete("/tmp/boot.img");
Click to expand...
Click to collapse
Thank you very much for the amazing help.
I did, i ve added to the kitchen.... Anyway will check all again.
Thanks again
SkyDragon© You Are Not Allow To Lick My Banner, Stay Away!
dragonesdenano said:
Thank you very much for the amazing help.
I did, i ve added to the kitchen.... Anyway will check all again.
Thanks again
SkyDragon© You Are Not Allow To Lick My Banner, Stay Away!
Click to expand...
Click to collapse
I hope that helped you out.
I'm adding this to the OP....
one thing I should point out....using the latest TWRP, a ROM created w/ this kitchen will not flash. You will need to replace the update-binary in \META-INF\com\google\android. See the attached file (remove the .zip).
also, you'll want to update the updater-script to replace the format /system cmd to:
format("ext4", "EMMC", "/dev/block/mmcblk0p37", "0", "/system");
Well I planned to build a kernel for S5830 from samsung msm 7x27-cm-11.0 source . I obtained the zImage successfully. Later on I used Koush's AnyKernelUpdate.zip.
1- I placed the zImage in the folder named Kernel in the AnyKernelUpdate.zip
2- Modified
Code:
mount("MTD", "system", "/system");
with
Code:
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
When I flash this zip from CWM it gives Installation aborted.
Any help?
Thanks in advance.
Anyone??
Aloha community,
after 3 years of using an iphone i switched back to android with a new shiny z3 compact aka aries.
while staying in touch with android by developing apps and rooting/flashing a few phone from friends i am a bit out of ideas when it comes to my new phone...
what i did so far:
rooted phone,
backed up ta-partition
opened bootloader
installed cwm-recoverey by doomlord
tried to flash cm 12 (edited update-script to allow 'aries') -> install aborts without error message
tried to flash cm 11 -> black screen after reboot need to refresh boot.img in fast boot and restore android from backup
tried aosp 5.0.2 -> works fine but no detection of SIM, Camera, no root... i will wait for the official release from sony.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Since i want to get rid of the whole sony bloatware (which is a pain to remove manually on the phone) and also don't want to do it every time i need to reboot + want to offer the opportunity to others to install a relatively clean rom i tried to make my own rom based on the cwm backup...
therefore i copied the boot.img from the backup + the extracted system.ext4.tar folder in a new folder.
I removed all apps i didn't want / added others
I copied the META-Inf from the DRM-resoter zip and edited the updates-script.
it now reads:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
ui_print(" ");
ui_print(" Deleting /system ");
ui_print(" ");
delete("/system/*");
ui_print(" ");
ui_print(" Extracting Files ");
ui_print(" ");
package_extract_dir("system", "/system");
ui_print(" ");
ui_print(" Setting Permissions ");
ui_print(" ");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm_recursive(0, 0, 0755, 0644, "/system/framework");
set_perm_recursive(0, 0, 0755, 0644, "/system/priv-app");
ui_print(" ");
ui_print(" Unmounting System ");
ui_print(" ");
unmount("/system");
ui_print("------------------------------------------");
ui_print(" Finished ");
ui_print("------------------------------------------");
i stored the folder as a zip and signed it. Now it should be a flashable rom...
when i try to install it with cwm recovery the installation aborts.
the Log says:
Code:
-- Installing: /storage/sdcard1/custom-signed.zip
Finding update package...
I: Update location: /storage/sdcard1/custom-signed.zip
Opening update package...
Installing update...
Installation aborted.
I: using /data/media for /sdacrd/0/clockworkmod/.last_install_path.
I:Can't partition non mmcblk device: /devices/msn_sdcc.2/mmc_host
can someone tell me where i did something wrong?
if anyone likes to have a look at the rom:
Code:
archy.no-ip.org/owncloud/public.php?service=files&t=bf55a79f9d9660641b115db5da352f5f
I hope you guys can help me!
Greetings
i think i could describe my problem better, updated the start post
Hi mates, I need your help, thank you!
I would use my old phone (g900v cdi11 locked bootloader) as a videosurvelliance camera, to do that I need that it can reboot automatically if battery runs out and power appears again. To do that I need to change lpm file inside /system/bin folder, switch off phone, plug the power abd check if script lpm file works, if not edit it and check again. . To do that I have these ideas:
1) flash a rooted LL rom, and use a root file manager and overwhite lpm file, is it that easy and possible?
2) Boot on safestrap (which I've already installed and accessible flashing the KK bootloader with Odin, the version is about 2.7.4, don't remember exactly) and chage from there, but the SS file manager don't see any files, probably it's running not rooted (??), maybe /system not mounted, and I don't know all the Unix command I've to type in console to edit lpm or overwrite it, or eventually with ADB.. it copied but in reality I don't know where, it's not /system/bin.
3) so I need to "flash"/install a .zip file containg the /system/bin/lpm file, but for doing this I need a script, which is actually what I'm asking here
4) Any other ideas? Please remember I have a cid11 g900v, so no root on MM, and some other complications unfortunately.
For the script I've tried to arrange from one SS installation, and I tried to save only these lines, but I'm not sure it will do the job, the idea is to create a zip file with system/bin/lpm file and META-INF/com/google/android/updater-script file:
Code:
ui_print("*************************************");
ui_print("* Change lpm *");
ui_print("*************************************");
ui_print("");
unmount("/system");
ui_print("Writing System Files");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_dir("system", "/system");
set_progress(0.600000);
ui_print("Setting Permissions...");
ui_print(" ");
#PERM
set_metadata_recursive("/system/bin", "uid", 0, "gid", 2000, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
ui_print("------> Done!");
unmount("/system");
ui_print(" ");
ui_print(" Installation complete ");
ui_print(" ");
ui_print(" ");
What is missing eventually?
Thank you!
By the time I solved flashing every time the whole rom (exploded, edited and repacked in Windows), boot It and wit its installation.
It still interesting to read your suggestions, thank you