yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
Are you sure you didn't corrupt the ROM (boot.img AND system.img) when you put it in your Mac? Your error message seems to imply that. The boot.img looks fine on my PC (I don't have a Mac), just like any other regular boot.img.

What happens when you type this command on your Mac? od -A n -h -j 0 -N 8 boot.img
[Android] Mikenif:
Im trying to port a kingdom rom to my desire hd.

Ive taken the self-explanatory porting steps and tried to build it without modding anyting. only porting. But no luck it sticks at the splashscreen.

Ive done some reading and seen some tips on using logcat to see whats wrong but theres no feedback at the splashscreen.

Anyone know what im doing wrong here?

[im using Ace_Gingerbread_S_HTC_WWE_2.36.405.8_R_Radio_12.54.60.25_26.09.04.11_M2 as a base and im trying to port Kingdom_Sprint_WWE_0.81.651.0_Radio_1.05.00.0429_NV_SPCS_2.25_0429_PRL21078_test_188785 to my ace]
[Android] dsixda:
Recovery log?
[Android] Mikenif:
Hmm when i dump it its blank.

When it try to logcat i get a message

- exec '/system/bin/sh' failed: No such file or directory (2) -

but the file is present in my kitchen
[Android] freak69ize:
Where did you find these intructions on using the kitchen to port roms? Ive looked all over..
[Android] Mikenif:
its option 19 in the advanced menu of the kitchen :D
[Android] freak69ize:
Oh.. lol i thought you were talking about intructions you found in the forums somewhere.. my bad
[Android] freak69ize:
Silly question.. what do you suppose would happen if you changed a roms boot image with another?
[Android] dsixda:
No no...dump it after you flash but before you reboot. Just read the FAQ.

The error above is because something was wrong with your mount points and /system didn't get flashed. It was asked a few days ago.
[Android] dsixda:
Already asked a few days ago.. just search this thread.
[Android] Mikenif:
OK got it:D

I also included my update-script. Hope you can help me pinpoint where it goes wrong.

I havent modified anything. Its a straight port. Maybe its because the Kingdom rom im trying to port comes in folder format? (boot, data etc)
[Android] dsixda:
Why don't you just open up and read the recovery log you just posted to me. The answer to your problem is right in front of you. I want you guys to learn, not rely on me ;)

To fix it you can remove some components you don't need.
[Android] ldrifta:
sorry if this has already been asked but im running the latest vrsion of kitchen and cant work on a cooked rom.. does anyone kno what im doing wrong? option 11 doesnt even show up in mine.. is there an updated user manual to this?
[Android] trock79:
I tried the porting option and everything seemed to build correctly but when I went to flash I got this error

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

E: Error in /sdcard/inc_signed_050411_223603.zip

(status 7)

Installation aborted
[Android] dsixda:
That's because you didn't unzip the files properly. You don't need a user manual for that. Make sure you have a scripts and tools folder unzipped.
[Android] dsixda:
Did you check recovery log?

Or convert to update-script or Google it.
[Android] trock79:
Thanks for the quick response. Yes the first thing I always do is Google my issues. All I found was issues with recovery version. I know mine is good. The Rom I am trying to port is a gb Rom and between that and my current recov ver using edify I'm not sure that is it (not saying that I won't try it). I will look at the log and see what it says first. Thanks again.
[Android] Mikenif:
Thanks mate! I didnt notice it running out of space:p thought there was a problem symlinking

Its booting fine now
[Android] ab65:
I've treid the kitchen on a Intel Mac from my friend and it runs and creates a signed zip without any problems.

I'm using a PPC architecture Mac and can't use the intel binary code, I'm convinced that's the problem.

Thank you for all your efforts made in this matter.

respectfully ab65
[Android] dsixda:
Hmmm I was never aware of these slight differences! But it would make sense.

What's the OS version?
[Android] dsixda:
Let us know if you find an issue worth noting .. thanks
[Android] ab65:
On a PPC mac you can only run version 10.5 leopard

Intel mac's are running 10.6 snow leopard

But the PPC is a outgoing model it will fade away in history Apple only uses Intel today. So no big deal about this.

once again thanks for your efforts

respectfully ab65
[Android] tommytomatoe:
Dsixda and company,

any one know for sure if the latest kitchen works on ubuntu 11.04? I have the kitchen on my hackintosh but i am preparing to do a clean reinstall of Mac OS X. I figure ill just convert to Ubuntu for the time being. I have a copy of ubuntu 10.04 somewhere on my external hd but the latest one is 11.04. Thanks gang.

T
[Android] klquicksall:
It works. I cooked up a rom on the new version.
[Android] tommytomatoe:
Thanks man for the quick response. I was gonna do it anyways...but figured I'd ask.
[Android] AngelDeath:
I have a problem, which I cant seem to figure out, and any help would be great, because at this point after 2 days of doing this, I am wondering if it might be the kitchen, dont know so I thought I would ask.

I took a rom (HD2 imilka's 0.1 dblshot sense 3.0), its setup as a CWR used by magdlr, I put it into the kitchen, made a working folder, and then saved it making sure it worked, did it, booted fine, no problems, then added a couple of apks I wanted in, re-cooked it, again fine no problems. Here is where it makes no sense:

I then decided to switch my phone to clk, so I flashed clk, did all the steps, everything fine, then I flashed this rom, knowing it wouldnt work cause of the boot.img, so I followed the directions after flashing the rom, and ran the one line command in fastboot, rebooted the phone, perfect. So then I decided to re-cook the exact same rom, but this time with a clk setup, so I picked build rom, chose #2 for clk, and it went on to cooking, rom done, flash it, bootloop, didnt make sense, looked thru the recovery nothing out of the ordinary, everything went fine, so deleted the work folder, took the working cwr zip, re-did the working folder again, picked clk rom again, cooked. ran it again, bootloop, checked the recovery log again, nothing. Now getting frustrated, took a clk updater-script from a different rom and compared it to the one the kitchen made (just to see if I saw anything different) nothing, even the assert command line for the boot.img is there. re-cooked it a 3rd time, flashed it, boom it worked, rom booted in clk format. thought great, so then I decided I wanted to change somethings in the rom, just testing, expecting some of the changes would fail the rom, which it did, but I had made a backup of the working folder just for that reason. So took the backup working folder, deleted the current one, and cooked it again, again bootloops, and every single time since then it does the exact same thing, first screen of android fine, gets to the second screen (boot animation) and about 1min it goes into rebooting the boot animation. So finally, I re-cooked the rom using the same working folder and option #1 (magdlr with boot folder), cooked, flashed the rom, and then used the one line command in fastboot for the kernel, phone booted no problems.

What the hell am I missing or doing wrong?!?! How is it that I get it to work a couple of times, and the rest fails? Is it me, is it a kitchen bug? Am I crazy? And each time before flashing the rom, I do a data/factory erase, a boot erase, a system erase, and a davlik erase.
[Android] jdwhite87:
I got a rom ported from legend to aria. Everything works but Bluetooth and wifi. Where is a good place to learn how to load the drivers? I've been searching forever and am coming up empty :confused:
[Android] andyks:
Adding RIL and drivers

Howdo i add new RIL and drivers to a custom rom with this kitchen?
[Android] lynxboy:
I'm having the same issue with the data/app directory not installing correctly with the latest CM7 source. For any builds prior to Nightly #63 5th May (Move to EXT4), the function works as it should, upon boot all apps are present. Using the latest source, the apps don't appear upon boot. I've tried to locate my recovery.log in the /cache/ and /tmp/ but constantly get "No such file or directory" message. Any ideas or could anyone using the latest source replicate my issue?

Thanks in advance.

Regards.
[Android] dsixda:
Well if it's not there you need to do an "ls" to find it. On my Nexus S it is named /cache/recovery/last_log
[Android] :
I made the update you recommended to the update-script and got the following error:

I//system/xbin/busybox( 41): reloc_library[1245]: 48 cannot locate 'sysinfo'...CANNOT LINK EXECUTABLE

I/logwrapper( 41): /system/xbin/busybox terminated by exit(255)

I then noticed that there were a lot of commands in the update-script from my last related successfully flashed and booted ROM, so I added these into my update-script for the one I am having trouble with and got the same error:

I//system/xbin/busybox( 41): reloc_library[1245]: 48 cannot locate 'sysinfo'...CANNOT LINK EXECUTABLE

I/logwrapper( 41): /system/xbin/busybox terminated by exit(255)

In addition to the update-scripts being different, I noticed that the firstboot.sh are different too.

I need to crash though.

I am definitely into trying to figure this one out.

I am grateful for your help.
[Android] dsixda:
Me too, I would like to figure this out, but I am also tired and it's almost 3am :-)

Don't forget to read my other reply as well, regarding init.rc.
[Android] :
Yup, I noticed that as well.

Odd.

Maybe another approach is to try modifying the init.rc in the ramdisk and remove that command related to busybox. I am just trying different things to see what works without really understanding the pieces.

Wierd how they can boot the beta on 32B.
[Android] dsixda:
That command is trying to initiate the system/etc/init.d folder, which is a folder that lists a sequence of bootup scripts:

00sysctl

01coldboot

02apps2sd

03userinit

04compcache

99complete

So, if you open up the 02apps2sd and 03userinit, you'll see that the busybox stuff is also in there (might be the reason for the errors you mentioned in last reply).
[Android] :
I am updating the devs in the ROM thread. There may be a simple explanation or not. They are getting some seemingly random crashes and reboots so we'll see what they say.
[Android] dsixda:
Ok cool, I noticed just now.

Keep us updated if you find a reason. Thanks
[Android] :
It drives me nuts going to bed without fixing a problem like this, but I gotta crash.

See what we can do tomorrow.....thx
[Android] dsixda:
I just noticed a mistake in 0.41 when porting ROMs -- the boot.img was being copied to /system/lib/modules. This issue has been fixed in the new version, 0.42. Please make sure you download that one. Sorry for the inconvenience.

I have made a couple more updates as well.
[Android] :
I noticed that about the boot.img. Thanks, I downloaded your latest release and have resumed testing.

No matter how I build the ported ROM, I still get the same busybox errors.

I don't have time now, but I will look further into it.

I see 2 options:

(1) Add all of the missing busybox parts or

(2) Remove references to busybox

It baffles me why the ROM boots on the 32B G1 and mytouch but not the 32A Magic. Why don't they have issues with busybox on first boot?
[Android] dsixda:
So they got it ported to the 32B (myTouch) without problem?

Maybe the scripts check for a particular hardware version somewhere?
[Android] :
Trying to add in what is needed for busybox seems hopeless unless we get a dev that knows more about it.

They pulled the busybox stuff in the xbin folder in their ROM and somehow they can boot it no problem.

Something in our port is pointing to busybox. I think finding that seems like an easier and then see if we can remove it and boot.

What is odd is that references to busybox are everywhere in the ROM including the permissions file shell script in the data folder.
[Android] dsixda:
You know, maybe others don't see that issue because they flashed 2.4 Stable before and didn't wipe it when they flashed the Beta. The 2.4 has busybox under /system/xbin already. Maybe it got copied to /data after it was flashed, so it was still there later when the beta got flashed?? I don't know.. just throwing around ideas.

The link I showed you yesterday with the Cyanogen ROM had the same error messages as yours, and they had to flash an earlier version of the ROM before flashing that ROM, to get it fixed!
[Android] dsixda:
BTW there is no system/bin/sysinfo or system/xbin/sysinfo file in that ROM, so that's why it is giving you that error.

Plus I can't find where sysinfo is being referenced. None of the files in the ROM or its boot.img ramdisk folder contain any mention of it!

BTW are you copying the boot.img or the boot.img-kernel from the 32A?

If it's the boot.img, then you have to be careful that you don't have any scripts in there that refer to stuff that are not in the 32B ROM.
[Android] :
I could try flashing 2.4 and then the new beta over it, but the devs are saying to do a full wipe anyway before flashing 3.0 so it's not adding up.
[Android] :
I realized that but....

...but I did not think of that.

Good catch. I was copying the boot.img instead of the boot.img-kernel. There are init files in the ramdisk that may be the culprit. They point to busybox all over the place. Haven't found the sysinfo reference but would not be surprised if it's there.

Maybe I will extract the boot.img-kernel from the ported 32A rom for the new radio and try to re-package it with the ramdisk from the original ROM. With luck there won't be some incompatibility or conflict.
[Android] :
Nope....the ramdisk is identical in both the original boot.img and the ported boot.img.

The only differences in the boot.img files are in the boot.img-kernel.
[Android] :
It would be nice if there was a defanged base for AOSP 2.1.
[Android] :
I got the problem fixed or found a good enough work around.

(1) I set up a working folder for the ROM I want to port using #2.

(2) I used MAGIC Port to create the boot.img, wlan.ko and build.prop files.

(3) I copied the files from the MAGIC Port over the same in the working folder.

---none of that changed from my earlier attempts---

(4) I added the permissions into the update-script for busybox

set_perm 0 0 04755 SYSTEM:xbin/busybox

(5) I copied the entire /system/xbin folder from a ROM that works on the 32A Magic new radio 6.35 (on the phone model to which I wanted to port) to the ROM in the working folder.

(6) I copied a version of the busybox file that Haykuro has posted here

http://android-dls.com/files/linux/busybox over the one that is in the /system/xbin that I just copied to the ROM in the working folder.

(7) I then ran #99 to build the update.zip file, wiped and flashed.
[Android] dsixda:
Good work! Is there anything that my kitchen should check for when porting, or is it just "one of those things" that we can't do anything about .. unless we know how to fix it manually?

What's the difference in this new busybox you have mentioned?
[Android] :
I'm not sure at this point what the difference is in this new busybox file from Haykuro's link, but the file is ~200 kb larger than the one I replaced. I need more tweaking and analysis. However, in adb logcat, the boot process did not stop when an error related to busybox occurred. With the new file there were some errors, but the boot process continued anyway.

Also, I think a crude check for your kitchen would be to verify whether there is a busybox file at all. If there is no busybox file (you could also check for other contents of the /system/xbin/ folder) then your ROM could maybe step through the items I outlined or if that is too much you could provide the user with instructions????

I am checking some of the ROMs I could not port successfully previously. I am curious to see if busybox was the cultprit. I have been searching google and it seems busybox is a key feature for a lot of ROMs.

So I did a quick check in 2 of the Donut ROMs I could not port (SuperCSDI there are a few verions out there) and they are missing busybox.
[Android] lynxboy:
Thanks, that was it, I was following the FAQ for Amon_RA! Anyway, here is the log. I'm pretty sure it's to do with the switch to EXT4 but I don't know how I would go about manually changing the mounts for /data/app. I've looked through the updaterscript and can't find anything.

Thanks for the swift reply dsixda!!

Regards.

EDIT: So it is a mount issue and must be related to the switch to EXT4. On latest source I see this in the log:

mount: failed to mount /dev/block/mmcblk0p25 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p25 at /system:

On previous builds I get no problems and log shows this:

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
35760 inodes, 142847 blocks
7142 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
5 block groups
32768 blocks per group, 32768 fragments per group
7152 inodes per group
Superblock backups stored on blocks:
32768, 98304
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Creating journal inode: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p25: 11/35760 files (0.0% non-contiguous), 6357/142847 blocks
about to run program [/tmp/check_data_app]

Any ideas on how to resolve?

Regards.
[Android] T-Macgnolia:
Ok guys I really have tried searching to answer this for myself. It is now 8:55 a.m. and I started trying to install and get the kitchen up and running around 10:00 p.m. last night. I have did two separate searches and each one came up with 40 pages I will be honest I only looked over the first 20 pages of boht my searches but could not find an answer. I would Google it but I think my problem is specific to cygwin.

This is my problem I got the cygwin_packages installed, I have tried multiple times to reinstall it too. But when I click on the icon on my home screen I get the below error message.I have even re downloaded the cygwin_packages.zip twice and still the same thing. Can some one please point my in the right direction here, or tell me where to get the cygwin1.dll file and where to place the dang thing once I get it.

Thanks a ton
[Android] lynxboy:
I can't help with Cygwin but have you not tried another method, such as a VM Ubuntu install?

Regards.
[Android] T-Macgnolia:
No I have not tried that yet as I was really hoping to use Windows but I probably will try the other method if I can not find a fix for what seems to be a small problem just don't know how to fix it yet.

Plus I have to use my HD2 to WiFi tether while I am at home, and seeing as I only get a Edge signal at my house my internet at home is slow. So I will have to go to a WiFi Hot Spot today and download the stuff to try the other method mentioned in the front of the thread.
[Android] dsixda:
What are the differences in the 'mount' commands between the original updater-script (in the ROM you downloaded) vs the updater-script in the script you produced with the kitchen?

Also you might have an outdated recovery menu.
[Android] dsixda:
No... I wouldn't waste time trying to use another method while the first method is unresolved.

Just follow the instructions again from scratch and read them carefully.. I have never seen anyone with this problem. This is a generic cygwin issue so you should probably consult Google search for details.
[Android] lynxboy:
Recovery is up to date. I've been checking the updater-scripts between the differing zip files and it seems that the kitchen is failing to enable the data/app funtionality when using latest CM7 source as a base. I've tested my own compliled builds and the latest official nightly. While the kitchen creates the data/app directory in the working folder, when checking 'Working folder information" it returns that data/app functionality is NOT enabled. Comparing the updater-scripts confirms this as the following code is completely missing from the zip produced by the kitchen.

package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");

I'm going to look into it further, i'll try making manual adjustments to see if I can overcome the issue that way.

Regards.

EDIT: SOLVED! Will post instructions how to resolve it soon. The kitchen isn't creating the correct instructions in the update-script when using the latest CM7 2.3.4 Nightlies. I think the mount "ext4" instructions of the original update.zip are throwing it off?? Maybe you could take a look?

FURTHER EDIT: For those struggling with the data/app issue using latest CM source follow these steps.....

Enable /data/app in the kitchen.

Check /data/app is present in the working folder

Return to Kitchen and check working folder information

If data/app is enabled you are ok!

If not copy and past this script to the update-script in your working folder.

delete DATA:app
copy_dir PACKAGE:data DATA:
set_perm_recursive 1000 1000 0771 0644 DATA:app

Check /data/app enabled in working folder information (it should now be ok)

Place Apps in /data/app

Build ROM from working folder.

Hope this helps some of you.
[Android] dsixda:
Just send me a direct link to the original ROM.. I'll take a look at it later. Been losing a lot of sleep lately by working on suggestions for the kitchen. I think I'll take a break for a while. But just send me the link anyway. Thanks
[Android] lynxboy:
http://mirror.teamdouche.net/?device=ace

Issues are with the latest nightlies. Test 64 and compare with Nightly 57. To be honest, it's nothing major. Now I've figured it out, I'm happy to manually edit the update-script but obviously it's worth investigating for future users.

Thankyou for giving me the hint about comparing the updater-scripts!

Regards.
[Android] dsixda:
Thanks for pointing out the specific files. Very interesting.. I see a couple of issues. But no worries, I'll get something fixed in a few days.
[Android] pimpmaneaton:
Help Please.

Hey everyone just hoping to get a little help here. I'm porting the RCMixHD rom to the Desire Z and using the kitchen all seems to go well but during install get status 7 error.

mount() expects 4 args, got 3

E:Error in /sdcard/download/RCMixHD_PORT_2_Vision.zip

(Status 7)

Installation aborted.

There are my first few lines in update-script

show_progress 0.500000 0

copy_dir PACKAGE:data DATA:

set_perm_recursive 1000 1000 0771 0644 DATA:app

format ext3 EMMC /dev/block/mmcblk0p25

show_progress 0.500000 40

copy_dir PACKAGE:system SYSTEM:

I'm guessing it is the mount point being discussed but kinda a bit new to this. Could someone possibly tell me what the mount should be in the updater-script. Thanks for and info.

Also does the Rom need to be Signed?

Okay got past the mount() expects 4 args, got 3 by changing ext3 to ext4 in update script. But now I have a new error of

E:Can't open /sdcard/download/RCMixHD_PORT_2_Vision_Build2.zip

(bad)

Installation aborted

Damn Getting Closer.
[Android] dsixda:
You need to convert it to updater-script. The kitchen didn't catch that case and should have done it automatically. I'll fix that when I am in a slightly less sleepy state.

If you're not sure about something just use the defaults (signing) .