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
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！
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Thanks hope udK will use this version in R5 release
I wonder which is the difference between this and 20931 build
Sorry to ask, How to add wince.nls manually
suaaa said:
for newest 21109 SYS , here are 21109 XIP for Polaris use.
please add wince.nls manually.
http://rapidshare.com/files/178146056/MSXIPKernel_21109.rar
Click to expand...
Click to collapse
Wow! but where is the \SYS ?
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
chavonbravo said:
SYS found on xbeta.
I believe this might be WM6.5, but haven't tried it yet.
Click to expand...
Click to collapse
Isn't real or?
The experts out there...
Does it make sense to mix most recent XIP (like this one) with older SYS
e.g. 19965.1.2.3 because of the lack of native (german) translated newer SYS?
I mean, can you have overall (speed) gain from newer XIP though you use it
with an older SYS?
I really would appreciate an experts reply on this
Olioaglio
Seems, the SYS 21109 is again chinese hex magic according to:
http://forum.xda-developers.com/showthread.php?p=3104209#post3104209
Hmn, AKU 5.0 or 5000 instead of 1.5.0 or 1500 ?!? seems a fake
WOndering, if XIP is also hex edited or real...
Olioaglio
Nice!!
so its fake or not???
where can i get sys / xip for polaris???? the lastest release
Hi!
i decide to post my question here because this thread is visited by too many "rom cookers"....
I have a Benq E72, but nobody knows how to help me =(
I'm cooking a spanish 6.5 rom using a kitchen that i found on a polish forum but it have an old XIP, so i found a new xip for smartphone i ported it to my Benq E72....
But my question is: The kitchen folder have a "ROM" subfolder and inside have the files imgfs.bin (1kb), the old xip.bin (2,89mb) and the file os.nb (3mb), so i replace the xip.bin with the new xip.bin i left the imgfs.bin but i don't know what to do with the file os.nb...(i'm not sure but i must integrate the new xip.bin into the os.nb?)
Hope someone could help me...!
Sorry for my english
No ideas? =(
I have cooked the rom with the xip that comes in th kitchen, i just want to know what to do with the file that i've mentioned!
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.