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...
Related
Hello all,
Can anyone please post ace_ddi.dll found in AKU3.3 to be used in WM6?
This DLL has been (will be) applied in the new WMXL.2, but I don't feel like flashing my highly tuned device once again, so I simply wish to add this DLL to fix video corruption with TCPMP and CorePlayer...
So, anyone, please? thanks
Same here. Would really appreciate if someone could upload this dll.
shandar said:
Same here. Would really appreciate if someone could upload this dll.
Click to expand...
Click to collapse
look... download an AKU 3.3 ROM from the Wiki and then extract it... use ROM Kitchen or whatever if you like, but either way, do it yourself... it's easy enough
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Ai, that sucks. How exactly did you extracted that file from AKU3.3? If I do a ROM dump, I get a subdirectory called ace_ddi.dll instead of a file. That subdir contains a bunch of files. I looked into those files, none of them seems to be containing binary data what would represent the original file (no DLL entry point found). the S00* files combined seems to be the size of the file needed though, are they encoded in a different format? how do I convert that into the file I need?
you need to have RecMod.exe in the same directory as viewimgfs.exe IIRC or the dlls won't be created from modules. If its there, the reconstructed dll will also be in the folder.
Ah, thanks a bunch, that worked. gonna try applying it (but after a backup as you sugested)
Well... Have to report that once I applied it, the system doesn't boot anymore, and indeed a hard reset is needed.
How did it got integrated into WMXL.2 ?
The dll from the HTC 3.3 dump is identical.
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
This is true, you cant do anything to them once they are active, I was trying to do this yesterday.
kyphur said:
I've replace a few system dlls in WMXL v0.20 and it seems that you must actually embed system dlls into the Rom, not replace them after your device is flashed.
Click to expand...
Click to collapse
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
It didn't fix it for me...
Heimiko said:
Can you confirm that with the WMXL.2 release TCPMP can make use of the ATI decoder without scrambling the screen?
Click to expand...
Click to collapse
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
the trick is ....just replace the dll not the whole module.
Thought I tried that and the resultant dll was 0 bytes ... Must've been something I did... I'll try again.
Sleuth255 said:
hmmm... I've not been able to make a valid os.nb containing ace_ddi.dll using aChef tools. This dll is a system module, and while I can delete it w/o issues with delfile.exe, I am unable to use addfile.exe to add the AKU3.3 version.
Addfile.exe blows up if I point it to the directory containing the module information from viewimgfs (assuming because I'm pointing it to a directory not a file here). Adding the actual ace_ddi.dll reconstructed by recmod works with addfile, but a resultant viewimgfs dump of the new os.nb shows shows a zero byte ace_ddi.dll instead of a module directory.
Is there a trick I'm missing here?
Click to expand...
Click to collapse
try this; install developer certs and sign the DLL with the privileged certificate, no doubt it'll work after that post-install.
Got it to work this time. Subsequent imgfs dump showed the correct size for ace_ddi.dll. The only thing I did different was put the ace_ddi.dll file itself into the same directory as addfile.exe... hard to believe it was that though. New Os.nb flashed just fine & i've got improved ImageON performance. It still pixelates somewhat but at least it doesn't tear up the whole screen any more...
must be my quirky kitchen
edit: notes on ImageON pixelation: There's some good workarounds for this that still retain ImageON acceleration in the Coreplayer forums. apparently things work better in landscape mode....
more on this: I didn't test right. When I set up coreplayer correctly, ImageON was still experiencing the same issues. My 8525 also showed this same problem on WM6 with the replaced ace_ddi.dll from the Cingular AKU3.3 rom. However, when I flashed the AKU3.3 ROM back onto my 8525, the problem went away
Conclusion: it would appear that there's more to this fix than simply the newer ace_ddi.dll
need original ace_ddi.dll
Sleuth255 said:
Get a full backup first. I applied ace_ddi.dll form Cingular AKU 3.3 to my WM6 and bricked. Had to hard reset to fix. I'm checking for diffs between that and the HTC ROM now...
Click to expand...
Click to collapse
Hi! Can you give me the ace_ddi.dll from rom, please?
Hello there.
well, i'm trying to cook a new version of my ROM, but i have sawn on Fanman release that there's no RGU files...
Because he seems to have merged all of them in the default.hv.
I've tried, but many keys disappear when flashing it to phone...
Have you got any ideas ?
Thanks
Best regards
What kitchen are you using to cook the rom? I've been using the Core Pro kitchen but noticed that none of the changes I made to the .hv files were being included in the cooked rom so this would explain why none of yours are either. For now stick all the changes into 1 rgu file, will be much easier to insert into the hives once it is working again that way I'd imagine.
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
kulbut0r said:
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
Click to expand...
Click to collapse
Is that not what he already has tho? I thought the point of his post was how to get all the rgu files into the hives but since this is not currently possible (as far as I am aware, kitchen dependant of course) he may as well place them all into one rgu file.
yep, all changes are not tooked in the hv files, i wanna have only the hives to gain more spaces...
I'll try again
aje_fr said:
to gain more space...
Click to expand...
Click to collapse
kulbut0r said:
Click to expand...
Click to collapse
No more RGU = More space on ROM
This evening, i tried to copy HV after buildos and before createrom, but nothing more....
And when i looked on the temp folder of kitchen, the hv files are really small and doesn't include the hv files in sys\metadata...
Really strange, it seems that modifications in the hives of sys\metadata are not included in final rom ?!
aje_fr said:
No more RGU = More space on ROM
Click to expand...
Click to collapse
small benefit however !
why not to stay with markquinton's recommendation : place all you updates into one rgu file.
So, i finally make it work but strangely i have more memory but software couldn't start and claim an memory error...
I can't even access to program folder
Anybody don't know why ?!
Thanks
aje_fr this is file FRE mui in Faman Rom and RGU file..!
http://rapidshare.com/files/44793173/MUI_RGU_040C.exe
method :
Dump Faman Rom and Copy All file to Dump Folder.Then it.Run PKT tools make OEM and SYS.Now u have OEM and Sys.In OEM and SYS copy all file FRE lang u need..!
Cheers..!
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
aje_fr said:
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
Click to expand...
Click to collapse
u online yahoo mesenger ???
i'm online now...!
Has anyone managed to successfully edit the hive files and have the changes included in their built rom? As I've been playing around with this for a while but have as yet still not managed it. I'm getting annoyed with having to set a lot of default settings in rgu files when they could easily be included in the hives from the start.
Ok im seeking those who have expierience with this, I am porting the XIP from the Raphael build and managed to port everything over but heres where problems start:
1. When i use the reloc tool 2 of the modules wont reloc it give me and invalid key error.
2. Once i reloc and rebuild the xip_out.bin how do i combine that and make a new OS.nb? Also how big approximately should the .nb file outputted by the XIPport tool be, mines only about 6mb...
3. What is the default XIP device key to put in the XIPport to in the line above nk.nb for the Vogue?
PLEASE help me all help is appricieated.
fayfay392 said:
Ok im seeking those who have expierience with this, I am porting the XIP from the Raphael build and managed to port everything over but heres where problems start:
1. When i use the reloc tool 2 of the modules wont reloc it give me and invalid key error.
2. Once i reloc and rebuild the xip_out.bin how do i combine that and make a new OS.nb? Also how big approximately should the .nb file outputted by the XIPport tool be, mines only about 6mb...
3. What is the default XIP device key to put in the XIPport to in the line above nk.nb for the Vogue?
PLEASE help me all help is appricieated.
Click to expand...
Click to collapse
1. what 2 modules? you will find future porting will be easier if you only move modules in OEMXIPKernel.
2/3. in xipport the bottom box is for the address to insert your xip.bin back into os.nb.payload. for vogue you want address 00320000
dcd1182 said:
1. what 2 modules? you will find future porting will be easier if you only move modules in OEMXIPKernel.
2/3. in xipport the bottom box is for the address to insert your xip.bin back into os.nb.payload. for vogue you want address 00320000
Click to expand...
Click to collapse
Thanks for the quick reply, if there anyway you can help me on MSN? I can only remember one module at the time its like hd.dll...
Ok im making progress, i have it ported and moved into the OUT folder into there corresponding locations. Now i use the 320000 code and export it to xip.bin now how to i combine this to the os.nb to make into the new one?
PLEASE HELP QUICK!!!
Sounds like you need to read some more guides.
00320000 is how you combine it.
Thats what i used and did. typo. flashing now.
Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar
Bump, no one want to look in it and help me ??
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.
How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.
Bump, bump, bump.
Must be some1 out there, there can help me find my mistake ;/
danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon
anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot
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.