yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] Ameet:
I know :( Dont know if the calculations I'm doing are wrong. Will trouble you more sometime on msn just for a recheck :D

nbmerge crashes since the imgfs LBA created by Ervius's tool is incorrect. If you manually change them then it works well. Also if you dont use the -conservative switch then it crashes. Main problem is if you do use the -conservative switch then you can cook larger sized imgfs (OEM+SYS) into this smaller OS.nb

The text boxes are very much right brother. I'm talking about the LBA of the imgfs partition. If the imgfs starts at 320000 offset then the LBA is to be 40 06 (in little endian) and the no of sectors of XIP partition is supposed to change to 60 00 but it still remains at 00 09. See the first page here for screenshots of the MBR & MSFLSH50 region

Also 2nd problem is you cannot manually change the size of new XIP to be inserted, which makes it difficult to get the new imgfs start divisible by 20000 as needed by Diamond ROM. Check this image. After removing ULDR I want the XIP to start at 20000 and end at 31FFFF making the imgfs divisible by 20000 and start at 320000. But with this revision I cannot do that. After changing the value if I click on preview, the value goes back to default. I think the solution is if the ULDR can be only reduced by 30000 and made to start at offset 1000 as default and end at 19FFFF making the XIP start at 20000. Coz after using the tool, the ULDR at 1000 is only filled with "FF FF FF FF FF FF FF FF" as default is "FE 03 00 EA 00 00 00 00"

Wont quote your earlier line :p I checked the PPCGeeks link you gave me and was going to reply to you, but forgot. Sorry. Calcu has used 0mb PP which gains the available Ram. There's no pagefile which can be deleted in Win Ce
[Windows Mobile Software Development] ervius:
I can change the textbox with a combobox, so you can choice a right value, between min-max value of xip lenght.....

maybe tlnight I update the soft.....
[Windows Mobile Software Development] Ameet:
I tried it again. Manually changing those values and clicking "write" does do the job but then it wil be great to have an option to watch the preview to know exactly what is going to happen ;)

Hopefully, you would also have a solution to the non booting ROM coz of the payload size and the MBR bytes :)

Is it possible for you to make the kitchen keep the payload size what it is just reducing the ULDR by 300000 bytes and shifting the XIP and increasing the imgfs? Maybe then the OS.nb can be made for template using -conservative switch without any manual editing and cooking
[Windows Mobile Software Development] abusalza:
hi ervius, regarding my question. should i change those file as for kaiser reference?
[Windows Mobile Software Development] itje:
does the os.nb affect the language setup?

I have been porting the 757 build to xperia, and it works great.

Now I have changed language on sys and in oem, but after booting up, the system is a mismatch of both norwegian and english. What can cause that? (I used xip from a norwegian blackstone build, the same with sys)
[Windows Mobile Software Development] anryl:
just ported 20940 xip to kaiser with ervius new kitchen xip tools it is perfect.

for the uldr removal on kaiser i tried every possibility to move the imgfs but no booting or white screen or no booting probably as abusalza tested already we can not move the imgfs past some adress on kaiser.

gona test next releases but i think it wont work without uldr ever. :(

edit rev.7 no go again tried 5c 60 6c white screen no uldr NO GO

the xip size is not updated in header 1da 1db and the imgfs starts allways at 400000 so have to insert FF to get it where i want to
[Windows Mobile Software Development] ervius:
new updates:

revision 7:

http://rapidshare.com/files/171258728/XipporterEx_version_1_2_revision_7.rar

now you can choice in a range from min/max values for xip lenght, so, if I readed well, also into kaiser is possible to make a good bootable rom, pratically, you can choice for xip lenght, a range of values, from riginal ann optimized (maybe for kaiser last value can be 5a0000, if I remeber well.....)

try it.....

bye!!!
[Windows Mobile Software Development] Blackdragon_860:
sorry but i became everytime this message:

No IMGFS signature found. Exiting.

what i must do?
[Windows Mobile Software Development] Olioaglio:
The ROM you are trying to dump is protected... :(

Olioaglio
[Windows Mobile Software Development] pawaj:
Are imgfs & imgfs_header in MyTools can use with Artemis ?
[Windows Mobile Software Development] ervius:
today, I've modified the apps, so it can recognize 0x800 or 0x200 rom block, but someone have to test it.....

I'll post as soon as possible.....
[Windows Mobile Software Development] Blackdragon_860:
and how i can remove the protection?
[Windows Mobile Software Development] :
you dont. That is something the rom cook place in there so that you can not decompile the rom and then use thier work. And i am going to say that you are trying to decompile one of UDK rom. and if that is the case. well have a fun time scratching your head.
[Windows Mobile Software Development] Blackdragon_860:
no, thats not true..

i have used the official one for niki..

but i am looking for solving this problem
[Windows Mobile Software Development] pawaj:
Thank so much
[Windows Mobile Software Development] :
This xip tool is not working on the Touch Pro. It works and it will boot, but it is placing everything into the diamond partions. Where I only end up getting 72 mb of free space. where has before I would have 280.

Not sure what I am doing wrong. It ports the xip fine. but I cant handle it cutting out 200 mb of free space.
[Windows Mobile Software Development] magic55:
I can confirm that xip porting is problematic.

19974 - ok,

20757 - problem,

19971 - problem

Many times, many tests. By the way xipport works ok. I think that your tool has a problem to save xip.bin directly to the right address on Touch Pro.
[Windows Mobile Software Development] Ameet:
I think till many tests are done on the resulting payload, one should continue doing manually removal of ULDR & increasing of IMGFS ;)

I sincerely feel the problem lies in the resulting payload being smaller (3.8mb only) After doing this the OS.nb has to use the -conservative switch in nbmerge and ImgfsFromNb tools and the smaller payload with this switch wont support adding larger new imgfs to it :(
[Windows Mobile Software Development] magic55:
For my other device X800 I have used great kitchen made by kva based on bepe's tools and *.jar scripts to build ROM.

http://eten-users.eu/index.php?s=&showtopic=13131&view=findpost&p=78248
[Windows Mobile Software Development] hellonasty:
now i'm trying reduce my os.nb.payload but dont start... dont boot.
[Windows Mobile Software Development] abusalza:
well! one of the best tools!

but not working for uldr removal on kaiser. it's read imgfs start at 6C0000 instead 700000. after reducing xip length it's not correctly writing mbr.

will try another way later;)
[Windows Mobile Software Development] Calkulin:
Instead of removing a module, how can one add one and create a corresponding .txt file? I can figure most of it out but I just can't figure out the lpszFileName, so does anyone know how to do it or create the whole .txt file? I wanna test something but without that, it won't create the xip correctly
[Windows Mobile Software Development] ervius:
new version revision 8, now, maybe, it can works with 0x800 and 0x200 block roms, mut you have to test it, and if you leave the binds temp files, you can see:

boot.bin, uldr.bin, xip.bin and imgfs.bin (only original!)

tell me about!!!!!

download here:

http://rapidshare.com/files/171845907/XipporterEx_1_2_Revision_8.rar

bye!
[Windows Mobile Software Development] Ameet:
what do we download when the file is deleted by the original uploader :rolleyes:
[Windows Mobile Software Development] ervius:
yes, becouse, it wrote 2 times new xip addresses in MBR table and not new IMGFS table..... try this one!!!

http://rapidshare.com/files/171902826/XipporterEx_1_2_Revision_8.rar

bye!
[Windows Mobile Software Development] anryl:
xipporter

Bug on first screen m8 Find start xip offset not working i have to open xiptool done then it is working ?

moved imgfsstart from 6c to 64 working rom booting xip on 32 uldr not reduced

good job :D
[Windows Mobile Software Development] ervius:
strange, I've just tested on an original 1.97 Italian rom, and.....

and it boots well..... ;)

send me your own payload so I can analyze it.....
[Windows Mobile Software Development] anryl:
ITS booting fine i just did not test removal of uldr yet just tried reducing xipsize

but if i want just xipport then the find offset resulted error.

uldr removal on kaiser have to test when i got more time

rev7 : ported xip 20764 20931 20940 perfect
[Windows Mobile Software Development] ervius:
from rev 5 to actual (8) I only reprogrammed all uldr/xip reducing on payload, nothing touched on xipport part!
[Windows Mobile Software Development] anryl:
i dont know but its there
[Windows Mobile Software Development] ervius:
uhmmm.... investigating about.....
[Windows Mobile Software Development] abusalza:
hope anryl can up payload from kaiser.

just making me confused on payload. imgfs header start at 700000, divisible 20000 but showing 36 instead of 38. it's make your tool read imgfs start at 6C0000.

uldr start at 1000
[Windows Mobile Software Development] ervius:
bug defeated:

revision 9 here:

http://rapidshare.com/files/171927082/XipporterEx_1_2_Revision_9.rar

P.S.:in some cases, IMGFS start at offset xxxxx, in MBR table, but really, it start into payload bytes and bytes after, in fact you see only FFFFFFFFF, for now the tools read MBR table and start from it to find all sections, but in next releases, I'll try to delete all FF unused before real IMGFS section start into Payload.
[Windows Mobile Software Development] chavonbravo:
Question on reducing ULDR. When this is reduced, everything gets moved over to a smaller address, including the end of the fat partition. Why isn't the FAT partition made bigger by the amount reduced in ULDR so that it ends in the same place it ended before?? Wouldn't this give more storage?
[Windows Mobile Software Development] abusalza:
i don't think so. you will have more storage only if you touch imgfs section, and reduced uldr or xip partition. FAT partition just a left amount of total partition (on kaiser total of 4 partition is D95F000 = 227930112)

but it's just what i'm think:p
[Windows Mobile Software Development] anryl:
WORKING rev:9

ImgfsFromNb 2.1rc2

Sector size is 0x800 bytes

ImgFs partition starts at 0x00340000 and ends at 0x04de0000

Dumping IMGFS at offset 0x00380000 (size 0x04a60000)

Done!

ULDR ON KAISER REMOVED :D

i have now 136.79 MB ( 12.82 used , 123.97 free ) MEM 85.32 MB ( 36.46 used , 48.86 free )
[Windows Mobile Software Development] Ameet:
I think that is a case only with shipped ROMs. Coz my shipped ROM MBR shows imgfs starts at 7A0000 but physically it starts at 7E0000. But the first cooking without any edits, it corrects itself to 7A0000 ;)
[Windows Mobile Software Development] Ameet:
So you cooked the final ROM using -conservative switch? Did you convert the payload into OS.nb for template using -conservative?
[Windows Mobile Software Development] !Aman!:
thats because of -bigstorage mode ;)
[Windows Mobile Software Development] spastico:
I'm on day 3 of reading & searching on how to get a working XIP from my Treo Pro's Rom Dump.

So far I have dumped and packaged to OEM & SYS

(that was the easy part)

I've renamed Part01.raw to xip.bin

Am I now in the right place (this thread) to convert Part01.raw (xip.bin) to XIP?

Also, you say:

Do I use the above OS.nb.payload, or should I use a different base for doner?

There has been no official release from palm, which I could then just do nbh to nb.

All I have started with is the .raw files dumped from my treo pro.

Am I going to be able reconstruct what I have to a flashable rom?

TIA,

Berd
[Windows Mobile Software Development] spastico:
I should mention;

This is how far I got with XIP using another tutorial:

I'm not sure if any of what I've done with XIPPort is going the right direction or what.

Thanks Again,

Berd
[Windows Mobile Software Development] c_shekhar:
Rev_9 seems to be having some problem.

1. The xip_Out.bin created after porting does not show "initialized data of region_1 " in the Map.txt.

2. I put same xip.bin in folder xip.bin_old as well as xip.bin_new. Then I press PortIT!. It gives me xip_out.bin in XIP_new_Ported folder.

Then I dump this XIP using XIPPORT and write maps. I observe that it does not have 3 modules in OUT\Modules.

That means three modules are lost during porting. Thats strange...
[Windows Mobile Software Development] Ameet:
Back to my sudden problems with the XIP shifting and ULDR removal. I tested it with Aman too. Did the calculations in MBR & MSFLSH50 regions perfectly. Removed data from correct offsets. Converted the os.nb.payload into os.nb with -conservative. Cooked the new ROM with -conservative in NbMerge and ImgfsToNb tools, yet the ROM is non booting. Gets stuck at the screen with red letters :(

Anyone else facing the same issue or do I need to format my PC? :(
[Windows Mobile Software Development] anryl:
i did not convert it to os.nb .

i used the payload for coocking .

no conservative

@echo off
CD..
copy ROM\OS.nb.payload temp\OS.nb.payload
cd temp
..\TOOLS\ImgfsFromNb OS.nb.payload imgfs.bin
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin > out.out
..\TOOLS\ImgfsToNb imgfs-new.bin Os.nb.payload Os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
cd..
echo Copying OS-new.nb in \TOOLS Folder...
copy TEMP\OS-new.nb tools\OS-new.nb
cd tools
autopatcher_v1_cli.exe -cert os-new.nb
htcrt.exe /buildrom proj\kaiser.htcrtproj kaisimg.nbh -build
echo FINISHED
[Windows Mobile Software Development] Ameet:
Hey Anryl. But you are cooking for Kaiser right? Will the same work for Diamonds too since for both the sector sizes are same? If this works then I'll have to change the tutorial too, will test it out tonight ;)
[Windows Mobile Software Development] !Aman!:
yeah, u can also use the payload as template. if u do that, u need to edit the kitchen a bit, so that it copies the payload from \ROM instead of NB.
[Windows Mobile Software Development] Ameet:
Hey Aman, I'll try it out tonight itself :D

Btw, with so much happening now in open for Diamonds and newer devices, how about testing the RTC too? :D
[Windows Mobile Software Development] !Aman!:
:D yeah. but first we should sort out the problems being faced by u.
[Windows Mobile Software Development] ervius:
why did you use -conservative mode?

I allways cook my roms with bigstorage mode and allways all works well...

P.S.: the resulting payload you can also flash directly it, using nbmerge -kayser os.nb and then converting it into nbh file, so after building new os.nb.payload, you reduce it with xipporterex, and then merge it into os.nb.....

P.P.S.: and, I can test only on diamond, so on a device that suppirts 0x800 bloxk rom, for 0x200 block roms, I need help, becouse teorically all seems to be right, but pratically.....

bye!
[Windows Mobile Software Development] ervius:
nbinfo told me all infos about.....

you can see 2 payloads from original 1.97 WWE original diamond rom (reduced using a blanc \temp\dump folder), before a nd after using my xipporter tools.....

and nbinfo_xxx.txt shoes nbinfo results on both, all seems to be right, and I can confirm that the resulting payload after using my tool, boots well on my diamond.....

download and check.....

http://rapidshare.com/files/172030886/xipporterex_revision10_results.rar

bye!

P.S.: for my italian 1.97 kitchen I used a payload of 7.5 Mb, like the os.nb.payload_before, and all works well....
[Windows Mobile Software Development] ervius:
using xipporterex, it deletes all unused modules, don't warry, the resulting xip_out.bin is good, on diamond boots, if there are differences for other devices, tell me all modules needed to have a resulting good xip.bin, and I'll provide to modify the tool, to preserve all needed modules to have a good xip on non-diamond devices.
[Windows Mobile Software Development] Blackdragon_860:
can somebody say me when i must write the xip with the tool?

before i remove the ULDR (at 0032000) or after (002000)
[Windows Mobile Software Development] ervius:
when you want, you only have to insert preferred payload file into "\payload folder"

and insert xip into!

but is preferred before, so the xiptools can cut better the payload after you have inserted a smaller xip.bin into it! ;)
[Windows Mobile Software Development] Ameet:
Hey brother. It will be great if you can make the XIP size option more friendly by making it manually editable. for e.g. my xip_out.bin size is 301A32. As per your current tool I have to make the XIP size lowest which is 3FFFFF and make the IMGFS start at 420000. Why waste space when I can have XIP of size 320000 and make the IMGFS start at 340000? :D

Flashing in some time, so will know the results :)
[Windows Mobile Software Development] ervius:
to respect block size, if yours is 301A32, is larger than 2FFFFF, so: 2FFFFF+20000=31FFFF, strange that you cannot choice right space, maybe you have to "insert.exe" the xip into payload, then you have all "FF" after xip end, that my progrz recognize like unused space, and can return real xip size into combobox!

editing by hands, means that a lot of users will have non bootable rom after....

but if you want (experts!) I can build an app whit non-readonly textbox into xip size ;)
[Windows Mobile Software Development] ervius:
new revision 10, inserted:

conservative mode switcher (if have unused space before IMGFS header)

and more space saving if your xip_out.bin is more smalled that original old into rom (by clicking "give from your xip_out.bin" if you have builded and inserted new into your payload!)

so: verions are:

revision 9 (full working for me!) here:

http://rapidshare.com/files/171927082/XipporterEx_1_2_Revision_9.rar

revision 10, new to test for new opotions inserted!, here:

http://rapidshare.com/files/172125712/XipporterEx_1_2_Revision_10.rar

tell me about.....
[Windows Mobile Software Development] hellonasty:
Ervius and the good work!!! :D

The os.nb.payload in your folder os_nb_payload_Reduced is working for you?
[Windows Mobile Software Development] ervius:
yes........

and.....

revision 11 of program, maybe there were something else to hexedit, try with your own payload, then use it to build new rom with your preferred kitchen, tell me if works now.....

here:

http://rapidshare.com/files/172247969/XipporterEx_1_2_Revision_11.rar

bye!
[Windows Mobile Software Development] c_shekhar:
It is only a syggetion. If feasible..

Kindly dont develop such a wonderful utility keeping in mind only "Diamond". There are other types of devices too. cachefilt.dll or mencfilt.dll or encfilt.dll are not completly redundant modules. But, they are removed by this utility.

I would suggest that your utility should not remove any of the modules on its own. Let this option be given to the user.

Secondly why does it not display the "initialized data of region_1" (sections from 01f901fd to 02000000) in the Map.txt when dumped using the traditional XIPPORT?

I am very excited about this utility indeed..
[Windows Mobile Software Development] ervius:
for the modules yes, its possible, with the flags to choice what delete what not....

gor the section until 20000, all modules ewrw g'relocked, builded into a mini payload and then redumped, maybe this operation delete this part, but on my diamond all seems works perfectly.

P.S.: seems that xipporter revision 11 works perfect, I used original 1.93 diamon payload, edited with tool, inserted my own xip into , reduced, and used to build new rom, and boots well ;)

bye!
[Windows Mobile Software Development] PhamQuang:
Rev. 11 work well for Raphael !!!

Thank Ervius.
[Windows Mobile Software Development] ervius:
thanks all you for testing, and upping revision 12 that have choice for delete:

chacefit.dll

mencfid.dll

and encfit.dll

some minutes..... ;)

EDIT:

revision 12 here:

http://rapidshare.com/files/172346856/XipporterEx_1_2_Revision_12.rar

bye!

todo, pagepool patching (to have working pagepool with pagepool changer!) for diamond ;)
[Windows Mobile Software Development] Alexx~:
It is possible still to add hd.dll, initvmmap.exe, osaxst0.dll, bmui.nb0, wince.nls?
[Windows Mobile Software Development] ervius:
yes, I need some more space into form... heheheh!!!

but:

hd.dll and osaxst0.dll are useless, mbui.nb0, yes, can insert into, and wince.nls, is untouched, if the program find it into original xip (old xip), it leave, if not, not insert it.

and remeber, you need some more free space into xip to build new with greater modules, if I leave all inside, xipport give you error and can't build new xip.bin ;)

next release so...... ;)

bye!
[Windows Mobile Software Development] Alexx~:
I need in replacement cecompr.dll for support LZX (XIP for my device from official wm 6.0 ROM supports only XPR). How it can be made with the help of your program?
[Windows Mobile Software Development] ervius:
for now, insert it by hands, (or insert module without relative txt into oem\oemdrivers! ;) ) then I'll add also this option.
[Windows Mobile Software Development] Alexx~:
By hands I certainly shall insert, but it would be desirable to have a complete cycle.

In any case, thank for the answers:)
[Windows Mobile Software Development] anryl:
rev 11

working OK tested xipport and reduced conservative :D

edit :

rev12 working as well

the posts are too fast didnt catch that one :D
[Windows Mobile Software Development] c_shekhar:
Wow! so fast, so swift. I suggest and you deliver. Great man, you are great. Three cheers to you..

I shall test and get back to you with comments..

EDIT: Observations..

1. Tested the tool. It is still deleting the htcfsfilter.DLL from \OUT\MODULES .

2. Still it does not display the "initialized data of region_1" (sections from 01f901fd to 02000000) in the Map.txt when dumped using the traditional XIPPORT? In my opinion you are forgeting to store the dllfirst (D=01F901FD). because in the imageinfo.txt of the modules it does not show the "D=" against o32[1].o32_realaddr:
[Windows Mobile Software Development] magic55:
v.12 is working for Touch Pro. Thanks !!!!
[Windows Mobile Software Development] Ameet:
WOW!! You going at lightining speed brother :D

Only xip porting works on my ROM and nothing else. Will try cooking on another PC and re test ;)
[Windows Mobile Software Development] Blackdragon_860:
for niki nothing works..

i am testing since 5 days, every version and every possible combination but nothing :-(
[Windows Mobile Software Development] ervius:
niki has 0x200 block size into rom, but maybe xipporting must work correctly, for uldr reducing and xip moveing, I cannot try, only theory for me!!!!
[Windows Mobile Software Development] anryl:
im using os.nb.payload from latest oficial build with ervius buildos package tool 5.3

in mytools\os.nb.payload insert oficial payload for my device

in xip.bin_old inserted my oficial xip.bin or use the xipporter for extract it from payload

in xip.bin_new - yeah the nex xip.bin whatever device i get

thats it for xipporting

if u start xipporter from kitchen 5.3 it will copy payload modified into rom folder

if u then test reducing sizes u have to copy reduced payload manualy into rom folder for coocking

dont forget to write ported xip into payload as it wont boot (did few times :D )
[Windows Mobile Software Development] :
anyone know a good way to reduce size on os.nb.payload?

If i use an officical rom on touch pro, the os.nb.payload file is 117mb. i can port xip, and reduce the uldr fine. and everything works. remvoing the uldr takes it down to 114 mb. So it is getting removed and everything.

I have so that i try and use, but when i remove the uldr it wont build it. it cant find the uldr.

If I try and use the os.nb.payload that is already in the folder. it is from diamond and it has the partions messed up.

Also revison 7 cut the offical os.nb.payload down to 4.5 mb. but it would not boot. imgfs could not be found.

So is there any easy way to reduce this file size?