yashsingh1/xdaforums huggingface dataset:
[Android] famonaco:
desire hd, new ginger base 2.36.405.8, the kitchen recompile the rom not well so when i flash it give me flash aborted :confused:

maybe rebuild bad updater script?????
[Android] reef2009:
Hi dsixda,

I'm trying to Sign a update.zip but get this error.

It does find the file but it shows the filename :s
[Android] dsixda:
I don't know where this Ginger Base ROM is, show me the link. Also please post the exact error message you saw, not a summary.

Edit: never mind, I think I know which ROM you're talking about.. it's not called Ginger Base :P. I'll fix it later, thanks
[Android] dsixda:
Oops! Sorry, that was a very silly error on my part. I have fixed it, just re-download it now. Thanks
[Android] BlueHarford:
Error on glacier build

Copying boot.img and system.img ...

Adding an update-script ...

NON-YAFFS FILE FORMAT DETECTED IN ROM

Mounting system.img to loopback device and then extracting files ...

[sudo] password for *******:

mount: you must specify the filesystem type

cp: cannot stat `../tmp/*': No such file or directory

umount: ../tmp: not mounted

Error: No /system/framework folder found!
[Android] dsixda:
Ok... You'll need to be more specific. What device, what ROM, which type of Linux?
[Android] reef2009:
Thnx it works again :D
[Android] BlueHarford:
Building for the Glacier which uses ext4

using our rom, since still working out a bug in the otapackage.

tried it on debian and ubuntu 10.04 same error
[Android] dsixda:
Link to ROM? I had already tested ext4.. ughhh.. I don't understand anymore why issues still pop up.
[Android] BlueHarford:
you can grab the boot.img and system.img from

system

boot

yea kitchen is my save the day when the otapackage is being reworked. this is my first time using it with ext4 rom
[Android] famonaco:
yes mate is ginger base but with modify script for ext4 partition, btw i solved write the ext4 script :)

thx for your help ;)
[Android] dsixda:
It is called Ginger Base?? Wasted my time searching and downloading what i thought was this rom. Send the link then.
[Android] old.ghost:
Thanks a lot for your great job.
[Android] famonaco:
ops sorry man is my custom rom based on ginger new base btw the link is :http://www.androidiani.com/forum/mo...ggio-andro-v2-3-3-sense-2-3-a.html#post435439

see ya :D
[Android] dsixda:
Is this a shipped ROM or nandroid?

If you get it working, let me know.. thanks
[Android] BlueHarford:
this is a custom AOSP rom, Closest it would be is "shipped"

i run Make in the repo to build it... and i can make the IMG's but the otapackage function is borked for the moment, hence my need for kitchen
[Android] dsixda:
I can't download from those sites while at work due to firewall. Can you just post the updater-script of the ROM that was giving problems initially?
[Android] BlueHarford:
do you know whats with the error i posted?
[Android] dsixda:
Even the ext4 tool in Windows doesn't recognize it... your build is hosed.
[Android] dsixda:
Your build is not valid so the script complained about it.

I'd have to go into Linux, check out your problem, and modify the error messages in the script to make them more clear next time.
[Android] BlueHarford:
Can you explain more about not valid?
[Android] dsixda:
Whatever you used to build it didn't make it into the correct format.
[Android] leith51:
You do know you have to wipe your phone and format to ext4 before trying to flash a ext4 Rom either that or mount system and mount data before flashing

Also do you have the correct file in the Rom not sure what it is on xda app at min

Plus the updater-script needs to be edited to ext4

Sent from Levo v2.1
[Android] famonaco:
yes friend i know and i made all, but the problems were when i recompile the build , the kitchen recompile a bad updater script (i don't know why, btw i love the kitchen, good job dsixda) btw i have solved all , if i don't convert the file to update script, and rebuild ,all work fine ;)

cheers :D
[Android] JGW310:
its still a no go :( i will try some of the things recommended in the FAQ again and see if that helps... stupid sed :P
[Android] dsixda:
Can you post the updater-script that was causing the problems?
[Android] famonaco:
sure mate :)

this is the updater script that make the kitchen rebuilding the rom (and always installation aborted)

cheers
[Android] reef2009:
Hi dsixda,

What do you feel about adding services like APKTOOL.

It would be great if we can (de-)compile *.apk's and so on.

Now I Use your Kitchen, AutoAPKTool1.0.6, APKTool 1.4.1 and some others but

I will better use one good tool than 10 and I like this Your Kitchen so...
[Android] dsixda:
No.... I have already stated many times before that I do not want this to be an app/theme modding tool.. it is just a kitchen to build ROMs. I am already spending way too much time on this and I want to spend as much time away from it as possible.

My priority is to make things as stable as possible, and nothing else. You see what happens whenever I add something that someone suggested and it ends up breaking some other functionality.

Feel free to make a plugin for the kitchen if you wish.
[Android] Slatter39:
I have used the Kitchen to cook my own rom from the leaked RUU. However i have 2 questions. i dont know if they have been asked or not.

1. Is there a way to change the build number in the kitchen?

2. Everytime i add .apk file in system/app, it boots to the splash screen and thats it. if i remove them, i can boot and use my phone without any issues. If i add .apk files under data/app, i can boot and use my phone but the apps will not show. Any ideas?

Thanks a bunch.

PS Please dont chew me up if this has been asked already.
[Android] dsixda:
Is this the original updater-script in the ROM?? That's what I was asking for, not the one you created.

I converted it to update-script and then converted it back to updater-script, and the file was the same as it was before..
[Android] dsixda:
Ok, 0.163 is up. Please see Release Notes for details.

Enjoy
[Android] dsixda:
Hahah.. Don't worry.. we (including myself) may all act like tough guys behind the computer screen, but in reality.... ;)

Answer to #1 -- You could use the 'Change ROM Name' option in the kitchen, or edit the working folder's /system/build.prop file for other options

Answer to #2 -- Get ready to be chewed, because I normally type this answer two or three times a day: Read the FAQ for boot issues and flashing issues (recovery.log, logcat)

;)

BTW, if you're replacing an existing APK in system/app, make sure the ROM is de-odexed first, so that the .APKs don't rely on a .ODEX file dependency.
[Android] Slatter39:
Thank Man, because of you i can play with roms and make what i can call my own.

JAH BLESS

Oh and i hit the button too.
[Android] Slatter39:
When i use the change rom name, it changed the Software number but not the build number, unless i am doing something wrong.
[Android] dsixda:
Yes, on the Evo it is different (unlike most other devices).. It is another value in build.prop, as I said earlier.
[Android] Slatter39:
Will check build.prop out. Thanks again
[Android] gchatt10:
OK so yesterday I installed the android kitchen on my unbuntu desktop. Set up went just fine. A little background about me... Java and c++ experience, normally windows user, pretty new to android, very computer literate. So I went to edit my first ROM today. It's last Fridays miui release packaged by Jason voures (sp? Sorry). I had been running miui previously to this and like it.

First I went through the ROM and deleted the .apks I didn't want eg notes, protips, and also some more serious apps like the miui browser, and backup utility. I deleted more but you get the idea. I then replaced the stock browser with Firefox. I also added other apps such as ROM manager, juice def, CPU master etc. I moved these apps to the /system/apps folder. I deleted. Total of 7 stock and moved 10 to system/apps folder. I then opened the ROM with android kitchen and began the editing. I did task killer mem tweak and others... I aligned the .apks but didn't sign them.. don't know exactly what it means to sign them.

I built the ROM then flashed it to my phone. Everything went fine on the boot up. And almost everything works perfectly... expect Firefox and CPU master. When ever I restart the phone, those to apps force close if I open them. If I go thru my file explorer, navigate to system/app folder and open the. Apks (reinstall them) they work just fine. However I like to do a lot of editing, development which requires lots of reboots sso the process of reinstalling those two apps thru file manager is annoying. CPU master force closes after reboot ( I'm guessing cuz I have it on set at boot) l, Firefox only f.c.s if I attempt to open after restart before manual reinstallation.

So all in all I am pretty happy with my first custom build but I strive for perfection... anyone have any ideas on getting those apps to work? All the other apps I moved into system/app folder work fine except those two. It wouldn't be a big deal to redo the ROM and move those two back out but I'd like to know why they are doing this, although I just made the switch to Firefox and it's not what I was expecting so I may switch back anyway... anyone have any ideas? Any help is appreciated.

**Edit** Sorry if this has been asked before as I'm sure it has but I've spent the last 12 hours in front of the comp and don't feel like looking thru 500 pages of posts.

Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel
[Android] famonaco:
Is the updater script that convert the kitchen when rebuild the rom, the original is different :D

i'm speaking about ext4 rom, with ext3 the kitchen work smooth :)

ps: i don't understand why some version of the kitchen doesn't open the menu in my pc and others yes :O

version 161 work properly but the new version nop :(
[Android] wachw:
You could use the advanced build options in kitchen to add data/app functionality then put your apks in /data/app instead of /system/app. Had a similar issue and doing that sorted it out.
[Android] dsixda:
Some apps only work if they are installed in the usual place, which is /data/app. If you have them under /system/app you won't be able to update them in the Market. Anyways just follow the procedure that is already outlined in the FAQ.
[Android] dsixda:
I asked for the updater-script that was causing the problems, not the one you rebuilt. The kitchen was already updated in 0.161 to support ext4. If you deleted updater-script.orig (as the kitchen instructed you not to) then it won't convert properly.

I don't know why you are having issues with the kitchen, you need to be more specific (ie. Paste the output here), as I keep saying repeatedly. I don't think you fully understand what you are doing.
[Android] famonaco:
maybe i can't explain me because my english is not good :p btw, well i try to explain the issue : i write and updater script when i rebuild the rom the kitchen change my updater script and the rom doesn't work :rolleyes: with ext3 works properly man ;)

cheers
[Android] dsixda:
Yes I KNOW what the summary is, I keep telling you that I want you to be specific and mention details for your issues, like posting the original updater-script. Otherwise I'll have nothing to work with. Your problem was already fixed in 0.161. Capiche? Comprendez? Samjay? ;)

Never mind, I think I will jump off a cliff now before I start sounding like a broken record.
[Android] zooz11:
Do I need to change the files & folders (inside working folder) permissions manually before I build the rom?
[Android] dsixda:
No.... just read the FAQ and follow the procedure. If you have to do anything extra then the kitchen would tell you. Permissions are already automatically done by the update script.
[Android] zooz11:
I asked this question because when I flash the rom I find in the logcat "unknown file permission" for so many files!! and the rom will not continue the setup too!
[Android] dsixda:
Permissions issues have to do with signing apks when you don't need to, or removing required Google apps. There's lots of discussion in this thread about permissions issues, just search it.
[Android] Weemoney:
Clean Option

Hey,

Prolly gonna get flamed for asking this but Ive searched in the posts for a bit (450+ is a lot) and googled, but knowing my luck its in the FAQ's or something. Anywho, is there a way to clean the kitchen out? Im on mac and after messing around with a dump I found on the web the kitchen file tells me that there is only 4kb of space available.
[Android] TMartin:
Hey dsixda,

Don't know if you still needed it, but this is for the Desire S aka Saga.

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
[Android] dsixda:
I'm flaming mad at you!!!!

Just remove OLD_WORKING and then clean out your trash folder.
[Android] dsixda:
Thanks, that's the same as on the Desire HD. I'll update the definitions file tonight but keep it at 0.163.
[Android] Slatter39:
I have checked out a lot of forums, and even at XDA and honestly you are the only OP(thread creator) who actually responds to questions posed by users. Not kidding. I have so much mad respect for you. "i want to be just like you when i grow up" kudos man, just keep it up.
[Android] freak69ize:
Although Dsixda is one cool mo fo.. and i got mad respect for him too.. especially for what he's done here ( and ima twitter follower too ) but maybe youre subcribing to the wrong threads dude cuz.. there alot of good peeps here in The Awesome XDA forums.. :D
[Android] kiruya:
thank you for this app
[Android] Yusei:
hello

after i installed all java required in home account and ubuntu virtual console when i tried start kitchen it happens this http://img863.imageshack.us/img863/5097/stuckv.jpg

anyone can help me?
[Android] dsixda:
This error message you are showing us is in Cygwin. You said you installed Ubuntu virtual console (??). What are you doing?
[Android] rsxtypes72:
I'm sorry if this has been asked before I tried searching but had no luck.

I running the kitchen on ubuntu 11.04 64 bit. I have an HTC Vision that is fully rooted and S-Off. I have the latest version of CWR.

I have made several roms from an official release. I make sure its rooted, busy box installed and several other options. The rom is zipped correctly but when its time to install I always, ALWAYS get an error stating the following:

assert failed: write_raw_image("/tmp/boot.img", "boot")

E:Error in /sdcard/vision_signed_*****.zip (Status 7)

Installation aborted

I would really like to learn how to make my own roms from official releases without having to wait for a dev to do it.

Can please explain what I am doing wrong. Is the Vision aka G2 not supported by your rom kitchen?
[Android] dsixda:
Why did you change it to say write_raw_imgae instead of write_raw_image??
[Android] rsxtypes72:
Thats just a spelling error on my part.

That doesnt answer my question though
[Android] dsixda:
That did answer your question, if your script spelled it wrong.

Check the first post. Vision = Desire Z? I don't know what else to say.
[Android] Droidzone:
@dsixda,

Since you've implemented a conversion of update-script, I wanted to ask a doubt regarding an edify code..

As pointed out in the Android git, an ifelse construct can be made. I've run into an Error code 6 on one of them, and was wondering if someone could point out where the bug is..

ui_print(" ");
ui_print("Test script by Droidzone ");
mount("MTD", "system", "/system");
ui_print("Checking if StarBurst was installed previously! ");
ifelse(file_exists("/system/build.prop"), (ui_print("Build.prop exists"); ui_print("Once again, It EXISTS!");), (ui_print("Build.prop does not exist");));
ui_print(" ");
ui_print("Done! ");

Btw, my update-binary is the kitchen's auto generated one.
[Android] Yusei:
I've mix the instructions

plz can you make a copy/past only with the things of the 1st post that i need to do?

EDIT:

i've already found my self

but that error continue
[Android] ThunderStick:
First off my device

ThunderBolt

Clock Work Recovery

Working with gingeritis beta gingerbread rom

I can not get a rom to flash when built with this kitchen. I am using a custom rom originally, ODEX. I zip align it, deodexing does not work. Everything goes smooth otherwise as far as the kitchen goes. When flashing in CWR it says

1 parse errors

e:error in (FILENAME)

(status 6)

installation aborted

When I check the recovery log it appears there is something wrong with the updater script

says

line 1 col 1:syntax error, unexpected BAD, expecting IF or STRING or '!' or '('

1 parse errors

e:error in (FILENAME)

(status 6)

installation aborted

What can I do to fix this. This is starting to bug the hell out of me, I have been at this all day:o

Please and thankyou for the help
[Android] PvilleComp:
OG Droid Incredible AMOLED

Running Ubantu in Oracle VirtualBox on Vista

Downloaded the new leaked HTC Gingerbread from here

http://forum.androidcentral.com/inc...hacks/85963-raw-gingerbread-leak-mirrors.html

Running the latest Kitchen in Ubantu

Imported ROM OK

Rooted in Kitchen OK - No Errors

Added busybox in Kitchen OK - No errors

Rebuild Update scripts - No errors

Removed Bloatware, CityID, VZNavigator, ect.

Built ROM using option 1 and yes to everything. - No Errors

Check Update script - no errors in kitchen.

Load ROM on SD, Wipe Data, Cache and Dalvik, Flash ROM - No Errors

Reboot - Splash1 shows, then the top half of Splash1 goes to static and it's frozen.

I'm sure I'm doing something stupid, but I've read and re-read the first 4 posts and many many posts in the thread, including the last 20 pages.

Tried to capture a logcat, but nothing is captured. Just sits on waiting on device.

Any thoughts?
[Android] jaykresge:
@PvilleComp

Just some comments, as I did the same as you for my build (Liberation). First, make sure you're using the new patched root (the one that mentions force closes) as the older two methods don't work properly. Also, you may have the wrong "leak" as the current 5/19 leak has minimal bloatware. CityID wasn't even included in this leak.

If CityID was just a type, start small. Import the ROM, root it, then build. Check to see if it works. If it works, then add busbox and check again. Then, remove bloatware, and check again. If all else fails, just download Liberation (link in sig) and add busybox. Or, find RMK's release, and remove bloatware.
[Android] PvilleComp:
Thanks, I'll start from scratch and just root it first.

I typed City ID by force of habit when mentioning bloatware! ;) Sorry - it was not there you are correct.

I'll try it tomorrow. Too late now I'll make mistakes just from tierdness.

I'll let you know what happens.
[Android] dsixda:
You need to be more specific -

what do you mean de-odexing "does not work"? Also please post the updater-script, otherwise there's no way I would be able to help.
[Android] dsixda:
You read the first four posts but you didn't view or mention the result of your recovery log. The last few days of posts have been mainly about using recovery log and logcat to debug the boot issues. That would be the only way to know your problem.
[Android] dsixda:
There is no way to tell what your problem is without knowing specifically what you are trying to do. The instructions are clearly explained in detail in the FAQ, there is nothing more I can do. I'm not going to cut and paste and spoonfeed information... just read the FAQ without rushing through everything.
[Android] dsixda:
It won't work in the current kitchen if this new IF/ELSE syntax was only introduced yesterday. The update-binary files would need to be recompiled to support it. Unfortunately I don't know how to compile the three different flavours of update-binary .. I asked Koush two different times but he never replies.
[Android] Slatter39:
You are absolutely correct and i am not taking anything from anyone but i am just appreciating this dude.
[Android] Slatter39:
See what i mean by people not responding to questions?
[Android] dsixda:
Haha but don't expect me to respond ALL the time ;)
[Android] PvilleComp:
So hacking won out over sleep - big surprise!

Tried again with just root and busybox and it booted - now to have fun!

Thanks again!
[Android] ThunderStick:
DEODEX seems to have problems with specific apps, I attached a screen dump of what happened on the first fail when deodexing. Also I attached updater-script along with the original and update-script

Hopefully this will help you iron some things out.

Thanks for the hard work. I have spent a lot of time today learning about building roms and I have just completed my first. I have a lot to learn.. WOW
[Android] Droidzone:
Nope..the If/Else blocks have been there in the git for a long time.. Dont know which version of the binary supports it though.. I should probably start with something simpler and try :)
[Android] old.ghost:
Thanks dsixda for your awesome tools.

I got one question. I enter advanced options to choose item 20 for unpacking boot.img, but I don't know how to re-pack these files back to boot.img as there is no repack option found. Would you please help me out? Many thanks.
[Android] Slatter39:
absolutely not. You are already doing a wonderful job.
[Android] leith51:
You can't the option not there but you can unpack boot.img from working folder and rebuild the boot.img in working folder.

If you move the boot.img into working folder unpack it you can rebuild it job done

Sent from Levo v2.1
[Android] Weemoney:
Thanks man. I thought I had tried that, but obviously not if the dev is telling me to do it. Nice work btw. Appreciate what youve done.
[Android] dsixda:
Search

http://xdaforums.com/showpost.php?p=13039844&postcount=4314
[Android] dsixda:
Ok, in that case, if it's been around for a while, then I guess nobody has used it ;) I'll stop worrying about it for now ;)
[Android] :
I will try porting one of these ROMs to see if I can replicate my steps for busybox. If I can replicate then we're on to something.

But I will leave it until tomorrow or Tuesday.
[Android] RandyM:
HTC Android Kitchen .42 enabling apps2sd

When I try to run the option to enable apps to sd, I get the following error:

Is this ok? what am I doing wrong? Thanks

RandyM
[Android] dsixda:
That's strange.. a bigger (and newer?) busybox? Can you attach that new version please?

Well, to check for busybox is easy :D --> "find . -name busybox"

So basically, if the init.rc has reference to busybox, we should search for it? Is that sufficient? Because, that file is started at bootup, unless we have something else that has precedence.

I could just give a warning that busybox is missing and you need to add it (either copying it manually from the tools folder or by prompting to run the "add_busybox" script).

What do you think?

I am also currently modifying my kitchen, thanks to an idea you gave me yesterday. I will have an option that will let you extract the kernel + modules + build.prop from a ROM of your choice. This is actually useful for me, because I want to grab the Cyanogen kernel and put it into my cooked ROM.

Thanks bro.