Re: dcd_titan_3.2.5
 

i downloaded an oemizer. how do you add programs to it. sorry for all the questions

Re: dcd_titan_3.2.5
 

open the program on the left is your list of items...start with oem info...name the folder arcsoft_oem then name the app arcsoft mms delete the text thats in the tip box...from there click on files and shortcuts make sure that box is checked then click it again to open a new window within oemizer...from there you will import the arcsoft cab by clicking import cab....once thats done go back to oem info then click on new guid...must be new cant match any other that is in the oem folder...once that is done click on create oem...will take a few seconds to complete...from there it will be in a folder called oem...where ever the app is stored. open that oem folder and copy the arcsoft_oem folder into the dcd oem folder and presto chango...and bobs yer uncle

Re: dcd_titan_3.2.5
 

ok, will try that.. can't get the pic msg working. but txt do...

Re: dcd_titan_3.2.5
 

ok, i am only tried to add or cook 4 other programs into my rom now. they are Verizon Carrier July 19 2008, GC Arcsoft MMS 5.0.31.25, QuickMenu 2.7 and SPB Mobile Shell. when i do this i am getting and error saying default .hv and user .hv error. could you give me a hand on fixing this please?

thanks

Re: dcd_titan_3.2.5
 

that typically means bad oem file...you cant cook the carrier cab into the rom nor can you make an oem out of it... it just doesnt pack it correctly...take it out then rebuild

Re: dcd_titan_3.2.5
 

thanks will try

Re: dcd_titan_3.2.5
 

Doesn't pack it correctly? Please elaborate.

Re: dcd_titan_3.2.5
 

for some reason oemizer doesnt create the oem properly for the carrier cab...i have tried several times...and everytime i do...it doesnt work so when i remove it from the kitchen...it works fine

Re: dcd_titan_3.2.5
 

In what manner does it "not work"? error during OEM create, error during build, error during rom packaging, error during flash, won't boot, or doesn't appear to have taken once booted?

Re: dcd_titan_3.2.5
 

i've not used OEMizer, but surely its missing the xml provisioning, as most people do when they try to extract the carrier cabs by hand.
most of my carrier cabs only configure the #777 connection via provisioning xml. some old ones probably set the areacode to state mapping too.