yashsingh1/xdaforums huggingface dataset:
[Android] Hiataby:
No did not tried that. Because I don't have a Desire HD. I have a Desire and tried to put apps from the one to the other. I'm new on this Android thing. So didn't know that it wouldn't work.
[Android] Reza WM:
in desire z 1.72 rom extracted...

but when created with v0.112 in flash with recovery have error... and update aborted... how to fix it?!
[Android] dsixda:
You need to be specific and post the exact error messages.
[Android] dsixda:
Ok got it:

android.policy.odex and services.odex in the HTC Ace ROM require:

com.htc.framework.jar:com.orange.authentication.simcard.jar
[Android] Droidzone:
@dsixda,

I was discussing an issue with Data2SD with Sibere, the dev involved in making Data2SD for Desire..And we noted something which looks like a bug..

When I run my kitchen generated rom, my init.rc file contains:

Instead of:

Also the file 99complete is missing from init.d, which means that

Could this be a bug, or is it just the way the kitchen creates the files? When I cook the rom for the Desire, the only option I leave out is A2SD because I want it to be made with Data2SD.. Maybe this is the issue, and not a bug as such? In that case, I think I might add a2sd with the kitchen and then manually remove the a2sd scripts?
[Android] lovethyEVO:
The kitchen does not add the init.d folder nor does it add any init.d scripts.

You can add the busybox run-parts for the init.d scripts using the kitchen but you have to create the init.d directory yourself and add the scripts you want to use.
[Android] Reza WM:
in copying files step have this error

E:Board does not support mtd utils.E:Failure atline 77:

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

;)

thanks for your support:)
[Android] dsixda:
I posted a response to this error probably 2 days ago. Please search first. Let me know if you solve it.

Maybe open up a working cooked ROM for this device and see how they did it in the script.

EDIT: You may need to convert it to an updater-script. I noticed in a ROM in the Desire HD forum that he put some additional stuff at the end for the boot.img.
[Android] dscott23:
I'm having an issue with a2sd in Kitchen 0.112, with a Nexus One.

The first ROM I put together was FRG83G, rooted only. I enabled most of the options available, built, flashed, and everything was fine. Dalvik was moved to the ext partition automatically, and after first boot I ran a2sd manually in order to move the apps.

I then made some more modifications; going back to the kitchen, I used the first build as my starting point, added some custom theme work, and rebuilt. Seeing as this was just an upgrade as opposed to a new ROM, I didn't wipe, and simply flashed over the first build. But after boot, dalvik and app-private were the only things on the ext partition, and I had to manually run a2sd again, then reboot, in order to get my app directory back.

Should this be necessary every time?
[Android] dsixda:
You shouldn't have to manually run apps2sd. Should be fine right after flashing every time.
[Android] dscott23:
Because after installing the ROM, the only thing symlinked from the ext partition was /system/sd/dalvik-cache. Running it manually was the only way to get the app and app-private folders moved aswell.
[Android] dsixda:
To be safe, I would back up my previous ROM's data with Titanium Backup, then wipe and flash the new ROM, then restore everything back, so that they all go on the SD card.
[Android] dscott23:
That's actually what I had done the first time, but the Titanium restore failed because it had run out of space. That's when I checked the symlinks through adb and discovered that only dalvik had been moved.

I'm going to try it again tomorrow, start with the clean ROM, build from there, and see if I can't figure out what went wrong.

Just so I know, is there a specific order I should be following when enabling things in the Kitchen (busybox, a2sd, etc)? I would assume the order doesn't matter.

Thanks for your help.
[Android] stoute:
I screwed up while in the terminal and opened ./menu file while in root access and now I can;t edit the folder at all. Any idea how to remove the folder to create a new one or to change the permissions?

i hopped on ubuntu's site and it says how from the root dir how to change but not from the user's folder.

HELP!!! lol I really dont want to spend another day reinstalling ubuntu and all the install files again. ugh.
[Android] dscott23:
I had a chance to try it again tonight. After building, the install went fine, and once booted I checked through adb, and again, a2sd had not run. I checked /data/dta2sd.log, and everything looks fine until this:

[X] No Apps2SD Start flag detected...Apps2SD will not be started.

Seems the start flag isn't being set properly. Could you point me to the specific script where this is supposed to happen?
[Android] dsixda:
Probably best to ask tkirton in his Apps2sd thread, as I'm not the expert on his scripts.

Regarding your previous question, normally deodexing is done first after you extract a ROM, then you can do everything else, and then you do zipalign last before you build the ROM.
[Android] dsixda:
chown -R yourusername foldername
[Android] dsixda:
Version 0.113 is now out.

Going to bed!
[Android] mike1986.:
Hey :) Just want to as what does it mean 'Added more support for deodex of HTC Ace (Desire HD) ROMs" ---> now there will be no more problems with deodexing framework?
[Android] ferrarinews:
Hi everybody.

Just one question. I was working with this ktchen in my HTC Magic. Now i have a HTC Desire, can i use too this kitchen is this model?

Thanks.
[Android] SpaceK33z:
Yes, if you use another ROM ofcourse.
[Android] ferrarinews:
If i use another ROM? Sorry i don't understand?

Thanks.
[Android] SpaceK33z:
I mean, it's pretty logical that you don't use the same ROM you used for the Magic in your new phone.
[Android] ferrarinews:
Of course....lol.

Thanks.
[Android] dsixda:
Yes, hopefully. I did an entire Ace ROM successfully.
[Android] dscott23:
Thanks, that's exactly how I've been doing it. I'll give it a go again today. Quick question: for the java JDK download, you link to v5, but the newest is v6. Does this make a difference which one we use?

edit: nevermind, found an answer to the java question in the thread. Either 5 or 6 should be fine.
[Android] EddyOS:
A2SD+ doesn't work at all, /data/app still on internal memory and ignores my EXT3 partition

Hasn't worked on v0.110, 111, 112 or 113
[Android] dsixda:
What's A2SD Plus? Nobody reported issues for apps2sd during the 1.5 months that 0.110 was out. Worked on my device. Try asking tkirton in his thread.
[Android] EddyOS:
Plus is also moving dalvik cache to SD...thought this would be know as it's widely known in the HTC world

That aside, A2SD isn't working. /data/app is still on the internal memory so I'm guessing the script isn't working correctly. If you need anything from me I can upload files if required. I'm using the HTC Desire 2.29.405.5 RUU system/boot.img
[Android] dsixda:
Well I don't have a Desire so I can't really test it properly. ;) sorry... I advise you run the a2sd commands to verify what you have installed. tkirton could help you out.

That being said, I need to take some time off this kitchen, have been up very late the last few days working on these things. Not good. The only kitchen I want to see now is the one with food :)
[Android] EddyOS:
Testing a theory here, do init.d commands in the /etc folder need to different numbers? I had 04app2sd and 04perflock_disabler so changed the name to 08perflock_disabler and will see how it goes
[Android] EddyOS:
Yep, that was it!! Working now

One more thing learnt today :D
[Android] dsixda:
Awesome, good to know.. Maybe tell the developer of the perf lock disabler or of Apps2SD to avoid using 04, to prevent conflicts?
[Android] dscott23:
Looks like my problems are solved as well :). I didn't do anything different this time other than using the updated Kitchen, 0.113.

I had initially tried to convert update-script to updater-script (after reading about possible incompatibilities with amon's recovery image), but that resulted in busybox permissions not being set properly, and so the boot sequence would just freeze.

I did it again with just an update-script, and everything seems to be working great now. Dalvik and all apps are on the ext partition, and stay that way after a ROM upgrade as well.
[Android] dsixda:
Ouch, that's not good... what did you observe specifically?
[Android] dscott23:
After I flashed the rom and rebooted, it sat on the initial loading screen for a while, so I used ddms from the sdk to see what was going on. I can't remember the exact wording now, but it was "/system/xbin/busybox: Permission denied"
[Android] Reza WM:
i have problem with desire z flash rom still now,

i tested all mood

when use 99

enter no=flash fail

enter yes & yes=flash fail

enter yes & no= flash fail

:confused:
[Android] dsixda:
What options were enabled in the ROM? Could you paste the "Show working folder information" screen here? Just enclose it within

tags. Thanks
[Android] dsixda:
Sorry, can't help you any further, as I only have a Nexus One. Try asking in your device forum and get back to us if you have a solution.
[Android] Droidzone:
@dsixda,

Following 0.111, the kitchen version number isnt being updated for me. After downloading the zip, I'm extracting the contents of the zip to the respective folders of kitchen. Maybe I'm douing something wrong and the process is supposed to be automated?
[Android] Noonski:
Did you open the ./menu and check if the version number is changed there?
[Android] Droidzone:
Yes indeed. That is where I'm looking for the version number. It's still at 0.111. It's no big deal. Just wanted to inform dsixda in case it's a bug, though a mild and harmless one at that.
[Android] cedric123:
This kitchen made my day made a own custom ROM with OC and it Is fast as hell with all my favorite apps pre-installed!!
[Android] dsixda:
No, current version has 0.113 in the 'menu' file.
[Android] dsixda:
The problem is that the boot.img in your ZIP file must be copied to a temporary folder (/tmp) on your device before it can be flashed:

1) You must first convert your update-script into an updater-script to make this work.

2) Then, replace the write_raw_image("boot.img", "boot") statement in the new updater-script, so that it looks like this now:

package_extract_file("boot.img", "/tmp/boot.img");
write_raw_image("/tmp/boot.img", "boot");
delete("/tmp/boot.img");

With the kitchen, you don't need to do this manually. All you need to do is build the ROM while you have your update-script and allow the kitchen to convert it into an updater-script when it asks. This should perform the change above automatically and fix the boot.img flashing issue.
[Android] Droidzone:
Ah..I'm embarrassed..I just forgot to copy the .menu file! Sorry, false alarm :o
[Android] dsixda:
FYI this kind of conflict is going to be fixed in the next version of apps2sd. It will look for the next available number slot in /etc/init.d and rename the file accordingly.

Also, the current version of Apps2SD has a bug that I am also facing -- my Apps2sd is not starting on first boot, causing the device to hang. tkirton sent me a fix which I will add ASAP to the kitchen.
[Android] dsixda:
Ok, I've updated the kitchen to 0.114.

Apps2SD has been tested on my device and is now back to working properly - but it is an older version, due to issues in his Beta version.
[Android] damasko:
hello dsixda, with 0.114 i got errors deodexing twitter from huawei u8150 stock rom.

with 0.112 it worked fine.

PS thank you for the tool!
[Android] dsixda:
0.112 had the same version of smali/baksmali, 1.2.6, as in 0.114 - nothing was changed. Perhaps you are referring to Kitchen 0.110.

Please paste the errors in your reply, so I can see what the problem is. Some people said the older version of the deodex tools (baksmali/smali 1.2.5) work better. So you can download those and try.
[Android] theintelligent:
Desire HD Cooking

After preparing the rom from the kitchen whenever I tried to flash it via CWM, it is successfully flashed, no errors, but when the device boots up, the device is with the old rom instead of new one? Updater-script attached for reference.

Any clues?
[Android] max1919:
I tryed this kitchen, but it doesen't work good with LG optimus gt540 (swift), I can build rom but when I try to flash it my phone stuck in boot loop... :(
[Android] dsixda:
Old ROM? that means you flashed the wrong ROM, has nothing to do with the kitchen.
[Android] dsixda:
As I said on page 1 -- Read the FAQ first for help, and then paste the output here. Also please be more specific as to what you added to the ROM, otherwise I'll have no idea. Let me know what you get.. thanks.
[Android] theintelligent:
Old Rom meaning the one on which I have flashed the new one.
[Android] Flecky:
Someone proven desire to hd?.

Does not work, creates the rom.zip but the flash fails.

Thanks.
[Android] dsixda:
The updater-script formats the system partition, the old ROM would have been wiped out.
[Android] dsixda:
What do you mean flash "fails"? Guys... Please be specific about error messages.

If you mean u are trying to port a Desire ROM to Desire HD it's going to take a lot of work.
[Android] theintelligent:
This is the point exactly that there is no error and all is successful but still the rom is not flashed.

Any clues/hints?
[Android] anryl:
8120 as well smali/backsmali from 0.110 working fine

:D
[Android] dsixda:
After you attempt to flash it (while still in recovery menu), can you grab the recovery.log and post it?
[Android] Flecky:
Sorry I'm using google translator.

After creating the working folder using a customized rom, delete an application and build the rom. not flashing the output file.zip

Error:

-Finding update package...

-Opening update package...

-Installing update...

-Formatting SYSTEM:...

-Deleting files...

-Copying files...

-Deleting files...

-Deleting files...

-Copying files...

-E:Board does not support mtd utils.E:Failure at line 89:

-write_raw_image PACKAGE:boot.img BOOT:

-Installation aborted.

Thanks, Flecky.
[Android] dsixda:
I just posted a solution yesterday and in another thread in this forum. You'll need to search before posting. Let me know if it works.
[Android] pokerhiih:
No. ... does not work. I tried a few times

Think it has to do with boot.img

Maybe something I did wrong .......
[Android] dsixda:
What do you mean "does not work"? -- can you post the error message or recovery.log here.
[Android] bobsbbq:
Hello dsixda, Thank you for your sharing of this kitchen. Can I ask if it is known to work on the MT4G also known as the HTC Glacier? I did not see it in the list in the OP.

Thanks,

Bob
[Android] pokerhiih:
Same as "flecky" up there.

-E: Board not does support mtd utils.E: Failure at line 80:

-write_raw_image PACKAGE: boot.img BOOT:

-Installation aborted

If you are writing:

run_program ("/ xbin / busybox / mkdir", "/ boot");

mount ("MTD," boot "," / boot ")
[Android] ferrarinews:
Hi.

I am using this kitchen for some time. Now I have a HTC Desire and the official ROM. This ROM have *.odex files in the \system\app and \system\framework.

The question is, if I do deodex to this files with option (11), the rom after I install gets 70MB internal space, if I dont do option (11), and leave those files I get 136MB. Can someone explain that.

Thanks.
[Android] dsixda:
I have no idea, whatever is on the first page is all I know. However, it doesn't hurt to try ;-)
[Android] dsixda:
Ok thanks for letting me know. You guys will have to ask a dev in your device forum, because you're asking someone who doesn't even own that device. If you find out then let us know, thanks.

P.S. Easiest way would be to open up the update.zip of a Desire HD custom kernel and see how the updater-script flashes the boot.img. Anyways I am too busy now to do that - it's something for you to figure out for your device.
[Android] pokerhiih:
Thanks anyway ..... if I find solution I will let you know ....
[Android] pokerhiih:
Hm .... I'm not that good:)
[Android] dsixda:
Just open the zip file and see what it says at the end about the boot.img -- how hard is that.
[Android] nikitto:
dsixda, first of all, thanks for your kitchen. It works great.

Just say, it works properly for Desire HD. I've been working with Flecky, to do it posible.

We used 114 kitchen and we followed your steps.

After we copied both lines to updater-script.

run_program("installbusybox");

run_program("/xbin/busybox/mkdir", "/boot");

mount("MTD", "boot", "/boot");

package_extract_file("boot.img","/tmp/boot.img");

*Check mistakes in second line.

That's all. Best regards!
[Android] dsixda:
Congrats! So the only thing you added to my instructions was the busybox script, correct? What mistakes were in second line?
[Android] puertoblack2003:
question dsixda. using the explore2fs is that something new.I noticed it when it popped up extracting a stock rom when i stripped it from ruu..

pb
[Android] dsixda:
Yes for ext3 ROMs.
[Android] puertoblack2003:
ok thanks.Time to play around with the evo shift :)
[Android] dsixda:
Ok, found the reason for this. After the "installbusybox" line in your updater-script, the following should be added:

set_perm(0, 1000, 0755, "/system/xbin/busybox");

So, it should look like this:

run_program("installbusybox");
set_perm(0, 1000, 0755, "/system/xbin/busybox");

Sorry about that, that's a bug in the kitchen.
[Android] dscott23:
Cool, thanks. If I rebuild again using updater-script I'll make sure to check this.
[Android] dsixda:
Not sure why it doesn't complain when an update-script is used instead.. But, it seems to have fixed the issue for updater-script ;-)
[Android] dsixda:
Ok guys, I've uploaded version 0.115. This will fix the Desire HD updater-script issue for the boot.img during a flash, as well as the busybox permissions issue when booting.
[Android] Kalashnikitty:
Beta 4 from Darktremors A2SD Script is out. Could u implement this to your kitchen?
[Android] dsixda:
I'll wait for it to be more stable. I haven't tested Beta 4 yet, although tkirton told me it was going fine. I had a lot of problems with Beta 3 though.
[Android] theintelligent:
Please find attached both the recovery log and updater-script
[Android] dsixda:
Thank you. Your problem is shown near the start of the recovery.log:

Installing update...
I:Trying update-binary.
mount: no mtd partition named "userdata"
format: no mtd partition named "system"
mount: no mtd partition named "system"

I have no idea why it doesn't like your partition names that you had specified in your updater-script. ??

ui_print("Mounting Data Partition");
mount("MTD", "userdata", "/data");
ui_print("Formatting System Partition");
format("MTD", "system");
ui_print("Mounting System Partition");
mount("MTD", "system", "/system");

Maybe it's called 'data' and not userdata? Maybe you should mount system before format? I forget.

Anyways I am going to sleep... working too much on this kitchen. Need a break.
[Android] theintelligent:
Please go ahead :)

But strange enough when I flashed some other ROM in which the partitions name is same as of my updater-script, they worked flawlessly.

I will do some experiments and after that I will update you.

Update:

--------

Well i have tried your suggestions but no luck same error is encountering. Recovery.log is attached for reference.

Update:

--------

Well it seem I have a solution, let me confirm it :)

Update:

--------

Well a partial solution, what i have done is i manually mount system & data partitions in clockworkmod and then flash the rom. This seems to work partially, ROM is partially installed, boot.img is not installed and data partition is also not installed.

Errors are same as previous ones.
[Android] mike1986.:
first you format:

format("ext3", "EMMC", "/dev/block/mmcblk0p25");

format("ext3", "EMMC", "/dev/block/mmcblk0p26");

then you mount:

mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");

mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");
[Android] theintelligent:
Thanks mike, I will definitely try this and report back.

Really appreciate your support.
[Android] mike1986.:
You also need newest update-binary.
[Android] dsixda:
Careful - Is this update-binary universal for all devices or compiled only for a specific device?
[Android] puertoblack2003:
yea dsixda, i was having issue with the evo shift trying to flash.It'll go through it motion but nothing happens.Then i remember when i was extracting the rom, which i was stripped form ruu. i had to use the manual explore2fs, which you said its only used for ext3

i figured it out through poking around on other roms and this is what i used and worked the dirty way.I have to clean it up. see attached.

*** i suggest no one use this script***
[Android] theintelligent:
So should I use the approach or not?
[Android] puertoblack2003:
you can try it.It worked for me with my first custom shift rom.But i ran into issue with root permission but after using the visionary apk everything is back to normal. so far so good ;)
[Android] theintelligent:
Thanks I will try it and report back
[Android] dsixda:
I was referring to the update-binary in the post you replied to, not the updater-script. ;-)

By the way, the mount points (eg. the lines with "ext3 EMMC") vary from device to device, so what works for Evo Shift may not work for Desire HD. Just keep that in mind.

Thanks
[Android] puertoblack2003:
gotcha buddy. You may want to add evo shift on your list ;) after removing all the bloatware i got 320mb internal :)
[Android] nikitto:
Sorry dsixda, I was really busy.

Yes, we did thay you said:

The problem on your device is that the 'boot' partition is not mounted to a folder yet. The following should fix that:

1) First, convert the update-script to an updater-script (you can convert it from the Advanced menu section of the kitchen)

2) Then, use the kitchen to install busybox

3) Finally, open up your updater-script, and put this before the lines containing the "boot" partition:

run_program("/xbin/busybox/mkdir", "/boot");

mount("MTD", "boot", "/boot");

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

Simply, you forgot (") after MTD, and (;) at the end of the line. Nothing else.

OK, thanks again. We're downloading it to test. I'll tell you something early.

BB
[Android] theintelligent:
It was successful. ROM successfully flashed :)

Thank you all for your support :)

But the mystery is still unresolved that why it was not working with the partitions name.

Any suggestion to find out the root cause for that?
[Android] dsixda:
Cool! Thank you for trying. Nice to know the ext3 ROMs are now working ;)
[Android] dsixda:
Yeah I noticed that mistake later. Sorry about that.

I tested the new lines on my Nexus One. Even though the Nexus doesn't require the script to mount the boot partition (it works without having to add those lines), it still flashed without complaints.
[Android] nikitto:
Hi again.

We tested this new version (115) and it works properly. Thanks for your dedication.

Best regards !
[Android] pokerhiih:
Hi dsixda...still same error on desire HD
[Android] dsixda:
?? The person above you said it worked perfectly. You have to convert it to updater-script
[Android] pokerhiih:
I did....but still same error...dont now what am doing wrong

boot still do not wont to flash
[Android] dsixda:
What steps did you follow? Please give details, not vague replies.
[Android] pokerhiih:
1) First, convert the update-script to an updater-script (you can convert it from the Advanced menu section of the kitchen)

2) Then, use the kitchen to install busybox

3) Finally, open up your updater-script, and put this before the lines containing the "boot" partition:

run_program("/xbin/busybox/mkdir", "/boot");

mount("MTD", "boot", "/boot");

after all these I built ROM.

Flash ... all went well until...

-Finding update package...

-Opening update package...

-Installing update...

-Formatting SYSTEM:...

-Deleting files...

-Copying files...

-Deleting files...

-Deleting files...

-Copying files...

-E:Board does not support mtd utils.E:Failure at line 81:

-write_raw_image PACKAGE:boot.img BOOT:

-Installation aborted