New BuildOS - Report Bugs Here
 

This is the place to report any bugs you experience with the new BuildOS. Please try to be as thorough as possible in your descriptions (specifically: the error you got, the last few lines of the BuildStatus window (if applicable), and what you were doing when you got it). I will update this first post regularly as bugs are found/fixed.

ALL VERSIONS PRIOR TO 08/25/08 RELEASE ARE NO LONGER SUPPORTED.
If you are using an older release, you should upgrade to the 08/25/08 kitchen.

User Error:
1. Can't find ROM
- Your kitchen is incomplete. Either you are missing a needed .rar or you did not use a selections.txt file when launching BuildOS.

Known Issues:
1. Column headers may have letters one off from the actual letters.
- if you experience this issue, please post your OS, SP level, language, and version of .Net installed (including SP level).

2. When using the group buttons on the left, the group isn't scrolled to the same place on the right all the time.

3. 2.04/2.05 bootloader phones can have a rom that is too "full" without getting the "max rom size exceeded" error. The symptom will be white boot screen.
- currently, remove about 300K of OEMs to work around the issue.

Fixed Issues:

If you use updater and get a File Not Found error downloading Upater.exe or the kitchen help file, you MUST download updater.exe manually from http://ppckithen.org/downloads/updater.exe and place it in c:\program files\ppckitchen.org\buildos\updater (replace the existing file)

Okay, so its not a bug, more a feature request. And I won't take credit for the idea. Could we get a Nero-style size bar at the bottom of the screen? (I'm thinking as when you add items to your CD it shows usage like a percent complete bar, and it is green until you go over 650mb)
That, or just a column next to OEM Author as OEM Size?

Thanks for everyone's hard work, looks amazing so far!

Both are on my todo list. It's not as straightforward as you might think, however, so it will be some time before a version containing this feature is released.

I loaded BuildOS and got this error.

an attempt was made to load a program with an incorrect format

I am running XP x64 ed.

I have the same issue on Vista x64, so it must be a 64bit OS problem :-|

Maybe someone will make a fix soon for that. I really didnt want to have to build this on my laptop but i will if i have to. I can't wait.

i posted in the other thread about my issue with the missing .dll file. i actually solved that issue by copying the msvcr71.dll file from the \tools\ folder to the buildos\ root folder. it seems to go through without a hitch now. only problem is, i get stuck when i try to flash the rom. it's not finding my device.

i'm running bootloader v1.04 (at least that's what it says on the bottom of the screen).

edit: the exact error code i'm getting is Error 201. "get device data error". i've followed the steps in the documentation for RUU, but i'm still getting the same error.

Your device has the new bootloader on it. In the BuildOS window at the top of the screen you'll see a drop down that says "Standard". Click that and choose the X.04+ option and try building again.

thanks a ton, worked like a charm. thanks to all you guys that worked on this.

I don't get this one. Tried building using the new kitchen, buildOS gives me this error message every time, no matter how lean or full I pack the ROM. This started from the first attempt with an absolute basic ROM, "nk.nbf not found"

I take it this is a reference to one of the startup splash screens?

Extremely common error. You did not select the prj file from the proper folder during the encoding step. Unfortunately the HTC64 tool memorizes the last kitchen folder you were in, so when you chose the prj for you carrier it was from another kitchen folder. You should make it a habit to back out to C: and then purposely drill back down to the correct folder (in this case it would be C:\BuildOS\Tools unless you modified that path during install).

That will solve your problem.

LOL. Duh! You think after flashing a few hundred ROM's I'd remember that!
Thanks luv2chill

-TOV

I dont know if the tools have changed drastically since the old kitchen but with the older tools we have always been able to use x64 OSes (Vista and XP) to flash the ROMs.

Really? I'll remove that then. The tools have changed substantially, however. Please see me in the chat room - I need you to test a few things so I can narrow the problem down.

Here is Builders' Base BuildOS config.
 

this has the bare minumum necessary for a good kitchen install with apps you will need. see the attached file.:headbang:

U just need to change your .prj file.

Me and GGuruUSA are working on the 64 bit OS problem

Can you upload the config that leads to white screen for me, please?

Yeah, I haven't had any issues to date on Vista x64, not even connection problems that require new drivers or the change in the connection settings in WMDC. Hopefully you can get this resolved then, it would be much appreciated.

Changing network service locks up phone
 

I'm not sure this is a bug, but did not notice this till the new kitchen build. If I go into the phone, options, services and then network service and change the setting from EVDO to 1x or the other setting or just go in there and do nothing but say ok, it resets the phone. If I have one of the task managers on the top bar (HTC) then it locks up the device. I have to either hard reset it and then remove the task manager and put it back or leave it off. If I do remove it and put it back its fine after this and no longer locks up

This thread is for bugs with BuildOS, not with the kitchen itself. But to answer your question, that has happened with every ROM as far as I know. Simple solution: don't open that panel unless you plan to change the mode :)

Thanks, and sorry didn't pay attention to where this was posted.

I used the solution to the Verizon 2.05 bootloader problem that was posted and it worked perfectly. Then used the new build os to make my rom. I tried multiple times to flash my phone and it kept giving me an error of "wrong model".. and I was using the correct Verizon file to encode. However after reading another post here, I then tried changing the ruu from "standard" to "no id" and it worked right off!.. Is this ok? or should it have worked with the other, meaning something went wrong when I reverted the bootloader?
P.S.
And by the way I am really jazzed about this..I just fell in love with my phone all over again! You guys are great to put this out here for those of us with little to no experience-My paypal will be on it's way soon.

The new buildOS Is kick ass. You guys totally rewrote the book on it.
I had a quick question though. Did you talk or think about maybe adding a little size meter of the oems Maybe on the option.xml? Or A little box that would keep increasing to let you know how big your kitchen is getting with a limit size? Like when you make a cd every time you add a track a Little less space is left.

It's in the works.

having trouble loading the rom.. it hangs on the 1st boot screen..
i cooked up 3 roms and all of them seem to give this problem.i decreased the files in each one thinking i had an overcooked rom but it still hung there.. the initial htc screen didnt even goto the wm green screen. while cooking i cudnt find the reliance prj file so i loaded it from my previous wm6 helmi rom.. i had loaded the same prj file for a wm6 verizonguys rc1 rom so i can confirm that its working.. had to go back to that rom again to keep me on a ph.. thankfully the older one loaded fine now.
the problem i had was that the htc64 tool ..i had used to cook previous rom on this comp and it gave the older places to copy and get the nbk and fat16 files. i cud get the fat16 file from the rom folder but where do i save it .please specify the path as the tool doesnt remember anything. i even had to name the file as nk.nbf. as the name was also default.. however it encoded successfully but the buildOS tool gave an final error as nk.nbf file not found. then i manually placed the nk.nbf file which it saved to the noid ruu folder and ran the application . it loaded my rom till 100 pc and asked me to hard reset .but on hard resettign apart from the 1st screen with htc logo and the build and valus given nothing happened. tried soft resetting hard restting and all. but it wud alway give the same .. waited for sum time took out the battery n all but no avail.
please if u cud also load the reliance prj file which is missing in the tools folder. i have that working file but dont know where to upload it .
thanks ..

You are getting the file not found _because_ you are using a .prj from a different project. Edit your .prj (using htc64_encoder) to put the .nbf in the new kitchen's temp folder, save, and then you should be fine. You can upload you reliance .prj file here, just attach it to a post.

Sounds like you have a kitchen incompatiblity issue. Try building with the default selections, verify that works, add your carrier, verify that works, then slowly add your other stuff in. If you haven't added any OEMs (other than PPCGeeks_OEM), attach your selections.txt file ("apache_helmi_wm6 selections.txt", unless you've made a new file) to a post and I'll try to replicate your issue.

Yep - that's the way it works after doing the 2.05->2.02 bootloader downgrade. You have to just keep using the NoID RUU. At least that's what I was told.

I just got an unhandled exception from BuildOS. Very reproducible.

Start the app and rightclicked on the BlueFrog BigButton dialer and asked to visit the homepage. That resulted in the popup. The exception text is attached...

Nice find! That one's actually my fault I think... I inadvertently put a space in the URL field right before the http: and BuildOS didn't like it.

Maybe gguru will decide to account for that case in BuildOS, but fact is that space had no business in a URL field!

In the meantime if you get that exception you can click Continue and proceed just fine. And if you want to read about BlueFrog here's the link:

http://pdaphonehome.com/forums/ppc-6...heme-here.html

FYI I will be moving all kitchen-related bug posts to the appropriate thread (stickied at the top of this forum).

This thread is for problems with BuildOS only (i.e. the application you use to make the kitchen), not problems with the kitchen itself.

BuildOS problems are generally these: Kitchen Installation fails, kitchen shortcuts don't work, application fails to start, Application exits with error msg XXX, unexplainable errors during build or startup, added OEMs don't show in BuildOS, visual display problems in BuildOS, Boot issues (white screen on PPC), and corrupt boot splash.

All other problems, particularly problems incurred on PPC, are kitchen issues.

Please do not post in both bug threads.

i am getting an

out of memory
Failed:ffffffffffff

error, am i selecting too many options?

Yes, try removing office and see if that works, office is big so you free up loads of space, them work on your chioce of oems if you want office

Ack!
 

Geez I feel stupit tonight! BuildOS will not run

"The applicaiton failed to initialize properly (0xc0000135). Click on OK to terminate the application.

Will someone kindly slap me upside the head?

Please?

You probably need to install the .net framework.

Also noticed that o2 option.xml lists itself as an excluded item

<Guid type="p">43fef5a4-b736-11db-8314-0800200c9a66</Guid>
<OEMVersion>1.0</OEMVersion>
<OEMDate>10/25/2007</OEMDate>
<OEMAuthor>colonel</OEMAuthor>
<AppVersion>1.0</AppVersion>
<AppAuthorURL>http://www.seeo2.com/product/XdaIIi/template/O2Plus.vm</AppAuthorURL>
<ButtonType>Check</ButtonType>
<Exclude>43fef5a4-b736-11db-8314-0800200c9a66</Exclude> <<<<<<<<<<<<here
<Exclude>6cfca20e-12f0-11dc-8314-0800200c9a66</Exclude>
<Exclude>4cbe6fc6-12ee-11dc-8314-0800200c9a66</Exclude>
<Exclude>57bee5da-12ef-11dc-8314-0800200c9a66</Exclude>
<Exclude>021c9ba4-12ef-11dc-8314-0800200c9a66</Exclude>
<Exclude>42ac0a82-12f0-11dc-8314-0800200c9a66</Exclude>
</Item>
</Items>

Thanks, PaulFix

Clicking on Tools/Set PagePool Size causes a DirectoryNotFound exception to be thrown.

Important part of the text of the exception appears to be:
"Could not find a part of the path 'C:\BuildOS\ROM\nk.fat'"

That file appears to be in the Apache_Helmi_WM6.rar.

Thanks. If you've never run the app before, it will work once. You'll get this error every time thereafter. Updated BuildOS available from first post.

This worked for me as well! Thanks!