Related
BA WM5 ROM Kitchen (Bepe's)
All of this Guide is taken from bepe's ROM Kitchen, and also the dev tool are taken from Bepe's, so all credits goes to Bepe for his great method and tools!, currently not All the file are linked except for my AKU3.2 OS + LOC & some OEM packet, since I dont hv permission yet from bepe, bepe is currently on vocation, but u can always go to bepe site here to get the old AKU files (OS, LOC, OEM):
http://buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&id=23392&catid=64
ROM Kitchen is a tool to cook your personal Windows Mobile 2005 ROM by the packages you need.
.NET Framework v2.0 must be installed!
Device-dependent packages:
DEV:
DEV_BA_v1.01+SAP.rar
ROM:
ROM_BA_v1_5.04.06_.rar - 32MB RAM
Independent packages: !!! Both should have the same AKU !!!
(Currently only my AKU3.2 Test Link Is available, I dont hv permission yet, since bepe still on vacation, check the above bepe's link for more info about Bepe AKU)
OS:
OS_AKU_2.0_v1.50.rar - AKU 2.0 (Build 14847)
OS_AKU_2.2_v1.50.rar - AKU 2.2 (Build 14928)
OS_AKU_2.3_v1.50.rar - AKU 2.3 (Build 14955)
OS_AKU_3.0_v1.51.rar - AKU 3.0 (Build 15096)
OS_AKU_3.2_TEST.rar - AKU 3.2 (Build 15605)
LOC:
LOC_AKU_2.0_v1.50_[ WWE | GER ].rar - AKU 2.0
LOC_AKU_2.3_v1.50_[ WWE ] - AKU 2.3
LOC_AKU_3.0_v1.50_[ WWE ] - AKU 3.0
LOC_AKU_3.2_TEST_[ WWE ] - AKU 3.2
OEM PACK:
ArcsoftMMS v3.0.7.19_WWE
Frequency Tuner v1.5
GB SOFT Tweak
IA Camera Oem
XCPUScalar
TaskMgr v1.6
more maybe will be added by others, lets work together guys...
How-To build a ROM:
Extract the DEV folder
Extract one ROM to DEV
Extract one OS to DEV
Extract one LOC to DEV
Extract all OEM Packages you need to OEM
Run CreateOS.exe and click the button
Run CreateROM.bat
Done, your new ROM is located at DEV/Temp/NK.nbf
How-To build ur own OEM Package:
An OEM Package is just a simple folder containing files and registry settings for the ROM
First of all you'll need a GUID number for your Package.
Go to http://kruithof.xs4all.nl/ uuid/uuidgen to get one.
In my case:
283b9db7-cb03-4c1b-820e-ca49b2c3b5db
Necessary steps:
1. Create a new folder:
Dev/OEM/[Your package name]/
2. Create a empty text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.dsm
(CreateOS.exe will finish this file for you)
If needed:
3. Create an UNICODE text file:
Dev/OEM/[Your package name]/283b9db7-cb03-4c1b-820e-ca49b2c3b5db.rgu
This file could be used to add registry entries to the ROM
First line is:
REGEDIT4
...
and there MUST be a empty line at the end!!
4. Create an UNICODE text file:
Dev/OEM/[Your package name]/initflashfiles.txt
This file could be used to create folders or copy files on the ROM.
Example: Open Dev/LOC/initflashfiles.dat using a text editor
Copy all files you need to Dev/OEM/[Your package name]/
First Big Thanks to MAMAICH for his great tools that makes this possible, and BEPE for this briliant method of buildin rom that make it really easy for everyone and also BIG Thanks to indra9110 for lot of help, thanks dra...really appreciate it bro...
This is still on test stage, so trust me, something might be wrong or anything, I'm really need an input on this method, since I'm not so familiar with bepe's briliant way, he'll do it better I supposed? hehe....
Midget_1990, xplode, Black6spdZ, thingonaspring, logout , tautara and others input and help will be a huge help for make it better.
regard,
Helmi
Update:
by thingonaspring
A full changelog is in "changes.txt". Lots of fixes, cleanups and speedups included, power management improved, pagging pool etc.
please go here and be thankfull to thingonaspring... thanks man :wink:
The 1.1 archives are here :-
ftp://xda:[email protected]/Uploads/Blue Angel/AKU3.2/KITCHEN_1.1
The 1.2 archives are here :-
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/DEV.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/LOC.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/OEM.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/OS.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/ROM.zip
Optional OEM Packages are available individually here :-
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/Camera.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/Backup.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/TCPMP_072RC2.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/TaskMgr 1.6.zip
ftp://xda:[email protected]_KITCHEN_1.2/Packages/Total Commander 2.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/PocketRar3.60.zip
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/Packages/Ringtones.zip
ftp://xda:[email protected]/Uploads/Blue Angel/For Helmi/MMS_3.0.16.16.zip
ftp://xda:[email protected]/Uploads/Blue Angel/For Helmi/mamaich_overclock.zip
Task Manager 1.9
psShutXP
vbar
And the full changelog is here :-
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN_1.2/changes_1.2.txt
Way to go helmi
Hi helmi,
Coupla broken links....
OS link should be
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN/OS/OS_AKU3.2_TEST.rar
ROM Link shoudl be
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN/ROM/nk.rar
let's get some OEM packages up here pronto!
wow, thanks helmi_c
looking forward for ppl to post nice packages
imatrix
Hi helmi, this is real good stuff.
What's the intention however? I quite like the current state of affairs with everyone focussing on one ROM. One ROM to rule them all etc.
Is the idea for people to start creating their own? I'd rather see everyone pull together to produce one fantastic BA WM5 ROM. We aren't all that far away from it just now. But if we start to fragment the effort, it'll slow things right down.
I made many packages for my Himalaya. It would be great to make some place on ftp to share them. This place shouln't be device specific (as I remember some of packages are uploaded into BA or Wizard section)
But better place would some wiki page, where people could write which package works on which hardware.
Also it's good idea to notice in package name which version of software it is, and if it's UPXed or not (I'm UPXing almost all packages gaining about 50% of space)
I have:
AKU 2.2+ Title Bar Clock
AutocompletePL
Call2Contact_1.0
CamRecSvc_by_ADX
Cambridge_bluetooth (Himalaya)
Compact_Framework_2
DKToday 1.80
DSP
DorucenkaSMS
ExtROMUnlock_UPX
File Support
FlightMode (Himalaya?)
GB-SOFT Tweak
MagicButton_2.0_UPX
NetCFVersion
O2_Operator_UPX
PQView
Regedit_PHM_0.70+TRE_0.90_UPX
Reset
SimMessaging 0.04
SoftKeyAppletEx
TaskMgr1.6
Tcpmp_0.72RC1_UPX
TodayAgenda
Toggle
Total Commander 2
TreoSpeedDial_UPX
VJVolubilis_0.41_UPX
WM2k5 SMS Alert Fix (Himalaya?)
WM5 NewMenu_1.0_UPX
WM5torage 1.7 (seems 1.5 is more stable)
XCPUScalar
idiffce_0.3_UPX
Personally i miss AEButton package but can't do it.
Some of them are unfinished (NET CF2 is the most important of them), some of them are untested because i'm still in process of converting new packages
And it would be nice to group packages by type, maybe place them in submenus
Re: Way to go helmi
thingonaspring said:
Hi helmi,
Coupla broken links....
OS link should be
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN/OS/OS_AKU3.2_TEST.rar
ROM Link shoudl be
ftp://xda:[email protected]/Uploads/Blue Angel/ROM_KITCHEN/ROM/nk.rar
let's get some OEM packages up here pronto!
Click to expand...
Click to collapse
oops... fixed... thanks thingonaspring... hopes we can be more active on this thingonaspring... :wink:
imatrix said:
wow, thanks helmi_c
looking forward for ppl to post nice packages
imatrix
Click to expand...
Click to collapse
its still early stage, we need more people involved, but maybe with thingonaspring here (I believe he ready to put some nice stuff here), midget, blackspz, logout, tautara, xplode , everyone who willing to work as a team, for me its doesnt matter who build/make the rom, I believe we just want a ROM that we can use right? so working together on the fix / update issues would produce a "Best" or "less bug" rom, plus with ability to customizing it for personal use. well, at least that my intention. hopes we all can work together.
Marx2 said:
I made many packages for my Himalaya. It would be great to make some place on ftp to share them. This place shouln't be device specific (as I remember some of packages are uploaded into BA or Wizard section)
But better place would some wiki page, where people could write which package works on which hardware.
Also it's good idea to notice in package name which version of software it is, and if it's UPXed or not (I'm UPXing almost all packages gaining about 50% of space)
I have:
AKU 2.2+ Title Bar Clock
AutocompletePL
Call2Contact_1.0
CamRecSvc_by_ADX
Cambridge_bluetooth (Himalaya)
Compact_Framework_2
DKToday 1.80
DSP
DorucenkaSMS
ExtROMUnlock_UPX
File Support
FlightMode (Himalaya?)
GB-SOFT Tweak
MagicButton_2.0_UPX
NetCFVersion
O2_Operator_UPX
PQView
Regedit_PHM_0.70+TRE_0.90_UPX
Reset
SimMessaging 0.04
SoftKeyAppletEx
TaskMgr1.6
Tcpmp_0.72RC1_UPX
TodayAgenda
Toggle
Total Commander 2
TreoSpeedDial_UPX
VJVolubilis_0.41_UPX
WM2k5 SMS Alert Fix (Himalaya?)
WM5 NewMenu_1.0_UPX
WM5torage 1.7 (seems 1.5 is more stable)
XCPUScalar
idiffce_0.3_UPX
Personally i miss AEButton package but can't do it.
Some of them are unfinished (NET CF2 is the most important of them), some of them are untested because i'm still in process of converting new packages
And it would be nice to group packages by type, maybe place them in submenus
Click to expand...
Click to collapse
this is exactly what I want.. people share their stuff.. and make our BA more rich with feature/option on spesific stuff... yes u might modify anything if u thing necessary (as long u didnt delete it ...lol) and inform about the update, so others know about it.
fraser said:
Hi helmi, this is real good stuff.
What's the intention however? I quite like the current state of affairs with everyone focussing on one ROM. One ROM to rule them all etc.
Is the idea for people to start creating their own? I'd rather see everyone pull together to produce one fantastic BA WM5 ROM. We aren't all that far away from it just now. But if we start to fragment the effort, it'll slow things right down.
Click to expand...
Click to collapse
hmm... maybe that could happen, but I beleive if we make it together? maybe it'll slow a bit, but more bug will be fix/resolve, share experience, it doesnt matter about who makes the rom. well, we'll see about this proggress...
About ROM Kitchen and 'the One ROM'
The ROM Kitchen is a wonderful idea.
IMO, things should walk towards stabilizing a base ROM with all features working (including WModem ).
But we also shouldn't leave to the users the effort to create their own ROMs, that's too troublesome.
Maybe all devs could get closer together and agree on some tools to integrate to it, and call it the 'XDA ROM', instead of Bepe, Helmi, TuMa or whatever.
So, we could have a 'BASE ROM', meant to be used on the ROM Kitchen, and the XDA ROM supported by all devs, built from the BASE ROM with tools which were agreed to be useful, so the less geeky can have a nice working ROM to update their BAs with. With things like PHM regedit, ability to choose between BT stacks, GB Soft Tweak and other useful stuff.
That does not stop the devs from having their own name branded ROMs placed on the site...
Agreed, a base ROM system is the best of both worlds. Say I was to pickup a base ROM and build on it, is there anything I can do that can't be done using ExtROM installers? Sure, you get to put stuff in the ROM, but it's already stuffed full it would seem!
I remember reading about an anti-theft application that you could put in the ROM. If the phone number changed, it would start sending you text messages telling you about the current owner/thief. Is this an option for the BA once we get a kitchen?
I will test it tonight after work, , i will test my latest SAP package and maybe if it works OK i will post it in this thread
i still have to dump some devices roms to see what can i get from them, at this moment i have new versions of CommManager and WlanMgr and maybe fix for wifi integration, but first should test it...
Once again i want to thank everyone involved in WM5 development for BA
It will be a very long list .. so i will mention just a few names:
mamaich, bepe, helmi, logout, tuatara, Midget_1990 and many more
Right way to roll in UPXed system apps?
OK, I have just decompressed all files, but I have no OEM packages rolled int yet.
I have tested many UPXed system dlls and exes, and I would like to roll them in to save space, in place of the original ones.
Where do I put them?
Attempted to build a base rom from the files provided and i am getting an error after clicking on CreateOS. The error is "Error: OS\2849e391-1e39-4a98-87b9-53932dec51d3 is not listed in packages.sof". How do you add or remove packages listed in the sof file or is that possible? How can i remedy this error?
Thanks in advance
i have 3 errors for 3 folders in os folder, i just moved them into oem folder
more results soon
I had the 3 errors too, and moved the files to OEM. The ROM image was built (apparently) was successfully built.
BUT, the million dollar question is:
How much free space do we have without adding any OEM stuff at all (a BARE ROM)?
We need to know our KB budget to know how much we can roll in...
I have the same error. What did you move exactly?
OK i have it.
It's:
2849e391-1e39-4a98-87b9-53932dec51d3
e3055288-19cd-4317-9125-a63654628fb3
fb30fdba-23d9-4a92-af78-041b1ee1d46c
Move them from the OS directory to the OEM directory
Marx2 said:
I have the same error. What did you move exactly?
Click to expand...
Click to collapse
When you get the error, move the folder with that name to OEM.
Another subject:
Hey all,
I have unpacked the ROM (nk.nba), replaced all folders ending with .exe and .dll with the actual file contained in each, and UPXed all exes and dlls.
Suspicious files are automatically skipped by UPX, and I compressed them with 'upx -i --compress-exports=0 --compress-resources=0 --strip-relocs=0', because when I was testing compressing (Office) with the default options, it didn't work. All compressible files worked, with these options.
The 'dump' contents went from 52,3 MB to 30,6 MB.
The catch: I don't know if the nk.nba generated from them will work
I haven't tried repacking it into an nba and flashing a ROM. Does anyone want to experiment with this file?
EDIT:
After BuildImgfs.exe finished, it reported the following:
Total Sectors: d2a8
Used Sectors : b984
Free Sectors : 1924
In decimal: 53928,47492,6436.
How big is a IMGFS sector? 512bytes? 1KB? more?
/EDIT
i did it with a few files
simply deleted them and created OEM package with UPXed versions
My Himalaya is flashing now AKU 3.2!
It flashed ok, hovewer entering BT settings hangs device
I will wait for Bepe
EDIT: BT stack is my fault cause by UPXing it
i create my rom ... very fast
but when i turn off my 9090 , it don't turn on ( display is balack) :evil:
any solution?
hi,
how to build a SD-Card Images?
DEV STOPPED DUE TO BROKEN DEVICE
After 1/5 years of flashing and testing my device has died so is time to move on to an X10
i am glad that i could contribute to this comunity and improve an wonderful device released without updates and proper software
new Simplicity 035
!to lock device press long end key
ROM
http://hotfile.com/dl/80099972/d92e93b/X1_Simplicity_035.rar.html
Kitchen
http://hotfile.com/dl/79038370/1993115/X1_Simplicity_010_kitchen.rar.html
NEW ROM X2
http://hotfile.com/dl/46430983/30d4a41/r10bx2.rar.html
Thanks to all cooks and clefs that did not forget the real purpose of this forum and share !
______________________________________________________________________
______________________________________________________________________
Bepe Kitchen
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BEFORE REPORTING ANYTHING PLEASE SPECIFY KITCHEN VERSION AND LANGUAGE
I CAN NOT TRACK PROBLEMS WITHOUT THIS
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
______________________________________________________________________
Visual Kitchen with real 6.5 XIP RHODIUM BASE
______________________________________________________________________
NEW KITCHEN BASED ON MIXED OEM FROM WM DEVIECES
http://hotfile.com/dl/39478945/86eb812/k2.54_10.rar.html
Visual Kitchen with real 6.5 XIP X2 BASE
http://hotfile.com/dl/39711502/da4485d/k11x2.rar.html
BUGS
for gps bug in wm6.1 just copy dnsapi.dll from any oem to the new oem
______________________________________________________________________
OTHER PROJECTS
!!!! GAME WARCRAFT 2 WVGA (WARGUS) fixedhttp://forum.xda-developers.com/showthread.php?p=3491567#post3491567
!!!! GAME STARCRAFT 2 WVGA (STRATEGUS ENGINE)http://forum.xda-developers.com/showthread.php?t=497086
Regional Time Clock Settings http://forum.xda-developers.com/showthread.php?p=3623077#post3623077
______________________________________________________________________
______________________________________________________________________
Bepe Kitchen Intructions
USAGE.....
unpack the core kitchen to c: drive
unpack an sys&xip inside
unpack an oem inside
Run 2_Create_ROM.bat
check KITCHEN\INFO\WMReloclog.txt latest line
if it last adress is starting with 01 rom will boot if not
recmod some dlls and try again
____________________________________________
Recmoding
nueRecMod.exe module_name
copy resulting file in place where module was
Folders that can be safely recmoded
BROWSING*
ConfettiCore*
CHome*
BROWSINGCORE
AdobeFlash*
browsingie*
Entertainment*
IPSECVPN*
MSTag*
Perfbox*
RemoteDesktopMobile*
Skybox*
Skymarket*
Transcriber*
VoiceCommand*
Webview*
WelcomeCenter*
WindowsLive*
WMWidgets*
! * means all folders that have the same name
big thanks to bepe,duttythroy and all other that made this possible for their work in this comunity
and itje for all his contributions
Da_G for wm6.5 porting and bug solving
which version of the blackstone are you taking them from?
I've not used the very latest rom yet, but the best Dshow seem to be from the 2nd quartz rom.
So you've got an X1 now? Are you likely to be getting involved in the android dev for it?
fards said:
which version of the blackstone are you taking them from?
I've not used the very latest rom yet, but the best Dshow seem to be from the 2nd quartz rom.
So you've got an X1 now? Are you likely to be getting involved in the android dev for it?
Click to expand...
Click to collapse
next project
for now i am triing to put an kitchen up
BR
Uploading ?
jerpelea said:
Hy all,
i have a new kitchen for you
is based on 2AA original xperia and latest Blackstone OEM and SYS
UPLOADING.....
Click to expand...
Click to collapse
Hi Jerpelea,
Have you been able to get this uploaded somewhere?
I am happy to put up a Rapidshare mirror when you do.
-Kodiak7
lookin forward to see a great change.... wishing to cooked it myself...
kodiak7 said:
Hi Jerpelea,
Have you been able to get this uploaded somewhere?
I am happy to put up a Rapidshare mirror when you do.
-Kodiak7
Click to expand...
Click to collapse
i was working on all known bugfixes
removed pannels
added tf3d (blackstone)
added calculator
fixed storage
fixed comm manager
fixed dialer
i hope to upload today the latest version
added UPX compression
BR
Feels like a dumb question, but can we download this somewhere? I'd like to experiment on cooking my own rom. I don't have the illusion I can do it better than Itje or Jack, but some experience on how hard it is to release a stable rom would be nice......
Kitchen Launched
Error building boot.hv
Using all of the default application selections, I receive the error popup 'Error building boot.hv!'
The log.txt file in the temp directory is:
ERROR: C:\MacB\private\winceos\COREOS\filesys\reg\reghive\.\hive.c line 877: FS: Registry Exception Handler
Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
wmain: (RGUComp) !ERROR failed building BOOT hive
*EDIT* Looks like the kitchen doesn't work on Windows 7, but it does on Vista.
Created and flashed with this, pretty impressed with the speed of it...only thing I see is that the bot up is very slow,but once the today screen comes up...very fast.. Had to create and flash 2 times as was stated in the directions for this.
WC
downloading. and thank you for this.
will let you know how it goes.
new diamond 2 sys and oem launched
BR
cool. will have a look when it's done.
jerpelea said:
new diamond 2 sys and oem launched
BR
Click to expand...
Click to collapse
hi there, i've tried your new kitchen with diamond 2 oem and its working great, thanks for sharing this kitchen.
1. i just noticed that i takes a while for the album tab to load pictures & for the music tab to search music.
2. also in settings tab, my contact card does not do anything.
3. and also in home tab, the camera soft key is not working.
4. the hardware keyboard is messed up.
other than that it works great & fast including in landscape mode.
will still test some more with this new kitchen.
thanks again.
edit:
1. i noticed that the contact editor is not working properly, when adding favorite people manila restarts.
twisted
...Cool...New Manila
jerpelea said:
Hy all,
i have a new kitchen for you
is based on 2AA008 original xperia and latest Blackstone OEM and SYS
Download
SYS 20769(20769.1.4.5) WM6.1 from HTC Blackstone shipped rom
kitchen 1.029 http://rapidshare.de/files/45443253/KITCHEN_X1i_20769_20769_6.1_1.029.rar.html mirror http://www.dump.ro/fisiere/kitchen-x1i-20769-20769-6-1-1-029-rar/93981/oKtbw0sLEO1CwZYL
kitchen 1.514 http://rapidshare.de/files/45566055/KITCHEN_X1i_20769_20769_6.1_1.514.rar.html mirror http://www.dump.ro/fisiere/kitchen-x1i-20769-20769-6-1-1-514-rar/95204/Z8SyGwaHupE46yE5
SYS 21014(21014.1.6.0) WM6.1 Beta bbs.xbeta.cn
kitchen 1.515 UPLOADING....
SYS 21159(21159.5.0.0) WM6.5 Beta 3 from ppcgeeks.com
kitchen 1.515 UPLOADING....
big thanks to duttythroy (sources) and SatScan (dump)
Click to expand...
Click to collapse
Excellent job!!! I'm looking forward to the WM6.5 kitchen. I wanna see if i can put the new tfl3d on it.
yes it really is superb, the new manilla has some of the same errors as ITJE's beta 1.
Contacts mainly, but otherwise it's very well done. build is very easy.
OH and it does work in WM7, it's just some of the tools used need setting to be vista compat mode (running as admin helps as well).
fards said:
yes it really is superb, the new manilla has some of the same errors as ITJE's beta 1.
Contacts mainly, but otherwise it's very well done. build is very easy.
OH and it does work in WM7, it's just some of the tools used need setting to be vista compat mode (running as admin helps as well).
Click to expand...
Click to collapse
I think there is a deeper issue with the contacts tab because tfl3d still crashes when u do certain things in the contacts tab. I wonder if we are missing something important....
I decided to use Visual Kitchen 1.5 to cook my ROM, but i have a few questions. After i dumped the contents of my original UK R3AA010.nbh i saw that the kitchen uses XPR compression. I was thinking about not compressing anything for the purpose of speed. Can it be done? And something else i would like to learn. The file that will be created in the end will contain only the OS part and not the radio and SPL that came from the original ROM right? Thank you. Wish me luck...
1-
NBH has many parts: OS, radio, splash 1, etc...
most cookers (if not "all") only include OS part
but you can include anything you want (outside a stock kitchen, using NBHtools)
2-
uncompressed ROM ???
huh... it wouldn't fit
MS, HTC, Sony, Samsung they all use XPR
Just a couple of small devices use LZX (better compress ratio, but also slower to decompress in real time use)
OK. Thank you gtrab.
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
you will get flamed for this
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
This really is an admirable goal, but you're attempting to bite & chew WAY more than your mouth can handle!!!
You're a web developer, good.
You have no experience in developing android roms, bad.
You want to develop a free kitchen, good.
You have no experience with cooking roms, bad.
You want developers to help you in exchange for a free kitchen for their rom, bad & good.
You don't know how to update the "update.zip" file and re-sign it, bad.
You don't know how to add an APK to the above mentioned "update.zip" file and re-sign it, bad.
You have a little bit of an idea, but want a clearer process, bad.
All of the above noted BAD points, have been discussed, referenced, and linked on these forums countless times shararti.
You really need to search, read, search some more, and apply what you've learned.
I too am a Web Developer/Designer. I've been in the business of creating websites since 1999 (off & on). And the above mentioned project it something I WON'T EVEN DARE ATTEMPT.
Good luck!
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing. Well I do know signing and adding apk part, and the rest, i agree, i need some help. I'm willing to give my summer to this project and develop this kitchen for the xda community (i'm also willing to give it away to xda). Now if anyone is willing to help me, please pm me.
Actually, it isn't that difficult.
There are quite a few scripts and programs that you could simply employ on your website. I'm sure those developers wouldn't mind
You would have to tier your ROM baking based on the major ROM cores, and the features swappable between flavors of those cores.
It's simply letting the user choose what he wants in his base ROM, pushing the files into the zip, and running the script to sign them.
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Sounds like a very cool idea and I wish you all the best and hope you find some programmers willing to teach you about roms, and you can do the web coding and make your idea a reality.
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
APrinceAmongMen said:
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Click to expand...
Click to collapse
Perhaps, share the information here once you two have things worked out?!
shararti said:
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing ...
... I'm willing to give my summer to this project and develop this kitchen for the xda community ...
Click to expand...
Click to collapse
XDA is such a huge resource, full of solutions, bricked devices and lost newbs LOL.
After trolling for a few months, I was ready to flash my first WinMo SmartPhone a few years ago. I haven't used a 'regular phone' ever since.
This would be an ideal summer project. As I said, I'm also a Web Developer.
Hit me up for some theme/template ideas. I do most of my work with Notepad++ and Adobe Fireworks CS4.
Goonish said:
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
Click to expand...
Click to collapse
hhmm, never thought of that!
You're right ... sounds unreal!
Something the iFans would never be able to attain.
Even better, how about, instead of flashing some large file, only the ones affected by an update are flashed, resulting in a much SMALLER file (thus saving on data usage) and a FASTER flashing (saying on battery life).
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
Well it all depends on what you want. I would suggest you have a base rom without the boot.img stored with minimal capability in a folder. then allow the user to choose what type of kernel and capabilities they would like with it. That will be the minimum amount for a rom. Then you can follow it up with additions such as extra scripts and applications that can be added and moved to the appropriate directories. at the end, you would zip up the selection and sign it, with the appropriate update-script (which should be the same as the stock rom's unless the additions require something drastic)
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
That should be about right. its 3 am here lol so i may be missing something. pm me if you need more help or post here
Exactly.
The great thing about it. The ROM core files can be optional. You can bake a kernel or you can bake CM w/ custom kernel and custom mods, i.e. modded phone.apk. You can bake anything and everything.
Mmm baking never sounded so good.
Check this website out:
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/
My small contribution to this project
The basic kitchen:
forum.xda-developers.com/showthread.php?t=633246
Sorry it's not a link, apperantly new users cannot post links
flybyme said:
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
Click to expand...
Click to collapse
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
shararti said:
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Click to expand...
Click to collapse
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
shararti said:
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
Click to expand...
Click to collapse
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
You MAY have to change the update-script if for example you want to put some things in the data partition and symlink them or change the data partition to include the ext partition instead of just for apps. Changes like that are usually for ROMs that are too big to fit properly on the nexus ( youll also have to check the size of the system and data folders to make sure they fit on the phone without modification)
Most of this stuff will be figured out in testing haha but ya at the very basicee its what you have here. You really have to know what you actually want users to be able to cook and then build the kitchen to that effect
flybyme said:
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
Click to expand...
Click to collapse
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
flybyme said:
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
Click to expand...
Click to collapse
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
shararti said:
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
Click to expand...
Click to collapse
Well it really depends on what ROM's your looking at. Some devs change the apps to their liking. For example, CyanogenMod has a modified Settings.apk that has features specific to his rom. However, all ROMs have Settings.apk. As such, you will probably have to have a Core ROM folder for each specific rom.
I would suggest looking at other online kitchens and see what features they offer, come up with a specific feature set and then decide what direction that you want to take.
zipalign is a compression technique that optimizes how .apk files are accessed in android. it makes things faster and is not required but would be nice to have. you lose the benefits if you open and modify any files from a zipaligned apk
Let's clear some things up here.
First, core files are not interchangeable between main roms but only flavors of those main roms.
As of now, we have 3 main roms for the nexus one.
CyanogenMod, Modaco Custom ROM, and Desire/Sense Roms.
Each of these roms have their own unique cores amd features and are not interchangeable.
There are flavors of each of these roms.
Flavors of CM has parts that are interchangeable with other flavors but use Cyans core.
Say there is one CM flavor that has some themieing and a few other changes you don't want. You can take the themed files and put them into your CM base and leave the rest out.
You can't put that themeing into a Modaco Custom ROM though.
Kernels I believe are the only things can be put into any ROM base. Most apps are as well.
Now that I look at it. Doing a Nexus One kitchen isn't that difficult but making a full featured HTC kitchen would be a mountainous task. There are so many mods, roms and themes to keep track of. We'd have to designate people from each device forum to feed us the ROMs and parts that are active and functional.
P. S. Lectures are over at 7 today. ill be able to crack down on it with you then
Kitchens are for the Food Network...
well thanks flybyme and APrinceAmongMen, these 2 posts really cleared up somethings. I'm in the process and will keep you guys updated.
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
shararti said:
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
Click to expand...
Click to collapse
boot animations are located either in /data/local or /system/media
radio flash will require you to change the update-script
you can look at the FRF50 update with the radio to figure it out ( or pm me if thats too difficult, its a little late else id do it myself)
Just make sure the radio is excluded by default.
Another thing about radios, the newest radio usually works on older roms, but old radios don't work on the roms released with and after the newest radio.
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!
just what i need
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?
Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.
Just when I thought this kitchen was a goner, you came along and made it work again
I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal
Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.
The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)
Awesome job mate :good:
tomorrow`s homework !
thanx !
Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!
Great.
Just what i was looking for.
dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps
Please link to download the kitchen, thank you very much.
misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.
This is great!
Thanks dsixda.
YZ.
Please not see me? can give direct link? thank you very much
misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.