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！
Related
XIP 20275 for Polaris
New XIP 20296
http://forum.xda-developers.com/showthread.php?t=420419
the compressed (zipped ) folder is invalid or corrupted
great job thanks
SHAYDER said:
XIP 20275 for Polaris
Click to expand...
Click to collapse
What is XIP 20275? Tried searching, but although there are lots of posts talking about XIP versions, I could not find any telling me that XIP is, and what's to do with it
ayman morsy said:
the compressed (zipped ) folder is invalid or corrupted
Click to expand...
Click to collapse
Try WinRar http://rarlab.com
pananza said:
what's to do with it
Click to expand...
Click to collapse
copy "MSXIPKernel" folder to "SYS" folder, and "boot.rgu" to "ROM\XIP". Then Build ROM.
One more: in "boot.rgu"
Code:
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:419
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:419
419 is russian language.If you want english you must set 409
New XIP 20296
http://forum.xda-developers.com/showthread.php?t=420419
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 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
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
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...