PPCGeeks - New kitchen release

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- HTC Apache (http://forum.ppcgeeks.com/forumdisplay.php?f=14)

- - New kitchen release (http://forum.ppcgeeks.com/showthread.php?t=4843)

Almost ready for prime time!

Well, I took the plunge this afternoon and am posting this from my PPC-6700 newly flashed with the new R1 kitchen.

It went well for the most part. I did Kolano's edit to the batch file and then was able to just enter "nk.nbf" and "nk.nba" for the filename in the encoder with no other path information. If we can get that fixed, I think we have a winner.

Before that, I took the time to go through all the "option.xml" files to set the checkbox defaults. Now the next time I run BuildOS.exe, the checkboxes will be where I want them. That is priceless... as is the included Alltel ExtROM files (thanks CaptainJager!).

Now, all I have left to do is figure out ho to get the 6 programs I use into the OEM. Unfortunately, they all seem to fit BigJ's definition of "complicated". We'll see how it goes...

Thanks to everyone involved in this!

Quote:

Originally Posted by Trident

Quote:

Originally Posted by kevdawg

Quote:

Originally Posted by Anton2006

Quote:

Originally Posted by Kolano

Quote:

Originally Posted by Anton2006

Quote:

Originally Posted by Rally1

Which Fat File error, there are two. One is a pathing issue, and one doesn't really matter.

One of the final steps, use the extended rom tool, hit encode, it comes up with a fat error, you click okay and it's supposed to encode the rom anyways, mine didn't, it just sat there

The current kitchen has an improper path specified to the .nba file (i.e. the file specified in the "FAT16 file:" box). Make sure that points to the nk.nba file found in the Kitchen's temp folder. After doing that you will still receive an error about the ROM being too large, ignore that, hit OK, and you should be good to go.

will give it a shot, thank you ! :)

I still get an error after pointing it to the right .nba file saying:

Unable to encode FAT16 image.

I fixed the FAT16 image location, but the Extended ROM file location doesn't look right either. And I can't find it anywhere- I did a search for nk.nbf in the folder and no results. Is the nk.nbf created during a previous point in the process or is it something that should be in one of the folders?
Still unable to encode.

The .nbf files is the output file, it is not supposed to exists before you hit encode. The field that gives a location for the .nbf file is merely specifying where the .nbf file will be writen to.

So the secound fat 16 file size error is ok?

The encoder worked...after it gave me the file size error...

Thx

I realize this post is not contributing much; but every once in a while you're just so excited by something you want to share.

The latest kitchen is greatness synthesized! You could bottle it and sell it at this point. I bought my phone on December 27th 2006, and today, it is what I finally wanted it to be. It really took off for me when I figured out how to grab the OEM's from the FTP site and add them into the kitchen.

This is purely my opinion, but I would recommend to anyone thinking of flashing a new ROM, focus on cooking your own via the new kitchen. just download it and start reading BigJ's instructions.

As far reconciling BigJ's instructions with the actual ROM building process, I can tell u what I did when I got the FAT16 error message...

1) Cancel out of the Encoder / .bat process.
2) copy ur 'nk.nba' file from the 'temp' folder to the 'tools' folder
3) run 'HTC64_Extended_ROM_Tool.exe' from the 'tools' folder manually
4) On the 'Extended ROM file' field, lop off the directory structure and simply go with 'nk.nbf' (just like the picture shows in BigJ's instructions
5) On the 'Fat16 file' field, lop off the directory structure and simply go with 'nk.nba'
6) click 'Encode'
7) move the resulting 'nk.nbf' file from the 'temp' folder to the 'upgrade' folder
8) copy the 'APACUpgradeUt_noID.exe' file from the 'NoID flash utils' folder to the 'upgrade' folder and run it.
9) follow the instructions

Quote:

Originally Posted by Kolano

Quote:

Originally Posted by Trident

The .nbf files is the output file, it is not supposed to exists before you hit encode. The field that gives a location for the .nbf file is merely specifying where the .nbf file will be writen to.

OK. That makes sense. But I'm still getting the "Unable to encode..." error message.
Like the FAT16 directory, the nbf file output directory is also pointing to the wrong place (somewhere on my C: drive). Is it possible that it being pointed to the wrong place is causing an error? When I try to change it to the correct directory, it always changes back.

Like bonuts, I found most of the directions on how to set the paths somewhat incomplete/ambiguous. R2 should address the problem, but I found making Kolano's changes the easiest (least typing):
In CreateROM.bat

Code:

CALL ..\temp\HTC64_Extended_ROM_Tool.exe

changed to

Code:

REM CALL ..\temp\HTC64_Extended_ROM_Tool.exe 

CD ..\Temp 

CALL HTC64_Extended_ROM_Tool.exe

Then, the Extended ROM file filepath should be

..\upgrade\nk.nbf

The FAT16 file filepath should be

..\temp\nk.nba

nk.nba

(either setting should work since temp is the current directory - I use ..\temp\nk.nba for consistency) [relative pathing works for me] If you save the project, you'll never have to make these changes again!

Push encode, acknowledge the "FAT16 is to large" error, and follow the remaining directions.

The only problems I've noticed so far are:
If you select O2 Plus, you have to uncheck

(these load the same DLLs O2 Plus loads, leading to a file exists error when you build)
O2 Calendar
O2 Last Call
O2 Running Programs

and you have to check

(these load additional DLLs - if you don't select them, your PPC will lock up on it's initial boot)
O2 Meters
O2 Sound Profiles

[the easiest way to fix this is to copy o2Meters.dll and o2profile.dll into the optional_o2 directory - then you either select O2 Plus and get it all or you select the individual components.]
Additionally, o2opr.dll (for the divert option) is not present in the optional_O2 directory, so I imagine the Divert Profile in O2 options won't work so well.

VoiceCommand installation requires voicecmd.exe be copied into the appropriate Optional_Voice_Command... directory before you start building. [you can find directions on how to extract this file from a licensed copy elsewhere on the site]