Hello,
this is a small tutoriel witch explain how to patch XIP.
"maby that work for Kaiser and niki too"
You must have :
- Kitchen for polaris "thank to Udk"
- XIPPort tools "thanks to bepe"
- M'Reloc "thanks to misar"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to All XDA develepers and beta testers without exeption.
And Sorry for my very bad english
Note : If you use "All_packages_to_one.exe" to protect your ROM this method not work
Nice Nice Nice thanks man nice work i will try this soon.
This should all guides look like Great job! I my self would like a tutorial that shows how to Build a rom from Raw-files
Good work M-Amine and thanks for sharing...
Thanks.
But this should be called patch XIP , not port.
vivi
vivi said:
Thanks.
But this should be called patch XIP , not port.
vivi
Click to expand...
Click to collapse
Hi vivi,
Yes it's not a Full XIP porting but for me this is the only solution to have the correct build.
If you know how to port full XIP share it with us
thank you
..........
vivi said:
Thanks.
But this should be called patch XIP , not port.
Click to expand...
Click to collapse
Yes a vivi full xip's port tutorial !
Same,
I never sucess to port bootable XIP with Polaris.
Only patch it.
I can port XIP of ASUS P525 and 535 in 2 minutes with ease. But for Polaris I think there is a secret I don't know.
I ask udk but he never answer my PM, also bepe.
I think if we share what we know , it's better to our communities.
I will buy a Diamond soon.
So tired with Polaris.
vivi
Hello,
ok rectified now "XIP Patch"
Why you cannot port polaris' xip????
I ported a lot of them, and worked ever perfectly.....
no need patch xip!!!
ervius said:
Why you cannot port polaris' xip????
I ported a lot of them, and worked ever perfectly.....
no need patch xip!!!
Click to expand...
Click to collapse
Hi ervius,
we don't have knowledge to make this. an assistant from you or another dev will be the welcome .
thank you
M-Amine said:
Hi ervius,
we don't have knowledge to make this. an assistant from you or another dev will be the welcome .
thank you
Click to expand...
Click to collapse
only need:
original polarix (ORIGINAL!!!) xip and new other device xip
xipport and xipaddresstool
dump both
the original is "\out"
the new is "\out_new" (and package made!)
duplicate "\out" (original polaris xip (no package mode!))
rename into "\out_ref"
open xipaddresstool
open work_dir and select "out"
open ref_dir
and select "out_ref"
compare, all is ok...
now go into out_new\modules\xipkernel\
select "coredll.dll" module, for i.e.
parte module into \out\modules\, overwrite existing
reopen work_dir and ref_dir in xipaddresstool
something to change...
see the values into coredll.dll module, and change by the referred, just on right in same line
now go into xip_new\files\xipkernel, select xipkernel dsm (it start usually with "72")
and paste into \out\files
now if xipaddresstool give all ok, open xipport , realloc P, maybe something goes wrong, about an address, not important, write map, and chek into \out\map.txt if there are some !!! (maybe no "!!!" inside"),
ok, with xipport click on build xip_out.bin
you have ported (partially!) new xip.bin, if you repeat theese operations for all modules on xipkernel, maybe you have a complete xipporting on polaris!
P.S.: some modules in xipkernel give problem and is hardest reallign the modules, so you can leave them, or try step, by step, to port them into old-new xip (\out folder!)
good work!!!
bye!
hi ervius,
when I use insert.exe to insert xip in os.nb.payload devices don't boot at all.
note :
- I use m'reloc to realocate addresses in all modules in MXIPKERNEL, one by one.
- I clic on realoc P
- Write map
- write xip_out.bin
Hello,
J’ai essayé de porter le xip Build 19588 de la ROM du Diamond, si je laisse tout dans MXIPKernel l’appareil ne boot pas, si je laisse les 7 fichiers dans MXIPKernel l’appareil boot mais le XIP est en 19209 (je ne sais pas ou il va chercher ça) merci M-Amine
Pour que XIPPort.exe fonctionne il faut pkgcomon.dll 5.1.10000.1 et pas .dll 5.2.0.0 ;-)
#########Hello,
I tried to bring the xip Build 19588 of the ROM Diamond, if I leave everything in MXIPKernel the camera does not boot, if I leave the 7 files in the ruise MXIPKernel boot but the XIP is a 19209 ( do not know where it fetches it) merci M-Amine
For XIPPort.exe works must be pkgcomon.dll 5.1.10000.1 not. Dll 5.2.0.0 ;-)
Hello dr-jo,
look first post
Note : If you use "All_packages_to_one.exe" to protect your ROM this method not work
Merci M-Amine, le post à changé depuis se matin ;-)
Ça fonctionne, par contre j’ai deux questions, quelle méthode fonctionne pour sécuriser la ROM, et comment changer la date du build 2007 en 2008, merci.
#####Thank you M-Amine, the post was changed from morning ;-)
It works by cons I have two questions, what method works to secure the ROM, and how to change the date of build 2007 to 2008, thank you.
Salut dr-jo,
pour sécuriser ta ROM supprime just les fichier RGU :
- ouvre le fichier \tools\Create_ROM_For_Polaris.bat
- remplace le contenu par ça :
Code:
@echo off
TOOLS\G'Reloc.exe -doit -dump
copy ROM\OS.nb.payload temp\OS.nb.payload
cd temp
@Echo Suppression des fichiers RGU
attrib dump\*.rgu -h -s -r +a
DEL dump\*.rgu
@Echo Activation des attributs HSR
attrib dump\*.dsm +h +s +r
attrib dump\*.dll +h +s +r
attrib dump\*.png +h +s +r
attrib dump\*.tsk -h +s +r
attrib dump\mxip*.* +h +s +r
attrib dump\FMH*.bmp +h +s +r
attrib dump\ha_*.bmp +h +s +r
attrib dump\I-*.bmp +h +s +r
attrib dump\ses*.bmp +h +s +r
@Echo Appuyez sur une touche pour continuer
pause
..\TOOLS\ImgfsFromNb OS.nb.payload imgfs.bin
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Hello dr-jo,
to protecte your ROM, open \tools\Create_ROM_For_Polaris.bat and replace all texte with this :
Code:
@echo off
TOOLS\G'Reloc.exe -doit -dump
copy ROM\OS.nb.payload temp\OS.nb.payload
cd temp
@Echo Suppression des fichiers RGU
attrib dump\*.rgu -h -s -r +a
DEL dump\*.rgu
@Echo Activation des attributs HSR
attrib dump\*.dsm +h +s +r
attrib dump\*.dll +h +s +r
attrib dump\*.png +h +s +r
attrib dump\*.tsk -h +s +r
attrib dump\mxip*.* +h +s +r
attrib dump\FMH*.bmp +h +s +r
attrib dump\ha_*.bmp +h +s +r
attrib dump\I-*.bmp +h +s +r
attrib dump\ses*.bmp +h +s +r
@Echo Appuyez sur une touche pour continuer
pause
..\TOOLS\ImgfsFromNb OS.nb.payload imgfs.bin
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
ervius said:
only need:
original polarix (ORIGINAL!!!) xip and new other device xip
xipport and xipaddresstool
dump both
the original is "\out"
the new is "\out_new" (and package made!)
duplicate "\out" (original polaris xip (no package mode!))
rename into "\out_ref"
open xipaddresstool
open work_dir and select "out"
open ref_dir
and select "out_ref"
compare, all is ok...
now go into out_new\modules\xipkernel\
select "coredll.dll" module, for i.e.
parte module into \out\modules\, overwrite existing
reopen work_dir and ref_dir in xipaddresstool
something to change...
see the values into coredll.dll module, and change by the referred, just on right in same line
now go into xip_new\files\xipkernel, select xipkernel dsm (it start usually with "72")
and paste into \out\files
now if xipaddresstool give all ok, open xipport , realloc P, maybe something goes wrong, about an address, not important, write map, and chek into \out\map.txt if there are some !!! (maybe no "!!!" inside"),
ok, with xipport click on build xip_out.bin
you have ported (partially!) new xip.bin, if you repeat theese operations for all modules on xipkernel, maybe you have a complete xipporting on polaris!
P.S.: some modules in xipkernel give problem and is hardest reallign the modules, so you can leave them, or try step, by step, to port them into old-new xip (\out folder!)
good work!!!
bye!
Click to expand...
Click to collapse
Ervius ,
Thanks for the knowledges.
Shame on those selfish guys.
vivi
Thanks for sharing ervius
I am trying to build a 21042 Titan kitchen ... I have built an NBH file and flashed it, but I can not view text messages, or send new ones. It looks to me like the IMGFSfromDUMP command is not working properly.
If I start with ppck_Titan_21042.nbh (in the zip ... 21042 Titan ROM built with the PPCKitchen.org kitchen) ...
NBHExtract ppck_Titan_21042.nbh
NBSplit -titan 02_OS.nb
IMGFSfromNB 02_OS.nb.payload 02_OS_imgfs.bin
IMGFStoDUMP 02_OS_imgfs.bin
IMGFSfromDUMP 02_OS_imgfs.bin new_imgfs.bin
... The two IMGFS files are different sizes!
02_OS_imgfs.bin - 46,137,344
new_imgfs.bin - 45,834,240
Anyone run into this one before?
Thanks in advance!
DJ
Code:
[URL="http://rapidshare.com/files/248601008/ppck_Titan_21042.zip"]ppck_Titan_21042.zip[/URL]
I was mistaken ... The new_imgfs.bin (converted to .NBH and flashed) works fine. I am ultimately trying to build a Titan kitchen. Looks like my text messaging issue is a BuildOS issue (see http://forum.xda-developers.com/showthread.php?t=530146).
Solved!!!
It is a file attribute issue. All I needed was ...
Code:
attrib /s +A +S +R dump\*
attrib /s -S -R dump\imageinfo.txt
attrib /s -S -R dump\S???
Hello!
I'm trying to cook a ROM for SonyEricsson Experia X1 with some of newer XIP versions but I've got an error on Installin CABs on device.
If I cook with XIP 23562 I havn't got any problem, but if I cook with 28238, 28240, 28244 or 29002 I'll receive an "Error 0x80004005 - Install error" during Customization.
I don't understand what's the problem.
I've got this folders/files:
1) OperatorPkg - config_operator.txt
Code:
LOCK:Enabled
CFG: \WINDOWS\config_PT.txt
2) OperatorPkg_PT - config.PT.txt
Code:
CAB: \WINDOWS\wlan_1.5.cab
CFG: \Windows\config_AP.txt
3) ConfigAP - config_AP.txt
Code:
CFG: \WINDOWS\config_end.txt
4) OperatorPKG - config_end.txt
Code:
CFG: \Windows\config.txt
5) OperatorPKG - config.txt
Code:
LOCK:Enabled
LOCK:Disabled
RST: Reset
But when, in Customization, it tryes to install "wlan_1.5.cab" I receive that Error.
Same error for any cab I can put as replacement for that one.
Signing CABs could be the problem? But with XIP 23562 all cabs are installed without problems...just with newer XIP versions I've got that problem.
Can you help me?!
Thanks!!!!
TRY ONLY THE CONFIG.TXT and put them like the following example:
CAB: \windows\rescoexploreren_aio.arm_1.cab
CAB: \windows\SKTools5q.cab
TSK: \windows\nikos wvga blue.tsk
LOCKisabled
RST: Reset
Leave the rest txt untouched.
try to remove windows security
I think it is problem related to setting the attributes correct. Check this post.
http://www.mobileunderground.info/showthread.php?t=17128&p=45430#post45430
THX guys!
That's it! (with a bit changes)
No any attrib changes in EVK, so I've added whole this section:
Code:
attrib +H temp\dump\S00? /S
attrib +S +H +R temp\dump\*.dll
attrib +S +H +R temp\dump\*.exe
attrib -S -H -R temp\dump\*.lnk
attrib +S +H +R temp\dump\*.csv
attrib +S +H +R temp\dump\*.htm
attrib +S +H +R temp\dump\*.mui
attrib +S +H +R temp\dump\*.doc
attrib +S +H +R temp\dump\*.dat
attrib +S +H +R temp\dump\*.provxml
attrib +S +H +R temp\dump\*.xls
attrib +S +R temp\dump\*.xml
attrib +S +R temp\dump\*.mid
attrib +S +R temp\dump\*.vol
attrib +S +R temp\dump\*.txt
attrib +S +R temp\dump\*.wav
attrib +S +R temp\dump\*.wma
attrib +H temp\dump\*.png
attrib +H temp\dump\*.brn
attrib +S +R temp\dump\*.gif
attrib -S -R -H temp\dump\*.inf
attrib -H -S -R temp\dump\*.jpg
attrib -H -S -R temp\dump\*.bmp
attrib +A +R +H +S temp\dump\*.provxml
attrib +H temp\dump\*_manila
attrib +H temp\dump\*manil*
Now it works!!
AndrewSh said:
24606_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409
Windows CE: 5.2 Build 5405 (April 13 2010. 23:12:43)
DFT
Click to expand...
Click to collapse
Very thanks for this
Anyone have a normal xip from this build??
Cheers
Laurentius26 said:
I don't know if you did and what device your cooking for but on HD2 you need to remove SMS_Providers from SYS.
Click to expand...
Click to collapse
Oh, did not know that. Thanks I have no sms issues but it might save some space
EDIT: Does this also include if i have TMOUS as a base? I guess that the op info is in OEM.
All the rollups from B4PJS 4shared account seem to be gone? Anyone got a COM3 rollup handy?
AndrewSh said:
23648_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 AKU5305 Windows CE: 5.2 Build 4578 (Apr 15 2010. 15:44:15)
25016_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 AKU5300 Windows CE: 5.2 Build 5912 (Apr 13 2010. 17:23:20)
DFT reuploaded by asusmobile.ru
Click to expand...
Click to collapse
You Have maybe, normal xip.bin from this build?
AndrewSh said:
21651_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 AKU5300 Windows CE: 5.2 Build 3579 (Apr 15 2010. 17:00:08)
22013_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 AKU5305 Windows CE: 5.2 Build 4908 (Apr 15 2010. 15:44:14)
DFT - asusmobile.ru
Nokser, no I don't have it - DFT never uploads xip.bin in the builds. Is that a big problem? Normally it takes 3 or 4 seconds to generate bin from packages.
I use a kind of OSBuilder that can use either MSXIPKernel or xip.bin to make roms so actually I don't care...
Long ago I uploaded here the utility to make xip.bin. Read txt files to know howto - they are in several folders - you should read all of them.
Click to expand...
Click to collapse
Thanks My friend for this
People on the DFT, they helped me with this also
Thanks Andrew.
Nothing new on the 231XX?
New Builds 23xxx:
23648_AKU5305
23645_AKU5305
Or
24xxx
or
25xxx
AndrewSh said:
23651_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409
23651 - AKU5305 Windows CE: 5.2 Build 4580 (Apr 22 2010. 15:43:28)
Thanx to indagroove for hosting provided!!!
Click to expand...
Click to collapse
Very thanks AndrewSH
I will look for the flash dio for 21903.. htcpedia doesn't have it yet..
@AndrewSh
Thanks m8...but any chance for 0407 Packages wqvga ?
It would be nice....
GoodMonk said:
@AndrewSh
Thanks m8...but any chance for 0407 Packages wqvga ?
It would be nice....
Click to expand...
Click to collapse
Would be But DFT always uploads only English and Chinese. I prefer English
I would offer to take the closest lang files from any available rollup - last few months there is not so many changes in lang files - just compare correspondent English langs from old and new build in Restorator and add new items from new English mui to your old German ones if necessary.
That's the way how my Russian colleagues always do.
Does anybody can share a working Base 1.77.931.1 (i.e. translated WWE)?
barbapappa_86 said:
23568_WVGA_0409 EVK ready
http://www.4shared.com/file/hSiV0Laz/23568_WVGA_0409.html
Click to expand...
Click to collapse
Oooh nice! You also happen to have vga or the rollup?
nickschot said:
Oooh nice! You also happen to have vga or the rollup?
Click to expand...
Click to collapse
No, sorry. I have the .dio so you can dump it. Then i think you´ll get all resh.
no one has the rollup of 23568?? looking for vga.
Diegis0n said:
you can find all 23568 stuff here
Click to expand...
Click to collapse
isnt that only for the ppckitchen though?
and not the vk kitchen?
hasseye said:
isnt that only for the ppckitchen though?
and not the vk kitchen?
Click to expand...
Click to collapse
You can sort it to VK by TehPenguin's tool easily. (search for dump sorter)
hasseye said:
isnt that only for the ppckitchen though?
and not the vk kitchen?
Click to expand...
Click to collapse
I used those files from that link and my rom came out really corrupted. So i used a 23568 that was posted for wvga here on xda and used the vga res files from 23566 instead of the wvga files in the 23568 package i downloaded.
just fyi: that files are prepared for the ppckitchen, and the attributes are modified. If you want to use it for vk, you need to modify the CreateBuildRom.bat.
attrib S00? +H /S
rem attrib *.* +A -S -H -R
attrib *.dll +S +H +R
attrib *.exe +S +H +R
attrib *.lnk -S -H -R
attrib *.csv +S +H +R
attrib *.htm +S +H +R
attrib *.mui +S +H +R
attrib *.doc +S +H +R
attrib *.dat +S +H +R
attrib *.provxml +S +H +R
attrib *.xls +S +H +R
attrib *.xml +S +R
attrib *_manila +H
attrib *manil* +H
attrib *.mid +S +R
attrib *.vol +S +R
attrib *.txt +S +R
attrib *.wav +S +R
attrib *.wma +S +R
attrib *.png +H
attrib *.brn +H
attrib *.gif +S +R
attrib *.jpg +S +R
attrib *.bmp +S +R +H
REM Fix for smartskey.inf
attrib *.inf -S -R -H
attrib +A +R +H +S *.provxml
attrib -H -S -R *.jpg
attrib -H -S -R *.bmp
ECHO. Fixing Attributes
Click to expand...
Click to collapse