[8-3-09] eRice New Style TP Kitchen [Build 23016.5.3.0] - Page 41

l33tlinuxh4x0r · #**401** (**permalink**) 01-11-2009, 09:25 PM

Quote:

Originally Posted by electronicrice

already fixed these and am uploading the new kitchen tonight

Sounds good. If I decide to make any changes to the new kitchen I will upload the changed oems with instructions to use them.

l33tlinuxh4x0r · #**402** (**permalink**) 01-11-2009, 09:38 PM

If you didn't already do it... Here are the the images for the Touch PRO RRU. I see that in your last kitchen you used the GSM version. The images that I uploaded are for the cdma version.

Also could you please add CusTSK to your kitchen so that we can set up custom themes?

anotherv8blazer · #**403** (**permalink**) 01-11-2009, 11:58 PM

edit... was about changing the pp but i figured out how to do it

**electronicrice** · #**404** (**permalink**) 01-12-2009, 01:06 AM

having some trouble connecting to the FTP to upload. gimme a lil bit more

**electronicrice** · #**405** (**permalink**) 01-12-2009, 03:35 AM

it's up now. had to megaupload it

shad0w77 · #**406** (**permalink**) 01-12-2009, 09:15 AM

Cant wait to try the new kitchen! Any chance we will see the multiselect in messaging and elsewhere fixed in this release or a near future one?

Also, have you noticed that the X button/task manager program list is empty eventhough there are programs in the background running? I have to click on the setting or memory buttons on the dropdown, then close that window. When I click the X button/task manager again, the programs all show. I made sure the apps I was running were not in the exception list as well.

captblaze · #**407** (**permalink**) 01-12-2009, 03:42 PM

eRice

the new kitchen rocks.. i just have one issue. whenever i try to add new oems, BuildOS breaks. as a temporary work around i have added the .cab files in the appropriate OEM carrier folder and edited the config_operator file to allow installation during the customization phase after flashing.

am i missing something when it comes to making the oems? i am using the cab2 OEM app included in the tools folder and seems to be sucessful in creating the OEM files for each .cab, but when i start BuildOS i get an error and have to restart the app. removing the new OEMs fixes the issue and BuildOS works again.

any help would be greatly appreciated

creedin · #**408** (**permalink**) 01-12-2009, 05:00 PM

Quote:

Originally Posted by captblaze

eRice

the new kitchen rocks.. i just have one issue. whenever i try to add new oems, BuildOS breaks. as a temporary work around i have added the .cab files in the appropriate OEM carrier folder and edited the config_operator file to allow installation during the customization phase after flashing.

am i missing something when it comes to making the oems? i am using the cab2 OEM app included in the tools folder and seems to be sucessful in creating the OEM files for each .cab, but when i start BuildOS i get an error and have to restart the app. removing the new OEMs fixes the issue and BuildOS works again.

any help would be greatly appreciated

make sure there are proper dsm files...

**electronicrice** · #**409** (**permalink**) 01-12-2009, 05:48 PM

Quote:

Originally Posted by l33tlinuxh4x0r

If you didn't already do it... Here are the the images for the Touch PRO RRU. I see that in your last kitchen you used the GSM version. The images that I uploaded are for the cdma version.

Also could you please add CusTSK to your kitchen so that we can set up custom themes?

I was going to include the new RUU image as I downloaded it and everything and then I had a brain fart.. so they're not included. but I'll keep them for future versions

**electronicrice** · #**410** (**permalink**) 01-12-2009, 05:52 PM

Quote:

Originally Posted by captblaze

eRice

the new kitchen rocks.. i just have one issue. whenever i try to add new oems, BuildOS breaks. as a temporary work around i have added the .cab files in the appropriate OEM carrier folder and edited the config_operator file to allow installation during the customization phase after flashing.

am i missing something when it comes to making the oems? i am using the cab2 OEM app included in the tools folder and seems to be sucessful in creating the OEM files for each .cab, but when i start BuildOS i get an error and have to restart the app. removing the new OEMs fixes the issue and BuildOS works again.

any help would be greatly appreciated

as creedin said, make sure you have correct *.dsm files in each OEM. I've added numerous OEMs as part of my own build and they worked fine