Related
XIP 20748 for Polaris
In "os.nb.payload" and in packeges.
"os.nb.payload":
http://rapidshare.com/files/143695076/payload.zip.html
Thank you, these rom's seem more speedy and less bugs.
721 is from the same serie I think, very stable.
Leo
make sys plz.
You are the hero....Thanks a lot bro!
...regards
....c_shekhar
I build with this XIP.My device freez on boot screen.
niars said:
I build with this XIP.My device freez on boot screen.
Click to expand...
Click to collapse
How you built? Use "os.nb.payload".
SHAYDER said:
How you built? Use "os.nb.payload".
Click to expand...
Click to collapse
Yes,but with RK19965 from PDAMOBIZ.com.
Thank you for SYS as well, let the cooking begin.
niars said:
I build with this XIP.My device freez on boot screen.
Click to expand...
Click to collapse
Location of XIP as well as the imgfs are changed in this payload as follows:--
1 XIP 0x20000 (Earlier) to 0x1000 (in this payload)2. imgfs 0x320000 to 0x7a0000
c_shekhar said:
Location of XIP as well as the imgfs are changed in this payload as follows:--
1 XIP 0x20000 (Earlier) to 0x1000 (in this payload)2. imgfs 0x320000 to 0x7a0000
Click to expand...
Click to collapse
Does this mean if I would rebuild my own german ROM based on the dump of
RUU_Polaris_O2_DE_3.13.207.0_radio_sign_25.85.30.0 7_1.59.42.15_Ship
with the "os.nb.payload" XIP version from the 1st post with Polaris Kitchen
V1.3 would also result in white screen because of wrong locations in the
build?
My goal is to rebuild the O2 rom with reduction of some unneeded files and apps,
cook in NetCF 3.5 and use XIP 20743 from this thread instead of the original.
However, could someone please clarify if my build could work? I used my
modified SYS/OEM from O2 german base rom above and the os.nb.payload
from the 1st post in ROM folder to build with Kitchen 1.3.
I already cooked my build and it did not give any errors in the kitchen
but now I do not dare to flash it because of the maybe
wrong location of the XIP...
Olioaglio
Use my "os.nb.payload" (in 1st post)
Probably error in nls.
Shayder,
I've been facing an issue when cooking using your 748 payload file and 753 one. Problem happens in the same way either using one or another.
I can't match xip with sys part. It means that build version is fine but xip does not. If I change payload file for one like 721 I'm using now, rom boots ok but with CE OS 19965.
I can successfully get 748 and 753 Build version but all with CE OS 19965. I'm using your XIP released in first post.
Any idea what can be causing this behaviour?
Thanks my friend.
SHAYDER said:
Use my "os.nb.payload" (in 1st post)
Probably error in nls.
Click to expand...
Click to collapse
SHAYDER said:
XIP 20748 for Polaris
In "os.nb.payload" and in packeges.
"os.nb.payload":
http://rapidshare.com/files/143695076/payload.zip.html
Click to expand...
Click to collapse
thankS！thankS！thankS！thankS！
XIP 20931 for Polaris.
http://www.megaupload.com/?d=C775IR0I
OS.nb.payload
http://www.megaupload.com/?d=FC5KB4ST
already done , but thanks you very much..........
You help lots of people cooking easily...
Shayder,
do we need your 7MB os.nb.payload again as it was
in 20753 XIP? If yes, is it possible to use the same one,
or do we need another one?
Olioaglio
You actually can keep the current one. Payload file act more as a template. It's valuable to move to a new or different one unless you made changes in partition for instance. Otherwise, keep the actual you have.
Olioaglio said:
Shayder,
do we need your 7MB os.nb.payload again as it was
in 20753 XIP? If yes, is it possible to use the same one,
or do we need another one?
Olioaglio
Click to expand...
Click to collapse
Olioaglio said:
Shayder,
do we need your 7MB os.nb.payload again as it was
in 20753 XIP? If yes, is it possible to use the same one,
or do we need another one?
Olioaglio
Click to expand...
Click to collapse
OS.nb.payload
http://rapidshare.com/files/167149915/payload.zip.html
SHAYDER said:
XIP 20931 for Polaris.
http://rapidshare.com/files/166956197/MSXIPKernel.zip.html
Click to expand...
Click to collapse
Link not working.
It can therefore only be downloaded 10 times.
This limit is reached.
can you re-up on Megaupload?
epimazzo said:
You actually can keep the current one. Payload file act more as a template. It's valuable to move to a new or different one unless you made changes in partition for instance. Otherwise, keep the actual you have.
Click to expand...
Click to collapse
Thanks for clarification, m8
Olioaglio
bigix1 said:
Link not working.
It can therefore only be downloaded 10 times.
This limit is reached.
can you re-up on Megaupload?
Click to expand...
Click to collapse
Same here...
Look 1-st post.
Thanks man.
A question: this xip upgrade only number of CE, or it's a complete port of xip?
Cause i've inserted and cooked in my rom, but build version is still old version. May it depend cause my rom it's Ita version?
You are a bit confused about, the XIP it's only the core, not the SYS.
Thank's very much for your reply Udk, your kitchen it's greatest and easy to use!
So I must import SYS folder, thanks!
Anyway, a question that nails my brain since times is:
Does it generally make sense to mix e.g. a 19965 SYS with 20931 XIP
to maybe benefit from speed gain or better stability?
I am currently using my self cooked german ROM ATM with german
SYS 19965 from O2 official WM6.1 mixed up with Shayders posted
XIP 20753 since some time and it runs REALLY rockstable and fast. But I am a
also a "latest version junkie" and ask myself, if I should cook and
reflash with this new XIP 20931. It's a pity, that newer SYS always
is just available in WWE, never in other languages. Is there a bearable
way to convert a WWE sys to german? I think it's not just copying
the 0407 files over the 0409s, is it?
Olioaglio
I am using ervius to build a rom, Everything works according to the kitchen except that it could not find the ppchanger. But that shouldn't be an issue. However, whenever I load it to the phone. It becomes stuck at boot. What am I doing wrong? Here's the build log.
Update: I moved the wincenls_wwe to my oem to no avail. still stuck at touch pro screen. Here's the latest build log after recmodding some files:
Everything seems to be ok and if it stucks in the first splash screen is issues related to XIP check your OEMxipkernel all the modules.... same format! check the MSXIPkernel all the modules same format!
i see you are addin manila but i couldn saw any manila pkg in OEM or EXT cause you dont have nothing in EXT and you just have OEM and SYS.. where did you get all of this OEm SYS and addons?
Thanks for your reply. All I did was dump a shipped rom. Then I tried to add a 6.5 build. The shipped rom had manila within the oem.
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
and yes dont forget to check the thread of how to make rom bootable..
+ Que PPC said:
ok... first of all... wich device is it? wich rom was the original rom? 6.1 or 6.5? did you checked 6.5 real aku on the kitchen?
Click to expand...
Click to collapse
Well I tried the Verizon XV6850_MR1_Upgrade_v2.0 for the Touch Pro. I am trying to create the rom for CDMA device (herman correct?) The original rom is 6.1 and I am trying to put the 21903 build. Yes I checked the aku 6.5. I've read the threads from others with the similiar issues. I've tried the recmod.exe in the Ervius tools folder, and I've also tried the recmod auto zip. I've downloaded and went through the list of sys files that can be recmodded with no luck. What steps exactly do I take to make sure that the oemxipkernel and msxipkernel are the same format?
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
+ Que PPC said:
Hi well it seems that you need to know this, if your dumped rom was 6.1 your kernel is not real aku 6.5 so you dont check that box in the kitchen
Click to expand...
Click to collapse
oh... so even if I am using 6.5 sys & xip.bin if I am bringing over the oem kernel from the base rom then I should NOT check it... Is that what you are saying?
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
+ Que PPC said:
send to the hell the 6.1 version
Click to expand...
Click to collapse
+1...man its been probably about 2 yrs since I used a 6.1 ROM! lol
+ Que PPC said:
Exactly!
If you dump the 6.1 STOCK ROM you will have xip.bin payload rromhdr.bin and OEMXIPKERNEL V6.1 and you will not check the the real aku6.5 on the kitchen
If you dump a 6.5 STOCK rom you will have everything in 6.5Version so you can check that checkbox... Why you dont take a look into the main stickie in repositories maybe you can find your Native 6.5 OEMXIPKERNEL and send to the hell the 6.1 version
Click to expand...
Click to collapse
So it doesn't matter if the 6.5 stock rom is not for cdma touch pros? As long as I choose the right dpi and of course remove gsm stufff then I can create a build for it? Am I right in my thinking?
yes the thing that makes the GSM or CDMA rom is in your OEMXIPKERNEL things and in your OEM folders
Wow!! This is some amazing stuff. Ok one more question, of late most builds do not include the oemxipkernels, and I've learned that you can generate this with xipport button in ervius. If i was to use this, and i port the os.payload & the build's xip.bin, should I check the box that this is a native 6.5 kernel?
Touch pro is the FUZE isnt it?
Why you dont ask in Da_G thread for the Native 6.5 TOUCH P kernel
i cant remember well but i guess i saw it
you dont need to do that the kitchen ports the xip.bin payload bal bla bla autopmatically for you
Just want to say thanks for your help. I find your insight very helpful. I will start from scratch and see what happens. Thanks again.
I have tried several 21905 builds but with all of them I Get on the About window CE OS 5.2.21901 (Build 21905.5.0.93)
Did MS forgot to update the OS version?
I did try to search for the string and 558D word, but nothing found...
Can anyone hint me to a solution? or a good 21905 SYS.
Sounds like you updated your sys, but not xip.
Hmm, I did rebuild my xip. But only once.
I will check again.
tnx!
Its probably just that way...i know lot of builds these days have a different sys and xip numbers. But I dont use COM2, so i really cant tell.
Use Dsm Editor to change the build number in oemxipkernel rgu...it Will be fine
shafizal said:
Use Dsm Editor to change the build number in oemxipkernel rgu...it Will be fine
Click to expand...
Click to collapse
Sorry I think it's at MSXipKernel rgu file
To correct myself, should be MsXipKernel DSM file, open with DSM EDITOR and change the number if necessary and save
Pisca said:
Sorry I think it's at MSXipKernel rgu file
Click to expand...
Click to collapse
Thanks for thé correction
The rgu only has an entry for encfilt, but I presume you mean the dsm file.
It already had 21905 as the QFE level. (5.2.5093.21905)
I have rebuild xip from 3 different sources but I keep getting
CE OS 5.2.21901 (Build 21905.5.0.93)
on the About screen.
So either all sources for 21905 are wrong or I am missing something.
I tried to find where it is but no unicode string or binary value for 21901 (558d) I can find 21905 (5591) in the shell part.
...
Oooo, I feel stupid...
There was a MSXIPKernel folder in my OEM folder with a 21901 dsm...
I tried a 21898 xip and sys and still had 21901 in the about screen.
So I wass puzzled until I found it... No idea how it got there!
sony66 said:
Oooo, I feel stupid...
There was a MSXIPKernel folder in my OEM folder with a 21901 dsm...
I tried a 21898 xip and sys and still had 21901 in the about screen.
So I wass puzzled until I found it... No idea how it got there!
Click to expand...
Click to collapse
Microsoft are trying to sabotage us
Badwolve1 said:
Microsoft are trying to sabotage us
Click to expand...
Click to collapse
LOL...thats funny...
Hi, Greetings
Im cookin my own rom, sys 23536 i installed the lang 0c0a and everything works great but im trying to put manila 2.5 and when the phone boot the menu setting from start menu dissappears, only show home tab.
In home tab only show the clock and the appointment, the h-bar with all tab dissappears. i cant change the tabs.
I dont know how to fixed, i would appreciate any helps.
Thanks and sorry for my english.
Edit:
Theres no sliding bar only the button like landscape
Info:
Phone: Htc RhodiumW Touch Pro 2 CDMA-GSM WorldPhone
Kitchen Os Builder 1.1.5
Sys 23563 MULTILANG - ROM-XIP 21887
MSXIPKernel 5.2.21887.5086
MSXIPKernelLTK 5.2.21887.5086
Manila_Sense_2_5_20173921_0
Originaly this kitchen was an 0409 kitchen from indagroove and i inserted the new sys 23563
EDMYJOSE said:
Hi, Greetings
Im cookin my own rom, sys 23536 i installed the lang 0c0a and everything works great but im trying to put manila 2.5 and when the phone boot the menu setting from start menu dissappears, only show home tab.
In home tab only show the clock and the appointment, the h-bar with all tab dissappears. i cant change the tabs.
I dont know how to fixed, i would appreciate any helps.
Thanks and sorry for my english.
Click to expand...
Click to collapse
S i had this problem when i start cooking for a first Time it show only today in start menu... I think thé problem is from Start_Menu_Grid.CPR ...but I did not sure...
This is the reg key for having back WM Settings in Start Menu:
Code:
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo]
"HideSettings"=dword:00000000
Be sure to cook it at least after Manila in your Kitchen.
af974 said:
This is the reg key for having back WM Settings in Start Menu:
Code:
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo]
"HideSettings"=dword:00000000
Be sure to cook it at least after Manila in your Kitchen.
Click to expand...
Click to collapse
Thanks af974
Well, the reg key, works fine, i cooked again the rom but now manila not boot i have to activate from today and stay in tab in screen to boot manila and doesnt matter how much i tap, he never boot, i check the initflashes.dat and everythink is fine
I dont think that this reg key stop Manila booting but anyway you should try to delete it and cook again your rom to see if it boot up.
Did you touch something other apart the reg key?
EDMYJOSE said:
Well, the reg key, works fine, i cooked again the rom but now manila not boot i have to activate from today and stay in tab in screen to boot manila and doesnt matter how much i tap, he never boot, i check the initflashes.dat and everythink is fine
Click to expand...
Click to collapse
af974 said:
I dont think that this reg key stop Manila booting but anyway you should try to delete it and cook again your rom to see if it boot up.
Did you touch something other apart the reg key?
Click to expand...
Click to collapse
Hi.
I only apply the reg key to make appear the setting icon in start menu, my manila just finally booted with the same issues here is an screenshot
I booted from today. well i just add some prgram to oem and add more line to initflashes.dat about to manila and other programs. but i dont know how to fixed.
Thanks for all buddy.
The problem in the attached pics its a missing language file.
Are you cooking for an English rom?
It should be usefull if you post here much more informations and your build log so we can check it.
EDMYJOSE said:
Hi.
I only apply the reg key to make appear the setting icon in start menu, my manila just finally booted with the same issues here is an screenshot
I booted from today. well i just add some prgram to oem and add more line to initflashes.dat about to manila and other programs. but i dont know how to fixed.
Thanks for all buddy.
Click to expand...
Click to collapse
af974 said:
The problem in the attached pics its a missing language file.
Are you cooking for an English rom?
It should be usefull if you post here much more informations and your build log so we can check it.
Click to expand...
Click to collapse
Well my friend. y downloaded an english kitchen who has many build in 0409 for RhodiumW. i find and new sys 23563/xip.bin multilang and i added to the kitchen. and all the files 0409 i change it to 0c0a . every thing works fine. titanium works fine. but i cant make work manila.
I remember in one oportunity i cook in 0c0a and manila work fine but without the lang file, then i installed the lang pack and everything looks normally in 0c0a lang.
I think im missing to do something to make manila work fine.
Thanks for your help
There are 2 folders that contains insided the language folders:
Manila Core and Manila Home.
Now, i bet that you are cooking for 2018 sense?
My suggestion is to import an Original rom with your language and use that Manila for training.
Look here for some original roms http://shipped-roms.com/shipped/ im sure that you will find a 0c0a sense rom here.
Otherwise if you will find 0c0a Sense language for your current rom you will be good.
As a said you before , we need your log build for a better check.
EDMYJOSE said:
Well my friend. y downloaded an english kitchen who has many build in 0409 for RhodiumW. i find and new sys 23563/xip.bin multilang and i added to the kitchen. and all the files 0409 i change it to 0c0a . every thing works fine. titanium works fine. but i cant make work manila.
I remember in one oportunity i cook in 0c0a and manila work fine but without the lang file, then i installed the lang pack and everything looks normally in 0c0a lang.
I think im missing to do something to make manila work fine.
Thanks for your help
Click to expand...
Click to collapse
af974 said:
There are 2 folders that contains insided the language folders:
Manila Core and Manila Home.
Now, i bet that you are cooking for 2018 sense?
My suggestion is to import an Original rom with your language and use that Manila for training.
Look here for some original roms http://shipped-roms.com/shipped/ im sure that you will find a 0c0a sense rom here.
Otherwise if you will find 0c0a Sense language for your current rom you will be good.
As a said you before , we need your log build for a better check.
Click to expand...
Click to collapse
Ready i uploaded the buildlog.txt 2 image 1 with the lang pack installed and 2 without lang pack all is in the post #1, you was close im using Manila_sense_2_5_20173921_0
All the original rom i have to downloaded for my rhodiumW cdma-gsm is in 0409, no exist in 0c0a, but for rhodium gsm 1 or 2 is in 0c0a but have manila 2.1. i look in saint google fo an manila 2.5 0c0a and only fina the cab lang pack but not the manila oem.
I will look for other device to see if i can have the complete manila 0c0a.
You can use Rhodium GSM packages as well the most important thing is that you want never use the OEM Drivers or you will brick your phone, EXT packages are pretty the same.
If you did find the cab for language ,oh well, this is not a big problem, i attached a program that converts cab to oem/EXT ..install it in C:\ otherwise it will not works.
Its not easy find your language packages( Spanish?) for sense up to 1922 because for us European this is the only version made from HTC , the others(2012/2014/2016/2018) are from TMOUS and OBOE phones ,so only WWE or Chinese.
I have the same problem as you since im Italian infact my phone is still in English now.
EDMYJOSE said:
Ready i uploaded the buildlog.txt 2 image 1 with the lang pack installed and 2 without lang pack all is in the post #1, you was close im using Manila_sense_2_5_20173921_0
All the original rom i have to downloaded for my rhodiumW cdma-gsm is in 0409, no exist in 0c0a, but for rhodium gsm 1 or 2 is in 0c0a but have manila 2.1. i look in saint google fo an manila 2.5 0c0a and only fina the cab lang pack but not the manila oem.
I will look for other device to see if i can have the complete manila 0c0a.
Click to expand...
Click to collapse
Ready i uploaded the files and add new information in the post #1
I do not understand this
"..install it in C:\ otherwise it will not works."
You mean all the converted files i have to put it in root of the phone or use this program in drive c:\ of my pc. for the converter no problem because i have it with all the kitchen i have donwloaded, and i have converted all the prgrams i usually use, but im waiting to cook my rom good to after add my programs oems
Besides the Manila problem i would change your MXIPKernel with the original 23563 ,mixing SYS and XIP from 2 different builds should cause problems in your rom.
af974 said:
Besides the Manila problem i would change your MXIPKernel with the original 23563 ,mixing SYS and XIP from 2 different builds should cause problems in your rom.
Click to expand...
Click to collapse
Ok, i will change MXIPKernel with 23563 and only left OEMXIPKernel 21887 to see if works
af974 said:
Besides the Manila problem i would change your MXIPKernel with the original 23563 ,mixing SYS and XIP from 2 different builds should cause problems in your rom.
Click to expand...
Click to collapse
i figure out something. in my kitchen exist this folder, donors, ext, oem, rom, sys
in donors i put the MSXIPKernel or xip.bin 23563
ext i put all the oem programs
oem i put oemdriver, OEM_Lang_0C0A and other folders
rom i put xip.bin and MSXIPKernel, MSXIPKerneltk, OEMXIPKernel 21887
sys i put sys 23563
when i click go he automaticaly change MSXIPKernel 21887 for MSXIPKernel 23563.
so everythink works fine but im stuck with manila.
af974 said:
You can use Rhodium GSM packages as well the most important thing is that you want never use the OEM Drivers or you will brick your phone, EXT packages are pretty the same.
If you did find the cab for language ,oh well, this is not a big problem, i attached a program that converts cab to oem/EXT ..install it in C:\ otherwise it will not works.
Its not easy find your language packages( Spanish?) for sense up to 1922 because for us European this is the only version made from HTC , the others(2012/2014/2016/2018) are from TMOUS and OBOE phones ,so only WWE or Chinese.
I have the same problem as you since im Italian infact my phone is still in English now.
Click to expand...
Click to collapse
Well if u want i can give you sys 23563 multilang but in manila dont have
I trying to put an tier autoinstaller for when my phone is hard reset install other cabs automaticaly but when i put it he always ask me to select the cabs i want to install. i want after make the first boot he start the customization alone like this, "after booting he said 3,2,1 starting customization", i ben use xda_uc i don like. easy installer cant make work and runcc cant make work, never install the cabs.
Since you said that this is from my kitchen, why not post in my kitchen thread? You will likely get answers from the person who is most familiar with the kitchen you are using (Me) quickest that way.
Anyway, by looking at your build log, I see a few issues right off the bat. First of all, you need to take a look at the packages.sof file that you imported into the kitchen with the new sys. OSBuilder builds first based on packages.sof order, and then .dsm order if packages are not found in packages.sof. You are building packages all out of preferred order, which will not achieve desired results. Take a look at the packages.sof from my preconfigured kitchen, or better yet, download my most recent kitchen and just use that.
Also, I see that you are building in both phonecanvas versions. One version is for com2 and com 5 builds, and the other is for com 3 builds, so that will cause you some issues.
In regards to your manila issue, I believe that the kitchen you are working with likely only contains 0409 manila files, because I think that is the one and only build that I used the manila lang sorter on, and stripped all non wwe manila files from the kitchen. I'm talking about lang files in the manila common folders (which contain over 10 different languages by default -- even though these are supposed to be "common" files. The recent version of the kitchen does contain all lang manila files in common, you just need to add your lang pack.
indagroove said:
Since you said that this is from my kitchen, why not post in my kitchen thread? You will likely get answers from the person who is most familiar with the kitchen you are using (Me) quickest that way.
Anyway, by looking at your build log, I see a few issues right off the bat. First of all, you need to take a look at the packages.sof file that you imported into the kitchen with the new sys. OSBuilder builds first based on packages.sof order, and then .dsm order if packages are not found in packages.sof. You are building packages all out of preferred order, which will not achieve desired results. Take a look at the packages.sof from my preconfigured kitchen, or better yet, download my most recent kitchen and just use that.
Also, I see that you are building in both phonecanvas versions. One version is for com2 and com 5 builds, and the other is for com 3 builds, so that will cause you some issues.
In regards to your manila issue, I believe that the kitchen you are working with likely only contains 0409 manila files, because I think that is the one and only build that I used the manila lang sorter on, and stripped all non wwe manila files from the kitchen. I'm talking about lang files in the manila common folders (which contain over 10 different languages by default -- even though these are supposed to be "common" files. The recent version of the kitchen does contain all lang manila files in common, you just need to add your lang pack.
Click to expand...
Click to collapse
Hello sorry that I have not asked directly to you, do not save the post from which to download the kitchen and honestly I downloaded many kitchen for testing. and good that yours was the most use and I started changing from a few things until the end wanted to put it in my native language is Spanish, q is both the modification that the only thing I did was left of your original rom was the xip of 21 887 rom yet and would change the 21 889 that I previously had the stock rom dump.
Ok and will review these issues you mention about the canvas was originally com2 off but I had to activate q 3 for the full-dialer will see that when I was the only COM5 dialer being cut came out but not approach it because I wanted to do first operational as of manila to accommodate those details later.
I would love to hear a lot that kitchen, cooperation could give me the link to download if not much problem.
Thanks for everything.
EDMYJOSE said:
Hello sorry that I have not asked directly to you, do not save the post from which to download the kitchen and honestly I downloaded many kitchen for testing. and good that yours was the most use and I started changing from a few things until the end wanted to put it in my native language is Spanish, q is both the modification that the only thing I did was left of your original rom was the xip of 21 887 rom yet and would change the 21 889 that I previously had the stock rom dump.
Ok and will review these issues you mention about the canvas was originally com2 off but I had to activate q 3 for the full-dialer will see that when I was the only COM5 dialer being cut came out but not approach it because I wanted to do first operational as of manila to accommodate those details later.
I would love to hear a lot that kitchen, cooperation could give me the link to download if not much problem.
Thanks for everything.
Click to expand...
Click to collapse
http://www.mobileunderground.info/showthread.php?t=12797