Titan 20270 GPS kitchen

[djfujiyama]

Ok this is frustrating...i've been screwing with this for like 7 hours now.

I keep getting the dreaded "ERROR building default.hv and user.hv" message when trying to cook with this kitchen.

I'm not using any custom OEMs. Just the ones that came with the kitchen.

I've googled it for hours and have eliminated all of the usual suspects...touchpal, custom keypads, vogue dialers, etc.

Can't figure out what's causing this thing to bomb. I've even re-zero'ed the DSMs which someone recommended. Can't figure out what the damn problem is. I don't want to have to go through EACH OEM and toggle them to figure out what's causing the problem.

When I tried to build with zero OEMs checked, it built fine, so i'm guessing it's a bad OEM.

Any advice?

[gof]

I'm running into the "ERROR building default.hv and user.hv" problem as well. I even completely uninstalled and erased the kitchen and reloaded. Same problem.

On another note, I think it would be a GREAT idea for all of us to rewrite the info blurbs for the modules available. Since there have been more and more contributions, understanding which is which would be quite helpful. Many have a short blurb, and come are clickable to the supplier page, but not all. Heck, even a link back here to PPC Geeks or xda would be perfect if it was about the module being discussed (and better yet, perhaps pics for the skins). It would sure cut down on the trial and error.

[gguruusa]

that error is a .rgu problem usually, and very rarely a .dsm problem. Find the last oem processed (identified by the last guid in the log). Error will be at top of .rgu if nothing specific was given as to line number. Occasionally, the error will be at the top of the very next .rgu to be processed.

Uninstalling and reinstalling the kitchen is a completely pointless exercise.

[gguruusa]

Originally Posted by gof

On another note, I think it would be a GREAT idea for all of us to rewrite the info blurbs for the modules available. Since there have been more and more contributions, understanding which is which would be quite helpful. Many have a short blurb, and come are clickable to the supplier page, but not all. Heck, even a link back here to PPC Geeks or xda would be perfect if it was about the module being discussed (and better yet, perhaps pics for the skins). It would sure cut down on the trial and error.

That would be very helpful. A post with the required info is sufficient.

[gof]

Well, looking at the log, the last reference is the following.

package "Phone_DPI_96" does not contain .rgu file "b6d39515-64f2-451c-b50f-f5bd700d3b2b.rgu"
package "PhoneRedist_DPI_96" does not contain .rgu file "82ccf63c-1f61-4ccd-ab38-c178277fa43f.rgu"
package "Phone_dpi_96_resh_240_resv_320" does not contain .rgu file "68efe065-332b-4b55-8a00-05dce036176e.rgu"
importing registry file ".\Registry\12e09329-dd44-4d62-a5b7-25124bb2ef88.rgu"...
importing registry file ".\Registry\15947029-6127-4062-bb7f-b3c8bed871ac.rgu"...
..... lots of imports ......
 
importing registry file ".\Registry\0f5c182e-9447-45b6-bad0-713566ed5fcc.rgu"...
wmain: (RGUComp) !ERROR failed building DEFAULT hives

[djfujiyama]

$(^T@!)#)@&#%

It was the Samsng Omnia D3D Driver that was screwing up. I spent 2 hours doing build after build and slowly narrowing down what OEM was causing the problem by process of elimination.

[gof]

Originally Posted by djfujiyama

$(^T@!)#)@&#%

It was the Samsng Omnia D3D Driver that was screwing up. I spent 2 hours doing build after build and slowly narrowing down what OEM was causing the problem by process of elimination.

That was it. While I haven't loaded the ROM yet, removing The Samsung D3D selection allowed for the compilation to complete. =D>

[djfujiyama]

Ok another weird thing. When I try to compile/cook and flash, it gets all the way through and then the ROM Update Util bombs. it gives me an error message saying:

"C:\Users\djfadmin\documents\buildOS RUU\RUU_signed.nbh"

When I hit ok, it gives me:

ERROR [238]: FILE READ
The Update Utility can not open the requested file. Please check your Update Utility.

I looked in the path mentioned and i see a 95 meg RUU_signed.nbh file that i'm assuming is the cooked ROM. Is it corrupt or something? Why is this thing failing?

This is the most finicky and troublesome ROM i've ever cooked.

Any ideas?

[sc00b4s7eve]

Gonna have to agree with the follks that said "It was the Samsung Omnia D3D Driver," causing the building error for .hv files.
I actually had to unistall the kitchen and manually delete the folders in Program Files\ppckitchen AND the build files in \Documents and Settings\application files\etc... you find it (haha, I forget and I'm writting it on my titan). And then Re-downloading buildos.msi and the files.
The transition to the new buildOS file structure was not smooth for me.
In conclusion:
Back up your user OEM's and Projects folder w/ selections.txt in them
Uninstall buildOS
Delete BOTH app folders
and reinstall+redownload.

It was my last resort and it works now.

[bradleyem]

Originally Posted by djfujiyama

Ok another weird thing. When I try to compile/cook and flash, it gets all the way through and then the ROM Update Util bombs. it gives me an error message saying:

"C:\Users\djfadmin\documents\buildOS RUU\RUU_signed.nbh"

When I hit ok, it gives me:

ERROR [238]: FILE READ
The Update Utility can not open the requested file. Please check your Update Utility.

I looked in the path mentioned and i see a 95 meg RUU_signed.nbh file that i'm assuming is the cooked ROM. Is it corrupt or something? Why is this thing failing?



This is the most finicky and troublesome ROM i've ever cooked.

Any ideas?

Are you on a domain where you're profile is stored on a server, or is your "My Documents" folder redirected to a network folder or share?

I had the same problem, and I have a file server that I use for central storage, and my "My Documents" folder is redirected. Apparently buildOS doesn't like the fact that its on a network share.

What I did, is just copy the entire BuildOS RUU directory to a local drive (like your C Drive), and run the ROMUpdateUtility from there.