yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] mr_omega:
At init.rc file i have this code:

service bootanim /system/bin/bootanimation
user graphics
group graphics
critical
oneshot

this one is hashed:

#service samsungani /system/bin/samsungani
# user graphics
# group graphics
# disabled
# oneshot

I have file bootanimation in folder /system/bin

and good boot animation file sanim.zip at folder /system/media (i used it earlier when I made a simple change)

and... nothing... black screen at booting... :(

When I un-hashed the previus code, and hashed the second one, standard animation was played...

EDIT----------------

Haaaa!! All works perfectly! I mixed up the files and I used a compressed sanim.zip file, instead of uncompressed - so that's why did not work.

Thanx for your big help!
[Galaxy S Plus I9001 Android Development] dsixda:
Good work!

Could you (or someone else) post a reliable step-by-step guide that may help other users, and can you post links to the files you required? Thanks!
[Galaxy S Plus I9001 Android Development] mr_omega:
sure, in the evening I prepare step-by-step howto about boot animation.
[Galaxy S Plus I9001 Android Development] teshxx:
I can unpack boot.img, but kitchen won't change the options to repack it. I have boot.img-ramdisk and zImage in the folder extracted, but no option to repack. Can anyone please tell me how to repack boot.img?? thanx (using 182 kitchen)

-------

Nevermind had to redo everything and finally got it to work.
[Galaxy S Plus I9001 Android Development] mr_omega:
Dsixda's Android Kitchen supports custom boot animation, but unfortunately this function don't work with our i9001 properly. So, we must work around this problem.

What to do:

0. Prepare the file sanim.zip This file contains the boot animation consisting of frames. Every frame is a picture in resolution 480 x 800 px in .png format. See sample file (with standard boot animation). You can use it to make you own animation. Remember! - .zip file with animation must be non-compressed zip!

1. Download FeaCore 1.3.1 (OCor nonOC - which you want), from this topic: http://xdaforums.com/showthread.php?t=1331164

2. Unpack FeaCore zip file. You will see files: recovery.img, boot.img, bootanimation

3. copy files recovery.img and boot.img to the /original_update kitchen's folder with other necessary (to make a new rom) files.

4. start the kitchen. when your WORKING folder is made, copy file bootanimation to /system/bin folder

5. check if bootanimation file has executable permition, if not, set it

6. copy sanim.zip file to the folder /system/media placed at WORKING folder

7. back to the kitchen menu and choose 0 (ADVANCED OPTIONS) then 20 (Tools for boot image), and finally "w" (Extract kernel+ramdisk from boot.img). Now boot.img is extracted to the new folder /BOOT-EXTRACTED You will find there another folder /boot.img-ramdisk

Go there and edit the file "init.rc" using any text editor. Find in the code of this file this string:

"service samsungani /system/bin/samsungani"

Make sure, that all section after this line is hashed (#) like this:

#service samsungani /system/bin/samsungani
# user graphics
# group graphics
# disabled
# oneshot

and the other one section near isn't hashed:

service bootanim /system/bin/bootanimation
user graphics
group graphics
critical
oneshot

(If you un-hash the first one section, and hash the second, stock boot animation will be displeyed).

If all is ok, close editor and back to the kitchen.

Press option "b" (Build boot.img from BOOT-EXTRACTED folder (for working folder)) this will compile the boot file.

8. make your new rom pressing 99 at the kitchen menu

Attention: point 7 of this how-to is only just to make sure, that needed section is un-hashed (and to show you how to extract boot.img file)

You don't need to do that point, cause FeaCore supports custom boot animation.

Sorry my bad english :D
[Galaxy S Plus I9001 Android Development] dsixda:
Cool..

How would you check the permissions in Step 5?
[Galaxy S Plus I9001 Android Development] mr_omega:
Using Linux, being in the directory where the file bootanimation is located type this:

ls -l |grep bootanimation

in response you receive something like this (there is "omega" cause it's my username in system):

-rwxrwxr-x 1 omega omega 23160 2011-12-23 00:17 bootanimation

1. if we got -rw-rw-r-- it means: file don't have permition to execute

2. if we got -rwxrwxr-x it mens: file have permition to execute, and all is ok

in the first case you must add that permition, so type this:

chmod +x bootanimation

We can use the graphic mode too - you must click LMB at file bootanimation and choose properties of the file - and there you must to find "access rights" and check box rights to execute.

In Windows - sorry, i don't use it, so i don't know. But it must be similar to the graphic mode at Linux.
[Galaxy S Plus I9001 Android Development] skywalker01:
No, it isn't similar unfortunately. :(

The file permissions in Windows are totally different from Linux ie. when using the NTFS file system which is standard since Win XP. If you still use the older FAT file system on any partition you don't have any file permissions there at all, ie. everybody can do anything with all files (and folders) on this FAT partition.

BTW: USB memory sticks and all types of memory cards like sd cards are very often still formatted with the old FAT file system. A good reason for this is that nearly every OS today can read (and write) the FAT file system while some may not be able to read or even write to NTFS. So never forget about the disadvantages of FAT because it is still vastly used especially on external media.

So when using windows you have to modify the updater-script of the update.zip package you are creating and add a command that takes care about setting the correct file permissions on the destination device:

set_perm(0, 0, 0755, "/system/bin/bootanimation");

It is a good idea to do it always like that even when using Linux to create the update package because this method makes sure that it will always work ;)

And this is also a main reason why dsixda doesn't implement odin flashable ROMs in tar archives (or smd etc.) There are no updater-scripts in these type of ROM packages, only CWM flashable zip update packages offer this very handy feature.
[Galaxy S Plus I9001 Android Development] dsixda:
Yeah we should be setting the permissions in the updater-script. Setting permissions directly to the file from the computer OS is not a reliable method.

mr_omega: why are you copying the recovery.img? Did you include a write command for recovery image in the updater-script? Otherwise it will not be flashed to device. However, good to know you got the animation working.
[Galaxy S Plus I9001 Android Development] kelt525:
Hi.

i have problem: If i make wipe on my rom after the update in cwm , all program what i istall (kithen/working.../data/app) is delited! if i dont make the wipe after update, all program is install!

Sorry for my bad english. THX
[Galaxy S Plus I9001 Android Development] lfaber06:
I'm trying to add my phone to the kitchen, does anybody know how? Or would you look at my attached zip and fix it for me? I included my build.prop , recovery.fstab (so you can see which mmcblk's are what) and how i'm thinking it should look.
[Galaxy S Plus I9001 Android Development] dsixda:
Is this about the Galaxy S Plus? Please note the current forum and stay on topic for the benefit of other readers of this thread, as I said in page 1.

If it's about another device, please read post #1 of the main kitchen thread on how to add them. Sorry, I can't help any further in this specific thread.
[Galaxy S Plus I9001 Android Development] afengdd:
there is no enough space in phone memory for install apk after i used kitchen,help me

:(:confused:i have met a problem when i do my rom with kitchen 0.182. recovery1.31...

after i finish and built on my device with wipe data and cache

it remind my there is no enough space in phone memory for install apk.

:(:(:(:(:(:(
[Galaxy S Plus I9001 Android Development] macdroid2:
Really enjoyed it!
[Galaxy S Plus I9001 Android Development] mikeeo019:
The previous poster is some kind of troll. He has wrote 15 posts and all of them have been like "Thanks, I really enjoy!" or "I will try, I enjoyed it" Nothing else.

EDIT: And yeah, even on Android Revolution ROM thread he said "I enjoyed" :D

EDIT2: typos
[Galaxy S Plus I9001 Android Development] jarjar09:
Hello, thanks for the kitchen!!

I Cooked a rom from the stock XXKPU, decompressing .md5 and used the files boot.img, cache.img.ext4 and system.img.ext4. Cooked from Cygwin with the last kitchen v0.183 and I have a question:

The market me does not appear: is it known anybody which is the mistake?

SOLVED: Putting Vending.apk in working_folder\data\app (data\app funcionality...)

Thanks a lot

P.D: Sorry for my bad English, I´m Spanish
[Galaxy S Plus I9001 Android Development] kubson1999:
'Application 'clear' is not installed - the kitchen will not function propertly witchout it. Ensure you did not miss a step during instalation'

I have to install to work?
[Galaxy S Plus I9001 Android Development] dsixda:
The same error message also says afterwards to read the FAQ before asking the question. I don't understand how you and so many others overlook that. The FAQ already has the solution, so please read it.
[Galaxy S Plus I9001 Android Development] kubson1999:
I can not find an answer to this question, please help me if you want
[Galaxy S Plus I9001 Android Development] dsixda:
I am not explaining this answer for the hundredth time. You overlooked a step that was mentioned in the instructions. Go to the FAQ part 2, it is one of the first questions.

You guys are on xda, please do some reading, do not expect to be spoonfed every time.
[Galaxy S Plus I9001 Android Development] kubson1999:
I did as you need bulls to get it working, I gave the download and attracted more than 3 hours, finally stopped. What to do to more quickly attracted. I can uncheck something?

Wysłane z mojego GT-I9001
[Galaxy S Plus I9001 Android Development] alexis!:
Here good way to post "logcat.txt"?

Everything is going ok, just root XXKQ1, busybox and zipalign, sign...etc

But when i try to flash, bootloop on Samsung logo, again and again.

I haven´t made any other changes.

Thanks!

I tried to reinstall kitchen at all, and tried to make other ROMs, with XXKQ7, root, busybox... But when i try to flash i sitll get bootloops.

I always do a clean install, Wiping cache, data, system, emmc.

PD: Now, kitchen is not working, im sure have tar file on original_update, but when i try to set Working Folder ROM, it says No ROM found!! :(

PD SOLVED: Was my fault, the file as named "xxxx.tar.md5" and it didn´t recognize it. I had to remove the .md5 extension. Sorry then.
[Galaxy S Plus I9001 Android Development] alexis!:
+Up this.

Can someone, please, take a look the "logcat.txt" attached above?

Im trying to deodex XXKQ7, or XXKQ1, XXKPU, anyway, cant do it with any stock ROM.

Always got bootloop at Samsung Galaxy S Plus screen.

I just root, busybox, deodex and zipalign, no more. But cant boot..

Thanks!!
[Galaxy S Plus I9001 Android Development] alexis!:
Still trying to build XXKPS, KPU, KQ1 modified with kitchen.

When i make the .zip, in output_zip, its usual that into de now built ROMnamesigned.zip its still system.img.ext4 and cache.img.ext4? I mean into the .zip, i can see already those files. The rests of the ROMs haven`t it.

Any ideas please? I have tried en different PCs but nothing...

I dont know if all is working good, maybe updater-script or update-script?
[Galaxy S Plus I9001 Android Development] nail16:
You have to extract the system.ext4 first then deodex did you do that ?
[Galaxy S Plus I9001 Android Development] alexis!:
Yes, first make working folder and extract from stock system.img.ext4, cache.img.ext4...

All steps seems ok, i mean when i sign .zip

I look into the zip, in output_zip, and there are still those files into system folder. I must remove them before signing and making the zip?

Dont know if i explained right.

Enviado desde mi GT-I9001 usando Tapatalk
[Galaxy S Plus I9001 Android Development] nail16:
You should use ext2explorer to extract the .ext4 files in the working folder.

it's already included in the kitchen tools folder.

Did you create the working folder manually ?
[Galaxy S Plus I9001 Android Development] dsixda:
Those should have been removed when you extracted the files from them. If you didn't *close* ext2explore (or whatever program) after extracting the files -- as the instructions told you on the screen -- then Windows will be unable to remove system.ext4/cache.ext4. There is an error message on the screen that specifically tells you about it if you had it open still and it was unsuccessfully trying to delete the file.

Make sure you don't rush and ignore instructions and errors in the kitchen.
[Galaxy S Plus I9001 Android Development] alexis!:
Thanks for replys.

Thats what confuse me, i do every step right, i dont ignore any error (there arent errors during the kitchen progress), and of course when ext2explorer finishes extracting files, i close it. Same with Linux Reader.

I dont set the Working Folder manually, i use to remove the old, and create new one.

I think its the only mistake, when i remove those files, and repack/sing again, theres no problem
[Galaxy S Plus I9001 Android Development] nail16:
After ext4explorer extracts the file do you close the cygwin window or press enter ?
[Galaxy S Plus I9001 Android Development] alexis!:
It says Press Enter, so i Enter.
[Galaxy S Plus I9001 Android Development] wintel_mac:
Did you try it with a native linux system? Maybe it's more a cygwin error...
[Galaxy S Plus I9001 Android Development] alexis!:
No sorry, i only work with Windows.

Its curious that in other PC with XP OS (the other was Win 7, UAC minimun and no capital letters into the folder except META-INF, these were known bugs, so i started with them), didn´t work too.
[Galaxy S Plus I9001 Android Development] nail16:
Maybe cygwin can't detect jdk so it fails.

did you install jdk before or after installing cygwin ?

can you upload the updater-script of the rom from the output zip folder.
[Galaxy S Plus I9001 Android Development] alexis!:
I installed sdk and jdk, jre all before cygwin and kitchen.

Same in other PC, im sure that installation its ok.

Just leave home, when i become back i will upload.

Really thanks, i was getting crazy.
[Galaxy S Plus I9001 Android Development] dsixda:
No there shouldn't be a problem with jdk, otherwise there would be an error when kitchen starts.
[Galaxy S Plus I9001 Android Development] alexis!:
I have tried cooking again, but nothing. Those files (system.img.ext4 and cache.img.ext4) are still in the signed zip, its really heavy 458MB.

I have attached my updater-script.

I installed SDK in C:\Program Files\Android\android-sdk but all PATHs and all its set right. I have to put android-sdk folder in the root of C:\? Or it doesnt matter?

Btw, i have cygwin in the root of C:\ and kitchen is in C:\cygwin\home\Alexis\kitchen.

Right way?

Really thanks!
[Galaxy S Plus I9001 Android Development] dsixda:
You don't need the sdk to run the kitchen. All the setup details are in the FAQ.
[Galaxy S Plus I9001 Android Development] alexis!:
Well it doesnt matter, cause i need SDK too. I use to play with ADB.

Is there any problem with my updater-script?

Thanks!
[Galaxy S Plus I9001 Android Development] nail16:
I see you have made minor changes to the updater script (the way it writes the boot.img )

but that's not a problem :)

try reinstalling cygwin.
[Galaxy S Plus I9001 Android Development] crybert:
Have you already tried to delete the *img files by hand?

The updater-script seems to be right.

EDIT: Just tested the mentioned problem on my Mac with version 0.188

When I extract the ROM out of an ODIN-Package. There will be the system.img.ext4 and cache.img.ext4 in the /system folder together with the extracted files. Dsixda, could it be that there ist something wrong in your scripts, so that the files will not be deleted.
[Galaxy S Plus I9001 Android Development] dsixda:
I think I know what the problem is in the code. Sorry guys, I'm surprised this mistake was there for so long without detection. Am away from my PC at the moment but will fix and test it shortly.
[Galaxy S Plus I9001 Android Development] crybert:
I discovered this some time ago but for me it was no big deal. I just deleted the files and everything was good. And then I didn't used the kitchen for a long time and forgot this.
[Galaxy S Plus I9001 Android Development] dsixda:
OK, problem has been fixed, now version 0.189 is up. Thanks for your feedback!
[Galaxy S Plus I9001 Android Development] alexis!:
Hi @dsixda, problem has been solved, but actually we have other:

whenever i try to flash, i get CWM Error (Status 6).

I did no changes related to updater-script, and if i change it for Cranium`s updater-script for example, it boots.

Maybe something wrong in the new version of kitchen updater-script?

Thanks!
[Galaxy S Plus I9001 Android Development] dsixda:
There is no new version of kitchen updater script.. I never changed it. What other details are in the error message after it says Status 6? What does it say in the recovery log?

Based on Google search, Status 6 happens if you modified the updater-script with a non-unix compliant editor such as Notepad or Wordpad..
[Galaxy S Plus I9001 Android Development] wintel_mac:
Exactly. We had that before.
[Galaxy S Plus I9001 Android Development] dsixda:
What I could do, to cover people's butts if they used the wrong editor, is to have the kitchen automatically re-format the update-script/updater-script to a unix-readable format so that this problem does not happen. The convert_to_unix file in the scripts directory can do that.

Or I could just leave it as is, and rely on the user to know what he/she is doing ;)
[Galaxy S Plus I9001 Android Development] nail16:
Yes that would help a lot, Automatically Converting the script EOL to unix format will avoid such problems in future :)
[Galaxy S Plus I9001 Android Development] alexis!:
I edit with Notepad++, never used other editor.

It would be nice to modify what you say.

Maybe i did something wrong. Will try again at home.
[Galaxy S Plus I9001 Android Development] dsixda:
OK done, see version 0.190.

As you probably know by now, I'm retired from my kitchen work because my hand is a mess.. so I can only do simple fixes like this on the keyboard before it starts getting painful.
[Galaxy S Plus I9001 Android Development] nail16:
Thanks Man really appreciate the work you are doing :)
[Galaxy S Plus I9001 Android Development] alexis!:
Really thanks dsixdas, i only told you what i noticed.

Thanks for your effort, and for helping people like me, to start cooking some bases.

Thanks a lot! Now life its pretty izi :D
[Galaxy S Plus I9001 Android Development] c_shekhar:
@dsixdas

Great favour done to the android community by you. This kichen has made the job very simple for the people looking for customization.

Thanks a lot bro!..

...c_shekhar
[Galaxy S Plus I9001 Android Development] dsixda:
Hi guys, I've been testing my new "Hackintosh" system, and so I decided to add a fix for Mac OS X in the latest update of the kitchen, which previously wasn't allowing extraction of the CSC from cache.img.ext4 file.
[Galaxy S Plus I9001 Android Development] icedTricky:
Hey guys,

i currently want to build a zip out of a stock-rom because my usb isn't working in download-mode anymore.

So i downloaded the I9001XXKQM_I9001DBTKQ2_DBT from samfirmware. I extracted the .tar.md5, renamed it to .tar and placed it in the original_update folder.

While trying to set up working folder from ROM i receive the following error:

Extracting ROM from TAR file ...
boot.img
cache.img.ext4
system.img.ext4

Analyzing system.img.ext4 ...
Analyzing cache.img.ext4 ...

Compiling simg2img ...
simg2img successfully compiled

Adding an update-script ...

Mounting ext4_system.img to loopback device and then extracting files ...
Error: Unable to mount ext4_system.img

Error: No /system/framework folder found!

As i want to sell it, i need to put it back to stock. Anyone knows the error and maybe a way to fix it?

My system is Debain 7 x86 with OpenJDK (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1)
[Galaxy S Plus I9001 Android Development] texten:
just try another firmware. loos like yours is incomplete. the framework folder is missing.

and i would prefer mobile odin or adb shell instead of the kitchen.
[Galaxy S Plus I9001 Android Development] loanky:
I'm having this same problem, how did you manage to repack it. I was trying to repack boot.img of my tecno y2, mt6572. This frustrating.
[Android Q&A, Help & Troubleshooting] carrot34:
Can you see your Google Wallet app transaction history on the web somewhere? It _looks_ like you should be able to see purchases made using the Google Wallet app at https://wallet.google.com/manage/#transactions, but this page just lists my Google Checkout transactions -- there's no record here of anything I bought using the phone app. As far as I can tell, the only place where I can see any record of those transactions is on the phone itself by selecting "Transactions" in the Google Wallet app. Is there a way to see this stuff online that I'm missing? And if these transactions _are_ only recorded on the phone, will all record of them be erased if/when my phone is wiped?

Thanks,

Alan
[Android Q&A, Help & Troubleshooting] The-Captain:
Does this help?

http://support.google.com/wallet/bin/answer.py?hl=en&answer=1349469

Thank me if this helped!
[Android Q&A, Help & Troubleshooting] carrot34:
Thanks, but I don't see that link helping to solve this. I still don't see a page on the web where I can see a record of transactions made on the phone. Do you?
[Android Q&A, Help & Troubleshooting] The-Captain:
Can't you just click wallet??
[Android Q&A, Help & Troubleshooting] carrot34:
I'm not following you -- "click wallet" where, on what webpage? (If I go to wallet.google.com and then sign in, the list of transactions that comes up does not include anything I bought with my phone.)
[Android Q&A, Help & Troubleshooting] The-Captain:
At the bottom of this page..

http://support.google.com/wallet/?hl=en
[Android Q&A, Help & Troubleshooting] carrot34:
Thanks -- no, the list of transactions that that calls up includes everything I ever bought on Google Checkout, but nothing I bought using Google Wallet NFC purchasing on my Nexus phone. Do you see things on that page that you bought using the Google Wallet Android app?

I'm guessing that this is just about Google not having yet fully integrated Google Checkout and Google Wallet. Though it's possible that it's something screwy with my particular account.
[Android Q&A, Help & Troubleshooting] erikskean:
I was looking for the same thing when I came across your thread. I would like to see the two integrated soon because Google definitely advertises it as such. It would be nice to view all transactions online or on your phone. Not exclusive to the device you used.
[Android Q&A, Help & Troubleshooting] distortedloop:
No, it's not unique to your account.

I wiped my phone, installed a new ROM, reinstalled Wallet. My prepaid card balance showed up, but not a single transaction that I'd made on it shows on either the phone or the web anywhere.

There's a lot of things Google needs to improve to make Wallet a reliable and viable tool. It's no wonder they're not supporting it on any but one phone at this time. It's way undercooked for the masses.
[Android Q&A, Help & Troubleshooting] carrot34:
Thanks! This is really good to know. Yeah, with issues like this, it sounds like Google Wallet's still in Beta. I'm not complaining -- it's wonderful to get these visions of the future, and given the choice between using this cool Wallet thing now and waiting a year until it's really polished, I'll choose the former. But, yeah, a fully-baked Wallet product should let you see your NFC transactions somewhere besides on the phone; and there should be an (accessible) record of them that you can access even if you get a new device or wipe your phone.

Alan