yashsingh1/xdaforums huggingface dataset:
[Android] zelendel:
I have to agree. While we will never be rid of the winzip rom makers tools like this help give people a place to start and to decide if they want to dig deeper into it. How can I say this you ask, it is because I am one of them. When I first started on XDA I knew next to nothing about development but with some of the great kitchens that were available I started to learn. Then When I needed to make deeper changes I had to dig in more and learn.

Now on Android. I started out learning by unzipping roms and looking inside, Then came apktool and learning to theme to fix issues that others made in themes, then I moved up to a kitchen. Now I have taken the dive and to working on Source code. Which includes making my PC dual boot a Linux distro (which alo of people are not able.willing to do). None of which would have happened had I not started with tools just like this one.

Now I see people going off at the mouth at each other. Some of you seem to think you are a coding wiz. Well let me tell you what. Your attitude is just the kind that we dont need. Personally I dont care what your title says. Get over yourselves and get back to what XDA is all about. Sharing and learning. If your not part of the solution then you are part of the problem. I would rather the tool be used by 100 people if it even helps 1 on the path to learning even more.
[Android] PoorCollegeGuy:
I started out on ROM kitchens (dsixda) as well. It was cool to run through the menu system and seeing things work. I went from dsixda's kitchen to UOT and when I realized what UOT did, I started making themes and replacing the appropriate files in the ROM with the files that UOT spit out which gave me my own custom themed ROMs. Realizing that most theming elements were held in apk files, I used apk tool and apk manager to figure out that the images could be removed, edited and replaced and thus learned theming.

It is a process, but there's invaluable experience and knowledge from using kitchens and tools like this. It gets users familiar with the file structure, identifies the important files. Once you have that confidence that you know how a ROM is constructed, then it's only a matter of time before you start constructing them from scratch yourself.

I've only made it as far as compiling from source code, but I can at least take a system dump and turn it into a ROM, writing my own updater and everything. Got the Nix partition, go the work folders set up. It's a process and one that's churned out several good developers around here. Even if it's just learning to include the libs with an apk to make it work properly, that's still more than most people learn in years here.

People actually do learn this way :)
[Android] THeLogiC:
Sorry had to jump into this.

I am not a developer or elite developer myself but that doesn't mean I dont want to do simple changes in kernels I use. This tool can't be used to make any kernels but well for users like me who want to change bootsplash etc it comes in very handy. If someone by using this tool releases a modified kernel then its his thinking/pschology that he developed himself but instead he just modified.

The way it's being said, I take it as a fact that all the toolkits,kitchen(even root toolkits) etc are absolutely against development and shouldn't be released at all. Don't tell you meant that? did you??

I don't have enough knowledge about kernels like you do have but I have to say if you would have just checked championswimmer's threads, he has a thread for How to's building kernels from source. I myself used his guide to build a kernel and lot other users have used it.

Championswimmer's Ultimate HOW-TO
[Android] Toledo_JAB:
Doesn't this thinking make flashtool a type of kitchen, couldn't imagine my x10 without the speed & ease of using it. But still never looked @ it's code.
[Android] championswimmer:
and i really don't understand if it's insecurity or what haunts some developers here ....

if you are a real developer ... stay proud of it.... what's your problem with some noobies coming up with cooked works and calling themselves as developers ??

those who can judge the real from the fake will alsways value your work over the work of cooks/chefs ....

and there are two factors that drive not only xda but the whole world - popularity and originality

even the film awards have a popular category and a critics category...

they best work may not be the most popular one... i mean ... AndroidRevolution is more cooked than compiled from source and yet it's the most popular ROM out here...

this is where xda as a community has to take a few decisions and draw some lines...

we could turn ourselves into code aurora forums where only work on source code is welcome... or we could turn into modaco where the forum has a much more relaxed tendency towards chefs (and even encourages them)....
[Android] Hacre:
Yeah that's great. I'm sure WM development, Android development and kernel development are all exactly the same. Except they're not.

You'd also think someone of your seniority would realise the licensing implications of such a tool, such as distributing and redistributing Linux kernel binaries without any source code available which is an instant breach of GPL.

Nevermind though eh? Keep banging that drum of living in the past. Newsflash, XDA isn't the site it used to be and the people that used to make good use of kitchens and tools to further their development skills don't make much noise around here anymore.

If you think pointing out developmental achievments is some kind of willy waving then you're either reflecting or have some weird inferiority complex, which having seen your posts in the past I very much doubt. It was mentioned to point out I'm not just another bit of white noise from the peanut gallery throwing an opinion on a tool like this because I'm bored. There is very little educational use here. You don't learn how to develop by being lazy. Does that mean absolutely no-one will use this then go on to develop? No, of course not. However the pros don't come anywhere close to outweighing the cons.

Unless of course, I'm wrong. Perhaps XDA is a moderator's utopia. Nothing ever gets copied or stolen, no kernel developers or distributors ever breach GPL and not a single ROM thread is a mere kitchen dump that's then posted in the hope of donations. Large development communities haven't upped and left the site because none of their work was repackaged and released without any changes and released under someone else's name or because of the masses of lazy people bothering them. If that's the case then sure, what's the big deal about one tool that has potential for more harm than good, right?
[Android] championswimmer:
and still no one replies to this

http://xdaforums.com/showthread.php?p=27748756#post27748756

and thanks to this ruckus... this thread is resurrected and many people are getting more and more interested in this now :p :D

no one other than 3-4 members from xperia family actually used to use this... but thanks to all this... the word is spreading
[Android] championswimmer:
ok so i want to ask an question now then... a curious and innocent question and not an arguement...

i accept i myself do not know each and every intricacy of the GPL

but as far as i understand... according to the section 3 of GPL v2,

we are supposed to provide an option to view the source of the precompiled binary when we distribute the binary...

(i hope i interpreted it right ?)

now what my kitchen will allow you to do is repack a boot.img using a kernel binary that was already floating around somewhere there on the internet and was most probably not made by you but by someone else.

the best solution would be ...

"The zImage used in my boot.img is compiled by <dev-name-here> which you can find on original thread <link-here>. The sources of this kernel zImage has been released by the dev here <git-repo-link-here> "

^^ does that still violate GPL ??

oh and btw, i am NOT distributing kernel zimage anywhere in my tool. This is just the scripts.

secondly, even dsixda kitchen has got boot.img editing sections in it. Isn't that as much dangerous as this for GPL violations ?

I just made editing ramdisks a standalone procedure, rather than part of a massive kitchen that can make coffee.

and finally i would request you to have a look through all the pages (just 9 of them, 7 if you remove all the ruckus in last two pages)

you'll notice that everyone (yes EVERYONE, not ALMOST EVERYONE) who has used this tool has used it only for personal purposes only... I have even got many pm's regarding this and most people just want to make a few changes here or there to suit their personal needs... i have not yet heard of anyone using this to redistribute any kernel

and for the argument that anyone who can compile a zImage can also pack a boot.img i want to say that .... yes definitely, but then this is a shorter method....

you don't need to spend time finding mkbootfs and mkbootimg sources and compiling those programs .... the kitchen does it for you....

this is not meant for integrated developers who make everything using just

"mka -j4 otapackage"

this is for independent kernel developers who want to make kernels for stock roms
[Android] Hacre:
That doesn't, no. Got a link to the sources for the binary only builds from stock ROMS? You said yourself it lets people create boot.imgs from stock ROMs, stock ROMs have stock kernels, stock kernels often don't have source code anywhere.

I know, I didn't say you were. I did point out that this tool being a local collection of scripts keeps YOU clear of GPL breach.

I must point out that I was referred to this thread, I tend to steer clear of kitchens as I have no use for them. I didn't know dsixda kitchen lets you download boot.imgs. That puts dsixda kitchen and anyone who redistributes ROMs built using it in clear violation of GPL if they can't provide access to the source code used to create that zImage. Which from a kernel standpoint, makes dsixda kitchen a bigger problem than your collection of scripts.

Are there posts in ROM kitchen threads where people have posted to say "Great thanks, I created a ROM using this and have posted it in <thread> and everyone thinks I made it!"? I'm willing to bet your tools have had more downloads than there have been posts in this thread. I'll reiterate, your tool has pros, but they don't outweigh the cons. In case there's a language barrier here, the good points of your toolset unfortunately do not outweigh the potential negatives. In a vacuum, your tool is great. It's a good idea. We're not in a vacuum though, we're on a site where kitchened ROMs get passed off as someone's own work and we're on a site where breaches of GPL happen almost daily and that's without your nifty set of scripts.

./mkrelease.sh ninphetamin3-1.1.1-test

That's all I type when my kernel and initrd get glued together for the SGS3. Just as short a method but with enough still to do leading up to that, that it's not possible for any idiot to whip up a kernel and start distributing. The fact I'm not posting it on XDA for public consumption also goes some way towards that, heh.

I will also point out that it's little wonder people like you think nothing of producing and distributing tools like this and not worrying about GPL, when things like dsixda kitchen are provided, endorsed, posted about on the front page and given nary a look by the XDA staff, despite the fact that every time it produces a download link, the fact that it contains a boot.img is a potential GPL headache.

So that end, championswimmer, I apologise to you for opening up with such a harsh volley a few pages back. If the site endorses bigger and clearer breaches of GPL and encourages much bigger examples of doing everything for you, then it's not to be placed upon your shoulders when you do similar but less severe.
[Android] championswimmer:
@hacre

about the apology... it's all cool... and thanks for explaining about GPL and the copycat menatility in the above ^^ post.

regarding GPL violations i have posted a warning in my OP, and i sincerely hope people read it and not ignore it.

as regarding people misusing this tool... i stick with my stand.... if xda wants to close down this thread seeing the potential of abuse, i'm in all agreement to such a decision and will not challenge it :)
[Android] Tof37:
You're not guilty and you're tool as well if people don't mind about GPL....

Xda and more over Android community basement is sharing...

but there are rules to respect : when someone uses someone else's work then we have to ask for agreement and add credits....

you did it for this tool and everyone using this tool to mod an existing kernel should do it...
[Android] championswimmer:
version bumped to 0.2.0

now kernel.elf files (xperia s/u/p/sola) can be edited too

once again i must say... please read the warning in the op carefully and do not misuse the tool
[Android] blazingwolf:
@championswimmer,

Thanks for the tool. While I haven't used it nor plan to it is nice to see someone contribute to the site and the community.

It's a sad day indeed when "respected developers" of the community must belittle and attack people that are trying to help no matter how misguided. When all is said and done it is the "respected developer" that looks like the jerk.
[Android] jerdog:
championswimmer - I appreciate your dedication to helping others on XDA, and your RC title bears that out. Thank you for adjusting your OP and making sure people understand that using something like this should only be used for private/personal use so as to avoid the complications of a possible GPL violation. I can definitely understand your desire to share your work and what has helped you become more interested in Android and source, and I can only hope that there will be others that follow that example.
[Android] championswimmer:
yes, surely, and just to make my intentions further clear i have added another few lines in my op (a word of advice)

and i have added section 3 of GPL to my OP too (albeit using the 'show content' button)
[Android] championswimmer:
for my personal referrence for future work

http://xdaforums.com/private.php?do=showpm&pmid=7608679
[Android] blazingwolf:
Something wrong with the link. It leads to an invalid page.

Also, you made the portal. :)

http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
[Android] championswimmer:
i said PERSONAL referrence ;) :p

it's a link to a pm in my inbox.. i get 20 daily.. it'll be lost in 3 days if i don't keep a link to it somewhere safe..lol

and saw the portal :D

very happy :D
[Android] blazingwolf:
LOL. I need to quit reading things like that when I'm still waking up. I obviously couldn't figure out personal. :silly:
[Android] Davidlemmings:
:) great tool!!
[Android] .c0dy:
Is it possible that it's not compatible with I9000-Kernels yet?

'Cause with I9000-Kernels i'll get the message while trying to extract boot.img:

"Android magic not found in boot.img. Giving Up"
[Android] championswimmer:
Galaxy S you mean ??

that uses a different format from boot.img i'm not wrong??

i have never worked with Galaxy S so it never occured to me

it could be added in future :)
[Android] .c0dy:
Yes, I9000 is the Galaxy S.

I got no clue about the format :p

I'm pretty new to the kernelthing.

I just wondered if im to dumb to get it working, but if its not supported yet, im glad to hear that its not my "fault" haha

Nvm though :)

Would be cool if its getting supported sooner or later :)
[Android] onlychevys:
I have been using dsixda's kitchen for a long time and it has taught me a lot, got me looking at the file system etc. I have not released any "cooked" roms, but I damn sure fixed what I had the way I wanted and have learned how to do a lot of things on my own. Keep up the great work & if you get this to suport galaxyS2 I will be all over it!!
[Android] :
a little off topic but couldnt you try to work on a sim-unlock for us champ? modifying loader.sin?
[Android] *boy*racer*:
FYI I only wanted to change boot logo for mine and my gf phones. Not to create a boot.img.
[Android] mskip:
There is already a free sim unlock available on the market for International SGS3 phone.

Mark.
[Android] da-pharoah:
this is way cool! thanks!
[Android] slumpz:
Hi,

I'm trying to find a way to unpack and edit the ramdisk of this boot (recovery) image but till now I'm still unsuccessful.

It's unpacked OK but the format of the ramdisk is not gzip. Can you help?

Here's the attach of the recovery image.

http://www.mediafire.com/?or2p1i4s0g75rc1

The device is using a MTK6575 CPU

Thanks in advanced.

Added: Thanks to me I found this, problem solved :D

http://xdaforums.com/showthread.php?t=1587411
[Android] DearTanker:
When support build zImage ramdisk to boot.img

It seems the kernel.sin can unpack to 4 piece:

ramdisk
hearder-file
ramdisk.cpio.gz
zImage

But,The kitchen can't pack those file to a boot.img

this thread seems helpful

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

sorry for my english.:D
[Android] andry yg mana aja:
hey bro.. why if i try to open kitchen.. and i select 1. Work with boot.img files (extract or build) but after i select that the kitchen is closed..

why.. and one again.. on first open menu 1 point is empty is Imagemagick binary.. maybe because that or what..

Edit: i use ubuntu 12.04 desktop..??

sorry for my bad english.. :(
[Android] championswimmer:
sudo apt-get install imagemagick
[Android] Ali78x:
This tool works with xperia x10 phone? ( I want to change bootsplash screen of Okernel fxp mod by OODIE )
[Android] wo88les:
Yes:)
[Android] Ali78x:
Thank you ! I am testing it.
[Android] Toledo_JAB:
Just got my ION from AT&T and I am getting ready to see if the kitchen works for it. I know it says for all 2012 but no reports about ion, yet. I would like to get more governors and I/O options.

Hey CHAMP, I am very glad to here the ION made it to India. I hope it is at the top of your list ;)

~Jaramie

from my LT28at ION rooted and eating an Ice Cream Sandwich :D
[Android] championswimmer:
yep we got the not-LTE version and it's top of my wishlist right now... thankfully i held of my urges to get the Sola or the S till now :D

still will compare between the TX (international GX) and Ion before buying any of them :P
[Android] Ali78x:
I have changed " logo.rle" and "initloge.rle " to my custom .rle in archive ramdisk .

But I have an error when I build the kernel, there is written lines like " loader.sin : no such file or directory" and "Error

loading loader.sin to jar archive"

Another question : Can I change the color of led when the phone is booting and add the vibrator ?

Thank you for your help !

Edit : I excrated "kernel.ftf" with unarchiver and I put loader.sin in input folder but it doesn't work
[Android] mxracer101:
Just a heads up that tool is confirmed to work with Asus TF700 Infinity using TWRP backup boot image.

Thanks man, this made a long process short. ;)
[Android] championswimmer:
put the unlocked loader as loader_unlocked_x10 (or loader_unlocked_msm7x27 for the other phones) and try doing it...

my other suggestion is to create only a kernel.sin file instead ... and the flashtool can create the bundle for you after it :)
[Android] Ali78x:
I put the loader in ftf folder and it has worked ! Thank you !

And are there tutos to learn to change the color of led and to add the vibrator ? =)

I try to read and to understand "hw_config.sh" and other files but I can't .
[Android] championswimmer:
should be in /sbin/bootrec

and colours cannot be changed like this, you have to compile recovery from source to do that :)
[Android] Ali78x:
Ok thank you. I will try to build a recovery with other color of led !
[Android] i0nsn0w:
This is what I call great work!

Really good job!
[Android] Ali78x:
If I change tune2fs.cwm5 to other tune2fs.cwm5 ( different ), I will have an other recovery ?
[Android] championswimmer:
you have to change /sbin/recovery too :)

and the corresponding png images it needs in /res folder too :)
[Android] Ali78x:
Ok thank you, I do it :) .
[Android] Daniel D.:
I can't change the bootsplash image - using Win7-64 & Cygwin. I extract boot.img and use DooM's .bat scripts to extract the picture because the integrated of the kitchen didn't work. If I change the picture and convert it to a .rle file (with DooM's script), copy the new logo.rle to the ramdisk-contents folder and try to re-create the boot.img, the picture is still the same!

What do I have to copy to the input folder?

- ramdisk-contents folder?

- .cfg file?

- initrd.img?

- zImage?

Which files do I have to rename/keep? I've problems to follow the info given in the command prompt.
[Android] Ali78x:
ramdisk archive ! not ramdisk folder

Edit :

extract your ramdisk archive, change your bootsplash screen and rebuild your ramdisk archive ( with script )
[Android] Daniel D.:
I'm sorry, but can you add more details? I didn't understand your answer completely. :-/
[Android] Ali78x:
You have to replace bootlogo.rle ( I'm not sure for the exactly name ) in ramdisk.cpio.gz by your rle file,

and place this ramdisk.cpio.gz in input folder. ( and others needed files )

Edit : You have to extract " ramdisk.cpio.gz" with kernel-tools and the extracted folder is "ramdisk-content" and then you have to replace boot logo.rle in the folder.

Finally

you have to rebuild the new ramdisk.cpio.gz

with your modified ramdisk-content folder.

Edit 2 : May be you have not ramdisk.cpio.gz but an other type of file ( .img ? ) .
[Android] Ali78x:
For recovery I'll try this:

-----------------------------------------------------------------------

Kcernel cosmicmod ( one recovery )

Oodie kernel ( 3 recovery )

Oodie

, I copy :

/sbin/recovery.xRec

/sbin/tune2fs.xrec

and I move to sbin folder in ramdisk of kernel cosmicmod

I copy png files corresponding at xrecovery in oodie kernel and paste in /res in kcernel ramdisk

Kcernel

,

I change a line in bootxrec file :

" /rec/runrec CWM4 " by " /rec/runrec xrec "

-----------------------------------------------------------------------

So is this going to work? I want to test but I don't know if I have forgotten files.

If my kernel has a problem, my phone will be broken forever?

Edit : My phone is a x10i

Edit 2 : I tested and it doesn't work .
[Android] danibosev:
I cant Create ftf file from kernel.sin and ramdisk
[Android] championswimmer:
sorry but that part has some issues...

you can manually put the loader.sin of an xperia 7x27 device in the ftf folder and name it loader_unlocked_7x27.sin and rerun the program :)

or you can just create the sin file and then create ftf from sin using flashtool :)
[Android] ksmuthucv:
@championswimmer

Thanks for all your efforts and time to make this possible...i'm so close to be one of the successor of your efforts...i got into the below problem...could you please help me out in this?

1. splitted the boot.img

2. took the ramdisk-contents folder, renamed to ramdisk-folder and replaced the logo.rle as i liked

3. kept the above folder to input

4. cleaned up the output folder

5. created the ramdisk ["ramdisk.cpio.gz" and renamed it "initrd.img".]

6. copied the zImage and initrd.img [newly generated one] into input folder

7. created the boot.img and flashed it.

8. i was able to get into cwm and installed the rom [with complete wipe].

9. restarted the system.

10. boot logo came up as i wanted...but it didnt load the rom...i.e boot animation of the rom didnt appear and it got stuck at boot logo itself.

Environment Details: windows 7 64 bit with cygwin and there was no error during the whole process!!!
[Android] championswimmer:
you sure the rom and the kernel are compatible with each other ???

and i would still recommend linux instead of cygwin :)
[Android] ksmuthucv:
Thank you for responding.

yes, kernel and rom really are compatible. after the bool logo modification the changed was displayed. i could get into cwm and install the rom. if i reboot got stucked in boot logo. i really wish i could do something to get this done. PFA of the cygwin command window with the execution ./menu command. i have xperia ray with me. i'm not sure whether i can mention details of the kernel and where from i have picked the logo.rle.

Thanks,

Muthu