yashsingh1/xdaforums huggingface dataset:
[Android] VolcanicSkunk:
I've had similar issues when trying to deodex the framework. It'll hang really badly when trying to deodex certain ones. Not sure which at the moment, but I remember it freezing my terminal when it failed to deodex.
[Android] dsixda:
Please specify the ROM (mention links) and files that are giving you problems.
[Android] dsixda:
Sorry... Don't want to spend my time on this. Looks like a demand more than a request :P

Feel free to make a plugin for the kitchen for it. I don't want to do your work for you ;)
[Android] dsixda:
While in recovery menu, see if you can grab the recovery.log file. That should contain a reason for that error.
[Android] DearTanker:
Sorry for my english.I think you are think that way because i can't use english in a polite way.

But someday,I think you will add this option in you kichen.

And i will not post anything in you thread until that day.

Because i think my post will make you uncomfortable.

By the way,Chinese is the most polite people in the word,just except me.
[Android] frostincredible:
Thank you!

Thank you so much for this! Got it up and running FLAWLESSLY on Mac OS X 10.6.5.
[Android] nfinitefx45:
Hello, and great work with the kitchen, one thing I have noticed is that if I include run parts only (no A2SD) then it never sets the permissions for busybox. this is on both the update and updater scripts.

With this if I include scripts that I want to run and add the the "on property:cm.filesystem.ready=1" to my init.rc then the system will fail to boot due to no permissions.

I add this to my updater-script and it works perfectly.

"set_perm(0, 0, 04755, "/system/xbin/busybox");"

I didnt know if you where aware of this.
[Android] lovethyEVO:
You probably aren't choosing to install busybox.

My update script does not have a single line setting permissions for busybox. What it does have is a line to run a script to install busybox.
[Android] dsixda:
Were you using a ROM that already had busybox symlinks in the update-script before you added run-parts?

Also, why are you adding that flag to the init.rc? Do you have scripts in init.d that will change that value to 1 so that it stops waiting on it?
[Android] nfinitefx45:
yes I have my last script set to change the vaalue to one. I actually did this off of the latest update from Sprint (hero cdma) built from ruu with buybox, bash, and runparts added. They where not there prior (factory image) but did not include A2sd.

At boot I got the busybox error about the permissions, so I added them myself and everything was fine. I did this twice just to check that it wasnt something I had done. first time on 107 and second time on 108 with the same end result.

It is not a big issue as I will just check before build to verify that it is there, but atleast wanted to let you know incase it is happening to others.

Thanks for the quick reply.
[Android] dsixda:
Did you have the installbusybox script in the root folder of your ROM? It includes a 'chmod 755' of the busybox binary.
[Android] dsixda:
Oops,sorry, those aren't Perl scripts, they were compiled in C, I think.

Do you have the two mkboot* files under your tools/ folder?

I just tried my kitchen right now and it works fine. I'm using the latest version, 0.18.
[Android] dsixda:
I also notice in your output above that there is a 'space' between the "/" and the "mkboot". There shouldn't be one there.
[Android] robin04:
yes, i have two files in the folder tools mkbootfs and mkbootimg.

the space between "/" and "mkboot *" because I've written with my hand, my mistake. however, do not script this error.

I think that the terminal does not "recognize" the file mkbootfs and mkbootimg.

I also tried it with split boot image, compiled in perl, and when I write command to recreate the image:

mkbootimg - cmdline 'no_console_suspend = 1 console = null' - kernel-kernel boot.img - ramdisk ramdisk-new.gz-o boot-new.img

gives me error "mkbootimg command not found"

Same thing with mkbootfs, "mkbootfs command not found"
[Android] robocik:
I am using 0.18 and it is working good :) thank you dsixda :D

Try to download and unpack again... maybe it went wrong somewhere there.
[Android] elelinux:
Thanks again for the great work :D

I'm have question, is possibly for you to make one more option in the kitchen.

A script for resigning apk files .

Thanks again really love this kitchen tool :D

Best regards elelinux //

Sorry for my bad enlish :(
[Android] dsixda:
Your English is fine! That's a good suggestion, I have never signed apk's but I was actually thinking of doing that (as well as other things like making update.zip for extracted radio.img). I could add that, but I'll do so after I finish playing with my new Nexus One which should be arriving soon :)
[Android] kendong2:
valid suggestion, i am not sure about implementing this:

signing regular apps would break update compatibility, as it needs the same signature for that. signing system apps breaks the whole system, as they must not be signed with test keys.

maybe you could elaborate a bit on what you want to do exactly?

and for radio update.zips: not the worst idea, but since there are only a handfull different radios and they are all available in update format i don't see the need. don't let that stop you, but keep in mind that more options keep more potential for errors/problems...
[Android] dsixda:
Hi guys,

I received my new Nexus One yesterday :) I was able to port the kitchen so that it can now build a custom ROM for the Nexus One. I also have modified the kitchen to potentially work with the HTC Magic and the Dream.

I guess it's no longer limited to the Hero, so perhaps I should get a mod to move it to another subforum... ;-)

The new version has been tested and working with the Hero and Nexus One so far.
[Android] anzo:
Congratulations!

I tried the kitchen, the Acer Liquide and update.zip it works perfectly. Unfortunately, the boot.img can not expand. :confused:

Thanks! :)
[Android] dsixda:
Thanks for trying it out.. however it is only for HTC devices so far.
[Android] dsixda:
Wow.... 1400 downloads in 12 hours for version 0.19! That's more than all previous 18 versions of the kitchen combined (when it was just a Hero kitchen)! Looks like there are A LOT of Nexus One owners out there! Thank you so much.

I have now added version 0.20, which has a Wireless Tether update. Not a big deal for Hero owners, but for Nexus One it requires some kernel modification.. so this kitchen will be helpful.
[Android] antz88c:
followed all the steps but when i try to flash, i get

- "can't open/sdcard/signed_xxxxx.zip

- (bad)

Installation aborted.

I am using my nandoind backup/
[Android] dsixda:
Looks like you didn't unmount your SD card properly -

Search xda for: update.zip "can't open"

And you'll get:

http://xdaforums.com/showthread.php?t=476615
[Android] samaral:
Hi!

Hi dsixda! I have been an avid follower of your Elf/Elfin roms till my phone got replaced to a G1. I would be glad to try this thing out in the next couple of days. :)

Cheers mate!
[Android] CHERNAB0G:
guess ill be the first dream user, downloading now
[Android] dsixda:
Thanks guys, let me know how it goes on your HTC Dreams :)
[Android] YanDroid:
Can anyone make a video on how to do this? I honestly want to learn how to make ROMs, but some of the stuff here are quite confusing...
[Android] dsixda:
What part is confusing? The aim of the kitchen is supposed to make it easier ;)

I have been staying up a bit late tonight, updating the FAQ for this thread, so there is now more information available to read at the moment.
[Android] antz88c:
@dsixda

Good thing you included this. I used my nandroid backup the first time I did my cooking and it failed when flashing.

I downloaded the one from wiki and everything went well. It only took me awhile to figure out how to remove unwanted apps before I finally perfected my cooking and i must say, I made it!

Thanks so much for this, now I am using my own ROM just the way I like it. (and did i say, it's really delicious)
[Android] dsixda:
That's great to know! Did you use a Hero?
[Android] nfinitefx45:
Yes I do, I will create another rom from scratch tonight and verify that it is or isnt doing it.

I will post back later and let you know.

this is you installbusybox shript

#!/system/bin/sh
cd /system/xbin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin

and shouldnt it be

#!/system/bin/sh
cd /system/xbin
/system/[COLOR="Red"]xbin[/COLOR]/chmod 755 busybox
./busybox --install -s /system/xbin

?
[Android] radar369:
Sorry for being so far behind you guys but I JUST decided to try and make my own rom for my Evo but I am having one problem (for now)! I installed the java dk you said to install on the first page BEFORE I installed the cygwin program......but when I try and start my kitchen it says that I haven't installed it yet...and it ask if I want to start the kitchen anyway!

Now I know I installed the jdk that was said to install.........why is it still saying I didn't?! Thanks for anybodys help!!!!!!!!!
[Android] dsixda:
No, because xbin/chmod is created by busybox in the final line, so it wouldn't yet exist at that point you specified.

bin/chmod is the default version of chmod that comes with the operating system.
[Android] nfinitefx45:
Gotcha, I will run a test rom tonight and just check it, it could have just been the particular rom I was working on.
[Android] lovethyEVO:
dsixda beat me to it.
[Android] Silverexp:
Ok, I’ve customized a stock FRG83 w/Deodex, root, & App2SD. All I need for my heavy daily usage. Read a couple of ways to run the update FRG83D, but all result to stuck splash screen. Is there a way to incorporate the FRG83D update in the kitchen? Sorry if I’ve over looked it or if my search result didn’t come up with a hit.
[Android] dsixda:
No you can't do it through the kitchen. I have never tried patching an update with an existing ROM, but some guys know how to do it manually. For the update you mentioned, I just downloaded one that someone already merged with a full ROM.
[Android] VolcanicSkunk:
Here is the recovery log that you requested.
[Android] dsixda:
I didn't request it, I told you to take a look at it :) I can't open it right now... do you see any errors in there?
[Android] lovethyEVO:
According to his log file there is something going on with the boot.img. Maybe there is not boot.img in the package or maybe the boot.img is corrupt somehow.

That's the only error I saw that stands out.

calling command write_raw_image
Writing BOOT:...
E:Can't find BOOT:
E:Failure at line 82:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
[Android] VolcanicSkunk:
Sorry about that. That did sound really bad. I didn't mean to offend. I did look at the log and like LovethyEvo said, that was the only error I could find. Everything else seemed to be flashing properly. I do have a boot.img in my final build. I'm not sure what the problem is. I've tried replacing the zimage as mentioned previously and that didn't work either. I still get the same error. It varies between error on line 80 with the stock kernel and line 82 with Gr8Gorilla/King's kernel. Thanks so much for helping guys!
[Android] jbrew78:
I'm using the system.img and boot.img from a nandroid backup I made on my myTouch 4G. There are 2 files in system/framework that will not deodex: android.policy.jar and services.jar
[Android] Silverexp:
Thanks for the response. I found a custom rom close to stock I want to use, but stuck at the “Found an updater-script but not an update-script.” scenario . Selecting 1,2, or 3 still produces a stuck splash screen rom. In the WM days I could extract a rom, remove the packages I didn’t want, then compile it back to a rom. I’m just behind the curve in the Nexus/Android kitchen. :o
[Android] TMartin:
What I would do is extract the files from the OTA (which will have .p patch files of only the new files), right down all the changes then drag the the changed files from the custom ROM you found into your kitchen overwriting the files from FRG83 with the new FRG83D. Then you would compare your build.prop to the build.prop of the custom ROM. Then you don't have to worry about changing the update-script or updater-script.
[Android] dsixda:
Do these patch files need to be changed in any way, or just renamed to their real file names?
[Android] TMartin:
That I don't know. I just use the actual OTA as a reference and use the files from a stocking custom Rom with the OTA already applied.

Posted from my HTC Evo 4G on Tapatalk Pro!
[Android] rs125:
You can add error checking on-updater script?

So do not transform the update-script in the updater-script!

Thanks
[Android] webstar1:
Hi can anyone help me please, now I know the kitchen isn't designed for samsung galaxy s but this kitchen is capable for making roms for other phones and this error I'm getting is a general problem not related to my phone. The rom is flashing fine until halfway through I get the following error:

E: Can't symlink system/bin/su

E: Failiure at line 74

symlink /system/xbin/su SYSTEM:bin/su

Installation aborted.

I am using clockwork recovery to flash this rom. Please people I really need help
[Android] BesFen:
I think there is no su file in system/bin and system/xbin, check it again.
[Android] webstar1:
I don't think thats the problem as the root update.zip only has the following files:

system/xbin su

system/xbin busybox

system/app superuser.apk

Thanks
[Android] dsixda:
Looks like you already have a system/bin/su on your device so it is unable to make a symlink there. Also, run the update-script verification tool.
[Android] webstar1:
My rom does not already have su in the bin folder and the rom wipes the system partition before it starts copying files so it can't be that, I also ran update verification and only gave errors where I modified update-script so the rom installs properly on my phone, it didnt give errors where the symlink is created
[Android] dsixda:
Find the recovery.log on your device and see what it says at the point it failed.
[Android] webstar1:
Where is that?
[Android] webstar1:
Thanks for all the help, my rom is now working
[Android] dsixda:
Well, let us know then what you did.
[Android] BesFen:
Congrat..... what did you do to make it work?
[Android] Existence.:
Webstar, are you using a stock rom straight from Samsung, then modifying that to create your custom rom? Or are you modifying someone else's custom rom? I'm asking this because I'm unable to import stock Samsung firmware into the kitchen.
[Android] rs125:
.....................................UP!!
[Android] webstar1:
Ok guys so this is how I did it:

1) installed clockwork on my stock! Samsung firmware.

2) did nandroid backup.

3) connected to my ubuntu pc.

4) launched htc android kitchen.

5) now since samsung galaxy has 2 bootloaders so the device doesn't brick any way so we have no boot.img in the backup, so I used system.img and renamed cache.img to boot.img as it is usually empty.

6) then once working folder created, in it I deleted boot.img and in update.script I removed the line where it installs boot.img .

7) did all three modifications I wanted to In my rom.

8) now I got symlink error.

9) so I extracted update.zip and saw for any file that was already named system/bin/su and it didn't show up because this time I was on my laptop which is a windows 7, then I unchecked hidden files and there it was, I then deleted it and went back to htc kitchen,

10) recompiled the rom, flashed and I am now running my custom rom :D

Thanks to:

Dxsida for telling me why I got symlink error
[Android] Bladyle:
I use run-parts function to add init.d script support to my froyo then make a init.d folder and add 99complete with "setprop dev.filesystem.ready 1;" but script dosn't run. Any idea ?!
[Android] dsixda:
So, basically this kitchen works for Galaxy S ROMs as long as you don't build it with the boot.img?
[Android] dsixda:
:P

I don't understand fully your question but making a verification for updater-script is too difficult and I don't have time anymore.
[Android] webstar1:
yes you can add galaxy to the list giving the boot.img note, and it should also work with the american galaxy models such as galaxy vibrant, fascinate etc.

~Webstar1
[Android] dsixda:
Cool! Thanks

The only other thing, however, is that the stick ROMs cannot be extracted. You'd need the nandroid .img files or update.zip
[Android] rs125:
I understand ... and why is it difficult?

You can add the system to check the details as to the update-script?
[Android] dsixda:
Updater-script syntax is more complex than the simple update-scripts.. plus unfortunately I don't have time to work on that. If someone wants to contribute a plugin to the kitchen to do that, they are free to do so.
[Android] mike1986.:
New SDK is out. Maybe you can implement new zipalign.exe tool to the kitchen? Replacing zipalign.exe in tools\zipalign_files is ok or some changes needs to be done also to mgwz.dll or zipalign?
[Android] dsixda:
Are there changes to zipalign?
[Android] mike1986.:
The size of each is different so might be. I don't know where to check some kind of changelog?
[Android] WaPeR32:
Hi!

I want to make my own modification of the CyanogenMod 6.1 for Nexus One, but I don't know what to do with the updater-script.

If I leave it: boot animation loop

If I convert it into a update script: error in the recovery

Can you help me?

Thanks!
[Android] dsixda:
Search this thread for Cyanogen.
[Android] dsixda:
Version 0.109 is now out. Enjoy
[Android] vermaekansh:
great going man...v'l download and start cooking once reach home...
[Android] WaPeR32:
I tried that but search was disabled, i'm going to try again

Thanks!
[Android] mercury700ir:
HI all...

and a special hello for dear DSIXDA for his efforts...

I used your kitchen from the 0.88 version but with just using the simple modes not in scripts...

I have a question now...

In all the roms I made with the kitchen I added App2SD option to the roms, but in non of them it works..

1- Should I do anything special for my Roms to work or activate the App2SD ..??

---------------

2- I used 2.1 version of roms because my cellphone is legend, in 2.2 I want to start, if anything special should I with the 2.2 roms for activating App2SD please tell .. ( because I used now MVZ-supperfroyo but It seems the app2sd in this rom does not work...

----------------

Thanks a lot...

(I searched the thread for >>> app2sd activation <<< but I did not find anything)
[Android] dsixda:
You need to go to your recovery menu and partition your SD card for an ext2 partition and then change it to ext3. There are instructions in the kitchen when you start apps2sd.
[Android] mercury700ir:
Thanks alot DSIXDA, I've done this in 0.9x versions but I have not got any succeed in activating App2Sd, maybe I did some thing wrong.

Thanks again for your answers...

Be more successfull and happy everyday more than previous days...
[Android] alb3rt018:
hey DSIXDA no what i try i cant get it working on window 7 i got java jdk install

edit:nvm got it working
[Android] alb3rt018:
hey DSIXDA what about adding option to odexed a rom?
[Android] dsixda:
I've added version 0.110, which includes just a minor update for apps2sd.
[Android] dsixda:
Thanks man! I'll update the first page with plugin info.
[Android] OShocke:
Followed install guide but whenever but it doesn't do anything when i type in somthing I'll type in "1" hit enter it goes away and some text comes up but i can't read it goes away to quick...

I'm on a Mac using snow lep.
[Android] StenaviN:
dsixda

You can also add Q/A in FAQ section, if you want:

QUESTION: Why some applications in the data/app folder force close and others don't?

Probably, they have native libraries, which not installed after your flash your ROM. Use Application Verifier plugin to check such apps and make required update zip.
[Android] lovethyEVO:
Hey dsixda,

Got a bunch of things that I was curious about. I know you said you're not a themer and this isn't really related to theming period but when I try to swap a framework-res.apk in the rom for one that is already themed the rom bootloops.

If I flash the themed framework over the stock framework after the rom is flashed there are no problems.

I was wondering if you knew if certain apks have to be signed in a certain way in order to be integrated into the rom like the framework apks.

I was thinking of just taking the original framework from the rom and decompiling, editing, and resigning it "with its own signature?" but honestly that's too much work when there is already a framework file that has all the edits I want. This leads me to my other concern, could I just insert the edited framework into the working folder and then sign it with the kitchen or would that still not make it work?

Also, it would be great if you could add the memory tweak for stock kernels in the rom information list.

Last, is it possible to add the option to change the default launcher that the rom uses? Old freshevo versions I remember would start launcherpro by default. It would be great if this was an option in the kitchen. If it's too much work I understand.
[Android] mike1986.:
dsixda have you checked the new zipalign.exe? Any changes?
[Android] roalex:
Could we get a ODEXing feature as well ?:) For instance i found this script on MoDaCo which works on the phone itself.
[Android] alb3rt018:
i would love to have to have odex option
[Android] dsixda:
Thanks, done!

I can't answer your theming question cos I'm not an expert on that kind of stuff... there has been a lot of discussion on that in the past though... just search for framework.

I can't put the memory / task killer numbers in the Show Info screen because non-stock kernels sometimes use a script to override those settings, which would make them false if shown.

I don't know how to set default launcher, plus i wouldn't want a whole new set of bugs generated and questions being asked about a feature that I wouldn't use much, if at all.

Nope... and i don't know, sorry. Why don't you find out on your own. I don't look at the SDK much anymore.

Yes, I know. Already been asked and answered in this thread and in the FAQ. Plus it will be hell to sign the odex files and determine which JARs and APKs need odexing. Not something I want to do and have time for. (Wasted a whole month on de-odexing exercise already.) :(

Anyways if somebody wants to take initiative and figure out and do these things then that would be great, since my free time is almost zero these days and there really isn't any incentive anymore.

Haha what a negative reply ;)
[Android] lovethyEVO:
Thanks for the reply. I'm basically just going to tweak the phone the way I like it and then "try" to make another rom from the nandroid files. I know it's not recommended but I figure the only things I really change from the rom I make the first time to the tweaked rom is the framework files and uninstall of stock apps so theoretically I can use the same update script from the first rom. Here's hoping.
[Android] mike1986.:
Well all I know it's working fine. I replaced the one from the kitchen with new one from new SDK. The size of file is much smaller so I think it's just some code improvements.
[Android] alain57:
sorry if that question was already asked, but well reading more than 200 page will take hours :(

what should i do port a ROM

my example :

I have a desire HD

and I want to try porting the desire (not HD) MIUI ROM

should i first open the DHD ROM, then go advanced menu => port => MIUI ROM ?

I also tried it, and funnily i needed to first open a ROM

then the port open one ROM

and directly after that asked for an other one (so i open 3 times a ROM )

edit: i forgot to open my eyes, it was clearly marked ^^

just hopping it will work :)

edit2: not working :(

i get an error

Board does not support mtd utils E:Failure at line 244

write_raw_image Package: boot