Related
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Why not ?
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, because for me use m'reloc is useless.
Click to expand...
Click to collapse
ervius, you doesn't use m'reloc when you port xip ?
can you tell me which XIPPort is the last one because Bepe doesn't make release number...
The procedure you're using is :
- Dump the xip.bin
- Make Pkgs
- Replace the new modules
- Undo
- Realloc P
- Build xip_out.bin
Thanks for your help
ervius said:
Hi all, I've a question, I readed in a lot of 3ds that to reallocate modules into xip section with xipport (the last by bepe) someone use also m'reloc....
I cannot find into xipport.exe imageinfo.bin references, apart the ones that creates imageinfo.bin into \out\modules\modulename!
now, my question is:
why they try to use m'reloc if xipport doesn't need it???
xipport.exe works on modules by imageinfo.txt, with D=, V= and R= values
if someone can explain better this step, becouse for me use m'reloc is useless.
Click to expand...
Click to collapse
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
peter petrelli said:
m'reloc isnt useless. Traditionally m'reloc is used when the 'realloc P' and 'write map' buttons of Bepes XIPPort.exe causes the program to crash. In other words when two XIP modules occupy the same address and produce '!' characters throughout your MAP.txt.
Click to expand...
Click to collapse
you need m'reloc for nothing.
all xipport process is based on imageinfo.txt files, while m'reloc changes module values on imageinfo.bin (and xipport ignore thatr file in module, in realloc P and in write Map.txt), bwt, I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt.
and to confirm all I hex edited xipport.exe, and it only writes imageinfo.bin, while dump xip.bin, never read imageinfo.bin to check values inside., try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin, realloc P, write map, write new xip.bin, insert into payload and flash rom, it starts normally...., xipport not need imageinfo.bin, and doesn't use them.
ervius said:
.. xipport not need imageinfo.bin, and doesn't use them.
Click to expand...
Click to collapse
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
mun_rus said:
modifed xipport can make imgainfo.bin and u can manually extract it from xip.bin (it's not so complicated)
m'relock is usefull when u have to move VA of module coz of !!!!!!!!! in map.txt
Click to expand...
Click to collapse
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
ervius said:
for me is useless, becouse, I don't know whatr kind of xipport you use, the one that I use, only create imageinfo.bin for compatibility with other utils, but created imageinfo.bin in modules, xipport ignores them until xip_out is created.
Click to expand...
Click to collapse
Can you share your XIPPort release please ervius ?
MickyMax said:
Can you share your XIPPort release please ervius ?
Click to expand...
Click to collapse
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
ervius said:
is not mine, is xipport that you also use, only I told that it create files imageinfo.bin, but never it use them, I checked all operations, an dthe imageinfo.bin files remain invariates, after: coredll.dll porting from xip to other ones...., only imageinfo.txt chenge values.
Click to expand...
Click to collapse
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
MickyMax said:
Excuse me. I would like to say : can you upload the release you use because we can found many builds in the forum but they seem the same... ?
Click to expand...
Click to collapse
bo problem, I use this release and xiptools to realloc better all modules into xip...
bye!
Big thanks ervius !
ervius said:
try you also to hexedit it and change imageinfo.bin inside into:"omageinfo.bin", dump xip.bin, and inside all modules, you 'll find "omageinfo.bin", delete all omageinfo.bin
Click to expand...
Click to collapse
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
tjkhattak61 said:
Hey ervius, you were right about this I did it and have now deleted all omageinfo.bin files from all modules. But now may I ask how to as you said "I use XIPAddrTools, joined to xipport, and it use m'reloc, but with m'reloc, this utility:"XIPAddrTools", changes values on imageinfo.txt, it's the real way to port xip, playing around imageinfo.txt". Please explain little I will do rest thanks.
Click to expand...
Click to collapse
you have to use xiptools with imageinfo.bin...
after, when finish, before realloc P and build Map, and build xip_out.bin, delete all imageinfo.bin, xip_out.bin will be created successfull, like all imageinfo.bin were inside all modules...
P.S.: is bit difficult use the xip_tools, but when you understood how it works, is easiest port xip... thanks to the author...
try it!!!!
no more needs external cab extractor...
(from an idea of:"ArHon" with his: OEM Packages Compiler, that opened my mind about....)
full registry compatible now....
new version 2.2 solved problem with "spaced" folder for remodule!!
bye!
lastest 2.7 version
solved unicode saving iusse for rgu files!
solved bug on "\" folders creation into registry, the good keys were with "\\" not only with "\"
Thanks ervius GREAT AGAIN!!!
i will try, you have save us a lot of work creating OEM Packages.
Here is my little contribution. Added Spanish language to lang.xml.
Thanks again.
can you explain what can it do?
Hello
Thank you very much, this is my contribution french language added to lang.xml.
thanks guys, I added both xml files, and now at 1st post can download yet included francays and spanish language, 2.1 version.
addedd "cab" filter on openfile...
P.S.: the package creator, is able to remodule all files inside only if executed on non "spaced" folder,
example:
c:\documents and settings\... (no GOOD)
c:\_a_b_c_C\kitchen_deV_Trin_19900\ (is GOOD!)
ok???
bye!
yuzanuvole said:
can you explain what can it do?
Click to expand...
Click to collapse
it trasforms cabs into package to insert in kitchen to cook roms...
ervius said:
it trasforms cabs into package to insert in kitchen to cook roms...
Click to expand...
Click to collapse
And it adds even registry keys automatically??(I am not very expert in cooking ROMs!!)
yuzanuvole said:
And it adds even registry keys automatically??(I am not very expert in cooking ROMs!!)
Click to expand...
Click to collapse
yes it do!!!
ervius said:
yes it do!!!
Click to expand...
Click to collapse
Very very great!!!
ervius said:
it trasforms cabs into package to insert in kitchen to cook roms...
Click to expand...
Click to collapse
Is there any posibilities of doing the inverse process, i mean to take and OEM package, and build .CAB file automactly?
I know it is not very usefull for ROM cooking, but i have many OEM Package translated to Spanish and a lot of users like to install LITE ROM and then add .cabs of dessired applications...
I think it will be the perfect complement for this GREAT!!! application.
Very Good Work Ervius, congratulations... you are allways surprising us...
axl79 said:
Is there any posibilities of doing the inverse process, i mean to take and OEM package, and build .CAB file automactly?
I know it is not very usefull for ROM cooking, but i have many OEM Package translated to Spanish and a lot of users like to install LITE ROM and then add .cabs of dessired applications...
I think it will be the perfect complement for this GREAT!!! application.
Very Good Work Ervius, congratulations... you are allways surprising us...
Click to expand...
Click to collapse
if initflashfiles.txt inside, I think is possible....
have to study about...
hi ervius
thank's is good packtages creator v2.1
if possible share kitchen_deV_Trin_19900 ?
Posted in the correct thread.
http://forum.xda-developers.com/showthread.php?p=2159891#post2159891
Sorry for ask here off-topic.
Thanks.
hi
axl79
rom 19701 rom pdaviet
POLARIS_WM6.1_v1.52.61.06_B19701
extract xip polaris =>> trinity not fonction ... 42.b3 ....
extract polaris =>> xip polaris ok ...
patch polaris to trinity ??? i don't no ??
if possible xip polaris =>> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00340000
trinity xip ==> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00300000
?????
oggi1969 said:
hi
axl79
rom 19701 rom pdaviet
POLARIS_WM6.1_v1.52.61.06_B19701
extract xip polaris =>> trinity not fonction ... 42.b3 ....
extract polaris =>> xip polaris ok ...
patch polaris to trinity ??? i don't no ??
if possible xip polaris =>> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00340000
trinity xip ==> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00300000
?????
Click to expand...
Click to collapse
this 3d is for package creator v2 not for xipporting.
news:
in 1st post version 2.2, solved problem for "spaced" folders for remodule files, now you can use also "c:\documents and settings\..." folders..... for example!
axl79 said:
i didn´t realise "My rom: Italian WM6.1 os 5.2.19900 build 19900 1.0.4!!!"
have you ported build 19900 from another device????
where it is released... i dind´t see anything about this build...!!!
sorry for offtopic, but where trying to port build 19701 from hermes to trinity with your kitchen and the resultant ROM won´t boot, we take XIP dump from hermes ROM (PDAVIET), put files into new XIP folder, push "Port IT!", and choose XIP from other device when asked, but it doesn´t boot!!
What we are doing wrong?, is this the correct procedure?.
Thanks.
Click to expand...
Click to collapse
xipporting on mi kitchen maybe needs some corrections....
try this last version of buildos....
and tell me if works xipporting now...
download here:
http://rapidshare.com/files/111296473/kitchen.zip
bye!
FOR package creator, we all need other language into lang.xml, so if someone can insert other languages, I'll happy to update the program!!
bye!
Portuguese Language
ervius said:
FOR package creator, we all need other language into lang.xml, so if someone can insert other languages, I'll happy to update the program!!
bye!
Click to expand...
Click to collapse
Hi!
Find attached the XML file with Portuguese language.
Thanks
FInixNOver said:
Hi!
Find attached the XML file with Portuguese language.
Thanks
Click to expand...
Click to collapse
good, thanks!
ervius said:
try it!!!!
no more needs external cab extractor...
(from an idea of:"ArHon" with his: OEM Packages Compiler, that opened my mind about....)
full registry compatible now....
new version 2.2 solved problem with "spaced" folder for remodule!!
bye!
Attached Files package-creator-v2_2.zip (297.5 KB, 40 views)
__________________
.....nothig.....
My rom: Italian WM6.1 os 5.2.19900 build 19900 1.0.4!!!
if you appeciate my works and want drink a beer with me... Donate to me!!!
bye!
Click to expand...
Click to collapse
Let's sit down and Bottoms up!!
Thank you so much
Hi all, cooperating with udk, and thanks to the author of the tricks into \mytools folder (I'd like to thank but I don't know who he is!), XipporterEx was born, how it works.....
easy:
you have to insert into:
old xip, new xip to port, and your payload.....
in one click you can port all xip or only MSXipkernel, done it, you can inster xip_out.bin into your os.nb.payload, and if you don't know where, the rightg offset where insert it into payload, you can find it only clicking on a button, and finally you have your new os.nb.payload updated, ported and ready to cook....
all infos and download here:
http://www.forumhtc.com/forum/showthread.php?t=3471
or here:
http://forum.xda-developers.com/showpost.php?p=2813417&postcount=9
bye!
ervius said:
Hi all, cooperating with udk, and thanks to the author of the tricks into \mytools folder (I'd like to thank but I don't know who he is!), XipporterEx was born, how it works.....
easy:
you have to insert into:
old xip, new xip to port, and your payload.....
in one click you can port all xip or only MSXipkernel, done it, you can inster xip_out.bin into your os.nb.payload, and if you don't know where, the rightg offset where insert it into payload, you can find it only clicking on a button, and finally you have your new os.nb.payload updated, ported and ready to cook....
all infos and download here:
http://www.forumhtc.com/forum/showthread.php?t=3471
bye!
Click to expand...
Click to collapse
Looks very cool, i will download it now..
danny_and_2 said:
Looks very cool, i will download it now..
Click to expand...
Click to collapse
yes, for me works well, ported all 2075x and 209xx xips and ever worked fine....
try it and report
bye!
Thanks, excellent news!!!
Public link: http://rapidshare.com/files/168872430/XipporterEx_new_find_xip_into_payload.rar
xxxelent tool it work very fine
Works good here too. Great work!
Awesome tool!!! Thanks a lot!
Hey Ervius. Using your tool (its ROCKING & AWESOME brother)
Couldnt port the 20759 XIP but maybe something is wrong with the bin that I have. Will try again on shipped XIP and check
mondilv said:
Thanks, excellent news!!!
Public link: <deleted>
Click to expand...
Click to collapse
You are probably best off to go to the thread in the op. This way you get the most recent version of the tools.
Best regards,
-boggsie
I have triyed it using as old xip Diamond XIP 1.97 and new XIP Blackstone 1.14 20757, to port only MXKERNEL, it works without anywarning, but when I dump the xip using XIPPort some module are missing like :
cachefilt.dll
mencfilt.dll
relfsd.dll
htcfsfilter.DLL
kd.dll
and some other for which I have read that they can be deleted
Is it normal ?
try again,,
TekTonik said:
I have triyed it using as old xip Diamond XIP 1.97 and new XIP Blackstone 1.14 20757, to port only MXKERNEL, it works without anywarning, but when I dump the xip using XIPPort some module are missing like :
cachefilt.dll
mencfilt.dll
relfsd.dll
htcfsfilter.DLL
kd.dll
and some other for which I have read that they can be deleted
Is it normal ?
Click to expand...
Click to collapse
yes, its normal!!!
I got xipporting.bat error
pawaj said:
I got xipporting.bat error
Click to expand...
Click to collapse
??? what mean xipport.bat, if there is an exe to port xip???
ervius said:
yes, its normal!!!
Click to expand...
Click to collapse
Hi Ervius what should we do with cleaned modules ?
put it manualy in the xip or un rom or never take care about these modules ?
Regards
ervius said:
??? what mean xipport.bat, if there is an exe to port xip???
Click to expand...
Click to collapse
Thankyou for your respond.I fix it already i forgot to install .net
by the way How can I use with Artemis?
TekTonik said:
Hi Ervius what should we do with cleaned modules ?
put it manualy in the xip or un rom or never take care about these modules ?
Regards
Click to expand...
Click to collapse
the xip have to works better without all the unused modules (on diamond!) but you can try on other devices, and report witch are useless and witch not!
last version: 1.2 revision 6, here:
http://forum.xda-developers.com/showpost.php?p=3007615&postcount=383
use your preferred os.nb.payload and your preferred xip (old and new!)
in this release you can port xips and now, remove uldr section, move xip and reduce unused space between xip and imgfd section, and your os.nb.payload will be reduced around 3.5 Mb, ready to be used to build new smaller (so more memory avaiable into rom on device ) roms
ervius said:
in this release you can port xips and now, remove uldr section, move xip and reduce unused space between xip and imgfd section, and your os.nb.payload will be reduced around 3.5 Mb, ready to be used to build new smaller (so more memory avaiable into rom on device) roms
Click to expand...
Click to collapse
The problem with this revision is the resulting payload being only 3.8MB. For the ULDR removal and IMGFS increase to work we need to use the -conservative switch on nbmerge and ImgfsToNb tools. This switch doesnt allow the higher size imgfs to be packed into the lower size template
Also the tool doesnt modify the LBA & no of sectors of IMGFS partition and needs to be done manually, but again the payload wont work since the nbmerge has to be with -conservative switch. Hope I am sounding clear without confusions
I Used HTC Rom Tool. to make the NBH file. and it worked fine. my os.nb.payload file is now 4.11 mb. xip os is 20764. Available memory before was 203.49, size after was 203.49. So I am not sure what i did wrong. aside from the smaller os.nb.payload file. everything seems to be the same.
It does boot and everything is fine there.
Full Xip Porting with original OEMXIPKernel
-NEW FROM HTC IOLITE 5.2.20765
View attachment 152516
Please Feedback!
-5.2.20769 Xip
View attachment xip_out20769.zip
-5.2.21014 Xip
View attachment xip_out.zip
Try to download SYS 1,5 kb/s ....
media fire
nothing about new direct 3d driver?
magic55 said:
Try to download SYS 1,5 kb/s ....
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?p=3120826
You'll have to port it though. It's for a Hermes.
adwinp said:
Here you go:
http://forum.xda-developers.com/showthread.php?p=3120826
You'll have to port it though. It's for a Hermes.
Click to expand...
Click to collapse
Dzięki / Thanks
new 5.2.20769 available !
New xip.bin from htc Iolite on post #1
for SYS 20765? any news?
I used search and find this
http://forum.xda-developers.com/showthread.php?t=476828&highlight=20765+sys&page=2
How to import the xip_out.bin to the OS.NB.payload.
Have tried XIPPort.exe and Insert.exe, none working?
infido said:
Full Xip Porting with original OEMXIPKernel
Click to expand...
Click to collapse
Good initiative brother But for complete porting, we also need to Gwes.exe from same XIP builds, remember? Details can be read from my tutorial thread
What must i do to change the xip? Where must i copy the xip.bin?
thanks a lot!
write xip_out.bin in to os.nb.payload ,address 00320000,with XipPort Tool.
best tool to port and replace original Xip is XipPorterEx made by Ervius
GWes.exe???
infido said:
write xip_out.bin in to os.nb.payload ,address 00320000,with XipPort Tool.
best tool to port and replace original Xip is XipPorterEx made by Ervius
GWes.exe???
Click to expand...
Click to collapse
i'm so sorry, but i don't undestand anything. i'm new in this type of changes.
can you explain it to more slowly?
Thank you!
Searching for tool XipPorterEx made by Ervius
Hello,
where i can find this tool.
i search for an hour, and no download-link is working for this tool.
thanks
everal
german glofiish m800 rom-customizer.
Hi!
I'm a rom developer and i've managed to cook a rom for my Benq E72 using the build 23017, but now i want to use the build 23090.
I'm trying to extract the "XIP" of an Standard Emulator Image from MS SDK 6.5.3 using this command:
nbsplit -emu os.nb
os.nb.payload
RomMaster -w 5 os.nb.payload -x -o xip.bin >NUL
But i always get an error....
[Info] It is a common ROM.
[Error] Load nb00 failed.
Also i have a rom for this device that use the build 23090, but i cannot extract the xip either
Hope someone could help me! Or tell me where i can get the XIP and SYS 23090 for Smartphone!
Thanks!!!
Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish
AndrewSh said:
Why do you want to use an ancient build?
It's from November 2009
The new builds are available here... But it's your choice anyway.
The closest think I have is 23092. If that will make you happy - get it
http://dl.dropbox.com/u/3324710/23092_XIP.BIN_MSXIPKernel_SYS_DPI_96_192_0409_0419.7z. Only Eng and Ru - no Spanish
Click to expand...
Click to collapse
Thanks!
I want to use that build because is the only one i know that works well on my device....
Thanks for the file, i'll try it!
I can mix that XIP 23092 and SYS 23090 right? i have the spanish resources from the emulator rom
samWMEmuKitchen v0.2b - ROM Kitchen for Windows Mobile Emulator
nickleby said:
I can mix that XIP 23092 and SYS 23090 right?
Click to expand...
Click to collapse
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Alexx~, dude , I think nick has problems with extracting the stuff from emulator.
AndrewSh said:
Sure you can. And it's not a mix - xips in 23089-23094 were the same modules with different dsm. So the only difference will be number of the build - it will look like CE.OS 5.2. 23092 (Build 23090.x.x.x)
Click to expand...
Click to collapse
Ok! Thanks for all your help!!
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
You have to check it by yourself. Normally everything should work, why not. All the issues described in the topic are for 20% device-dependent and for 80% user-dependent
For me and of course for Alexx~ (he knows much more than me about the things) - every build works
AndrewSh, i realized what the problem is. In samWMEmuKitchen have the opportunity to extract dump, after the dump will be created os.nb, from which they can then extract xip.bin the usual way.
It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin
nickleby said:
Oh, just to be sure....
All the things posted here http://forum.xda-developers.com/showthread.php?t=544445 works on Smartphones
Click to expand...
Click to collapse
NO! Those builds does not work on Smartphone devices.
BenQ E72 does have WM Standard.
Those resources are for touchscreen devices (WM Professional).
Alexx~ said:
It is still easier, nbImageTool extracts xip.bin directly from the emu image.bin
Click to expand...
Click to collapse
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks
nickleby said:
How??
nbimagetool SP_ESP_GSM_QVGA_VR.bin
Files is not an NBH!
Checking for .nb
Error reading MBR
Forget it! xD i've solved the problem....
Thanks
Click to expand...
Click to collapse
run the program as an administrator
I am writing in this way directly, since I have not received help in the forum, and that maybe I have not been very specific in my request to place it in the forum.
I own a Smartphone, brand MWG Zinc 2 Rom and all I own are in English.
Just explained on the website of the creators of the ROM for my device, the entire procedure for Cook ROM.The page es PDAGismo.com
My question is very different from the way this process is done for different devices because they do not know much about it.
The page is in Thailand but you can translate, I do not understand is the whole process of the preparation of the ROM.
Someone could explain all this ?
It is so hard to accomplish this task by a person with basic computer knowledge and without any programming domain?
Help me, please.
Thanks