yashsingh1/xdaforums huggingface dataset:
[Android] kharv:
I am trying to install this on Windows 7 and have followed the txt file to the letter, but I continue to have issues at step #6.

When I get to this step, I am told that there are no packages installed. If I go ahead and click the arrows to say install I get another error stating something about "null" files and I have to click OK to continue.

Any ideas to what is going wrong here?
[Android] Ganii:
What about porting option at the kitchen?

Tried to port a custom MIUI ROM from Nexus One to a custom

Desire Z ROM,but nothing working,stuck on htc splash image.

Maybe should change few things manually,libs ect.!

But don`t know.

Anybody ported a ROM without problems?

Or maybe anybody can explain step by step what I have to do?
[Android] leith51:
still doesnt work
[Android] leith51:
some help please still getting same bash problem no matter if im using windows or virtualbox
[Android] TJinWV:
Run the following command in virtualbox:

sudo find / -name "menu"

That'll return something like

/home/user/kitchen/menu

Then cd to that place (without the /menu)

cd /home/user/kitchen
[Android] leith51:
edited mis read forgot to take off the /menu cheers for your help
[Android] Droidzone:
UOT Supercircle mod and the Rom cooking

I've been trying to integrate a Supercircle battery mod in my Rom. Though the UOT-cooked framework flashes fine when flashed as a standalone after Rom install, when I try to replace the framework-res.apk from the UOT in the Rom and then build it in kitchen, I'm facing bootloops. Could anyone give me a pointer towards a fix?
[Android] twopumpchump:
did you sign the framework-res.apk after you modded it? you need to sign that file and also the other apks in system/app that are dependent on it. if you sign the entire system/app directory then you will have problems with some apps updating in market.
[Android] Droidzone:
I did try signing the framework-res.apk alone and reflashing, but that didnt solve it. Would you know which ones are dependent?

Edit: Never mind, I'll try signing everything in my working folder except /data/app and then overwriting the apps with those that need to have Market updates..
[Android] jaykresge:
Let me know if you get this working. I was having a similar problem and gave up.
[Android] jadeboy7:
Try putting the original meta-inf folder and android manifest file from the original apk into the new one using 7-zip or something similar.
[Android] Droidzone:
Hey..What do you know?! This worked! Thanks a lot, twopumpchump

Yup, I'd tried this method too. Used pkzip which is very good for file substitutions in zip, but again I had bootloops.

Signing everything (except selected apps) helped solve it!
[Android] leith51:
I found a different method which may have helped you do the battery mod in kitchen as normal using apk manager decompile framework and drop the decompiled apk on desktop then decompile the original framework-res.apk open the drawable - hdpi folder in both frameworks delete the original battery out of the original framework then in the cooked framework drag and drop all the battery icons in to original framework

Then open drawable folder in both and move all stats battery xml there are 3 to original framework once that done complie original framework it will ask is it system app answer yes then it will ask if you want to keep original signature answer yes wait for it to do its thing

Open keep folder delete the battery stats icons again and the 3 xml and the resource click enter then rename apk by deleting unsigned open Rom using winrar (do not extract) navigate to framework folder then drag and drop your new created framework into it replacing the old one click yes or ok to everything close winrar

Drop zip on to SD card and flash as normal

Then you keep all original signatures everything will be as it should and no extra battery drain or bootloops

My other phone is an iPhone it makes a great coaster but not to good as a hammer
[Android] Droidzone:
Thank you. I will keep this for reference and try it in my next release. Already uploaded the other one. :)
[Android] leith51:
no worries i will share info how i find stuff as so many have helped me if you have a look at my signature link to leedroid batt mods i did a couple of battery mods for leedroid rom take a look at them it would be simple to change them to other roms as well if you use the method i just posted it also works on other phones to as i transfered the first mod i created on to the girlfriends deisre the mod was for dhd i just adjusted the size and lowered the dpi

i have 2 mods at min one is something i created from scratch and the other is the stock battery just modded to be more visable plus % down and % showing on charge

im working on a third but its nothing like you would expect its one of those crazy off the wall mods if it turns out how i expect it to then it going to be well funny
[Android] incubus26jc:
im trying to extract a system.img with .142 and it wont export using explore2fs.

When click export to working/system nothing happens. Any ideas?\Dont normally have this issue extracting system imgs. Exporting usually works fine
[Android] dsixda:
What ROM?

.
[Android] incubus26jc:
htc saga

http://www.filefactory.com/file/ca1...0805U_38.03.02.11_M_release_177977_signed.exe
[Android] dsixda:
Probably ext4 or some weird filesystem format not supported by explore2fs. Let us know if you get it extracted.
[Android] incubus26jc:
i will do that.. know any other way to extract the system.img?
[Android] dsixda:
Try doing it in Ubuntu. I can't get it working in Windows/Cygwin either with explore2fs.

I'll look into it more during the weekend.
[Android] dsixda:
Hi guys, 0.143 is now out. Please read the Release Notes in Post #2 for details.
[Android] coiledwire:
I've been using this round about way in windows to open nand backup img files.

I take any ROM and extract it into a working folder. I rename boot.img to something else. Take the system.img and rename it boot.img and place it in the same ROM working folder. Now use kitchen #22 (i think that's the boot.img option) and extract the boot.img with option w. You should get a working folder created with your system.img decompiled in it.

Hope this helps.

Sent via XDA app.
[Android] jbrew78:
Is there any way to get this to work with system.img and boot.img from honeycomb? The program that pops up to extract the system.img due to ext3 doesn't extract anything. Just sits there like I didn't do anything. I'm mainly just trying to get the .img's extracted to take a look at them. Any help would be appreciated.
[Android] dsixda:
Have you been reading the replies right before you? What device's ROM are you using?
[Android] dsixda:
I don't understand, you're talking about a Nandroid backup? And you are unpacking the system.img with the boot.img tools?
[Android] coiledwire:
Yes. I just wanted to unpack the img files from a nandroid backup. I was using kitchen 0.139 I think. The option to unpack data files didn't work. I tricked the kitchen to unpack those img files (system.img, data.img, boot.img from nandriod backup) as if they were all ROM boot.img files.

I hope this clears it up some. I just saw someone wanted to unpack data.img, but was unable to. I used a backdoor way of extracting these files, so I thought that member could find it useful. I haven't tried your newer builds, so maybe this work around isn't needed anymore.

I apologize if I misunderstood the problem.
[Android] dsixda:
Really? What device is this for? I have tried Nandroid data.img on Nexus One with no problem through kitchen.
[Android] coiledwire:
HTC EVO. The data working folder would be created. But it wouldn't recognize the data.img file placed in it.

Sent via XDA app.
[Android] jbrew78:
I'm using the honeycomb rom ported to the nook color from the emulator. Its missing quite a bit. I found a stock honeycomb system.img and boot.img. I would like to unpack those and see what I can find to add into the incomplete rom to make more things work the way they should. The post right before me was posted while I was typing my last post.
[Android] dsixda:
Is there a sample data.img you can upload for me to try out?
[Android] dsixda:
Oh.. I don't know if the Nook Color would work in this kitchen.
[Android] coiledwire:
I'll PM you a link to a data.img file when I get to my pc to upload one.

Sent via XDA app.
[Android] DonJuan692006:
I'm trying to use the port feature in 0.143. I'm running it in VMware running Ubuntu 10.10, but I'm sure that has nothing to do with the problem. The first problem I ran into was the update giving an error from the boot.img. I think it retained the boot.img from the ROM I'm trying to port which is for a different device. So I grabbed a copy of the boot.img from CyanogenMod CM 7 and slapped it into the working folder. I edited the updater-script to include the mount paths for /system and /data, then built the ROM and flashed. I'm currently stuck in a bootloop. I pulled a logcat and have it uploaded here. I honestly don't even know where to start since this is my first shot a cooking my own ROM.

FWIW, I'm cooking the ROM for a myTouch Slide and the ROM I'm trying to port is for an LG P509. The ROM I'm porting can be found here.
[Android] dsixda:
Well you have BOOTCLASSPATH issues in your logcat, which means your boot.img's init.rc file has references to /system/framework/*.jar files that do not exist in your actual working folder. You shouldn't put just any random boot.img into a working folder.

#
#
W/PackageManager( 112): Boot class path not found: /system/framework/bouncycastle.jar
#

#
W/PackageManager( 112): Boot class path not found: /system/framework/core-junit.jar
#

If you are saying u are getting boot.img errors when flashing, then u need to get the recovery.log and see why there were flashing errors.
[Android] coiledwire:
PM sent.

Please let me know if I was doing something wrong.

Thanks!
[Android] DonJuan692006:
I actually realized that the boot.img file I initially was trying to use was for 2.3.2 so I swapped for CM 6's boot.img and am not getting through the flash process, but I'm still getting stuck in a bootloop. There's probably going to still be some existing links that I'll need to cleanup, but I've got to get that part figured out. This is a huge learning experience for me since I'm don't really have an extended knowledge of using Linux, much less dev'ing.
[Android] dsixda:
There is no extended Linux or development knowledge required ;) I am just like you... you learn through fixing your problems. ;) Took me a year to figure a lot of things out, thanks to this thread.
[Android] dsixda:
Not sure what you were doing, but your Evo's data.img did unpack in Cygwin.

Actually, you mentioned you were using 0.139, and data.img functionality was broken in that build, but fixed in 0.140 (see the Release Notes..).

Anyways, ALWAYS make sure you have the latest version of the kitchen before you report a problem.
[Android] coiledwire:
Sorry about that dsixda. A person before my 1st post was asking having difficulties with data.img. I was only offering my experience as a possible alternative to getting it done. Forgive me, as it wasn't my intention to report this as a problem.

I completely agree with you; in general, you must read the entire 1st post and use the latest revision before reporting a problem. The kitchen you support is an invaluable tool for me and many others. I thank you for your efforts and I apologize for taking you off track for a bit. My bad.

Sent via XDA app.
[Android] dsixda:
No problem! I forgot you were using an older version..
[Android] dsixda:
I can confirm that this ROM can be unpacked with Linux, using my kitchen.

However, in Cygwin it will not do anything if you use Explore2FS. I'll keep looking for a solution, however. If anyone has a solution, feel free to post it!

EDIT:

Ext2Read can do it: http://sourceforge.net/projects/ext2read/

I'm guessing this ROM uses EXT4.
[Android] jbrew78:
I'm really more trying to figure out a way to unpack the system and boot img's than cook a rom. I had just used this kitchen on my mytouch 3g and mytouch 4g and knew it would unpack a system.img and boot.img. Just doesn't seem to be working with the honeycomb ones. The ones i have are stock img's from the xoom. Just want to take stuff out of this and add onto the honeycomb on my nook.
[Android] dsixda:
Let us know if you solve the issue. You can also ask around in the Nook Color forum on XDA.
[Android] dsixda:
Ok, 0.144 is now up.

I have added Cygwin support for the HTC Desire S shipped ROM, as well as ROMs for other devices that use EXT4 filesystem. (This feature was already supported in Ubuntu Linux.) Please read the Release Notes in Post #2 for more info on this and other updates.
[Android] NinjaWolf:
thanks for your hard work, you fixed a couple of my main issues with this, plus some new features(no working folder to extract boot.img/new cancel option).

Awesome work, keep it up
[Android] af974:
@ Dsixda:

App2SD is fixed with new Kitchen...thanks.

Little advice:

In the Working folder i have the boot.img, i need to chenge the zimage so i convert it in Boot folder and thats ok, however if im going to repack it and then start the cooking process it will reconvert in boot folder.

Since im using Clk with Hd2 and it use boot.img layout, how can i fix this issue?

Many thanks.
[Android] mike1986.:
Little issue found:

When selecting a build option it's written that 1 (Interactive mode) is default. But after pressing "Enter" the operation is canceled so it seems that actually default is "Cancel" :)
[Android] dsixda:
There was a problem with apps2sd? I didn't touch a thing. ;-)

I don't understand the rest of your post. Can you explain again... and do u mean 'boot-extracted' folder or 'boot' folder?? And what is Clk?
[Android] dsixda:
Doh... thanks for pointing that out. I'll fix it after I get my butt out of bed.
[Android] arif-ali:
cLK is cedesmith's little kernel bootloader for the HD2, which is open-source, an alternative to MAGLDR

link in my signature
[Android] dsixda:
Fixed.. thanks Mike.

I've re-submitted 0.144 (version # remains the same) and updated the Release Note with this change.
[Android] dsixda:
Oh, so you guys want to use a boot.img instead of a boot folder - in some cases?

Can you upload an example of a valid boot.img for the HD2?
[Android] arif-ali:
Hey dsixda,

i don't use your kitchen, but fyi the boot.img is created in the following way for cLK, this is what I have in my scripts

mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 boot.img
[Android] dsixda:
Thanks, that's what I needed.

What would be the generic term for an HD2 ROM that uses boot.img instead of /boot folder? I thought NAND-based ROMs only referred to those with the /boot folder. I can have an option when building, to prompt the user about this.
[Android] arif-ali:
At the moment, this is only for cLK, because of how that is working at the moment. It is still in development, and at the moment does not support the normal CWM /boot directory method. Hopefully, (sometime in the future) we will not need the boot.img (all credits to cedesmith for this). So in this case you could just say "HD2 cLK boot" or something similar. Or you can give an option to build for MAGLDR or cLK, and then do it automatically for cLK, and leave it as it is for MAGLDR builds

FYI, here's an excerpt from one of my updater-scipts for CWM to put this on

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

I hope that helps

btw, here is my script that I use to create my roms

createROM.sh

I am happy for you to take anything you want out of that
[Android] af974:
Thanks Arif............uhm......how many times i say to you? :D........you did help me a lot.
[Android] chukis13:
I keep getting '.' is not recognized as an internal or external command, operable program or batch file.
[Android] dsixda:
When you do what? You need to be specific, otherwise I have no idea.
[Android] dsixda:
Thanks Arif for the cLK/MAGLDR info. Yeah, I'm already aware of how to handle the boot.img in the updater-script, as this is the way we do it for regular Android devices with boot.img.

Actually I still need to find out the offset of the kernel (not the base address) in the boot.img, but I guess I can just download an HD2 ROM with a boot.img and figure that out.
[Android] miharkula:
Here's a link of just a kernel update http://xdaforums.com/attachment.php?attachmentid=544656&d=1300368669
[Android] dsixda:
OK, cLK support for NAND-based ROMs (ie. on HD2) has now been added.

Version 0.145 of the kitchen is now available. Please see Release Notes in Post #2 for details of all changes.
[Android] dsixda:
You need to be more specific and tell me which device it's for and how you got this file.
[Android] dsixda:
Yeah the same problem happened to me when I dumped the system.img from an LG Shine Plus.. I probably just dumped it wrong.
[Android] ciolnadu:
i know i'm a little off topic

i have ported a cm6 rom to lg p500 and it boots but got no radio working (signal, wifi)

can someone help?
[Android] leith51:
hi

im pretty new to all this and i have a question i get the general idea on how to use the kitchen i pretty much built a rom with this kitchen

question is there a virtual emulator to use with windows 32 bit so i can test the rom as i dont have the phone im building rom for and i dont want to brick anyones phone

many thanks for info and advice
[Android] dsixda:
Not sure.. there is the Android emulator included with the SDK but I have never tried putting update.zip ROMs in there. I don't know if it's possible with update.zip, unless you convert it into a system.img+boot.img format.
[Android] dsixda:
Ok guys, I just added an update (version 0.146) that allows importing of Nexus S custom ROMs. This hasn't been tested with a real device, but the scripts will be able to handle the mount points in the updater-script.

If you don't care about the Nexus S then you don't need to update from 0.145.
[Android] casacristo:
Hi,

Can this kitchen be used to assist with rom porting?

If so besides the obvious (boot.img and .so kernel modules) what other files are hardware dependant?
[Android] qaliza:
Thank you so much for this great kitchen

Im working on my own ROM now, Desire for HD2
[Android] dsixda:
Yes there is a porting menu, but it's experimental and won't do everything automatically, only kernel transplanting and some .so modules.
[Android] casacristo:
I am an experienced linux admin, so not afraid to get my hands dirty.

Could you give me a few pointers of what steps would need to be done manually?
[Android] dsixda:
I'm not much of a porting guru, sorry.. I'm just using a basic method that allows the device to boot up. You'll have to ask around in your device forum.
[Android] af974:
Thanks Dsixda, new version work like a charm with my HD2.

3JM28704R6215371G
[Android] TMartin:
This might help a little:

-excerpt from incdoes blog-
- system/usr (for buttons)
- system/lib/hw (for lights)
- system/lib/modules (for wifi)
- system/etc/vold.stab (for sdcard readable)
- build.prop (for market and LED's fix)
please note: some prop files include different edits that can break market/data/network/LED's...
[Android] dsixda:
Thanks, this is probably something I can incorporate into the kitchen in the future.
[Android] TMartin:
Glad to help. There is a lot more to do, especially when you're trying to port a Gingerbread to a Froyo device, etc.
[Android] NilsP:
I love the options for ROM creation and use the option 1 where I get to choose ZipAlign and creation of the updater-script and by default signing. In one of the prior releases in option 1 the default for creating updater-script was yes and now it is no so I have to enter yes. I know, I know what's 1 extra keystroke buy I would like that to default to yes since that is all I create now. Especially since most everyone is now on CWM3

This way I just hit enter for each option instead of having to think since I always ZipAlign, create updater-script and sign. In those rare occasions when I want other than I can just type N.

You know me, I was the one who wanted express to do it ALL anyway so this is a good compromise

Thanks for listening
[Android] casacristo:
Most people with an HTC desire are on CWM2.5.0.7 (it simply works fine)
[Android] dsixda:
No, the updater-script was never the default when building the ROM.. I would never enforce someone to use a new and more complex method by default.

However, the build would automatically choose updater-script without asking, if it meets certain criteria (eg. device is a Desire HD or it contains Edify commands) such that an update-script wouldn't flash successfully.

Some of you guys are just lazy ;) Look at the amount of work I have to do. LOL.. These optional things are a waste of time.
[Android] NilsP:
I guess so is offering suggestions
[Android] qaliza:
I finished my ROM but have one problem

I enabled the custom bootanimation

When I place the bootanimation.zip in data/local I still get the default one

Any help PLZ...?

My ROM is Desire 2.32.415.3 on HD2

Thank You
[Android] leith51:
Did you delete the original one ?

My other phone is an iPhone it makes a great coaster but not to good as a hammer
[Android] leith51:
If I create a Rom from source and use the functions to root install busy box etc etc then flash to my phone how can I be sure I'm not going to brick my phone ?

My other phone is an iPhone it makes a great coaster but not to good as a hammer
[Android] qaliza:
No.. Do I have to? where is it located
[Android] leith51:
Yes you do if you want to change it

after a bit of searching on htc desire thread

try this

check inside the rom in the following order open system>customize>resource

it should be in there if you winrar just open with winrar not extract and navigate to the folowing above you should find another zip file called bootanimation

just drag and drop your bootanimation into the resource folder it will replace the original and then just close winrar put on sd card and reflash

the other option would be to use root explorer and navigate to to the same place as a above and paste your bootanimation there while deleting the one that is already there but dont forget to set root explorer to r/w
[Android] k6gk:
Compiling Roms for Nexus GSM or CDMA radios

I stumbled on Android Kitchen when I was looking at various GB roms on the Nexus development forum. I thought this might be a perfect place to ask the question.

I happen to have one of the Nexus One developer phones with a CDMA radio. The software version is 2.1.1. I've tried updating the phone with new builds for the the standard Nexus GSM phone but it kills the radio (no signal and GPS) but otherwise the phone works (ends up being a Nexus Touch). So it seems that any software build has calls for a specific radio type and this phone will forever be on 2.1.1?

I discovered that the radio.img from a Droid EVO / Incredible flashes and still works fine with CDMA. It was a last ditch experiment to try to get a newer Nexus build to work.

Would it be possible to use Android Kitchen to create a custom rom for this phone with Nexus GSM source code blended with EVO radio code?

Tnx,

glenk
[Android] dsixda:
No, you are asking for a 'compromise' not a suggestion.. It's my kitchen, I can do whatever I want with it and with my time. You asked for this more than once and I said I wouldn't change it.
[Android] dsixda:
As long as you have a custom recovery menu and a nandroid backup before flashing, then you will be fine...
[Android] leith51:
Thank you when I have more time to sit down and play around will give it ago

My other phone is an iPhone it makes a great coaster but not to good as a hammer