How to make a custom rom using Helmi's AKU 3.3 ROM Kitchen
 

EDIT:

This started out as a request to gather new ideas for the next "Helmi" AKU 3.3 ROM - then Helmi chimed in and actually posted his Rom Kitchen that he used to build the 3.3 Rom we've all been using.

Read along and enjoy the journey. Here is the highlights:

here's the Apache AKU3.3 ROM Kitchen:
ftp://xda:xda@ftp.xda-developers.com....3_Kitchen.rar

and here's the instruction how kitchen work its might be difference a bit, but basically its on the same stuff:
http://www.buzzdev.net/index.php?opt...4,23392,page=1

Helmi told me, in PM, that the ROM Kitchen image above builds the exact ROM we started with - in other words, it will not have any .NET installed, and it will have the picture & video DLL problem, so those are the first two things to fix. It will also not have a working BT PAN profile.

So, if you are game to cook your own ROM with just exactly what you want, this is another way to do it. Read that second link above all the way to the end, there is a lot of info in there on how to add new OEM packages, and there are some example OEM packages as well.

My Personal Goal is to make a baseline 3.3 Rom Kitchen image with the simple fixes above (.NET 2.0SP1, fixed P&V DLLs) and release that, then start adding OEM packages for the SPRINT extended rom (so you no longer need that) and so on, for various freeware that I use. It will take a while, I don't have a ton of free time :D

Original Post Below:


Can we start this now? Is Helmi gonna cook us another one?

I'm not bashful, I'll start

#1 - 3.5 based if at all possible (with issues addressed below)

If not #1, then cleanup on 3.3 including

- correct dlls for pic&vid in rom
- working BT PAN
- .NET in rom (1.x ok, 2.x better)

I think that's really the short list. Just doing that will free up over a meg of store on internal memory.

Wide, you're plugged in with Helmi - is he considering/working on another rev? This one rocks, and I am totally happy it happened, but you know it could be just a bit *more* perfect :D

Check your PMs

-check
-not yet
-check

How about maybe saving some space by UPXing some files, like wideawake did with the aku 2.2 rom.

Also lets try to incorporate some of the necessary reg edits as well, so that the 6700 can run at peak performance.

Thats all i can think of.

Cant wait for the next rom!

Thanks to all involved

-s

those were my thoughts too all the above especially .net 2 and pic/vid files.... the upxed dlls would be nice too.

Hello all...

I have a better idea... what about rom Kitchen for APACHE? so everybody can built their own really customize what the rom contain...:)

here's the Apache AKU3.3 ROM Kitchen:
ftp://xda:xda@ftp.xda-developers.com....3_Kitchen.rar

and here's the instruction how kitchen work its might be difference a bit, but basically its on the same stuff:
http://www.buzzdev.net/index.php?opt...4,23392,page=1

lets the rom cooking era for APACHE device begin?...

This looks very, very confusing. What does this do?

I am very excited about this! Thanks, helmi_c!

that are tools and technique for built your own customize rom... yes built your own ROM... :)

u can add/replace an OEM* pack with ur personal needs and thats it.. u've just create ur own personal customize apache rom...

maybe read a couple of document will help to understand about how to make ur own ROM... trust me... its worthed...

hopes someone will post a customize rom soon...:)

* all app/addition/extras app, netcf2 for example, or broadcomm stack, icon customize, or regular app that u use the most to be built in rom.

Any idea how much free space there is to add files? It looks really straightforward.

Driver and SAP (Standar Aplication, like Button setting, device info), and also some driver like SERIAL_BTUR.DLL, TIACXWLN.DLL etc is a built in drivers also U might check the *.RGU file in DLL dir if it link to Drivers\BuiltIn then its not something u should mess around with cos its device spesific, u should not replace with other device drivers...

but hey, as far as I know? if u mess with roms? and if it wont boot? just get to bootloader and flash a working rom, and u're safe, I dont know if this applied to Apache device... but it should work the same like any other device I know...