yashsingh1/xdaforums huggingface dataset:
[Android] colonel_lp:
yes..

Extracting contents of system.img ...

scripts/make_kitchen: line 100: ../../tools/unyaffs_files/unyaffs.mac.new: Bad CPU type in executable
[Android] looktall:
sorry, yes, i am using cygwin, with win7.

update-script.zip is attached.

but if i understand you correctly, if i remove line 10 from the update-script in my working folder and then re-create the output_zip file, the rom will work?
[Android] dsixda:
Ohh ok.. you should have told me that before ;)

I'm at work right now, but perhaps a Google search can help you find what the reason for that error is. Also, you said your gcc is messed up? Why? Do you have a faulty install of Mac OS?
[Android] dsixda:
Yup, the error happens because update-script is performing operation on a file that doesn't exist. So if you remove the line, it should be ok. Also the kitchen has a hack for libA2DP.so in Cygwin, so it will create it anyway during the flash procedure... so you shouldn't be losing any functionality.

Thanks.. Will hopefully look at it during my lunch break in an hour. (On second thought, it's a beautiful day outside :D ..)

EDIT: Oh wait, sorry.. Don't remove that line. That line is actually the hack I put in. That's the one that worked on the Tattoo, but looks like it is not working on yours. Give me some time to figure it out. Can you tell me if you have a "liba2dp_upper" folder under your WORKING_*/system directory?
[Android] looktall:
yes there is.
[Android] dsixda:
Can you do a search under your working folder for liba2dp*.so, and let me know where they all are?
[Android] colonel_lp:
sorry, i didnt see the error until you asked...did a google search and it brought me to my post.. haha... and something about 32bit 64bit... i dont have a 64bit core...

i believe my gcc/mac install is fine... all the errors were related to the unyaffs.c file..

thanks for your help anyway... i will send a donation your way later..
[Android] looktall:
i got two results back.

liba2dp_upper.so in a folder of the same name in /system and liba2dp.so in a folder called liba2dp_lower in /working_*

i did the same search on rom's that have installed fine and i got the same results.
[Android] colonel_lp:
many many thanks... my install of xcode was f***ed.....

rebuilt unyaffs and all works fine now..

cheers..
[Android] dsixda:
Cool... Do you have 32-bit or 64-bit system? Is there something we should revise for the kitchen?
[Android] colonel_lp:
macbook pro... intel core duo (32bit)
[Android] dsixda:
Ok, how about I make this modification to the kitchen:

If, after making the working folder, the "system" folder does not have an "app" folder underneath, then we will need to re-compile unyaffs and then try again?

Was this a similar situation and solution to yours?
[Android] colonel_lp:
exactly what happened.. (infact, there were no folders at all in system)
[Android] dsixda:
In my case, sometimes it creates the "customize" folder, and that's all. Another time, with another ROM, there was only a build.prop! So for now, we can use the "app" folder as the error condition.
[Android] dsixda:
Ok, thanks.

BTW, the libA2DP.so is an important file, so if you don't have it copied (ie. if you delete it from update-script) then the device will not boot (usually).

Can you do me a favour ....

After you flash it and get that error message, are you able to do an "adb shell" into the device?

If so, can you do a "cd /system/lib" and then view the contents of the folder with "ls". I want to know if liba2dp.so and libA2DP.so are already there or not.

Thanks

EDIT:

I'm including the problematic line (in bold) from the update-script, if anyone is interested in sorting this with me.

Basically, all it does is create /system/lib/libA2DP.so (but a symbolic link) and /system/lib/liba2dp.so:

# liba2dp.so duplicate filename hack for Cygwin
[B]symlink SYSTEM:liba2dp_upper/liba2dp_upper.so SYSTEM:lib/libA2DP.so[/B]
copy_dir PACKAGE:liba2dp_lower SYSTEM:lib

The line in bold gave the following error message on the Magic. However, this fixed the non-booting ROM issue on the Tattoo and there was no error.

E: can't Symlink /system/lib/libA2DP.so
E: failure at line 10: symlink system: lib/libA2DP.so

installation aborted
[Android] dsixda:
For the above issue, I think the problem may be solved with a script that is called during the flashing, that will copy the two files to the correct locations. I will test it tonight on my Nexus One (obviously to a limited extent, because it doesn't have this problem) to ensure the files are copied properly.
[Android] looktall:
i can adb shell to the device, but i cannot get to the lib directory. mainly because it does not exist. :/

C:\Documents and Settings\user>adb shell
/ # cd system/lib
cd system/lib
/sbin/sh: cd: can't cd to system/lib
/ # cd system
cd system
/system # ls
ls
app build.prop etc framework
bin customize fonts lost+found
/system #
[Android] dsixda:
TMP (/tmp) is a temporary partition on your device used by the updateR-script (Edify). It is *not* a folder in your ROM.

The update-script (Amend) is not able to use it ... that's why the kitchen told you it will later be converted to updater-script when you build.
[Android] pjgowtham:
I m just porting a ROM from one device to motorola defy. What is the main thing i should do first and by the way what are the .bin files . Are they drivers??

which one i should use as a base??

The modded other device's rom

or

MY current working Rom
[Android] dsixda:
Just run the porting tool, it will tell you what to do and explain what it will try to do.

Motorola Defy has a locked bootloader so I don't know how far you'll go with this exercise, unless you remove the boot.img before you build.
[Android] pjgowtham:
i ll try doing what you said
[Android] pjgowtham:
ive followed ur porting tools

i get an following error during flashing

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

E:error in sdcard/ROM.zip (status 7)

installation aborted

and u told me to remove boot.img

after i removed boot.img after extracting the original rom ,it goes back to the porting tools screen without doing anything
[Android] dastin1015:
Remove the boot.img from the finished product I believe. Also I believe the Status 7 error is caused by the use of an incorrect update binary. Use the original update binary that was used with your original ROM.

Sent from my Hero that never dies! ;D
[Android] rsxtypes72:
hey dsixda,

Just wanted to let you know that for the vision you can use either ext3 or ext4. Phone boots just fine with either one. I used ext4 on my edify_defs.

Thanks for the update.
[Android] pjgowtham:
hello guys i get an error during my flash

I m using moto defy and i tried to port sense from salsa to defy

i used the porting tools in the kitchen

i removed the boot.img and replaced update binary from the original working rom

i receive the following error

format() expects 3 args, got 2

E:error in /sdcard/sense.zip

(status 7)

Installation aborted
[Android] dsixda:
No no... I said to remove it before you *build* the ROM.
[Android] dsixda:
No don't touch the update-binary when porting, the kitchen will add the correct one depending on what the new updater-script will look like
[Android] dsixda:
Exactly, you manually changed the update-binary when you shouldn't.

Let me know what happens when you finally manage to flash it properly.
[Android] dsixda:
What did you use as a base ROM?
[Android] PalmerCurling:
i am running linux mint debian.... would that work, or is that my problem right there?

sorry you had to get out of bed! i was on xda on my phone, couldnt really find links, xda was giving me fits. i forgot about tapatalk..... oops lol
[Android] GazaIan:
Available ROMs:

(1) Sensored_Blizzard V0.9_signed.zip
(2) GB-Sense-Glacier-Leak.zip
(3) MIUI.us_glacier_1.6.17_Eng_Deo_ZipA_Signed_option94.zip
(4) Honeysense HD 6.0.zip
(5) HoneyMIUI1.0.zip
(6) WORKING_honeymiui

Enter selection number (default=1, cancel=0): 1

[B]scripts/choose_rom: line 158: [: original_update/Sensored_Blizzard: binary operator expected
You did not choose a ROM
Quitting and cleaning up folders ...[/B]

Press Enter to continue

Oddly enough, this has happened frequently in this version. Changed the name of the .zip to SB, now it worked fine. Why is that?

EDIT: And again, this has happened with a Flyer ROM I tried to put through:

Available ROMs:

(1) GB-Sense-Glacier-Leak.zip
(2) MIUI.us_glacier_1.6.17_Eng_Deo_ZipA_Signed_option94.zip
(3) sb.zip
(4) Honeysense HD 6.0.zip
(5) HoneyMIUI1.0.zip
(6) WORKING_SensoredBlizzard
(7) WORKING_honeymiui

Enter selection number (default=1, cancel=0): 4

scripts/choose_rom: line 158: [: too many arguments
You did not choose a ROM
Quitting and cleaning up folders ...

Press Enter to continue
[Android] GazaIan:
This may may have been from weeks ago.. but Downloading and install OpenJDK 6 deom Ubuntu Software Center works fine. Now I don't know if its the JDK or my computer, but everything happens fast as f*ck, at least 20 times faster than it did on Cygwin and 10 times quicker than the problematic 64 bit version of Ubuntu.
[Android] dsixda:
No problem, I'm not an operating system expert so I can't answer your question about Mint.. but someone once said he ran the kitchen fine with it.
[Android] dsixda:
You have spaces in your ROM name, remove them. This question pops up every couple of weeks ;) Unix systems in general are not very friendly with spaces in file names.
[Android] tommytomatoe:
You're right about spaces. I'm having a terrible time making my script work for spaces on the name of apk. I might just have to use sed to add a "\ " in place of any spaces in the name. It's something to consider but I'm not sure how well it work.
[Android] dsixda:
Why do you have spaces in the name of the apk?
[Android] dsixda:
Do you have a fool-proof procedure (for 64-bit and non-64-bit Ubuntu) that we could replace the current section of the FAQ with?
[Android] pjgowtham:
Before building the rom what should I remove?

Should I remove both the boot.img on working as well as porting roms

When I remove boot.img on the working folder it does not continue further and returns back to the option selection screen when we select porting tools

How to remove boot.img ? I can't remove it after it created the working folder

Should I remove it on the zip itself?
[Android] dsixda:
Dude.. pay attention to what I said before. Just remove the boot.img right before you *build* the ROM (OPTION 99). Don't remove it from the ZIP or after extracting or whatever. The kitchen will take care of the rest.

What do you mean you can't remove it? Select it with your mouse and press the Delete key on your keyboard.

I also don't know how much success you will get with this exercise... porting Sense to a Blur device is no easy task.
[Android] tommytomatoe:
A buddy of mine sent me a bunch of apks he had and many had a spaces in it. Its not something I would use but just in case someone tries to use my tool to decompile an apk with spaces in the future, it will be ready for it.

Or, I can just say make sure there are no spaces and call it a day.
[Android] Namit1994:
Thanks for this kitchen. Dsixda. I ported a sense eclair ROM to G1. Now the only things that need fixing are LEDs and backlights, wifi, and it can't detect my sdcard. Any threads to point me to the right direction? And any thread that will teach me to make the ROM faster?
[Android] jomeister15:
Thanks again for the kitchen dsixda. I have a couple of questions: 1.Do you think there will ever be a point in time when the kitchen will be able to edit updater-scripts? And, 2., in the meantime, do you have any advice as to how I can edit it (it being the updater-script) to give my rom wipe properties without the kitchen?
[Android] Namit1994:
Just add the option to wipe when it is update-script and then use the options to convert it to a updater-script.
[Android] dsixda:
Just read the sticky thread posted by Cyanogen. I'm not a ROM expert and cannot give lessons on how to customize a ROM in this thread, I just write the scripts.

I have answered this many times -- the answer is no. Again, see the FAQ for the complete answer.

Correct.
[Android] dsixda:
Actually, I have a fix for this. I just needed to fix two lines and your problem will now go away. See version 0.168.

This was a bug that was introduced in 0.165 when I allowed support for old working folders under original_update. The kitchen recently has become so complex that all of the newer features always seem to break existing features ;-)
[Android] pjgowtham:
@dsixda

I did what u said. I removed boot.img at last and i tried it on my phone

I didnt convert updateR-script to Update-script

When i convert updater script to update scripts, symlink takes more time and it is just processing for a very long time

I get an following error during my flash

Welcome to salsasense 1.3!

assert failed: getprop("ro.product.device") == "

hero" || getprop(ro.build.product") == "hero" |

E:error in /sdcard/salsasense.zip

(status 7)

Installation aborted
[Android] anryl:
remove the first assert line that's checking device :cool: from META-INF/com/google/android/updater-script then it will work
[Android] pjgowtham:
I did what u said

I get the following during installation

Copy system

..........................................

symlinking busybox

..........................................

symlinking toolbox

..........................................

Symlinking kernel modules

..........................................

Setting permissions

..........................................

Writing boot

..........................................

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

(status 7)

Installation aborted
[Android] dsixda:
Just remove that line at the top then.. :P

If you followed the default method and chose to convert the updater-script then you wouldn't have had that issue.
[Android] dsixda:
Like I said, you didn't convert the updater-script. Hence the script didn't remove this line when you removed the boot.img. :P

You don't know what you are doing. DO NOT port unless you know how to build a regular ROM.
[Android] pjgowtham:
I got your thing.....

the kitchen does well with update script and the kitchen hates updater scripts

i m not able to convert updateR scripts to update scripts...........it freezes on symlink (this may take few minutes)

Because of that i m unable to convert...i m using cygwin in windows

I have learnt many through your kitchen........i ll improve as i practice with it.

I can improve only with your help.... u r my only hope...i request u to hlp me with this

installing ubuntu

and i ve learnt editing update scripts

a small question...........will these roms brick in such a way that i cannot restore my phone back??

And after i flash salsa sense i lose my recovery and my phone gets into bootloop. There is a backup.sh script and file....should i have to restore that manually ???

is it a recovery thing??
[Android] pjgowtham:
Its really annoying

I just managed to get into bootloop and managed to delete recovery many times

hmm...........need a real testing device.

dsixda.......you are really brainy.....kitchen is amazing.....motorola is going to unlock its bootloaders.......we ll wait till that

I managed to edit updateR scripts manually but resulted in fail..........no init boot and no 2nd boot working.........

Going to turn myself to normal and i am going to stop giving annoying stress tests

I ve flashed more than 20 times........but i m sure that i have learnt a lot of stuffs...by the way thanks for ur help.................i have lots to ask you.......may i know ur email so that i can chat with you....:).............plzzz

Dont think i m much old and feeble.Started learning about android 2 weeks ago........
[Android] dsixda:
What do you mean 'it freezes'? How long did you actually wait? If new progress dots are still appearing then the script is doing its job.

The script also has a protection mechanism in case there are syntax errors in the user's original updater-script's symlinks, so that it exits and prevents an endless loop.
[Android] dsixda:
"I'm 17, male, new to Android, would love to chat." Sorry I don't do online dating, I'm married ;) :)

Just kidding. Anyways, 17 is old. At least old enough to be able to read the replies I sent the last two days:

Also if you need more help just ask in the Chef Central forum. There are lots of helpful people.
[Android] pjgowtham:
Hey not for dating at all.......i love techs........i hate people going for dat....:D:D:D:D:D:D

Dating is something which rich people do

The dots are going and going and going for 4 to 5 lines...didnt finish waited for half an hour..(symlink)

pjgowtham@gmail.com

i m 17 means i have still lot to learn......and i need a real teacher.........u r a teacher to me........" Dating a teacher ".........doesnt that sound funny....ha.ha.ha

I am no engineer......i am a medical student studying in INDIA...........1st year

when u die...................sell your brain to me man............

And to compensate for spamming this much

Some people are trying to port sense to defy there and they just craeted some sbf files fot that.........i m not sure of what they are doing

how to clarify my doubts???

Please give me your google email id
[Android] mike1986.:
@pjgowtham you should be called "the dots-man" :D Can't you write normal post instead of typing hundreds of dots? It will be much easier to read and it will prove that 17 can be mature enough to use internet forums.
[Android] leith51:
@pjgowtham

Dude are you for real??? Do as suggested start small use a Rom designed for your phone stop trying to port something you obviously don't know. I have been building roms for only a short time about 2months, but it took a lot of reading for over 6 months before I started and now I have a great Rom(so I've been told) and have a decent following, but yet I still have not attempted to port anything as I know my knowledge is not good enough yet.

You admit you have been doing this for 2 weeks and I don't doubt you are intellectual. But please please please take this suggestion stop spamming this thread and stick to building a Rom from base and stop trying to port, take some time and learn how to port then try again. As it has been said by the kitchen master himself start with the basics and work your way up

Sent from Dogma v3.0.4 ext4 built by me
[Android] pjgowtham:
Guys..

I wanna learn by practical methods and have no belief on theoretical things

I know only about updater scripts, (edify ,amend) and editing them

I know some basic things like custom recovery and other things

I had a small play with the kitchen

Learnt many fro that

I have stopped porting or creating ROMs because my defy is just 2 months old and i am not ready to lose it .I cannot tell me as a beginner but as an intermediate fellow.

And i will stop using dots on my text. Thanks for your reply
[Android] koohkoohbird:
But dots. are so fun
[Android] leith51:
Practical methods and no theory but you say your a medical student I think theory is very important without it there would be no practical

Sent from outer of space
[Android] pjgowtham:
You are right.....theories are the basement........
[Android] dastin1015:
Just start slow. Learn what files do what in ROMs, understand how things work and then it'll come naturally. I didn't even touch the advanced section of the kitchen until about a month. And now that I learned how it worked, I got a working port of Honeycomb on my device.

Sent from my Hero that never dies! ;D
[Android] pjgowtham:
Ok...where should i start??...........tell me an website.........from which site u learnt everything??.............should i want some programming skills...........i know some updater scripts functions........is that enough??

From which site u learnt everything??
[Android] dastin1015:
Oh I still haven't learned everything. I'm still learning. I taught myself by looking in the custom ROMs themselves to learn where certain files go and what the files pertain to. Also try wiki.cyanogenmod.com cause there is a lot of info there. I also learned a lot by learning how to compile ROMs using the cyanogenmod repo. I don't know any programming whatsoever, but I'm going to college for that.

Sent from my Hero that never dies! ;D
[Android] pjgowtham:
U learnt by extracting the zip file and looking at the files......and googling it......rite??
[Android] anryl:
:D:D:D:D:D:D:D i know just one :cool::cool::D:D:D:D:D:eek::eek::eek:

srry m8
[Android] pjgowtham:
U are a recognized developer na...........so write everything and give me..

or give me the site.

pjgowtham@gmail.com
[Android] dsixda:
@pjgowtham - don't post your email address on a public forum

Can you post your updater-script in an attachment here? I don't know why it takes 30 minutes to convert, unless you are using a Pentium 1 or there some big flaw in the original updater-script.
[Android] pjgowtham:
http://www.multiupload.com/NF383HEQEV

this is the updater script file
[Android] rsxtypes72:
I used PC10IMG_Vision_Gingerbread_S_TMOUS_2.13.531.8_Radi o_12.52.60.25_26.08.04.30_M3 that was posted by football as a final GB for G2.
[Android] dsixda:
Arghh.. don't post to Multiupload, Opera Mobile has issues downloading it. It's only 11KB...just attach it here like I told you, or paste it to pastebin.com. Thanks
[Android] NinjaWolf:
@Dsixda:Version 0.168 is broken, menu just opens and closes teminal really fast, i redownloaded and it persist, going back to 0.167.
[Android] dastin1015:
That's what I thought too, but you just open Terminal and cd to the folder and then issue ./menu the way you're supposed to. The double clicking was just convenient. In the FAQ is the correct way to open the Kitchen.

Sent from my Hero that never dies! ;D
[Android] dsixda:
Why are you doing it that way?? Type ./menu and don't use older versions.
[Android] dsixda:
He is porting a Sense ROM to the Motorola phone.

Holy crap, that's a long updater-script. People should use a busybox install script rather than putting the hundreds of symlinks into the updater-script.
[Android] pjgowtham:
People are not using .zip ROMs to make sense work on my device.

They are using .sbf fixed sbf files to make it work

Any reason behind that?

What do you think?
[Android] mike1986.:
I know it could sound strange to you, but I have bad experience with busybox installing script. It used to cause strange bootloops is some situations.
[Android] dsixda:
What kind of errors were there in logcat or recovery log?
[Android] mike1986.:
I don't remember now because it was more then one half year ago. But I will do some testing in few days and let you know.
[Android] dsixda:
In one-half year there have been over 50 new versions of the kitchen ;-)

A lot of basic infrastructure has been corrected over that time.
[Android] mike1986.:
I know :) But maybe you remember once I told you about some mistake in installbusybox file? I don't remember now what was that but since you corrected it there was no other changes I think. It's very simple script, not much to change there.
[Android] dsixda:
Yeah I believe that was that was fixed.. it was an issue with the updater-script. Later on, I also had an Desire HD like you, and never had issues with the installbusybox.
[Android] leith51:
@dsixda thank you so much for your kitchen it works fantastic.

Can I ask 1 thing if its possible to create a option to have the choice to build Rom either ext3 or ext4.

Not that it matters much its easy enough to change it when built, I just forget to now and again now I have 3 roms on the go.

Will be sending a little something your way to say thank you for your work and help.

Sent from outer of space
[Android] leith51:
as i said i would just a little something from me to say thank you

Confirmation number: 4JA890004B383140S
[Android] dsixda:
Depends on your kernel, you can just change the file in tools/edify_defs. I don't want to mess around with the values in those files.

If the edify_defs file has "ext3" format but the custom ROM contains "ext4" in the original updater-script, then the kitchen will use ext4 automatically when it converts back from update-script to updater-script.
[Android] leith51:
thank you for your reply the kernel is ext4 just done what you advised in your post