yashsingh1/xdaforums huggingface dataset:
[Android] GazaIan:
It's happened before because of boot.img and I read the FAQ's, as well as searched the thread.. although, it did slip my mind to check the recovery log.

Also, for the java on 64 bit machines;

Install OpenJDK Java 6 Runtime from software center (if the user does not already have software center, they can follow the sudo apt-get install software center steps you have.)

Next, open terminal and type apt-get install ia32-libs (sudo might be needed, although it doesn't say it here).

That's what I did, but Google suggests the same thing in reverse and all through terminal so I suppose it works either way.
[Android] GazaIan:
had to throw this on pastebin because the post was 50,000 chars longer than what's allowed, so here's the paste: http://pastebin.com/LE1FFuPR
[Android] jim74s:
you can get help for my problem..:)
[Android] dsixda:
Sorry, but I have to finally hand out infractions for this kind of re-posting.

Jim, I have already told you to look up the answer in the FAQ to your specific question, and warned you last week not to re-post again and again. I think this is the 6th or 7th time in the last two weeks you have posted this. If people are unable to help you (I don't think you got the hint?), then there is enough information already available in the FAQ. Your alternative is a Virtual Box installation. Anyways please consult the FAQ or try VBox.
[Android] dsixda:
So it looks like the script exited early because it couldn't run that /sbin/grep script, and hence didn't finish flashing. Not really a kitchen issue though.
[Android] jim74s:
Thanks, I will follow your advice.

sorry if I posted the same question several times.;)
[Android] dmeadows013:
When I try running the kitchen after some recent updates, I get :

Welcome to the HTC Android Kitchen

Please wait .....sed: illegal option -- -

usage: sed script [-Ealn] [-i extension] [file ...]

sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

Error: You do not have the correct version of 'sed' installed.

Refer to the FAQ for the HTC Android Kitchen at

xda-developers.com to ensure you have installed the GNU

version of sed.

This is after uninstalling Macports and fixing the libiconv.dylid error. I know I have GNU sed installed, because the kitchen worked previously. I have tried reinstalling it, but get nothing. I have also searched the FAQ with no help. Can someone help me with this?
[Android] lovex8:
I got the same error when type ./menu. Anyone can help me?
[Android] lovex8:
I think I find the reason.Check this

6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)

I just got the same error,and now every thing is OK!
[Android] bobster0001:
That's what I did and it still doesn't work. Thanks for replying though.
[Android] dr.notor:
Is it just me or is the Add Nano text editor + sysro/sysrw functionality broken for someone else? Never worked for me, always end up adding the nano binary + sysro/sysrw scripts manually, they get never copied to /system/bin via the kitchen scripts.

Also, the /dev/block/mtdblock3 device in sysro/sysrw is clearly phone-specific, better to remove it altogether, specifying the device node is unneeded for remounting.
[Android] dsixda:
Ouch, good catch.. Yeah someone else created that nano/sysro script and submitted it for the kitchen, and I never really took a good look at it. Worked on my Nexus One ages ago, but haven't tried it since!!

I'm assuming the Nano part should work. It seems to be adding to /system/bin fine for me. Actually I should change that routine so that it goes to /system/xbin instead.
[Android] dr.notor:
Heh, nothing major. ;)

Hrrrm. Seems I am haunted then. :D Well, I will try again when you change the scripts path to /system/xbin, indeed sounds like a better location.
[Android] dsixda:
Yeah I will test that again on my device to make sure it's still working ;) I'll put up the changes in several days, as part of the bigger changes coming up. I've been spending the last week on Galaxy S2 support... still a lot left to do.

EDIT: Nano launches properly on my Nexus S using terminal emulator.
[Android] Faryaab:
Please update the Kitchen with latest smali tools.

Thanks.

Faryaab
[Android] dsixda:
Just download smali/baksmali from the website in the meantime..
[Android] Roqu3:
nano and the rw/ro scripts works fine on P500
[Android] stian230:
Can you see the light at the end of the tunnel making SGS2 support ?? I'm so ready for it.
[Android] dsixda:
Yes but sysrw/ro will not work with devices that do not use partition 3 as the system mount point.
[Android] Roqu3:
Sorry I was refering to this:

I also had the P500 and that functionality (add the scripts) works fine.
[Android] dsixda:
Yes I know. I had earlier confirmed that Nano installs fine with the kitchen, but sysro/rw will not work with partitions other than mtd 3 .. Thus it will only work on devices like Nexus One and yours.
[Android] dincdoes.me:
Has anyone used this for nook color I've got some ideas / somethings that I want to do with zee nook
[Android] speeed_demon47:
to dsixda:

It's really a good thing creating this,it got me started with ROM development.

So,I got a question (a little off topic).

I'm new to programming and coding and all this stuff (I don't even know the basics of........anything:() and I mainly want to develop for android,I've created some apps using eclipse and this thread got me started on ROMs.

And I need to get started on programming,I understand I need to learn Java,C/C++ and Linux kernel,I got started on Linux kernel a little while back (a training course) and I'm gonna start learning java pretty soon.

My question is:

What do I need to learn about programming at whole before getting started with java or C/C++,and which to learn first,java or C/C++?:confused:

I'm sorry if it annoys you me posting here,but trust me,I've asked a lot of people and made threads on the forums but I still didn't get an answer on this.:(

Thanks in advance.
[Android] dsixda:
Start with C then C++/Java. But I haven't programmed in years. I just write scripts at work and at home. But there is already a long thread on your subject in this sub-forum... I don't have the link on me right now though but you can probably find it. Good luck
[Android] speeed_demon47:
Thanks,that's all I needed to know just to make sure I'm on the right track.
[Android] dsixda:
I have just uploaded the kitchen to version 0.175. This release includes the big Samsung Galaxy S2 update, as well as some other general changes.

Please see the Release Notes in Post #2 for details.

I'll come out with a guide for creating the SGS2 ROMs soon.
[Android] vitalij92:
Wow, that are great news!
[Android] dr.notor:
Seems something went wrong with the upload?

--2011-08-20 23:36:28-- https://github.com/dsixda/Android-Kitchen/zipball/-
Resolving github.com (github.com)... 207.97.227.239
Connecting to github.com (github.com)|207.97.227.239|:443... connected.
WARNING: cannot verify github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV CA-1':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 302 Found
Location: https://nodeload.github.com/dsixda/Android-Kitchen/zipball/- [following]
--2011-08-20 23:36:29-- https://nodeload.github.com/dsixda/Android-Kitchen/zipball/-
Resolving nodeload.github.com (nodeload.github.com)... 207.97.227.252
Connecting to nodeload.github.com (nodeload.github.com)|207.97.227.252|:443... connected.
WARNING: cannot verify nodeload.github.com's certificate, issued by `/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287':
Self-signed certificate encountered.
HTTP request sent, awaiting response... 404 Not Found
2011-08-20 23:36:30 ERROR 404: Not Found.

Error: dsixda_Android_Kitchen_-.zip was not downloaded
[Android] dsixda:
Yeah the script is having problems parsing the release notes file. Just download it from the first post while I fix it.
[Android] dr.notor:
Yeah, already figured.

$ notes=`scripts/get_latest_notes`; latest_ver=`echo $notes | sed -e 's/.*Version[ ]*\([0-9]*.[0-9]*\) .*/\1/g' -e 's/[ ]*//g'`; echo $latest_ver
-

Should return 0.175, not - :D

While at it... hmmm, I realize that this saves you one file, but maybe uploading something like latest.txt with simple version string in it to github and using that would be a lot less coding? :-)
[Android] dsixda:
Fixed in 0.175 now (I added an open-bracket to the expression string), although I don't know why it was working all this time until today.

Wouldn't be a lot less coding, I would still need to go into GitHub, get the file and then search for the specific release notes for that version. I addition, certain people are blocked from GitHub, so I can't put a latest.txt file up there.. If they cannot download it then they can at least view the release notes on XDA.

In the meantime, here's the fix just in case ... just unzip the attachment and copy to /scripts folder.
[Android] dsixda:
Android Kitchen Guide for Samsung Galaxy S2 users right here:

http://xdaforums.com/showthread.php?t=1227549
[Android] dr.notor:
Yeah, that works now... thanks.

(BTW, wrt the sysro, sysrw scripts - I did not really mean to remove them completely, removing the device node is enough and should work everywhere just fine. Like this:

mount -o ro,remount /system
mount -o rw,remount /system

You just need to specify the mount point when remounting, the device is optional. ;)
[Android] dsixda:
That's all? LOL Arghh.. Are you sure it works that way with all devices?
[Android] dr.notor:
Well, as long as they have system on /system, yes. :D Actually, the should not be device-specific at all, can screw up just if you have broken mount applet in busybox. I tried with a bunch of them, including the latest 1.19.0, no problem with that.

It works for others as well, not just /system. Can have some speedup fun with that like e.g.

for k in $(busybox mount | grep relatime | cut -d " " -f3)
do
sync
busybox mount -o remount,noatime,nodiratime $k
done
[Android] dsixda:
Ok I'll put it back for next release. Time to take a break. ha ha

But does it require busybox?

I use Root Explorer anyway for mounting/umounting, I'm not good enough for ADB. *hides*
[Android] dr.notor:
Well... it does not require busybox, any standard mount binary should work (the stock ones), but you know how much some vendors suck. :p

If you really want to make sure it uses busybox for sanity, call it like this:

busybox mount -o ro,remount /system
[Android] joeykrim:
first time dsixda kitchen user. attempting to unpack the latest htc evo 3d boot_signed.img file from software update (2.08.651.2 released Aug 18th).

Kitchen seems to pull out the zImage but doesn't pull out the ramdisk.

From main menu - pick 0 - pick 20 - type a - rename boot_signed.img to boot.img and dropped in the folder.

Pasted output below. Am i missing something?

Script says extracting kernel and ramdisk and then says done, but I only have a zImage file, no ramdisk. Results below:

thanks for any help!

edit: RUU .exe is found here - http://xdaforums.com/showthread.php?t=1225737

directions for using wine to extract rom.zip - http://tjworld.net/wiki/Android/ExtractRomImageFromWindowsRuuExeOnLinux#no1

file is boot_signed.img inside of the rom.zip inside of the .exe ...
[Android] dsixda:
Can you post the boot.img? I don't want to download the entire ROM. Thanks.
[Android] joeykrim:
Appreciate the quick response!

I've tried to post as much information as I've been able to gather

Not working (zImage extracts but not ramdisk) - http://joeykrim.com/evo3d/files/boot_signed.img

Working (zImage and ramdisk extract) - http://joeykrim.com/evo3d/files/recovery_signed.img

edit: looking at this boot_signed.img thru a hex editor ... it really is missing the phrase ANDROID! (41 4E 44 52 4F 49 44 21) which the recovery_signed.img has.. although it has the console info upfront and seems to have the padding and beginning A0 E1 00 00 A0 E1 00 00 .. etc

to make sure my linux/wine windows emulation didnt cause any issues, i also loaded the ruu .exe on a windows machine, pulled the rom.zip and extracted boot_signed.img .. same image.

edit #2: using this script - http://xdaforums.com/showthread.php?t=1008619 - split_signed_bootimg.pl.zip - attached to the OP. it errors out on the boot_signed.img file with this message: "Android Magic not found in boot_signed.img. Giving up." From looking at the perl script (dont know anything bout perl) I'm guessing that is this:

use constant BOOT_MAGIC => 'ANDROID!';

use constant BOOT_MAGIC_SIZE => 8;

and this function

# Read the Magic

read(INF, $buf, BOOT_MAGIC_SIZE);

unless ($buf eq BOOT_MAGIC) {

die "Android Magic not found in $fn. Giving up.\n";

}

SOLUTION: .. don't run the splitting scripts on the boot.img without removing the first 256 bytes from the header as they will permanently remove a large chunk of the boot.img corrupting it. splitting scripts work fine if you manually remove the signed 256 bytes at the beginning. but even better:

dsixda kitchen works fine on the original, untouched file (no hex editing needed!!!!

thanks for all the help!!
[Android] dsixda:
Thanks for the info... I'll take a look myself later.
[Android] xpack90:
See that there is an update but getting a 404 when trying to download the update
[Android] dastin1015:
Then just download it manually from his Github.
[Android] dsixda:
Works fine for me. Looks like you figured out the issue; you ran a 3rd-party script on the boot.img -- which corrupted it -- and then you ran it on the kitchen. You should have mentioned that first, you had me worried that I broke something in the kitchen. ;-) :P

The kitchen already automatically figures out where the Android header is. Those other scripts only work on older boot.img and some of the newer ones.
[Android] dsixda:
Read the previous page.
[Android] tommytomatoe:
Hey d. I don't like off topic on dedicated threads just as much as you...

But I just wanted to give you a big thanks for kitchen. I am updating android-utility tomorrow then I am starting work on my first official rom. Ive used the kitchen for personal rom set ups but my next project should be fun enough to share.

Thank you. :-)
[Android] dr.notor:
As said above. Or:

wget --no-check-certificate https://github.com/dsixda/Android-Kitchen/zipball/0.175 -O dsixda_Android_Kitchen_0.175.zip
[Android] dsixda:
Hi guys, version 0.176 is now up.
[Android] TMartin:
I don't have the deodex error to post yet. I will in a bit but in the mean while I noticed then when building.

scripts/add_initd_perm_to_update_script: line 57: scripts/fix_update_script_blan
ks: No such file or directory
[Android] Yay 4 Juggs:
Can you tell me what you would need to fully support the motorola photon?
[Android] dsixda:
Sorry about that, just add "cd .." on the line before that command.
[Android] dsixda:
Just post the updater-script if there is an existing custom ROM, and also dump the contents of the 'mount' command if you are rooted.

For 'full' support however you would need to know how to extract the stock image and all that. I'm not going to do that extra work for the kitchen. ;) The work on the Galaxy S2 just burned two weeks of my life :)
[Android] TMartin:
Ok cool. So I won't have that error for you on the deodexing until later but I think Ubuntu is having issues with the new lines to move baksmali & smali. Seems like its working fine here at work on cygwin.
[Android] dsixda:
OK will try when I get home. The work never ends :( lol

The original error you mentioned should not affect your ROM. The same script is called again when you build.
[Android] TMartin:
Yea but this is just tiny stuff. Overall, the move to include Galaxy II support seemed to keep everything working properly. Great job!
[Android] carl1961:
this did not effect what I was doing, just posting in case you needed to know

showed up when script running was removing temp boot folder after running script
[Android] biglcny:
I built an Ubuntu VM and started learning with your kitchen literally less than 3 days ago. I only really know enough to get myself in trouble, but these scripts wouldn't work on my thunderbolt with the new GB leak. I am pretty sure it had to do with paths or something (could there be another version of mount somewhere in the base?) because the following fixed it for me:

busybox mount -o ro,remount /system
busybox mount -o rw,remount /system

If you look at the code here for remount, they do it the same way.

http://code.google.com/p/synergy-thunderbolt/source/browse/trunk/system/bin/remount?r=57

Also, deodexing /system/app and /system/(can't remember).... does not work in Ubuntu for me. I've tried everything I could think of and looked through the scripts. I can deodex single files using the single file option. Based on some posts, it looks like I'm not the only one. What can I try to fix this and is there any information I could provide to help others with issue? Let me know.
[Android] dsixda:
What's the error message?

What's the error message??
[Android] kushdeck:
same for me on ubuntu.

NOW AT FILE 31 OF 31 IN system/framework: svc.odex
Disassembling svc.odex ...
Error: baksmali.jar not found!
-> Using brute-force method (ignore above error if successful):

Disassembling svc.odex ...
Error: baksmali.jar not found!

--> Trying older version of baksmali/smali (1.2.6
)

cp: target `baksmali.jar' is not a directory
cp: target `smali.jar' is not a directory
Disassembling svc.odex ...
Error: baksmali.jar not found!
-> Using brute-force method (ignore above error if successful):

Disassembling svc.odex ...
Error: baksmali.jar not found!

--> Reverting to newer baksmali/smali (1.2.7
)

cp: target `baksmali.jar' is not a directory
cp: target `smali.jar' is not a directory
ERROR: Aborting svc.odex

-deck
[Android] TMartin:
I just got home to post and you beat me to it lol....Thanks.

Looks like that new cp line isn't working in Ubunutu.
[Android] bbcisdabomb:
I'm looking to customize my Droid Incredible 2 but I can't find the stock firmware anywhere. I do have a stock, non-rooted backup (running CM7 now), would I break anything by restoring that backup, updating to GB, and making a backup of that to put in this kitchen?

If anyone has a link to an official GB firmware for the DInc2 that would be simpler, but I can't seem to find one.

Thanks in advance!
[Android] TMartin:
PG32IMG_RUU_Vivo_W_VERIZON_WWE_1.34.605.4_Radio_0. 99.01.0225_2_NV_VZW1.92_release_182876_signed.zip

EDIT: Not sure if this is GB. Nandroid will suck but you can try.

EDIT2: Here are something close to stock ROMs

http://xdaforums.com/showthread.php?t=1161411

http://xdaforums.com/showthread.php?t=1220623
[Android] biglcny:
just running sysrw and sysro would return this:

Usage: mount [-r] [-w] [-o options] [-t type] device directory

rather than no output as usual. I believe there may be another version of mount that takes different parameters. When a rom is flashed and you connect to it with adb shell there is a version of mount in /system/bin that is different and accepts options in a different format.

simply typing running mount at the command line or in a shell script uses that one instead of the busybox one.

For the deodexing, it goes on and on for every file like this (erro message below). I followed the FAQ and other instructions rather carefully. The kitchen is located at /homes/<user id with no space>/kitchen. I just unziped it and renamed the folder to kitchen, i tried the with the rom.zip from the RUU from the 2.10.605.1 leak and a the stock /w root (nothing else done to it) from here http://rootzwiki.com/showthread.php?t=3247 to rule out any problems from the RUU.

Let me know if there is anything you would like to do or provide, thanks.

NOW AT FILE 15 OF 147 IN system/app: com.htc.StockWidget.odex

Disassembling com.htc.StockWidget.odex ...

Error: baksmali.jar not found!

-> Using brute-force method (ignore above error if successful):

Disassembling com.htc.StockWidget.odex ...

Error: baksmali.jar not found!

--> Trying older version of baksmali/smali (1.2.6

)

cp: target `baksmali.jar' is not a directory

cp: target `smali.jar' is not a directory

Disassembling com.htc.StockWidget.odex ...

Error: baksmali.jar not found!

-> Using brute-force method (ignore above error if successful):

Disassembling com.htc.StockWidget.odex ...

Error: baksmali.jar not found!

--> Reverting to newer baksmali/smali (1.2.7

)

cp: target `baksmali.jar' is not a directory

cp: target `smali.jar' is not a directory

ERROR: Aborting com.htc.StockWidget.odex

NOW AT FILE 16 OF 147 IN system/app: com.htc.TrendsWidget.odex

Disassembling com.htc.TrendsWidget.odex ...

Error: baksmali.jar not found!

-> Using brute-force method (ignore above error if successful):

Disassembling com.htc.TrendsWidget.odex ...

Error: baksmali.jar not found!

--> Trying older version of baksmali/smali (1.2.6

)

cp: target `baksmali.jar' is not a directory

cp: target `smali.jar' is not a directory

Disassembling com.htc.TrendsWidget.odex ...

Error: baksmali.jar not found!

-> Using brute-force method (ignore above error if successful):

Disassembling com.htc.TrendsWidget.odex ...

Error: baksmali.jar not found!

--> Reverting to newer baksmali/smali (1.2.7

)

cp: target `baksmali.jar' is not a directory

cp: target `smali.jar' is not a directory

ERROR: Aborting com.htc.TrendsWidget.odex
[Android] carl1961:
deodexing fine on Cygwin

deodexing working as normal on Cygwin running windows 7 32bit ( running v0.176)
[Android] dsixda:
Fixed, fixed and fixed. ;) I have uploaded version 0.177 of the kitchen.

Please see Post #2 (Release Notes) for details.
[Android] spc_hicks09:
dsixda,

Noticed on the OP that it says Motorola Droid: Unconfirmed

Just built 2 ROMS using this for the OG Droid so I can confirm that it works!

Instead of installing a laggy virtual machine, there is something called "Wubi" (for those that don't know about it). It allows you to install Ubuntu right along side Windows, it's pretty much a dual boot and the upside is that you don't have to use a laggy or unstable virtual machine. I used your Kitchen before when building for the Eris and loved it, and still love it to this day. Very simple and easy to use. Thanks!
[Android] pkoper:
Need some help guys. I am having a really hard time extracting system.img.

Tried just about everything.

unyaffs quits with a access violation error. wunyaffs crashes.

Installed cygwin and the kitchen according to carls guide and it all works the way it should, but

ext2explore does not open the .img

explore2fs can open it, but quits with error: could not find valid superblock

Pretty sure it is something basic I am missing.

Win7x64

cygwin

system.img is from stock Samsung Galaxy Tab 10.1 (P7500)
[Android] dr.notor:
Well, the above is an example of totally screwed up mount binary, dunno which phone and ROM you are using but the guy who produced the above would deserve a bit hit with a cluebat into their head.

If you have similar broken crap, simply edit the scripts to call busybox mount and not mount.
[Android] EddyOS:
0.176 and 0.177 both give me this error when wanting to setup a new kitchen - suggestions?

EDIT: Seems to work OK, though - just wondering what the error was really
[Android] dr.notor:
Find the line with [! and add a space before ! - also would suggest adding a space before the closing ]

Like this

if [ ! -e original_update/factoryfs.img ]
[Android] EddyOS:
Thanks for that, worked a treat! Got another issue now, though. I select the option for Nano parts (#14) and then when checking the working folder options (#10) it says it's not installed, even though it apparently is
[Android] dr.notor:
Do you actually have nano somewhere in the WORKING_* folder? Should be in /system/xbin but check elsewhere as well.
[Android] EddyOS:
No, I don't have it in /system/xbin

Trying to add it gives the message in my 1st attachment, 2nd attachment shows no entry for nano
[Android] dr.notor:
Thanks, this explains the issue I mentioned a couple of days ago, nano simply does not get added to the ROM in certain cases. Used to fail silently before.