yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
That's because if you installed bash it takes over from sh as the default shell, which gets renamed to sh0. You can try renaming it back to sh.
[Android] vido.ardes:
sh was still in the bin folder, I didn't use any options in the kitchen other than the porting tools. I also tried to start porting it manually but I can't even get it to build... maybe a little out of my depth me thinks...
[Android] dsixda:
Yeah actually my answer was wrong anyway... sh gets replaced by another sh which is a symlink to bash. But since u didn't use bash, then forget what I said.

I wouldn't give up... porting is not a one-click process, it requires some debugging to patch things up.

I've seen other people have this issue in the past when porting. Have you found anything through searching the web?
[Android] vido.ardes:
Most of the people getting this error seem to be trying to push files to /system, and the fix is that /system was mounted properly, but I am not sure if that is relevant, unless the boot.img isn't mounting /system properly perhaps?
[Android] dsixda:
Check the recovery log after you flash it and before the first reboot.

And what device are you porting to and from??

Edit: Did you make sure your ROM has an updater-script and not update-script?
[Android] lolingu:
¿Is it safe to edit the MIUI rom with the kitchen? I mean to delete some apps from the stock one I don't use and are not other app-dependant.
[Android] vido.ardes:
I've attached the recovery log, the only thing that sticks out for me is:

format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25

I googled for it and the only refer I found to it was in this thread, and you said you didn't think it was a problem, so I am stumped

I am porting from the Deisre HD (Ace) to Incredible S (vivo), there hardware is almost identical, the incs has a slightly smaller screen and a front facing cam, other than that it is the same
[Android] dsixda:
So your system was not mounted.

Will look at it later.. at work now.
[Android] vido.ardes:
I am porting from the Deisre HD (Ace) to Incredible S (vivo), there hardware is almost identical, the incs has a slightly smaller screen and a front facing cam, other than that it is the same
[Android] dsixda:
If you search for that error message "format_ext3_device failed", you'll find a link to a source code for the update-binary for Cyanogen:

https://github.com/CyanogenMod/android_bootable_recovery/blob/gingerbread/updater/install.c

The reason for the error is that it is unable to format the location for the system partition (I know, that's obvious already) :

} else if (strcmp(fs_type, "ext3") == 0) {
int status = format_ext3_device(location);
if (status != 0) {
fprintf(stderr, "%s: format_ext3_device failed (%d) on %s",
name, status, location);
result = strdup("");
goto done;
}

Perhaps the kernel drivers refer to the Desire HD filesystem type.
[Android] vido.ardes:
The filesystem type should be identical, the partition table looks to be the same from what I can tell.
[Android] freak69ize:
Just click on the menu file in the kitchen folder and then right click on menu file and run in terminal and it will take you to kitchen..
[Android] dsixda:
No, the HD uses EMMC but Incredible S uses MMC.
[Android] dsixda:
Yes it should be possible. Make a nandroid backup anyway.. that's the only way anything can be "safe".
[Android] Faryaab:
How to use 911sniper's leaked roms in this because it all just have folders?
[Android] Droidzone:
Just like importing any other Rom.
[Android] spaarc:
Is the porting tool stable enough

because i m not able to port the droid's to the xperia x10
[Android] dsixda:
What do you mean by "not able to port"? Please be more specific and give details about why you are not able to port it and what you tried to debug it.

The porting tool is experimental so it's not the silver bullet for every single device imaginable.
[Android] vido.ardes:
Makes sense, I must admit I didn't think there was a difference. Don't spose you know which driver would need replacing do you? I've had a google but I can't find the answer
[Android] dsixda:
No idea, man... sorry. You could first try porting just the kernel and not the drivers.. see if it boots that way.
[Android] vido.ardes:
To be honest I'd be happy with a stock kernel, I replaced the whole boot.img with one from the stock ROM but that gave a similar error
[Android] dsixda:
Why are you replacing the whole boot.img?? You should only be replacing the kernel portion (zImage).
[Android] vido.ardes:
I thought that was what the kitchen was doin so I'd try something else.
[Android] :
OKay my plan to manually port is going to be the following:

- First I'll start with replacing the rom I want to port's boot.img.

- If that doesn't work then I am going to use the update-script and binary from a rom that works on my phone

- If that doesn't work I'll edit the build.prop to look like a rom's build.prop that works on my phone

- If that doesn't work then I'll start porting over drivers :D

I'll report back if any create a successful boot :D
[Android] localguyincali:
Does anyone have a Good link to a tutorial in how to back the kernal you use into a rom i followed this tutorial http://xdaforums.com/showthread.php?t=1049970

i got it to work but my Wifi wont turn on just has a error when i check mark the box greyed out error, im trying to cook 4.3.1-cfs-nohavs--sbc into my rom..

Thanks hope someone has a solution
[Android] dsixda:
NO no no.. No. like I said, replace the kernel, not the boot.img. You will run into other issues if you do that. You need to learn what goes on inside the system rather than blindly replacing this and that.

The boot.img consists of the following major components:

1) The kernel -- This is specific to only one device (like the OEMXIPKernel in WM 6.x.)

2) The ramdisk -- Can be ported to other devices (like the MSXIPKernel in WM 6.x). BUT you cannot replace the ramdisk of an Android 2.1 device with one from a 2.2 device, if you know what I mean. That will mess things up.

So if you just replace the boot.img with another you will have unpredictable results.

No! You will have symlinking and permissions errors due to missing files in the working folder when using a random update-script. Why do you need to replace the update-script? They're set up automatically when you port the ROM through the kitchen (I'm assuming you're using that method).

Like I said, use the logcat/recovery.log to help you debug. I wouldn't change those parameters until you run into an issue. The kitchen will do the build.prop for you (just the basic stuff to assist in booting, but you may require more.. but bootup shouldn't require anything else usually).

The kitchen does port over the drivers automatically when you port a ROM, if you decide to use the kitchen for that purpose.
[Android] dsixda:
There's a guide in the FAQ for porting a kernel.

Also you are missing wi-fi drivers that are probably under /system/lib/modules of the ROM that has the kernel you want.
[Android] :
Do i need to change the init.xx.rc to init.heroc.rc if it isn't named that in the ramdisk? my device is a heroc so if it isn't that should i change it?

Also i cant' get my phone to logcat on boot :(

And i'll wait to change the build.prop :D
[Android] dsixda:
Replace those .rc file names to match the value found under your ro.product.board in your device's original build.prop.

I've already answered this more than once today ... get the recovery log after you flash.
[Android] localguyincali:
hmm i never touched the wifi drivers in the rom, all i did was extract my kernal file went into kernal folder and copy zImage into BOOT-EXTRACTED folder.

in my kernal ...netarchy-toastmod-4.3.1-cfs-nohavs-sbc-universal-signed/system/lib/modules

i have 4 .ko files i dont know why the wifi wont turn on? unless i copy rest of those folders over to BOOT-EXTRACTED folder except the META-INF one?

EDIT just saw this part..... If the kernel come with other files, such as *.ko files for the /system folder, then copy them to the appropriate locations.
[Android] :
Nvm I got it to logcat, I know how to it just wouldn't but I fixed it :D It was a minor mistype :p

and thanks for the first part :D
[Android] localguyincali:
ok, still not working still getting error when i try to enable Wifi, these 3 screenshots are whats inside my extracted kernal...

View attachment 581298

View attachment 581299

View attachment 581300

Then the other 2 are from i have going on in kitchen

View attachment 581301

View attachment 581302

i havent switched anything yet, my last try i put from my extracted kernal 2 folders which were.. lib and etc packed everything backup and flashed still had same problem, so im still at a loss kernal is there but wifi wont turn on :(
[Android] Droidzone:
wifi "error" = missing module.

Go to the /system/lib/modules dir of the source kernel, copy everything you see there to the corresponding dir of the destination rom.

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] localguyincali:
OK i went into my extracted kernal /system/lib/modules and copy these 4 files into BOOT-EXTRACTED/boot.img-ramdisk/system

as seen here, is this right?

also what about the original files that came with this ROM does anything need to be deleted out of here?
[Android] dsixda:
No... you have to put the modules into system/lib/modules of the system folder not the ramdisk.
[Android] localguyincali:
Sorry i just re read what you said where it goes, i put those files in the ROM directory packing it now then will flash and see

**EDIT** YAY!!!! it worked :D :D :D:) :) :)

Thanks all for the help! my first kernal bake LOL
[Android] dsixda:
Congrats :-)

Finally some good news on here LOL
[Android] Droidzone:
Excellent...

You know, to check out such issues, u needn't reflash the rom. You can just adb push the module, and either restart device or insmod.

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] Faryaab:
please add feature for compiling latest aosp roms from the google android master branch for all supported device this feature will be the BEST.
[Android] shelooga:
q

Everytime I create a rom for my TB superuser fcs if I update any app. Root or nonroot needed. I've tried all three versions of su. Any ideas?
[Android] dsixda:
See post #1 plugins.
[Android] dsixda:
See post #3 - FAQ
[Android] Faryaab:
It doesnt create gingerbread rom.
[Android] dsixda:
Then tell the developer or feel free to contribute a plugin.
[Android] shelooga:
USB debugging is on. Also, its when I update apps whether they require root or not
[Android] dsixda:
Sounds like a signature issue. I have no idea --

Did you re-sign any apps in the ROM?
[Android] dhemke17:
Man. This sounds like you are using the Chain super user instead of the patched version. I have the rmk version of superuser if you want it, just pm me.
[Android] dsixda:
No, he said he tried all three versions of superuser. The kitchen has the patched version.
[Android] Droidzone:
Can you run any app which requires root?

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] dhemke17:
Not sure what the deal with this was, but I downloaded his rom and reflashed the rmk superuser patch and it worked on there. i have been using the .153 version of your kitchen as it serves me well and the patched version from that works great on my rom...so im not sure why it would do this on his rom, but I thought I'd just keep ya up to date on this.
[Android] loganbeaupre:
it works for the Desire HD, so i'm assuming it works for the Inspire 4G? They're like almost exactly the same thing.
[Android] dsixda:
Is it identified as an "ace" under build.prop for ro.product.device? If yes, then you can use it without problem.
[Android] erlucky:
Hi dsixda

but is possible un-pack and re-pack zImage of boot.img??????

Can you add this feature in your programm????

Sorry for my question i'm newbie...:D

Your Kitchen is fantastic......:p
[Android] dsixda:
You mean de-compile the kernel into its source code written in C? And then compile it without a Makefile - which would also require AOSP source code dependencies ;)
[Android] arif-ali:
:D:D:D:D:D:D

I think we all would want that hehe!!
[Android] erlucky:
OK...:p But i can compile Kernel with windows 7???? or i can only use linux (ubuntu).

I have find this guide for Acer Liquid:

1. Download acer's kernel source from acer's website

2. Download toolchain from codesourcery

3. Extract kernel source to a folder and rename it KERNEL

4. Extract toolchain to a folder and rename it TOOLCHAIN ( note that these names are at your choice,these two are only default names)

5. Copy /arch/arm/configs/acer-q8k-al-dvt_defconfig to KERNEL and rename it .config

6. Copy acer_kernel_patch.txt to KERNEL and rename it acer_kernel_patch (without any extension)

7. Patch the kernel ,typing in terminal: patch -p0 < acer_kernel_patch

8. Build source; Just type in terminal: make ARCH=arm CROSS_COMPILE=~/TOOLCHAIN/bin/arm-none-linux-gnueabi-

But if i want modify the zImage or i can only compile (alone) this?

Compile the kernel is only way.....?

Thanks.
[Android] :
that would be pure AWESOME-NESS IF YOU DID THAT !!!! :D:D:D:D:D
[Android] powduh09:
I just setup this kitchen last night using the walkthrough on theunlockr.com... Thinking about trying to either modify one of the many custom roms I have downloaded, or starting from scratch with original source... Anyone have any tips/help to get a noob started?
[Android] jlmancuso:
can kyocera zio work with your kithchen?
[Android] dsixda:
I only know of the devices on the first page. You can try it to see if it works.
[Android] fadimo305:
HELP!? I Installed the kitchen on my Windows 7 Professional PC and everytime I run Cygwin it just opens CMD and immediately closes with some bash error.Fyi it worked for me perfectly with Windows Vista.
[Android] dsixda:
Try starting with a shipped ROM, to understand how everything is created. Don't do everything at once though. Just use the first (basic) menu for your first builds.
[Android] powduh09:
awesome... I'm working on some different things now... playing with the basic commands, changed a few name entries, and now I am looking into trying to add some themes... Trying for my own use for now... but I'm also looking to learn how to do some complete custom roms...
[Android] GazaIan:
cd /gratitude

sweet. awesome. thanks!
[Android] cuttysark76:
I was able to create my first custom ROM with your kitchen! Thx

The device is a ZTE Joe / Vodafone 945http://android.modaco.com/content/other/338564/zte-joe-eclair-rom/

Although APP2SD is added to the ROM I'm not sure if it is working...

Now I'm going to study the Port tools menu!
[Android] dawynkoop:
Having an issue creating a custom ROM for my HTC Incredible. Everything seems to be working fine except the /data/app feature. I enable /data/app in the kitchen, then copy the apk files I want to install to the folder, I build the ROM, but when I flash the ROM it doesn't create the /data/app folder or install any of the apps I copied to /data/app. If I look through the zip file I see the apps under /data/app, they just arent installing when I flash the ROM.

Any suggestions or fixes? I tried searching but search currently isn't working.

Thanks.
[Android] dsixda:
Read the FAQ regarding how to get a dump of the recovery log.
[Android] ab65:
thanks to your kitchen

I successfully made a rom with ubuntu (make me feel like a terminal wizard)

But just to curiosity wen I try to do it with my PPC Mac I get stuck at point 1.

And get this error:

Found system.img

Found boot.img

hboot_7225_1.01.0001_101117.nb0

Adding an update-script ...

Android header not found at start of boot.img

Warning: Android header not located anywhere in boot.img

NON-YAFFS FILE FORMAT DETECTED IN ROM

Fuse installed

Trying to mount the filesystem

Filesystem mounted

File system listed, analyzing

Failed to mount the filesystem: mount point empty

Error: No /system/framework folder found!

I'm using the same update.zip as the one used in ubuntu and there he did the job, so that can't be the problem.

Is there anybody out there with an idea?

(Sorry for not taking the time to read the whole thread)
[Android] powduh09:
Thanks to this kitchen and the GB test leak, I have successfullycreated my first rom... Nothing too much changed... Just added root privilages, superuser, busybox support, moved some bloat apps to data/app, zipaligned, deodexed, added custom boot image and sound, and viola...powduh GB V1.0 was born... Now to figure out how to get my custom boot sound working...
[Android] powduh09:
Edit: just found that super user wasn't working (kept force closing) went back and checked, and I had moved it to /data/app... Moved it back to system/app, and everything's fine... Valueable lesson learned...
[Android] freak69ize:
Ive been messing around with this kitchen but havent reallty made alot of progress yet. I have a HTC Desire CDMA so theres really not alot of choices for me and others of my kind.. and theres really not alot more that you could do to cyanogen with the kitchen that it doesnt already have.. so my question is.. can the porting tools be used to port another rom from GSM to CDMA or a CDMA rom from different devices to my Desire.. and yes i googled and searched the forum and as you can see.. it would take all day to search this thread..
[Android] dsixda:
I don't know, just try it out.
[Android] dsixda:
What's the exact output when you tried the same thing successfully in Ubuntu?
[Android] leith51:
Thank you dsixda I've built my first Modded custom Rom yesterday with your kitchen. It works great.

One question.

How come I can make changes on my phone like removing apps, but when I do the same in the working folder then rebuild Rom and flash it gets stuck on splash screen.

The apps removed have been removed from other roms but they boot fine

Any ideas why the second build doesn't boot?

Sent from Levo Rom V1.0
[Android] freak69ize:
Ok.. will do.. one more question so im not jus fumbling around.. is there a brief tutorial on the porting tools in the kitchen anywhere? I hate asking cuz i know youre prolly a busy man with all this and even get asked the same questions all day long.. and thanks for the kitchen and reply bud..
[Android] dsixda:
Check the guides in the first post.. I am not much of an expert on porting... I just put whatever people tell me that works.
[Android] fadimo305:
I am working on a very important build and can't get a response from anyone on this thread :/...let down
[Android] mskip:
You feel let down because you didnt get a response within 1 day? Did you think that maybe you havent got a response because people just dont know what is causing your problem?

Im sure you have done everything yourself to try and figure out this problem what kind of answers did you get from googling the problem?

Mark.
[Android] dsixda:
Recovery log and logcat.
[Android] dsixda:
Recovery log and logcat
[Android] fadimo305:
Perfect.hi dsixda I can't get your kitchen to run on my PC (Windows 7 Professional) CMD just closes up and all I can barely see it says bash error
[Android] fadimo305:
Actually 2 or 3 days I am trying to get my build finished as soon as possible
[Android] dsixda:
I don't know... it works for me.
[Android] dsixda:
You want to port Touch Wiz to an Evo 4G?? Why?

http://xdaforums.com/showthread.php?t=1057051
[Android] dsixda:
ab65,

When you are using your Mac, what happens when you go into your Working folder and type this:

od -x -A x boot.img | grep -m 1 "4e41"

Can you copy and paste the EXACT output?

Thanks
[Android] ab65:
dsixda thank you for taking time and effort.

2lip:~ agentorange$ cd /Volumes/kitchen/

2lip:kitchen agentorange$ od -x -A x boot.img | grep -m 1 "4e41"

od: boot.img: No such file or directory

od: boot.img: Bad file descriptor

(don't know maybe it's related to PPC I will try later on my friends Intel Mac.

It's just strange to me that linux can read the rom.zip and mac can't. Kitchen it self on mac starts without any error message after setup from FAQ)
[Android] AngelDeath:
dsixda,

Been using your kitchen off and on, but today while using it, I noticed something I didnt before, and thought I would post a suggestion about the kitchen. I notice that obviously we have a folder called "original rom" which we put our rom into, and then press "1" to create a working folder, (Thanks BTW for using my suggestion of being able to rename the folder :)), After the working folder is created, the kitchen re-copies the same zip into the working folder before extracting it, which I think takes more time. Since your extracting the rom in the working folder, couldnt you skip that copy step, and extract from the "original rom" folder and place the extracted rom into the working folder? Just a thought.
[Android] fadimo305:
Well I'm Adventourist and I hear Touchwiz 4.0 is really nice also I love the Epic Colorful menus and vibrant system.

Also do you think that Java can be messing up my kitchen setup and closing CMD ?
[Android] TJinWV:
Check your cygwin directories (bin, etc) and see if they have files in them. Sounds like you didn't install it correctly.
[Android] dsixda:
No no... I said to go into the WORKING folder. That's where your boot.img is. Try it again.
[Android] dsixda:
I suppose I could do that...

I am always finding new ways of optimizing old parts of the scripts (ie. when I was a total newb). I will look into it later. Thanks
[Android] dawynkoop:
I have attached my recovery.log file.

Thanks.
[Android] ab65:
Sorry for being so noob, I hope this time is right

2lip:~ agentorange$ cd /Volumes/kitchen/WORKING_050311_150133 /

2lip:WORKING_050311_150133 agentorange$ od -x -A x boot.img | grep -m 1 "4e41"

0030b70 7cb3 1097 ade2 4e41 dcf7 2df9 c623 eef0

Thanks for your patients
[Android] arvati:
Great topic, must reading one.
[Android] dsixda:
Did you open it up and take a look? I want you to learn what's going on, that's the point. I can't sit around debugging people's ROMs, I have work to do ;-)

EDIT: Why are you installing apps2sd on this device?? I thought it already has a large internal storage.
[Android] dsixda:
You mean it looks like this, with the proper spacing?

0030b70 7cb3 1097 ade2 4e41 dcf7 2df9 c623 eef0
[Android] dsixda:
What's an Adventourist?

Java has nothing to do with Cygwin opening up.. it's a separate application.

Install Cygwin carefully by following the instructions word for word.. don't rush. But it seems like you're in a hurry trying to get something done, which is potentially going to lead to a buggy product. Porting TouchWiz to an HTC device is no easy task.
[Android] ab65:
yeah exactly that way

(today is not my day I can't get anything done right it seems)

and what does that mean?
[Android] fadimo305:
I know its not easy I have never had problems with your kitchen till now.
[Android] fadimo305:
Thanks I will see if files are missing
[Android] dsixda:
It's just trying to dump out specific parts of the file. I use it to figure out the location of certain values in a file.

Macs format the output of the 'od' command differently .. but I had thought I had already taken care of that a couple of months ago.
[Android] dsixda:
Can you send me the link to the ROM please? I have no idea what the problem is. Or just a link to your boot.img.
[Android] dsixda:
Kitchen version 0.160 is now up. Please view the Release Notes in post #3 for details.

Enjoy
[Android] jdwhite87:
I'm wanting to port a cm7 kernel to a froyo sense rom. They are from the same device. Can I do it with this?
[Android] ab65:
Im using the rom.zip out of

RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe

here is a link to the boot image

http://www.mediafire.com/?qfaxa1dxsyygn1y
[Android] dawynkoop:
Yeah, I opened it and looked, it looks like it's not able to mount the data partition for some reason but not sure why.

Apps2SD isn't enabled, it's just the data/app folder so I can add a few pre-installed apps that can be uninstalled later if needed.
[Android] dsixda:
It looks fine to me except that you have bad blocks, which is probably preventing data partition from being mounted.
[Android] TJinWV:
Not trying to be an arse, but the title of the OP needs updated. :)
[Android] dsixda:
Thanks! ;-)