New kitchen release - Page 8

avaya · #71 (**permalink**) 06-09-2007, 02:09 PM

I just point to the nb file in the temp directory and point the nk.nbf file to the Upgrade directory manually everytime.

Are you guys trying to make it so people won't have to do any manual intervention?

Kolano · #72 (**permalink**) 06-09-2007, 02:23 PM

Quote:

Originally Posted by colonel

I believe this should work if someone wants to test it out.

Results in "Unable to get Fat16 filesize" for me.

Thus far in testing I can only use paths that includes a full directory path from the drive letter. For instance...
"C:\Documents and Settings\Username\Desktop\Phone Roms\Helmi_APAC_WM3.5_NEW_Kitchen_R1\temp"
"\Documents and Settings\Username\Desktop\Phone Roms\Helmi_APAC_WM3.5_NEW_Kitchen_R1\temp"

But if I adjust the CreateROM.bat file to call the ROM encoder differently...

...
REM CALL ..\temp\HTC64_Extended_ROM_Tool.exe
CALL HTC64_Extended_ROM_Tool.exe
...

Then the generic paths...
"..\Upgrade\nk.nbf"
"nk.nba"
...work.

I'm not 100% sure if that change effects other CreateROM.bat processing as of yet though.

One other annoyance, since the ROM encoder is copied from \TOOLS to \temp each time, saving your changes when running CreateROM.bat will have no effect. Be sure you save your files to "\TOOLS" if you want changes to stick.

Kolano · #73 (**permalink**) 06-09-2007, 02:37 PM

Quote:

Originally Posted by colonel

"Unable to encode FAT16 file" is a different one of a yet to be determined origin.

This occurs when the "Extended ROM file" location can't be found.

peacock93 · #74 (**permalink**) 06-09-2007, 03:21 PM

I just did as search fo nk.nbf and cannot find it anywhere in he "helmi_APAC_Wm3.5_NEW_kitchen-R1" folder. I must be missing something in the instructions. Do I have to create the nk.nbf??

**colonel** · #75 (**permalink**) 06-09-2007, 03:24 PM

Well, what is strange is the encoder should create the nk.nbf for you. However maybe this encoder is different and needs an existing nk.nbf to either use or at least validate the path. I will try to get some more testing done on this.

For now, there is a nk.nbf in my ftp folder that you can put in your Upgrade folder.

Kolano · #76 (**permalink**) 06-09-2007, 03:49 PM

Quote:

Originally Posted by colonel

Well, what is strange is the encoder should create the nk.nbf for you. However maybe this encoder is different and needs an existing nk.nbf to either use or at least validate the path. I will try to get some more testing done on this.

For now, there is a nk.nbf in my ftp folder that you can put in your Upgrade folder.

The input is just a little strange. The Extended ROM Location points to a file rather than a directory. When you use the "..." selector you need to also specify the filename you want it to save as "nk.nbf" before it will let you Save.

As mentioned be Colonel, the "nk.nbf" is the output file, and does not need to pre-exist.

Kolano · #77 (**permalink**) 06-09-2007, 04:02 PM

Quote:

Originally Posted by Kolano

Quote:

Originally Posted by colonel

I believe this should work if someone wants to test it out.

Results in "Unable to get Fat16 filesize" for me.

Thus far in testing I can only use paths that includes a full directory path from the drive letter. For instance...
"C:\Documents and Settings\Username\Desktop\Phone Roms\Helmi_APAC_WM3.5_NEW_Kitchen_R1\temp"
"\Documents and Settings\Username\Desktop\Phone Roms\Helmi_APAC_WM3.5_NEW_Kitchen_R1\temp"

But if I adjust the CreateROM.bat file to call the ROM encoder differently...

...
REM CALL ..\temp\HTC64_Extended_ROM_Tool.exe
CALL HTC64_Extended_ROM_Tool.exe
...

Then the generic paths...
"..\Upgrade\nk.nbf"
"nk.nba"
...work.

I'm not 100% sure if that change effects other CreateROM.bat processing as of yet though.

One other annoyance, since the ROM encoder is copied from \TOOLS to \temp each time, saving your changes when running CreateROM.bat will have no effect. Be sure you save your files to "\TOOLS" if you want changes to stick.

This should have said...

Code:

REM CALL ..\temp\HTC64_Extended_ROM_Tool.exe
CD ..\Temp
CALL HTC64_Extended_ROM_Tool.exe

Then the generic paths...
"nk.nbf"
"nk.nba"
...work.

peacock93 · #78 (**permalink**) 06-09-2007, 08:52 PM

Colonel,

Adding your nk.nbf to the folder did the trick. This is one screaming fast AKU!!! Now for my new problem; I can't load any programs to my 6700 since the NEW rom update. Everything that I chose from the generic kitchen works fine but I can't load any new programs to my phone. Also, I have an issue with internet explorer. It will not go to the internet even if I have a wifi or data connection up and running.

lecumeur · #79 (**permalink**) 06-09-2007, 10:23 PM

At first, thanks for the good job: everythink work as it should.

Colonel, adding your nk.nbf and modifying the createrom.bat did the trick.
For now i am not observing anything strange after flashing the phone.
I did not let verizon customization to run. I just did *228. Mail, exchange synchro, web are ok. I will try bluetooth and wifi tonight.

That kitchen is nice - the doc is a nice job - but still complicated - anyway, the phone is now stable and fast as it should be - Good Job!

Bluetooth and Wifi fine

**Trident** · #80 (**permalink**) 06-09-2007, 11:43 PM

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.