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

[finster869]

Do a search for Power and you will come to HKLM\System\CurrentControlSet\Power

Thanks again....don't know how I missed it!

[Perasite]

One thing I really liked about Mike's method when creating my custom ROM was it was step by step. I felt like Mike was right next to me saying "OK, now do this."

With the kitchen method, I managed to screw up pretty quickly. It sounds really easy, but I like the hand holding Mike gave us. Once someone gets a good grasp of the Kitchen method, I'd really appreciate if you could write up instructions like Mike did so the rest of us don't have to bang our heads against a wall for too long.

This sure is fun, though!

[finster869]

As SchettJ said in the IMCOKEMAN thread:

Originally Posted by schettj

Cool all around!

Here's my suggestion (while we all wait for ppcgeeks 2.0 tomorrow!)

Let's call yours the baseline - once the ftp site is up, upload your kitchen to it as such. Looks a little cleaner then mine, and clearly it's working

As we all make OEMs, we upload em to an "OEM" folder on the FTP site.

The HOW TO should tell folks how to

(1) download the baseline + any addition tools (wide's tools to make the final rom & the rom flasher package)
(2) build the baseline
(3) flash it.

and then...

(4) how to add/remove OEM packages (mostly just download the OEM packages you want, put em in the OEM folder of your kitchen, and then go from (2) above) - or delete/move a package out of the OEM folder to remove it...

(5) how to remove apps from the baseline image - for example, removing MSN is done by removing the three MSN folders from OS, then building from step 2 above...

and finally

(6) how to make your own OEM package from a CAB file, and/or manually by poking around your own device after installing an app.

We want to make sure also we don't get ppcgeeks into any trouble, so no commercial OEM packages, right? I you did want to move a commercial app into your rom, you could build your own OEM package for it, but you'd not want to share it.

Spiffy?

So, we should have a step by step in the near future. People are still tinkering with the kitchen approach.

[vboyz103]

so I wanted to add wisbar advance and use the WinCE Cab Manager to extract its content from the cab file. Now there are sub directories in it, and it doesn't seem like CreateOS.exe like sub directories. How do I add sub directories correctly for CreateOS.exe at all?

[jokeman3000]

Does anyone know if it's possible to change the splash logo in kitchen?

[pgdeaner]

Since helmi was nice enough to provide a link to a 3.5 kitchen, I have been playing around with the 3.3 kitchen for the apache and subbing the 3.5 OS and LOC files from the BA kitchen. I am able to get the PPC6700 to boot, but it locks up after the config routine at the point at which you tell it to skip the password. Anyone else playing with this or made more progress than I have?

Originally Posted by helmi_c

yes it does... I dont know if it workin or not since I dont hv the device... this kitchen supposed to produce just like my AKU3.3 for apache, with some mod...

I dont see any instruction out there...Its hand made... as u can see, there not much people create kitchen...Actualy I dont see any for now, except old one by bepe, I hopes that u dont get bored with my name with kitchen...hehe
here's AKU3.5 Kitchen For Himalaya (check the OS & LOC ?)
http://buzzdev.net/index.php?option=...=read,26,28289
And here's AKU3.5 Kitchen For Blueangel (check the OS & LOC ?)
ftp://xda:mad:da@ftp.xda-developers....itchen__R0.rar
and also wizard and prophet, but I can post it, u might check pdamobiz.com

[ImCoKeMaN]

I haven't worked on that yet, but now that my kitchen is out i was planning to give it a shot. I think Wideawake was able to boot aku3.5 at least to that point, but i don't know of anyone getting any further on the apache yet.

I think the kitchens will make it easier though as we can mix and match the old and new drivers from the OS and LOC folders until we have a set that works. I'm sure some drivers will be better in the updated version, but others are probably the cause of the lockups. It will be a lot of trial and error i'm sure, but hopefully we'll be able to get a working 3.5 rom soon enough. Not as sure about a crossbow one though since it can't really be shared yet, but maybe soon enough?

[colonel]

Originally Posted by jokeman3000

Does anyone know if it's possible to change the splash logo in kitchen?

Just use the tool in WideAwake's Rom Tools to change the splash screen on you .nba.

[schettj]

Originally Posted by ImCoKeMaN

I think the kitchens will make it easier though as we can mix and match the old and new drivers from the OS and LOC folders until we have a set that works. I'm sure some drivers will be better in the updated version, but others are probably the cause of the lockups. It will be a lot of trial and error i'm sure, but hopefully we'll be able to get a working 3.5 rom soon enough. Not as sure about a crossbow one though since it can't really be shared yet, but maybe soon enough?

Yep - work's still killing me (and will until mid week next week - sigh) but I'm keeping track of many of the interesting ROM Kitchen gotchas we're finding.

This one is important to not lose track of...
In OEM packages, we want to avoid as much as possible the file copy action, as in

Directory("\whatever"):-File("foo.bar","\Windows\foo.bar")

in our initflashfiles.txt for an OEM package, as that makes a copy in storage memory, not ROM (which I really thought was not true, but others confirm is true) and eats storage memory, for anything but small (lnk) files if at all possible.

[colonel]

You shouldn't have to copy many files at all. Actually, the only ones that are copied in my Rom (other than .lnk files) are the ones set up by the Original developers.

The only thing I needed to use initflashfile for was setting up and copying shortcuts for exe files. This does not take up too much space and should be all you need to do as well.