Hello Devs,
I was using android kitchen. Regarding that I have one question.
When I am extracting a new ROM, I am receiving below instruction from kitchen. What to do in this situation? I am confused here.
Should I go for option 1 or for option 2, here?
Please help me.
Found an updater-script but not an update-script. For
compatibility with the kitchen scripts, only update-
scripts are used in the kitchen (see the kitchen's FAQ
at xda-developers.com for a detailed explanation).
The kitchen will attempt to convert your updater-script
into an update-script file using the old (or similar)
syntax of an update-script, which makes it easier for
the kitchen to make changes for different devices. When
the ROM is built, it will be converted back.
WARNING:
If you are using a custom ROM (ZIP) that was made
without the kitchen, then the conversion may not be
100%. The kitchen will make a backup of this file
as META-INF/com/google/android/updater-script.orig.
Choose an option number:
1 = Convert it to update-script (Amend format)
2 = Do nothing, keep updater-script (Edify format)
Click to expand...
Click to collapse
captain_nemo said:
Hello Devs,
I was using android kitchen. Regarding that I have one question.
When I am extracting a new ROM, I am receiving below instruction from kitchen. What to do in this situation? I am confused here.
Should I go for option 1 or for option 2, here?
Please help me.
Click to expand...
Click to collapse
Hello, do you have any further clues on this? I have the same issue. Absolute newbie to ROMs..
I downloaded the stockrom from safariking from here http://forum.xda-developers.com/showthread.php?t=2489395. Created a working folder and rebuilt the ROM without any changes to check if I got the kitchen working properly or not. I choose option 1 but the cooked ROM refuses to flash - gave some Status 7 error.
Thanks.
ongalaxy said:
Hello, do you have any further clues on this? I have the same issue. Absolute newbie to ROMs..
I downloaded the stockrom from safariking from here http://forum.xda-developers.com/showthread.php?t=2489395. Created a working folder and rebuilt the ROM without any changes to check if I got the kitchen working properly or not. I choose option 1 but the cooked ROM refuses to flash - gave some Status 7 error.
Thanks.
Click to expand...
Click to collapse
Use option 2 and manually change the updater-script from the path.
ok i am also using android kitchen from a xda guide
so just dt kitchen wud recognises your rom you have to convert your updater script to update script
den modify your rom or do any changes you want
den before repacking your rom again convert the update script to updater script and then pack it
worked fr me
http://forum.xda-developers.com/showthread.php?t=2195858
jesuinodsa said:
ok i am also using android kitchen from a xda guide
so just dt kitchen wud recognises your rom you have to convert your updater script to update script
den modify your rom or do any changes you want
den before repacking your rom again convert the update script to updater script and then pack it
worked fr me
http://forum.xda-developers.com/showthread.php?t=2195858
Click to expand...
Click to collapse
All new versions of CWM use updater script to install the ROM. Update script was used previously and used in the kitchen. So if you are using the kitchen then make sure you convert it to updater script as update script wont work anymore
Dark Wraith said:
All new versions of CWM use updater script to install the ROM. Update script was used previously and used in the kitchen. So if you are using the kitchen then make sure you convert it to updater script as update script wont work anymore
Click to expand...
Click to collapse
ya i know but kitchen is in old ways to remember it paths and ways to rom it must be converted to update and when ua rom iis dne den again convert to updater and den pack the rom
check the link above
jesuinodsa said:
ya i know but kitchen is in old ways to remember it paths and ways to rom it must be converted to update and when ua rom iis dne den again convert to updater and den pack the rom
check the link above
Click to expand...
Click to collapse
Ya i sed the same thing..should have quoted the op..however in my humble opinion,its better to cook a ROM manually instead of kitchen as you'll learn a lot more.Plus dxdia has stopped working on the kitchen so you'll get limite
d options and very less support
Related
Hello,
I have made a bounch of scripts which allow me to play with my camera settings.
I copy the files manualy and its looks like it is working.
I want now to create a zip pack which i will be able to install from recovery (like any other patch i can use for the ROM).
Is thee some guide or some refernce i can use which describes how to create such pack, and what are the commands which i can use in the installaion script
[crowd] said:
Hello,
I have made a bounch of scripts which allow me to play with my camera settings.
I copy the files manualy and its looks like it is working.
I want now to create a zip pack which i will be able to install from recovery (like any other patch i can use for the ROM).
Is thee some guide or some refernce i can use which describes how to create such pack, and what are the commands which i can use in the installaion script
Click to expand...
Click to collapse
If you are talkin about file and not string of code, you can use Update.zip 2.0 Modifier/Creator this script let you create an update.zip signed flashable from recovery...
Hanisa said:
If you are talkin about file and not string of code, you can use Update.zip 2.0 Modifier/Creator this script let you create an update.zip signed flashable from recovery...
Click to expand...
Click to collapse
Hi there ,
thanks ! thats exactly what i was looking for!
do you know where could i find a list of commands which i could put on the script
MortScript
With MortScript you'll automate the whole process.
See;
MortScript
[Mortscript] Source Compendium
[MortScript] Examples Accumulation
Have fun,
Senax
Senax said:
With MortScript you'll automate the whole process.
See;
MortScript
[Mortscript] Source Compendium
[MortScript] Examples Accumulation
Have fun,
Senax
Click to expand...
Click to collapse
Hi,
Thanks but i can't see how is this has anything to scripting in recovery mode.
Actualy i am not even sure this is Android supported (i can see the android player but not the scripting part) ...
Anyhow I am looking for a way to install my script from recovery mode actually all i need now is a place in which there will be a list of commands which are accepted buy the recovery updater.
Thanks.
dsixda's Android Kitchen - Now for Samsung Galaxy S Plus (I9001)
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S Plus custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.182, you can now create your own Galaxy S Plus ROMs with the kitchen.
I'd like to thank the guys in this thread, especially crybert, oisis and mbba67 for helping me out, as well as for testing on their devices and providing feedback. I only have a Bell Galaxy S2 I9100 so their assistance was greatly appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S Plus (I9001) with a ClockworkMod-based custom recovery.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows or Linux or Mac. Ensure you read the FAQ carefully.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S Plus, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
system.img.ext4 and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a system.img.ext4 but then didn't include the cache.img.ext4, then you have the option to add a cache.img.ext4 later using the Extract SGS2 CSC script in the Advanced menu's 'Plugins' section.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Here are some screenshots of how to use the kitchen for the I9001, thanks to crybert.
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss Samsung Galaxy S Plus in this thread!
Most of all, have patience, take your time and enjoy!!
Reserved...
Reserved, just in case
Great stuff .. Thanks for ur work
great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?
Blumdum said:
great work!
did anyone tried the porting option in this kitchen?
could be very usefull to port miui or cyanogenmod to our device
i know its signed as experimental but anyone know the chances that this option will lead to a success?
Click to expand...
Click to collapse
Would be kind of hard to do..., but I heard that the SGSPlus is similar to the Desire HD, so I would start with a ROM from there.
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Desire HD uses the same cpu/gpu as i9001 so there should be a big similarity
im asking myself the same question wether there is a chance for a full brick
but the boot.img will be written on the right partition
I don't know much about porting apart from the generic steps in the kitchen scripts. But if you have a nandroid backup, how would you brick (unless you mean the wrong partition would mess it up.. In that case just double check the updater-script before building).
maybe a wrong boot.img could lead to a brick
crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
I dont know about porting or boot.img, but what if you just replace SGS+ boot.img over the DesireHD Cyanogenmd Rom boot.img then just fix them in the kitchen. I dont know..........
crybert said:
You think the Cyanogenmd for the DesireHD would work? And if I try the porting thing. Is there a big chance to full brick my phone. I know I have to look that the boot.img and the system is flashed on the right partition. So if something goes wrong I think I can enter Download-Mode anyway?
Click to expand...
Click to collapse
if the porting of cynogenmod from DHD succeeds we will be able to port their ICS too then. with some modifications to boot.img, build.prop. etc.. , replacing drivers, maybe we can try camera drivers and libs from I9000 port , of course we'll need someone to compile the right kernel. imo it can be done if we put a team work into it
but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots
Blumdum said:
but we can first try to port the desireHD rom to our device using the kitchen and then see if the device boots
Click to expand...
Click to collapse
the rom from DHD won't boot on I9001 without the right kernel.
Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?
rayiskon said:
the rom from DHD won't boot on I9001 without the right kernel.
Click to expand...
Click to collapse
did you try it?
EDIT:
when we need a CM kernel we could build one
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
mr_omega said:
Can you tell me where can I find an information how to add to my fresh cooked rom CWM FeaMod Recovery?
Click to expand...
Click to collapse
1. just add the recovery.img to the main directory of your rom. Where /system and META-INF is located
2. add the following line to your updater-script:
package_extract_file("recovery.img", "/dev/block/mmcblk0p13");
P:S.
We should move the discussion about CM to another thread. I think this is a bit offtopic
Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.
dsixda said:
Hi guys, I have updated the kitchen to 0.182. See the main thread (linked on post #1) for full release notes.
Click to expand...
Click to collapse
Hi, how come i can extract boot.img but cant repack, there is no option for repack
try porting MIUI instead of CM7. MIUI is not only fast but customize able and i think dsixda does the work for you and then minor bugs can be fixed.
Hi all,
I'm using this rom ZaSa_4chacha_GB1.54_v2.0 (1.54.401.2) and I want to use UOT kitchen to modify theme.
But I don't know which framework-res.apk and systemUI.apk use.
Can someone help me ?
Thanks
Well, nobody inspired ?
I'll try to be more clear and give more explanations.
I used files extract from the 1.33 RUU to create my theme. First question, I don't know if I'm right...
Then I've downloaded the UOT files and flash it. When I reboot my phone, I've got a problem with com.android.phone. It crashed, so I can do nothing.
I don't know if my files are good, or if I have the correct settings on UOT kitchen. (Suche like edify or amend script)
The problem is here:
I'm using this rom ZaSa_4chacha_GB1.54_v2.0 (1.54.401.2).
Click to expand...
Click to collapse
I used files extract from the 1.33 RUU to create my theme
Click to expand...
Click to collapse
Can you see now where the problem occurs?
If you want to use UOT then you must use the files from ZaSa, as you have flashed 1.33 files over the 1.54 version.
It's exactly the same as you did with the 1.33 files. In case you are having issues, use Root Explorer, mount it as R/W and browse the files on your phone then copy-paste them to your SD card from the app.
Well, I used the 1.33 files because I've read somewhere that I should use "proper file". I was thinking it means from stock rom whereas it means from my rom.
I've made a try with the files extract from Zasa rom, but I've got a SHTF files.
Should I used the com.htc.resources files ? On UOT site they explain that's for rom with sense, but Zasa 1.54 v2.0 is provide without sense whereas this file exist in the rom. Not sure my explanations are clear... Very sorry for my english.
Thanks for your help!
It's possible that even if ZaSa comes without Sense (since it's still a stock rom though) those files are being used anyway. Give it a try with the files suggested by UOT for the Sense rom.
I've tried with and without the recommended file for sense rom, I've always SHTF files!
Become a Themer
If someone send me the link for a 1.57 RUU chacha rom.zip, i will work on it to make it a great rom as i did for my Desire
No need to UOT kitchen when you can do it by yourself _ check out my tutos if you are curious and wanna learn something new in android.
https://sites.google.com/site/androidbyyorzua/home/tutorials/become-a-themer
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
pratyush.creed said:
not very hard ,just extract initramfs.cpio from the zImage ,add this line
CONFIG_EXT4_FS=y in filesystems,then change Mount points in init.rc of Ramdisk
and then Format All Dev Blocks e.g. System,Data,Cache to ext4 !!
Click to expand...
Click to collapse
Prodai said:
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
Click to expand...
Click to collapse
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
yeshwanthvshenoy said:
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
Click to expand...
Click to collapse
I have unpacked boot.img using advanced options in kitchen's menu, now I have folder ramdisk and zImage, what to do now to convert it to ext4?
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Prodai said:
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Click to expand...
Click to collapse
ur boot.img from stock is rfs format so it wont work if u use that...use boot.img from any custom rom that is also based on ur baseband version(DXKT7)man..the boot.img will automaticaly have the ext4 filesystem(in custom boot.img not stock)....kernel is later part of ur rom man better not go into that now .....copy boot.img from custom rom of ur baseband version then system.rfs and csc.rfs file from stock rom and do as i said above and dont forget to replace update-binary in ur rom after creating the output_zip file from any other custom rom or ur rom wont install
Hello First sorry for my bad English. I have this file I8262XXBNC1_I8262ODDNC1_I8262DDNB1_HOME.tar a official firmware. can i use this to make a custom rom. I know that i can use a rom from this forum to change but i want to this project for fun, I opened it with winrar those files(photo below) and i saw that i need more files to do that. What you suggest to do?
Don't know well!!! But I think you can... just extract the firmware and found the "system" folder from there!!!
Press the Thanks button!!!
From my research i saw how to extract the files from the system but no way how to make one file again. I did that and i bricked my phone so i install again original firmware with odin.
If you have a pc... then use apktool to make and edit your rom!!!!
Or,
If you don't have a pc.. then install apktool in your device!!!
Install sygwin if you're on windows, then download dsixda kitchen or archi kitchen. Make it compatible for your phone and there you go...making flashable zips from official firmware with root, deodex, init.d etc.
tys0n said:
Install sygwin if you're on windows, then download dsixda kitchen or archi kitchen. Make it compatible for your phone and there you go...making flashable zips from official firmware with root, deodex, init.d etc.
Click to expand...
Click to collapse
Ok i will try it tomorrow