yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] Blackdragon_860:
ok, since rev 12 uldr removing works perfect on niki..

the problem is only by xipporting..

i tested my manually ported xip and it works.

then i tested your tool with the same xip and it doesnt works.

but after all that i never say,

that you have made a greate work..

continua cosi ervius..
[Windows Mobile Software Development] ervius:
well!!! thanks!!

but a question:

for niki, don't you have buildxip.exe?!?!!?

bye!
[Windows Mobile Software Development] abusalza:
just using os.nb.payload from ervius tools and now it's working for my kaiser.

just found a different with official it's "NULL" header at start of uldr. if you want using official os.nb try to change your uldr header with "NULL", maybe that's hacked to get booting rom after uldr removal

EDIT: thanks ervius for a great tools as always;)
[Windows Mobile Software Development] Ameet:
you are really on fire :D by the way, where is the pagepool hack? didnt see any in rev 12 (i thought you had it there) also brother, in rev 12, selecting xip_out.bin of size 320000 didnt change the no of sectors to 40 06 :( it kept them as 00 09 :( hopefully that is solved in rev 15 :)

EDIT: No.. Same thing in rev 15 too. Doesnt change to 40 06 instead keeps it 00 09 when even the XIP LBA is 40 00 and IMGFS LBA is 80 06
[Windows Mobile Software Development] :
It does not work on the rapheal or diamond, gives me an error saying "PP sign Not Found! Nothing to patch, or try by hands!"

But when i try and change using pagepool changer. vs 2.2.1. It says it change. but it does not change it on boot. I am still at the 203.49 mb like i was before. So not sure what needs to be done.

If this is your last build. thanks for all your help on this great tool ervius.

edit: My guess is that CDMA is different pp hex strings. Following the guides in post 5. I cant find any of those stirings anway similar to those. So my guess is CDMA is different. and we are just out of luck. unless someone knows what to look for.

edit: okay after looking more into it. I have been able to come up with this. CDMA Rapheal page pool hex string in nk.exe s000. The offset location is 000590E0, and the string is 03 15 A0 03 06 16 A0 13 00 10 83 E5 3E BB FF EB. That is the CDMA rapheal Pagepool information. located in nk.exe s000.

CDMA Diamond is located at offset 00056900, That string is 03 15 A0 03 06 16 A0 13 00 10 83 E5 E9 BB FF EB.

Does anyone know what I need to change these last 4 bytes to in order to make it work? Or is there any way to get this place into a new versious ervius :D. If we know how to get it patched?

If you need anything else let me know. I can test has well. I have both devices sitting in front of me, so let me know.

EDIT: On the CDMA Rapheal (Touch Pro) in order to get the page pool changer to work, you need to edit the hex string to this.

from 03 15 A0 03 06 16 A0 13 00 10 83 E5 3E BB FF EB

to 03 15 A0 03 06 16 A0 13 00 00 A0 E1 3E BB FF EB

I will test tomw on the diamond and get the setting for that. If you wanted it might be good to add these value to post 5.
[Windows Mobile Software Development] ervius:
try by hands to change xip lenght from 0x900 to 0x640, and try to flash it then, on my diamond the rom doesn't boot, if on yours, it boot, then I'll change it, try.....

for pp patcheng, it search only for some bytes, not of all into post 5, I hope this can help laso some other devices to have pp changer working, and if doesn't work, 2 things: or is yet patched, or doesn't match STR Rx, [Ry], and don't patch it, becouse could waste all!

and...

ababrekar, try to change by hands and if boots, I'll have all into source, I have "REMmed" the modifying part on xip size hexedit!

bye!
[Windows Mobile Software Development] Ameet:
So changing the XIP by hand doesnt boot your ROM? :eek: This is news

I'll test both ROMs one with the XIP no of sectors edited and not edited by hand and see. I also have to check by cooking on another PC, coz none of the guides except XIP porting works suddenly :(

EDIT: Moved Ervius's post with Final Version (revision 15) moved to Post #11 (http://xdaforums.com/showpost.php?p=2813417&postcount=11) and updated the first post index ;)

@Ervius. Gave you the control of post #11 brother. Please post the future versions and updates there so it will be easier to find :)
[Windows Mobile Software Development] bouod:
for my TD every thing is working with v12

thanks ervius for the greate tool and ababrekar for the manual

just one question

How to Reduce os.nb.payloa size

can I just delete every thing after "wce_rex.dll" ??

thanks
[Windows Mobile Software Development] abusalza:
both 0x900 and 0x580 working on mine with kaiser. but not checking for total size partition (0x900) if it's still D95F000

thanks ervius
[Windows Mobile Software Development] abusalza:
wce_rex? did you mean on xip region?

please tell more specific...
[Windows Mobile Software Development] bouod:
I open ervius os.nb.payload with hex editor and notice wce_rex.dll is the last thing in it

so I asked . .

is it that easy to reduce os.nb.payload ??

by delet every thing after wce_rex.dll well it work?? . . . I think NOT
[Windows Mobile Software Development] abusalza:
you had answered:D

wce_rex is the last last thing on the xip region. after that will be continues by imgfs region. so you can't delete it if imgfs start not divisible by 20000.

please look first page for details by AB
[Windows Mobile Software Development] ervius:
well, thanks!!!

last version: revision 18, I modified the pagepool sign search, maybe it will work better now, I tryed on xips from: diamon, raphael and blackstone and seems work well.....

download here:

http://xdaforums.com/showpost.php?p=2813417&postcount=9

try it and report please ;)

and.... for xip size changeing by hands, from 0x900 to 0x640 (or 0x600 or 0xXXX)??? what about?, on my diamond continues to not work if change from 0x900.....
[Windows Mobile Software Development] abusalza:
maybe you can make an options to keep it 0x900 or following the real xip size!
[Windows Mobile Software Development] ervius:
no, maybe is better to try, and report, I'd like to have a real xip size instead of non.original from old xip size ;)

probally it has to work, becouse the xip ends at 0xXXX, where starts IMGFS part, then, so it has to works, but for an unknows reason, on my device it doesn't....

try, hexedit by hands and report, we are near the final full functional version :)
[Windows Mobile Software Development] abusalza:
i had tried and both of them working!

but i'm forget to check if total storage still shown D95F000 (regarding on FAT partition as left of total storage size)
[Windows Mobile Software Development] ervius:
well... for FAT, if I'm not wrong, when you build new rom, all done by the imgfs tools used to build it, so them reallign all, from imgfs (end) to fat (start-end!), if i checked well...
[Windows Mobile Software Development] abusalza:
i guess FAT and imgfs reallign following all the partition size on mbr.

uldr - 3E 00 00 00

xip - 00 09 00 00

imgfs - 40 00 00 00

fat - (it must be) 40 A9 01 00

anyway i'm not known what's effect if total storage has less or more than D95F000:D
[Windows Mobile Software Development] abusalza:
oh, 1 Q ervius. can i reduced uldr less than 1FFFF?

i 'd tried to put xip start at 1800 (i mean i make uldr size into 1. 1800-1000=800 <=> 800/800=1). but device won't boot. maybe something i'm left?
[Windows Mobile Software Development] :
Revision 18, pagepool is still not getting patched. Not a big deal though. I have it figured out. So I am not going to worry about it.

CDMA is different and so its a pain.

EDIT

Revision 19, Pagepool patcher does not work. Still not found. I did send you a link with both xip.bin. so you can take a look at those. Revision 19 looks nice. very good features in there. Thanks for all this.
[Windows Mobile Software Development] ervius:
I just tryed on 2.00 diamond xip and it found pagepool sign, give me yoyr own xip.bin and tell for what device is it! ;)
[Windows Mobile Software Development] anryl:
just tested rev:18 with the give from your xip out bin

IT IS WORKING BOOTING PERFECT

but if you try then to make xip bigger by seccond time it gets some crazy numbers
[Windows Mobile Software Development] ervius:
yes, doing 1 thing for time ;)

use it to reduce now :)

and, revision 19 is ready at post 09:

http://xdaforums.com/showpost.php?p=2813417&postcount=9

added:

payload tools, to patch pageppol protection and Cert file protection, directly on a payload

and

"flag" to rewrite real xip size into payload to coock, after uldr,xip reducing...

so you can test it and report if it works or not (if ppc boots or not) specifiyng kind of device and options into bat: (conservative or not conservative mode!)

bye!!!
[Windows Mobile Software Development] Ameet:
:D Go Ervius!! :cool: Great work my brother :D Am formatting my PC so will know in sometime of re settings whether something was wrong with the PC or the device that it doesnt take anything else other than just XIP porting :D

Great job brother
[Windows Mobile Software Development] g0dspeed:
Hi, ervius

Please import new XIP's 'nFilesize'　& 'ftTime' value (in [filename].txt).
[Windows Mobile Software Development] Ameet:
how do these values help?
[Windows Mobile Software Development] g0dspeed:
for "perfect" porting.

Files & imageinfo.txt values from newXIP, but these 2 values from oldXIP.

if old one are the same as new one, never mind.

#I think these values are not important for boot.
[Windows Mobile Software Development] anryl:
rev 19 write new xip size into mbr NO BOOTING
[Windows Mobile Software Development] ervius:
well, continue testing, while I made revision 20, some graphical updates and improved pagepool protection sign searcher.....

downloadable at this post:

http://xdaforums.com/showpost.php?p=2813417&postcount=9

bye!!!
[Windows Mobile Software Development] :
pagepool is now patched on both CDMA diamond and Rapheal. Thanks for getting that right.
[Windows Mobile Software Development] anryl:
rev 20

REV.:20

original payload

0100203F0118 02000000 3E0600000000

0119233F0135 40060000 400700000000

0136253F818A 800D0000 409500000000

818B043F81CA C0A20000 0010010055AA

xiptool SETTING

uldr 1000 1FFFF

xip 20000 31FFFF

imgfs 340000

FAT 4DE0000

+conservative

+new xip size into mbr 31FFFF

reduced payload

0100203F0100 02000000 3E0000000000

0101233F011D 40000000 400600000000

011E253F818A 80060000 409500000000

818B043F81CA C09B0000 0010010055AA

coocked os-new.nb.payload

0100203F0100 02000000 3E0000000000

0101233F011D 40000000 400600000000

011A253F81A5 80060000 00A300000000

81A6043F81AE 80A90000 4002010055AA

RESULT BOOTING OK

Pagepool on kaiser not found or yet patched

edit : xipsize 2DFFF and 2FFFF - NO BOOTING

edit : -conservative +new xip size into mbr xipsize 31FFFF BOOTING OK
[Windows Mobile Software Development] Blackdragon_860:
same problem here, with niki
[Windows Mobile Software Development] ervius:
well, thanks anryl,

for pagepool 'patcheng, are you shure that it has to be patched????

Maybe you don't have this kind of problem, you have to postto me file: nk.exe, so I can check it!
[Windows Mobile Software Development] anryl:
:rolleyes: dunno
[Windows Mobile Software Development] g0dspeed:
\nk.exe\S000

5120C: 00 E0 84 05 -> 00 00 A0 E1

5121C: 00 E0 84 05 -> 00 00 A0 E1

51258: 00 E0 84 05 -> 00 00 A0 E1
[Windows Mobile Software Development] ervius:
seeing about....

EDIT, seems that this nk.exe doesn't need to be patched (not yet patched, but born without needed of..., but only CMONEX can confirm about, she is the Real GURU of ARM Asm!!! ;)
[Windows Mobile Software Development] Ameet:
XIPPort Settings

ULDR 1000 - 1FFFF

XIP 20000 - 31FFFF

IMGFS 340000 - 3A5FFFF

FAT 3A60000 - D37FFFF

No -conservative

unedited (shipped os.nb.payload simply recooked without -conservative)

01 00 20 3F 01 18 02 00 00 00 3E 06 00 00 00 00
01 [COLOR=red]19[/COLOR] 23 3F 01 3C 40 06 00 00 00 09 00 00 00 00
01 [COLOR=red]3D[/COLOR] 25 3F 41 F5 40 0F 00 00 40 6E 00 00 00 00
41 [COLOR=red]F6[/COLOR] 04 3F 81 BE 80 7D 00 00 40 32 01 00 55 AA

os.nb.payload reduced (revision 20)

01 00 20 3F 01 00 02 00 00 00 3E 00 00 00 00 00
01 [COLOR=red]01[/COLOR] 23 3F 01 24 40 00 00 00 00 09 00 00 00 00
01 [COLOR=red]25[/COLOR] 25 3F 41 F5 80 06 00 00 40 6E 00 00 00 00
41 [COLOR=red]F6[/COLOR] 04 3F 81 BE C0 74 00 00 40 32 01 00 55 AA

os-new.nb.payload (cooked)

01 00 20 3F 01 00 02 00 00 00 3E 00 00 00 00 00
01 [COLOR=red]01[/COLOR] 23 3F 01 24 40 00 00 00 00 09 00 00 00 00
01 [COLOR=red]1A[/COLOR] 25 3F 41 D7 80 06 00 00 80 6F 00 00 00 00
41 [COLOR=red]D8[/COLOR] 04 3F 81 9B 00 76 00 00 00 31 01 00 55 AA

F%$#ing ROM just wont boot :mad: Its like my Diamond has now refused to accept any ROM cooked with anything except the XIP porting, which still works :(

I tried on another PC, another kitchen, reinstalled everything and tried again :( Anyone care to explain why the 2nd bytes are changing?
[Windows Mobile Software Development] c_shekhar:
@ervius

I have found the solution. I was replacing the .VM and .ROM in your My TOols with my polaris .VM and .ROM . I think that was not to be done. Now, I continue with your original .VM ans .ROM and it shows the "initialized data of region_1". My mistake.....

But regarding deletion of the htcfsfilter.dll, Is it really so difficult in your program algorythm for not allowing the tool to delete any module/file without users' control? I notice that You had to add a separate checkbox for each of the module not to be deleted.

Else, kindly add one more checkbox for this one too, like other three checkboxes...

If it is possible...
[Windows Mobile Software Development] g0dspeed:
if you upload os.nb.payload[0x000~0xFFF:first 4KB], I will check/try for you.
[Windows Mobile Software Development] ervius:
is not a problem to assign a flag for each file or module inside, is a problem of phisical space inside, usually, when you port a new xip, new modules are larger, so you need some more space, and 2 are solutions:

1) enlarge xip, playing on lastdll offset etc...;

2) deleting some unused modules/files,

I think is bettere the 2nd choice ;)

so no more modules will be added to choice if keep or not!
[Windows Mobile Software Development] ervius:
don't warry, from revision 19 to 20, I modified/edited also this byte, I seen that is modified on my modified payload from someone that really know the MBR structures, so I decided to edit also that one, but rom boots well, also il the red byte "3D" became "25"
[Windows Mobile Software Development] ervius:
revision 21 at post "9", here:

http://xdaforums.com/showpost.php?p=2813417&postcount=9

some little improvements and creation of "report.txt" to see the differences before/after!

bye!
[Windows Mobile Software Development] jeesus123:
Is this how I inject xip to rom with Raphael or is there other way to do it? If I do like this new ROM doesn't boot past boot screen.
[Windows Mobile Software Development] ervius:
use xipporterex to do that....
[Windows Mobile Software Development] Blackdragon_860:
what? the .vm and .rom must not be replaced by the .vm and .rom from the other device?

can you confirm that ervius?
[Windows Mobile Software Development] ervius:
yes, keep them as they are, seems that *.vm* in \mytools\sys is a modified version (modified into imageinfo.bin) to reallign all xip\ modules..... don't touch it.

P.S.: there is also revision 22 (with xip.bin and os.nb.payload importer!)

here:

http://xdaforums.com/showpost.php?p=2813417&postcount=9
[Windows Mobile Software Development] itje:
I am trying to make a norwegian build for xperia, I have ported the NOR blackstone one, ported xip, exchanged all mui files in OEM folder with my locale (0414) I think I have changed most language related stuff. But still I get a rom with mixed languages? Is this because there are some language spesific files in xip that make problems for me?

I must notice that I have ported and translated many roms before with full success, but somehow it dont work well now.

Any hints on anything could be in xip, or perhaps the os.nb/os.nb.payload?
[Windows Mobile Software Development] ervius:
xip doesn't have language, is universal, so, maybe, with muis you have to edit also initflashfiles.dat in OEM\ folder!
[Windows Mobile Software Development] itje:
allright, thx for the tip. I will try look into it :)

cheers
[Windows Mobile Software Development] xtep:
Error porting XIP 20931 to x7510

I have been trying to port XIP build 20931 to my x7510 ROM, but the ROM never boots.

If I execute "task 37" I have the following error (several times):

ERROR: function @ Ordinal 2799 missing in Module 'coredll.dll'
!!! Please Check your SYSGEN variable !!!

Please help!!
[Windows Mobile Software Development] ervius:
maybe in new coredll.dll you don't have this function (routine), retry with old coredll.dll
[Windows Mobile Software Development] Ameet:
The values of start and size are from Diamond. Like Ervius said, try inserting through the tool or if you wish to go manual then find out the exact values. Getting stuck at boot screen means improper porting by the way coz the ROM wont cook if the values are wrong ;) Maybe problem with nk.exe or some module left out

But this byte changes even when go manually. But the bottom line is nothing works on my device except only XIP porting :( Changed the PC changed the kitchen did everything I could. Maybe the device has stopped accepting ROMs without ULDR and all the edited stuff :mad: I dont understand what is going wrong

Maybe now only Cmonex can help me out, only if she reads this and gets time to help :(
[Windows Mobile Software Development] g0dspeed:
000001C0: 01 00 20 3F 01 00 02 00 00 00 3E 00 00 00 00 00
000001D0: 01 01 23 3F 01 19 40 00 00 00 [color=red]40 06[/color] 00 00 00 00
000001E0: 01 1A 25 3F 41 D7 80 06 00 00 80 6F 00 00 00 00
000001F0: 41 D8 04 3F 82 9B 00 76 00 00 00 31 01 00 55 AA

boot 0x0001F000
XIP 0x00032000
IMGFS 0x037C0000
FAT 0x98800000

XIP-End was wrong. (XIP-End > IMGFS-Begin)

EDIT: Oops! this is only Partition table. I don't know MSFLSH50 header about your rom.
[Windows Mobile Software Development] Ameet:
What do these mean? :rolleyes:

I'll post the MBR block for you to check :) Hopefully you can help me. I'll post the block from shipped rom (working), re cooked shipped rom (working) & uldr, imgfs increasing edited rom (non working) All of these cooked without -conservative switch
[Windows Mobile Software Development] g0dspeed:
please upload os.nb.payload [0x000~0xFFF].
[Windows Mobile Software Development] Ameet:
The MSFLSH50 header in my ROM is good. No issues with that. Reports correct start address of imgfs
[Windows Mobile Software Development] !Aman!:
could u explain what's wrong with XIP end?
[Windows Mobile Software Development] Ameet:
he edited the post to show correct xip no of sectors :rolleyes:

till rev 19 the tool kept the no of sectors in xip partitions as existing (00 09) in mine :)
[Windows Mobile Software Development] !Aman!:
ok, its clear now :D
[Windows Mobile Software Development] Ameet:
Hi Ervius. Last night I tried once again, this time with your os.nb.payload that you have in your tools. The whole operation worked for me :D But what I dont understand is that if I do it manually, it doesnt work (I didnt select to flag the real value on sectors in reduced XIP so the tool kept it as 00 09 instead of 00 06, I fail to understand how that still works :(

Can you post the bat file or commands to get the os.nb.payload like yours? So I can post my payload for you guys to check. I mean my payload is 65 MB while yours is only 4 MB. Although I didnt compare both payloads since it was too late last night. But will do it tonight
[Windows Mobile Software Development] Blackdragon_860:
hey ameet!

you are moderator?

since when?

greets
[Windows Mobile Software Development] Ameet:
Since long :D Maybe you remember "ababrekar"? Just had a nick change recently :D
[Windows Mobile Software Development] ervius:
if you, build a os-new.nb.payload with blanc temp\dump\ folder, your payload became 4mb or around.
[Windows Mobile Software Development] Ameet:
Sorry brother. Didnt understand :o Care to explain the steps a bit in detail? :)
[Windows Mobile Software Development] ervius:
maybe is easyer using this little and just created for you tool.....

http://rapidshare.com/files/173869857/payload_reducer.rar

(place your preferred *os.nb.payload* into the folder and execute the bat file!)

bye!!! ;)
[Windows Mobile Software Development] Ameet:
:D Thanx brother. Bat files are easier to understand :D Will add this to the misc uploads too
[Windows Mobile Software Development] mac_es:
Hi,

XipPorterEx is only for Diamond or it will work for trinity?

Thanks in advance
[Windows Mobile Software Development] hellonasty:
Or see the 539 post or test with your rom!!!

In kaiser work!!!

Good luck!!!
[Windows Mobile Software Development] ervius:
if you refer at xipport, it works, shure, but you have bepe's builxip for trinity, if you refer to rom tools, I wrote that you have to try and report for 0x200 roms block size..

so, try and report if works! ;)
[Windows Mobile Software Development] mac_es:
Thanks but I was asking for room tools. The os.nb.reducer as I understand is an image whith only xip part and an imgfs part whihout any file. So this should work in any device.

Ok I will try, now already have ported 20931 XIP so I guess I will no obtain further improvements no? I was asking because I see you can reduce the size of XIP so you gain free space...

I will wait for a new xip arrival to test your tool. It is my work phone so I can't flash it anytime.

@ervius Thank you very much for your programs. I'm using your kitchen for trinity :)
[Windows Mobile Software Development] c_shekhar:
Hey bro! are you aware , whether bepe's buildXIP is available for polaris too? If yes then can you lead me for a link?
[Windows Mobile Software Development] Blackdragon_860:
yes i know that you are ababrekar, but i never see that you are mod :-)

ervius ma dove lo trovi tutto questo tempo :-)

ervius where you find all this time for programming :-)

greets
[Windows Mobile Software Development] Ameet:
Modified the ULDR removal guide a bit to reflect the latest development and added Ervius's tools to his post so can be downloaded from here itself :)
[Windows Mobile Software Development] abusalza:
And beer link also:D:D:D
[Windows Mobile Software Development] Ameet:
Beer link added in 1st post. Am currently persuing Aman to help me test his (R)eal (T)ime (C)lock trick for Diamonds.., busy guy :D
[Windows Mobile Software Development] Ameet:
Edited Ervius's post to include screenshots of his tool for better understanding of the usage and payload reducer information ;)

Also changed the All Guides offline tutorial accordingly :)
[Windows Mobile Software Development] ramersonw:
hi ervius, first thanks for your tool. Finally I can port new xips to my device without trouble. But I have a problem with rom tools. When i put my os.nb.payload or payload reduced in the payload folder and click rom tools an error window appear (the index was out of range). What it could be?
[Windows Mobile Software Development] ervius:
post to me the payload, and I analyze it!

bye!
[Windows Mobile Software Development] ramersonw:
Hi Ervius the payload is attached.

Thanks.

PS.: Xip already ported.
[Windows Mobile Software Development] ervius:
yes, seems that your payload doesn't have the "Fat" section, try last revision (only exe!) nr. 23 at 1st page of this 3d....

here:

http://xdaforums.com/showpost.php?p=2813417&postcount=9

and report me! ;)

bye!
[Windows Mobile Software Development] ramersonw:
Revision 23

Hi Ervius. It works. :D

Very thanks for the super fast support.
[Windows Mobile Software Development] ervius:
thanks you too, for testing ;)

bye!