Related
XIP 20296 for Polaris.
two days two great contributions,
cheers
SHAYDER said:
XIP 20296 for Polaris.
Click to expand...
Click to collapse
?! Sorry but what is XIP 20296 for Polaris, what does it?
Yes Please Tell Us For What Need This Xip ????
I'm not entirely sure, but I think a XIP is the OS part of a ROM. This file is needed when a ROM cook creates a ROM.
JAYmasta said:
Yes Please Tell Us For What Need This Xip ????
Click to expand...
Click to collapse
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20296 is current XIP.
To build ROM with new XIP you must: put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
Is it worked for ya?
Some kitchens or even ROM packages already comes with most files found in msxipkernel...you should cut off one side or another. I generally keep bottu.rgu alone in XIP and move msxipkernel to sys folder...then cook...
still playing with 20275.
Where 20296 is from?
Thanks for sharing!
SHAYDER said:
XIP is kernel of OS.
You can see a version of XIP: Start->Settings->System->About
OS CE 5.2.20296 is current XIP.
To build ROM with new XIP you must: put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder. Then build you new ROM with new XIP.
For Example you can use Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)
http://forum.xda-developers.com/showthread.php?t=379559
for build ROM.
Click to expand...
Click to collapse
If You use "Polaris Kitchen v1.3 - WM6.1 (Build 19214.1.0.4)"
You have 3 main folders: "SYS" "OEM" "ROM"
In "ROM":
You have "XIP" folder and "os.nb.payload" (XIP in "os.nb.payload")
In "XIP" folder you have ONLY "boot.rgu" (it is not main XIP)
In "OEM" you nave drivers and applications.
In "SYS" you have OS.
1)You must put "MSPPCXIPKernel" and "MSXIPKernel" folders to "SYS" folder.
2)Replace "os.nb.payload" in "ROM" folder. (because thet "os.nb.payload" with old XIP. You must put my "os.nb.payload" without XIP. And when you cook you ROM, new XIP copy from "MSPPCXIPKernel" and "MSXIPKernel" folders)
3)Put my "imgfs.bin" to main folder.
4)Run "BuildOS.exe"
5)Run "Build ROM.bat"
There where I took this XIP, written that it is taken from Diamond.
But i am not sure. Because i cant find official Diamond ROM with this XIP.
Thanks m8 for your contribution !! Really appreciate 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.
Hi all,
I try to cook rom for my device Samsung M490. I have a Ship rom in Korean language(0412) ( i cannot find the English one).
I build with new WM6.1 SYS/XIP (lang 0409) , the device boot ok, the language changed to Eng, but the setting shortcut not work. I cannot set the rington.
I build with new WM6.5 SYS/XIP (0409) and it cannot boot, the screen turn off after the Anycall logo appear.
Now can you ask me how to make it work with W6.5 build? what thing I will do, what file/folder will be change/edit?
My ship rom here:
Code:
211.189.38.83/umsvcbin/SCH-M490/SCH-M490_CI24_pda.bin
I do follow as below:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN (23662) as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build (23662), repalce initflashfiles.dat by English one. add XIP.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Thanks very much for your help
There is too little info here to help you. Does your device have a native 6.5 kernel? You will need to have one to be able to flash a 6.5 ROM and make it work on your device.
You mean ''oemxipkerner''? .Samsung didn't release the wm6.5 rom. but i found some cooked wm6.5 rom in Korean and Chinese. can I take it from these rom?
I dont think so. You will first need to dump a stock rom provided by Samsung for your device. Then replace the oemxipkernel with a patched one, which has a 6.5NK.
I dump a ship rom already, I use XIPkithen to make a new xip.bin from a new wm6.1 release, the device boot ok , I do the same way with build wm6.5 but the device can't boot. where can i find a patched oemxipkerner?
You will have to search for it. You will need a 6.5NK for WM 6.5.X to boot on your device.
If Samsung has not released a stock 6.5 ROM for your device, chances are you wont have a native 6.5 kernel.
If you don't have a native 6.5 kernel, you need to recmod a lot of files/folders. This thread @ Mobile Underground has lots of good info.
You said you dumped a stock 6.1 ROM. In this ROM, see if you have a 6.5 Native Kernel by dumping xip.bin. Open nk.exe/s000 in a hex editor. Search for the ASCII string "platform". Near this string there should be the build number that this nk.exe was compiled against.
WM 6.5 builds began around 21100. WM 6.1 and previous builds will be <=21058.
OsKitchen can import the ROM of that phone and also seems able to rebuild it correctly (but make sure the final file is correct for your phone since there are something like ten different BIN file formats) and since it can already suggest the packages to recmod it could also help with 6.5.5 porting if you don't have a 6.5 kernel (which you probably won't find anywhere: the only modded 6.5 kernels I've seen are for htc devices).
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
theanh6 said:
thank airxtreme, i use os kitchen before. I dump a Ship rom and build it again, flash rom to phone and it not boot. I try to use new Ervius kitchen but i don't know how to make file OS.NB.PAYLOAD. Now i try a old type Ervius kitchen (5.3).
I just do:
-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs and use Xipkitchen to make a new XIP.BIN out.
-Dump Ship 6.1 rom, replace SYS by new wm6.5 SYS build, repalce initflashfiles.dat by English one. add XI.BIN out above into file OS.NB.
- Copy os.nb to \ROM, copy \SYS, \OEM, \ROM into kitchen an run.
- It is still not boot, please advice anything else to to?
Click to expand...
Click to collapse
Which EXT packages are you using?
anand12 said:
Which EXT packages are you using?
Click to expand...
Click to collapse
I don't use any EXT packages.
theanh6 said:
...-Take out the XIP.BIN form a WM6.5 Cooked by chinese guy an use it as DEVICE_BINs , use a new build XIP.BIN as DONOR_BINs....
Click to expand...
Click to collapse
First of all - don't try to dump someones roms to get xip.bin or whatever!
Many guys, including me (does not matter - Chinese or not) - are deleting reloc sections and dsm files while building custom roms to save the space. So if you use such a xip - you will get non-bootable rom.
1. Take the latest OFFICIAL rom
2. Dump it to get original XIP and original OEM
3. Download new build that you want to cook.
4. Port new xip. Use the original XIP as donor of OEMXIPKernel and new xip from downloaded build as a source of MSXIPKernel & MSXIPKernelTLK
5. Take ported xip, OEM (drivers) from official rom, SYS from downloaded new build
6. Start cooking.
Very nice step by step explanation by Andrew. It doesnt get simpler than this!
The most important part - Dump the official rom released for YOUR device NOT for any other. You risk bricking your device.
Thanks AndrewSh & anand12 for your advice, i follow step by step but it only ok for a 6.1 build, and wm 6.5 fail to boot again.
Now I sucess to build an English wm6.5, my way is:
-Dump a cooked Korean ROM build 21815, I have \ROM, \OEM, \SYS, XIP.BIN.
-Remove all file/folder in \SYS but keep .ROM, .VM , Metadata, then copy all from SYS build 21815E(English-0409).
-add XIP.BIN above into OS.NB get from official rom an copy new OS.NB to \ROM.
-Now i have \ROM; \SYS; \OEM, copy them into kitchen an run. Flash new rom to phone and it work ok.
I try to cook a new ROM with last wm6.5 build, but i feel sad because it fail again.
Now i have some quesion, please spend a litle time to help me to clarify:
1. i think my problem is at "Metadata" folder. When we cook a new build, what will we do with "Metadata" (change all folder, change some file/folder or edit some thing) ?
2. I can not set the ringtone for my cook rom, both in 6.1&6.5 build. The "Ringtone" feild is empty as the picture i attached. What thing be wrong here?
Look you must have a 6.5 NK for your device. If not, you must recmod files. Are you doing that? Please be sure and clarify.
@theanh6: Can you upload your cooked here? Thank you very much.
Thank you all, It fully working now (with some small bug but no problem)
@Mrkid: Please send an email to me at [email protected] if you want to try this rom.
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
How to cook a bootable rom using XIP from one build and SYS from another build of the same branch? All my efforts resulted in non bootable roms.
What kitchen are you using?
What kitchen are you using? I make many of such ROMs for the LG KS20. Even mixing various versions of wm. (I made 1 wm6 ROM with wm6.5.3 styled menus.) Try using xipport. It solved all my bugs.
Thanks for the reply. I use EVK for HTC Gene. I was trying to cook xip from 21899 and sys from 21916. But the rom do not go beyond the first boot screen. Can u elaborate a bit more?
Did it flashed a bit brighter for a while and then went dim again? It would mean XIP started ok, if not - then it's XIP...
Are you sure you have wince.nls SOMEWHERE? (either XIP or SYS)
And another question: are you sure you're implanting XIP into image properly? Generally, mixing SIMILAR XIP and SYS is not a problem at all... some time ago it was everyday practice, as we had more SYS releases and porting XIP was a bit harder than nowadays. Find a XIP porting tutorial here on xda.
Yes it flashed bright and then went dim. the first boot screen comes but afterwards no tapping instructions and remains still. I changed only MSXIPKERNEL. I get a bootable rom with 21899 SYS and XIP as well with 21916, in the same kitchen. Thanks for all the input.